CN104023321A - Safe and reliable information transmission system based on mobile network - Google Patents
Safe and reliable information transmission system based on mobile network Download PDFInfo
- Publication number
- CN104023321A CN104023321A CN201410262981.7A CN201410262981A CN104023321A CN 104023321 A CN104023321 A CN 104023321A CN 201410262981 A CN201410262981 A CN 201410262981A CN 104023321 A CN104023321 A CN 104023321A
- Authority
- CN
- China
- Prior art keywords
- message
- client
- receipt
- server end
- subsystem
- 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
Landscapes
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a safe and reliable information transmission system based on a mobile network. The safe and reliable information transmission system comprises a presentation layer, a business layer and a data layer, wherein the presentation layer is a mobile client used for providing an interface of interactive operation for a user; the business layer is formed by an openfire server cluster and is used for receiving, processing, transmitting and retransmitting client information, giving a receipt of the client information and pushing the information to the client, and the business layer comprises a server side information processing sub-system, a server side information retransmission sub-system and a server side information push sub-system; the data layer is used for storing related data of an application system and comprises a business database and a zookeeper data storage cluster. According to the safe and reliable information transmission system, a user of the mobile client learns a transmission status of information quickly, and the information is guaranteed to be safely and reliably transmitted, so that the user experience is improved, the communication quality is guaranteed and the user satisfaction is improved.
Description
Technical field
The present invention relates to transmission of messages field, particularly a kind of safe and reliable message delivery system based on mobile network.
Background technology
Along with popularizing of mobile Internet, mobile device has become the main media of society Information Communication.Mobile Internet shows day by day on the impact of people's interactive mode, however poor user experience, communication quality is low and the high demand of user between also more and more in-depth of contradiction.In order to solve this contradiction, need a kind of solution that can improve user's experience, strengthen communication quality badly.
Summary of the invention
In view of this, the present invention proposes a kind of safe and reliable message delivery system based on mobile network, described system can make mobile client end subscriber learn fast the transmission state of message, and can guarantee the safe and reliable transmission of message, thereby promote user, experience, guarantee communication quality, improve user satisfaction.
Described in the safe and reliable message delivery system based on mobile network that the present invention proposes, system is divided into presentation layer, operation layer and data Layer, it is characterized in that,
Described presentation layer is mobile client, be used to user that the interface of interactive operation is provided, receipt, message retransmission and message display function give information, comprise client message subsystem, client message receipt subsystem, client message retransmission subpacket system and client message display subsystem, wherein
Described client message subsystem, for judging whether the message receiving exists; And display message queue is safeguarded;
Described client message receipt subsystem, for when the client success receipt message, structure also sends client message receipt to server end;
Described client message retransmission subpacket system, for resending the unsuccessful message of sending to server;
Described client message display subsystem, for showing accordingly message according to the type of client received message;
Described operation layer is server end, for receiving, process, forward and retransmitting client message, give client message receipt and to client push message, comprise server end Message Processing subsystem, server end message retransmission subsystem and server end message push subsystem, wherein
Described server end Message Processing subsystem, receives, forwards client message and give receipt to client message for being responsible for;
Described server end message retransmission subsystem, for resending the unsuccessful message of sending to client;
Described server end message push subsystem, for receiving other application server to the message of client push, then forwards to client; Obtain the message receipt that client is returned, according to described message receipt, determine message compensation policy; And when successfully receiving the message of described other application servers, structure also sends message receipt to described other application servers;
Described data Layer is for storing the related data that comprises user profile and deferred information.
Described client message subsystem is after receiving message, the described message receiving and the message in display message queue are compared, determine whether to exist identical message, if existed, abandon this message: if there is no, message is sent to described client message display subsystem to show.
The queue of described display message is the queue that the message that shown of client forms.
Described client message subsystem is saved in the id of the message having shown in display message queue.
Whether the id of the id of the message that described client message subsystem receives by judgement and message in display message queue identical determines whether to exist identical message.
The type of the message of described client message subsystem based on receiving is safeguarded display message queue: if what receive is message receipt, delete the message corresponding with message receipt in display message queue.
If the message receiving is PUSH message, described client message display subsystem shows PUSH message in client; If the message receiving is common message, described client message display subsystem display message content in chat interface.
When receiving PUSH message or common message, corresponding receipt is constructed and sent to described client message receipt subsystem to server end.
Described client message retransmission subpacket system is also for the queue of maintain customer end transmitted message, when receiving the receipt of service end success receipt message, from the queue of described client transmitted message, delete corresponding message, if do not receive receipt, when traveling through queue, retransmits timer period this message, with this, improve the reliability that user end to server end sends message, the queue of described client transmitted message is the queue that client transmitted message forms.
Described client message display subsystem for according to this three types of common message, message receipt and PUSH message to the message receiving from message eject mode, different Graphics Processings is carried out in message font color aspect.
After described server end Message Processing subsystem receipt message, according to the state of the object client of described message, process accordingly: directly send, save as deferred information, abandon message; And send corresponding receipt to the transmission client of described message.
The queue of described server end message retransmission subsystem maintenance server end transmitted message, when receiving receipt, from described server end transmitted message queue, delete corresponding message, if do not receive receipt, when traveling through queue, retransmits timer period this message, with this, improve server end and to client, send the reliability of message, the queue of described server end transmitted message queue for being formed by server end transmitted message.
Described server end message retransmission subsystem is taked the retransmission policy of different stage according to the significance level of message, frequency and the number of times of more important message retransmission are higher.
Described server end message push subsystem or server end Message Processing subsystem structure message receipt have following situation:
Situation 1: when the object client of message is online, server end message push subsystem or server end Message Processing subsystem directly send to message the object client of described message, and receive the message receipt " the successful receipt message of message recipient " that described object client sends, then send to the transmitting terminal of message;
Situation 2: when the object client off-line of message, server end message push subsystem or server end Message Processing subsystem are deferred information by message stores, and construct message receipt " message has saved as deferred information ", then above-mentioned message receipt " message has saved as deferred information " is sent to the transmitting terminal of message;
Situation 3: when the object client of message is logined, server end message push subsystem or server end Message Processing subsystem extract by the deferred information that belongs to the object client of this message the object client that sends to this message from database, and receive the message receipt " message recipient successfully receives deferred information " that described object client sends, then send to the transmitting terminal of message.
Situation 4: when the object client of message does not exist or is anonymity, server end message push subsystem or server end Message Processing subsystem are constructed message receipt " message recipient does not exist or is anonymous ", and described message receipt " message recipient does not exist or is anonymous " are sent to the transmitting terminal of message;
Situation 5: when the object client of message arranges authority and forbids that the transmitting terminal of described message sends message to it, server end message push subsystem or server end Message Processing subsystem are constructed message receipt " because shielding action cannot send to recipient by message ", and described message receipt " because shielding action cannot send to recipient by message " are sent to the transmitting terminal of message.
Situation 6: when not receiving the message receipt that the object client of message sends, server end message push subsystem or server end Message Processing subsystem trigger described server end message retransmission subsystem and resend message to the object client of message, then construct message receipt " message resends ", and described message receipt " message resends " is sent to the transmitting terminal of message.
Situation 7: when the sending times of described server end message retransmission subsystem reaches in limited time, server end message push subsystem or server end Message Processing subsystem structure message receipt " message retransmission number of times has reached the upper limit; abandon retransmitting and being stored as deferred information ", and described message receipt " message retransmission number of times has reached the upper limit, abandons retransmitting and being stored as deferred information " is sent to the transmitting terminal of message.
Described server end is also for the queue of maintenance server end transmitted message, after server end receipt message, added in the queue of described server end transmitted message, when server end receives corresponding message receipt, from the queue of described server end transmitted message, delete corresponding message.
Message server of the present invention adopts trunking mode, and each message server need to be shared the queue of same server end transmitted message, and the present invention realizes the sharing and synchronization of server end transmitted message queue by the zookeeper with memory function.Zookeeper is by electing leader and follower, and the correct prerequisite of carrying out of its algorithm is to have machine over half normally to work, therefore should adopt odd number platform machine.Every machine is disposed a message server and a zookeeper server, carries out load balance between each message server, carries out data synchronous between each zookeeper server, and message server is preferentially from local zookeeper server access data.In each machine, only have a machine as master server, all the other are as dependent server, and master server is responsible for the repeating transmission of message.
In client, by each client, safeguard separately the queue of a client transmitted message, its mechanism is similar with server end retransmission mechanism, does not repeat them here.Server end message retransmission strategy guarantees that the message that server sends must be arrived by client, client message retransmission policy guarantees that the message that client sends must serviced termination receive, server end message retransmission strategy and client message retransmission policy have been guaranteed the safe and reliable transmission of message.
Timer control message is retransmitted, and requires message in transmitted message queue at least to comprise message body, data such as sending times, last transmitting time.When carrying out the queue of timer task traversal, if certain message apart from last time transmitting time surpass threshold value and just retransmit this message, and revise the last transmitting time of message and transmission times, when certain message transmission times reaches the upper of setting, just saved as deferred information in limited time, treat to receive again this message after user logins.Message retransmission mechanism has improved the probability that message is sent to, and has improved communication quality.
Accompanying drawing explanation
Fig. 1 is the structural representation of the safe and reliable message delivery system based on mobile network that provides of one embodiment of the invention;
Fig. 2 is client receipt and the server end receipt schematic diagram of message delivery system of the present invention;
Fig. 3 is message and the message receipt schematic diagram of message delivery system of the present invention;
Fig. 4 is the synchronous and shared schematic diagram of openfire cluster data of message delivery system of the present invention;
Fig. 5 is the message retransmission mechanism flow chart of message delivery system of the present invention;
Fig. 6 is the mobile client message sink flow chart of message delivery system of the present invention.
Embodiment
As shown in Figure 1, the present invention proposes a kind of safe and reliable message delivery system based on mobile network, this message delivery system consists of presentation layer, operation layer and data Layer, and wherein presentation layer consists of client message receiving subsystem, client message receipt subsystem, client message retransmission subpacket system, client message display subsystem; Operation layer consists of server end Message Processing subsystem, server end message retransmission subsystem, server end message push subsystem; Data Layer main usage data storehouse and zookeeper storage presentation layer and the required data of operation layer.This message delivery system is used three machines to build message server cluster and zookeeper cluster: message server cluster is intended to reduce by load balancing the pressure that single server bears, providing more efficiently, more stable service; Zookeeper cluster is mainly to carry out data synchronously and data sharing for each message server.
Presentation layer mainly refers to mobile client, and the interface for user provides interactive operation, comprises the functions such as message receipt, message retransmission and message demonstration.
Operation layer mainly consists of openfire server cluster, for receiving, process, forward and retransmit client message, give client message receipt and to client push message etc.In addition, also comprise data access interface, for accessing boat trip database and zookeeper data storage in length and breadth.
Data Layer is for storing the boat trip related data of application system in length and breadth, and its Air China trip is the main storing subscriber information of database and deferred information etc. in length and breadth, and zookeeper cluster is mainly stored the shared data of openfire cluster.
Client message subsystem, for judging whether the message receiving exists; And display message queue is safeguarded;
Client message receipt subsystem, for constructing the concurrent client message receipt that send.When client successfully receives online message or deferred information, to service end, send the receipt of " successfully receiving online message " or " successfully receiving deferred information ", notification server end client successfully receives message, need not resend this message.
Client message retransmission subpacket system, for resending the unsuccessful message of sending to server.Queue being formed by client transmitted message of client message retransmission subpacket system maintenance, when receiving the receipt of service end success receipt message, from queue, delete corresponding message, if do not receive receipt, when timer period travels through queue, retransmit this message, with this, improve the reliability that user end to server end sends message.
Client message display subsystem, for giving different demonstrations according to type of message to message.For difference common message, message receipt and PUSH message, client message display subsystem ejects the aspects such as mode, message font color and has carried out different processing from message.
Server end Message Processing subsystem, for receiving, forwarding client message and give receipt to client message.After server end receipt message, according to the different conditions of message recipient, carry out different message policies, as direct transmission, save as deferred information, abandon message etc., and send corresponding receipt to sender of the message.
Server end message retransmission subsystem, for resending the unsuccessful message of sending to client.Server end is safeguarded a queue being comprised of server end transmitted message, when receiving receipt, from queue, delete corresponding message, if do not receive receipt, when traveling through queue, retransmits timer period this message, and with this, improve server end and to client, send the reliability of message.Server end is taked the retransmission policy of different stage according to the significance level of message, frequency and the number of times of more important message retransmission are higher.Multi-level retransmission policy be more convenient for customization, more flexible.
Server end message push subsystem, for forward other application servers by server end the message to client push, and obtain the message receipt that client is sent, thereby determine and take which kind of message compensation policy according to message receipt.
Server end Message Processing subsystem, server end message push subsystem, server end message retransmission subsystem cooperate jointly, have guaranteed the high reliability of message push on the basis that completes message push function.
As shown in Figure 2, the safe and reliable message delivery system based on mobile network of the present invention, its message transmitting procedure is divided into 4 stages: (1) sender of the message sends a message to server end; (2) server sends to message recipient by message; (3) message recipient sends to server by receipt; (4) server sends to sender of the message by receipt.Wherein, message receipt can be divided into two large classes according to the state of message recipient: client receipt and server end receipt.When message recipient is online, it receives message and is responsible for structure message receipt later, and sends to server end to be transmitted to sender of the message by server end in this receipt, and this programme is constructed this type of message receipt by client is called client message receipt.When message recipient is non-presence, server end is responsible for constructing message receipt, and this message receipt is sent to sender of the message, and this programme is constructed this type of receipt by server end is called server receipt.As can be seen from Figure 2, to be to construct the main body of receipt different for client receipt and the main distinction of server end receipt.
Fig. 3 is the design sketch of message and message receipt.Message receipt is realized principle:
(1) when message recipient is online, server directly sends to message recipient by message, and by message recipient structure message receipt " the successful receipt message of message recipient ", server is responsible for this message receipt to send to sender of the message;
(2) when message recipient off-line, server is deferred information by message stores, by server constructs message receipt " message has saved as deferred information ", and this message receipt is sent to sender of the message;
(3), when user logins, server extracts from database the deferred information that belongs to this user send to user.User constructs message receipt " message recipient successfully receives deferred information " after receiving deferred information, by server, is responsible for this receipt to be transmitted to sender of the message.
(4) when message recipient does not exist or be anonymous, server constructs message receipt " message recipient does not exist or is anonymous ", and this message receipt is sent to sender of the message;
(5) when message recipient arranges authority disable message sender to its transmission message, server constructs message receipt " because shielding action cannot send to recipient by message ", and this receipt is sent to sender of the message.
Except the 5 class receipts of showing in figure, also have receipts such as " message resend " and " message retransmission number of times has reached the upper limit, abandons retransmitting and being stored as deferred information ", in view of length restriction, at this, will not enumerate.
Fig. 4 is the schematic diagram that openfire cluster and zookeeper cluster carry out data interaction.For supporting message retransmission function, each openfire server need to be shared same message queue, after Openfire receipt message, added to shared queue, receive message receipt Shi Xucong shared queue and delete corresponding message, the present invention uses zookeeper cluster to realize the sharing and synchronization of message queue.Zookeeper is by electing leader and follower, and the correct prerequisite of carrying out of its algorithm is to have machine over half normally to work, therefore should adopt odd number platform machine.Fig. 4 is openfire cluster and the mutual schematic diagram of zookeeper cluster, every machine is disposed an Openfire server and a zookeeper server, between each Openfire, carry out load balance, between each zookeeper, carry out data synchronous, openfire is preferentially from local zookeeper access data.In each machine, only have a machine as master server, all the other are as dependent server, and master server is responsible for the repeating transmission of message.
Fig. 5 is message retransmission mechanism flow chart of the present invention.For realizing message retransmission, need to safeguard a message queue, when openfire receives message, message is added to queue, when receiving message receipt, Openfire deletes corresponding message from queue.Message in queue comprises message body, data such as sending times, last transmitting time, by timer period property, carries out repeating transmission task.When carrying out the queue of timer task traversal, if certain message apart from last time transmitting time surpass threshold value and just retransmit this message, and revise the last transmitting time of message and transmission times, when certain message transmission times reaches the upper of setting, just saved as deferred information in limited time, treat to receive again this message after user logins.Message retransmission mechanism has improved the probability that message is sent to, and has improved communication quality.
Fig. 6 is mobile client message sink flow chart.Client message comprises the steps:
Step 1, client, after message, is compared with the message in client message queue, checks the message that whether has identical id in message queue, if existed, abandons this message.
Step 2, client is saved in the id of the message having shown in message queue, before user's display message, first checking whether this queue has existed this message, if existed, can not repeat to be shown to user, with this, avoid repeating to be shown to user because retransmitting message mechanism receives duplicate message.
Step 3, the type of the message that judgement receives.If what receive is message receipt, in sending message queue, delete the message corresponding with message receipt; If PUSH message, shows PUSH message in client; If common message, display message content in chat interface.
Step 4, corresponding receipt can be constructed and send to client during to PUSH message or common message, to server end, by server, is responsible for message receipt to send to sender of the message.
Claims (15)
1. the safe and reliable message delivery system based on mobile network, described system is divided into presentation layer, operation layer and data Layer, it is characterized in that,
Described presentation layer is mobile client, be used to user that the interface of interactive operation is provided, receipt, message retransmission and message display function give information, comprise client message subsystem, client message receipt subsystem, client message retransmission subpacket system and client message display subsystem, wherein
Described client message subsystem, for judging whether the message receiving exists; And display message queue is safeguarded;
Described client message receipt subsystem, for when the client success receipt message, structure also sends client message receipt to server end;
Described client message retransmission subpacket system, for resending the unsuccessful message of sending to server;
Described client message display subsystem, for showing accordingly message according to the type of client received message;
Described operation layer is server end, for receiving, process, forward and retransmitting client message, give client message receipt and to client push message, comprise server end Message Processing subsystem, server end message retransmission subsystem and server end message push subsystem, wherein
Described server end Message Processing subsystem, receives, forwards client message and give receipt to client message for being responsible for;
Described server end message retransmission subsystem, for resending the unsuccessful message of sending to client;
Described server end message push subsystem, for receiving other application server to the message of client push, then forwards to client; Obtain the message receipt that client is returned, according to described message receipt, determine message compensation policy; And when successfully receiving the message of described other application servers, structure also sends message receipt to described other application servers;
Described data Layer is for storing the related data that comprises user profile and deferred information.
2. the safe and reliable message delivery system based on mobile network according to claim 1, it is characterized in that, described client message subsystem is after receiving message, the described message receiving and the message in display message queue are compared, determine whether to exist identical message, if exist, abandon this message: if there is no, message is sent to described client message display subsystem to show.
3. the safe and reliable message delivery system based on mobile network according to claim 2, is characterized in that, the queue of described display message is the queue that the message that shown of client forms.
4. the safe and reliable message delivery system based on mobile network according to claim 3, is characterized in that, described client message subsystem is saved in the id of the message having shown in display message queue.
5. the safe and reliable message delivery system based on mobile network according to claim 4, it is characterized in that, whether the id of the id of the message that described client message subsystem receives by judgement and message in display message queue identical determines whether to exist identical message.
6. the safe and reliable message delivery system based on mobile network according to claim 5, it is characterized in that, the type of the message of described client message subsystem based on receiving is safeguarded display message queue: if what receive is message receipt, delete the message corresponding with message receipt in display message queue.
7. the safe and reliable message delivery system based on mobile network according to claim 1, is characterized in that, if the message receiving is PUSH message, described client message display subsystem shows PUSH message in client; If the message receiving is common message, described client message display subsystem display message content in chat interface.
8. the safe and reliable message delivery system based on mobile network according to claim 1, is characterized in that, when receiving PUSH message or common message, corresponding receipt is constructed and sent to described client message receipt subsystem to server end.
9. the safe and reliable message delivery system based on mobile network according to claim 1, it is characterized in that, described client message retransmission subpacket system is also for the queue of maintain customer end transmitted message, when receiving the receipt of service end success receipt message, from the queue of described client transmitted message, delete corresponding message, if do not receive receipt, when traveling through queue, retransmits timer period this message, with this, improve the reliability that user end to server end sends message, the queue of described client transmitted message is the queue that client transmitted message forms.
10. the safe and reliable message delivery system based on mobile network according to claim 1, it is characterized in that, described client message display subsystem for according to this three types of common message, message receipt and PUSH message to the message receiving from message eject mode, different Graphics Processings is carried out in message font color aspect.
The 11. safe and reliable message delivery systems based on mobile network according to claim 1, it is characterized in that, after described server end Message Processing subsystem receipt message, according to the state of the object client of described message, process accordingly: directly send, save as deferred information, abandon message; And send corresponding receipt to the transmission client of described message.
The 12. safe and reliable message delivery systems based on mobile network according to claim 1, it is characterized in that, the queue of described server end message retransmission subsystem maintenance server end transmitted message, when receiving receipt, from described server end transmitted message queue, delete corresponding message, if do not receive receipt, when traveling through queue, retransmits timer period this message, with this, improve server end and to client, send the reliability of message, the queue of described server end transmitted message queue for being formed by server end transmitted message.
The 13. safe and reliable message delivery systems based on mobile network according to claim 12, it is characterized in that, described server end message retransmission subsystem is taked the retransmission policy of different stage according to the significance level of message, frequency and the number of times of more important message retransmission are higher.
14. according to the safe and reliable message delivery system based on mobile network one of claim 1-13 Suo Shu, it is characterized in that, described server end message push subsystem or server end Message Processing subsystem structure message receipt have following situation:
Situation 1: when the object client of message is online, server end message push subsystem or server end Message Processing subsystem directly send to message the object client of described message, and receive the message receipt " the successful receipt message of message recipient " that described object client sends, then send to the transmitting terminal of message;
Situation 2: when the object client off-line of message, server end message push subsystem or server end Message Processing subsystem are deferred information by message stores, and construct message receipt " message has saved as deferred information ", then above-mentioned message receipt " message has saved as deferred information " is sent to the transmitting terminal of message;
Situation 3: when the object client of message is logined, server end message push subsystem or server end Message Processing subsystem extract by the deferred information that belongs to the object client of this message the object client that sends to this message from database, and receive the message receipt " message recipient successfully receives deferred information " that described object client sends, then send to the transmitting terminal of message;
Situation 4: when the object client of message does not exist or is anonymity, server end message push subsystem or server end Message Processing subsystem are constructed message receipt " message recipient does not exist or is anonymous ", and described message receipt " message recipient does not exist or is anonymous " are sent to the transmitting terminal of message;
Situation 5: when the object client of message arranges authority and forbids that the transmitting terminal of described message sends message to it, server end message push subsystem or server end Message Processing subsystem are constructed message receipt " because shielding action cannot send to recipient by message ", and described message receipt " because shielding action cannot send to recipient by message " are sent to the transmitting terminal of message;
Situation 6: when not receiving the message receipt that the object client of message sends, server end message push subsystem or server end Message Processing subsystem trigger described server end message retransmission subsystem and resend message to the object client of message, then construct message receipt " message resends ", and described message receipt " message resends " is sent to the transmitting terminal of message;
Situation 7: when the sending times of described server end message retransmission subsystem reaches in limited time, server end message push subsystem or server end Message Processing subsystem structure message receipt " message retransmission number of times has reached the upper limit; abandon retransmitting and being stored as deferred information ", and described message receipt " message retransmission number of times has reached the upper limit, abandons retransmitting and being stored as deferred information " is sent to the transmitting terminal of message.
The 15. safe and reliable message delivery systems based on mobile network according to claim 14, it is characterized in that, described server end is also for the queue of maintenance server end transmitted message, after server end receipt message, added in the queue of described server end transmitted message, when server end receives corresponding message receipt, from the queue of described server end transmitted message, delete corresponding message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410262981.7A CN104023321A (en) | 2014-06-13 | 2014-06-13 | Safe and reliable information transmission system based on mobile network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410262981.7A CN104023321A (en) | 2014-06-13 | 2014-06-13 | Safe and reliable information transmission system based on mobile network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104023321A true CN104023321A (en) | 2014-09-03 |
Family
ID=51439849
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410262981.7A Pending CN104023321A (en) | 2014-06-13 | 2014-06-13 | Safe and reliable information transmission system based on mobile network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104023321A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105005253A (en) * | 2015-06-17 | 2015-10-28 | 中山市默拜尔网络科技有限公司 | Information transmission monitoring system |
| CN105554142A (en) * | 2015-12-24 | 2016-05-04 | 北京奇虎科技有限公司 | Method, apparatus and system for pushing messages |
| CN105871703A (en) * | 2016-06-03 | 2016-08-17 | 用友网络科技股份有限公司 | Push and pull combined instant communication message acquisition system and method |
| CN106201735A (en) * | 2016-06-27 | 2016-12-07 | 北京票之家科技有限公司 | Method for message transmission and system |
| CN106790728A (en) * | 2017-03-30 | 2017-05-31 | 北京深思数盾科技股份有限公司 | information push method and system |
| CN107147562A (en) * | 2017-04-27 | 2017-09-08 | 腾讯科技（深圳）有限公司 | Message treatment method and device |
| CN108989157A (en) * | 2017-06-05 | 2018-12-11 | 北京京东尚科信息技术有限公司 | Method, apparatus for smart machine control |
| CN109582017A (en) * | 2018-11-27 | 2019-04-05 | 中国电子科技集团公司第二十研究所 | A kind of representation method for the unmanned systems mission planning result for supporting multimode to distribute |
| WO2019071620A1 (en) * | 2017-10-09 | 2019-04-18 | 华为技术有限公司 | Garbage data cleaning method and equipment |
| CN111211973A (en) * | 2020-01-15 | 2020-05-29 | 百望股份有限公司 | Information processing method and device in invoice field and storage medium |
| CN114143334A (en) * | 2021-12-03 | 2022-03-04 | 爱信诺征信有限公司 | Terminal control method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1604097A (en) * | 2003-09-29 | 2005-04-06 | 英业达股份有限公司 | Method and system for processing information dispatching |
| CN101079835A (en) * | 2006-12-21 | 2007-11-28 | 腾讯科技（深圳）有限公司 | A method and system for realizing offline multimedia word leaving based on instant communication software |
| CN101083634A (en) * | 2006-11-17 | 2007-12-05 | 腾讯科技（深圳）有限公司 | System and method for handling electronic mail |
| CN101583096A (en) * | 2009-06-16 | 2009-11-18 | 中兴通讯股份有限公司 | Multimedia Messaging Service (MMS) center and method thereof for caching mobile paper messages |
| CN102647365A (en) * | 2011-02-16 | 2012-08-22 | 北京大学 | Method and device for processing message and message status and data exchange server |
| CN102664827A (en) * | 2012-04-24 | 2012-09-12 | 深圳市三木通信技术有限公司 | Instant messaging message receipt method and system |
-
2014
- 2014-06-13 CN CN201410262981.7A patent/CN104023321A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1604097A (en) * | 2003-09-29 | 2005-04-06 | 英业达股份有限公司 | Method and system for processing information dispatching |
| CN101083634A (en) * | 2006-11-17 | 2007-12-05 | 腾讯科技（深圳）有限公司 | System and method for handling electronic mail |
| CN101079835A (en) * | 2006-12-21 | 2007-11-28 | 腾讯科技（深圳）有限公司 | A method and system for realizing offline multimedia word leaving based on instant communication software |
| CN101583096A (en) * | 2009-06-16 | 2009-11-18 | 中兴通讯股份有限公司 | Multimedia Messaging Service (MMS) center and method thereof for caching mobile paper messages |
| CN102647365A (en) * | 2011-02-16 | 2012-08-22 | 北京大学 | Method and device for processing message and message status and data exchange server |
| CN102664827A (en) * | 2012-04-24 | 2012-09-12 | 深圳市三木通信技术有限公司 | Instant messaging message receipt method and system |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105005253A (en) * | 2015-06-17 | 2015-10-28 | 中山市默拜尔网络科技有限公司 | Information transmission monitoring system |
| CN105554142A (en) * | 2015-12-24 | 2016-05-04 | 北京奇虎科技有限公司 | Method, apparatus and system for pushing messages |
| CN105554142B (en) * | 2015-12-24 | 2019-02-01 | 北京奇虎科技有限公司 | The method, apparatus and system of message push |
| CN105871703A (en) * | 2016-06-03 | 2016-08-17 | 用友网络科技股份有限公司 | Push and pull combined instant communication message acquisition system and method |
| CN106201735A (en) * | 2016-06-27 | 2016-12-07 | 北京票之家科技有限公司 | Method for message transmission and system |
| CN106790728A (en) * | 2017-03-30 | 2017-05-31 | 北京深思数盾科技股份有限公司 | information push method and system |
| CN107147562A (en) * | 2017-04-27 | 2017-09-08 | 腾讯科技（深圳）有限公司 | Message treatment method and device |
| CN108989157A (en) * | 2017-06-05 | 2018-12-11 | 北京京东尚科信息技术有限公司 | Method, apparatus for smart machine control |
| US11126546B2 (en) | 2017-10-09 | 2021-09-21 | Huawei Technologies Co., Ltd. | Garbage data scrubbing method, and device |
| WO2019071620A1 (en) * | 2017-10-09 | 2019-04-18 | 华为技术有限公司 | Garbage data cleaning method and equipment |
| US11704240B2 (en) | 2017-10-09 | 2023-07-18 | Huawei Technologies Co., Ltd. | Garbage data scrubbing method, and device |
| CN109582017A (en) * | 2018-11-27 | 2019-04-05 | 中国电子科技集团公司第二十研究所 | A kind of representation method for the unmanned systems mission planning result for supporting multimode to distribute |
| CN111211973B (en) * | 2020-01-15 | 2022-06-21 | 百望股份有限公司 | Information processing method and device in invoice field and storage medium |
| CN111211973A (en) * | 2020-01-15 | 2020-05-29 | 百望股份有限公司 | Information processing method and device in invoice field and storage medium |
| CN114143334A (en) * | 2021-12-03 | 2022-03-04 | 爱信诺征信有限公司 | Terminal control method and device |
| CN114143334B (en) * | 2021-12-03 | 2024-04-09 | 爱信诺征信有限公司 | Terminal control method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104023321A (en) | Safe and reliable information transmission system based on mobile network | |
| US10834031B2 (en) | Information exchange method, client, and apparatus | |
| US8769262B2 (en) | VPN connection system and VPN connection method | |
| CN109561159B (en) | Data processing method and system based on Websocket long connection | |
| US9037935B2 (en) | Apparatus and method for retransmitting message in message transmission system | |
| CN106713126B (en) | Method and system for one-way transmission of e-mail information between internal network and external network | |
| CN110413424B (en) | Configurable third-party message callback method, device, server and storage medium | |
| CN102347916A (en) | Gateway, cross-community group information processing system and method | |
| CN106161190A (en) | Point-to-point instant communicating method | |
| US20130191484A1 (en) | Mail transfer system, mail gateway and data store server | |
| CN103684707A (en) | Server-side and user-side message transmission processing method, message transmission method and message transmission system | |
| CN105165035B (en) | Have both the multimedia message transmission of text message transmission | |
| CN104348613A (en) | User verification method, apparatus and system | |
| CN109120385B (en) | Data transmission method, device and system based on data transmission system | |
| CN112994851B (en) | Method and device for supporting differentiated negotiable parallel data communication | |
| CN103648085A (en) | Mobile terminal message transmitting method for overcoming network jitter | |
| US9451524B2 (en) | Wireless networking with flexibly-ordered relayers | |
| CN102904764A (en) | Data transmission device and transmission method thereof | |
| CN105024907A (en) | IM information pushing method and system, server and platform | |
| CN101001213A (en) | Short message transmission system and method | |
| CN103391238A (en) | Method for message delivery state notification and reliable transmission based on XMPP | |
| CN102986173B (en) | Method for setting message status and converged internet protocol message (CPM) traffic server | |
| US10623365B2 (en) | Message redirection protocol | |
| CN112187408B (en) | Data processing method, system, device, storage medium and processor | |
| CN101494569B (en) | Method and apparatus for processing message |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140903 |
|
| RJ01 | Rejection of invention patent application after publication |