CN102904962A - Message pushing system and message pushing method thereof - Google Patents
Message pushing system and message pushing method thereof Download PDFInfo
- Publication number
- CN102904962A CN102904962A CN2012104084469A CN201210408446A CN102904962A CN 102904962 A CN102904962 A CN 102904962A CN 2012104084469 A CN2012104084469 A CN 2012104084469A CN 201210408446 A CN201210408446 A CN 201210408446A CN 102904962 A CN102904962 A CN 102904962A
- Authority
- CN
- China
- Prior art keywords
- message
- client
- module
- server
- described client
- 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
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention relates to a message pushing system which comprises a client and a server, wherein the client comprises a first communication module which is used for generating an identification number of the client, setting message subscribing types and transmitting the message subscribing types to the server; and the server comprises a second communication module and a monitoring module, wherein the second communication module is used for receiving the identification number of the client and the message subscribing types and generating a client proxy object, and the monitoring module is used for monitoring messages. The first communication module transmits a message request, the second communication module receives the message request, updates the time of connection with the client and returns the messages to the client according to the message request when the messages are monitored by the monitoring module, and the first communication module receives the messages, parses the messages and controls page display. The message pushing system disclosed by the invention has the advantage that the messages of the server can be displayed at the client in time.
Description
Technical field
The present invention relates to network service, relate in particular to the method for a kind of message push system and message push thereof.
Background technology
The working method that the WEB of traditional mode uses is as follows:
The user sends request to browser;
Browser sends to server with request;
The request of server response browser returns to browser with data after the processing;
Browser is received response data, shows the result after resolving.
This traditional mode of operation only has the user to send on one's own initiative request, and browser end just can obtain the renewal of server end.And in the application of a lot of reality, the renewal of server end need to immediately be embodied in browser end, such as instant messaging, and Real Time Monitoring etc.Take instant messaging as example, other users' login is published, and the change of state sends message etc., and browser need to reflect these variations of server end in real time.The mode of traditional user's active request obviously can't satisfy the demand of this reality.
In the prior art, often adopt following scheme to solve:
1、Flash?XMLSocket
Implementation method: in html page, embed a Flash program of using the XMLSocket class.JavaScript communicates by the socket that calls this Flash program and provide and the socket of server end.JavaScript resolves the return data of the XML form of receiving server end, the displaying contents of control html page.
The shortcoming of this scheme: client must be installed Flash player plug-in unit; XMLSocket does not have the HTTP tunnelling function, may be stoped by fire compartment wall.
2, the stream of Iframe and htmlfile (streaming) mode
Implementation method: in html page, embed a concealment frames (Iframe), the src attribute of this concealment frames is made as request to a long connection, server end returns the calling of browser end JavaScript function, and the JavaScript engine of browser end is receiving that JavaScript that server returns will run time version when calling.
The shortcoming of this scheme: the progress bar of browser can not finished in the display page loading, and the figure rotating savings of IE top is ceaselessly rotated.
3, WebSocket mode
HTML has introduced the WebSocket interface and has defined the communication port of a full duplex, at the enterprising line operate of WEB, supports the page to use the WebSocket agreement to carry out communicating by letter of full duplex with server by a single socket.
The shortcoming of this scheme: different browsers is variant to supporting dynamics and the specific implementation of HTML5, and the IE browser is not supported these new technologies.
Summary of the invention
In view of this, be necessary to provide the method for a kind of message push system and message push thereof, to be implemented in the upper data variation that in time embodies server (backstage) of client (browser).
Message push system provided by the invention, comprise client and server, wherein: client comprises: first communication module, for the identification number that generates described client, the type of subscribe message is set, and the identification number of described client and the type of subscribe message are sent to described server; Described server comprises: second communication module is used for receiving the identification number of described client and the type of subscribe message, and generates the Client Agent object according to the identification number of described client and the type of subscribe message; Monitor module, be used for monitoring information; Wherein said first communication module also is used for sending message request, described second communication module also is used for receiving described message request, and the connect hours of renewal and described client, described second communication module returns described message to described client according to described message request when described monitoring module listens to message, described first communication module also is used for receiving described message, and resolve described message, the control page shows.
It is client push message that the method for message push provided by the invention is used for server, comprising: described client generates the identification number of client, the type of subscribe message is set, and sends the identification number of described client, and the type of subscribe message is set; Described server receives the identification number of described client, and the type of subscribe message is set, and according to the identification number of described client, the type that subscribe message is set creates the Client Agent object; Described server monitoring information; Described client sends message request; Described server receives described message request, and the connect hours of renewal and described client; Whether listen to message; If then return described message to described client; The described message of described client, and resolve described message, the control page shows.
Message push system in the embodiment of the present invention and the method for message push thereof have realized that the message of server in time shows in client.
Description of drawings
Fig. 1 is the modular structure figure of message push system in an embodiment of the present invention;
Fig. 2 sets up the flow chart of monitoring in the information push method in an embodiment of the present invention;
Fig. 3 is the flow chart that client detects and reconnects in the information push method in an embodiment of the present invention;
Fig. 4 is the flow chart of server return messages in the information push method in an embodiment of the present invention.
Fig. 5 is the flow chart that client cancels subscriptions in the information push method in an embodiment of the present invention;
Fig. 6 is the flow chart of server cleaning Client Agent object in the information push method in an embodiment of the present invention;
Fig. 7 is the flow chart of message push in an embodiment of the present invention.
Embodiment
The below describes embodiments of the invention in detail, and the example of described embodiment is shown in the drawings, and wherein identical or similar label represents identical or similar element or the element with identical or similar functions from start to finish.Be exemplary below by the embodiment that is described with reference to the drawings, only be used for explaining the present invention, and can not be interpreted as limitation of the present invention.
In description of the invention, term " interior ", " outward ", " vertically ", " laterally ", " on ", orientation or the position relationship of the indications such as D score, " top ", " end " be based on orientation shown in the drawings or position relationship, only be for convenience of description the present invention rather than require the present invention with specific orientation structure and operation, therefore can not be interpreted as limitation of the present invention.
See also Fig. 1, Figure 1 shows that the modular structure figure of message push system in an embodiment of the present invention.
In the present embodiment, message push system is comprised of client 10, server 20 and network (not shown).
In the present embodiment, client 10 comprises: first communication module 110, counting module 120, the first timing module 130 and the first judge module 140.
In the present embodiment, server 20 comprises: second communication module 210, monitoring module 220, the second judge module 230 and the second timing module 240.
In the present embodiment, first communication module 110 for the identification number that generates described client 10, arranges the type of subscribe message, and the identification number of described client 10 and the type of subscribe message is sent to described server 20.
Monitor module 220 and be used for monitoring information.In the present embodiment, the type of message of monitoring module 220 monitorings is the type of subscribe message.
In the present embodiment, first communication module 110 also is used for sending message request, and second communication module 210 also is used for receiving described message request, and the connect hours of renewal and described client 10.
In the present embodiment, second communication module 210 returns described message to described client 10 according to described message request when described monitoring module 220 listens to message, described first communication module 110 also is used for receiving described message, and resolves described message, and the control page shows.
In the present embodiment, counting module 120 is used for when described first communication module 110 receives described message expired times are set to " 0 ".
The first timing module 130 is used for beginning when described first communication module 110 sends described message request timing.
In the present embodiment, the first timing module 130 stops timing and stop timing when timing time is overtime when first communication module 110 is received the message of returning.
The first judge module 140 is used for judging whether 130 timing of described the first timing module are overtime, wherein, described counting module 120 also is used in described the first timing module 130 record expired times when overtime, described the first judge module 140 is used for also whether judging described expired times greater than the max-timeout number of times that described first communication module 110 enters when also being used in described expired times greater than the max-timeout number of times and connects the stage that reconnects of detecting.
In the present embodiment, described the first judge module 110 also is used for judging whether to finish to subscribe to, and described monitoring module 220 cancellation message after finishing subscription is monitored, and clears up described Client Agent object.
In the present embodiment, the second judge module 230 is used for judging whether described monitoring module 220 listens to message, when wherein said monitoring module 220 listens to message described message request is not hung up.
The second timing module 240 is used for recording the suspension time of described message request, wherein, described the second judge module 230 is used for also judging whether the suspension time of described message request surpasses the set time, and described second communication module 210 returns null message to described client 10 when described suspension time surpasses the set time.
In the present embodiment, described the second timing module 240 also connects the time of described client 10 with the described Client Agent object of record.
In the present embodiment, described the second judge module 230 is used for also judging whether described Client Agent object connects time of described client 10 overtime, described monitoring module 220 also be used for described Client Agent object connect 10 times of described client when overtime cancellation message monitor, clear up described Client Agent object.
See also Fig. 2, Figure 2 shows that and set up the flow chart of monitoring in an embodiment of the present invention in the information push method.
In the present embodiment, at step S100, described client 10 generates the identification number of client 10, and the type of subscribe message is set, and passes through the identification number that first communication module 110 sends described client 10, and the type of subscribe message is set.
At step S102, described server 20 receives the identification number of described client 10, and the type of subscribe message is set, and according to the identification number of described client 10, the type that subscribe message is set creates the Client Agent object.
See also Fig. 3, Figure 3 shows that the flow chart that client detects and reconnects in the information push method in an embodiment of the present invention.
At step S200, the first communication module 110 of client 10 sends message request.
At step S201, the first timer 130 beginning timing of client 10.
In the present embodiment, the first timing module 130 stops timing and stop timing when timing time is overtime when first communication module 110 is received the message of returning.
At step S202, the first judge module 140 of client 10 judges whether 130 timing of described the first timing module are overtime.In the present embodiment, if be overtime when the first timing module 130 timing times surpass 25 milliseconds, in other execution modes of the present invention, also can be set as timing is overtime above 20 milliseconds or 30 milliseconds.
If 130 timing of the first timing module are overtime, at step S204, the counting module 120 record expired times of client 10.
At step S206, the first judge module 140 of client 10 judges that whether described expired times are greater than the max-timeout number of times.In the present embodiment, the max-timeout number of times is 3 times.
If described expired times are greater than the max-timeout number of times, at step S208, client 10 enters to connect to detect and reconnects the stage, then enters step S210.
If described expired times are not more than the max-timeout number of times, then at step S210, the first judge module 140 of client 10 judges whether to finish to subscribe to.
If client 10 finishes to subscribe to, then at step S212, client 10 is closed connection, cancels subscriptions.
At step S214, the monitoring module 220 of server 20 is cleared up described Client Agent object finishing to subscribe to the monitoring of rear cancellation message.
If client 10 does not finish to subscribe to, then at step S216, client 10 continues to keep connecting.
See also Fig. 4, Figure 4 shows that in an embodiment of the present invention the flow chart of server 20 return messages in the information push method.
In the present embodiment, at step S300, the second communication module 210 receipt message requests of server 20, and the connect hours of renewal and described client 10.
At step S302, the second judge module 230 of server 20 judges whether monitor module 220 listens to message.
Listen to message if monitor module 230, then at step S304, second communication module 210 returns described message to described client 10.
At step S306, the first communication module 110 of described client 10 receives described message, and resolves described message, and the control page shows.
Do not listen to message if monitor module 230, then at step S306, monitor module 220 and hang up described message request.
At step S308, the suspension time of the described message request of the second timing module 240 records of server 20, the second judge module 230 of server 20 judges whether the suspension time of described message request surpasses the set time.
If described suspension time surpasses the set time, then at step S310, the second communication module 210 of server 20 returns null message to described client 10.
See also Fig. 5, Figure 5 shows that the flow chart that client 10 cancels subscriptions in the information push method in an embodiment of the present invention.
At step S400, client 10 receives the message of returning, and counting module 130 is set to expired times " 0 ".
At step S402, client 10 is resolved the message of returning, and the control page shows.
At step S404, the first judge module 140 of client 10 judges whether to finish to subscribe to.
If client 10 finishes to subscribe to, then at step S406, client 10 is closed connection, cancels subscriptions.
At step S408, the monitoring module 220 of server 20 is cleared up described Client Agent object finishing to subscribe to the monitoring of rear cancellation message.
If client 10 does not finish to subscribe to, then at step S410, client 10 continues to keep connecting, and sends message request.
See also Fig. 6, Figure 6 shows that in an embodiment of the present invention the flow chart of server 20 cleaning Client Agent objects in the information push method.
At step S500, the described Client Agent object of the second timing module 240 records of server 20 connects the time of described client 10.
At step S502, server 20 judges whether described Client Agent object connects time of described client 10 overtime.Be overtime when in the present embodiment, described Client Agent object time of connecting described client 10 surpasses 80～100 milliseconds.
If it is overtime that the Client Agent object connects the time of described client 10, then at step S504, described server 20 cancellation message are monitored, and clear up described Client Agent object.
See also Fig. 7, Figure 7 shows that the flow chart of message push in an embodiment of the present invention.
A, client 10 are initiated message request;
B, server 20 are received message request, and whether check has message.If there is not message, then message on hold request;
If C has message, return messages are to client 10 immediately;
D, in the process that message request is suspended, arrive if any new information, then wakeup message request, return messages are to client 10;
E, server 20 are not received new information in time-out time, return null message to client 10;
F, client 10 are initiated next time message request after receiving the message of returning of server 20;
After G, server 20 once connect, receive that next time if new information is arranged that message is temporary, one has message request by the time, just this message is back to client 10 before the message request on closing.
Message push system in the embodiment of the present invention and the method for message push thereof, the message that has realized server 20 in time shows in client 10, and when cancelling subscriptions or client 10 is long-time when not being connected with server 20, cancellation message is monitored, in time clear up the Client Agent object, reduced the load of server 20.
Although the present invention is described with reference to current preferred embodiments; but those skilled in the art will be understood that; above-mentioned preferred embodiments only is used for illustrating the present invention; be not to limit protection scope of the present invention; any within the spirit and principles in the present invention scope; any modification of doing, equivalence replacement, improvement etc. all should be included within the scope of the present invention.
Claims (12)
1. a message push system comprises client and server, wherein:
Client comprises: first communication module for the identification number that generates described client, arranges the type of subscribe message, and the identification number of described client and the type of subscribe message is sent to described server;
Described server comprises: second communication module is used for receiving the identification number of described client and the type of subscribe message, and generates the Client Agent object according to the identification number of described client and the type of subscribe message;
Monitor module, be used for monitoring information;
Wherein said first communication module also is used for sending message request, described second communication module also is used for receiving described message request, and the connect hours of renewal and described client, described second communication module returns described message to described client according to described message request when described monitoring module listens to message, described first communication module also is used for receiving described message, and resolve described message, the control page shows.
2. message push system as claimed in claim 1 is characterized in that, described client also comprises:
Counting module is used for when described first communication module receives described message expired times are set to " 0 ";
The first timing module is used for beginning when described first communication module sends described message request timing;
The first judge module, be used for judging whether described the first timing module timing is overtime, wherein, described counting module also is used in the overtime time record expired times of described the first timing module, described the first judge module is used for also whether judging described expired times greater than the max-timeout number of times that described first communication module enters when also being used in described expired times greater than the max-timeout number of times and connects the stage that reconnects of detecting.
3. message push system as claimed in claim 1 is characterized in that, described the first judge module also is used for judging whether to finish to subscribe to, and described monitoring module cancellation message after finishing subscription is monitored, and clears up described Client Agent object.
4. message push system as claimed in claim 1 is characterized in that, described server also comprises:
The second judge module is used for judging whether described monitoring module listens to message, when wherein said monitoring module listens to message described message request is not hung up;
The second timing module, be used for recording the suspension time of described message request, wherein, described the second judge module is used for also judging whether the suspension time of described message request surpasses the set time, and described second communication module returns null message to described client when described suspension time surpasses the set time.
5. message push system as claimed in claim 4 is characterized in that, described the second timing module also connects the time of described client with the described Client Agent object of record.
6. message push system as claimed in claim 5, it is characterized in that, described the second judge module is used for also judging whether described Client Agent object connects time of described client overtime, described monitoring module also is used for when overtime in the time that described Client Agent object connects described client cancellation message to be monitored, and clears up described Client Agent object.
7. the method for a message push is client push message for server, comprising:
Described client generates the identification number of client, the type of subscribe message is set, and sends the identification number of described client, and the type of subscribe message is set;
Described server receives the identification number of described client, and the type of subscribe message is set, and according to the identification number of described client, the type that subscribe message is set creates the Client Agent object;
Described server monitoring information;
Described client sends message request;
Described server receives described message request, and the connect hours of renewal and described client; Whether listen to message;
If then return described message to described client;
The described message of described client, and resolve described message, the control page shows.
8. the method for message push as claimed in claim 7 is characterized in that, also comprises:
The time that the described message request of described client records sends;
Described client judges whether described message request is overtime;
If, described client records expired times then;
Described client judges that whether described expired times are greater than fixed value;
If then described client enters and connects the stage that reconnects of detecting.
9. the method for message push as claimed in claim 1 is characterized in that, also comprises:
Described client judges whether to finish to subscribe to;
If then described server is cleared up described Client Agent object finishing to subscribe to the monitoring of rear cancellation message.
10. the method for message push as claimed in claim 7 is characterized in that, also comprises:
Described server judges whether to listen to message;
If do not listen to message, then described server is hung up described message request;
The suspension time of the described message request of described server record;
Described server judges whether the suspension time of described message request surpasses the set time;
If described suspension time surpasses the set time, then described server returns null message to described client.
11. the method for message push as claimed in claim 10 is characterized in that, also comprises:
The described Client Agent object of described server record connects the time of described client.
12. the method for message push as claimed in claim 11 is characterized in that, also comprises:
Described server judges whether described Client Agent object connects time of described client overtime;
If the time that described Client Agent object connects described client is overtime, then described server cancellation message is monitored, and clears up described Client Agent object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012104084469A CN102904962A (en) | 2012-10-23 | 2012-10-23 | Message pushing system and message pushing method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012104084469A CN102904962A (en) | 2012-10-23 | 2012-10-23 | Message pushing system and message pushing method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102904962A true CN102904962A (en) | 2013-01-30 |
Family
ID=47576997
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012104084469A Pending CN102904962A (en) | 2012-10-23 | 2012-10-23 | Message pushing system and message pushing method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102904962A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105656971A (en) * | 2014-11-24 | 2016-06-08 | 中国移动通信集团公司 | Method, device and system for building message subscription relation between nodes |
| CN105825409A (en) * | 2015-01-07 | 2016-08-03 | 航天信息股份有限公司 | System and method of pushing electronic invoice message |
| CN106162367A (en) * | 2015-04-21 | 2016-11-23 | 广州市动景计算机科技有限公司 | A kind of video broadcasting method and device |
| CN106534253A (en) * | 2016-09-27 | 2017-03-22 | 山东浪潮商用系统有限公司 | On-line chatting method and on-line chatting device |
| CN106572146A (en) * | 2015-10-13 | 2017-04-19 | 腾讯科技（深圳）有限公司 | Message sending method and message sending device |
| CN107888683A (en) * | 2017-11-10 | 2018-04-06 | 郑州云海信息技术有限公司 | A kind of client exchange method and device |
| CN108881395A (en) * | 2018-05-23 | 2018-11-23 | 北京五八信息技术有限公司 | Information push method, equipment, message manager and computer readable storage medium |
| CN110321140A (en) * | 2019-05-23 | 2019-10-11 | 天津五八到家科技有限公司 | Data-updating method, device and mobile terminal |
| CN110730206A (en) * | 2019-09-06 | 2020-01-24 | 浪潮金融信息技术有限公司 | Data service scheme applied to data display of new retail platform |
| CN111245874A (en) * | 2018-11-28 | 2020-06-05 | 杭州海康威视数字技术股份有限公司 | Information pushing method and device, server and storage medium |
| CN111314444A (en) * | 2016-06-30 | 2020-06-19 | 亳州鼎源科技信息有限公司 | Information pushing and displaying method and device |
| CN111427703A (en) * | 2020-03-12 | 2020-07-17 | 上海昊沧系统控制技术有限责任公司 | Industrial data real-time display method and system |
| CN112565214A (en) * | 2020-11-26 | 2021-03-26 | 中国船舶工业系统工程研究院 | Data transmission method, system and medium based on WebSocket |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102625156A (en) * | 2011-01-27 | 2012-08-01 | 天脉聚源(北京)传媒科技有限公司 | information synchronization method and system |
-
2012
- 2012-10-23 CN CN2012104084469A patent/CN102904962A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102625156A (en) * | 2011-01-27 | 2012-08-01 | 天脉聚源(北京)传媒科技有限公司 | information synchronization method and system |
Non-Patent Citations (1)
| Title |
|---|
| 周巍: "基于请求策略和状态切换的服务器推送技术研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 11, 15 November 2009 (2009-11-15), pages 10 * |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105656971A (en) * | 2014-11-24 | 2016-06-08 | 中国移动通信集团公司 | Method, device and system for building message subscription relation between nodes |
| CN105825409A (en) * | 2015-01-07 | 2016-08-03 | 航天信息股份有限公司 | System and method of pushing electronic invoice message |
| CN105825409B (en) * | 2015-01-07 | 2021-03-02 | 航天信息股份有限公司 | Electronic invoice message pushing system and method |
| US10523718B2 (en) | 2015-04-21 | 2019-12-31 | Guangzhou Ucweb Computer Technology Co., Ltd. | Video playing method and device |
| CN106162367A (en) * | 2015-04-21 | 2016-11-23 | 广州市动景计算机科技有限公司 | A kind of video broadcasting method and device |
| CN106572146A (en) * | 2015-10-13 | 2017-04-19 | 腾讯科技（深圳）有限公司 | Message sending method and message sending device |
| CN111314444A (en) * | 2016-06-30 | 2020-06-19 | 亳州鼎源科技信息有限公司 | Information pushing and displaying method and device |
| CN111314444B (en) * | 2016-06-30 | 2022-08-12 | 亳州鼎源科技信息有限公司 | Information pushing and displaying method and device |
| CN106534253A (en) * | 2016-09-27 | 2017-03-22 | 山东浪潮商用系统有限公司 | On-line chatting method and on-line chatting device |
| CN107888683A (en) * | 2017-11-10 | 2018-04-06 | 郑州云海信息技术有限公司 | A kind of client exchange method and device |
| CN108881395A (en) * | 2018-05-23 | 2018-11-23 | 北京五八信息技术有限公司 | Information push method, equipment, message manager and computer readable storage medium |
| CN111245874A (en) * | 2018-11-28 | 2020-06-05 | 杭州海康威视数字技术股份有限公司 | Information pushing method and device, server and storage medium |
| CN111245874B (en) * | 2018-11-28 | 2023-12-05 | 杭州海康威视数字技术股份有限公司 | Information pushing method, device, server and storage medium |
| CN110321140A (en) * | 2019-05-23 | 2019-10-11 | 天津五八到家科技有限公司 | Data-updating method, device and mobile terminal |
| CN110730206A (en) * | 2019-09-06 | 2020-01-24 | 浪潮金融信息技术有限公司 | Data service scheme applied to data display of new retail platform |
| CN111427703A (en) * | 2020-03-12 | 2020-07-17 | 上海昊沧系统控制技术有限责任公司 | Industrial data real-time display method and system |
| CN112565214A (en) * | 2020-11-26 | 2021-03-26 | 中国船舶工业系统工程研究院 | Data transmission method, system and medium based on WebSocket |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102904962A (en) | Message pushing system and message pushing method thereof | |
| CN101159714B (en) | Instant communication method and device | |
| CN102754387B (en) | The system and method for multimedia conferencing is carried out between the telephone plant allowing UPnP and WAN equipment | |
| CN105812235B (en) | Message processing method, device and system | |
| US20050213724A1 (en) | Method and system for providing an improved communications channel for telephone conference initiation and management | |
| CN104520866A (en) | Privacy protection method and terminal equipment | |
| WO2015149471A1 (en) | Information pushing method, system and device and computer storage medium | |
| CN104426728A (en) | Communications device utilizing a central discovery mechanism, and respective method | |
| CN103491162B (en) | Information sharing method based on mobile Internet and system | |
| JP2011510394A (en) | Method and apparatus for handling third device events in a home network supporting UPnP remote protocol | |
| CN101388887A (en) | Network service processing method and system | |
| CN101299689A (en) | On-line detection method as well as mail server | |
| CN102664831B (en) | Method, client and the system of file data are transmitted by instant messaging tools | |
| EP3369236A1 (en) | Information system | |
| CN102882708A (en) | Operation and maintenance auditing method, device and system | |
| CN103929555A (en) | IP recording system voice stream mirroring method | |
| WO2006115377A1 (en) | Notification system and method using messenger | |
| CN103312586A (en) | instant communication | |
| CN202094936U (en) | Fire alarm image-text system | |
| CN103533054A (en) | Method for realizing coordinated processing among multiple terminals and multi-terminal coordinated processing device | |
| CN102932319A (en) | Method and device for keeping calling | |
| CN103491057A (en) | Method, system and device for sharing session data | |
| CN115052003B (en) | Data synchronization method, related device and medium | |
| CN102868837A (en) | Conference call control system and conference call control method | |
| CN106100979B (en) | Instant messaging method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: SHENZHEN ENTERPRISE CLOUD TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: SHENZHEN HUIZHIJI INFORMATION TECHNOLOGY CO., LTD. Effective date: 20130814 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 518000 SHENZHEN, GUANGDONG PROVINCE |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20130814 Address after: Shenzhen City, Baoan District province Guangdong District Longchang road 518000 67 Daqian Industrial Park Building 1, 1 floor, room A04 Applicant after: Shenzhen Enterprise Cloud Technology Co., Ltd. Address before: 1108 room 518057, overseas student Pioneer Building, Nanshan District high tech Southern District, Guangdong, Shenzhen Applicant before: Shenzhen Huizhiji Information Technology Co.,Ltd. |
|
| DD01 | Delivery of document by public notice |
Addressee: Liang Jinghu Document name: Notification of Passing Examination on Formalities |
|
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130130 |