WO2017190411A1 - 应用同步方法及装置 - Google Patents

应用同步方法及装置 Download PDF

Info

Publication number
WO2017190411A1
WO2017190411A1 PCT/CN2016/086941 CN2016086941W WO2017190411A1 WO 2017190411 A1 WO2017190411 A1 WO 2017190411A1 CN 2016086941 W CN2016086941 W CN 2016086941W WO 2017190411 A1 WO2017190411 A1 WO 2017190411A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
new
original
management
application management
Prior art date
Application number
PCT/CN2016/086941
Other languages
English (en)
French (fr)
Inventor
梁王乐文
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP16900933.9A priority Critical patent/EP3442161A4/en
Priority to US16/098,135 priority patent/US10649793B2/en
Publication of WO2017190411A1 publication Critical patent/WO2017190411A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44568Immediately runnable code
    • G06F9/44584Portable applications, i.e. making applications self-contained, e.g. U3 standard
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/52Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Definitions

  • This document relates to, but is not limited to, the field of application management technology, and relates to an application synchronization method and device.
  • the multi-open function of the application can be supported.
  • the so-called multi-opening means that an application (such as Tencent QQ) can also be in the mobile terminal while the mobile terminal is running.
  • Running multiple such applications such as QQ1, QQ2), this application (ie QQ) is called the original application, while the same application running (ie QQ1, QQ2) is called the derivative new application, and the original application and the new application essence It is multiple processes of the same application, such as Double WeChat, Dual Weibo, etc.
  • each application initiates a self-registration start request to the system.
  • all registered applications are displayed in a list for the user to manage, and the application displayed at this time is generally limited to the original application.
  • the system only recognizes the unique package name information of the original application, and there is no new application, thus causing the system to display the list of registered applications.
  • the embodiment of the invention provides an application synchronization method and device, which can automatically synchronize the application management category of the original application to a new application.
  • An embodiment of the present invention provides an application synchronization method, including:
  • the new application is an application derived from the original application, and the original application and the new application are different processes of the same application.
  • the application management category includes at least one of the following: an application permission, an application freeze, an application move, and an application security lock.
  • the method further includes: before the step of acquiring an application management category of the original application, creating a new application corresponding to the original application according to the original application.
  • the method further includes: before the step of acquiring an application management category of the original application, when the new application management mark corresponding to the original application is opened, creating the original application corresponding according to the original application. New application.
  • the method further includes: after the step of creating the new application corresponding to the original application, creating the new application management list, where the new application management list is used to record the new application Application management category;
  • the step of synchronizing the acquired application management category to the new application corresponding to the original application includes:
  • the method further includes: determining, before the step of synchronizing the acquired application management category to the new application corresponding to the original application, when the application management category of the application changes, determining whether the application is original application;
  • the acquired application management category is synchronized to the new application corresponding to the original application, where the acquired application management category is the changed application of the application. Manage categories.
  • An embodiment of the present invention further provides an application synchronization device, including:
  • Obtaining a module configured to obtain an application management category of the original application
  • An application management module configured to synchronize an application management category acquired by the acquiring module to a new application corresponding to the original application, so that an application management category of the new application and the original application should be Same as management category;
  • the new application is an application derived from the original application, and the original application and the new application are different processes of the same application.
  • the application management category includes at least one of the following: an application permission, an application freeze, an application move, and an application security lock.
  • the device further includes:
  • Creating a module configured to create a new application corresponding to the original application according to the original application.
  • the creating module is further configured to: when the new application management tag corresponding to the original application is opened, create a new application corresponding to the original application according to the original application.
  • the creating module is further configured to: after creating a new application corresponding to the original application, create a new application management list, where the new application management list is used to record an application management category of the new application. ;
  • the application management module is configured to: synchronize the acquired application management category into the new application management list.
  • the device further includes:
  • the determining module is configured to determine whether the application is the original application when the application management category of the application changes; and if the application is the original application, determine whether the new application management flag of the application is valid;
  • the application management module is further configured to: when the determining module determines that the new application management flag is valid, synchronize the changed application management category of the application to the new application corresponding to the application.
  • the above method or device can automatically synchronize the application management category of the original application to the new application, thereby improving the user experience.
  • the embodiment of the invention further provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions, and the computer executable instructions are implemented to implement an application synchronization method.
  • FIG. 1 is a schematic flow chart of an application synchronization method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic flowchart of an application synchronization method according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic flowchart of an application synchronization method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic flow chart of an application synchronization method according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic structural diagram of an application synchronization apparatus according to Embodiment 4 of the present invention.
  • FIG. 6 is another schematic structural diagram of an application synchronization apparatus according to Embodiment 4 of the present invention.
  • FIG. 7 is still another schematic structural diagram of an application synchronization apparatus according to Embodiment 4 of the present invention.
  • FIG. 1 is a schematic flowchart of an application synchronization method according to an embodiment of the present invention.
  • the application synchronization method can be used in a mobile terminal, such as an electronic product such as a smartphone or a tablet computer based on an Android operating system (or other operating system).
  • the method flow of Figure 1 includes:
  • Step 11 Obtain an application management category of the original application
  • Step 12 Synchronize the application management category obtained in step 11 to the new application corresponding to the original application, so that the application management category of the new application is the same as the application management category of the original application, where the new application is derived from the original application.
  • An application, and the original application and the new application are different processes of the same application.
  • the application management category includes but is not limited to at least one of the following: application permission, application freeze, application relocation, and application security lock.
  • a new application management list may be set for managing the application management category of the new application.
  • the synchronization operation in step 12 may be to modify the information under the application management category in the new application management list to the application management category obtained in step 11.
  • the application synchronization method of this embodiment can automatically synchronize the application management category of the original application to the new application, thereby improving the user experience.
  • FIG. 2 is a schematic flowchart of an application synchronization method according to an embodiment of the present invention.
  • the process of Figure 2 includes:
  • Step 21 When the new application management tag corresponding to the original application is opened, create a new application corresponding to the original application according to the original application;
  • Step 22 After creating a new application corresponding to the original application, create a new application management list, where the new application management list includes: a new application package name and an application management category;
  • Step 23 Obtain an application management category of the original application
  • Step 24 Synchronize the acquired application management category to the corresponding application management category in the new application list.
  • an original application list may be provided, where the original application list includes: an original application package name (identity identifier, that is, an original application package name) and a new application management tag, and the new application management tag is off by default.
  • an operation of creating a new application corresponding to the original application is performed.
  • not all applications in the mobile terminal can create new applications, for example, the system application does not allow, so the original application list generally only contains the original application that can create a new application, so that the user can see which applications support the new application.
  • the creation of an application is not limited thereto.
  • the original application list may include information of all non-system applications, but for the original application that does not support the new application creation, the corresponding new application management flag is closed and cannot be modified. .
  • the creating a new application corresponding to the original application in step 21 generally includes: starting a process of the new application, the new application process is a process associated with the original application process, and the new application process is not visible in the application management list of the system, only The original application process can be seen. However, the technical solution of the embodiment of the present invention is adopted. You can then see the new application process in the new app management list.
  • the original application may be associated with a new application list (or a derivative list), the new application list includes the original application package name, and the new application package name (the format is generally: original application package name + suffix) , data information such as application name and application icon.
  • the desktop Launcher can later create the application icon and application name of the new application on the desktop.
  • the new application list records the correspondence between the original application and the new application by using the original application package name and the new application package name, so that when the subsequent action is performed, the new application corresponding to the original application or the new application may be found according to the new application list. Corresponding original application.
  • the new application management list may include: a new application package name and an application management category, and may include: an original application package name, an application name, and detailed permission information. And the new application management list here and the aforementioned new application list may be combined into one list for easy operation.
  • the obtaining the application management category of the original application in step 23 is not necessarily performed after step 22, for example, the obtaining operation in step 23 may be performed in step 21 or step 22. That is to say, in the present application, there is no strict execution order between each step, and those skilled in the art can reasonably arrange the execution order of each step as needed.
  • the application management category information of the original application is automatically assigned to the created new application, thereby implementing management of the new application.
  • FIG. 3 is a schematic flowchart of an application synchronization method according to an embodiment of the present invention.
  • the method flow of Figure 3 includes:
  • Step 31 When the application management category of the application changes, determine whether the application is the original application. If it is the original application, go to step 32; if it is not the original application, end the process;
  • Step 32 Determine whether the new application management flag of the application is valid. If the new application management tag of the application is valid, if it is proved that the application has a new application, step 33 is performed; if the new baby management flag of the application is invalid, the process ends;
  • Step 33 Obtain an application management category after the application is changed.
  • Step 34 Synchronize the changed application management category to the new application corresponding to the application.
  • the application management category change of the application may be that the user modifies the permission of the application. For example, when the user performs the management operation on the original application, the application obtains the permission of the GPS (Global Positioning System), and the application of the application at this time. The management category will change.
  • GPS Global Positioning System
  • step 31 it is determined whether the application is the original application, and the original application list mentioned above may be queried by using the package name of the application, and if the application package name of the same application (same) is queried in the original application list, the application is proved. For the original application, otherwise it is not the original application.
  • the new application management flag in step 32 may be stored in the original application list, and the new application management flag is determined to be valid by querying the original application list by the application package name, for example, the default new application management flag is set to 0, when When the new application management tag for the query is set to "1", it indicates that the application's new application management tag is valid.
  • step 33 is not strictly required after step 32. For example, when the application management category of the application is found to change in step 31, whether the application is the original application or not, whether the new application management flag is valid or not The application management category of the application may be obtained first, but step 34 is performed only when it is determined that the application is the original application and the application management flag is valid.
  • step 34 the application management category after the application is changed is synchronized to the new application corresponding to the application, that is, the application management category of the new application is modified to be the same as the original application.
  • application management categories may include: application permissions, application freezes, application relocations, and application security locks. In practice, only one of the above changes may occur, for example, the application security lock has changed. In this case, only the application security lock item under the application management category of the new application may be modified to adapt to the original application.
  • the system when the user performs a management operation on the original application, the system automatically performs the same management operations on the new application, such as application rights, application freeze, application relocation, and application security lock, which are currently present, thereby greatly Improved user experience.
  • FIG. 4 is a schematic flowchart of the application synchronization method of the example, which includes:
  • Step 41 The system is normally turned on
  • Step 42 Setting a list of original applications
  • the original application list can contain information about all of the original applications that can generate new applications, such as the original application package name and the new application management tag.
  • WeChat is the original application
  • the original application list includes: WeChat package name and new application management tag.
  • the new application management flag is off.
  • Step 43 When the new application management tag corresponding to the original application WeChat is opened in the original application list, the new application process WeChat 1 is started; for example, when the user opens the new application management flag corresponding to the WeChat in the original application list.
  • the new application WeChat 1 process is a process that is associated under the original application process, and is not visible in the system application management list. Only the original application WeChat process is visible in the system application management list.
  • Step 44 Start generating a new application list (ie, a derived list);
  • the new application list includes the original application WeChat package name, new application WeChat 1 package name, WeChat 1, WeChat 1 icon, WeChat 1 capability set and other data information.
  • the initiating the generation of the new application list may refer to adding the information of the new application WeChat 1 to the list of new applications with a predefined format.
  • Step 45 After the new application list is created, create a new application management list.
  • the new application management list includes: original application package name, new application package name (original application package name + suffix), application name, application management category, and detailed permission and other data information.
  • the application management category includes, but is not limited to, an application management category such as an application permission, an application freeze, an application move, and an application security lock. According to the original application package name and the new application package name correspondence, the original application is created when the new application management list is created.
  • the class application management authority information is assigned to the corresponding new application.
  • the creating a new application management list may refer to adding the related information of the new application (that is, the information defined by the new application management list) to the new application management list of the above defined format.
  • Step 46 When the user performs a management operation on the original application, the application Y is obtained.
  • Step 47 Determine whether the application Y belongs to the original application that can generate a new application, and whether the application Y has a new application management mark. If the application Y belongs to the original application that can generate a new application, and the application Y has a new application management mark, then the step is entered. 48.
  • Step 48 Query the new application list according to the correspondence between the application Y package name and the new application package name.
  • the system finally copies the detailed permission of the application management category of the application Y to all corresponding new application management lists, and completes the same for the new application. Manage operations.
  • the application management information of the original application and the new application can be automatically synchronized. More importantly, the embodiment of the present invention provides an idea for managing the new application, thereby making up for the deficiencies of the related technologies.
  • FIG. 5 it is a schematic structural diagram of an application synchronization apparatus according to an embodiment of the present invention, which includes an acquisition module 51 and an application management module 52.
  • the obtaining module 51 is configured to acquire an application management category of the original application
  • the application management module 52 is configured to synchronize the application management category acquired by the acquiring module to the new application corresponding to the original application, so that the new The application management category of the application is the same as the application management category of the original application.
  • the application management category includes at least one of the following: an application permission, an application freeze, an application move, and an application security lock.
  • FIG. 6 it is another schematic structural diagram of an application synchronization apparatus according to an embodiment of the present invention.
  • the apparatus further includes: a creation module 53 configured to create a location according to the original application. Describe the new application corresponding to the original application.
  • the creating module 53 is further configured to: when the new application management tag corresponding to the original application is opened, the creating a new application corresponding to the original application according to the original application.
  • the creating module 53 is further configured to: after creating the new application corresponding to the original application, create a new application management list, where the new application management list includes: a new application package name and an application management category.
  • the application management module 52 is specifically configured to synchronize the acquired application management category to the application management category in the new application list.
  • the apparatus further includes: a determination module 54 configured to be an application management category of the application.
  • a determination module 54 configured to be an application management category of the application.
  • the application management module 52 is further configured to: when the determining module 54 determines that the new application management flag is valid, synchronize the changed application management category of the application to the new application corresponding to the application.
  • the application synchronization device of this embodiment can automatically synchronize the application management category of the original application to the new one. Apps that enhance the user experience.
  • the embodiment of the invention further provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions, and the computer executable instructions are implemented to implement an application synchronization method.
  • each module involved in the present application is a logic module.
  • a logical unit may be a physical unit, a part of a physical unit, or multiple physical units. Combined implementation.
  • the present embodiment does not introduce a unit that is not closely related to solving the technical problem proposed by the present application, but this does not indicate that there are no other units in the present embodiment.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种应用同步方法及装置。其中方法包括:获取原应用的应用管理类别;将所述获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应用管理类别相同。本发明实施例的技术方案可以自动地将原应用的应用管理类别同步给新应用,从而提升了用户体验。

Description

应用同步方法及装置 技术领域
本文涉及但不限于应用管理技术领域,涉及一种应用同步方法及装置。
背景技术
在移动终端中(如基于安卓操作***的智能手机),可以支持应用的多开功能,所谓多开即是指一个应用(如腾讯QQ)在一个移动终端运行时,还可以在该移动终端同时运行多个这样的应用(如QQ1、QQ2),将这个应用(即QQ)称为原应用,同时运行的相同应用(即QQ1、QQ2)称为衍生的新应用,而原应用和新应用实质是同一应用的多个进程,比如双微信,双微博等。
相关技术中,移动终端开机自动启动加载的应用时,每个应用会向***发起自注册启动请求。而当用户进行应用管理时,***会以列表的方式将所有注册的应用显示出来供用户进行管理,而此时显示的应用一般仅限于原应用。而对于新应用而言,因为当前***开机自启动的应用只有原应用,***识别的只有这个原应用的唯一的包名信息,并没有新应用,因此造成***在显示已注册的应用列表时并没有对应的新应用。即当用户进行应用管理时***会将所有注册的应用列表显示出来供用户选择,而***无法枚举到新应用,从而造成无法管理新应用的功能缺失。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种应用同步方法及装置,可以自动将对原应用的应用管理类别同步至新应用。
本发明实施例提供了一种应用同步方法,包括:
获取原应用的应用管理类别;将所述获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应用 管理类别相同;
其中所述新应用为所述原应用衍生而成的应用,并且所述原应用和所述新应用为同一应用的不同进程。
可选地,所述应用管理类别包括如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
可选地,所述方法还包括:所述获取原应用的应用管理类别的步骤之前,根据所述原应用,创建所述原应用对应的新应用。
可选地,所述方法还包括:所述获取原应用的应用管理类别的步骤之前,当所述原应用对应的新应用管理标记被打开时,根据所述原应用,创建所述原应用对应的新应用。
可选地,所述方法还包括:在所述创建所述原应用对应的新应用的步骤之后,创建所述新应用管理列表,其中,所述新应用管理列表用于记录所述新应用的应用管理类别;
所述将所述获取的应用管理类别,同步给所述原应用对应的新应用的步骤包括:
将所述获取的应用管理类别同步至所述新应用管理列表中。
可选地,所述方法还包括:在将所述获取的应用管理类别,同步给所述原应用对应的新应用的步骤之前,当应用的应用管理类别变化时,判断所述应用是否为原应用;
若所述应用是原应用,则判断所述应用的新应用管理标记是否有效;
若所述应用的新应用管理标记为有效,则将所述获取的应用管理类别,同步给所述原应用对应的新应用,其中所述获取的应用管理类别为所述应用的变化后的应用管理类别。
本发明实施例还提供一种应用同步装置,包括:
获取模块,设置为获取原应用的应用管理类别;
应用管理模块,设置为将所述获取模块获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应 用管理类别相同;
其中所述新应用为所述原应用衍生而成的应用,并且所述原应用和所述新应用为同一应用的不同进程。
可选地,所述应用管理类别包括如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
可选地,所述装置还包括:
创建模块,设置为根据所述原应用,创建所述原应用对应的新应用。
可选地,所述创建模块还设置为:当所述原应用对应的新应用管理标记被打开时,根据所述原应用,创建所述原应用对应的新应用。
可选地,所述创建模块还设置为:在创建完所述原应用对应的新应用之后,创建新应用管理列表,其中,所述新应用管理列表用于记录所述新应用的应用管理类别;
所述应用管理模块是设置为:将所述获取的应用管理类别同步至所述新应用管理列表中。
可选地,所述装置还包括:
判断模块,设置为当应用的应用管理类别变化时,判断所述应用是否为原应用;若所述应用是原应用,则判断所述应用的新应用管理标记是否有效;
所述应用管理模块还设置为:在所述判断模块判断到所述新应用管理标记为有效时,将所述应用的变化后的应用管理类别,同步给所述应用对应的新应用。
本发明实施例的有益效果是:
以上的方法或装置,可以自动地将原应用的应用管理类别同步给新应用,从而提升了用户体验。本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机可执行指令,所述计算机可执行指令被执行时实现应用同步方法。
在阅读并理解了附图和详细描述后,可以明白其它方面。
附图说明
图1是本发明实施例一的应用同步方法的流程示意图;
图2是本发明实施例二的应用同步方法的流程示意图;
图3是本发明实施例三的应用同步方法的第流程示意图;
图4是本发明实施例三的应用同步方法的第流程示意图;
图5是本发明实施例四的应用同步装置的结构示意图;
图6是本发明实施例四的应用同步装置的另一结构示意图;
图7是本发明实施例四的应用同步装置的又一结构示意图。
具体实施方式
下面将结合附图对本申请的每个实施方式进行详细的阐述。然而,本领域的普通技术人员可以理解,在本申请每个实施方式中,为了使读者更好地理解本申请而提出了许多技术细节。但是,即使没有这些技术细节和基于以下实施方式的种种变化和修改,也可以实现本申请每个权利要求所要求保护的技术方案。
实施例一
请参考图1,是本发明实施例的应用同步方法的流程示意图。该应用同步方法可以用于移动终端中,例如基于安卓操作***(或者其他操作***)的智能手机、平板电脑等电子产品。其中图1的方法流程包括:
步骤11:获取原应用的应用管理类别;
步骤12:将步骤11获取的应用管理类别,同步给原应用对应的新应用,以使新应用的应用管理类别与原应用的应用管理类别相同,其中所述新应用为所述原应用衍生而成的应用,并且所述原应用和所述新应用为同一应用的不同进程。
可选地,在步骤11中,应用管理类别包括但不限于如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
可选地,在步骤12中,可以设置一新应用管理列表用于对新应用的应用管理类别进行管理。此时步骤12中的同步操作即可以是将新应用管理列表中应用管理类别下的信息修改为步骤11中获取的应用管理类别。
本实施例的应用同步方法可以自动地将原应用的应用管理类别同步给新应用,从而提升了用户体验。
实施例二
请参考图2,是本发明实施例的应用同步方法的流程示意图。图2的流程包括:
步骤21:当原应用对应的新应用管理标记被打开时,根据原应用,创建原应用对应的新应用;
步骤22:在创建完原应用对应的新应用之后,创建新应用管理列表,其中该新应用管理列表包括:新应用包名和应用管理类别;
步骤23:获取原应用的应用管理类别;
步骤24:将获取的应用管理类别同步至新应用列表中对应的应用管理类别下。
其中,在步骤21中可以提供一张原应用列表,该原应用列表中包括:原应用包名(身份标识,即原应用包名)和新应用管理标记,该新应用管理标记默认为关闭,当该新应用管理标记被打开(例如由用户打开)时,则执行创建对应该原应用的新应用的操作。其中,移动终端中的应用,并非所有的都可以创建新应用,例如***应用则不允许,因此此张原应用列表一般仅包含可以创建新应用的原应用,如此可方便用户查看哪些应用支持新应用的创建。当然,本发明实施例也不限于此,例如该原应用列表可以包含所有非***应用的信息,但是对于不支持新应用创建的原应用,其对应的新应用管理标记为关闭并且不能够被修改。
其中,在步骤21创建原应用对应的新应用一般包括:启动新应用的进程,该新应用进程是在原应用进程之下关联的进程,在***的应用管理列表中不可见该新应用进程,只可见原应用进程。但是采用本发明实施例的技术方案 之后,可以在新应用管理列表中见该新应用进程。除此之外,还可以包括:原应用关联一个新应用列表(或称为衍生列表),该新应用列表包括原应用包名,新应用包名(格式一般为:原应用包名+后缀),应用名称和应用图标等数据信息。借助于该新应用列表中的信息,桌面Launcher(启动器)可以稍后在桌面创建该新应用的应用图标和应用名称。其中,新应用列表通过原应用包名和新应用包名记录了原应用和新应用之间的对应关系,以便于后续动作时,可以根据该新应用列表查明原应用对应的新应用或者新应用对应的原应用。
其中,在步骤22中,新应用管理列表除了可以包括:新应用包名和应用管理类别之外,还可以包括:原应用包名、应用名称、详细权限等信息。并且此处的新应用管理列表与前述提及的新应用列表可能合并为一张列表,以方便操作。
其中,步骤23中的获取原应用的应用管理类别并不一定是在步骤22之后执行,例如步骤23中的获取操作可以合并在步骤21或步骤22中执行。也就是说,在本申请中,每个步骤之间并不存在严格的执行顺序,本领域技术人员可以根据需要来合理安排每个步骤的执行顺序。
本实施例,在新应用被创建时,自动将原应用的应用管理类别信息赋予该创建的新应用,从而实现了对新应用的管理。
实施例三
请参考图3,是本发明实施例的应用同步方法的流程示意图。图3的方法流程包括:
步骤31:当应用的应用管理类别变化时,判断所述应用是否为原应用。如果是原应用则执行步骤32;如果不是原应用,则结束流程;
步骤32:判断该应用的新应用管理标记是否有效。若该应用的新应用管理标记有效,则证明该应用存在新应用,则执行步骤33;若该应用的新婴童管理标记无效,则结束流程;
步骤33:获取该应用变化后的应用管理类别;
步骤34:将该应用变化后的应用管理类别同步给该应用对应的新应用。
其中,在步骤31中,应用的应用管理类别变化可能是用户修改了应用的权限,例如用户对原应用进行管理操作时,打开了应用获取GPS(全球定位***)的权限,此时应用的应用管理类别将发生变化。
其中,步骤31中,判断应用是否为原应用,可以利用应用的包名查询前述提及的原应用列表,若能够在原应用列表中查询到完全一致(相同)的应用包名,则证明该应用为原应用,否则不为原应用。
其中,在步骤32中的新应用管理标记可以存储在原应用列表中,通过应用的包名查询原应用列表而判断新应用管理标记是否有效,例如,默认的新应用管理标记被设置为0,当查询到应用的新应用管理标记被设置为“1”时,则表明应用的新应用管理标记为有效。
其中,步骤33中的执行顺序并非严格的要求在步骤32之后,例如,在步骤31中发现应用的应用管理类别发生变化时,不论该应用是否为原应用,也不论其新应用管理标记是否有效,均可以先获取该应用的变化后的应用管理类别,只是当判断到该应用为原应用,且其应用管理标记为有效时,才执行步骤34。
其中,在步骤34中,将该应用变化后的应用管理类别同步给该应用对应的新应用,即是将新应用的应用管理类别修改为与原应用相同。一般地,应用管理类别可能包括:应用权限、应用冻结、应用搬家和应用安全锁。而实际中,可能仅有上述中的其中一项发生了变化,例如应用安全锁发生了变化,此时可以只修改新应用的应用管理类别下的应用安全锁项目,以适应原应用。
在本实施例中,在用户对原应用进行管理操作时,***自动对新应用做同样管理操作,例如当前存在的应用权限、应用冻结、应用搬家和应用安全锁等应用管理功能,从而极大地提升了用户体验。
下面具体示例对本申请的应用同步方法进行说明,以帮助本领域技术人员理解本申请。
请参考图4,是本示例的应用同步方法的流程示意图,其包括:
步骤41:***正常开机;
步骤42:设置原应用列表;
该原应用列表可以包含所有可以生成新应用的原应用的信息,例如原应用包名和新应用管理标记。例如,微信作为原应用,该原应用列表中包括:微信包名和新应用管理标记,默认情况下该新应用管理标记为关闭。
步骤43:在打开原应用列表中原应用微信对应的新应用管理标记时,则启动运行新应用进程微信1;例如当用户将原应用列表中的微信对应的新应用管理标记打开时。其中,新应用微信1进程是在原应用进程之下关联的进程,***应用管理列表中不可见,在***应用管理列表中只可见原应用微信进程。
步骤44:启动生成新应用列表(即衍生列表);
该新应用列表包括原应用微信包名包名,新应用微信1包名,微信1,微信1图标,微信1能力集等数据信息。其中,启动生成新应用列表可以是指将新应用微信1的信息添加至预先定义好了格式的新应用列表中。
步骤45:在新应用列表创建完成后,创建新应用管理列表;
该新应用管理列表包含:原应用包名,新应用包名(原应用包名+后缀),应用名称,应用管理类别和详细权限等数据信息。其中应用管理类别包含但不限于应用权限、应用冻结、应用搬家和应用安全锁等应用管理类别,根据原应用包名和新应用包名对应关系在创建该新应用管理列表时将原应用的以上4类应用管理权限信息赋予对应的新应用。其中,创建新应用管理列表可以是指将新应用的相关信息(即上述新应用管理列表定义了的信息)添加至上述已定义好了格式的新应用管理列表中。
步骤46:用户对原应用进行管理操作时,获得操作的应用Y;
步骤47:判断应用Y是否属于可生成新应用的原应用,且应用Y是否具备新应用管理标记,如果应用Y属于可生成新应用的原应用,且应用Y具备新应用管理标记,则进入步骤48。
步骤48:根据应用Y包名和新应用包名的对应关系查询新应用列表,***最终将应用Y的应用管理类别的详细权限复制到所有对应的新应用管理列表中,完成对新应用做同样的管理操作。
本实施例可以自动同步原应用和新应用的应用管理信息,更重要的是,本发明实施例提供了一种可以对新应用进行管理的思路,从而弥补了相关技术的不足。
实施例四
下面对相应于上述方法实施列的本发明的装置实施例进行说明。
如图5所示,是本发明实施例的应用同步装置的结构示意图,其包含:获取模块51和应用管理模块52。其中,获取模块51,设置为获取原应用的应用管理类别;应用管理模块52,设置为将所述获取模块获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应用管理类别相同。其中,所述应用管理类别包括如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
可选地,如图6所示,是本发明实施例的应用同步装置的另一结构示意图,与图5相比,该装置还包括:创建模块53,设置为根据所述原应用,创建所述原应用对应的新应用。
可选地,所述创建模块53还设置为:当所述原应用对应的新应用管理标记被打开时,所述根据所述原应用,创建所述原应用对应的新应用。
可选地,创建模块53还设置为:在创建完所述原应用对应的新应用之后,创建新应用管理列表,其中,所述新应用管理列表包括:新应用包名和应用管理类别。此时,应用管理模块52,具体用于将所述获取的应用管理类别同步至所述新应用列表中的应用管理类别下。
可选地,如图7所示,是本发明实施例的应用同步装置的又一结构示意图,基于前述任一应用同步装置,该装置还包括:判断模块54,设置为当应用的应用管理类别变化时,判断所述应用是否为原应用;若所述应用是原应用,则继续判断所述应用的新应用管理标记是否有效。
所述应用管理模块52还设置为:在所述判断模块54判断到所述新应用管理标记为有效时,将所述应用的变化后的应用管理类别,同步给所述应用对应的新应用。
本实施例的应用同步装置可以自动地将原应用的应用管理类别同步给新 应用,从而提升了用户体验。
本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机可执行指令,所述计算机可执行指令被执行时实现应用同步方法。
值得一提的是,本申请所涉及到的各模块均为逻辑模块,在实际应用中,一个逻辑单元可以是一个物理单元,也可以是一个物理单元的一部分,还可以以多个物理单元的组合实现。此外,为了突出本申请的创新部分,本实施方式中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入,但这并不表明本实施方式中不存在其它的单元。
本领域普通技术人员可以理解实现上述实施方式方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于一计算机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory,ROM)或随机存储记忆体(Random Access Memory,RAM)等。相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,例如通过集成电路来实现其相应功能,也可以采用软件功能模块的形式实现,例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。
本领域的普通技术人员可以理解,上述各实施方式是实现本申请的具体实施例,而在实际应用中,可以在形式上和细节上对其作各种改变,而不偏离本申请的精神和范围。
工业实用性
上述技术方案可以提升用户体验。

Claims (12)

  1. 一种应用同步方法,包括:
    获取原应用的应用管理类别;将所述获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应用管理类别相同;
    其中所述新应用为所述原应用衍生而成的应用,并且所述原应用和所述新应用为同一应用的不同进程。
  2. 根据权利要求1所述的方法,其中,所述应用管理类别包括如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
  3. 根据权利要求1所述的方法,所述方法还包括:所述获取原应用的应用管理类别的步骤之前,根据所述原应用,创建所述原应用对应的新应用。
  4. 根据权利要求1所述的方法,所述方法还包括:所述获取原应用的应用管理类别的步骤之前,当所述原应用对应的新应用管理标记被打开时,根据所述原应用,创建所述原应用对应的新应用。
  5. 根据权利要求3或4所述的方法,所述方法还包括:在所述创建所述原应用对应的新应用的步骤之后,创建所述新应用管理列表,其中,所述新应用管理列表用于记录所述新应用的应用管理类别;
    所述将所述获取的应用管理类别,同步给所述原应用对应的新应用的步骤包括:
    将所述获取的应用管理类别同步至所述新应用管理列表中。
  6. 根据权利要求1所述的方法,所述方法还包括:在将所述获取的应用管理类别,同步给所述原应用对应的新应用的步骤之前,当应用的应用管理类别变化时,判断所述应用是否为原应用;
    若所述应用是原应用,则判断所述应用的新应用管理标记是否有效;
    若所述应用的新应用管理标记为有效,则将所述获取的应用管理类别,同步给所述原应用对应的新应用,其中所述获取的应用管理类别为所述应用的变化后的应用管理类别。
  7. 一种应用同步装置,包括:
    获取模块,设置为获取原应用的应用管理类别;
    应用管理模块,设置为将所述获取模块获取的应用管理类别,同步给所述原应用对应的新应用,以使所述新应用的应用管理类别与所述原应用的应用管理类别相同;
    其中所述新应用为所述原应用衍生而成的应用,并且所述原应用和所述新应用为同一应用的不同进程。
  8. 根据权利要求7所述的装置,其中,所述应用管理类别包括如下至少一项:应用权限、应用冻结、应用搬家和应用安全锁。
  9. 根据权利要求7所述的装置,所述装置还包括:
    创建模块,设置为根据所述原应用,创建所述原应用对应的新应用。
  10. 根据权利要求9所述的装置,所述创建模块还设置为:当所述原应用对应的新应用管理标记被打开时,根据所述原应用,创建所述原应用对应的新应用。
  11. 根据权利要求7或10所述的装置,所述创建模块还设置为:在创建完所述原应用对应的新应用之后,创建新应用管理列表,其中,所述新应用管理列表用于记录所述新应用的应用管理类别;
    所述应用管理模块是设置为:将所述获取的应用管理类别同步至所述新应用管理列表中。
  12. 根据权利要求7所述的装置,所述装置还包括:
    判断模块,设置为当应用的应用管理类别变化时,判断所述应用是否为原应用;若所述应用是原应用,则判断所述应用的新应用管理标记是否有效;
    所述应用管理模块还设置为:在所述判断模块判断到所述新应用管理标记为有效时,将所述应用的变化后的应用管理类别,同步给所述应用对应的新应用。
PCT/CN2016/086941 2016-05-06 2016-06-23 应用同步方法及装置 WO2017190411A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16900933.9A EP3442161A4 (en) 2016-05-06 2016-06-23 METHOD AND DEVICE FOR APPLICATION SYNCHRONIZATION
US16/098,135 US10649793B2 (en) 2016-05-06 2016-06-23 Application synchronization method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610299114.XA CN107346253A (zh) 2016-05-06 2016-05-06 应用同步方法及装置
CN201610299114.X 2016-05-06

Publications (1)

Publication Number Publication Date
WO2017190411A1 true WO2017190411A1 (zh) 2017-11-09

Family

ID=60202533

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/086941 WO2017190411A1 (zh) 2016-05-06 2016-06-23 应用同步方法及装置

Country Status (4)

Country Link
US (1) US10649793B2 (zh)
EP (1) EP3442161A4 (zh)
CN (1) CN107346253A (zh)
WO (1) WO2017190411A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2555569B (en) * 2016-10-03 2019-06-12 Haddad Elias Enhanced computer objects security

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102760032A (zh) * 2012-03-19 2012-10-31 联想(北京)有限公司 一种信息处理的方法和电子设备
CN105224322A (zh) * 2015-09-25 2016-01-06 维沃移动通信有限公司 一种应用程序的分身方法及终端
US20160034265A1 (en) * 2014-08-04 2016-02-04 Tu Nguyen Method for Bulk App Loading on Mobile Devices
CN105468405A (zh) * 2015-11-18 2016-04-06 深圳市创想天空科技股份有限公司 一种应用程序的安装处理方法及装置

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6915307B1 (en) * 1998-04-15 2005-07-05 Inktomi Corporation High performance object cache
CA2245976A1 (en) * 1998-08-26 2000-02-26 Qnx Software Systems Ltd. Symmetric multi-processor system and method
US7334163B1 (en) * 2004-06-16 2008-02-19 Symantec Corporation Duplicating handles of target processes without having debug privileges
US8464250B1 (en) * 2004-09-23 2013-06-11 Transcontinental Events, Llc System and method for on-demand cloning of virtual machines
US20060090168A1 (en) * 2004-09-28 2006-04-27 Takeshi Ogasawara Method and system for speeding up mutual exclusion
US9286109B1 (en) * 2005-08-26 2016-03-15 Open Invention Network, Llc Method and system for providing checkpointing to windows application groups
US7529780B1 (en) * 2005-12-30 2009-05-05 Google Inc. Conflict management during data object synchronization between client and server
US7735051B2 (en) * 2006-08-29 2010-06-08 International Business Machines Corporation Method for replicating and synchronizing a plurality of physical instances with a logical master
US8522208B2 (en) * 2006-09-29 2013-08-27 Siemens Aktiengesellschaft System for creating and running a software application for medical imaging
US8875159B1 (en) * 2006-12-12 2014-10-28 Oracle America, Inc. System for defining non-native operating environments
EP1936498A1 (en) * 2006-12-21 2008-06-25 International Business Machines Corporation A method and system to manage memory accesses from multithread programs on multiprocessor systems
US8336046B2 (en) * 2006-12-29 2012-12-18 Intel Corporation Dynamic VM cloning on request from application based on mapping of virtual hardware configuration to the identified physical hardware resources
US8429653B2 (en) * 2007-05-31 2013-04-23 Sap Ag Process model control flow with multiple synchronizations
US9164812B2 (en) * 2009-06-16 2015-10-20 International Business Machines Corporation Method and system to manage memory accesses from multithread programs on multiprocessor systems
US8335765B2 (en) * 2009-10-26 2012-12-18 Amazon Technologies, Inc. Provisioning and managing replicated data instances
US8769155B2 (en) * 2010-03-19 2014-07-01 Brocade Communications Systems, Inc. Techniques for synchronizing application object instances
US9043706B2 (en) * 2010-08-31 2015-05-26 Anders Nancke-Krogh System and method for using state replication between application instances to provide a collaborative desktop environment
CN102567081B (zh) * 2010-12-07 2016-04-13 腾讯科技(深圳)有限公司 基于多进程的全局设置方法及***
US20130066832A1 (en) * 2011-09-12 2013-03-14 Microsoft Corporation Application state synchronization
US8756455B2 (en) * 2011-11-17 2014-06-17 Microsoft Corporation Synchronized failover for active-passive applications
US8918822B2 (en) * 2012-09-26 2014-12-23 Apple Inc. Displaying a synchronized instance of content on a portable electronic device
US9061210B2 (en) * 2013-03-21 2015-06-23 Nextbit Systems Inc. Synchronizing an instance of an application between multiple devices
JP6197585B2 (ja) * 2013-11-01 2017-09-20 富士通株式会社 情報処理装置、及び、情報処理装置の制御方法
US10171579B2 (en) * 2014-04-08 2019-01-01 Dropbox, Inc. Managing presence among devices accessing shared and synchronized content
US10231033B1 (en) * 2014-09-30 2019-03-12 Apple Inc. Synchronizing out-of-band content with a media stream
US10055129B2 (en) * 2015-02-23 2018-08-21 Oracle International Corporation Read concurrency using hardware transactional lock elision
CN104869569A (zh) * 2015-03-31 2015-08-26 小米科技有限责任公司 应用程序的网络权限控制方法及装置
US9715416B2 (en) * 2015-06-03 2017-07-25 Intel Corporation Adaptive queued locking for control of speculative execution
US10585627B2 (en) * 2016-03-24 2020-03-10 Microsoft Technology Licensing, Llc Distributed metadata management in a distributed storage system
US11341100B2 (en) * 2016-12-12 2022-05-24 Egnyte, Inc. System and method for eliminating full rescan synchronizations on service restarts
US10860464B2 (en) * 2017-03-10 2020-12-08 Micro Focus Llc Test selection for application commit
US10754641B2 (en) * 2017-05-30 2020-08-25 Red Hat, Inc. Optimizing continuous integration (CI) using code review quality

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102760032A (zh) * 2012-03-19 2012-10-31 联想(北京)有限公司 一种信息处理的方法和电子设备
US20160034265A1 (en) * 2014-08-04 2016-02-04 Tu Nguyen Method for Bulk App Loading on Mobile Devices
CN105224322A (zh) * 2015-09-25 2016-01-06 维沃移动通信有限公司 一种应用程序的分身方法及终端
CN105468405A (zh) * 2015-11-18 2016-04-06 深圳市创想天空科技股份有限公司 一种应用程序的安装处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3442161A4 *

