WO2012028033A1 - 消息更新的方法和装置 - Google Patents
消息更新的方法和装置 Download PDFInfo
- Publication number
- WO2012028033A1 WO2012028033A1 PCT/CN2011/076820 CN2011076820W WO2012028033A1 WO 2012028033 A1 WO2012028033 A1 WO 2012028033A1 CN 2011076820 W CN2011076820 W CN 2011076820W WO 2012028033 A1 WO2012028033 A1 WO 2012028033A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- index
- message index
- update
- user
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
Definitions
- the present invention relates to the field of microblog technology, and in particular, to a method and apparatus for message update. Background technique
- Message notifications are very frequent in the Weibo system.
- the method of message update in the Weibo system is: Update and display all new messages at one time.
- the Weibo server will provide all the published messages in the Weibo system from the Weibo client last update to the microblog as a new message.
- Bo client to complete the news update and display of the Weibo client.
- the Weibo server Since the messages in the Weibo system are usually in large quantities, the Weibo server needs to be sent many times to complete the message notification. Therefore, the pressure on the server is increased, and the Weibo client needs to occupy a large amount of storage to update and store new messages. Space, causing waste of resources on the client side, at the same time, displaying a large amount of messages to the user at one time, and also bringing a certain degree of harassment to the user. Summary of the invention
- an embodiment of the present invention provides a method and apparatus for message update.
- the technical solution is as follows:
- a method for updating a message comprising:
- the message index is obtained from the microblog server
- ⁇ is a natural number.
- a device for updating a message includes: An obtaining module, configured to: when the user requests the update message, obtain a message index from the microblog server; the first display module is configured to determine, according to the preset number ⁇ , the first message index in the obtained message index as the first display a message index of the message, obtaining a corresponding message from the microblog server according to the message index of the first display message, and displaying the message to the user;
- the ⁇ is a natural number.
- the technical solution provided by the embodiment of the present invention obtains the message index from the microblog server, determines the message index of the first display message according to the specified number, and obtains the corresponding message from the microblog server to display to the user, the microblog server does not need to be All messages are sent to the local, reducing the pressure on the Weibo server. Moreover, the local does not update and store all the messages to the local one-time, avoiding the waste of resources of the client. In addition, displaying the message to the user in a specified number of times also reduces the harassment of the user and improves the user experience.
- FIG. 1 is a flowchart of a method for updating a message according to Embodiment 1 of the present invention
- FIG. 2 is a flowchart of a method for updating a message according to Embodiment 2 of the present invention
- FIG. 3 is a schematic diagram of a combination of a received message index and a locally saved message index provided by Embodiment 2 of the present invention
- FIG. 4 is a schematic diagram of indexing of storage blocks and blocks according to Embodiment 2 of the present invention.
- FIG. 5 is a structural diagram of an apparatus for updating a message according to Embodiment 3 of the present invention. detailed description
- this embodiment provides a method for updating a message, including:
- the message index is obtained from the microblog server.
- ⁇ is a natural number.
- the method may further include:
- the remaining message index of the obtained message index except the message index of the first displayed message is used as the message index of the subsequent displayed message, and is obtained from the microblog server according to the message index of the subsequent displayed message. Take the corresponding message and display it to the user.
- the message is obtained from the microblog server according to the message index of the subsequent display message, and is displayed to the user, and specifically includes:
- the ⁇ message index is obtained from the message index of the subsequent display message as the current message index. If there are less than K, less than K message indexes are used as the current message index.
- the second message index gets the corresponding message from the microblog server and displays it to the user.
- the above method provided in this embodiment is performed on the microblog client, and the user requests the update message from the microblog server by using the microblog client, and the microblog server updates the new message to the microblog client through the index.
- the pre-specified number refers to the number of new messages displayed by the microblog client by default, which is usually preset by the microblog client.
- the specific value is not specifically limited in this embodiment of the present invention, for example, For 20 or 30 and so on.
- the index of messages obtained from the Weibo server is usually multiple, such as 100, 200, and so on. Among them, it is divided into two parts, one part is the message index of the first display message, and the other part is the message index of the subsequent display message.
- the microblog client can display 30 messages at a time, obtain 200 message indexes from the microblog server, and use the first 30 of them as the message index of the first display message, and the rest as the message index of the subsequent display message, if the user If the request continues to be updated, the subsequent messages continue to be displayed.
- the foregoing method provided in this embodiment obtains a message index from a microblog server, determines a message index of the first display message according to a specified number, and obtains a corresponding message from the microblog server to display to the user, and the microblog server does not need to have all of the information at one time.
- the message was sent to the local, reducing the pressure on the Weibo server.
- the local does not update and store all the messages to the local one-time, avoiding the waste of resources of the client.
- displaying the message to the user in a specified number of times also reduces the harassment of the user and improves the user experience.
- this embodiment provides a method for updating a message, including:
- the local microblog client forwards the request to the microblog server, and receives the message index returned by the microblog server.
- the index of the message received by the microblog client is an index of all new messages stored by the microblog server since the microblog client last updated.
- the Weibo client last updated the Weibo message at 9:00, and the current time 10:00 requests the update again, then the Weibo server sends the message index of all new messages between 9:00 and 10:00.
- the publisher of all the new messages may be a microblog client, but is usually a plurality of microblog clients, which are not specifically limited in this embodiment of the present invention.
- the messages involved in this embodiment all refer to messages published in the microblog system, and the message index refers to an index number that identifies the message, such as an ID number and the like.
- the local microblog client determines whether the received message index overlaps with the locally saved message index; if there is overlap, execute 203; otherwise, execute 204.
- the local microblog client saves the message index in various forms, including but not limited to the form of the index table.
- a locally stored message index usually has a fixed storage area.
- the currently received message index is usually stored in the cache, and the overlap means that the message index is the same. For example, there are 100 locally saved message indexes, one of which has a message index number of 50, and the current received message index has 70, and there is also a message index number of 50, which can determine that there is overlap.
- the non-overlapping part of the received message index is used as the message index of the current update, and then 205 is performed. For example, if there are currently 70 received message indexes, and 20 of the message indexes overlap with the locally saved message index, the remaining 50, that is, the non-overlapping parts are used as the message index of the current update, and overlapped. The part does not need to be updated.
- the locally saved message index has changed, and the content includes the original message index before the current message index update, and the message index saved in the current update.
- Figure 3 which contains a locally saved message index
- Table 2 shows the received message index of the temporary cache, one of which is the part that overlaps with the locally saved message index, and the other part is the non-overlapping part. That is, the new message index
- Table 3 is the locally saved new table obtained after determining the message index of this update, which is the result obtained by combining Table 1 and Table 2, wherein the overlapping part is unchanged, which is equivalent to A new message index is added based on Table 1.
- the new message index consists of two parts: the message index of the first displayed message and the message index of the subsequent displayed message.
- the step of merging the locally saved message index linked list and the temporarily cached received message index linked list may specifically adopt a Merge merge algorithm, which involves indexing the locally saved message index linked list and the cache linked list. Delete and add, merge to get a new local message index list, and make this list can represent the latest message status of the server.
- the index of the message that has been determined to be updated is stored locally, and may be in various forms, which is not specifically limited in this embodiment of the present invention.
- the maintenance may be performed in the form of a linked list and in units of blocks, as follows: The determined message index of this update is recorded as a block and the index of the block is set; the block and block of the block are saved locally. Since the Weibo client frequently updates the message, after multiple updates, multiple blocks are saved, and each update stores a block, and each block corresponds to an index of a block, which needs to be from the Weibo server. When pulling a message, first find the corresponding block through the index of the block, and then pull the corresponding message from the microblog server according to the message index in the block to update.
- the message index is stored in the linked list, and each updated message index corresponds to a block in the linked list.
- three blocks are taken as an example, and from bottom to top, respectively, block 1, block 2, and block 3
- index numbers 1, 2 and 3 are index numbers 1, 2 and 3.
- some blocks contain only the message index of the first displayed message, such as block 1, and some blocks contain not only the message index of the first displayed message, but also the message index of the subsequent displayed message.
- This embodiment is referred to as a fault, such as block 2 and block 3.
- the fault refers to that the message update is not completed once, but is completed according to the user's request.
- the message is continuously pulled according to the subsequent message index, according to the pre-specified number. K, each time the user requests to continue to update, the ⁇ message is pulled from the microblog server, and the update is completed step by step until all the messages are pulled or the user stops requesting to continue the update.
- 206 Obtain a corresponding message from the microblog server according to the determined message index of the first displayed message, and display the message to the user; at this time, the first display is completed, and the subsequent message is not pulled, in the local microblog client Only the message index of the subsequent message is saved, so the storage space of the Weibo client is greatly saved, and the waste of resources is avoided.
- the user can browse the two messages. If the user requests to continue the update, when the determined message index of the current update is maintained in units of blocks, according to the index of the block saved this time. Reading the corresponding block, and using the remaining message indexes other than the first message index of the first display message as the message index of the subsequent display message, when the determined message index of the current update is otherwise maintained. Without searching for a block, the remaining message indexes other than the first message index of the first display message are directly used as the message index of the subsequent display message, and each time the user requests to continue the update, all the messages are obtained from the message index of the subsequent displayed message. The index is used as the index of the current message. If there is less than one, the index of the message will be used as the index of the current message. According to the message index of this time, the corresponding message is obtained from the microblog server and displayed to the user.
- the number of displayed messages can be less than one. For example, if the microblog client receives 70 messages and 30 messages, the first 30 messages are displayed. When the user clicks on the request to continue the update, 30 messages are displayed again. If the user clicks on the request to continue the update, A message corresponding to the last 10 indexes of the 70 indexes is displayed to the user. A total of 3 times were displayed in the process, and the number of messages displayed last time was less than one. If the user no longer sends a request after the previous two displays, the last 10 messages are not displayed. In the embodiment of the present invention, the microblog client receives the message index sent by the microblog server, which may be one time or multiple times.
- the microblog server when the message index is sent by the microblog server, if the message index is too large, it needs to be sent to the microblog client in multiple times.
- the means for sending the multiple times is the prior art, and the embodiment of the present invention does not Make specific limits.
- the microblog server needs to send 200 message indexes, and according to the communication protocol, only 70 can be sent at a time, then the microblog server will send 3 times, the first two are 70, and the last time is 60.
- the microblog server first sends a message index to the microblog client, and the microblog client obtains the corresponding message from the microblog server according to the message index of the first displayed message and the message index of the subsequent displayed message.
- the Bo server does not need to send all messages to the Weibo client at one time, which reduces the pressure on the Weibo server.
- the microblog client does not update and store all the messages to the local one time.
- the subsequent messages are updated. If the user does not request to continue the update, the subsequent messages are not updated, and the client is avoided. Waste of resources.
- displaying the message to the user in a specified number of times also reduces the harassment of the user and improves the user experience.
- the embodiment provides a device for updating a message, including:
- the obtaining module 501 is configured to: when the user requests the update message, obtain the message index from the microblog server; the first display module 502 is configured to determine, according to the pre-specified number K, the message index as the first display in the obtained message index.
- the message index of the message is obtained from the microblog server according to the message index of the first displayed message, and is displayed to the user; wherein, ⁇ is a natural number.
- the device may further include:
- a first subsequent display module configured to: if the user requests to continue to update, use the remaining message index of the message index of the first displayed message in the obtained message index as the message index of the subsequent display message, according to the message index of the subsequent displayed message
- the blog server obtains the corresponding message and displays it to the user.
- the first subsequent display module is configured to: when the corresponding message is obtained from the microblog server according to the message index of the subsequent display message, and is displayed to the user, specifically:
- the message index is obtained from the message index of the subsequent display message as the current message index. If less than ⁇ , less than one message index is used as the current message index.
- the second message index gets the corresponding message from the microblog server and displays it to the user.
- the first display module 502 can include:
- a judging unit configured to determine whether the obtained message index overlaps with the locally saved message index; and the processing unit is configured to: if there is an overlap, the non-overlapping part of the obtained message index is used as the cancellation of the current update Index; if there is no overlap, the obtained message index is used as the message index of this update;
- the determining unit is configured to save the updated message index locally, and determine the ⁇ message index as the message index of the first displayed message in the updated message index according to the pre-specified number ⁇ .
- the determining unit may include:
- Save subunits which are used to save the index of blocks and blocks locally.
- the device may further include:
- a second subsequent display module configured to: if the user requests to continue to update, read the block according to the index of the block, and use the remaining message index of the block except the message index of the first displayed message as the message index of the subsequent display message, at each time the user When the request continues to be updated, the ⁇ message index is obtained from the message index of the subsequent display message as the current message index. If less than ⁇ , less than one message index is used as the current message index, according to the current message index. The corresponding message is obtained from the Weibo server and displayed to the user.
- the message index obtained by the obtaining module 501 is an index of all new messages stored by the microblog server since the local last update.
- the foregoing device provided in this embodiment may be a microblog client, and the method in any one of the foregoing method embodiments may be performed on the device.
- the method in any one of the foregoing method embodiments may be performed on the device.
- the foregoing apparatus obtains a message index from the microblog server, and obtains a corresponding message from the microblog server according to the message index of the first display message and the message index of the subsequent display message, so that the microblog server does not need to be sent at one time. All the news has alleviated the pressure on the Weibo server. Moreover, the local does not update and store all the messages to the local one time. When the user requests to continue to update, the subsequent messages are updated. If the user does not request to continue the update, the subsequent messages are not updated, and the resource waste of the client is avoided. In addition, displaying the message to the user in a specified number of times also reduces the harassment of the user and improves the user experience.
- the storage medium may be a magnetic disk, an optical disk, a read only memory (ROM) or a random access memory (RAM).
- Each functional unit in the embodiment of the present invention may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
- the integrated modules, if implemented in the form of software functional modules and sold or used as separate products, may also be stored in a computer readable storage medium.
- the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
- Each of the above described devices or systems may perform the methods of the corresponding method embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/819,703 US20130232208A1 (en) | 2010-08-31 | 2011-07-04 | Method and device for updating messages |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010102723350A CN102387178A (zh) | 2010-08-31 | 2010-08-31 | 消息更新的方法和装置 |
CN201010272335.0 | 2010-08-31 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012028033A1 true WO2012028033A1 (zh) | 2012-03-08 |
Family
ID=45772134
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/076820 WO2012028033A1 (zh) | 2010-08-31 | 2011-07-04 | 消息更新的方法和装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20130232208A1 (zh) |
CN (1) | CN102387178A (zh) |
WO (1) | WO2012028033A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9082154B2 (en) * | 2012-03-15 | 2015-07-14 | Sap Se | Aggregation and semantic modeling of tagged content |
WO2013149381A1 (en) * | 2012-04-05 | 2013-10-10 | Microsoft Corporation | Platform for continuous graph update and computation |
US20150040005A1 (en) * | 2013-07-30 | 2015-02-05 | Google Inc. | Mobile computing device configured to output haptic indication of task progress |
CN105100143A (zh) * | 2014-05-04 | 2015-11-25 | 腾讯科技(深圳)有限公司 | 显示数据的方法及装置 |
CN104935657A (zh) * | 2015-06-15 | 2015-09-23 | 清华大学深圳研究生院 | 主动推送信息的方法和嵌入式节点操作系统 |
CN110493122B (zh) * | 2019-08-29 | 2022-01-28 | 北京拉勾网络技术有限公司 | 一种会话信息的同步方法、装置、计算设备及存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1722671A (zh) * | 2004-07-14 | 2006-01-18 | 中兴通讯股份有限公司 | 电信网管的大流量数据显示方法 |
CN101304549A (zh) * | 2007-05-08 | 2008-11-12 | 华为技术有限公司 | 不下载发送消息的方法、消息服务器和终端 |
CN101674318A (zh) * | 2008-09-11 | 2010-03-17 | 北大方正集团有限公司 | 一种向移动设备定时推送数据的方法 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6167402A (en) * | 1998-04-27 | 2000-12-26 | Sun Microsystems, Inc. | High performance message store |
US7308453B2 (en) * | 2004-06-29 | 2007-12-11 | Nokia Corporation | Meta-data approach to indexing, retrieval and management of stored messages in a portable communication device |
US7693948B2 (en) * | 2006-05-15 | 2010-04-06 | Sap Ag | Email traffic integration into a knowledge management system |
JP4887918B2 (ja) * | 2006-06-09 | 2012-02-29 | 富士通株式会社 | メール一覧表示プログラムおよびメール管理プログラム |
KR100765791B1 (ko) * | 2006-07-13 | 2007-10-12 | 삼성전자주식회사 | 콘텐트 관리 방법 및 장치 |
CN101192218A (zh) * | 2006-11-23 | 2008-06-04 | 国际商业机器公司 | 提供和获取网络内容的方法、装置和系统 |
CN101277472B (zh) * | 2007-03-30 | 2011-08-10 | 华为技术有限公司 | 博客内容的同步方法、设备和系统 |
US7836037B2 (en) * | 2007-10-04 | 2010-11-16 | Sap Ag | Selection of rows and values from indexes with updates |
US20090106311A1 (en) * | 2007-10-19 | 2009-04-23 | Lior Hod | Search and find system for facilitating retrieval of information |
US20100274795A1 (en) * | 2009-04-22 | 2010-10-28 | Yahoo! Inc. | Method and system for implementing a composite database |
US20110178995A1 (en) * | 2010-01-21 | 2011-07-21 | Microsoft Corporation | Microblog search interface |
US8621012B2 (en) * | 2010-02-08 | 2013-12-31 | Google Inc. | Active e-mails |
-
2010
- 2010-08-31 CN CN2010102723350A patent/CN102387178A/zh active Pending
-
2011
- 2011-07-04 WO PCT/CN2011/076820 patent/WO2012028033A1/zh active Application Filing
- 2011-07-04 US US13/819,703 patent/US20130232208A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1722671A (zh) * | 2004-07-14 | 2006-01-18 | 中兴通讯股份有限公司 | 电信网管的大流量数据显示方法 |
CN101304549A (zh) * | 2007-05-08 | 2008-11-12 | 华为技术有限公司 | 不下载发送消息的方法、消息服务器和终端 |
CN101674318A (zh) * | 2008-09-11 | 2010-03-17 | 北大方正集团有限公司 | 一种向移动设备定时推送数据的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN102387178A (zh) | 2012-03-21 |
US20130232208A1 (en) | 2013-09-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6423059B2 (ja) | セキュリティプロトコルの動的選択 | |
US20180205976A1 (en) | Method and apparatus of obtaining video fragment | |
JP2022050451A (ja) | インターネットクラウドでホストされる自然言語による対話型メッセージングシステムサーバ連携 | |
US9131054B2 (en) | Synchronization in unified messaging systems | |
US9165081B2 (en) | Hovercard pivoting for mobile devices | |
US10097659B1 (en) | High performance geographically distributed data storage, retrieval and update | |
JP6952060B2 (ja) | インターネットクラウドでホストされる自然言語による対話型メッセージングシステムユーザリゾルバ | |
WO2017181709A1 (zh) | 推送消息获取、消息推送方法及装置 | |
US10331613B2 (en) | Methods for enabling direct memory access (DMA) capable devices for remote DMA (RDMA) usage and devices therof | |
WO2012028033A1 (zh) | 消息更新的方法和装置 | |
CN106874334B (zh) | 一种数据处理方法及装置、资讯处理系统 | |
JP2019530033A (ja) | インターネットクラウドでホストされる自然言語による対話型メッセージングシステムセッション化部 | |
US20130024526A1 (en) | Method of managing feeds based on classifications | |
JP2013521562A5 (zh) | ||
WO2013078689A1 (zh) | 一种云消息服务中实现消息传递的方法和装置 | |
CN103312751A (zh) | 一种基于浏览器的即时通信方法 | |
EP3028437A1 (en) | Messaging api over http protocol to establish context for data exchange | |
JP2013522782A5 (zh) | ||
EP2991280A1 (en) | Content sharing method and social synchronizing apparatus | |
US20150039675A1 (en) | Messaging over http protocol for data exchange | |
US9876776B2 (en) | Methods for generating and publishing a web site based on selected items and devices thereof | |
AU2014321418A1 (en) | Email webclient notification queuing | |
WO2012031511A1 (zh) | 管理消息的方法和装置 | |
WO2010078791A1 (zh) | 一种社会网络服务sns浏览方法及提供sns浏览的设备 | |
WO2019242279A1 (zh) | 一种消息处理方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11821059 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13819703 Country of ref document: US |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 08/05/2013) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11821059 Country of ref document: EP Kind code of ref document: A1 |