CN104660708A - HTTP (Hyper Text Transfer Protocol) based mobile application message forwarding method and system - Google Patents
HTTP (Hyper Text Transfer Protocol) based mobile application message forwarding method and system Download PDFInfo
- Publication number
- CN104660708A CN104660708A CN201510108911.0A CN201510108911A CN104660708A CN 104660708 A CN104660708 A CN 104660708A CN 201510108911 A CN201510108911 A CN 201510108911A CN 104660708 A CN104660708 A CN 104660708A
- Authority
- CN
- China
- Prior art keywords
- message
- mobile terminal
- service end
- http
- mobile
- 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.)
- Granted
Links
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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses an HTTP (Hyper Text Transfer Protocol) based mobile application message forwarding method and a system, relating to the field of mobile application message forwarding. The method comprises the following steps: segmenting a message into multiple message subjects by a server side; subscribing the message which is in accordance with the HTTP POST request to the server side by a mobile terminal; sending all messages to the mobile terminal through corresponding HTTP connection after the server side generates the message subject in accordance with the subscription of the mobile terminal and the matched ID message; enabling messages which are not forwarded to form a persistent buffer queue by the server side, taking out the messages from the persistent buffer queue and forwarding by the server side after the mobile terminal and the server side are re-connected; and processing the received message by the mobile terminal. The method is suitable for various types of mobile terminals, electric quantity and flow resources can be saved, the using cost is reduced, the message can be forwarded to the mobile terminal reliably when the connection of the mobile terminal and the server side is interrupted, and the use is convenient.
Description
Technical field
The present invention relates to Mobile solution message push field, be specifically related to a kind of Mobile solution information push method based on HTTP and system.
Background technology
Along with computing capability and the intelligentized development of mobile terminal, the application program of mobile terminal is more and more abundanter, and along with the progress of society, mobile terminal has been widely used among society.When the application of mobile terminal uses, need to obtain some particular messages (i.e. message push) from service end in real time, to remind user in time.
When service end carries out message push to mobile terminal, there is following defect:
(1) mobile terminal receipt message pushes needs to expend electricity, and then reduces the electric power flying power of mobile terminal, in order to ensure the normal use of mobile terminal, is difficult to poll services end message on mobile terminals.
(2) can data communication be carried out during mobile terminal receipt message, and then the flow of mobile terminal can be consumed, if the flow consumed is excessive, can the use cost of adding users, bring loss economically to user.
(3) type of mobile terminal is more, the method difference (mobile terminal of such as Android platform and the mobile terminal of apple ios platform have respective distinctive information push method) of dissimilar mobile terminal PUSH message, and then make to need for information push method corresponding to dissimilar mobile terminal exploitation, development cost is higher.
Application a large amount of on mobile terminal adopts mixed developing mode, and the core content of application adopts Web mode to realize.Http protocol (HyperText Transfer Protocol, HTML (Hypertext Markup Language)) is a kind of conventional agreement, and all types of mobile terminal all can adopt http protocol to carry PUSH message.
At present, the common information push method based on HTTP is:
(1) poll, namely mobile terminal is regularly from service end acquisition request message, and service end has message or do not have message all to terminate the connection with mobile terminal to mobile terminal return information; During each acquisition request message of mobile terminal, all need to re-establish with service end to be connected.
When adopting the mode of poll to carry out message push, mobile terminal and service end connect to be needed to take certain hour, not only makes mobile terminal from service end Real-time Obtaining message, and cannot can consume electricity and the flow of mobile terminal.
(2) long poll (also can be described as " drawing "), mobile terminal is from service end acquisition request message, before service end return messages, unimpeded (namely the using HTTP to grow to be connected) that keep mobile terminal and service end to communicate, terminates the connection with mobile terminal to mobile terminal return information when service end has message always.
When adopting the mode of long poll to carry out message push, the general single of service end returns a message, when mobile terminal obtains message again, still needs to re-establish with service end to be connected.
(3) WebSocket, WebSocket are the agreements that HTML5 mono-kind is new, and it can realize the full-duplex communication of browser and server; But what WebSocket set up is that full duplex TCP connects, and can only use under the environment of HTML5, cannot be applicable to http protocol, the scope of application is more single.
Summary of the invention
For the defect existed in prior art, the object of the present invention is to provide a kind of Mobile solution information push method based on HTTP and system.The present invention can be applicable to all kinds mobile terminal, can not only save power and floating resources, reduces use cost, and when mobile terminal and service end disconnecting, can to mobile terminal, be convenient to people and use by PUSH message reliably.
For reaching above object, the Mobile solution information push method based on HTTP provided by the invention, the method comprises the following steps:
S1: message is divided into some message subjects by service end, includes some dissimilar message in each message subject, every bar message is all configured with coupling ID, forwards step S2 to;
S2: mobile terminal sends HTTP POST request to service end, HTTP POST request comprises message subject, type of message, message sequence number and coupling ID, and mobile terminal subscribes to the message meeting HTTP POST and ask to service end, forward step S3 to;
S3: service end timing pushes heartbeat message to the mobile terminal subscribed to, and mobile terminal judges whether heartbeat message receives successfully, if so, forwards step S4 to, otherwise re-executes step S2;
S4: after service end produces the message of message subject and the coupling ID meeting mobile terminal subscription, service end is by message sequence, and service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S5 to;
S5: after service end sends a message to mobile terminal at every turn, all judges whether mobile terminal receives message, if so, forwards step S7 to, otherwise forwards step S6 to;
S6: the message do not pushed is formed persistence buffer queue by service end, and mobile terminal records receives the sequence number of last message; Mobile terminal re-establishes with service end and is connected, and mobile terminal subscribes to the message after last message sequence number, and service end is taken out message and pushed from persistence buffer queue, re-executes step S5;
S7: the message received is carried out unserializing and processing messages by mobile terminal.
On the basis of technique scheme, step S4 specifically comprises the following steps:
S401: service end inquires about the mobile terminal of all subscription current messages after producing message according to message subject, service end travels through all mobile terminals subscribing to current message, forwards step S402 to;
S402: judge successively the coupling ID of all mobile terminals whether meet current message theme under the coupling ID of all message, if so, forward step S404 to, otherwise forward step S403 to;
S403: judge whether the coupling ID of current mobile terminal meets the coupling ID of current message, if so, forwards step S404 to, otherwise forward step S405 to;
S404: service end is by current message serializing, and service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S405 to;
S405: judge whether service end completes all mobile terminal traversals, and if so, step S4 terminates, and forwards step S5 to; Otherwise continue to perform step S402.
On the basis of technique scheme, message subject described in step S1 is used for mark and organizes particular message, and message subject is a readable character string.
On the basis of technique scheme, described in step S1, mate the ID of ID that ID is message particular type or message relating resource.
On the basis of technique scheme, heartbeat message described in step S3 is the built-in message of mobile terminal.
On the basis of technique scheme, service end described in step S4 uses the exchanges data JSON form of lightweight by message sequence.
On the basis of technique scheme, step S6 is further comprising the steps of: if service end produces new information and the not yet successful connection of service end and mobile terminal, current new information is put into persistence buffer queue and carried out label by continuous numeric order by service end.
On the basis of technique scheme, the message received is carried out unserializing and after processing messages by mobile terminal described in step S7, further comprising the steps of: to judge whether mobile terminal removes subscription, if, service end removes mobile terminal subscription information, terminates, otherwise forwards step S4 to.
Realize the Mobile solution message push system based on HTTP of said method, this system comprises the subscribing module and message reception module that are positioned at mobile terminal, is positioned at the message subject administration module of service end, subscription management module and application module;
Described subscribing module is used for: when mobile terminal needs subscribe message, sends HTTP POST request to service end; When mobile terminal does not receive heartbeat message, control mobile terminal and continue to send HTTP POST request to service end;
Described subscription management module is used for: when mobile terminal subscribe message, keeps being connected with buffer memory HTTP, the information of record move terminal subscribes; When mobile terminal removes subscription, close HTTP and connect and remove mobile terminal subscription information; When PUSH message failure, the message do not pushed is formed persistence buffer queue;
Described application module is used for: after producing message, send the message push request of corresponding theme to message subject administration module;
Described message subject administration module is used for: after receiving the message push request of corresponding theme, and by defining the coupling ID of theme message structure and message, the agreement that mobile terminal and service end are reached an agreement also carries out message push; The information of the mobile terminal of record subscribe message theme, for needing the continuous sequence number of all message markings being sent to mobile terminal;
Described message reception module is used for: receive the message that service end pushes, message is carried out unserializing and processing messages.
Compared with prior art, the invention has the advantages that:
(1), compared with poll of the prior art, when the present invention uses, mobile terminal is asked to service end subscribe message by HTTP POST, and can be applied to various types of mobile terminal, the scope of application is more extensive.
Meanwhile, HTTP POST request comprises message subject, after service end produces message, issues all message to mobile terminal according to the message subject that mobile terminal is subscribed to; When mobile terminal and service end disconnecting, the present invention can make service end that message is carried out persistence buffer memory, to be connected normal time push to mobile terminal.
Therefore, the present invention can not only save mobile terminal and re-establish with service end the time be connected, save power and flow, and reliably by message push to mobile terminal, be convenient to people and use.
(2) HTTP POST request of the present invention also comprises coupling ID, service end is according to after message subject determination mobile terminal, can according to the particular message (namely carrying out Secondary Match to message) under coupling ID exact matching mobile terminal subscribe message theme, and then realize fine-grained subscription, reduce the data transmission information amount of mobile terminal and service end, reduce use cost.
Accompanying drawing explanation
Fig. 1 is the flow chart based on the Mobile solution information push method of HTTP in the embodiment of the present invention;
Fig. 2 is the sequential chart of the communication process of mobile terminal and service end in the embodiment of the present invention;
Fig. 3 is the flow chart of step S4 in the embodiment of the present invention;
Fig. 4 is the connection block diagram based on the Mobile solution message push system of HTTP in the embodiment of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the present invention is described in further detail.
Shown in Figure 1, the Mobile solution information push method based on HTTP in the embodiment of the present invention, service end uses SSE (Server-Sent Events, HTML5 server sends event), and technology is to mobile terminal PUSH message, and the method comprises the following steps:
S1: message is divided into some message subjects by service end, some dissimilar message is included in each message subject, every bar message is all configured with coupling ID (coupling ID can be the ID of message particular type, can also be the ID of certain resource of message relating), forwards step S2 to.
S2: mobile terminal sends HTTP POST to service end and asks (the important request in http protocol, update request is sent to destination server, and with request entity), HTTPPOST request comprises message subject, type of message, message sequence number and coupling ID, mobile terminal subscribes to the message meeting HTTP POST and ask to service end, forward step S3 to.
S3: service end timing pushes heartbeat message to the mobile terminal subscribed to, and mobile terminal judges whether heartbeat message receives successfully, if so, forwards step S4 to, otherwise re-executes step S2.
S4: after service end produces the message of message subject and the coupling ID meeting mobile terminal subscription, service end uses JSON form (JavaScript Object Notation, the data interchange format of lightweight) by a message sequence, service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S5 to.
S5: after service end sends a message to mobile terminal at every turn, all judges whether mobile terminal receives message, if so, forwards step S7 to, otherwise forwards step S6 to.
S6: the message do not pushed is formed persistence buffer queue by service end, and mobile terminal records receives the sequence number of last message; Mobile terminal re-establishes with service end and is connected, and mobile terminal subscribes to the message after last message sequence number, and service end is taken out message and pushed from persistence buffer queue, re-executes step S5.
S7: the message received is carried out unserializing and processing messages by mobile terminal; Judge whether mobile terminal removes subscription, if so, service end removes mobile terminal subscription information, terminates, otherwise forwards step S4 to.
The communication process of mobile terminal of the present invention and service end is illustrated below by 1 embodiment.
Shown in Figure 2, mobile terminal is to service end subscribe message, and the sequence number of message is 0,1,2 and 3, and service end is to mobile terminal PUSH message, and pushing successful message sequence number is 0 and 1, and pushing failure sequence number is 2.The message of sequence number 2 and 3 is formed persistence buffer queue by service end, and after client is subscribed to again, service end is taken out and PUSH message 2 and 3 to mobile terminal from persistence buffer queue, and mobile terminal removes subscription after receiving message 2 and 3.
Shown in Figure 3, step S4 specifically comprises the following steps:
S401: service end inquires about the mobile terminal of all subscription current messages after producing message according to message subject, service end travels through all mobile terminals subscribing to current message, forwards step S402 to.
S402: judge successively the coupling ID of all mobile terminals whether meet current message theme under the coupling ID of all message, if so, then determine that mobile terminal subscribes to all message under current message theme, forward step S404 to, otherwise forward step S403 to.
S403: judge whether the coupling ID of current mobile terminal meets the coupling ID of current message, if so, forwards step S404 to, otherwise forward step S405 to.
S404: service end uses JSON form by current message serializing, and service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S405 to.
S405: judge whether service end completes all mobile terminal traversals, and if so, step S4 terminates, and forwards step S5 to; Otherwise continue to perform step S402.
Message subject in step S1 is used for mark and organizes a certain class particular message, and message subject is a readable character string.
Heartbeat message in step S3 is the built-in message of mobile terminal.
Step S6 is further comprising the steps of: if service end produces new information and the not yet successful connection of service end and mobile terminal, current new information is put into persistence buffer queue and carried out label by continuous numeric order by service end.
Realize the Mobile solution message push system based on HTTP of said method in the embodiment of the present invention, comprise the subscribing module and message reception module that are positioned at mobile terminal, be positioned at the message subject administration module of service end, subscription management module and application module.
Subscribing module is used for: when mobile terminal needs subscribe message, sends HTTPPOST request to service end; When mobile terminal does not receive heartbeat message, control mobile terminal and continue to send HTTP POST request to service end.
Subscription management module is used for: when mobile terminal subscribe message, keeps being connected with buffer memory HTTP, the information of record move terminal subscribes; When mobile terminal removes subscription, close HTTP and connect and remove mobile terminal subscription information; When PUSH message failure (mobile terminal does not receive the message that service end sends), the message do not pushed is formed persistence buffer queue.
Application module is used for: after producing message, send the message push request of corresponding theme to message subject administration module.
Message subject administration module is used for: after receiving the message push request of corresponding theme, and by defining the coupling ID of theme message structure and message, the agreement that mobile terminal and service end are reached an agreement also carries out message push; The information of the mobile terminal of record subscribe message theme, for needing the continuous sequence number of all message markings being sent to mobile terminal.
Message reception module is used for: receive the message that service end pushes, message is carried out unserializing and processing messages.
The present invention is not limited to above-mentioned execution mode, and for those skilled in the art, under the premise without departing from the principles of the invention, can also make some improvements and modifications, these improvements and modifications are also considered as within protection scope of the present invention.The content be not described in detail in this specification belongs to the known prior art of professional and technical personnel in the field.
Claims (9)
1., based on a Mobile solution information push method of HTTP, it is characterized in that, the method comprises the following steps:
S1: message is divided into some message subjects by service end, includes some dissimilar message in each message subject, every bar message is all configured with coupling ID, forwards step S2 to;
S2: mobile terminal sends HTTP POST request to service end, HTTP POST request comprises message subject, type of message, message sequence number and coupling ID, and mobile terminal subscribes to the message meeting HTTP POST and ask to service end, forward step S3 to;
S3: service end timing pushes heartbeat message to the mobile terminal subscribed to, and mobile terminal judges whether heartbeat message receives successfully, if so, forwards step S4 to, otherwise re-executes step S2;
S4: after service end produces the message of message subject and the coupling ID meeting mobile terminal subscription, service end is by message sequence, and service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S5 to;
S5: after service end sends a message to mobile terminal at every turn, all judges whether mobile terminal receives message, if so, forwards step S7 to, otherwise forwards step S6 to;
S6: the message do not pushed is formed persistence buffer queue by service end, and mobile terminal records receives the sequence number of last message; Mobile terminal re-establishes with service end and is connected, and mobile terminal subscribes to the message after last message sequence number, and service end is taken out message and pushed from persistence buffer queue, re-executes step S5;
S7: the message received is carried out unserializing and processing messages by mobile terminal.
2., as claimed in claim 1 based on the Mobile solution information push method of HTTP, it is characterized in that, step S4 specifically comprises the following steps:
S401: service end inquires about the mobile terminal of all subscription current messages after producing message according to message subject, service end travels through all mobile terminals subscribing to current message, forwards step S402 to;
S402: judge successively the coupling ID of all mobile terminals whether meet current message theme under the coupling ID of all message, if so, forward step S404 to, otherwise forward step S403 to;
S403: judge whether the coupling ID of current mobile terminal meets the coupling ID of current message, if so, forwards step S404 to, otherwise forward step S405 to;
S404: service end is by current message serializing, and service end is the continuous sequence number of all message markings needing to be sent to mobile terminal; All message is sent to mobile terminal by corresponding HTTP connection by service end, forwards step S405 to;
S405: judge whether service end completes all mobile terminal traversals, and if so, step S4 terminates, and forwards step S5 to; Otherwise continue to perform step S402.
3. as claimed in claim 1 based on the Mobile solution information push method of HTTP, it is characterized in that: message subject described in step S1 is used for mark and organizes particular message, and message subject is a readable character string.
4. as claimed in claim 1 based on the Mobile solution information push method of HTTP, it is characterized in that: the ID mating ID that ID is message particular type or message relating resource described in step S1.
5., as claimed in claim 1 based on the Mobile solution information push method of HTTP, it is characterized in that: heartbeat message described in step S3 is the built-in message of mobile terminal.
6. as claimed in claim 1 based on the Mobile solution information push method of HTTP, it is characterized in that: service end described in step S4 uses the exchanges data JSON form of lightweight by message sequence.
7. the Mobile solution information push method based on HTTP as described in any one of claim 1 to 6, it is characterized in that, step S6 is further comprising the steps of: if service end produces new information and the not yet successful connection of service end and mobile terminal, current new information is put into persistence buffer queue and carried out label by continuous numeric order by service end.
8. the Mobile solution information push method based on HTTP as described in any one of claim 1 to 6, it is characterized in that: the message received is carried out unserializing and after processing messages by mobile terminal described in step S7, further comprising the steps of: to judge whether mobile terminal removes subscription, if, service end removes mobile terminal subscription information, terminate, otherwise forward step S4 to.
9. one kind realizes the Mobile solution message push system based on HTTP of method described in any one of claim 1 to 8, it is characterized in that: this system comprises the subscribing module and message reception module that are positioned at mobile terminal, be positioned at the message subject administration module of service end, subscription management module and application module;
Described subscribing module is used for: when mobile terminal needs subscribe message, sends HTTP POST request to service end; When mobile terminal does not receive heartbeat message, control mobile terminal and continue to send HTTP POST request to service end;
Described subscription management module is used for: when mobile terminal subscribe message, keeps being connected with buffer memory HTTP, the information of record move terminal subscribes; When mobile terminal removes subscription, close HTTP and connect and remove mobile terminal subscription information; When PUSH message failure, the message do not pushed is formed persistence buffer queue;
Described application module is used for: after producing message, send the message push request of corresponding theme to message subject administration module;
Described message subject administration module is used for: after receiving the message push request of corresponding theme, and by defining the coupling ID of theme message structure and message, the agreement that mobile terminal and service end are reached an agreement also carries out message push; The information of the mobile terminal of record subscribe message theme, for needing the continuous sequence number of all message markings being sent to mobile terminal;
Described message reception module is used for: receive the message that service end pushes, message is carried out unserializing and processing messages.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510108911.0A CN104660708B (en) | 2015-03-13 | 2015-03-13 | A kind of Mobile solution information push method and system based on HTTP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510108911.0A CN104660708B (en) | 2015-03-13 | 2015-03-13 | A kind of Mobile solution information push method and system based on HTTP |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104660708A true CN104660708A (en) | 2015-05-27 |
| CN104660708B CN104660708B (en) | 2018-01-12 |
Family
ID=53251395
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510108911.0A Expired - Fee Related CN104660708B (en) | 2015-03-13 | 2015-03-13 | A kind of Mobile solution information push method and system based on HTTP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104660708B (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105847063A (en) * | 2016-05-12 | 2016-08-10 | 中国联合网络通信集团有限公司 | Core network data management method and system |
| CN106230922A (en) * | 2016-07-28 | 2016-12-14 | 上海斐讯数据通信技术有限公司 | A kind of news subscribing method, message production unit and message reception units |
| CN106254439A (en) * | 2016-07-29 | 2016-12-21 | 努比亚技术有限公司 | A kind of method for pushing, device and a kind of mobile device management system |
| CN106911795A (en) * | 2017-03-27 | 2017-06-30 | 努比亚技术有限公司 | A kind of data request processing device and method |
| CN107046582A (en) * | 2017-05-23 | 2017-08-15 | 网易乐得科技有限公司 | Message prompt method, medium, device and the computing device of e-sourcing information |
| CN107181821A (en) * | 2017-07-05 | 2017-09-19 | 广州华多网络科技有限公司 | A kind of information push method and device based on SSE specifications |
| WO2017167020A1 (en) * | 2016-03-28 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Configuration information push method and device |
| CN107295003A (en) * | 2017-07-17 | 2017-10-24 | 联动优势科技有限公司 | A kind of data transmission method, apparatus and system |
| CN107733778A (en) * | 2017-08-18 | 2018-02-23 | 深圳市艾特智能科技有限公司 | Message treatment method, system, storage medium and computer equipment |
| CN108306852A (en) * | 2017-12-05 | 2018-07-20 | 上海金融期货信息技术有限公司 | A kind of message-oriented middleware system and method based on simple binary coding |
| CN109889513A (en) * | 2019-02-02 | 2019-06-14 | 上海市共进通信技术有限公司 | Realize the method that communication control is carried out between fusion device internal gateway and the end OTT |
| CN110086883A (en) * | 2019-05-08 | 2019-08-02 | 福州福昕网络技术有限责任公司 | A kind of information push method and system for windows platform |
| CN110730373A (en) * | 2019-12-18 | 2020-01-24 | 南京创维信息技术研究院有限公司 | Method and system for pushing videos across screens among devices with screens |
| CN110740195A (en) * | 2019-11-20 | 2020-01-31 | 山东鲁能软件技术有限公司 | distributed system data synchronization method and system based on message engine |
| CN112787993A (en) * | 2020-12-25 | 2021-05-11 | 北京金万维科技有限公司 | High-concurrency HTTP request caching and content pushing system and method based on UDP |
| CN114915659A (en) * | 2021-02-09 | 2022-08-16 | 腾讯科技（深圳）有限公司 | Network request processing method and device, electronic equipment and storage medium |
| CN115225696A (en) * | 2022-07-08 | 2022-10-21 | 北京天融信网络安全技术有限公司 | Remote data interaction method and device |
| CN118101751A (en) * | 2024-02-28 | 2024-05-28 | 广东柠檬火互联网科技有限公司 | Message pushing method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090292766A1 (en) * | 2006-02-01 | 2009-11-26 | Morris Robert P | HTTP Publish/Subscribe Communication Protocol |
| CN103686628A (en) * | 2012-09-17 | 2014-03-26 | 中国移动通信集团公司 | Information pushing method, system, network equipment, and mobile terminal |
| CN103916442A (en) * | 2013-01-07 | 2014-07-09 | 阿里巴巴集团控股有限公司 | Message pushing achieving method, mobile terminal and message pushing system |
-
2015
- 2015-03-13 CN CN201510108911.0A patent/CN104660708B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090292766A1 (en) * | 2006-02-01 | 2009-11-26 | Morris Robert P | HTTP Publish/Subscribe Communication Protocol |
| CN103686628A (en) * | 2012-09-17 | 2014-03-26 | 中国移动通信集团公司 | Information pushing method, system, network equipment, and mobile terminal |
| CN103916442A (en) * | 2013-01-07 | 2014-07-09 | 阿里巴巴集团控股有限公司 | Message pushing achieving method, mobile terminal and message pushing system |
Non-Patent Citations (1)
| Title |
|---|
| 廖清平: ""基于Web的服务器的Push技术研究和应用"", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017167020A1 (en) * | 2016-03-28 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Configuration information push method and device |
| CN107241204A (en) * | 2016-03-28 | 2017-10-10 | 阿里巴巴集团控股有限公司 | Configuration information method for pushing and device |
| CN105847063A (en) * | 2016-05-12 | 2016-08-10 | 中国联合网络通信集团有限公司 | Core network data management method and system |
| CN106230922A (en) * | 2016-07-28 | 2016-12-14 | 上海斐讯数据通信技术有限公司 | A kind of news subscribing method, message production unit and message reception units |
| CN106254439A (en) * | 2016-07-29 | 2016-12-21 | 努比亚技术有限公司 | A kind of method for pushing, device and a kind of mobile device management system |
| CN106911795A (en) * | 2017-03-27 | 2017-06-30 | 努比亚技术有限公司 | A kind of data request processing device and method |
| CN107046582A (en) * | 2017-05-23 | 2017-08-15 | 网易乐得科技有限公司 | Message prompt method, medium, device and the computing device of e-sourcing information |
| CN107181821A (en) * | 2017-07-05 | 2017-09-19 | 广州华多网络科技有限公司 | A kind of information push method and device based on SSE specifications |
| CN107295003A (en) * | 2017-07-17 | 2017-10-24 | 联动优势科技有限公司 | A kind of data transmission method, apparatus and system |
| CN107733778A (en) * | 2017-08-18 | 2018-02-23 | 深圳市艾特智能科技有限公司 | Message treatment method, system, storage medium and computer equipment |
| CN108306852A (en) * | 2017-12-05 | 2018-07-20 | 上海金融期货信息技术有限公司 | A kind of message-oriented middleware system and method based on simple binary coding |
| CN108306852B (en) * | 2017-12-05 | 2020-12-04 | 上海金融期货信息技术有限公司 | Message middleware system and method based on simple binary coding |
| CN109889513A (en) * | 2019-02-02 | 2019-06-14 | 上海市共进通信技术有限公司 | Realize the method that communication control is carried out between fusion device internal gateway and the end OTT |
| CN110086883A (en) * | 2019-05-08 | 2019-08-02 | 福州福昕网络技术有限责任公司 | A kind of information push method and system for windows platform |
| CN110740195A (en) * | 2019-11-20 | 2020-01-31 | 山东鲁能软件技术有限公司 | distributed system data synchronization method and system based on message engine |
| CN110740195B (en) * | 2019-11-20 | 2022-05-20 | 山东鲁能软件技术有限公司 | Distributed system data synchronization method and system based on message engine |
| CN110730373A (en) * | 2019-12-18 | 2020-01-24 | 南京创维信息技术研究院有限公司 | Method and system for pushing videos across screens among devices with screens |
| CN112787993A (en) * | 2020-12-25 | 2021-05-11 | 北京金万维科技有限公司 | High-concurrency HTTP request caching and content pushing system and method based on UDP |
| CN114915659A (en) * | 2021-02-09 | 2022-08-16 | 腾讯科技（深圳）有限公司 | Network request processing method and device, electronic equipment and storage medium |
| CN114915659B (en) * | 2021-02-09 | 2024-03-26 | 腾讯科技（深圳）有限公司 | Network request processing method and device, electronic equipment and storage medium |
| CN115225696A (en) * | 2022-07-08 | 2022-10-21 | 北京天融信网络安全技术有限公司 | Remote data interaction method and device |
| CN118101751A (en) * | 2024-02-28 | 2024-05-28 | 广东柠檬火互联网科技有限公司 | Message pushing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104660708B (en) | 2018-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104660708A (en) | HTTP (Hyper Text Transfer Protocol) based mobile application message forwarding method and system | |
| CN106059848B (en) | Electric power data acquisition transmission process system and method based on Big Dipper short message communication | |
| CN102739560B (en) | Instant communication method, system and device | |
| CN105991412B (en) | Information push method and device | |
| CN103096271A (en) | Information pushing system and information pushing method | |
| CN109327493A (en) | A kind of remote medical monitoring system based on cloud and monitoring method | |
| CN109246172A (en) | A kind of method, apparatus and computer storage medium for restoring session | |
| CN107426233A (en) | Data communication system, method, Web server and monitoring system based on B/S frameworks | |
| CN107360177B (en) | A kind of message transmitting method and device based on UDP | |
| CN107342934A (en) | A kind of mixed mode Mobile solution real-time messages method for pushing and system based on WebSocket | |
| CN103516588A (en) | Method and system of background processing of client-side | |
| CN108683653A (en) | A kind of active message push system based on WebSocket | |
| CN109040017B (en) | Intelligent customer service system based on MQTT and HTTP and implementation method | |
| EP2913977A2 (en) | Resource information acquisition method, system and device for internet of things terminal device | |
| CN114157537A (en) | System and method for realizing multi-source heterogeneous data access by general equipment gateway | |
| CN103546771A (en) | Television program review processing method and system based on smart terminal | |
| CN103516766B (en) | Method and system of communication between client-side and application server | |
| US20160285576A1 (en) | Gateway for interconnection of heterogeneous middleware and time synchronization method thereof | |
| CN116668977A (en) | Power distribution network safety information management and control method and platform | |
| CN117615043B (en) | Inter-service communication method and system on edge gateway | |
| CN110913453A (en) | Communication method, communication device, computer readable medium and electronic equipment | |
| CN106888431A (en) | The method and system of good friend are added on a kind of intelligent watch | |
| CN104937905B (en) | For managing the mechanism of communication session | |
| CN108632136A (en) | Patrol river data processing method and device | |
| CN102497306B (en) | A kind of distribution substation realizes the method and system of transfer of data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20180112 Termination date: 20190313 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |