CN108989443B - Method and system for pushing message to mobile terminal by push server - Google Patents
Method and system for pushing message to mobile terminal by push server Download PDFInfo
- Publication number
- CN108989443B CN108989443B CN201810855960.4A CN201810855960A CN108989443B CN 108989443 B CN108989443 B CN 108989443B CN 201810855960 A CN201810855960 A CN 201810855960A CN 108989443 B CN108989443 B CN 108989443B
- Authority
- CN
- China
- Prior art keywords
- mobile terminal
- application program
- message
- sdk
- push server
- 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
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
Abstract
A method for a main push server to push messages to an application program on a mobile terminal. The main push server can obtain terminal information I of the mobile terminal, wherein the terminal information I at least comprises time t when an application program on the mobile terminal or a main SDK integrated with the application program transmits a first signal to the main push server last time, information C1 of a first channel and information C2 of a second channel; the master push server is also able to obtain a set of slave push servers SP. The method comprises the following steps: step S100, if t0-t is not more than D, pushing a message to an application program of the mobile terminal by using a first channel corresponding to first channel information C1, otherwise, executing step S200, wherein D is a preset time threshold value, and t0 is the current time acquired by the main pushing server; step S200, if SP ≠ Null, C2 ≠ Nil, and there is a corresponding relationship between C2 and spi, wherein SP ≠ Null, C2 ≠ NiliE SP, then push the message to the application of the mobile terminal using the second channel corresponding to the second channel information C2. The invention improves the arrival rate of the push message.
Description
Technical Field
The present invention relates to message pushing, and in particular, to a method for a push server to push a message to a mobile terminal.
Background
Currently, applications of mobile terminals (e.g., mobile APP) generally use a message push service. Common push methods include that a server directly pushes a message to a mobile terminal application, and that a third party push service pushes a message to the mobile terminal application. However, when the user presses the HOME key of the mobile phone or performs a screen locking operation, the currently running application program is transferred to the background to run. The mobile terminal may close the network communication function of the application program running in the background in order to reduce system power consumption and save system resources, or even close the application program, which may cause that a mobile terminal user cannot timely receive information about the application program pushed by the server, reduce the arrival rate of pushed messages, be not beneficial to the user using the mobile terminal to timely obtain information, reduce user experience, increase the transmission amount of invalid information on the network, and waste network communication resources.
In addition, CN108063724A discloses an android platform based message pushing method and system, wherein a push server pushes a message to a mobile terminal according to a target vendor channel. Although the method can partially solve the problem of push message arrival rate under the background application condition, other technical problems are brought, and the method mainly comprises the following steps:
1. a technical means for pushing information without a manufacturer channel is not provided, so that the mobile terminal cannot be touched under the condition of high probability of the part of information;
2. due to the non-uniformity of the vendor channels, when the same message is pushed through different vendor channels, the message arrival rate and the arrival speed may have a relatively obvious difference.
Disclosure of Invention
In order to solve the above technical problem, the present invention provides a method for a master push server to push a message to an application on a mobile terminal, which is characterized in that: the method comprises the steps that a main push server can obtain terminal information I of the mobile terminal, wherein the terminal information I at least comprises (t, C1, C2), and t is the time when an application program on the mobile terminal or a main SDK integrated with the application program transmits a first signal to the main push server last time, and the first signal is used for indicating that the application program is in a state capable of receiving push information; c1 is information of a first channel of the push message from the main push server to the application program of the mobile terminal, including a first identifier of the mobile terminal and a first identifier of the application program; c2 is information of a second channel for pushing messages to the application program of the mobile terminal by the master pushing server, and when C2 is not equal to Nil, C2 comprises an identifier of the slave pushing server, a second identifier of the mobile terminal and a second identifier of the application program; the master push server is also able to obtain a set of slave push servers SP ═ { SP | the master push server is able to forward to send messages according to C2 to the slave push servers SP, SP is able to send messages to the application; (or the master push server can call the interface to the slave push server SP to send a message to the application);
the method comprises the following steps:
s100, if t0-t is not more than D, pushing a message to an application program of the mobile terminal by using a first channel corresponding to the first channel information C1, and ending the process; otherwise, executing step S200; wherein D is a preset time threshold, and t0 is the current time acquired by the main push server;
step S200, if SP ≠ Null, C2 ≠ Nil, and there is a corresponding relationship between C2 and spi, wherein SP ≠ Null, C2 ≠ NiliE SP, then push the message to the application of the mobile terminal using the second channel corresponding to the second channel information C2.
According to the technical scheme, the arrival rate of the push message is improved, so that a mobile terminal user can know the message in time, the user experience is improved, and meanwhile, the transmission loss and the waste of network resources caused by pushing the message to the application program incapable of receiving the message or the integrated main SDK are avoided.
Drawings
Fig. 1 is a flow chart of a method of pushing messages of the present invention.
Fig. 2 is a schematic diagram of a framework of the system for pushing messages of the present invention.
DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings. This description presents by way of example, and not by way of limitation, specific embodiments in accordance with the principles of the present invention, the description being in sufficient detail to enable those skilled in the art to practice the invention, and other embodiments may be utilized and the structure of various elements may be changed and/or substituted without departing from the scope and spirit of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense.
According to the present invention, the main push server may be physically implemented as one server, or may be implemented as a server group including a plurality of servers. The mobile terminal can be physically implemented as a smart phone, a PAD, and other devices capable of installing Android platform and IOS platform applications (e.g., APP). Those skilled in the art will appreciate that the model, specification, implementation, etc. of the main push server and the mobile terminal do not affect the scope of the present invention.
According to the invention, the main push server can push messages to one or more applications, and for each application, the main push server can obtain (I) the terminal information list TI of the N mobile terminals in which the application is installed1,I2,...,IN)，IiThe value of i is 1 … N for the terminal information of the ith mobile terminal. Those skilled in the art will appreciate that the foregoing meaning of "installed" includes at least "installed, and not uninstalled" or "installed, but uninstalled". The skilled person can also understand that the "obtaining terminal information list" has various implementations in the prior art, and in the present invention, a preferred implementation is that when an application on a mobile terminal is started, the application and/or a main SDK integrated in the application sends an identifier of the mobile terminal, an identifier of the application, and other relevant terminal information to a main push server, so that the main push server can generate a terminal information list TI of the application, and when a message of the application is pushed, terminal information of one or more mobile terminals can be queried according to the identifier of the application, and then the message is pushed.
When the main push server pushes a message to an application program on the mobile terminal, the terminal information I of the mobile terminal can be obtained, where I at least includes (t, C1, C2), where t is a time when the application program on the mobile terminal or a main SDK integrated with the application program last transmits a first signal to the main push server, and the first signal may be physically implemented as a data packet (e.g., a small data packet with a byte level size) for indicating that the application program is in a state capable of receiving push information. C1 is information of a first channel for a push message from a primary push server to an application of a mobile terminal, including a first identification of the mobile terminal (e.g., IMEI, MAC address, or other identifier uniquely identifying the terminal or user) and a first identification of the application (e.g., APPID). C2 is information of a second channel for pushing messages to the application of the mobile terminal by the master push server, C2 ≠ Nil, C2 includes an identification of the slave push server (e.g. server IP address, MAC address, server name or other identifier uniquely identifying the server), a second identification of the mobile terminal (e.g. an identifier uniquely identifying the terminal or user) and a second identification of the application (e.g. APPID). In one embodiment of the invention, the primary push server generates a first identification of the application, a first identification of the mobile terminal, from the registration of the application, and uses both identifications to determine the specified application on the specified mobile terminal. Similarly, a second identification of the application, a second identification of the mobile terminal is generated from the push server upon registration of the application, and the specified application on the specified mobile terminal is determined using both identifications. In another embodiment of the present invention, the identification of the application program may also be determined by a server approved by the application program or defined by the application program itself, and the identification of the mobile terminal may be determined by the aforementioned server or may be generated according to the communication address of the mobile terminal, the IMEI number. Therefore, the second identity of the mobile terminal in C2 is the same as or different from the first identity of the mobile terminal in C1, and the second identity of the application program in C2 is the same as or different from the first identity of the application program in C1.
According to the invention, the master push server is able to obtain a set of slave push servers SP ═ { SP | the master push server is able to forward messages to the slave push servers SP, SP is able to send messages to the application }. The master push server can call an interface to send a message to the slave push server sp, including generating a message to be pushed according to the message format specification of the slave push server sp, establishing a connection with the slave push server sp, and then sending the message to the slave push server sp. The set of slave push servers SP is not identical to the set of other push servers than the master push server, but is the set of push servers to which the master push server is able to send messages. According to one embodiment of the invention, the slave push server set comprises at least one slave push server (such as a millet push server, Huanji push server and the like) which can receive the message sent by the master push server and forward the message to the application program on the appointed mobile terminal.
Fig. 1 is a flowchart illustrating a method for pushing a message to an application on a mobile terminal by a primary push server according to a first embodiment of the present invention. The method may comprise the steps of:
s100, if t0-t is not more than D, pushing a message to an application program of the mobile terminal by using a first channel corresponding to the first channel information C1, and ending the process; otherwise, executing step S200; wherein D is a preset time threshold, and t0 is the current time acquired by the main push server;
step S200, if SP ≠ Null, C2 ≠ Nil, and there is a corresponding relationship between C2 and spi, wherein SP ≠ Null, C2 ≠ NiliE SP, then push the message to the application of the mobile terminal using the second channel corresponding to the second channel information C2. The correspondence between C2 and spi means that a mapping relationship exists between C2 and spi, for example, C2 indicates that the application integrates a millet SDK and/or runs on a millet mobile phone, and meanwhile, if the millet push server SP is included in the push server set SP, then a mapping relationship exists between C2 and spi, and it is confirmed that an available second channel exists.
In an embodiment of the present invention, the first channel is a channel through which the main push server directly sends a message to the application program on the mobile terminal or a main SDK integrated in the application program, for example, a push channel. In step S100, if it is determined that t0-t is not greater than D, it is determined that the first channel is available, and the application program of the mobile terminal or the integrated SDK thereof is in an active state, and is capable of receiving the push message.
In an embodiment of the present invention, the second channel is a channel in which the master push server forwards a message to the slave push server spi, and sends the message to the slave SDK of the corresponding spi of the K slave SDKs integrated in the application program via the slave push server spi. The slave push server, such as a millet push server, hua shi push server, etc., can push messages to the application program integrated with the millet SDK, hua shi SDK, etc., and the push has a better message arrival rate on the mobile terminal of the corresponding model. And in the process of determining the second channel, the slave SDK and the mobile terminal type identification (such as the model) integrated with the application program from the push server correspond to each other.
In one embodiment of the invention, K slave SDKs are integrated in the application program, wherein K is more than or equal to 0. The application may or may not integrate one or more slave SDKs, such as a millet SDK, hua shi SDK, etc. The situation may also be different for different versions of the same application, integrating the slave SDK, e.g. a new version application integrates the slave SDK, while an old version application does not integrate the slave SDK.
In an embodiment of the present invention, the main push server may receive a report message obtained and sent by the application program or a main SDK integrated with the application program, where the report message includes a first identifier of a mobile terminal, a first identifier of the application program, and a type identifier of the mobile terminal; and the main push server generates first channel information C1 and second channel information C2 according to the report message, and the mobile terminal type identifier and the second channel information C2 have a corresponding relation.
The main SDK acquiring the report message comprises the following steps: when the application program is started for the first time or at fixed time T1, the master SDK obtains a first identifier of a mobile terminal where the application program is located, the first identifier of the application program, a mobile terminal type identifier (such as a model) and a set SSDK of K slave SDKs { SDK | SDK is a slave SDK integrated with the application program and can receive a corresponding message sent from a push server }, wherein K is greater than or equal to 0; if the mobile terminal type identification is SDK from the SDK set SSDKjThere is a correspondence relationship, wherein sdkjIf the e belongs to SSDK, the mobile terminal type identifier is used as the mobile terminal type identifier of the report message, and sdk is addedjAnd if not, taking the Nil as the mobile terminal type identifier of the reported message. Wherein, the main SDK judges the type identification of the mobile terminal and SDKjThe existence of the correspondence is that the two have a mapping relation, for example, the type identifier of the mobile terminal is 'millet XXX', sdkjAnd confirming that the SDK is the millet SDK and the SDK has a mapping relation.
The main push server generates second channel information C2 according to the report message, including:
if the type identifier of the mobile terminal reporting the message is Nil, then C2 is Nil;
if the type identification of the mobile terminal reporting the message is not Nil, then sdk in the message is reported according to the corresponding relation between the type identification and C2jInformation, generating C2. Wherein, the main pushing server analyzes the reported message sdkjThe information from which the second identity of the application and the second identity of the mobile terminal are obtained and stored in C2. Meanwhile, the type id of the mobile terminal in the report message is also stored in C2. Thereafter, the main push server may determine which SDK the application is integrated with and runs on which mobile terminal based on the data stored in C2. In another embodiment, the main push server may identify and/or sdk according to the type of the mobile terminal reporting the messagejInformation, a second channel type identifier (for example, a millet channel, a hua channel) is determined and stored in C2, and when it is determined in step S200 whether a correspondence relationship exists between C2 and spi, the second channel type identifier may be directly used to compare with spi. In addition, the identifier of the slave push server is also included in C2, which may be collected and reported by the master SDK integrated by the application program to the master push server, or may be preset on the master push server with the identifier of the corresponding slave push server.
In another embodiment of the present invention, when the application program is started for the first time or at regular intervals of T1, the master SDK obtains a first identifier of a mobile terminal where the application program is located, the first identifier of the application program, a mobile terminal type identifier, and a set SSDK of K slave SDKs { SDK | SDK is a slave SDK integrated with the application program and is capable of receiving a message sent by a slave push server }, where K is greater than or equal to 0, directly packages all data to form a report message, and sends the report message to the master push server; the main push server judges according to the data in the report message, if the mobile terminal type identification is sdkjThere is a correspondence relationship, wherein sdkjE.g. SSDK, then according to the corresponding relation between the mobile terminal type identification and C2 and sdkjInformation, generating C2. Wherein, judging the type identification of the mobile terminal and sdkjThe corresponding relation exists and the mode of generating C2 is similar to the previous embodimentThe implementation is the same, except that in this embodiment, these processes are all done by the master push server.
According to the invention, when the application program runs in the mobile terminal, a first signal is transmitted to the main push server at fixed time T2. Further, when the application program is started, the first signal is also transmitted to the main pushing server.
In one embodiment of the invention, D is 1 to 10 minutes, preferably 3 minutes. Further, D ═ T2, that is, the value of T2 is also 1 to 10 minutes, preferably 3 minutes, so as to ensure the accuracy of determining whether the application or the integrated master SDK is suitable for receiving the information to be pushed.
In an embodiment of the present invention, the terminal information I of the mobile terminal further includes third channel information C3, where C3 is information of a third channel through which the main push server pushes a message to an application program of the mobile terminal, and includes a third terminal identifier of the mobile terminal (e.g., a communication number of the mobile terminal, a user mailbox, a micro signal); when it is determined in step S200 that the second channel does not exist, step S300 is further performed; step S300: and the main push server pushes the message to the mobile terminal through a third channel corresponding to the third channel information C3.
The third channel push is that the main push server pushes a message to the mobile terminal in a manner of short message, email, WeChat, or the like, or the information to be pushed may be transmitted to another information sending server (for example, a third-party server), and the information sending server sends the information to be pushed to the mobile terminal in a manner of short message (at this time, the information sending server is implemented as a short message sending server, for example), email (at this time, the information sending server is implemented as an email sending server, for example), WeChat (at this time, the information sending server is implemented as a WeChat sending server, for example), and the like.
When the main push server supports the push of messages to the mobile terminal in the modes of short messages, e-mails, micro-messages and the like, the main push server needs to know the communication number, the terminal identification such as a user mailbox, a micro-signal and the like and the user identification of the mobile terminal, the information can be obtained through an application program or an integrated main SDK on the mobile terminal and is provided for the main push server, and third channel information C3 is generated and stored in the terminal information I of the mobile terminal.
Further, the information content sent by the main push server to the mobile terminal through the third channel includes the push content information requested to be sent and also includes link information. In an embodiment of the present invention, the information content sent by the main push server to the mobile terminal through the third channel may include content information of the original push request, and may further include additional link information. When the terminal user views the message and triggers the link information, if the application program is installed on the mobile terminal, the application program is started, and if the application program is not installed on the mobile terminal, a webpage (Web page) related to the application program is displayed on the mobile terminal, for example, a page for downloading the application program, or a Web main page of an owner of the application program, and the like.
In the preferred embodiment of the invention, through the use of the link information, the user of the mobile terminal can quickly and effectively help the user to start the application program or download the application program again on the basis of acquiring the information in time, thereby being beneficial to improving the operation activity of the application program.
Referring to fig. 2, an embodiment of the present invention illustrates a message push system based on a mobile terminal. The message pushing system comprises: the system comprises a master push server (100), a slave push server (200) and a mobile terminal (300). The master push server (100) and the slave push server (200) are both connected to the mobile terminal (300) via a network and are capable of pushing messages to the mobile terminal. The master push server (100) is connected to the slave push server (200) via a network. The system may comprise a plurality of mobile terminals, a plurality of slave push servers, only one mobile terminal and one slave push server being illustrated in fig. 2 as an example.
The processing and functions performed by each server and mobile terminal included in the message push system have been described in the foregoing description, and are not described again here.
Moreover, other implementations of the invention will be apparent to those skilled in the art from consideration of the specification of the invention disclosed herein. The embodiments and/or aspects of the embodiments can be used in the systems and methods of the present invention alone or in any combination. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Claims (10)
1. A method for pushing a message to an application program on a mobile terminal by a main pushing server is characterized in that the main pushing server can acquire terminal information I of the mobile terminal, wherein the I at least comprises (t, C1, C2), and t is the time when the application program on the mobile terminal or a main SDK integrated with the application program last transmits a first signal to the main pushing server, and the first signal is used for indicating that the application program is in a state capable of receiving the pushing message; c1 is information of a first channel of the push message from the main push server to the application program of the mobile terminal, including a first identifier of the mobile terminal and a first identifier of the application program; c2 is information of a second channel for pushing messages to the application program of the mobile terminal by the master pushing server, and when C2 is not equal to Nil, C2 comprises an identifier of the slave pushing server, a second identifier of the mobile terminal and a second identifier of the application program; the master push server is also able to obtain a set of slave push servers SP ═ { SP | the master push server is able to forward messages to the slave push servers SP according to C2, SP is able to send messages to the application };
the method comprises the following steps:
s100, if t0-t is not more than D, pushing a message to an application program of the mobile terminal by using a first channel corresponding to the first channel information C1, and ending the process; otherwise, executing step S200; wherein D is a preset time threshold, and t0 is the current time acquired by the main push server;
step S200, if SP ≠ Null, C2 ≠ Nil, and C2 and SPiThere is a correspondence relationship wherein spiE SP, then push the message to the application of the mobile terminal using the second channel corresponding to the second channel information C2.
2. The method of pushing messages according to claim 1, wherein the application program is integrated with K slave SDKs, wherein K ≧ 0; the first channel is a channel through which the main push server directly sends a message to the application program or a main SDK integrated in the application program.
3. Method for pushing messages according to claim 2, characterised in that the second channel is that the master push server forwards messages to the slave push server spiAnd via a slave push server spiTo corresponding sp in K slave SDKs integrated in the applicationiA channel for sending messages from the SDK; in addition, the second identity of the mobile terminal in C2 is the same as or different from the first identity of the mobile terminal in C1, and the second identity of the application program in C2 is the same as or different from the first identity of the application program in C1.
4. The method according to claim 2, wherein the main push server is capable of receiving a report message obtained and sent by the application program or a main SDK integrated with the application program, and the report message includes a first identifier and a second identifier of the mobile terminal, a first identifier and a second identifier of the application program, and a type identifier of the mobile terminal; and the main push server generates first and second channel information C1 and C2 according to the report message, and the mobile terminal type identifier and the push server identifier in the second channel information C2 have a corresponding relation.
5. The method of pushing a message according to claim 4, wherein the acquiring, by the primary SDK, the report packet includes: when the application program is started for the first time or at fixed time intervals T1, the master SDK obtains a first identifier of a mobile terminal where the application program is located, the first identifier of the application program, a mobile terminal type identifier and a set SSDK of K slave SDKs { SDK | SDK is a slave SDK integrated with the application program and can receive a corresponding message sent by a slave push server }, wherein K is more than or equal to 0; if the mobile terminal type identification is SDK from the SDK set SSDKjThere is a correspondence relationship, wherein sdkj∈SSDK，Then the mobile terminal type identifier is used as the mobile terminal type identifier of the report message, and sdk is addedjAnd if not, taking the Nil as the mobile terminal type identifier of the reported message.
6. The method of pushing a message according to claim 5, wherein the generating, by the master push server, the second channel information C2 according to the report packet includes:
if the type identifier of the mobile terminal reporting the message is Nil, then C2 is Nil;
if the type identification of the mobile terminal reporting the message is not Nil, then sdk in the reported message is reported according to the corresponding relation between the type identification and the push server identification in C2jInformation, generating C2.
7. The method for pushing messages according to claim 4, wherein when the application program is started for the first time or at regular intervals of time T1, the master SDK obtains a set SSDK of a first identifier and a second identifier of a mobile terminal where the application program is located, the first identifier and the second identifier of the application program, a mobile terminal type identifier, and K slave SDKs { SDK | SDK is a slave SDK integrated with the application program and capable of receiving messages sent from a push server }, where K is greater than or equal to 0, forms a report message, and sends the report message to the master push server;
the main push server judges according to the data in the report message, if the mobile terminal type identification is sdkjThere is a correspondence relationship, wherein sdkjE.g. SSDK, then according to the corresponding relation between the mobile terminal type identification and C2 and sdkjInformation, generating C2.
8. A method for pushing messages according to any of claims 1 to 7, characterised in that the first signal is transmitted to the primary push server at regular intervals T2 when the application is running on the mobile terminal.
9. The method for pushing messages according to any one of claims 1 to 7, wherein the terminal information I of the mobile terminal further includes third channel information C3, C3 is information of a third channel of the message pushed by the main push server to the application program of the mobile terminal, including a third terminal identifier of the mobile terminal; when it is determined in step S200 that the second channel does not exist, step S300 is further performed;
step S300: and the main push server pushes the message to the mobile terminal through a third channel corresponding to the third channel information C3.
10. The method of pushing messages according to claim 9, wherein the information content sent by the main push server to the mobile terminal through the third channel includes the push content information requested to be sent and also includes link information; and when the mobile terminal user triggers the link information, starting an application program or displaying relevant information of the application program on the mobile terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810855960.4A CN108989443B (en) | 2018-07-31 | 2018-07-31 | Method and system for pushing message to mobile terminal by push server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810855960.4A CN108989443B (en) | 2018-07-31 | 2018-07-31 | Method and system for pushing message to mobile terminal by push server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108989443A CN108989443A (en) | 2018-12-11 |
| CN108989443B true CN108989443B (en) | 2021-02-19 |
Family
ID=64552466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810855960.4A Active CN108989443B (en) | 2018-07-31 | 2018-07-31 | Method and system for pushing message to mobile terminal by push server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108989443B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112187927A (en) * | 2020-09-29 | 2021-01-05 | 云账户技术(天津)有限公司 | Method and device for pushing channel selection |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107370810A (en) * | 2017-07-13 | 2017-11-21 | 北京奇艺世纪科技有限公司 | Push channel system of selection, server and terminal device |
| CN107888641A (en) * | 2016-09-30 | 2018-04-06 | 阿里巴巴集团控股有限公司 | A kind of information push method and device |
| CN108241500A (en) * | 2018-01-15 | 2018-07-03 | 腾讯科技（深圳）有限公司 | A kind of restorative procedure of hardware component, device, system and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9411870B2 (en) * | 2013-05-08 | 2016-08-09 | iData Crunch | System and method for location aware fine-grained multi-channel synchronization of mobile repositories along with aggregate analytic computation |
| US20160171540A1 (en) * | 2014-12-12 | 2016-06-16 | Suryanarayana MANGIPUDI | Dynamic Omnichannel Relevant Content And Services Targeting In Real Time |
-
2018
- 2018-07-31 CN CN201810855960.4A patent/CN108989443B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107888641A (en) * | 2016-09-30 | 2018-04-06 | 阿里巴巴集团控股有限公司 | A kind of information push method and device |
| CN107370810A (en) * | 2017-07-13 | 2017-11-21 | 北京奇艺世纪科技有限公司 | Push channel system of selection, server and terminal device |
| CN108241500A (en) * | 2018-01-15 | 2018-07-03 | 腾讯科技（深圳）有限公司 | A kind of restorative procedure of hardware component, device, system and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| "多操作系统推送平台的设计与实现";刘虹;《中国优秀硕士学位论文全文数据库 信息科技辑》;20150715;I138-88 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108989443A (en) | 2018-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5850126B2 (en) | Device management server, device management client, and method of locating a target operation object | |
| KR101133596B1 (en) | Apparatus and methods for providing configurable task management on a wireless device | |
| KR20160060118A (en) | Method and apparatus for implementing subscription notification | |
| WO2015021905A1 (en) | Software updating method, system, and device | |
| CN111263338A (en) | Network distribution method of Bluetooth Mesh network and related network distribution equipment and system | |
| WO2016127612A1 (en) | Monitoring processing method and device | |
| CN108471361B (en) | Version upgrading method and device | |
| WO2018000653A1 (en) | Information processing method for m2m application, cse and ae | |
| CN113196721B (en) | Method and device for discovering Internet of things equipment and terminal equipment | |
| CN108989443B (en) | Method and system for pushing message to mobile terminal by push server | |
| CN104955153B (en) | Method, device and equipment for discovering resources | |
| US8327391B2 (en) | Method, system and apparatus for transmitting remote procedure call commands | |
| CN107766212B (en) | Method and device for determining installation state of application program | |
| WO2015085573A1 (en) | Method and device for communication using white spectrum | |
| CN113115434A (en) | Network registration method, network equipment and terminal equipment | |
| CN104158728A (en) | Group adding method for social network site, group adding system and server | |
| CN111726417B (en) | Delay control method, device, server and storage medium | |
| CN109862135B (en) | Group communication method based on domain name block chain, block chain link point and medium | |
| CN108495299B (en) | Method and device for receiving service information and multimode terminal | |
| CN113254805A (en) | Method and network equipment for inquiring group position | |
| CN112995095A (en) | Data processing method, device and computer readable storage medium | |
| CN114697375B (en) | Voice packet switching method and device, storage medium and electronic device | |
| CN110855785B (en) | Data processing method and device | |
| CN111200508B (en) | Message sending method and gateway | |
| WO2022104806A1 (en) | Method and apparatus for controlling heterogeneous network devices, device, and 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 | ||
| CB02 | Change of applicant information |
Address after: 310012 Room 418, West District, Building A, 525 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province Applicant after: Daily interactive Co., Ltd Address before: 310012 Room 418, West District, Building A, 525 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province Applicant before: ZHEJIANG MEIRI INTERDYNAMIC NETWORK TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |