Automatic dynamic vetting of browser extensions and web applications
US-9762598-B1 · Sep 12, 2017 · US
US2016277496A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016277496-A1 |
| Application number | US-201615168364-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 31, 2016 |
| Priority date | Nov 28, 2013 |
| Publication date | Sep 22, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method is provided for application synchronization. The method includes: establishing a communication connection between an originating terminal and a destination terminal, where the originating terminal and the destination terminal log in the server through a same login account, and receiving a synchronization request message sent by the originating terminal, where the synchronization request message includes a program identification of a target application and a terminal identification of the destination terminal. The method also includes: based on the terminal identification of the destination termini, obtaining device information and address information of the destination terminal, querying an installation file matching with the program identification of the target application and the device information of the destination terminal, and sending the installation file to the destination terminal specified by the address information.
Opening claim text (preview).
What is claimed is: 1 . An application synchronization method, comprising: establishing, by a server, a communication connection between an originating terminal and a destination terminal, wherein the originating terminal and the destination terminal respectively log in the server with a same login account; receiving, by the server, a synchronization request message sent by the originating terminal, wherein the synchronization request message includes a program identification of a target application and a terminal identification of the destination terminal; obtaining, by the server, device information and address information of the destination terminal based on the terminal identification of the destination terminal; querying, by the server, an installation file matching with the program identification of the target application and the device information of the destination terminal; and sending, by the server, the installation file to the destination terminal based on the address information. 2 . The method according to claim 1 , before receiving the synchronization request message sent by the originating terminal, further comprising: checking, by the server, whether the originating terminal complies with a pre-established security policy and, when the originating terminal complies with the pre-established security policy, proceeding to receive the synchronization request message sent by the originating terminal. 3 . The method according to claim 1 , further comprising: obtaining, by the server, a user data of the target application installed on the originating terminal; and sending, by the server, the user data to the destination terminal. 4 . The method according to claim 2 , further comprising: obtaining, by the server, a user data of the target application installed on the originating terminal; and sending, by the server, the user data to the destination terminal. 5 . The method according to claim 3 , wherein sending the installation file to the destination terminal based on the address information further includes: compressing, by the server, the installation file; and sending, by the server, the compressed installation file to the destination terminal based on the address information. 6 . The method according to claim 3 , wherein sending by the server the installation file to the destination terminal based on the address information includes: when the transfer of the installation file is completed successfully, returning, by the server, a synchronization success indication message to the destination terminal. 7 . The method according to claim 5 , wherein the device information of the destination terminal includes: a device type and an operating system of the destination terminal. 8 . The method according to claim 6 , wherein the device information of the destination terminal includes: a device type and an operating system of the destination terminal. 9 . An application synchronization server, includes: a connecting module configured to establish a communication connection between an originating terminal and a destination terminal, wherein the originating terminal and the destination terminal respectively log in the server through a same login account; a receiving module configured to receive a synchronization request message sent by the originating terminal, and the synchronization request message includes a program identification of a target application and a terminal identification of the destination terminal; an obtaining module configured to obtain device information and address information of the destination terminal based on the terminal identification of the destination terminal; a querying module configured to query an installation file matching with the program identification of the target application and the device information of the destination terminal; and a first synchronizing module configured to send the installation file to the destination terminal based on the address information. 10 . The server according to claim 9 , further comprising: an authenticating module configured to check whether the originating terminal complies with a pre-established security policy and to instruct the obtaining module to proceed when the originating terminal complies with the pre-established terminal. 11 . The server according to claim 9 , further comprising: a second synchronizing module configured to obtain a user data of the target application installed on the originating terminal and to send the user data to the destination terminal. 12 . The server according to claim 10 , further comprising: a second synchronizing module configured to obtain a user data of the target application installed on the originating terminal and to send the user data to the destination terminal. 13 . The server according to claim 11 , wherein the first synchronizing module is further configured to compress the installation file and to send the compressed installation file to the destination terminal based on the address information. 14 . The server according to claim 11 , wherein the first synchronizing module is further configured to return a synchronization success indication message to the originating server when the transfer of the installation file is completed successfully. 15 . The server according to claim 13 , wherein the device information of the destination terminal includes a device type and an operating system of the destination terminal. 16 . An application synchronization system comprising a server according to claim 9 , further comprising: an originating terminal; and at least a destination terminal, wherein the server establishes a communication connection between the originating terminal and the destination terminal, and the originating terminal and the destination terminal log in the server in a same login account. 17 . An application synchronization system comprising a server according to claim 11 , further comprising: an originating terminal; and at least a destination terminal, wherein the server establishes a communication connection between the originating terminal and the destination terminal, and the originating terminal and the destination terminal log in the server in a same login account.
Physics · mapped topic
Protocols for data compression, e.g. ROHC · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Physics · mapped topic
for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.