Also Published As

Publication number Publication date
US20190155621A1 (en) 2019-05-23
US10649793B2 (en) 2020-05-12
EP3442161A4 (en) 2019-04-17
EP3442161A1 (en) 2019-02-13
CN107346253A (zh) 2017-11-14

Similar Documents

Publication Publication Date Title
US11799984B2 (en) Installable web applications
JP6397113B2 (ja) リモーティングセッションを通じた非サポートファイル形式の開封
US10237711B2 (en) Dynamic types for activity continuation between electronic devices
US8812451B2 (en) Programming model for synchronizing browser caches across devices and web services
US9560130B2 (en) Presenting availability statuses of synchronized objects
EP3610390B1 (en) Predictive local pre-cache for reduced latency digital content access rights determination
WO2016050112A1 (zh) 一种数据存储方法、存储装置及存储***
WO2016161961A1 (zh) 处理关注信息的方法、终端设备、服务器及***
TWI535327B (zh) 通信帳號各客戶端之間數據同步方法、裝置及伺服器
JP2017516174A5 (zh)
JP2017516173A5 (zh)
WO2019100985A1 (zh) 页面处理方法及移动终端
WO2015101320A1 (zh) 一种账号的生成方法、终端及后台服务器
US10209976B2 (en) Automated application installation
WO2015058574A1 (zh) 实现扩展应用程序的推送通知的方法及装置
TW201415249A (zh) 訪問音視頻社區虛擬房間之方法及系統
US20200220712A1 (en) Electronic apparatus managing data based on block chain and method for managing data
US11392694B2 (en) Electronic apparatus and controlling method thereof
WO2019015491A1 (zh) 应用程序的分身方法、装置、设备和介质
TW201544986A (zh) 資料的唯一性控制方法、資訊儲存方法及裝置
US10033710B2 (en) Electronic device and method of transmitting and receiving information by electronic device
KR20160086754A (ko) 펌웨어 리프레시 방법, 장치, 프로그램 및 기록매체
WO2017190411A1 (zh) 应用同步方法及装置
WO2017193475A1 (zh) 应用程序的管理方法及装置
CN107291524B (zh) 一种远程命令的处理方法和装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2016900933

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016900933

Country of ref document: EP

Effective date: 20181106

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16900933

Country of ref document: EP

Kind code of ref document: A1