CN113238808A - Message pushing method and device - Google Patents
Message pushing method and device Download PDFInfo
- Publication number
- CN113238808A CN113238808A CN202010074719.5A CN202010074719A CN113238808A CN 113238808 A CN113238808 A CN 113238808A CN 202010074719 A CN202010074719 A CN 202010074719A CN 113238808 A CN113238808 A CN 113238808A
- Authority
- CN
- China
- Prior art keywords
- message
- pushed
- client
- service platform
- push service
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 128
- 230000008569 process Effects 0.000 claims description 74
- 238000012545 processing Methods 0.000 claims description 29
- 238000012790 confirmation Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 9
- 239000000126 substance Substances 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 15
- 230000000694 effects Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 4
- 244000062793 Sorghum vulgare Species 0.000 description 3
- 239000005441 aurora Substances 0.000 description 3
- 230000014759 maintenance of location Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 235000019713 millet Nutrition 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 241000272205 Columba livia Species 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44594—Unloading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/484—Precedence
Abstract
The invention discloses a message pushing method and device, and relates to the technical field of computers. One embodiment of the method comprises: determining a message pushing service suitable for the client from one or more preset message pushing services; acquiring a device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier; and acquiring the message to be pushed to the one or more applications from the pushing service platform through the connection. The implementation mode ensures the compatibility of the client and the message push service and improves the arrival rate of the message to be pushed to a certain extent.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a message pushing method and apparatus.
Background
Based on the requirements of product functions and operation activities, many applications push some messages of system notification, consultation and activity types to users through a message pushing function, so that the users can acquire and consume the messages in time. Currently, the commonly used push services (i.e. pushing SDK or pushing software development kit) are: millet push service, Huacheng push service, aurora push service, and the like.
At present, because there are many push services, different manufacturers or applications may use different push services, and application permissions, push channels, flow consumed by push, push message formats and the like corresponding to different push services are all different, and the adaptability to different clients is different, so that the push services do not have good compatibility. In addition, to save resources, the application in the running state is often closed by the system, so that the arrival rate of the push message of the push service is biased, and the user experience is poor.
Disclosure of Invention
In view of the above, the present invention provides a message pushing method and device, which can select a message pushing service most suitable for a client from preset message pushing services according to the client, have universality, and enable an application to be in a running state through keep-alive processing on the application, so as to improve a message arrival rate of a message to be pushed.
In order to achieve the above object, according to a first aspect of the present invention, there is provided a method for pushing a message, which is applied to a client, and includes:
determining a message pushing service suitable for the client from one or more preset message pushing services;
acquiring a device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier;
and acquiring the message to be pushed to the one or more applications from the pushing service platform through the connection.
Optionally, the method further comprises:
and sending the equipment identifier to a service end so that the service end sends the message to be pushed to the pushing service platform according to the equipment identifier.
Optionally, the obtaining, from the push service platform through the connection, a message to be pushed to the one or more applications includes:
passively receiving the message to be pushed by the push service platform through the connection;
or actively pulling the message to be pushed from the push service platform through the connection.
Optionally, the method further comprises:
and after receiving the message to be pushed by the pushing service platform, returning a receiving confirmation indication corresponding to the message to be pushed to the pushing service platform.
Optionally, the method further comprises:
after the message to be pushed is acquired from the pushing service platform through the connection, the acquired message to be pushed is stored in a local cache;
and after the preset caching time corresponding to the message to be pushed passes, pushing the message to be pushed to the one or more applications, wherein the preset caching time is determined according to the time for the user of the client to use the one or more applications.
Optionally, the method further comprises:
keep-alive processing is carried out on one or more applications of the client side, so that the connection between the applications and the push service platform is in a connection state.
Optionally, the keep-alive processing is to configure a daemon process for the application process;
when the application process is closed, starting the application process through the daemon;
and when the daemon is closed, starting the daemon process through the application process.
Optionally, the keep-alive processing is to increase the priority of the application process, so that the application process is closed after other one or more processes are closed.
Optionally, the keep-alive processing is that, when the application process is closed, the application process is started through the determined other applications in the running state corresponding to the message push service.
To achieve the above object, according to a second aspect of the present invention, there is provided a message push client, including: the device comprises a message push service determining module, an equipment identifier acquiring module and a message to be pushed acquiring module; wherein the content of the first and second substances,
the message push service determining module is used for determining a message push service suitable for the client from one or more preset message push services;
the device identifier obtaining module is configured to obtain a device identifier of the client for one device through the determined message push service, and send the device identifier to a push service platform, so that the push service platform establishes a connection between one or more applications of the client and the push service platform according to the device identifier;
the message to be pushed obtaining module is used for obtaining the message to be pushed to one or more applications of the client from the pushing service platform through the connection.
Optionally, the device identifier obtaining module is further configured to,
and sending the equipment identifier to a service end so that the service end sends the message to be pushed to the pushing service platform according to the equipment identifier.
Optionally, the obtaining, from the push service platform through the connection, a message to be pushed to one or more applications of the client includes:
passively receiving the message to be pushed by the push service platform through the connection;
or actively pulling the message to be pushed from the push service platform through the connection.
Optionally, the to-be-pushed message obtaining module is further configured to,
and after receiving the message to be pushed by the pushing service platform, returning a receiving confirmation indication corresponding to the message to be pushed to the pushing service platform.
Optionally, the message to be pushed obtaining module is further configured to,
after the message to be pushed is acquired from the pushing service platform through the connection, the acquired message to be pushed is stored in a local cache;
and after the preset caching time corresponding to the message to be pushed passes, pushing the message to be pushed to the one or more applications, wherein the preset caching time is determined according to the time for the user of the client to use the one or more applications.
Optionally, the device identifier obtaining module is further configured to,
keep-alive processing is carried out on one or more applications of the client side, so that the connection between the applications and the push service platform is in a connection state.
Alternatively,
the keep-alive processing is that a daemon process is configured for the application process;
when the application process is closed, starting the application process through the daemon;
and when the daemon is closed, starting the daemon process through the application process.
Alternatively,
the keep-alive processing is to increase the priority of the application process so that the application process is closed after other one or more processes are closed.
Alternatively,
and the keep-alive processing is that when the application process is closed, the application process is started through other applications in the running state corresponding to the determined message push service.
To achieve the above object, according to a third aspect of the present invention, there is provided a message pushing method applied to a push service platform, including:
receiving a device identifier corresponding to a client sent by the client;
establishing a connection between one or more applications of the client and the push service platform according to the device identifier;
and sending the messages to be pushed of one or more applications to be pushed to the client through the connection.
Optionally, the method further comprises:
and receiving the message to be pushed, which is sent by the service end according to the equipment identifier.
Optionally, the method further comprises:
and receiving a receiving confirmation indication returned by the client according to the message to be pushed.
Optionally, the method further comprises:
storing the message to be pushed to a local cache according to any one of the following conditions: the message to be pushed fails to be pushed, the receiving confirmation indication is not received within the threshold time after the message to be pushed is pushed, and the message to be pushed which is not sent after overtime exists in the pushing service platform.
Optionally, the method further comprises:
according to a preset message processing rule, any one of the following processes is carried out on the message to be pushed stored in a local cache: deleting the message to be pushed and pushing the message to be pushed again.
Optionally, the method further comprises:
judging whether the received message to be pushed sent by the service end conforms to a preset rule or not;
and under the condition of meeting the preset rule, converting the format of the message to be pushed so as to enable the format of the message to be pushed to meet the message storage format of the push service platform or the message receiving format of the client.
To achieve the above object, according to a fourth aspect of the present invention, there is provided an electronic device for message push, including: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method as in any of the message push methods described above.
To achieve the above object, according to a fifth aspect of the present invention, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements the method as any one of the message push methods described above.
The invention has the following advantages or beneficial effects: the message push service suitable for the client is determined through one or more preset message push services, so that good compatibility between the message push service and the client and the message push service is ensured; by the keep-alive processing of the client application, the application is always in a running state, the connection between the application and the push service platform is ensured to be in a connection state, and the arrival rate of the message to be pushed is further ensured; the received message to be pushed is locally cached at the client, and the time for sending the message to be pushed to the application is determined according to the habit, the time and the like of the user for using the application, so that the click rate and the like of the user for the message to be pushed are improved to a certain extent, the experience of the user for using the application can be improved, and the retention rate of the application can be improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of a main flow of a message pushing method applied to a client according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a main flow of another message pushing method applied to a client according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of the main modules of a message push client according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a main flow of a message pushing method applied to a push service platform according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a main flow of another message pushing method applied to a push service platform according to an embodiment of the present invention;
fig. 6 is a schematic diagram of the main structure of a message push system according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a main flow of a message pushing method applied to a message pushing system according to an embodiment of the present invention;
FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a message pushing method applied to a client according to an embodiment of the present invention, and as shown in fig. 1, the method may specifically include the following steps:
step S101, determining a message push service suitable for the client from one or more preset message push services.
The preset one or more message push services include, but are not limited to: millet push service, Huashi push service, aurora push service, carrier pigeon push service and the like, and besides, the message push service can be customized according to actual requirements. Specifically, a plurality of different push services can be integrated through a template design mode, and a uniform interface is provided outwards, so that a proper message push service can be selected according to the actual requirements of a client. Therefore, the adaptability of the message push service and the client can be improved by utilizing the characteristics of different pushes, and the push arrival rate is further improved to a certain extent.
Step S102, obtaining the device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier.
The Device identifier, i.e. Device Token (DT for short), is in one-to-one correspondence with the client, e.g. the mobile phone system, and is generally fixed and unchangeable, so that the push service platform can establish a connection with the push service platform through the Device identifier, so that the push service platform can push a message through the Device identifier. In addition, the push service platform can also push messages to the application of one or more clients according to user accounts, client models and the like used by the client users when logging in the application, so that the directional sending of the messages to be pushed can be realized, and the group sending of the messages to be pushed can also be realized.
In a preferred embodiment, the connection between the one or more applications of the client and the push service platform is a Socket long connection. Furthermore, a Socket long connection between one or more applications of the client and the push service platform is established by using a Netty long link framework, so that a message can be sent to the server according to a certain time interval to ensure the Socket long link, and the length of the time interval can be set according to actual applications. And the Netty refers to a popular asynchronous event-driven Java open source network application framework for rapidly developing maintainable high-performance protocol servers and clients.
In an optional implementation manner, the device identifier is sent to a service end, so that the service end sends the message to be pushed to the push service platform according to the device identifier. That is, by sending the device identifier to the service end, the service end selects one or more clients receiving the message through the device identifier when sending the message of the relevant operation class, advertisement class, and activity class to the push service platform. It can be understood that the service end is bound with a corresponding push service platform by default so as to send the message, and meanwhile, under the condition that one or more push service platforms exist, the push service platform receiving the message can be selected according to the identification of the service platform to complete the push of the message.
In an optional implementation manner, one or more applications of the client are subjected to keep-alive processing, so that the connection between the applications and the push service platform is in a connection state. Therefore, the client application can be ensured to be always in the running state, so that the connection between the application and the push service platform cannot be closed due to the non-running of the application. It can be appreciated that there are many ways to keep alive an application, including but not limited to: dual process daemons, a pixel page, etc.
In an optional embodiment, the keep-alive process is to configure a daemon process for the application process; when the application process is closed, starting the application process through the daemon; and when the daemon is closed, starting the daemon process through the application process. That is, the daemon process polls the application process to detect the state of the other side, and when the other side is found to be closed, the daemon process is restarted immediately to reach the daemon state. Therefore, whether the application is closed or killed by the background can be detected in real time through the dual-process daemon mechanism, if the application is killed, the daemon process can immediately restart the application and run in the background, and therefore long links applied to the push service platform are guaranteed.
In an optional embodiment, the keep-alive process is to increase the priority of the application process, so that the application process is closed after the other process or processes are closed. It can be understood that one or more applications in the client have different priorities in the background runtime, and the higher the priority is, the lower the probability that the application is closed or killed in the background runtime is, so that the possibility that the application is closed can be reduced by increasing the priority of the application process, thereby ensuring long links applied to the push service platform.
In an optional implementation manner, the keep-alive processing is that when the application process is closed, the application process is started through the determined other applications in the running state corresponding to the message push service. Specifically, taking an example that the applications using the same message push service are application a and application B, respectively, when both application a and application B are in a background running state, and when application B finds that application a is closed by the background, application B may restart application a, so as to ensure long connection between application a and the push service platform.
Step S103, obtaining the message to be pushed to the one or more applications from the pushing service platform through the connection.
In an optional implementation manner, the obtaining, from the push service platform through the connection, a message to be pushed to the one or more applications includes: passively receiving the message to be pushed by the push service platform through the connection; or actively pulling the message to be pushed from the push service platform through the connection. That is, the application may not only passively receive a push message from the push service platform, but also actively pull the push message according to a policy, so as to ensure the real-time performance of the push message. Specifically, the client may determine the frequency, time, and the like of actively pulling the message to be pushed according to the memory occupancy rate, power consumption speed, traffic consumption, application response rate, and the like during the application operation, so as to ensure the timeliness of obtaining the message to be pushed while not affecting the normal operation of the client.
In an optional implementation manner, after receiving the message to be pushed, which is pushed by the push service platform, a receiving confirmation indication corresponding to the message to be pushed is returned to the push service platform. On the basis, the push service platform can calculate the arrival rate of the message to be pushed according to the received confirmation receiving indication. Meanwhile, the corresponding message to be pushed may be processed, for example, the message to be pushed is deleted, or the message to be pushed is retransmitted, etc., in case that the message pushing fails or the confirmation receiving instruction is not received.
In an optional implementation manner, after the message to be pushed is acquired from the push service platform through the connection, the acquired message to be pushed is stored in a local cache; and after the preset caching time corresponding to the message to be pushed passes, pushing the message to be pushed to the one or more applications, wherein the preset caching time is determined according to the time for the user of the client to use the one or more applications.
It can be understood that although the application can be guaranteed to be in the running state as much as possible through the keep-alive processing, it is inevitable that the application is in the closed state sometimes, and thus, in order to guarantee the arrival rate of the message to be pushed, the message to be pushed can be temporarily cached in the local cache when the message to be pushed is received, and then according to the user activity, that is, the time period when the user uses the application, and the like, when the cached message to be pushed is sent to the application, so as to improve the probability of clicking, viewing, and the like of the user on the message to be pushed. Specifically, taking the active time of the user as 6:00-22:00 in the afternoon as an example for explanation, the message to be pushed cached locally can be pushed to the application within the time period of 6:00-22:00 in the afternoon, so that the user can see the message to be pushed in time.
Based on the embodiment, the message push service suitable for the client is determined through one or more preset message push services, so that good compatibility between the message push service and the client and the message push service is ensured; by the keep-alive processing of the client application, the application is always in a running state, the connection between the application and the push service platform is ensured to be in a connection state, and the arrival rate of the message to be pushed is further ensured; the received message to be pushed is locally cached at the client, and the time for sending the message to be pushed to the application is determined according to the habit, the time and the like of the user for using the application, so that the click rate and the like of the user for the message to be pushed are improved to a certain extent, the experience of the user for using the application can be improved, and the retention rate of the application can be improved.
Referring to fig. 2, on the basis of the foregoing embodiment, an embodiment of the present invention provides another message pushing method applied to a client, where the method specifically includes the following steps:
step S201, determining a message push service applicable to the client from one or more preset message push services. The preset one or more message push services include, but are not limited to: millet push service, Huashi push service, aurora push service, carrier pigeon push service and the like, and besides, the message push service can be customized according to actual requirements.
Step S202, obtaining an equipment identifier corresponding to the client through the determined message push service, and sending the equipment identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the equipment identifier. The link is a Socket long connection between one or more applications of the client and the push service platform established by using a Netty long link framework.
Step S203, obtaining a message to be pushed to the one or more applications from the push service platform through the connection. It can be understood that the application can not only passively receive the push (push) message of the push service platform, but also actively pull (pull) the message according to the policy, so as to ensure the real-time property of the message. Specifically, the client may determine the frequency, time, and the like of actively pulling the message to be pushed according to the memory occupancy rate, power consumption speed, traffic consumption, application response rate, and the like during the application operation, so as to ensure the timeliness of obtaining the message to be pushed while not affecting the normal operation of the client.
Step S204, after receiving the message to be pushed by the push service platform, returning a receiving confirmation indication corresponding to the message to be pushed to the push service platform. On the basis, the push service platform can calculate the arrival rate of the message to be pushed according to the received confirmation receiving indication. Meanwhile, the corresponding message to be pushed may be processed, for example, the message to be pushed is deleted, or the message to be pushed is retransmitted, etc., in case that the message pushing fails or the confirmation receiving instruction is not received.
Step S205, store the acquired message to be pushed to a local cache.
Step S206, after a preset cache time corresponding to the message to be pushed elapses, pushing the message to be pushed to the one or more applications, where the preset cache time is determined according to a time for the user of the client to use the one or more applications. Therefore, when the application is in a closed state, the message to be pushed of the application can be received, and then according to the user activity, namely the time period when the user uses the application and the like, the time when the cached message to be pushed is sent to the application is determined, so that the probability of clicking and checking the message to be pushed by the user is improved.
Referring to fig. 3, on the basis of the above embodiment, there is provided a message push client 300, including: a message push service determining module 301, a device identifier obtaining module 302, and a message to be pushed obtaining module 303; wherein the content of the first and second substances,
the message push service determining module 301 is configured to determine a message push service applicable to the client from one or more preset message push services;
the device identifier obtaining module 302 is configured to obtain, through the determined message push service, a device identifier of the client for one device, and send the device identifier to a push service platform, so that the push service platform establishes a connection between one or more applications of the client and the push service platform according to the device identifier;
the to-be-pushed message obtaining module 303 is configured to obtain, from the push service platform through the connection, a to-be-pushed message to be pushed to one or more applications of the client.
In an alternative embodiment, the device identifier obtaining module 302 is further configured to,
and sending the equipment identifier to a service end so that the service end sends the message to be pushed to the pushing service platform according to the equipment identifier.
In an optional implementation manner, the obtaining, from the push service platform through the connection, a message to be pushed to the one or more applications of the client includes:
passively receiving the message to be pushed by the push service platform through the connection; or actively pulling the message to be pushed from the push service platform through the connection.
In an optional implementation manner, the to-be-pushed message obtaining module 303 is further configured to,
and after receiving the message to be pushed by the pushing service platform, returning a receiving confirmation indication corresponding to the message to be pushed to the pushing service platform.
In an alternative embodiment, the to-be-pushed message obtaining module 303 is further configured to,
after the message to be pushed is acquired from the pushing service platform through the connection, the acquired message to be pushed is stored in a local cache; and after the preset caching time corresponding to the message to be pushed passes, pushing the message to be pushed to the one or more applications, wherein the preset caching time is determined according to the time for the user of the client to use the one or more applications.
In an alternative embodiment, the device identifier obtaining module 302 is further configured to,
keep-alive processing is carried out on one or more applications of the client side, so that the connection between the applications and the push service platform is in a connection state.
In an optional embodiment, the keep-alive process is to configure a daemon process for the application process;
when the application process is closed, starting the application process through the daemon;
and when the daemon is closed, starting the daemon process through the application process.
In an optional embodiment, the keep-alive process is to increase the priority of the application process, so that the application process is closed after the other process or processes are closed.
In an optional implementation manner, the keep-alive processing is that when the application process is closed, the application process is started through the determined other applications in the running state corresponding to the message push service.
Referring to fig. 4, on the basis of the foregoing embodiment, a message pushing method applied to a push service platform is provided, where the method specifically includes the following steps:
step S401, receiving the device identifier corresponding to the client sent by the client.
Step S402, sending the device identifier to the client, so as to establish connection between one or more applications of the client and the push service platform according to the device identifier.
In an optional implementation manner, the message to be pushed, which is sent by the service end according to the device identifier, is received. That is, when sending the related messages of the operation class, the advertisement class and the activity class to the push service platform, the service end selects one or more clients receiving the messages through the device identifier. It can be understood that the service end is bound with a corresponding push service platform by default so as to send the message, and meanwhile, under the condition that one or more push service platforms exist, the push service platform receiving the message can be selected according to the identification of the service platform to complete the push of the message.
On the basis, the push service platform can store the messages to be pushed sent by the service end into the first-in first-out queue, then push the messages to be pushed in the queue to the specified client, delete the messages in the queue after the messages are successfully sent, and simultaneously, according to different actual requirements, formulate different management mechanisms for messages to be pushed which are not sent when the messages are overtime and for messages to be pushed which are failed to be sent.
In an optional implementation manner, whether the received message to be pushed sent by the service end meets a preset rule is determined; and under the condition of meeting the preset rule, converting the format of the message to be pushed so as to enable the format of the message to be pushed to meet the message storage format of the push service platform or the message receiving format of the client.
The preset rules include, but are not limited to: the message to be pushed is in a format, the timeliness of the message to be pushed, whether the message to be pushed indicates a user identifier for receiving the message, whether the message to be pushed indicates a device identifier for receiving the message, and the like. The format of the message to be pushed is converted into a uniform message storage format or a message receiving format of the client, so that the compatibility of the push service platform to the message format corresponding to the message push service is ensured.
Step S403, sending a message to be pushed to one or more applications to be pushed to the client through the connection. It can be understood that, the push service platform may actively push (push) the message to be pushed to the client through the fifo queue after receiving the message to be pushed sent by the service end, or may immediately push the message to be pushed to the client when a pull request is sent according to the message to be pushed by the client at regular time, and when there is no latest message to be pushed at present, the push service platform continues to monitor the update of the message to be pushed of the push service platform instead of directly rejecting the pull request of the message to be pushed, and once there is a new message to be pushed, returns the latest message to be pushed according to the pull request of the message to be pushed, thereby ensuring the real-time performance of the message to be pushed. In addition, a timeout period may be set for unsuccessful messages, and the messages are cleared immediately after the timeout period to ensure that the queue length is not too long.
In an optional implementation manner, an acknowledgement receiving indication returned by the client according to the message to be pushed is received.
On this basis, the push service platform may store the message to be pushed to a local cache under any one of the following conditions: the message to be pushed fails to be pushed, the receiving confirmation indication is not received within the threshold time after the message to be pushed is pushed, and the message to be pushed which is not sent after overtime exists in the pushing service platform.
Further, according to a preset message processing rule, any one of the following processes is performed on the message to be pushed, which is stored in the local cache: deleting the message to be pushed and pushing the message to be pushed again. The preset message rule is set according to actual requirements, and includes, but is not limited to, deleting a message to be pushed that is not sent overtime, resending a message to be pushed that does not receive an acknowledgement receipt indication, and the like.
Referring to fig. 5, on the basis of the foregoing embodiment, another message pushing method applied to a push service platform is provided, where the method specifically includes the following steps:
step S501, receiving a device identifier corresponding to a client sent by the client.
Step S502, establishing connection between one or more applications of the client and the push service platform according to the device identifier.
In addition, the message to be pushed, which is sent by the service end according to the device identifier, is received. That is, when sending the related messages of the operation class, the advertisement class and the activity class to the push service platform, the service end selects one or more clients receiving the messages through the device identifier. It can be understood that the service end is bound with a corresponding push service platform by default so as to send the message, and meanwhile, under the condition that one or more push service platforms exist, the push service platform receiving the message can be selected according to the identification of the service platform to complete the push of the message.
On the basis, the push service platform can store the messages to be pushed sent by the service end into the first-in first-out queue, then push the messages to be pushed in the queue to the specified client, delete the messages in the queue after the messages are successfully sent, and simultaneously, according to different actual requirements, formulate different management mechanisms for messages to be pushed which are not sent when the messages are overtime and for messages to be pushed which are failed to be sent.
Further, whether the received message to be pushed sent by the service end meets a preset rule is judged; and under the condition of meeting the preset rule, converting the format of the message to be pushed so as to enable the format of the message to be pushed to meet the message storage format of the push service platform or the message receiving format of the client.
The preset rules include, but are not limited to: the message to be pushed is in a format, the timeliness of the message to be pushed, whether the message to be pushed indicates a user identifier for receiving the message, whether the message to be pushed indicates a device identifier for receiving the message, and the like. The format of the message to be pushed is converted into a uniform message storage format or a message receiving format of the client, so that the compatibility of the push service platform to the message format corresponding to the message push service is ensured.
Step S503, sending a message to be pushed to one or more applications of the client through the connection.
Step S504, receiving the confirmation receiving indication returned by the client according to the message to be pushed.
Step S505, according to any one of the following conditions, storing the message to be pushed to a local cache: the message to be pushed fails to be pushed, the receiving confirmation indication is not received within the threshold time after the message to be pushed is pushed, and the message to be pushed which is not sent after overtime exists in the pushing service platform.
Step S506, according to a preset message processing rule, performing any one of the following processes on the message to be pushed stored in the local cache: deleting the message to be pushed and pushing the message to be pushed again.
Referring to fig. 3 and fig. 6, on the basis of the foregoing embodiments, a message pushing system 600 is provided, which includes a message pushing client 300, a pushing service platform 601; wherein the content of the first and second substances,
the message pushing client 300 is used for determining a message pushing service suitable for the client from one or more preset message pushing services; acquiring a device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier; obtaining a message to be pushed to the one or more applications from the push service platform through the connection;
the push service platform 601 is configured to receive a device identifier corresponding to a client sent by the client, and establish a connection between one or more applications of the client and the push service platform according to the device identifier; and sending the messages to be pushed of one or more applications to be pushed to the client through the connection.
Referring to fig. 7, on the basis of the foregoing embodiment, a message pushing method applied to a message pushing system is provided, where the method specifically includes the following steps:
step S701, the client determines a message push service applicable to the client from one or more preset message push services.
Step S702, the client obtains the device identifier corresponding to the client through the determined message push service.
Step S703, the client sends the device identifier to a push service platform.
Step S704, the push service platform receives the device identifier corresponding to the client sent by the client.
Step S705, the push service platform establishes a connection between one or more applications of the client and the push service platform according to the device identifier.
Step S706, receiving the message to be pushed sent by the service end according to the device identifier, and determining whether the received message to be pushed sent by the service end meets a preset rule. The preset rules include, but are not limited to: the message to be pushed is in a format, the timeliness of the message to be pushed, whether the message to be pushed indicates a user identifier for receiving the message, whether the message to be pushed indicates a device identifier for receiving the message, and the like. The format of the message to be pushed is converted into a uniform message storage format or a message receiving format of the client, so that the compatibility of the push service platform to the message format corresponding to the message push service is ensured.
Step S707, the push service platform performs format conversion on the message to be pushed in a case that the push service platform conforms to the preset rule, so that the format of the message to be pushed conforms to the message storage format of the push service platform or the message receiving format of the client.
Step S708, the client obtains the message to be pushed to the one or more applications from the push service platform through the connection. It is understood that the method includes passively receiving the message to be pushed (push) pushed by the push service platform through the connection; or actively pulling (pull) the message to be pushed from the push service platform through the connection.
Step S709, after receiving the message to be pushed by the push service platform, the client returns a receiving confirmation instruction corresponding to the message to be pushed to the push service platform.
Step S710, the push service platform receives a receiving confirmation instruction returned by the client according to the message to be pushed. It is understood that the push service platform may store the message to be pushed to the local cache according to any one of the following situations: the message to be pushed fails to be pushed, the receiving confirmation indication is not received within the threshold time after the message to be pushed is pushed, and the message to be pushed which is not sent after overtime exists in the pushing service platform. On this basis, the push service platform further performs any one of the following processes on the message to be pushed, which is stored in the local cache, according to a preset message processing rule: deleting the message to be pushed and pushing the message to be pushed again.
Step S711, the client stores the acquired message to be pushed to a local cache;
in step S712, the client pushes the message to be pushed to the one or more applications after a preset caching time corresponding to the message to be pushed, where the preset caching time is determined according to a time for the user of the client to use the one or more applications.
Fig. 8 shows an exemplary system architecture 800 to which a message pushing method or a message pushing apparatus according to an embodiment of the present invention may be applied.
As shown in fig. 8, the system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. The network 804 serves to provide a medium for communication links between the terminal devices 801, 802, 803 and the server 805. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 801, 802, 803 to interact with a server 805 over a network 804 to receive or send messages or the like. The terminal devices 801, 802, 803 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, and the like.
The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 805 may be a server that provides various services, such as a background management server that supports shopping websites browsed by users using the terminal devices 801, 802, 803. The background management server can analyze and process the received data such as the product information inquiry request and feed back the processing result to the terminal equipment.
It should be noted that the message pushing method applied to the push service platform provided by the embodiment of the present invention is generally executed by the server 805.
It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 9, shown is a block diagram of a computer system 900 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are executed when the computer program is executed by a Central Processing Unit (CPU) 901.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a message pushing service determining module, a device identifier obtaining module and a message to be pushed obtaining module. The names of these modules do not constitute a limitation to the modules themselves in some cases, for example, the message push service determination module may also be described as "a module for determining a message push service applicable to the client from among preset one or more message push services".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: determining a message pushing service suitable for the client from one or more preset message pushing services; acquiring a device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier; and acquiring the message to be pushed to the one or more applications from the pushing service platform through the connection.
According to the technical scheme of the embodiment of the invention, the message push service suitable for the client is determined through one or more preset message push services, so that the good compatibility between the message push service and the client and the message push service is ensured; by the keep-alive processing of the client application, the application is always in a running state, the connection between the application and the push service platform is ensured to be in a connection state, and the arrival rate of the message to be pushed is further ensured; the received message to be pushed is locally cached at the client, and the time for sending the message to be pushed to the application is determined according to the habit, the time and the like of the user for using the application, so that the click rate and the like of the user for the message to be pushed are improved to a certain extent, the experience of the user for using the application can be improved, and the retention rate of the application can be improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. A message pushing method is applied to a client and comprises the following steps:
determining a message pushing service suitable for the client from one or more preset message pushing services;
acquiring a device identifier corresponding to the client through the determined message push service, and sending the device identifier to a push service platform, so that the push service platform establishes connection between one or more applications of the client and the push service platform according to the device identifier;
and acquiring the message to be pushed to the one or more applications from the pushing service platform through the connection.
2. The message pushing method according to claim 1, further comprising:
and sending the equipment identifier to a service end so that the service end sends the message to be pushed to the pushing service platform according to the equipment identifier.
3. The message pushing method according to claim 1, wherein the obtaining the message to be pushed to the one or more applications from the push service platform through the connection comprises:
passively receiving the message to be pushed by the push service platform through the connection;
or actively pulling the message to be pushed from the push service platform through the connection.
4. The message pushing method according to claim 3, further comprising:
and after receiving the message to be pushed by the pushing service platform, returning a receiving confirmation indication corresponding to the message to be pushed to the pushing service platform.
5. The message pushing method according to claim 1, further comprising:
after the message to be pushed is acquired from the pushing service platform through the connection, the acquired message to be pushed is stored in a local cache;
and after the preset caching time corresponding to the message to be pushed passes, pushing the message to be pushed to the one or more applications, wherein the preset caching time is determined according to the time for the user of the client to use the one or more applications.
6. The message pushing method according to claim 1, further comprising:
keep-alive processing is carried out on one or more applications of the client side, so that the connection between the applications and the push service platform is in a connection state.
7. The message pushing method according to claim 6,
the keep-alive processing is that a daemon process is configured for the application process;
when the application process is closed, starting the application process through the daemon;
and when the daemon is closed, starting the daemon process through the application process.
8. The message pushing method according to claim 6,
the keep-alive processing is to increase the priority of the application process so that the application process is closed after other one or more processes are closed.
9. The message pushing method according to claim 6,
and the keep-alive processing is that when the application process is closed, the application process is started through other applications in the running state corresponding to the determined message push service.
10. A message push client, comprising: the device comprises a message push service determining module, an equipment identifier acquiring module and a message to be pushed acquiring module; wherein the content of the first and second substances,
the message push service determining module is used for determining a message push service suitable for the client from one or more preset message push services;
the device identifier obtaining module is configured to obtain a device identifier of the client for one device through the determined message push service, and send the device identifier to a push service platform, so that the push service platform establishes a connection between one or more applications of the client and the push service platform according to the device identifier;
the message to be pushed obtaining module is used for obtaining the message to be pushed to one or more applications of the client from the pushing service platform through the connection.
11. A message pushing method is applied to a pushing service platform and comprises the following steps:
receiving a device identifier corresponding to a client sent by the client;
establishing a connection between one or more applications of the client and the push service platform according to the device identifier;
and sending the messages to be pushed of one or more applications to be pushed to the client through the connection.
12. An electronic device for pushing messages, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-9.
13. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010074719.5A CN113238808A (en) | 2020-01-22 | 2020-01-22 | Message pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010074719.5A CN113238808A (en) | 2020-01-22 | 2020-01-22 | Message pushing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113238808A true CN113238808A (en) | 2021-08-10 |
Family
ID=77129866
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010074719.5A Pending CN113238808A (en) | 2020-01-22 | 2020-01-22 | Message pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238808A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114286293A (en) * | 2021-12-22 | 2022-04-05 | 广东悦伍纪网络技术有限公司 | Message push management method, device, system, computer equipment and storage medium |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130084896A1 (en) * | 2011-09-29 | 2013-04-04 | International Business Machines Corporation | Pushing Secure Notifications to Mobile Computing Devices |
| KR101398785B1 (en) * | 2013-03-22 | 2014-05-27 | 주식회사 엘지유플러스 | Apparatus , control method and recording medium thereof for push service |
| CN104144098A (en) * | 2013-05-07 | 2014-11-12 | 腾讯科技（深圳）有限公司 | Information pushing method and system and pushing server equipment |
| CN104584489A (en) * | 2012-08-30 | 2015-04-29 | 三星电子株式会社 | Push message service system and method |
| CN106648861A (en) * | 2016-12-05 | 2017-05-10 | 广州优视网络科技有限公司 | Method and device for keeping background service process activated |
| CN106657327A (en) * | 2016-12-20 | 2017-05-10 | 上海银禾油信息技术有限公司 | Message pushing method and message pushing device |
| CN106933660A (en) * | 2017-02-17 | 2017-07-07 | 广州启生信息技术有限公司 | The implementation method of application process keep-alive under a kind of Android platform |
| CN107172205A (en) * | 2017-06-29 | 2017-09-15 | 腾讯科技（深圳）有限公司 | Pushed information processing method, mobile terminal and computer-readable storage medium |
| CN107395767A (en) * | 2017-08-31 | 2017-11-24 | 北京奇虎科技有限公司 | Message push system and method based on long connection |
| CN107592324A (en) * | 2016-07-06 | 2018-01-16 | 广州市动景计算机科技有限公司 | Information push method and device and portable terminal |
| CN108737535A (en) * | 2018-05-14 | 2018-11-02 | 平安科技（深圳）有限公司 | A kind of information push method, storage medium and server |
| CN108768775A (en) * | 2018-05-30 | 2018-11-06 | 努比亚技术有限公司 | Information processing method, electronic equipment and computer storage media |
| CN108833521A (en) * | 2018-06-06 | 2018-11-16 | 广州视源电子科技股份有限公司 | Information push method, device, system, computer equipment and storage medium |
| CN108845875A (en) * | 2018-07-09 | 2018-11-20 | 北京顺丰同城科技有限公司 | A kind of Resident Process keep-alive system and method |
| CN109040326A (en) * | 2018-11-02 | 2018-12-18 | 北京京东金融科技控股有限公司 | The method and apparatus of PUSH message |
| CN109151056A (en) * | 2018-09-26 | 2019-01-04 | 携程计算机技术（上海）有限公司 | Information push method and system based on Canal |
| CN109347934A (en) * | 2018-09-30 | 2019-02-15 | 口碑(上海)信息技术有限公司 | Information push method and system and server, storage medium and electronic device |
-
2020
- 2020-01-22 CN CN202010074719.5A patent/CN113238808A/en active Pending
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130084896A1 (en) * | 2011-09-29 | 2013-04-04 | International Business Machines Corporation | Pushing Secure Notifications to Mobile Computing Devices |
| CN104584489A (en) * | 2012-08-30 | 2015-04-29 | 三星电子株式会社 | Push message service system and method |
| KR101398785B1 (en) * | 2013-03-22 | 2014-05-27 | 주식회사 엘지유플러스 | Apparatus , control method and recording medium thereof for push service |
| CN104144098A (en) * | 2013-05-07 | 2014-11-12 | 腾讯科技（深圳）有限公司 | Information pushing method and system and pushing server equipment |
| CN107592324A (en) * | 2016-07-06 | 2018-01-16 | 广州市动景计算机科技有限公司 | Information push method and device and portable terminal |
| CN106648861A (en) * | 2016-12-05 | 2017-05-10 | 广州优视网络科技有限公司 | Method and device for keeping background service process activated |
| CN106657327A (en) * | 2016-12-20 | 2017-05-10 | 上海银禾油信息技术有限公司 | Message pushing method and message pushing device |
| CN106933660A (en) * | 2017-02-17 | 2017-07-07 | 广州启生信息技术有限公司 | The implementation method of application process keep-alive under a kind of Android platform |
| CN107172205A (en) * | 2017-06-29 | 2017-09-15 | 腾讯科技（深圳）有限公司 | Pushed information processing method, mobile terminal and computer-readable storage medium |
| CN107395767A (en) * | 2017-08-31 | 2017-11-24 | 北京奇虎科技有限公司 | Message push system and method based on long connection |
| CN108737535A (en) * | 2018-05-14 | 2018-11-02 | 平安科技（深圳）有限公司 | A kind of information push method, storage medium and server |
| CN108768775A (en) * | 2018-05-30 | 2018-11-06 | 努比亚技术有限公司 | Information processing method, electronic equipment and computer storage media |
| CN108833521A (en) * | 2018-06-06 | 2018-11-16 | 广州视源电子科技股份有限公司 | Information push method, device, system, computer equipment and storage medium |
| CN108845875A (en) * | 2018-07-09 | 2018-11-20 | 北京顺丰同城科技有限公司 | A kind of Resident Process keep-alive system and method |
| CN109151056A (en) * | 2018-09-26 | 2019-01-04 | 携程计算机技术（上海）有限公司 | Information push method and system based on Canal |
| CN109347934A (en) * | 2018-09-30 | 2019-02-15 | 口碑(上海)信息技术有限公司 | Information push method and system and server, storage medium and electronic device |
| CN109040326A (en) * | 2018-11-02 | 2018-12-18 | 北京京东金融科技控股有限公司 | The method and apparatus of PUSH message |
Non-Patent Citations (2)
| Title |
|---|
| 王莹;: "基于移动互联网的终端消息推送方案研究", 菏泽学院学报, no. 05, 25 October 2017 (2017-10-25) * |
| 王钰;叶?越: "基于商用多媒体云平台的终端推送服务设计", 微型电脑应用, no. 06, 20 June 2017 (2017-06-20) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114286293A (en) * | 2021-12-22 | 2022-04-05 | 广东悦伍纪网络技术有限公司 | Message push management method, device, system, computer equipment and storage medium |
| CN114286293B (en) * | 2021-12-22 | 2023-03-14 | 广东悦伍纪网络技术有限公司 | Message push management method, device, system, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR20220062101A (en) | Information transmission method, apparatus, readable medium and electronic device | |
| WO2012134692A2 (en) | Techniques to manage file conversions | |
| CN111427701A (en) | Workflow engine system and business processing method | |
| WO2021237433A1 (en) | Message pushing method and apparatus, and electronic device and computer-readable medium | |
| CN112311656B (en) | Message aggregation and display method and device, electronic equipment and computer readable medium | |
| CN114979024A (en) | Computing power network transaction method and device, computer readable medium and electronic equipment | |
| CN112379982A (en) | Task processing method and device, electronic equipment and computer readable storage medium | |
| CN112653614A (en) | Request processing method and device based on message middleware | |
| US11463549B2 (en) | Facilitating inter-proxy communication via an existing protocol | |
| CN112084042A (en) | Message processing method and device | |
| CN112527530B (en) | Message processing method, device, apparatus, storage medium and computer program product | |
| CN113238808A (en) | Message pushing method and device | |
| CN113783913A (en) | Message pushing management method and device | |
| CN110321252B (en) | Skill service resource scheduling method and device | |
| CN112948138A (en) | Method and device for processing message | |
| CN113742617A (en) | Cache updating method and device | |
| US9596199B2 (en) | Enabling and supporting a presence server cache | |
| CN110019671B (en) | Method and system for processing real-time message | |
| CN111193656A (en) | Message pushing method and device | |
| CN113132480B (en) | Data transmission method, device and system | |
| CN116112880B (en) | MQ-based high concurrency short message sending method and device | |
| CN116436855B (en) | Data information processing method, device, electronic equipment and medium | |
| CN113766437B (en) | Short message sending method and device | |
| CN114064314A (en) | Service message processing method, system, electronic device and computer readable medium | |
| CN113765813A (en) | Method and device for dynamically adjusting message receiving rate |
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 |