CN111901440B - Multi-channel message pushing method and device - Google Patents
Multi-channel message pushing method and device Download PDFInfo
- Publication number
- CN111901440B CN111901440B CN202010799111.9A CN202010799111A CN111901440B CN 111901440 B CN111901440 B CN 111901440B CN 202010799111 A CN202010799111 A CN 202010799111A CN 111901440 B CN111901440 B CN 111901440B
- Authority
- CN
- China
- Prior art keywords
- channel
- push
- udtk
- mobile application
- equipment
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a multichannel message pushing method and a multichannel message pushing device, which comprise a server running on a server and a mobile application running on user equipment. The invention has the beneficial effects that: the method has the advantages that the mobile application system is endowed with the capacity of switching the push channel on line in real time by providing a multi-backup channel for the mobile application system, so that the reliability of the mobile application system in using the message push service is improved; meanwhile, the influence on the existing service logic of the mobile application system is reduced, which is specifically embodied in that: the original token and content adding mode in the process of connecting a third-party channel is kept, the characteristics that other systems cannot or do not need to know the information of specific users in the mobile application system are kept, and the capacity of message pushing operation on the specific users is kept.
Description
Technical Field
The invention relates to a message pushing method and a message pushing device, in particular to a multichannel message pushing method and a multichannel message pushing device, and belongs to the technical field of mobile communication.
Background
In order to send a message notification to a user in time, the mobile application system can be connected with a third-party push channel to realize a message push service. In order to realize the message pushing operation on a specific user and avoid knowing the specific user information stored in the mobile application system, a third party pushing channel provides a registration method in an SDK (software development kit) provided for the mobile application, and the SDK obtains a device token (also called registration ID and the like) after communicating with a third party pushing channel server in an initialization method, and the device token is reported to the mobile application system by the mobile application; when the mobile application system executes message pushing operation on a specific user, the equipment token and the message content are assembled into an instruction and are delivered to a third-party pushing channel for execution, and then pushing can be completed.
The reliability of the message push service depends on three links: 1) A self-built mobile application system (a server software system for supporting mobile application); 2) Network access services provided by a third party (services for helping a mobile application system to access the internet, such as network access services provided by China telecom, china Unicom, and the like); 3) Third party push channels (third party channels that provide basic push services, such as aurora, push, etc.).
For the mobile application system, the operation stability of the latter two non-self-built links cannot be determined. On one hand, when the traditional method is used for docking a third-party channel, after a mobile-end application program is distributed to a user for installation, a mobile application system cannot timely adjust the change of a network access condition and the change of the running condition of a third-party push channel, wherein the possible changes include but are not limited to interruption and blockage of network access service, failure of the third-party push channel, service shutdown and the like; on the other hand, the conventional method is lack of effective coping means when the push service is confronted with the change of the external environment.
Disclosure of Invention
The present invention is directed to a method and an apparatus for pushing a multi-channel message to solve the above problem.
The invention realizes the purpose through the following technical scheme: a multi-channel message pushing device comprises a server running on a server and a mobile application running on user equipment,
the server side comprises:
unified equipment identity assignment module: distributing a uniform and unique device identifier UDTK in the pushing device for the user equipment;
the device channel recording module: recording channel equipment identifications (CNTK) used by equipment in each channel;
a channel state detection module: detecting the communication state of the server and the push channel;
push management a module: recording push channels allowing connection, and calling the most appropriate push channel to execute push according to a preset push rule;
the mobile application includes:
unified equipment identification management module: storing and maintaining an effective device identifier UDTK;
a channel device identifier management module: maintaining an effective channel equipment identifier (CNTK) for each push channel;
a registration module: the device type, UDTK and channel token are registered with the server.
A pushing method of a multi-channel message pushing device comprises the following steps:
step one, initialization
(1) And (3) pretreatment: the mobile application correctly integrates the SDK of each push channel, and configures the push channel to be connected in the push management module;
(2) Initializing UDTK: calling the unified equipment identifier management module when the application of the mobile application is started every time;
(3) Initializing CNTK: the application of the mobile application calls the channel equipment identification management module;
(4) And equipment registration: calling the registration module by the application of the mobile application;
step two, associating users
When a user executes login operation, the mobile application reports the UDTK of the equipment to the mobile application system, and the mobile application system associates and binds the UDTK and the ID of the user;
step three, general use
(1) Communication state detection
The channel state detection module of the server periodically polls and checks the communication state of the server and each push channel and records the communication state;
(2) Message push
When an application system of the mobile application needs to send a message to a user, the following steps are completed: 1) Transmitting the message content and the UDTK corresponding to the user to a push management module of the server side; 2) The push management module checks various factors and selects a proper push channel according to a preset scheduling rule; 3) The push channel selected by the push management module pushes the message; 4) The push channel pushes the message to the mobile application completion;
step four, special use
(1) The manual appointed push channel is used, and when the push channel needs to be appointed, manual intervention is used for appointing: 1) The method comprises the steps of starting or closing a push channel allowed to be used in a push management module; 2) The use is carried out according to the mode in common use;
(2) Case of user replacing device: 1) When the user logs out from the equipment, the logging-out action provided by the mobile application system is executed, and the associated binding of the user ID and the UDTK is released; 2) The user uses the new device, and when the user directly logs in without logging out of the old device, the mobile application system uses the UDTK of the new device to replace the existing UDTK record.
Preferably, the initializing UDTK in the first step comprises the following steps:
1) Reading locally stored UDTK;
2) Returning a local UDTK to a unified equipment identifier distribution module of the server side, and if no UDTK exists, returning a null value;
3) And the unified equipment identifier management module judges whether the reported UDTK is valid or not, and generates and returns a valid UDTK if the reported UDTK is invalid.
Preferably, the initializing CNTK in the step one includes the following steps:
1) Calling the SDK of each push channel to obtain the latest CNTK of each push channel;
2) And persistently storing the obtained CNTK.
Preferably, the device registration in the first step includes the following steps:
1) Reading equipment information including an operating system type, an operating system version, a hardware brand and a hardware model;
2) And returning the equipment information, the UDTK and the CNTKs of all channels to an equipment channel recording module of the server side.
Preferably, the various factors in the message pushing of step three include:
1) A push channel that allows a connection to push the management module;
2) The server side pushes the communication state of the channel from the channel state detection module;
3) User equipment information from an equipment channel recording module;
4) Push channels from the device channel recording module are available to devices that successfully complete registration.
The beneficial effects of the invention are: the method has the advantages that the mobile application system is endowed with the capacity of switching the push channel on line in real time by providing a multi-backup channel for the mobile application system, so that the reliability of the mobile application system in using the message push service is improved; meanwhile, the influence on the existing service logic of the mobile application system is reduced, which is specifically embodied in that: the original token and content adding mode in the process of connecting a third-party channel is kept, the characteristics that other systems cannot/do not need to know the information of specific users in the mobile application system are kept, and the capacity of message pushing operation on the specific users is kept.
Drawings
FIG. 1 is a schematic diagram of the overall structure of multi-channel message pushing according to the present invention;
FIG. 2 is a schematic diagram of a mobile application of the present invention;
FIG. 3 is a schematic diagram of a mobile application system according to the present invention;
FIG. 4 is a schematic structural diagram of a multi-channel message push server according to the present invention;
FIG. 5 is a flowchart illustrating initialization of a mobile application according to the present invention;
FIG. 6 is a flowchart illustrating a mobile application user login process according to the present invention;
FIG. 7 is a flowchart illustrating a general push application process of the present invention;
FIG. 8 is a schematic diagram illustrating a push application process when a push channel or network fails according to the present invention;
FIG. 9 is a schematic diagram illustrating a push application flow when a push channel is manually designated according to the present invention;
FIG. 10 is a flow chart illustrating a user logout procedure according to the present invention;
FIG. 11 is a block diagram of a user of the present invention and (4) a flow schematic diagram of the renewing device.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
As shown in fig. 1, a multi-channel message pushing apparatus includes a server running on a server and a mobile application running on a user device.
The server is a multi-channel push server (aggregation message server), and specifically includes:
unified equipment identity assignment module: distributing a uniform and unique Device identifier UDTK (Universal Device Token) in the pushing Device for the user equipment;
the device channel recording module: recording a Channel Device identification (CNTK) used by the Device in each Channel;
a channel state detection module: detecting the communication state of the server and the push channel;
the pushing management module: recording the push channels allowing connection, and calling the most appropriate push channel to execute push according to a preset push rule.
The server is independent of the original mobile application system, and is used for realizing a message pushing process, and the method specifically comprises the following steps:
1) Connecting a plurality of third party push channels at a server end;
2) Checking the communication state and the working state of each third-party push channel at a server side regularly;
3) Establishing a black and white list for a push channel at a server side;
4) Managing unique unified equipment identification of each terminal equipment in the system at a server;
5) Managing channel equipment identifiers of each mobile terminal in a third-party channel at a server;
6) And when receiving and executing a push instruction sent by the mobile application system, pushing by referring to the latest channel state check result and a rule set by a black and white list.
The mobile application includes:
unified equipment identification management module: storing and maintaining an effective device identifier UDTK;
a channel device identifier management module: maintaining an effective channel equipment identifier (CNTK) for each push channel;
a registration module: the device type, UDTK and channel token are registered with the server.
The mobile application is based on a mobile application system. The method is characterized in that the method is modified on the basis of the original mobile application: 1) Integrating a plurality of third party pushing channels (SDKs) at a mobile terminal; 2) Acquiring and marking user equipment by using a UDTK identifier from a server; 3) When the mobile terminal is initialized, executing an initialization method of a third-party push channel (SDK), acquiring a token of the third-party push channel as a CNTK, returning UDTK and the CNTK to a multi-channel message push service terminal, and establishing an association relation; 4) When a user logs in, the UDTK is reported back to the mobile application system. The method is characterized in that the method is modified on the basis of the original mobile application system: 1) Receiving the UDTK returned by the mobile terminal at a login interface, and establishing association with a user account; 2) And when pushing is needed, sending the message content and the UDTK of the target user to a multi-channel message pushing server.
Examples
Entities applied in this embodiment include:
1. mobile application: an Application program, generally called APP (Application), running on a user's mobile terminal device (handset);
2. the mobile application system is used for supporting a service end system program operated by the mobile application;
3. the multi-channel message pushing server is used for realizing a server-side system program for pushing multi-channel messages;
4. a push channel 1, a first third party push channel;
5. a push channel 2, a second third party push channel;
6. the mobile terminal equipment which is provided with the mobile application can be a plurality of mobile terminal equipment;
7. the corresponding communication Network can be in a Local Area Network (LAN), the Internet, a Cellular Network of a mobile Network and the like.
Note: in practical use, a plurality of push channels can be used, and for simplicity of description, the number of push channels is simplified to 2 in the present embodiment.
As shown in fig. 2, a schematic structural diagram of a mobile application of the embodiment specifically includes:
1. a unified device identifier management module configured to: 1) Persistently storing the UDTK obtained from a multichannel message pushing server; 2) Transmitting the UDTK to a server side, verifying the validity of the UDTK and updating the valid UDTK timely; 3) Providing UDTK information to other modules.
2. A channel device identifier management module to: 1) Acquiring a channel device identifier CNTK used by a device in each push channel; 2) Storing each channel CNTK persistently; 3) CNTK information is provided to other modules.
3. A device registration module to: 1) Acquiring equipment information such as the type, version, hardware brand, model and the like of an operating system, which is referred to when a server selects a push channel; 2) And reporting the UDTK, the CNTKs of all channels and the equipment information to the server to finish registration.
4. And the integrated SDK of the push channel 1 is used for receiving the push message sent by the server through the push channel 1.
5. And the integrated SDK of the push channel 2 is used for receiving the push message sent by the server through the push channel 2.
6. And the user login module is used for communicating with the server user login interface to complete login operation.
7. And the user logout module is used for communicating with the service end user logout interface to finish logout operation.
As shown in fig. 3, a schematic structural diagram of the mobile application system of the embodiment specifically includes:
1. the user login interface is used for judging the user identity and establishing the incidence relation between a legal user and the incoming UDTK;
2. the user logout interface is used for cancelling the login state of the user and cancelling the association relationship between the user and the UDTK;
3. the user account module is used for recording user account information;
4. and the push message sending module is used for finishing the actual operation of sending the push message to the user.
As shown in fig. 4, which is a schematic structural diagram of a multi-channel message push server, the multi-channel message push server includes:
1. a unified device identifier assignment module configured to: 1) Recording the allocated UDTK; 2) The UDTK is distributed for the equipment, and the UDTK is ensured to be unique in the system; 3) And judging the validity of the UDTK transmitted by the mobile terminal.
2. And the device channel recording module is used for recording the channel device identifier CNTK used by the registered device in each push channel.
3. And the channel state detection module is used for regularly checking the communication states of the server and each push channel.
4. A push management module to: 1) Managing access to each push channel, and keeping AppKey, appSecret and the like used for communication with the push channels; 2) Managing a black and white list of a push channel and determining the enabling and disabling of the channel; 3) And executing specific pushing operation according to the instruction and the communication condition of the pushing channel.
As shown in fig. 5, which is a schematic flow chart of initialization of the mobile application of the present invention, the initialization of the mobile application of the present invention specifically includes
1. Initializing UDTK
When the mobile application is started each time, the unified equipment identification management module is called to complete the following steps: reading locally stored UDTK; secondly, the mobile terminal 'unified equipment identifier management module' reports local UDTK to the server 'unified equipment identifier distribution module', and if no UDTK exists, a null value is reported; thirdly, the server side 'uniform equipment identifier distribution module' judges whether the reported UDTK is valid or not, and if the reported UDTK is invalid, the valid UDTK is generated and returned; and fourthly, the unified equipment identification management module persistently stores and returns the UDTK.
2. Initial CNTK
The mobile application calls a channel equipment identifier management module to complete the following steps: firstly, calling a registration method of the SDK of each push channel to obtain the latest CNTK of each push channel; and secondly, storing the obtained CNTK persistently.
3. Device registration
The mobile application calls a 'registration module' to complete the following steps: reading equipment information including an operating system type, an operating system version, a hardware brand, a hardware model and the like; and secondly, reporting the equipment information, the UDTK and the CNTKs of all channels to an equipment channel recording module at the service end.
As shown in fig. 6, which is a schematic flow diagram of mobile application user login according to the present invention, when a login operation of a mobile application system is performed, the UDTK and the id of the user are associated and bound, and subsequently, in use, the mobile application system can push a message to a target user only according to the UDTK.
1. Querying for UDTK: the mobile application login module queries the UDTK used by the equipment to the unified equipment identification management module;
2. executing login; after obtaining the UDTK, the mobile application sends account information (account and password) and the UDTK to a mobile application system;
3. binding UDTK: and after the mobile application system is verified and judged, the user identity is bound with the UDTK.
As shown in fig. 7, a diagram of a general push usage flow is shown:
1. communication status detection
The server side 'channel state detection module' is used for polling and checking the communication state of the server side and each push channel at regular time and recording;
2. message push
When the mobile application system needs to send a message to a user, the following steps are completed:
1. the message content and the UDTK corresponding to the user are transmitted to a push management module of a server side;
the 'push management module' checks the following factors and selects a proper push channel according to a preset scheduling rule: 1) A push channel to grant connections (this module manages), where channel 1,2 is available; 2) The communication state between the server and the push channel (from the channel state detection module), wherein the channel 1,2 is available; 3) User equipment information (from a 'device channel recording module') determines a device type (Android or iOS); 4) Push channel (from "device channel record module") available to the device (successfully completed registration), where channels 1,2 are available;
3, the push management module pushes the message according to the push channel selected in the step 2;
4. and the push channel finishes message push to the mobile terminal.
FIG. 8 is a schematic diagram illustrating a push application process when a push channel or network fails
Suppose that the situation is that the communication between the push server and the push channel 1 fails, and at this time:
a communication state detection module detects and records a communication fault of a channel 1;
2. inquiring that the channel permitted to be used is push 1,2;
3. inquiring that the available push channel is 1;
4. other steps are omitted;
5. at this time, the "push management module" selects the push channel 2 to push the message.
As shown in fig. 9, a schematic diagram of a push using process when a push channel is manually designated.
The situation is assumed to be that, because of the service requirement, the push channel 2 is no longer used for pushing, and at this time:
1. the 'channel black and white list' in the 'pushing management module' specifies that the enabled pushing channel is 1;
2. inquiring that a permitted channel is 1;
a "communication status detection module": channels 1,2 are available;
4. other steps are omitted;
5. at this time, the "push management module" selects the push channel 1 to push the message.
Fig. 10 is a schematic diagram illustrating a log-off process for a user.
1. The user logout module in the mobile application submits logout command to the user logout interface of the mobile application system and attaches user identity information
2. The mobile application system 'user logout interface' sends an instruction to 'user account module' to unbind user information from UDTK
Therefore, the situation that after the user performs the logout operation, the push is still performed to the bound old UDTK device before logout can be avoided.
Fig. 11 is a schematic flow chart illustrating the process of replacing the new device for the user.
1. A user login module in the mobile application queries the UDTK from a unified device identifier management module;
submitting a registration instruction to a user login interface of a mobile application system by a mobile application module, and attaching user identity information and UDTK
3. And after receiving the instruction, a user login interface of the mobile application system judges the validity of the user identity, and if the user identity is legal, the user login interface informs a user account module to update the UDTK bound with the user identity.
Therefore, the user identity can be bound with the UDTK of the new device, the binding relation with the UDKT of the old device is eliminated, and the message is timely and accurately pushed.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.
Claims (5)
1. A pushing method of a multi-channel message pushing device is characterized in that:
the multi-channel message pushing device comprises a server running on a server and a mobile application running on user equipment,
the server side comprises:
unified equipment identity assignment module: distributing a uniform and unique device identifier UDTK in the pushing device for the user equipment;
the device channel recording module: recording channel equipment identification (CNTK) used by equipment in each channel;
a channel state detection module: detecting the communication state of the server and the push channel;
the pushing management module: recording push channels allowing connection, and calling the most appropriate push channel to execute push according to a preset push rule;
the mobile application includes:
unified equipment identification management module: storing and maintaining an effective device identifier UDTK;
a channel device identifier management module: maintaining an effective channel equipment identifier (CNTK) for each push channel;
a registration module: registering a device type, a UDTK and a channel token with a server;
the pushing method comprises the following steps:
step one, initialization
(1) And (3) pretreatment: the mobile application correctly integrates the SDK of each push channel, and configures the push channel to be connected in the push management module;
(2) Initializing UDTK: calling the unified equipment identifier management module when the application of the mobile application is started every time;
(3) Initializing CNTK: the application of the mobile application calls the channel equipment identification management module;
(4) And equipment registration: calling the registration module by the application of the mobile application;
step two, associating users
When a user executes login operation, the mobile application reports the UDTK of the equipment to the mobile application system, and the mobile application system associates and binds the UDTK and the ID of the user;
step three, general use
(1) Communication state detection
The channel state detection module of the server periodically polls and checks the communication state of the server and each push channel and records the communication state;
(2) Message push
When an application system of the mobile application needs to send a message to a user, the following steps are completed: 1) Transmitting the message content and the UDTK corresponding to the user to a push management module of the server side; 2) The push management module checks various factors and selects a proper push channel according to a preset scheduling rule; 3) The push management module pushes the message according to the selected push channel; 4) The push channel pushes the message to the mobile application completion;
step four, special use
(1) The manual appointed push channel is used, and when the push channel needs to be appointed, manual intervention is used for appointing: 1) The method comprises the steps of starting or closing a push channel allowed to be used in a push management module; 2) The use is carried out according to the mode in common use;
(2) Case of user replacing device: 1) When the user logs out from the equipment, executing a logout action provided by the mobile application system, and removing the associated binding of the user ID and the UDTK; 2) The user uses the new device, and when the user directly logs in without logging out of the old device, the mobile application system uses the UDTK of the new device to replace the existing UDTK record.
2. The push method of a multi-channel message push device according to claim 1, wherein initializing UDTK in the first step comprises the following steps:
1) Reading locally stored UDTK;
2) Returning a local UDTK to a unified equipment identifier distribution module of the server side, and if no UDTK exists, returning a null value;
3) And the unified equipment identifier management module judges whether the reported UDTK is valid or not, and generates and returns a valid UDTK if the reported UDTK is invalid.
3. The push method of a multi-channel message push device according to claim 1, wherein initializing CNTK in the first step comprises the following steps:
1) Calling the SDK of each push channel to obtain the latest CNTK of each push channel;
2) And persistently storing the obtained CNTK.
4. The push method of a multi-channel message push apparatus according to claim 1, wherein the device registration in the first step comprises the following steps:
1) Reading equipment information including an operating system type, an operating system version, a hardware brand and a hardware model;
2) And returning the equipment information, the UDTK and the CNTKs of all channels to an equipment channel recording module of the server side.
5. The method as claimed in claim 1, wherein the various factors in the message pushing of step three include:
1) A push channel from the push management module that allows connections;
2) The server side pushes the communication state of the channel from the channel state detection module;
3) User equipment information from an equipment channel recording module;
4) Push channels from the device channel recording module are available to devices that successfully complete registration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010799111.9A CN111901440B (en) | 2020-08-11 | 2020-08-11 | Multi-channel message pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010799111.9A CN111901440B (en) | 2020-08-11 | 2020-08-11 | Multi-channel message pushing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111901440A CN111901440A (en) | 2020-11-06 |
| CN111901440B true CN111901440B (en) | 2023-04-07 |
Family
ID=73246427
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010799111.9A Active CN111901440B (en) | 2020-08-11 | 2020-08-11 | Multi-channel message pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111901440B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112866414B (en) * | 2021-02-20 | 2022-08-05 | 每日互动股份有限公司 | Data information pushing method and device, computer equipment and storage medium |
| CN113452777B (en) * | 2021-06-25 | 2022-11-04 | 北京奇艺世纪科技有限公司 | Message pushing method and device |
| CN114363409B (en) * | 2022-01-05 | 2023-09-22 | 厦门市易联众易惠科技有限公司 | Multi-channel configurable unified message management method, platform and system |
Citations (4)
| 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 |
| WO2018058982A1 (en) * | 2016-09-30 | 2018-04-05 | 广东美的制冷设备有限公司 | Control information pushing method and pushing device, intelligent router and server |
| CN108063724A (en) * | 2018-01-12 | 2018-05-22 | 吉浦斯信息咨询（深圳）有限公司 | Information push method and its system based on Android platform |
| CN110855792A (en) * | 2019-11-19 | 2020-02-28 | 南京领行科技股份有限公司 | Message pushing method, device, equipment and medium |
-
2020
- 2020-08-11 CN CN202010799111.9A patent/CN111901440B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018058982A1 (en) * | 2016-09-30 | 2018-04-05 | 广东美的制冷设备有限公司 | Control information pushing method and pushing device, intelligent router and server |
| CN107370810A (en) * | 2017-07-13 | 2017-11-21 | 北京奇艺世纪科技有限公司 | Push channel system of selection, server and terminal device |
| CN108063724A (en) * | 2018-01-12 | 2018-05-22 | 吉浦斯信息咨询（深圳）有限公司 | Information push method and its system based on Android platform |
| CN110855792A (en) * | 2019-11-19 | 2020-02-28 | 南京领行科技股份有限公司 | Message pushing method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111901440A (en) | 2020-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111901440B (en) | Multi-channel message pushing method and device | |
| CN101222519B (en) | Remote activation of home devices | |
| CN110086652B (en) | Management system and method for service network element in 5G core network | |
| CN100499510C (en) | Method for positioning fault and service maintenance platform | |
| CN108933789B (en) | Method for preventing personal information leakage and third-party application server | |
| CA2629697A1 (en) | Configuration of ip telephony and other systems | |
| EP3897020A1 (en) | Method and apparatus for verifying subscriber identification module, electronic device, and storage medium | |
| CN107277799B (en) | Method, device, terminal and storage medium for binding mobile phone number | |
| CN100499473C (en) | Method for realizing business request and on-line instruction system | |
| CN110677383A (en) | Firewall opening method and device, storage medium and computer equipment | |
| CN108712440A (en) | User information management method, device, server and storage medium | |
| WO2009011555A2 (en) | System and method for providing device management service to electronic device having no broadband communication module | |
| CN106878987B (en) | Communication method, system and cloud server | |
| CN111309691A (en) | Data sharing exchange system and exchange method based on bus architecture | |
| CN101212346B (en) | Software version management method and device for network element management system | |
| JP5636100B2 (en) | International mobile device identity tracking method and tracking radio network controller for user equipment | |
| WO2008106873A1 (en) | A method, a system and a device for realizing register and communication of the personal handhold telephone terminal | |
| CN113364820A (en) | Equipment control method and device of Internet of things service system | |
| CN112542002A (en) | Car renting system control method and device | |
| WO2006116908A1 (en) | A method and interface apparatus for authentication and charging | |
| CN103888923A (en) | Call proceeding method, system and device applied to virtual private mobile network | |
| CN115866535A (en) | Method and system for realizing 5G message access by multiple protocols | |
| CN113783882B (en) | Information acquisition method and device for edge application, electronic equipment and medium | |
| CN110545527B (en) | Call forwarding method, video communication server and calling terminal | |
| CN101557382A (en) | Professional ability resource management system and professional ability resource access management method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |