CN108804434B - Message query method, server and terminal equipment - Google Patents
Message query method, server and terminal equipment Download PDFInfo
- Publication number
- CN108804434B CN108804434B CN201710282358.1A CN201710282358A CN108804434B CN 108804434 B CN108804434 B CN 108804434B CN 201710282358 A CN201710282358 A CN 201710282358A CN 108804434 B CN108804434 B CN 108804434B
- Authority
- CN
- China
- Prior art keywords
- terminal device
- server
- message
- query
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000004891 communication Methods 0.000 claims description 8
- 238000011022 operating instruction Methods 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 27
- 238000012360 testing method Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 8
- 230000001413 cellular effect Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Medical Informatics (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses a message query method, which can save storage resources of a server and improve the confidentiality of historical messages. The method comprises the following steps: the server receives an inquiry request sent by first terminal equipment; the server inquires whether a target history message corresponding to the inquiry request is stored locally; if not, the server sends the query request to a second terminal device, wherein the first terminal device and the second terminal device are both terminal devices bound with the same target account number; the server receives the target history message sent by the second terminal device, wherein the target history message is locally inquired by the second terminal device according to the inquiry request; and the server sends the target history message to the first terminal equipment.
Description
Technical Field
The present invention relates to the field of computer communication applications, and in particular, to a message query method, a server, and a terminal device.
Background
At present, computer technology, network technology and electronic technology are continuously developed, people can communicate with other people at any time and any place through computers and various portable intelligent terminals to establish contact. In this case, a large number of chat messages, i.e., history messages, may be generated on a personal computer, a mobile phone, or the like of each user, and the history messages need to be stored so that the user can view the history messages at any time when needed.
The currently adopted scheme is mainly as follows: all history messages of the user are stored in the server, and the same user can use different terminal equipment to inquire the same history message from the server.
However, storing all the history messages of the user in the server may consume a large amount of storage resources of the server; on the other hand, if the server is attacked, all the history messages of the user may be leaked, so that the confidentiality of the history messages is difficult to guarantee.
Disclosure of Invention
The embodiment of the invention provides a message query method, which can save storage resources of a server and improve the confidentiality of historical messages.
In view of this, a first aspect of the embodiments of the present invention provides a message query method, which may include:
the server receives an inquiry request sent by first terminal equipment;
the server inquires whether a target historical message corresponding to the inquiry request is stored locally;
if not, the server sends the query request to a second terminal device, wherein the first terminal device and the second terminal device are both terminal devices bound with the same target account number;
the server receives the target history message sent by the second terminal device, wherein the target history message is locally queried by the second terminal device according to the query request;
and the server sends the target history message to the first terminal equipment.
A second aspect of the embodiments of the present invention provides a method for querying a message, where the method includes:
a first terminal device receives a query request;
the first terminal equipment inquires whether a target history message corresponding to the inquiry request is stored locally;
if not, the first terminal equipment sends the query request to a server;
the first terminal device receives the target history message sent by the server, wherein the target history message is locally queried by the server according to the query request, or the target history message is sent to a second terminal device by the server when the server does not locally query according to the query request, the second terminal device locally queries according to the query request, and the first terminal device and the second terminal device are both terminal devices bound with the same target account number.
A third aspect of the embodiments of the present invention provides a message query method, which may include:
the method comprises the steps that a second terminal device receives an inquiry request sent by a server, wherein the inquiry request is sent to the server by a first terminal device in advance, and the first terminal device and the second terminal device are both terminal devices bound with the same target account number;
the second terminal equipment locally queries according to the query request to obtain a target historical message;
and the second terminal equipment sends the target history message to the server so that the server sends the target history message to the first terminal equipment.
A fourth aspect of an embodiment of the present invention provides a server, which may include:
the first receiving module is used for receiving a query request sent by first terminal equipment;
the query module is used for querying whether a target historical message corresponding to the query request is stored locally;
the first sending module is used for sending the query request to a second terminal device if the query module queries that a target history message corresponding to the query request is not stored locally, wherein the first terminal device and the second terminal device are both terminal devices bound with the same target account number;
a second receiving module, configured to receive the target history message sent by the second terminal device, where the target history message is locally queried by the second terminal device according to the query request;
and the second sending module is used for sending the target historical message to the first terminal equipment.
A fifth aspect of an embodiment of the present invention provides a terminal device, where the terminal device is used as a first terminal device, and the terminal device may include:
the first receiving module is used for receiving the query request;
the query module is used for querying whether a target historical message corresponding to the query request is stored locally;
the sending module is used for sending the query request to a server if the query module queries a target history message corresponding to the query request which is not stored locally;
a second receiving module, configured to receive the target history message sent by the server, where the target history message is obtained by the server according to the query request in a local area, or the target history message is obtained by sending the query request to a second terminal device by the server when the server does not obtain the query request in the local area according to the query request, where the second terminal device obtains the query request in the local area according to the query request, and both the first terminal device and the second terminal device are terminal devices bound with a same target account.
A sixth aspect of an embodiment of the present invention provides a terminal device, where the terminal device is used as a second terminal device, and the terminal device may include:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving an inquiry request sent by a server, the inquiry request is sent to the server by a first terminal device in advance, and the first terminal device and the second terminal device are both terminal devices bound with the same target account number;
the query module is used for locally querying according to the query request to obtain a target historical message;
a sending module, configured to send the target history message to the server, so that the server sends the target history message to the first terminal device.
According to the technical scheme, the embodiment of the invention has the following advantages: the server receives a query request sent by first terminal equipment, when the server does not query a target history message corresponding to the query request in the local area, the server indicates that the target history message is not stored in the server, at the moment, the server sends the query request to second terminal equipment, and then the server receives the target history message sent by the second terminal equipment, wherein the target history message is queried in the local area by the second terminal equipment according to the query request and indicates that the target history message is stored in the second terminal equipment. Therefore, a part of history messages can be reserved in the server, and a part of history messages can also be reserved in the second terminal device. In addition, if the server is attacked, the technical scheme of the invention does not cause the risk of leakage of all historical messages of the user, thereby improving the confidentiality of the historical messages. Therefore, the technical scheme of the invention can save the storage resource of the server and improve the confidentiality of the historical information.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a diagram of a message query system architecture in an embodiment of the present invention;
FIG. 2 is a diagram of an interactive embodiment of a message query method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a message window of a first terminal device according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a message manager of a first terminal device according to an embodiment of the present invention;
FIG. 5 is a diagram of an embodiment of a message query method according to an embodiment of the present invention;
FIG. 6-a is a schematic diagram of an interface for displaying a record of an unsearched message in a message manager according to an embodiment of the present invention;
FIG. 6-b is a schematic diagram of an interface for displaying a searched message record in a message manager according to an embodiment of the present invention;
FIG. 7 is a diagram of one embodiment of a server in an embodiment of the present invention;
FIG. 8 is a diagram of another embodiment of a server in an embodiment of the present invention;
FIG. 9 is a schematic diagram of another embodiment of a server in an embodiment of the present invention;
fig. 10 is a schematic diagram of an embodiment of a first terminal device according to the embodiment of the present invention;
fig. 11 is a schematic diagram of an embodiment of a second terminal device according to the embodiment of the present invention;
fig. 12 is a schematic diagram of an embodiment of a terminal device according to the embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a message query method, which can save storage resources of a server and improve the confidentiality of historical messages.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that the present invention is applied to a message query system, and please refer to fig. 1, where fig. 1 is a diagram illustrating an architecture of a message query system according to an embodiment of the present invention. As shown in fig. 1, the message query system includes a first terminal device, a server, and at least one second terminal device, where the first terminal device is configured to receive a query request for a history message sent by a user, and send the query request to the server when the first terminal device queries a history message corresponding to the query request that is not stored locally; the server is used for receiving the query request sent by the first terminal device and sending the query request to the second terminal device when the server queries the history message corresponding to the query request which is not stored locally; and the second terminal equipment user receives the query request sent by the server and locally queries the corresponding history message according to the query request.
The first terminal device and the second terminal device may be a smart phone, a tablet computer, a Personal Digital Assistant (PDA), or the like, and are not limited herein.
For easy understanding, referring to fig. 2, an interactive embodiment of the message query method according to the embodiment of the present invention includes:
101. a first terminal device receives a query request;
in this embodiment, the user may initiate the query request in the message window of the first terminal device, or the user may initiate the query request in the message manager of the first terminal device.
For example, an embodiment of the present invention provides a message window diagram of a first terminal device, that is, a message window diagram of a background work group of the first terminal device shown in fig. 3, and in fig. 3, a user may obtain a history message through a message recording option in the message window of the background work group.
An embodiment of the present invention further provides a schematic diagram of a message manager of a first terminal device, specifically as shown in fig. 4, a user may input a keyword in a column of keywords in the message manager to query a history message matching the keyword.
102. The first terminal equipment inquires whether a target history message corresponding to the inquiry request is stored locally, if so, executing step 109, and if not, executing step 103;
in this embodiment, after receiving the query request, the first terminal device may query, in the local message database, whether the target history message corresponding to the query request is stored, if the first terminal device queries the target history message corresponding to the query request in the local message database, step 109 is executed, and if the first terminal device does not query the target history message corresponding to the query request in the local message database, step 103 is executed.
103. The first terminal equipment sends a query request to the server;
in this embodiment, if the first terminal device does not query the target history message corresponding to the query request in the local message database, it indicates that the first terminal device does not store the target history message corresponding to the query request in the local message database, and then the first terminal device sends the query request to the server, that is, performs corresponding query from the server.
104. The server inquires whether a target historical message corresponding to the inquiry request is stored locally, if so, executing step 108, and if not, executing step 105;
in this embodiment, after receiving the query request sent by the first terminal device, the server may query whether the target history message corresponding to the query request is stored locally, if the server queries that the target history message corresponding to the query request is stored locally, step 108 is performed, and if the server queries that the target history message corresponding to the query request is not stored locally, step 105 is performed.
105. The server sends a query request to the second terminal equipment;
in this embodiment, if the server queries that the target history message corresponding to the query request is not stored locally, it indicates that the server does not store the target history message corresponding to the query request in its local message database, and then the server sends the query request to the second terminal device, that is, performs a corresponding query from the second terminal device.
It should be noted that the number of the second terminal devices may be 1 or multiple, and is not limited herein, and it is understood that, if the number of the second terminal devices is multiple, the server sends an inquiry request to at least two second terminal devices, so as to be able to inquire about the target history message from at least one of the at least two second terminal devices.
In addition, the first terminal device and the second terminal device are both terminal devices bound with the same target account, and obviously, the history message of the target account includes the target history message.
106. The second terminal equipment locally inquires according to the inquiry request to obtain a target historical message;
in this embodiment, the second terminal device receives the query request sent by the server, and then the second terminal device performs local query according to the query request to obtain the target history message.
107. The second terminal equipment sends the target history message to the server;
in this embodiment, the second terminal device archives the queried target history message, and uploads the archived target history message to the server.
108. The server sends the target history message to the first terminal device, and then executes step 109;
in this embodiment, after receiving the target history message sent by the second terminal device, the server sends the target history message to the first terminal device.
109. And the first terminal equipment displays the target history message.
In this embodiment, if the first terminal device queries the target history message locally, or the first terminal device receives the target history message sent by the server, the first terminal device displays the target history message.
In this embodiment, a server receives an inquiry request sent by a first terminal device, and when the server does not inquire a target history message corresponding to the inquiry request locally, it indicates that the target history message is not stored in the server, at this time, the server sends the inquiry request to a second terminal device, and then the server receives the target history message sent by the second terminal device, where the target history message is inquired locally by the second terminal device according to the inquiry request, and indicates that the target history message is stored in the second terminal device. Therefore, a part of history messages can be reserved in the server, and a part of history messages can also be reserved in the second terminal device. In addition, if the server is attacked, the technical scheme of the invention does not cause the risk of leakage of all the historical messages of the user, thereby improving the confidentiality of the historical messages. Therefore, the technical scheme of the invention can save the storage resource of the server and improve the confidentiality of the historical information.
Referring to fig. 5, a message query method in an embodiment of the present invention is described below from the perspective of a server, where an embodiment of the message query method in the embodiment of the present invention includes:
201. the server receives an inquiry request sent by first terminal equipment;
in this embodiment, the first terminal device may receive the query request first, and if the first terminal device does not query the target history message corresponding to the query request locally according to the query request, the first terminal device sends the query request to the server.
202. The server inquires whether a target history message corresponding to the inquiry request is stored locally, if not, step 203 is executed;
in this embodiment, after the server receives the query request sent by the first terminal device, the server may query whether the target history message corresponding to the query request is stored locally, and if the server queries that the target history message corresponding to the query request is not stored locally, step 203 is executed.
Optionally, in some possible embodiments, if the server queries that the target history message corresponding to the query request is locally stored, the server sends the target history message to the first terminal device.
203. The server sends a query request to the second terminal equipment;
in this embodiment, if the server queries that the target history message corresponding to the query request is not stored locally, it indicates that the server does not store the target history message corresponding to the query request in its local message database, and then the server sends the query request to the second terminal device, that is, performs a corresponding query from the second terminal device.
It should be noted that the number of the second terminal devices may be 1, or may be at least two, and the present disclosure is not limited thereto, and it is understood that, if the number of the second terminal devices is at least two, the server sends an inquiry request to the at least two second terminal devices, so as to be able to inquire the target history message from at least one of the at least two second terminal devices.
In addition, the first terminal device and the second terminal device are both terminal devices bound with the same target account, and obviously, the history message of the target account includes the target history message.
In order to avoid that the target account is not logged in the second terminal device, which results in that the server cannot obtain a response after sending the query request to the second terminal device, in some possible embodiments, before the server sends the query request to the second terminal device, the method may further include:
the server judges whether the target account is logged in on the second terminal device;
the sending, by the server, the query request to the second terminal device includes:
and if the target account is logged on the second terminal equipment, the server sends a query request to the second terminal equipment.
It can be seen that, before the server sends the query request to the second terminal device, it needs to determine whether the target account is already logged in the second terminal device, and only under the condition that the target account is already logged in the second terminal device, the server sends the query request to the second terminal device. If the target account is not logged in the second terminal device, the second terminal device cannot perform inquiry due to the fact that the target account is not logged in even if the server sends an inquiry request to the second terminal device. Therefore, the server can send the query request to the second terminal device only under the condition that the target account logs in the second terminal device, and the technical scheme of the application is perfected.
Further, in order to solve the problem that the second terminal device cannot perform querying because the target account is not logged in, in some possible embodiments, the method may further include:
if the target account is not logged in the second terminal device, the server sends a first indication message to the second terminal device, wherein the first indication message is used for indicating that the target account is logged in the second terminal device.
Therefore, the target account is indicated to be logged in the second terminal device through the first indication message, so that the problem that the second terminal device cannot be queried because the target account is not logged in is solved, and the technical scheme of the application is further perfected.
204. The server receives a target history message sent by the second terminal equipment;
in this embodiment, after the server sends the query request to the second terminal device, the second terminal device locally queries according to the query request to obtain the target history message, and the second terminal device sends the target history message to the server.
205. The server sends the target history message to the first terminal device.
In this embodiment, after receiving the target history message sent by the second terminal device, the server sends the target history message to the first terminal device.
Optionally, in some possible embodiments, before the server sends the target history message to the first terminal device, the method may further include:
the server stores the target history message;
the server sends a second indication message to the first terminal equipment;
the server receives an acquisition request of the first terminal device for the target historical message according to the second indication message;
correspondingly, the sending, by the server, the target history message to the first terminal device may include: and the server sends the target history message to the first terminal equipment according to the acquisition request.
It can be seen that when the server collects the target history message, the first terminal device is then notified to download the target history message.
Further, after the server sends the target history message to the first terminal device according to the acquisition request, the method may further include:
the server deletes the stored target history message.
It can be seen that the server deletes the stored target history message, considering that the target history message is already stored locally at the second terminal device and that the target history message is leaked in order to avoid the server being attacked.
In this embodiment, a server receives an inquiry request sent by a first terminal device, and when the server does not inquire a target history message corresponding to the inquiry request locally, it indicates that the target history message is not stored in the server, at this time, the server sends the inquiry request to a second terminal device, and then the server receives the target history message sent by the second terminal device, where the target history message is inquired locally by the second terminal device according to the inquiry request, and indicates that the target history message is stored in the second terminal device. Therefore, a part of history messages can be reserved in the server, and a part of history messages can also be reserved in the second terminal device. In addition, if the server is attacked, the technical scheme of the invention does not cause the risk of leakage of all the historical messages of the user, thereby improving the confidentiality of the historical messages. Therefore, the technical scheme of the invention can save the storage resource of the server and improve the confidentiality of the historical information.
For convenience of understanding, the message query method in the embodiment of the present invention may be described in detail in a specific application scenario, which specifically includes:
the user A logs in the instant messaging application on the computer 1 and the computer 2 by using the same account.
Step 1, in the process that a user A uses a certain instant messaging application on a computer 1, the user A wants to inquire history information. Then, the user a opens the message manager of the instant messaging application, wherein the message manager interface diagram is as shown in fig. 4, please refer to fig. 4, and fig. 4 is a message manager interface diagram of a common instant messaging application, and a search bar exists in the message manager interface.
And 2, inputting a test message in the search bar by the user A, and clicking a search option beside the search bar by using a mouse. And then searching for the message in the message manager, but not searching for the message record, wherein an interface schematic diagram showing that the message record is not searched for in the message manager is shown in fig. 6-a, please refer to fig. 6-a, and fig. 6-a is an interface schematic diagram showing that the message record is not searched for in the message manager, and in the interface schematic diagram, the message record corresponding to the 'test message' is not displayed.
And 3, because the computer 1 does not find the test record corresponding to the test message in the local message manager, the computer 1 sends the query request of the test message to the server, and the server sends the query request of the test message to the computer 2 after the server does not query the message record corresponding to the query request of the test message stored locally.
And 4, after receiving the query request of the test message, the computer 2 starts a message manager, automatically searches message records corresponding to the test message from the message manager, and searches the message records, wherein an interface schematic diagram for displaying the searched message records in the message manager is shown in fig. 6-b, please refer to fig. 6-b, fig. 6-b is an interface schematic diagram for displaying the searched message records in the message manager, and 5 message records corresponding to the test message are displayed in the interface schematic diagram.
And step 5, the computer 2 sends the 5 message records corresponding to the test message to the server, then the server sends the 5 message records corresponding to the test message to the computer 1, and the computer 1 displays the 5 message records corresponding to the test message.
The message query method in the embodiment of the present invention is described above by way of an embodiment, and the server in the embodiment of the present invention is described below by way of an embodiment, with reference to fig. 7, where an embodiment of the server in the embodiment of the present invention includes:
a first receiving module 301, configured to receive an inquiry request sent by a first terminal device;
the query module 302 is configured to query whether a target history message corresponding to the query request is stored locally;
a first sending module 303, configured to send a query request to a second terminal device if the query module 302 queries that a target history message corresponding to the query request is not stored locally, where the first terminal device and the second terminal device are both terminal devices bound with the same target account;
a second receiving module 304, configured to receive a target history message sent by a second terminal device, where the target history message is locally queried by the second terminal device according to a query request;
a second sending module 305, configured to send the target history message to the first terminal device.
In this embodiment, the first receiving module 301 receives an inquiry request sent by a first terminal device, and when the inquiry module 302 does not inquire a target history message corresponding to the inquiry request locally, it indicates that the target history message is not stored in the server, at this time, the first sending module 303 sends the inquiry request to a second terminal device, and then the second receiving module 304 receives the target history message sent by the second terminal device, where the target history message is inquired locally by the second terminal device according to the inquiry request, and indicates that the target history message is stored in the second terminal device. Therefore, a part of history messages can be reserved in the server, and a part of history messages can also be reserved in the second terminal device. In addition, if the server is attacked, the technical scheme of the invention does not cause the risk of leakage of all the historical messages of the user, thereby improving the confidentiality of the historical messages. Therefore, the technical scheme of the invention can save the storage resource of the server and improve the confidentiality of the historical information.
Optionally, referring to fig. 8, in some possible embodiments, the server may further include:
a determining module 401, configured to determine whether the target account is logged in the second terminal device before the first sending module 303 sends the query request to the second terminal device;
correspondingly, the first sending module 303 is specifically configured to send a query request to the second terminal device if the target account number is already logged in the second terminal device.
It can be seen that before the first sending module 303 sends the query request to the second terminal device, it needs to first determine whether the target account is logged in the second terminal device, and only under the condition that the target account is logged in the second terminal device, the first sending module 303 sends the query request to the second terminal device. Because if the target account is not logged in the second terminal device, even if the first sending module 303 sends the query request to the second terminal device, the second terminal device cannot perform the query because the target account is not logged in. Therefore, only under the condition that the target account logs in the second terminal device, the first sending module 303 sends the query request to the second terminal device, thereby perfecting the technical scheme of the application.
Further, the server may further include:
a third sending module 402, configured to send a first indication message to the second terminal device if the target account is not logged in the second terminal device, where the first indication message is used to indicate that the target account is logged in the second terminal device.
Therefore, the target account is indicated to be logged in the second terminal device through the first indication message, so that the problem that the second terminal device cannot be queried because the target account is not logged in is solved, and the technical scheme of the application is further perfected.
Further, the server may further include:
a storage module 403, configured to store the target history message before the second sending module 305 sends the target history message to the first terminal device;
a fourth sending module 404, configured to send a second indication message to the first terminal device;
a third receiving module 405, configured to receive an acquisition request of the first terminal device for the target history message according to the second indication message;
correspondingly, the second sending module 305 is specifically configured to send the target history message to the first terminal device according to the obtaining request.
Further, the server may further include:
a deleting module 406, configured to delete the stored target history message after the second sending module 305 sends the target history message to the first terminal device according to the obtaining request.
It can be seen that the deletion module 406 deletes the stored target history message, considering that the target history message is already stored locally at the second terminal device and that the target history message is leaked in order to avoid the server being attacked.
Further, the server may further include:
a fifth sending module 407, configured to send the target history message to the first terminal device if the target history message corresponding to the query request is stored locally.
Fig. 9 is a schematic diagram of a server 500 according to an embodiment of the present invention, where the server 500 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 522 (e.g., one or more processors) and a memory 532, and one or more storage media 530 (e.g., one or more mass storage devices) for storing applications 542 or data 544. Memory 532 and storage media 530 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 530 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, the central processor 522 may be configured to communicate with the storage medium 530, and execute a series of instruction operations in the storage medium 530 on the server 500.
The server 500 may also include one or more power supplies 526, one or more wired or wireless network interfaces 550, one or more input-output interfaces 558, and/or one or more operating systems 541, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, and so forth.
The central processor 522 may be used for,
receiving a query request sent by first terminal equipment;
inquiring whether a target history message corresponding to the inquiry request is stored locally;
if not, sending the query request to a second terminal device, wherein the first terminal device and the second terminal device are both terminal devices bound with the same target account;
receiving a target history message sent by second terminal equipment, wherein the target history message is locally inquired by the second terminal equipment according to the inquiry request;
and sending the target history message to the first terminal equipment.
The steps performed by the server in the above embodiments may be based on the server structure shown in fig. 9.
Referring to fig. 10, a terminal device in an embodiment of the present invention is described below by way of an embodiment, where the terminal device in the embodiment of the present invention is a first terminal device in a message query system, the message query system further includes at least one second terminal device and a server, and the terminal device includes:
a first receiving module 601, configured to receive a query request;
the query module 602 is configured to query whether a target history message corresponding to the query request is stored locally;
a sending module 603, configured to send a query request to the server if the query module 602 queries a target history message corresponding to the query request that is not stored locally;
a second receiving module 604, configured to receive a target history message sent by a server, where the target history message is locally queried by the server according to the query request, or the target history message is obtained when the server is not locally queried according to the query request, the server sends the query request to a second terminal device, the second terminal device is locally queried according to the query request, and both the first terminal device and the second terminal device are terminal devices bound with the same target account.
In this embodiment, the first terminal device may perform a query locally, and if the query is not locally performed, the first terminal device may receive the target history message that is queried locally by the server, or when the query is not locally performed by the server, the target history message that is queried locally by the second terminal device is received locally by the second terminal device, so that storage resources of the first terminal device, the second terminal device, and the server can be balanced, and it is avoided that all history messages are stored in a certain single terminal device or server.
Referring to fig. 11, a terminal device in the embodiment of the present invention is a second terminal device in a message query system, where the terminal device includes:
the receiving module 701 is configured to receive an inquiry request sent by a server, where the inquiry request is sent to the server by a first terminal device in advance, and the first terminal device and a second terminal device are both terminal devices bound with a same target account;
the query module 702 is configured to perform query locally according to the query request to obtain a target history message;
a sending module 703, configured to send the target history message to the server, so that the server sends the target history message to the first terminal device.
In this embodiment, since the target history message is not stored in the server, at this time, the server sends the query request to the second terminal device, and then the server receives the target history message sent by the second terminal device, where the target history message is queried locally by the second terminal device according to the query request, which indicates that the target history message is stored in the second terminal device. Obviously, compared with the prior art that all the history messages of the user are stored in the server, the technical scheme of the invention can share and store a part of the history messages through the second terminal device, so that the storage resource of the server is saved.
As shown in fig. 12, for convenience of description, only a part related to the embodiment of the present invention is shown, and details of the method according to the embodiment of the present invention are not disclosed. The terminal device may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (Personal Digital Assistant, PDA for short), a Point of sale terminal (POS for short), a vehicle-mounted computer, and the like, taking the terminal device as a mobile phone:
fig. 12 is a block diagram showing a partial structure of a cellular phone related to a terminal device provided in an embodiment of the present invention. Referring to fig. 12, the handset includes: radio Frequency (RF) circuit 810, memory 820, input unit 830, display unit 840, sensor 850, audio circuit 860, wireless fidelity (WiFi) module 870, processor 880, and power supply 890. Those skilled in the art will appreciate that the handset configuration shown in fig. 12 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile phone in detail with reference to fig. 12:
the RF circuit 810 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing downlink information of a base station after receiving the downlink information to the processor 880; in addition, data for designing uplink is transmitted to the base station. In general, RF circuit 810 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (Low Noise Amplifier, LNA), a duplexer, and the like. In addition, the RF circuitry 810 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), long Term Evolution (LTE), e-mail, short message Service (Short SMS), and so on.
The memory 820 may be used to store software programs and modules, and the processor 880 executes various functional applications and data processing of the cellular phone by operating the software programs and modules stored in the memory 820. The memory 820 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 820 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 830 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 830 may include a touch panel 831 and other input devices 832. The touch panel 831, also referred to as a touch screen, can collect touch operations of a user (e.g., operations of the user on the touch panel 831 or near the touch panel 831 using any suitable object or accessory such as a finger, a stylus, etc.) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 831 may include two portions, i.e., a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts it to touch point coordinates, and sends the touch point coordinates to the processor 880, and can receive and execute commands from the processor 880. In addition, the touch panel 831 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 830 may include other input devices 832 in addition to the touch panel 831. In particular, other input devices 832 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 840 may be used to display information input by the user or information provided to the user and various menus of the cellular phone. The Display unit 840 may include a Display panel 841, and the Display panel 841 may be optionally configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, touch panel 831 can overlay display panel 841, and when touch panel 831 detects a touch operation thereon or nearby, communicate to processor 880 to determine the type of touch event, and processor 880 can then provide a corresponding visual output on display panel 841 based on the type of touch event. Although in fig. 12, the touch panel 831 and the display panel 841 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 831 and the display panel 841 may be integrated to implement the input and output functions of the mobile phone.
The handset may also include at least one sensor 850, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 841 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 841 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing gestures of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometers and taps), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the WiFi module 870, and provides wireless broadband Internet access for the user. Although fig. 12 shows WiFi module 870, it is understood that it does not belong to the essential constitution of the handset, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The processor 880 is a control center of the mobile phone, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 820 and calling data stored in the memory 820. Optionally, processor 880 may include one or more processing units; preferably, the processor 880 may integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a modem processor, which mainly handles wireless communication. It will be appreciated that the modem processor described above may not be integrated into processor 880.
The handset also includes a power supply 890 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 880 via a power management system to manage charging, discharging, and power consumption.
Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.
In this embodiment of the present invention, when the terminal device is a first terminal device, the processor 880 included in the terminal device further has the following functions: receiving a query request; inquiring whether a target history message corresponding to the inquiry request is stored locally; if not, sending a query request to the server; receiving a target history message sent by a server, wherein the target history message is inquired locally by the server according to an inquiry request, or the target history message is obtained when the server is not inquired locally according to the inquiry request, the server sends the inquiry request to a second terminal device, the second terminal device is inquired locally according to the inquiry request, and the first terminal device and the second terminal device are both terminal devices bound with the same target account number.
In this embodiment of the present invention, when the terminal device is a second terminal device, the processor 880 included in the terminal device further has the following functions: receiving an inquiry request sent by a server, wherein the inquiry request is sent to the server by a first terminal device in advance, and the first terminal device and a second terminal device are both terminal devices bound with the same target account number; inquiring locally according to the inquiry request to obtain a target historical message; and sending the target history message to the server so that the server sends the target history message to the first terminal equipment.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is substantially or partly contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (17)
1. A message query method, comprising:
the server receives an inquiry request sent by first terminal equipment; the query request is generated based on query keywords input by a user;
the server inquires whether a target history message corresponding to the inquiry request is stored locally;
if not, the server sends the query request to second terminal equipment; the first terminal device and the second terminal device are both terminal devices bound with the same target account;
the server receives the target history message sent by the second terminal device; the target history message is locally inquired by the second terminal equipment according to the inquiry request;
the server sends the target history message to the first terminal equipment; the target history message corresponds to the query keyword.
2. The method of claim 1, wherein before the server sends the query request to the second terminal device, the method further comprises:
the server judges whether the target account is logged in the second terminal device or not;
the server sending the query request to the second terminal device includes:
and if the target account number is logged on the second terminal device, the server sends the query request to the second terminal device.
3. The method of claim 2, further comprising:
if the target account is not logged in the second terminal device, the server sends a first indication message to the second terminal device, wherein the first indication message is used for indicating that the target account is logged in the second terminal device.
4. The method according to any one of claims 1 to 3, wherein before the server sends the target history message to the first terminal device, the method further comprises:
the server stores the target history message;
the server sends a second indication message to the first terminal device;
the server receives an acquisition request of the first terminal device for the target historical message according to the second indication message;
the server sending the target history message to the first terminal device includes:
and the server sends the target history message to the first terminal equipment according to the acquisition request.
5. The method according to claim 4, wherein after the server sends the target history message to the first terminal device according to the obtaining request, the method further comprises:
the server deletes the stored target history message.
6. The method of claim 1, further comprising:
and if the server inquires that the target history message corresponding to the inquiry request is locally stored, the server sends the target history message to the first terminal equipment.
7. A message query method, comprising:
a first terminal device receives a query request; the query request is generated based on a query keyword input by a user;
the first terminal equipment inquires whether a target history message corresponding to the inquiry request is stored locally;
if not, the first terminal equipment sends the query request to a server;
the first terminal device receives the target history message sent by the server, wherein the target history message is locally queried by the server according to the query request, or the target history message is sent by the server to a second terminal device when the server is not locally queried according to the query request, the second terminal device is locally queried according to the query request, and the first terminal device and the second terminal device are both terminal devices bound with the same target account number; the target history message corresponds to the query keyword.
8. A message query method, comprising:
the second terminal equipment receives a query request sent by the server; the query request is sent to the server by a first terminal device in advance, and the first terminal device and the second terminal device are both terminal devices bound with the same target account; the query request is generated based on a query keyword input by a user;
the second terminal equipment locally queries according to the query request to obtain a target historical message;
the second terminal device sends the target history message to the server, so that the server sends the target history message to the first terminal device; the target history message corresponds to the query keyword.
9. A server, comprising:
the first receiving module is used for receiving a query request sent by first terminal equipment; the query request is generated based on query keywords input by a user;
the query module is used for querying whether a target historical message corresponding to the query request is stored locally;
the first sending module is used for sending the query request to the second terminal equipment if the query module queries that the target history message corresponding to the query request is not stored locally; the first terminal device and the second terminal device are both terminal devices bound with the same target account;
a second receiving module, configured to receive the target history message sent by the second terminal device, where the target history message is locally queried by the second terminal device according to the query request;
a second sending module, configured to send the target history message to the first terminal device; the target history message corresponds to the query keyword.
10. The server of claim 9, further comprising:
the judging module is used for judging whether the target account number is logged on the second terminal equipment or not before the first sending module sends the query request to the second terminal equipment;
the first sending module is specifically configured to send the query request to the second terminal device if the target account is already logged in the second terminal device.
11. The server according to claim 10, wherein the server further comprises:
a third sending module, configured to send a first indication message to the second terminal device if the target account is not logged in the second terminal device, where the first indication message is used to indicate that the target account is logged in the second terminal device.
12. A server according to any of claims 9 to 11, further comprising:
a storage module, configured to store the target history message before the second sending module sends the target history message to the first terminal device;
a fourth sending module, configured to send a second indication message to the first terminal device;
a third receiving module, configured to receive an acquisition request of the first terminal device for the target history message according to the second indication message;
the second sending module is specifically configured to send the target history message to the first terminal device according to the obtaining request.
13. The server according to claim 12, wherein the server further comprises:
and the deleting module is used for deleting the stored target history message after the second sending module sends the target history message to the first terminal equipment according to the acquisition request.
14. A terminal device for use as a first terminal device, comprising:
the first receiving module is used for receiving the query request; the query request is generated based on a query keyword input by a user;
the query module is used for querying whether a target historical message corresponding to the query request is stored locally;
the sending module is used for sending the query request to a server if the query module queries a target history message corresponding to the query request which is not stored locally;
a second receiving module, configured to receive the target history message sent by the server, where the target history message is obtained by the server according to the query request in a local area, or the target history message is obtained by sending the query request to a second terminal device by the server when the server does not obtain the query request in the local area according to the query request, where the second terminal device obtains the query request in the local area according to the query request, and both the first terminal device and the second terminal device are terminal devices bound with a same target account number; the target history message corresponds to the query keyword.
15. A terminal device for use as a second terminal device, comprising:
the receiving module is used for receiving a query request sent by the server; the query request is sent to the server by a first terminal device in advance, and the first terminal device and the second terminal device are both terminal devices bound with the same target account; the query request is generated based on a query keyword input by a user;
the query module is used for locally querying according to the query request to obtain a target historical message;
a sending module, configured to send the target history message to the server, so that the server sends the target history message to the first terminal device; the target history message corresponds to the query keyword.
16. A computer-readable storage medium having stored thereon operating instructions that, when executed by a processor, implement the message query method of any one of claims 1-8.
17. A terminal, comprising:
at least one processor, and at least one memory, bus connected with the processor;
the processor and the memory complete mutual communication through the bus; the processor is configured to invoke the operating instructions in the memory to perform the message query method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282358.1A CN108804434B (en) | 2017-04-26 | 2017-04-26 | Message query method, server and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710282358.1A CN108804434B (en) | 2017-04-26 | 2017-04-26 | Message query method, server and terminal equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108804434A CN108804434A (en) | 2018-11-13 |
| CN108804434B true CN108804434B (en) | 2022-12-27 |
Family
ID=64068901
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710282358.1A Active CN108804434B (en) | 2017-04-26 | 2017-04-26 | Message query method, server and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108804434B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112311652B (en) * | 2019-07-23 | 2023-02-07 | 腾讯科技（深圳）有限公司 | Message sending method, device, terminal and storage medium |
| CN111786750A (en) * | 2020-06-30 | 2020-10-16 | 深圳前海微众银行股份有限公司 | Message query method and message receiving terminal |
| CN113158002A (en) * | 2021-04-28 | 2021-07-23 | 北京达佳互联信息技术有限公司 | Searching method, searching device, electronic equipment and storage medium |
| CN114691898A (en) * | 2022-03-10 | 2022-07-01 | 北京旷视科技有限公司 | Image query method, terminal device, system and computer-readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101257375A (en) * | 2006-12-31 | 2008-09-03 | 华为技术有限公司 | Method and device for realizing multi-terminal message synchronization |
| WO2014019386A1 (en) * | 2012-08-02 | 2014-02-06 | 华为技术有限公司 | Message sending and receiving method, device and system |
| CN103747017A (en) * | 2014-01-28 | 2014-04-23 | 北京智谷睿拓技术服务有限公司 | Service information interaction method and equipment |
| CN104022938A (en) * | 2013-02-28 | 2014-09-03 | 腾讯科技（深圳）有限公司 | Message synchronization method, system, server and client end |
| CN105631303A (en) * | 2015-12-22 | 2016-06-01 | 广州三星通信技术研究有限公司 | Data acquisition method, electronic terminal used for data acquisition, data supply method, electronic terminal used for data supply, search implementation method and electronic terminal used for search implementation |
| WO2016169441A1 (en) * | 2015-04-23 | 2016-10-27 | 阿里巴巴集团控股有限公司 | Message pushing method and apparatus |
| CN106330684A (en) * | 2016-09-14 | 2017-01-11 | 广东欧珀移动通信有限公司 | Information synchronization method and terminal |
| WO2017028577A1 (en) * | 2015-08-19 | 2017-02-23 | 腾讯科技（深圳）有限公司 | Method and apparatus for displaying group chat content |
-
2017
- 2017-04-26 CN CN201710282358.1A patent/CN108804434B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101257375A (en) * | 2006-12-31 | 2008-09-03 | 华为技术有限公司 | Method and device for realizing multi-terminal message synchronization |
| WO2014019386A1 (en) * | 2012-08-02 | 2014-02-06 | 华为技术有限公司 | Message sending and receiving method, device and system |
| CN104022938A (en) * | 2013-02-28 | 2014-09-03 | 腾讯科技（深圳）有限公司 | Message synchronization method, system, server and client end |
| CN103747017A (en) * | 2014-01-28 | 2014-04-23 | 北京智谷睿拓技术服务有限公司 | Service information interaction method and equipment |
| WO2016169441A1 (en) * | 2015-04-23 | 2016-10-27 | 阿里巴巴集团控股有限公司 | Message pushing method and apparatus |
| WO2017028577A1 (en) * | 2015-08-19 | 2017-02-23 | 腾讯科技（深圳）有限公司 | Method and apparatus for displaying group chat content |
| CN105631303A (en) * | 2015-12-22 | 2016-06-01 | 广州三星通信技术研究有限公司 | Data acquisition method, electronic terminal used for data acquisition, data supply method, electronic terminal used for data supply, search implementation method and electronic terminal used for search implementation |
| CN106330684A (en) * | 2016-09-14 | 2017-01-11 | 广东欧珀移动通信有限公司 | Information synchronization method and terminal |
Non-Patent Citations (2)
| Title |
|---|
| How to Add Message History to your Pusher Apps;Phil Leggetter;《https://blog.pusher.com/how-to-add-message-history-to-your-pusher-apps/》;20150905;1-6 * |
| 基于手机通讯录的移动社交网络服务器的研究与实现;苏志毅;《中国优秀硕士学位论文全文数据库 (信息科技辑)》;20110915(第9期);I136-643 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108804434A (en) | 2018-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104518953B (en) | Method for deleting message, instant communication terminal and system | |
| CN109445917B (en) | Application processing method and device, electronic equipment and computer readable storage medium | |
| CN108804434B (en) | Message query method, server and terminal equipment | |
| CN108834132B (en) | Data transmission method and equipment and related medium product | |
| CN110597793A (en) | Data management method and device, electronic equipment and computer readable storage medium | |
| CN106230703A (en) | The process of chat record and acquisition methods and device | |
| US10298590B2 (en) | Application-based service providing method, apparatus, and system | |
| CN106791185A (en) | Method for managing contact person information, device and mobile terminal | |
| CN110532231B (en) | File query method, file query device and terminal equipment | |
| CN103383701A (en) | Information retrieving method, device and terminal | |
| CN106020945B (en) | Shortcut item adding method and device | |
| CN111314900B (en) | Wireless connection method, wireless connection device and mobile terminal | |
| CN107220073A (en) | A kind of information updating method and user equipment | |
| CN110602766B (en) | Personal hotspot identification method and method for determining association relationship between terminals | |
| CN106339402B (en) | Method, device and system for pushing recommended content | |
| CN106201536A (en) | The replacing options of a kind of application icon and terminal unit | |
| CN111274463A (en) | Information display method and device based on IM contact person grouping setting and storage medium | |
| CN112445967A (en) | Information push method and device, readable storage medium and information push system | |
| CN106777383B (en) | File sorting method and intelligent terminal | |
| CN115904179A (en) | Multi-screen desktop split-screen display method, device, equipment and storage medium | |
| CN107800880B (en) | Method, device, mobile terminal and storage medium for displaying number of unread messages | |
| CN109002535B (en) | Data updating method and device | |
| CN106487649A (en) | The prompting control method of group message and terminal unit | |
| CN106879046B (en) | Network scanning method and terminal equipment | |
| CN112214699A (en) | Page processing method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TG01 | Patent term adjustment |