CN105337926A - Multi-terminal linkage method and system, and associated equipment - Google Patents
Multi-terminal linkage method and system, and associated equipment Download PDFInfo
- Publication number
- CN105337926A CN105337926A CN201410273165.6A CN201410273165A CN105337926A CN 105337926 A CN105337926 A CN 105337926A CN 201410273165 A CN201410273165 A CN 201410273165A CN 105337926 A CN105337926 A CN 105337926A
- Authority
- CN
- China
- Prior art keywords
- client
- linkage
- protocol packet
- current operation
- behavior information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000004806 packaging method and process Methods 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 6
- 230000000694 effects Effects 0.000 abstract description 16
- 230000001360 synchronised effect Effects 0.000 abstract description 11
- 230000006399 behavior Effects 0.000 description 111
- 238000010586 diagram Methods 0.000 description 16
- 238000004590 computer program Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Landscapes
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a multi-terminal linkage method and system, and associated equipment. According to the scheme, when a first client receives a linkage operation instruction, obtained current operation behavior information, containing current operation interface information as well as current context description information, from an operation user of the first client is packaged into a linkage protocol packet; the packaged linkage protocol packet is forwarded to at least one second client associated with the first client by a server, so that the at least one second client reconstructs and displays the current operation behavior information of the operation user according to the received linkage protocol packet. Therefore, a problem that the operation interfaces and context description before and after switching are not synchronized when switching among different terminals is carried out by the user can be solved; the switching smoothness and continuity are improved during switching among different terminals; and an objective of improvement of a multi-end linkage effect can be achieved.
Description
Technical Field
The present application relates to the field of mobile communications technologies, and in particular, to a multi-terminal linkage method, and a related device and system.
Background
With the increasing popularity of mobile terminals, users often need to switch between different terminals, such as PC (personal computer) terminals and mobile terminals. In order to keep the consistency of user data before and after switching when a user switches between different terminals, a technical scheme of multi-terminal linkage is proposed in the industry, wherein the multi-terminal linkage can synchronize the user data (such as a message) of the user on one terminal to another terminal.
However, in the current multi-terminal linkage technical solution, multi-terminal synchronization of user data can only be achieved, so that when a user switches between different terminals, an operation interface before and after switching, context description, and the like cannot be synchronized, switching smoothness and continuity when switching between different terminals are reduced, and a linkage effect is not good. Therefore, it is desirable to provide a new multi-end linkage scheme to solve the above technical problems.
Disclosure of Invention
The embodiment of the application provides a multi-end linkage method, and related equipment and system, which are used for solving the problem that the linkage effect of multi-end linkage is poor at present.
The embodiment of the application provides a multi-end linkage method, which comprises the following steps:
the method comprises the steps that when a first client receives a linkage operation instruction, current operation behavior information of an operation user of the first client is obtained, wherein the current operation behavior information comprises current operation interface information and current context description information; and are
And packaging the obtained current operation behavior information into a linkage protocol packet, sending the linkage protocol packet to a server, and forwarding the received linkage protocol packet to at least one second client associated with the first client by the server, so that the at least one second client obtains the current operation behavior information according to the received linkage protocol packet, and reconstructs and displays the current operation behavior information on the at least one second client.
Further, the embodiment of the present application further provides another multi-end linkage method, including:
the method comprises the steps that a server receives a linkage protocol packet sent by a first client, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; and are
And forwarding the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet, reconstructs the current operation behavior information on the at least one second client and displays the current operation behavior information.
Further, the embodiment of the present application further provides another multi-end linkage method, including:
the method comprises the steps that a second client receives a linkage protocol packet from a first client forwarded by a server, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; and are
Acquiring the current operation behavior information contained in the linkage protocol packet according to the received linkage protocol packet, and reconstructing and displaying the current operation behavior information on the second client; wherein the first client is a client associated with the second client.
Correspondingly, an embodiment of the present application provides a client, including:
the receiving module is used for receiving a linkage operation instruction;
the obtaining module is used for obtaining current operation behavior information of an operation user of the client when a linkage operation instruction is received, wherein the current operation behavior information comprises current operation interface information and current context description information;
and the sending module is used for packaging the obtained current operation behavior information into a linkage protocol packet and then sending the linkage protocol packet to a server, and the server forwards the received linkage protocol packet to at least one other client associated with the client, so that the at least one other client obtains the current operation behavior information according to the received linkage protocol packet and reconstructs and displays the current operation behavior information on the at least one other client.
Further, an embodiment of the present application further provides a server, including:
the system comprises a receiving module and a processing module, wherein the receiving module is used for receiving a linkage protocol packet sent by a first client, the linkage protocol packet is obtained by encapsulating the obtained current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information;
and the sending module is used for forwarding the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet, reconstructs the current operation behavior information on the at least one second client and displays the current operation behavior information.
Further, an embodiment of the present application further provides another client, including:
the receiving module is used for receiving a linkage protocol packet from other clients forwarded by the server, wherein the linkage protocol packet is obtained by encapsulating the obtained current operation behavior information of the operation users of the other clients when the other clients receive a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; wherein the other clients are clients associated with the client;
the acquisition module is used for acquiring the current operation behavior information contained in the linkage protocol packet according to the received linkage protocol packet;
and the reconstruction module is used for reconstructing and displaying the current operation behavior information on the client.
Further, an embodiment of the present application further provides a multi-end linkage system, which includes at least one first client, a server, and at least one second client, where the second client is a client associated with the first client:
the first client is used for acquiring current operation behavior information of an operation user of the first client when a linkage operation instruction is received, packaging the acquired current operation behavior information into a linkage protocol packet, and sending the linkage protocol packet to a server, wherein the current operation behavior information comprises current operation interface information and current context description information;
the server is used for forwarding the received linkage protocol packet to at least one second client;
and the second client is used for acquiring the current operation behavior information according to the received linkage protocol packet, reconstructing the current operation behavior information on the second client and displaying the current operation behavior information.
The beneficial effect of this application is as follows:
in the technical scheme of the embodiment of the application, when a first client receives a linkage operation instruction, a first client can package current operation behavior information of an operation user of the first client, including current operation interface information and current context description information, into a linkage protocol packet and then forward the linkage protocol packet to at least one second client associated with the first client through a server, so that the at least one second client reconstructs and displays the current operation behavior information according to the received linkage protocol packet, the problem that the operation interfaces, context descriptions and the like before and after switching cannot be synchronized when the user switches between different terminals at present is solved, and on the basis of improving switching smoothness and continuity when the user switches between different terminals, the linkage of the user operation interface and the context can be realized to recover the final state of the user at other terminals, and the linkage effect of multi-terminal linkage is further improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart illustrating a multi-end linkage method according to a first embodiment of the present application;
fig. 2 is a schematic flow chart illustrating a multi-end linkage method according to a second embodiment of the present application;
fig. 3 is a schematic specific flowchart of the multi-end linkage method according to the second embodiment of the present application;
fig. 4 is a schematic flow chart illustrating a multi-end linkage method according to a third embodiment of the present application;
fig. 5 is a schematic structural diagram of the client according to the fourth embodiment of the present application;
fig. 6 is a schematic structural diagram of the server according to the fifth embodiment of the present application;
fig. 7 is a schematic structural diagram of the client according to a sixth embodiment of the present application;
fig. 8 is a schematic structural diagram of the multi-end linkage system according to the seventh embodiment of the present application.
Detailed Description
In the technical scheme of the embodiment of the application, when a first client receives a linkage operation instruction, a first client can package current operation behavior information of an operation user of the first client, including current operation interface information and current context description information, into a linkage protocol packet and then forward the linkage protocol packet to at least one second client associated with the first client through a server, so that the at least one second client reconstructs and displays the current operation behavior information according to the received linkage protocol packet, the problem that the operation interfaces, context descriptions and the like before and after switching cannot be synchronized when the user switches between different terminals at present is solved, and on the basis of improving switching smoothness and continuity when the user switches between different terminals, the linkage of the user operation interface and the context can be realized to recover the final state of the user at other terminals, and the linkage effect of multi-terminal linkage is further improved.
In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The first embodiment is as follows:
as shown in fig. 1, which is a schematic flow chart of the multi-end linkage method according to the first embodiment of the present application, the multi-end linkage method may include the following steps:
step 101: the method comprises the steps that when a first client receives a linkage operation instruction, current operation behavior information of an operation user of the first client is obtained, wherein the current operation behavior information comprises current operation interface information and current context description information.
In particular, in the embodiments described herein, the first client may generally be an instant messaging client. It should be noted that the first client may also be another client, such as an email client or a web browser, and may even be a terminal device relative to the server device, such as a PC terminal or a mobile terminal, which is not limited in this embodiment of the present application.
Further, taking the first client as an instant messaging client as an example, the first client may be a client disposed in a terminal device such as a PC terminal or a mobile terminal. Accordingly, the operation user of the first client may generally be an operation user corresponding to an account used when the first client logs in, which is not described in this embodiment of the present application.
Further, in the embodiment of the present application, the linkage operation instruction may be initiated by the operation user to the first client; alternatively, the server connected to the first client may also initiate to the first client. It is to be understood that, in the embodiments of the present application, a main body for initiating the linkage operation command may not be limited.
Specifically, the operating user can initiate a corresponding linkage operation instruction to the first client when determining that the operating user needs to log in on other clients through an account used by the first client when logging in; or, the operating user may also initiate a corresponding linkage operation instruction to the first client when determining that the operating user needs to suspend the corresponding user operation performed by using the first client, which is not limited in the embodiment of the present application. Similarly, the server may initiate a corresponding linkage operation instruction to the first client when determining that there are other clients logged in using the account used by the first client in logging in. It can be understood that, in the embodiment of the present application, a timing for initiating the linkage operation instruction may not be limited.
Further, in the embodiment of the present application, when receiving the linkage operation instruction, the first client may obtain current operation behavior information of the operation user of the first client by triggering a plug-in that is set in an operation interface when the operation user uses the first client to perform a user operation (here, the current operation behavior information may generally refer to a time or a time period when the first client receives the linkage operation instruction, or, in consideration of a negligible time difference between receiving the linkage operation instruction and obtaining the operation behavior information, the current operation behavior information may also refer to a time or a time period when the first client starts to execute obtaining corresponding operation behavior information according to the received linkage operation instruction).
Further, it should be noted that the current operation behavior information may generally be operation behavior information currently implemented by an operation user facing the first client, that is, relevant behavior information of an operation implemented by the operation user through the human-computer interaction interface of the first client.
Further, the current operation behavior information may include current operation interface information and current Context (Context) description information. Wherein the current operation interface information may generally include user-sensible interface information, such as at least one or more of the following: user interface data information, operation focus information, and window position information.
The user interface data information generally includes some text (for example, input content of an input box) on a UI (user interface) and/or data in user options (for example, a checkbox selection result, where the checkbox is a check box on a screen, and the like), and the emphasis is mainly on the representation on the UI.
The operation focus information typically includes the object that the user is currently operating, i.e., on which UI element or elements the user is currently focused. Wherein the UI element generally refers to a UI control, etc.
The window position information typically includes a current window display area; for example, if the user is currently operating a longer scrollview or list view, the window position information may refer to a region or a position of the scrollview or list view where the user is currently operating.
Further, the current context description information in the current operation behavior information generally includes information that is not embodied on a user interface and is not necessarily directly perceptible to a user, such as at least one or more of the following information: program configuration information and environment configuration information, wherein: the program configuration information may be program configuration information such as whether to play sound, whether to shake a reminder, whether to be in a stealth state, and the environment configuration information may be environment configuration information such as a current location of a user, a current network condition, and the like.
It should be further noted that the current operation behavior information acquired by the first client may include, in addition to the current operation interface information and the current context description information, information such as current user data (e.g., chat information or pictures) of the operation user.
Step 102: and the first client packages the acquired current operation behavior information into a linkage protocol packet and then sends the linkage protocol packet to a server, and the server forwards the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet and reconstructs and displays the current operation behavior information on the at least one second client.
Specifically, the second client associated with the first client may be a client that logs in with the first client by using the same account number and thus has a corresponding association relationship; alternatively, the first client may be a client that has a corresponding association relationship by being bound to the first client (for example, by binding the clients to each other according to a set service requirement), and the like, which is not limited in this embodiment of the present application. Further, when the second client is a client that is bound to the first client and has a corresponding association relationship, the second client may be a client that does not use the same account to log in with the first client, or the second client and the first client may be clients that do not need to log in with accounts, which is not limited in this embodiment of the present application.
Further, the second client may typically be a client of the same type as the first client, e.g., when the first client is an instant messaging client, the second client may also typically be a corresponding instant messaging client; when the first client is other types of clients such as an email client, the second client may also be other types of clients such as a corresponding email client. It should be noted that, when the first client and the second client are instant messaging clients, the first client and the second client may be respectively disposed in different terminal devices, for example, the first client may be an instant messaging client disposed in a PC terminal, and the second client may be an instant messaging client disposed in a mobile terminal, and the like, which is not limited in this embodiment of the present application.
Further, it should be noted that, when the first client and the second client are instant messaging clients respectively, the server may be an instant messaging server generally, which is not described in detail in this embodiment of the present application.
Further, in the embodiment of the present application, taking the first and second clients as instant messaging clients and taking the server as an instant messaging server as an example, the first client may package the acquired current operation behavior information into a linkage protocol packet and then send the linkage protocol packet to the server by the following means:
and packaging the acquired current operation behavior information into an application layer secondary protocol packet (for example, into a ServerMessageTypeSyncScreen application layer secondary protocol packet), packaging the application layer secondary protocol packet into an original instant messaging primary protocol packet (namely, an IM _ NTF _ IMMESSAGE primary protocol packet) to form a linkage protocol packet, and then sending the linkage protocol packet to the server through an instant messaging channel (namely, an IM channel).
That is to say, the technical scheme of the application can be realized by extending a secondary application layer protocol on the basis of the existing instant messaging technology, so that the method has the characteristics of short development period, high usability and the like, and can inherit the characteristics of instantaneity, reliability, accuracy and the like of the instant messaging technology, thereby further achieving the purpose of improving the multi-terminal linkage effect.
It should be noted that the technical solution described in the embodiment of the present application is specifically applicable to mainstream smart mobile operating systems ios, android, windows, and the like (that is, the best hardware may be a smart phone equipped with an operating system such as android or ios, or a PC computer equipped with a window, and the like). The optimal programming language in the embodiment of the application can be C, C + +, and the like, so that the purpose of further improving the application range and the practicability of the multi-end linkage can be achieved.
In the technical solution of the first embodiment of the present application, when receiving a linkage operation instruction, a first client may encapsulate current operation behavior information, including current operation interface information and current context description information, of an operation user of the first client into a linkage protocol packet, and forward the linkage protocol packet to at least one second client associated with the first client through a server, so that the at least one second client reconstructs and displays the current operation behavior information according to the received linkage protocol packet, thereby solving a problem that the operation interfaces, context descriptions, and the like before and after switching cannot be synchronized when the user switches between different terminals, and on the basis of improving switching smoothness and continuity when switching between different terminals, the linkage of the user operation interface and the context can be realized to recover the final state of the user at other terminals, and the linkage effect of multi-terminal linkage is further improved.
Example two:
in the second embodiment of the present application, the action executing party is taken as an example of a server, and the multi-end linkage method in the first embodiment of the present application is further described. Specifically, as shown in fig. 2, the multi-end linkage method may include the steps of:
step 201: the method comprises the steps that a server receives a linkage protocol packet sent by a first client, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information.
Specifically, the server may receive the linkage protocol packet sent by the first client through an instant messaging channel, where the linkage protocol packet is obtained by the first client packaging the acquired current operation behavior information into an application layer secondary protocol packet and encapsulating the application layer secondary protocol packet into an instant messaging primary protocol packet.
That is to say, the technical scheme of the application can be realized by extending a secondary application layer protocol on the basis of the existing instant messaging technology, so that the method has the characteristics of short development period, high usability and the like, and can inherit the characteristics of instantaneity, reliability, accuracy and the like of the instant messaging technology, thereby further achieving the purpose of improving the multi-terminal linkage effect.
Step 202: and the server forwards the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet, reconstructs the current operation behavior information on the at least one second client and displays the current operation behavior information.
The second client associated with the first client can be a client which logs in with the first client by using the same account number so as to have a corresponding association relation; alternatively, the first client may be a client that is bound to the first client and has a corresponding association relationship, and the like, which is not limited in this embodiment of the application.
Further, in the embodiment described in this application, as shown in fig. 3, after receiving the linkage protocol packet, the server may forward the linkage protocol packet to at least one second client by:
judging whether at least one logged second client exists currently (in a certain set time period, the current time is the time when the server receives the linkage protocol packet or the time when the server receives the linkage protocol packet), namely judging whether at least one online second client exists currently or a second client connected with the server exists currently, and if the judgment result is yes, forwarding the linkage protocol packet to one or more second clients in the at least one logged second client through an instant communication channel or in a Push (Push) mode; or,
if the judgment result is negative, namely the fact that the logged second client does not exist currently is determined, the linkage protocol packet is stored in an offline server, and after the offline server determines that at least one second client is changed from the offline state to the logged state, the linkage protocol packet is forwarded to one or more second clients in the at least one second client changed from the offline state to the logged state through an instant messaging channel or by adopting a Push mode and the like.
In the second technical solution of the second embodiment of the present application, after receiving a linkage protocol packet sent by a first client, a server may forward the linkage protocol packet to at least one second client associated with the first client, so that the at least one second client obtains current operation behavior information of an operation user of the first client carried in the linkage protocol packet according to the received linkage protocol packet and reconstructs and displays the current operation behavior information on the at least one second client, thereby solving a problem that an operation interface, context description and the like before and after switching cannot be synchronized when a user switches between different terminals, and on the basis of improving switching smoothness and continuity when switching between different terminals, the linkage of the user operation interface and the context can be realized to recover the final state of the user at other terminals, and the linkage effect of multi-terminal linkage is further improved.
Example three:
in the third embodiment of the present application, an action executing party is taken as a second client (i.e., a client that does not receive the linkage operation instruction) as an example, and the multi-terminal linkage method in the first embodiment of the present application is further described. Specifically, as shown in fig. 4, the multi-end linkage method may include the steps of:
step 301: the method comprises the steps that a second client receives a linkage protocol packet from a first client forwarded by a server, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; wherein the first client is a client associated with the second client.
Specifically, the first client associated with the second client may be a client that logs in with the second client by using the same account number and thus has a corresponding association relationship; alternatively, the second client may be a client that is bound to the second client and has a corresponding association relationship, and the like, which is not limited in this embodiment of the application.
Further, in the embodiment described in the present application, the second client may receive the linkage protocol packet forwarded by the server from the first client by:
receiving the linkage protocol packet forwarded by the server through an instant messaging channel or in a Push mode; or receiving the linkage protocol packet forwarded by the offline server through an instant communication channel or in a Push mode. The linkage protocol packet forwarded by the offline server is forwarded to the offline server when the server receives the linkage protocol packet sent by the first client and determines that the logged-in second client does not exist currently, which is not described in detail herein.
Step 302: and the second client acquires the current operation behavior information contained in the linkage protocol packet according to the received linkage protocol packet, and reconstructs and displays the current operation behavior information on the second client.
Specifically, after receiving the linkage protocol packet, the second client may perform protocol analysis on the linkage protocol packet to obtain the current operation behavior information included in the linkage protocol packet. Further, after the second client acquires the current operation behavior information, the second client may reconstruct, according to current operation interface information and current context description information and the like included in the current operation behavior information, operation behavior information consistent with the current operation behavior information on the second client to restore the final state of the operation user at the first client, so that the operation user may continue to engage in corresponding user operations that are not completed on the first client by the operation user on the second client based on the restored scene, thereby achieving the purpose of improving the linkage effect of multi-end linkage.
In the third technical scheme of the third embodiment of the present application, a second client may obtain current operation behavior information included in a linkage protocol packet according to the linkage protocol packet forwarded by a server from a first client, and reconstruct and display the current operation behavior information on the second client, so as to solve the problem that an operation interface, context description and the like before and after switching cannot be synchronized when a user switches between different terminals at present, and achieve the purpose of realizing linkage of the user operation interface and the context to restore the final state of the user at other terminals and further improve the linkage effect of multi-end linkage on the basis of improving switching smoothness and continuity when switching between different terminals.
Example four:
a fourth embodiment of the present application provides a client capable of implementing the method in the first embodiment of the present application, as shown in fig. 5, which is a schematic structural diagram of the client in the fourth embodiment of the present application, and the client specifically includes a receiving module 51, an obtaining module 52, and a sending module 53, where:
the receiving module 51 may be configured to receive a linkage operation instruction; specifically, the linkage operation instruction received by the receiving module 51 may be initiated by an operation user of the client to the client; or the server connected with the client initiates the client.
The obtaining module 52 may be configured to obtain current operation behavior information of an operation user of the client when a linkage operation instruction is received, where the current operation behavior information includes current operation interface information and current context description information; the current operation behavior information may generally be operation behavior information that is implemented by an operation user currently facing the first client, that is, operation behavior information related to an operation implemented by the operation user through a human-computer interaction interface of the first client. And the current operation interface information included in the current operation behavior information may include at least one or more of the following information: the current context description information included in the current operation behavior information at least may include one or more of the following information: program configuration information, environment configuration information, and the like, which are not limited in this embodiment.
The sending module 53 may be configured to package the obtained current operation behavior information into a linkage protocol packet, and send the linkage protocol packet to a server, where the server forwards the received linkage protocol packet to at least one other client associated with the client, so that the at least one other client obtains the current operation behavior information according to the received linkage protocol packet, and reconstructs and displays the current operation behavior information on the at least one other client.
The other clients related to the client can be clients which log in with the client by using the same account number so as to have corresponding association relation; or the client may be a client that is bound to the client and has a corresponding association relationship, which is not limited in the embodiment of the present application.
Further, the sending module 53 may be specifically configured to package the acquired current operation behavior information into an application layer secondary protocol packet, package the application layer secondary protocol packet into an instant messaging primary protocol packet to form a linkage protocol packet, and send the linkage protocol packet to the server through an instant messaging channel.
That is to say, the technical scheme of the application can be realized by extending a secondary application layer protocol on the basis of the existing instant messaging technology, so that the method has the characteristics of short development period, high usability and the like, and can inherit the characteristics of instantaneity, reliability, accuracy and the like of the instant messaging technology, thereby further achieving the purpose of improving the multi-terminal linkage effect.
Further, it should be noted that, in the embodiment of the present application, the client and the other clients involved may be instant messaging clients respectively, and accordingly, the server may be an instant messaging server, which is not limited in this embodiment of the present application.
The fourth embodiment of the present application provides a client, where when receiving a linkage operation instruction, the client may encapsulate, into a linkage protocol packet, current operation behavior information of an operation user of the client, including current operation interface information and current context description information, and forward the encapsulated operation behavior information to at least one other client associated with the client through a server, so that the at least one other client reconstructs and displays the operation behavior information of the operation user with respect to the client according to the received linkage protocol packet, thereby solving a problem that an operation interface before and after switching, context description, and the like cannot be synchronized when a user switches between different terminals at present, and achieving a purpose of enabling linkage of the operation interface and context of the user to recover a final state, and a final state of the user at the other terminal on the basis of improving switching smoothness and continuity when the user switches between different terminals, And further improve the linkage effect of the multi-end linkage.
Example five:
a fifth embodiment of the present application provides a server capable of implementing the method shown in the second embodiment of the present application, as shown in fig. 6, which is a schematic structural diagram of the server in the fifth embodiment of the present application, and the server specifically includes a receiving module 61 and a sending module 62, where:
the receiving module 61 may be configured to receive a linkage protocol packet sent by a first client, where the linkage protocol packet is obtained by encapsulating, when the first client receives a linkage operation instruction, current operation behavior information of an operation user of the first client, where the current operation behavior information includes current operation interface information and current context description information;
the sending module 62 may be configured to forward the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client obtains the current operation behavior information according to the received linkage protocol packet, and reconstructs and displays the current operation behavior information on the at least one second client.
The second client associated with the first client can be a client which logs in with the first client by using the same account number so as to have a corresponding association relation; alternatively, the first client may be a client that is bound to the first client and has a corresponding association relationship, and the like, which is not limited in this embodiment of the application.
Further, the receiving module 61 may be specifically configured to receive a linkage protocol packet sent by the first client through an instant messaging channel, where the linkage protocol packet is obtained by the first client packaging the acquired current operation behavior information into an application layer secondary protocol packet and encapsulating the application layer secondary protocol packet into an instant messaging primary protocol packet.
The sending module 62 is specifically configured to, if it is determined that at least one logged-in second client exists currently, forward the linkage protocol packet to one or more second clients of the at least one logged-in second client through an instant messaging channel or in a Push manner; or, the method may be specifically configured to, if it is determined that there is no logged-in second client currently, store the linkage protocol packet in an offline server, and after it is determined that there is at least one second client that changes from an offline state to a logged-in state, forward the linkage protocol packet to one or more second clients of the at least one second client that changes from the offline state to the logged-in state through an instant messaging channel or in a Push manner by the offline server.
The fifth embodiment of the present application provides a server, where after receiving a linkage protocol packet sent by a first client, the server may forward the linkage protocol packet to at least one second client associated with the first client, so that the at least one second client obtains, according to the received linkage protocol packet, current operation behavior information of an operation user of the first client carried in the linkage protocol packet, reconstructs and displays the current operation behavior information on the at least one second client, thereby solving a problem that an operation interface before and after switching, context description, and the like cannot be synchronized when a currently existing user switches between different terminals, and achieving a purpose of achieving linkage between the operation interface of the user and the context to recover a final state of the user at other terminals on the basis of improving switching smoothness and continuity when switching between different terminals, And further improve the linkage effect of the multi-end linkage.
Example six:
a sixth embodiment of the present application provides a client capable of implementing the method shown in the third embodiment of the present application, as shown in fig. 7, which is a schematic structural diagram of the client in the sixth embodiment of the present application, and the client specifically includes a receiving module 71, an obtaining module 72, and a reconstructing module 73, where:
the receiving module 71 may be configured to receive a linkage protocol packet from another client forwarded by the server, where the linkage protocol packet is obtained by encapsulating, when the other client receives a linkage operation instruction, the obtained current operation behavior information of an operation user of the other client, where the current operation behavior information includes current operation interface information and current context description information; and the other clients are clients associated with the clients. Specifically, the other clients associated with the client may be clients that log in with the client using the same account number and thus have corresponding association relationships; or the client may be a client that is bound to the client and has a corresponding association relationship, which is not limited in the embodiment of the present application.
The obtaining module 72 may be configured to obtain the current operation behavior information included in the linkage protocol packet according to the received linkage protocol packet;
the reconstruction module 73 may be configured to reconstruct and display the current operation behavior information on the client.
Specifically, the receiving module 71 may be configured to receive the linkage protocol packet forwarded by the server through an instant messaging channel or in a Push manner; or, the method can be used for receiving the linkage protocol packet forwarded by the offline server through an instant messaging channel or in a Push mode.
The sixth embodiment of the application provides a client, wherein the client can acquire current operation behavior information contained in a linkage protocol packet according to the linkage protocol packet forwarded by a server and from other clients, and reconstructs and displays the current operation behavior information on the client, so that the problem that an operation interface before and after switching, context description and the like cannot be synchronized when a user switches between different terminals at present is solved, and on the basis of improving switching smoothness and continuity when switching between different terminals, the aim of realizing linkage of the user operation interface and context so as to recover the final state of the user at other terminals and further improve the linkage effect of multi-terminal linkage is fulfilled.
Example seven:
a seventh embodiment of the present application provides a multi-end linkage system capable of implementing the method shown in any one of the first to third embodiments of the present application, as shown in fig. 8, which is a schematic structural diagram of the multi-end linkage system in the seventh embodiment of the present application, and the system specifically includes at least one first client 81, a server 82, and at least one second client 83, where the second client 83 is a client associated with the first client 81:
the first client 81 may be configured to, when receiving a linkage operation instruction, obtain current operation behavior information of an operation user of the first client 81, package the obtained current operation behavior information into a linkage protocol packet, and send the linkage protocol packet to the server 82, where the current operation behavior information includes current operation interface information and current context description information;
the server 82 is operable to forward the received linkage protocol packet to at least one second client 83;
the second client 83 may be configured to obtain the current operation behavior information according to the received linkage protocol packet, and reconstruct and display the current operation behavior information on the second client 83.
Specifically, the specific structures and functions of the first client 81, the server 82, and the second client 83 may be respectively the same as those of the clients or servers described in the fourth embodiment, the fifth embodiment, and the sixth embodiment of the present application, and details of this embodiment of the present application are not repeated. In addition, the first client 81 may further have a corresponding function of the second client 83, and the second client 83 may further have a corresponding function of the first client 81, which is not described in detail in this embodiment of the application.
The seventh embodiment of the present application provides a multi-end linkage system, where a first client in the multi-end linkage system, when receiving a linkage operation instruction, may encapsulate current operation behavior information, including current operation interface information and current context description information, of an operation user of the first client, into a linkage protocol packet, and forward the linkage protocol packet to at least one second client associated with the first client through a server in the multi-end linkage system, so that the at least one second client reconstructs and displays the operation behavior information of the operation user relative to the first client according to the received linkage protocol packet, thereby solving a problem that the operation interfaces, context descriptions, and the like before and after switching cannot be synchronized when the current user switches between different terminals, and on the basis of improving switching smoothness and continuity when switching between different terminals, the linkage of the user operation interface and the context can be realized to recover the final state of the user at other terminals, and the linkage effect of multi-terminal linkage is further improved.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus (device), or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (27)
1. A multi-end linkage method, comprising:
the method comprises the steps that when a first client receives a linkage operation instruction, current operation behavior information of an operation user of the first client is obtained, wherein the current operation behavior information comprises current operation interface information and current context description information; and are
And packaging the obtained current operation behavior information into a linkage protocol packet, sending the linkage protocol packet to a server, and forwarding the received linkage protocol packet to at least one second client associated with the first client by the server, so that the at least one second client obtains the current operation behavior information according to the received linkage protocol packet, and reconstructs and displays the current operation behavior information on the at least one second client.
2. The multi-end linkage method according to claim 1, wherein the current operation interface information includes at least one or more of the following information: user interface data information, operation focus information and window position information;
the current context description information includes at least one or more of the following information: program configuration information and environment configuration information.
3. The multi-terminal linkage method according to claim 1 or 2, wherein the linkage operation instruction is initiated by the operation user to the first client; or, the server initiates to the first client.
4. The multi-end linkage method according to claim 1 or 2, wherein the first client and the second client are instant messaging clients, respectively; the server is an instant messaging server.
5. The multi-terminal linkage method according to claim 4, wherein the step of encapsulating the acquired current operation behavior information into a linkage protocol packet and sending the linkage protocol packet to a server comprises the steps of:
and packaging the acquired current operation behavior information into an application layer secondary protocol packet, packaging the application layer secondary protocol packet into an instant messaging primary protocol packet to form a linkage protocol packet, and then sending the linkage protocol packet to the server through an instant messaging channel.
6. The multi-end linkage method according to claim 1 or 2, wherein the second client associated with the first client is a client that logs in with the first client using the same account.
7. A multi-end linkage method, comprising:
receiving a linkage protocol packet sent by a first client, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; and are
And forwarding the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet, reconstructs the current operation behavior information on the at least one second client and displays the current operation behavior information.
8. The multi-end linkage method according to claim 7, wherein the server receives the linkage protocol packet sent by the first client, and comprises:
and the server receives a linkage protocol packet sent by the first client through an instant messaging channel, wherein the linkage protocol packet is obtained by the first client packaging the acquired current operation behavior information into an application layer secondary protocol packet and packaging the application layer secondary protocol packet into an instant messaging primary protocol packet.
9. The multi-end linkage method according to claim 7 or 8, wherein forwarding the received linkage protocol packet to at least one second client comprises:
if at least one logged second client is determined to exist currently, the linkage protocol packet is forwarded to one or more second clients in the at least one logged second client through an instant messaging channel or in a Push mode; or,
and if the fact that the logged second client does not exist currently is determined, the linkage protocol packet is stored in an offline server, and after the offline server determines that at least one second client is changed from the offline state to the logged state, the linkage protocol packet is forwarded to one or more second clients in the at least one second client changed from the offline state to the logged state through an instant communication channel or in a Push mode.
10. The multi-end linkage method according to claim 7 or 8, wherein the second client associated with the first client is a client that logs in with the first client using the same account.
11. A multi-end linkage method, comprising:
the method comprises the steps that a second client receives a linkage protocol packet from a first client forwarded by a server, wherein the linkage protocol packet is obtained by encapsulating current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; and are
Acquiring the current operation behavior information contained in the linkage protocol packet according to the received linkage protocol packet, and reconstructing and displaying the current operation behavior information on the second client; wherein the first client is a client associated with the second client.
12. The multi-end linkage method according to claim 11, wherein the second client receives the linkage protocol packet from the first client forwarded by the server, and comprises:
receiving the linkage protocol packet forwarded by the server through an instant communication channel or in a Push mode; or receiving the linkage protocol packet forwarded by the offline server through an instant communication channel or in a Push mode.
13. The multi-end linkage method according to claim 11 or 12, wherein the first client associated with the second client is a client that logs in with the second client using the same account.
14. A client, comprising:
the receiving module is used for receiving a linkage operation instruction;
the obtaining module is used for obtaining current operation behavior information of an operation user of the client when a linkage operation instruction is received, wherein the current operation behavior information comprises current operation interface information and current context description information;
and the sending module is used for packaging the obtained current operation behavior information into a linkage protocol packet and then sending the linkage protocol packet to a server, and the server forwards the received linkage protocol packet to at least one other client associated with the client, so that the at least one other client obtains the current operation behavior information according to the received linkage protocol packet and reconstructs and displays the current operation behavior information on the at least one other client.
15. The client according to claim 14, wherein the current operation interface information acquired by the acquisition module at least includes one or more of the following information: user interface data information, operation focus information and window position information;
the current context description information acquired by the acquisition module at least includes one or more of the following information: program configuration information and environment configuration information.
16. The client according to claim 14 or 15, wherein the linkage operation instruction received by the receiving module is initiated by the operation user to the client; or, the server initiates to the client.
17. The client according to claim 14 or 15, wherein the client and the other clients are instant messaging clients, respectively; the server is an instant messaging server.
18. The client of claim 17,
the obtaining module is specifically configured to package the obtained current operation behavior information into an application layer secondary protocol packet, package the application layer secondary protocol packet into an instant messaging primary protocol packet to form a linkage protocol packet, and send the linkage protocol packet to the server through an instant messaging channel.
19. The client of claim 14 or 15, wherein the second client associated with the first client is a client that is logged in using the same account as the first client.
20. A server, comprising:
the system comprises a receiving module and a processing module, wherein the receiving module is used for receiving a linkage protocol packet sent by a first client, the linkage protocol packet is obtained by encapsulating the obtained current operation behavior information of an operation user of the first client when the first client receives a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information;
and the sending module is used for forwarding the received linkage protocol packet to at least one second client associated with the first client, so that the at least one second client acquires the current operation behavior information according to the received linkage protocol packet, reconstructs the current operation behavior information on the at least one second client and displays the current operation behavior information.
21. The server according to claim 20,
the receiving module is specifically configured to receive a linkage protocol packet sent by the first client through an instant messaging channel, where the linkage protocol packet is obtained by the first client packaging the acquired current operation behavior information into an application layer secondary protocol packet and encapsulating the application layer secondary protocol packet into an instant messaging primary protocol packet.
22. The server according to claim 20 or 21,
the sending module is specifically configured to forward the linkage protocol packet to one or more second clients of the at least one logged second client through an instant messaging channel or in a Push manner if it is determined that the at least one logged second client currently exists; or,
and if the fact that the logged second client does not exist currently is determined, the linkage protocol packet is stored in an offline server, and after the offline server determines that at least one second client is changed from the offline state to the logged state, the linkage protocol packet is forwarded to one or more second clients in the at least one second client changed from the offline state to the logged state through an instant communication channel or in a Push mode.
23. The server of claim 20 or 21, wherein the second client associated with the first client is a client that is logged in using the same account as the first client.
24. A client, comprising:
the receiving module is used for receiving a linkage protocol packet from other clients forwarded by the server, wherein the linkage protocol packet is obtained by encapsulating the obtained current operation behavior information of the operation users of the other clients when the other clients receive a linkage operation instruction, and the current operation behavior information comprises current operation interface information and current context description information; wherein the other clients are clients associated with the client;
the acquisition module is used for acquiring the current operation behavior information contained in the linkage protocol packet according to the received linkage protocol packet;
and the reconstruction module is used for reconstructing and displaying the current operation behavior information on the client.
25. The client of claim 24,
the receiving module is specifically configured to receive the linkage protocol packet forwarded by the server through an instant messaging channel or in a Push mode; or receiving the linkage protocol packet forwarded by the offline server through an instant communication channel or in a Push mode.
26. The client of claim 24 or 25, wherein the other clients associated with the client are clients that log in with the client using the same account.
27. A multi-end linkage system is characterized by comprising at least one first client, a server and at least one second client, wherein the second client is a client associated with the first client:
the first client is used for acquiring current operation behavior information of an operation user of the first client when a linkage operation instruction is received, packaging the acquired current operation behavior information into a linkage protocol packet, and sending the linkage protocol packet to a server, wherein the current operation behavior information comprises current operation interface information and current context description information;
the server is used for forwarding the received linkage protocol packet to at least one second client;
and the second client is used for acquiring the current operation behavior information according to the received linkage protocol packet, reconstructing the current operation behavior information on the second client and displaying the current operation behavior information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410273165.6A CN105337926B (en) | 2014-06-18 | 2014-06-18 | Multi-terminal linkage method and related equipment and system |
| HK16106569.0A HK1218594B (en) | 2016-06-08 | Method for interacting among multiple clients, related device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410273165.6A CN105337926B (en) | 2014-06-18 | 2014-06-18 | Multi-terminal linkage method and related equipment and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105337926A true CN105337926A (en) | 2016-02-17 |
| CN105337926B CN105337926B (en) | 2020-01-24 |
Family
ID=55288216
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410273165.6A Active CN105337926B (en) | 2014-06-18 | 2014-06-18 | Multi-terminal linkage method and related equipment and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105337926B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106357513A (en) * | 2016-09-14 | 2017-01-25 | 广东欧珀移动通信有限公司 | Message processing method, device, server and message processing system |
| CN107370657A (en) * | 2016-04-11 | 2017-11-21 | 连股份有限公司 | Equipment room application program interlock method and system |
| CN110224924A (en) * | 2019-05-21 | 2019-09-10 | 腾讯科技（深圳）有限公司 | State updating method and device, storage medium and electronic device |
| CN112202864A (en) * | 2020-09-24 | 2021-01-08 | 建信金融科技有限责任公司 | Context switching system, method, device, equipment and medium |
| CN119402506A (en) * | 2025-01-03 | 2025-02-07 | 杭州九麒科技有限公司 | Method and system for fast synchronization of data among multiple clients under the same account |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080168126A1 (en) * | 2007-01-07 | 2008-07-10 | Freedman Gordon J | Synchronization methods and systems |
| CN102882762A (en) * | 2011-07-11 | 2013-01-16 | 腾讯科技（深圳）有限公司 | Method and system for synchronizing chat status information in multiple pages |
| CN102932367A (en) * | 2012-11-15 | 2013-02-13 | 北京奇虎科技有限公司 | Terminal equipment, system and method for implementing switching of application program |
| WO2013035068A1 (en) * | 2011-09-08 | 2013-03-14 | Nds Limited | User interface |
| CN103294474A (en) * | 2013-05-31 | 2013-09-11 | 北京奇虎科技有限公司 | Browser operation synchronizing method and device for performing browser operation synchronization |
| CN103491055A (en) * | 2012-06-12 | 2014-01-01 | 中兴通讯股份有限公司 | Method for synchronizing information among clients, clients and server |
| US20140136638A1 (en) * | 2012-11-12 | 2014-05-15 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for message synchronization in instant messaging applications |
| CN103812755A (en) * | 2012-11-12 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Message synchronization method and device in instant messaging application |
-
2014
- 2014-06-18 CN CN201410273165.6A patent/CN105337926B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080168126A1 (en) * | 2007-01-07 | 2008-07-10 | Freedman Gordon J | Synchronization methods and systems |
| CN102882762A (en) * | 2011-07-11 | 2013-01-16 | 腾讯科技（深圳）有限公司 | Method and system for synchronizing chat status information in multiple pages |
| WO2013035068A1 (en) * | 2011-09-08 | 2013-03-14 | Nds Limited | User interface |
| CN103491055A (en) * | 2012-06-12 | 2014-01-01 | 中兴通讯股份有限公司 | Method for synchronizing information among clients, clients and server |
| US20140136638A1 (en) * | 2012-11-12 | 2014-05-15 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for message synchronization in instant messaging applications |
| CN103812755A (en) * | 2012-11-12 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Message synchronization method and device in instant messaging application |
| CN102932367A (en) * | 2012-11-15 | 2013-02-13 | 北京奇虎科技有限公司 | Terminal equipment, system and method for implementing switching of application program |
| CN103294474A (en) * | 2013-05-31 | 2013-09-11 | 北京奇虎科技有限公司 | Browser operation synchronizing method and device for performing browser operation synchronization |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107370657A (en) * | 2016-04-11 | 2017-11-21 | 连股份有限公司 | Equipment room application program interlock method and system |
| TWI654872B (en) | 2016-04-11 | 2019-03-21 | 日商連股份有限公司 | Method for interworking applications between devices |
| US10924519B2 (en) | 2016-04-11 | 2021-02-16 | Line Corporation | Method, apparatus, system, and non-transitory computer readable medium for interworking between applications of devices |
| CN107370657B (en) * | 2016-04-11 | 2021-04-23 | 连股份有限公司 | Method and system for linkage of application programs between devices |
| CN106357513A (en) * | 2016-09-14 | 2017-01-25 | 广东欧珀移动通信有限公司 | Message processing method, device, server and message processing system |
| CN106357513B (en) * | 2016-09-14 | 2021-01-29 | Oppo广东移动通信有限公司 | Message processing method, device, server and message processing system |
| CN110224924A (en) * | 2019-05-21 | 2019-09-10 | 腾讯科技（深圳）有限公司 | State updating method and device, storage medium and electronic device |
| CN110224924B (en) * | 2019-05-21 | 2021-04-09 | 腾讯科技（深圳）有限公司 | State updating method and device, storage medium and electronic device |
| CN112202864A (en) * | 2020-09-24 | 2021-01-08 | 建信金融科技有限责任公司 | Context switching system, method, device, equipment and medium |
| CN119402506A (en) * | 2025-01-03 | 2025-02-07 | 杭州九麒科技有限公司 | Method and system for fast synchronization of data among multiple clients under the same account |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1218594A1 (en) | 2017-02-24 |
| CN105337926B (en) | 2020-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9881359B2 (en) | Video communication method and system in instant communication | |
| EP3046331B1 (en) | Media control method and system based on cloud desktop | |
| CN105337926B (en) | Multi-terminal linkage method and related equipment and system | |
| KR102030226B1 (en) | Apparatus and method for maintaining a message thread with opt-in permanence for entries | |
| US20150229598A1 (en) | Method and system of synchroning an unread message in instant communication | |
| CN105871690B (en) | Method and device for realizing instant messaging | |
| US20180006976A1 (en) | Voice chat mode self-adapting method and apparatus | |
| WO2015065955A1 (en) | Bandwidth reduction system and method | |
| WO2015112600A1 (en) | Method and device for sharing data | |
| EP2605460A1 (en) | Method, apparatus, and system for transferring file to user of instant message system | |
| JP6861649B2 (en) | Session processing in instant messaging | |
| CN102902580A (en) | Program callback method and device | |
| CN108965932A (en) | A kind of even wheat window methods of exhibiting and device | |
| CN105207886A (en) | Instant messaging (IM) message sending and display methods, IM message sending and display devices, and IM message system | |
| CN105635133A (en) | Multimedia content transmission method and terminal | |
| US10757051B2 (en) | Integrating different messaging applications without relying on messaging protocols | |
| CN104469248A (en) | Video session method and device, server and terminal | |
| US8600359B2 (en) | Data session synchronization with phone numbers | |
| CN106657172A (en) | Method and device for realizing information push | |
| CN113014615A (en) | Data synchronization method, device and system | |
| CN114727154B (en) | Cloud application service data processing method, system, storage medium and processor | |
| CN103475574A (en) | Method and device used for sending messages | |
| CN110971860B (en) | A display method and device | |
| CN107070770A (en) | Method and device for resource transmission | |
| CN110300048B (en) | Audio message sending method, equipment and system based on instant messaging |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1218594 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |