WO2017161638A1 - 一种多系统的冻结与唤醒方法及装置 - Google Patents

一种多系统的冻结与唤醒方法及装置 Download PDF

Info

Publication number
WO2017161638A1
WO2017161638A1 PCT/CN2016/080623 CN2016080623W WO2017161638A1 WO 2017161638 A1 WO2017161638 A1 WO 2017161638A1 CN 2016080623 W CN2016080623 W CN 2016080623W WO 2017161638 A1 WO2017161638 A1 WO 2017161638A1
Authority
WO
WIPO (PCT)
Prior art keywords
operating system
freezing
operating
waking
instruction
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.)
Ceased
Application number
PCT/CN2016/080623
Other languages
English (en)
French (fr)
Inventor
陈磊
郭德英
叶瑞权
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yulong Computer Telecommunication Scientific Shenzhen Co Ltd
Original Assignee
Yulong Computer Telecommunication Scientific Shenzhen Co Ltd
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 Yulong Computer Telecommunication Scientific Shenzhen Co Ltd filed Critical Yulong Computer Telecommunication Scientific Shenzhen Co Ltd
Publication of WO2017161638A1 publication Critical patent/WO2017161638A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/48—Indexing scheme relating to G06F9/48
    • G06F2209/482—Application

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to a method and apparatus for freezing and waking up multiple systems.
  • Multi-system terminals (such as dual-system terminals) solve the multi-level requirements of users for terminals.
  • an existing multi-system intelligent terminal for example, a dual-system terminal installed with a security system and a general system
  • the corresponding The system manually freezes the application in an application, or closes the relevant data of the application in the system settings; that is, the user cannot directly freeze one of your systems.
  • the application that needs to be frozen cannot be selected, and only one of the systems can be selected one by one.
  • the freezing of the application or the operating system requires multiple operations, and there is a technical problem that the convenience of the operation is insufficient.
  • a multi-system freeze and wake-up method including:
  • the second operating system self-freezing after receiving the notification but retaining the wake-up listener/thread.
  • the method further includes: receiving, in the security operating system, a thaw instruction for the second operating system, where the operating authority level of the security operating system is not lower than the first An operating authority level of the operating system; notifying the second operating system in the secure operating system, the second operating system self-waking up after the receiving of the notification by the wake-up listener/thread.
  • the step that the second operating system freezes but retains the wake-up listener/thread after receiving the notification is specifically: the second operating system acquires the information included in the notification
  • the access authority level caches the data of the second operating system runtime according to the access permission level, but keeps running the wakeup listener/thread.
  • the step of the second operating system self-waking up after receiving the notification by the wake-up listener/thread is specifically: the second operating system listens to the incoming thread by using the reserved wake-up Receiving the notification, the data in the second operating system is restored from the cache.
  • the access permission level includes at least two levels of all applications inaccessible and only the phone and short message applications are accessible.
  • the step of notifying the second operating system in the first operating system is specifically: broadcasting the freeze instruction by using an Intent mechanism in the first operating system
  • the step of notifying the second operating system in the security operating system is specifically: broadcasting the freezing instruction to the second by using an Intent mechanism in the security operating system operating system.
  • a multi-system freeze and wake device comprising:
  • a freeze instruction receiving module configured to receive a freeze instruction in the first operating system, and obtain an identifier of the second operating system corresponding to the freeze command, where the first operating system and the second operating system are in an operating state,
  • the operating authority level of the second operating system is not higher than the operating authority level of the first operating system
  • a freezing module configured to notify the second operating system in the first operating system, the second operating system self-freezing after receiving the notification but retaining the wake-up listening/thread.
  • the apparatus further includes a defrosting instruction receiving module and a thawing module, wherein: the defrosting instruction receiving module is configured to receive a defrosting instruction for the second operating system in a secure operating system The operation authority level of the security operating system is not lower than the operation authority level of the first operating system; the defrosting module is configured to notify the second operating system in the security operating system, the second operation The system wakes up automatically after waking up the listener/thread to receive the notification.
  • the defrosting instruction receiving module is configured to receive a defrosting instruction for the second operating system in a secure operating system
  • the operation authority level of the security operating system is not lower than the operation authority level of the first operating system
  • the defrosting module is configured to notify the second operating system in the security operating system, the second operation The system wakes up automatically after waking up the listener/thread to receive the notification.
  • the freezing module is further configured to: acquire, by the second operating system, an access permission level included in the notification, and use the second operating system according to the access permission level.
  • the data cache at runtime, but keeps running the wakeup listener/thread.
  • the defrosting module is further configured to: the second operating system receives the notification by using a wake-up listener/thread that is reserved for running, and recovering from the cache in the second operating system Runtime data.
  • the freeze instruction receiving module is further configured to: in the first operating system, broadcast the freeze instruction to the second operating system by using an Intent mechanism; and the thaw instruction The receiving module is further configured to: in the secure operating system, broadcast the freeze instruction to the second operating system by using an Intent mechanism.
  • the freezing instruction can be directly sent to the system that needs to be frozen in the current system, and the related application of the system is directly frozen to avoid In the traditional technology, it must be in the system. It is necessary to freeze the system to be frozen one by one, which reduces the number of operations of the user when freezing the system or the application, and improves the operation convenience of the system freezing of the mobile terminal based on the multi-system.
  • the user can only wake up or unfreeze the frozen system in a secure operating system with administrator rights, so that the frozen system cannot be freely thawed, and the security of the user data is improved.
  • FIG. 1 is a schematic flow chart of a method for freezing and waking up multiple systems in an embodiment
  • FIG. 2 is a schematic structural diagram of a multi-system freezing and waking device in an embodiment.
  • a multi-system freeze is proposed.
  • the wakeup method may rely on a computer program that can run on a computer system based on the von Neumann system.
  • the computer program can be a system freeze and wake up program.
  • the method for freezing and waking up the multiple systems is based on a computer device in which multiple systems are installed, for example, a dual system mobile phone with a security system and a general system installed, and for example, a security operation is installed.
  • the system, the first operating system, and the second operating system of the second operating system (the first operating system and the second operating system are ordinary systems).
  • the multiple systems of the smart terminal refer to more than one operating system installed by the smart terminal, and one of the specific systems is an operating system with administrator rights, and the system may be referred to as a management operating system or a security operation. System, other systems are ordinary operating systems with equal rights. It should be noted that, in this embodiment, multiple systems can be operated simultaneously. For example, for a smart phone terminal with three operating systems S, A, and B installed, the display interface of the terminal displays A. The operating system, that is, the running system displayed on the current display interface is the A system, but at the same time, the system S and the system B can also be in the running state, and the user can switch the operating system displayed on the current interface through the system switching operation.
  • the method for freezing and waking up the multiple systems includes the following steps:
  • Step S102 Receive a freeze instruction in the first operating system, and obtain an identifier of the second operating system corresponding to the freeze command, where the first operating system and the second operating system are in a running state, and the second operating system is The operation authority level is not higher than the operation authority level of the first operating system.
  • the freeze command is a freeze command input by the user through the terminal, and the system carries the system that needs to be frozen, that is, the identifier of the system that needs to be frozen.
  • the first operating system is an operating system that issues a freeze command
  • the second operating system is an operating system that needs to be frozen.
  • the operation authority level of the first operating system that issues the freeze instruction is higher than or equal to the operation authority level of the frozen second operating system, that is, when the operating system issues a freeze instruction.
  • the frozen operating system can only be an operating system with the same operating authority level or lower operating authority level, and cannot freeze the operating system with higher operating authority level than itself.
  • the first operating system may be a secure operating system with administrator rights (ie, the freeze command of the second operating system is issued by the secure operating system), or may be a common operating system with normal rights;
  • the second operating system can only be a normal operating system with normal permissions and not a secure operating system. That is to say, in its own embodiment, an operating system with administrator rights can freeze other systems, but other ordinary systems cannot freeze the security system; ordinary systems can freeze each other.
  • the operating system corresponding to the current display interface of the terminal is the first operating system, and a freeze instruction is input in the system freeze application or the system freeze interface in the first operating system, and The operating system that needs to be frozen is selected, that is, the identifier of the operating system that needs to be frozen, that is, the identifier of the second operating system, is included in the above freeze instruction.
  • both the first operating system and the second operating system are in a running state, that is, the operating system that issues the freezing instruction and the frozen operating system are in a running state, that is, not in operation.
  • the operating system of the state cannot issue a freeze command or be frozen.
  • Step S104 Notifying the second operating system in the first operating system, the second operating system self-freezing after receiving the notification but retaining the wake-up listening/thread.
  • the system After the first operating system issues a freeze command, the system sends a notification to the second operating system through the first operating system in the first operating system according to the received freeze command and the second operating system identifier in the obtained freeze command.
  • the relevant freeze instruction information is carried in the notification.
  • the step of notifying the second operating system in the first operating system is specifically: sending, by the Intent mechanism, a broadcast freeze instruction to the second operating system in the first operating system.
  • the Intent is responsible for communication between the Android system and the Android system on the same terminal, that is, the transmission and transmission of data between the first operating system and the second operating system is a system provided by the Intent. Realized by the communication medium.
  • the first operating system can send data to the second operating system through the Intent.
  • the first operating system notifying the implementation of the second operating system may also implement communication between the two operating systems in other manners.
  • the first operating system may also send a broadcast to each operating system in the form of a broadcast, and the second operating system may obtain relevant information in the broadcast by parsing related information in the broadcast after receiving the broadcast, for example, knowing that the broadcast is about freezing systematic.
  • the secure operating system may also accept the relevant freeze broadcast, thereby obtaining the freeze information of the system.
  • the second operating system After the first operating system notifies the second operating system that the second operating system needs to be frozen, the second operating system receives the relevant notification and parses the related information in the notification, and then performs related operations of the freezing system according to the parsed related information. , that is, self-freezing.
  • the operating system also retains a wake-up listening process or thread after being frozen, so that the operating system can be thawed or awake after being frozen.
  • the step that the second operating system freezes but retains the wake-up listener/thread after receiving the notification is specifically: the second operating system acquires an access permission level included in the notification, according to the access permission The level caches the data of the second operating system runtime, but keeps running the wakeup listener/thread.
  • the access level is the accessible status of all applications of the operating system (that is, all applications), for example, all applications are inaccessible, and for example, only the privacy application is inaccessible.
  • the access authority level includes at least two applications are inaccessible and only the phone and the short message application can access two levels, and the user can also set other access permission levels as needed.
  • the specific setting corresponding to the access authority level can be obtained by the access authority level, that is, the access state setting of the application of the operating system is obtained. Then, according to the access state setting of the application in the access permission level, the running data of all the applications in the second operating system is cached, that is, the data that needs to be frozen is saved according to the freeze instruction, so that the system is performed. When thawing, it is thawed according to the data saved at the time of freezing.
  • the user may select a corresponding access authority level when inputting the freeze instruction, and the access authority level may be included in the freeze instruction; or, the default access authority level may be set, if not specified.
  • the default permission level that has been set is added to the freeze command by default.
  • the method for freezing and waking up the multiple systems further includes the following steps S202-S204:
  • Step S202 Receive a thaw instruction for the second operating system in the security operating system, where the operating authority level of the security operating system is not lower than the operating authority level of the first operating system.
  • a normal system that does not have administrator rights does not have the right to unfreeze other operating systems. That is, the thaw of the operating system can only be operated by a secure operating system with administrator rights. Therefore, the thaw instruction is generated. And receiving can only be done in a secure operating system, ie security
  • the operating authority level of the operating system is higher than the operating authority level of the normal system.
  • the thawing instruction is a thawing instruction of the second operating system that the user has thawed through the operating system defrosting page in the secure operating system or the operating system thawing application, and the operating system that needs to be thawed is carried in the instruction ( The identity of the second operating system.
  • the terminal parses the defrosting command, and determines a next operation according to the information included in the defrosting command, that is, step S204.
  • Step S204 Notifying the second operating system in the security operating system, the second operating system self-waking up after the notification is received by the wake-up listener/thread.
  • the security operating system After the step S202, according to the received defrosting instruction for the second operating system, the security operating system sends a notification to the second operating system through the security operating system, and the related information corresponding to the defrosting instruction is carried in the notification.
  • the step of notifying the second operating system in the security operating system is specifically: broadcasting, by the Intent mechanism, the freezing instruction to the second in the security operating system operating system.
  • the Intent is responsible for communication between the Android system and the Android system on the same terminal, that is, the transmission and transmission of data between the secure operating system and the second operating system is performed by the system provided by the Intent. Realized by the communication medium.
  • the secure operating system can send data to the second operating system through the Intent.
  • the implementation of the second operating system by the security operating system may also implement communication between the two operating systems by other means.
  • the security operating system may also send a broadcast to each operating system in the form of a broadcast, and the second operating system obtains related information in the broadcast by parsing related information in the broadcast after receiving the broadcast, for example, knowing that the broadcast is about freezing the system. of.
  • the second operating system receives the notification sent by the secure operating system by the wake-up listening process/thread and parses the related data in the notification.
  • the system is then self-defrozed based on the parsed relevant data.
  • the self-defrosting process is about to resume operation in the frozen application or process during the freezing process.
  • the foregoing second operating system calls itself by waking up the listener/thread to receive the notification.
  • the step of waking up is specifically: the second operating system receives the notification by the hold-up wake-up listener/thread, and recovers the data in the second operating system from the cache.
  • the operating system when the operating system is frozen, the related applications in the operating system and the data of the process are saved.
  • the operating system will be cached during the process of freezing the operating system. All data running by the operating system is restored, that is, all the cached applications and the running data of the process/thread are read from the cache and resumed.
  • This process is a self-wake process, that is, it is frozen. The process of thawing or waking up the system.
  • a multi-system is also proposed. Freeze and wake up device.
  • the freeze and wake-up device of the multiple systems includes a freeze instruction receiving module 102 and a freeze module 104, wherein:
  • the freeze instruction receiving module 102 is configured to receive a freeze instruction in the first operating system, and obtain an identifier of the second operating system corresponding to the freeze command, where the first operating system and the second operating system are in an operating state,
  • the operating authority level of the second operating system is not higher than the operating authority level of the first operating system;
  • the freezing module 104 is configured to notify the second operating system in the first operating system, and the second operating system freezes but retains the wake-up listening/thread after receiving the notification.
  • the foregoing apparatus further includes a freeze instruction receiving module 106 and a defrosting module 108, wherein: the defrosting instruction receiving module 106 is configured to receive, in the secure operating system, the second operating system The defrosting instruction, the operating privilege level of the security operating system is not lower than the operating privilege level of the first operating system; the defrosting module 108 is configured to notify the second operating system in the secure operating system The second operating system wakes up by waking up the listener/thread after receiving the notification.
  • the freezing module 104 is further configured to: acquire, by the second operating system, an access permission level included in the notification, and run the second operating system according to the access permission level.
  • the data is cached, but keeps running the wakeup listener/thread.
  • the defrosting module 108 is further configured to: the second operating system The data in the second operating system is restored from the cache by the cached wake-up listener/thread receiving the notification.
  • the access permission level includes at least two levels of all applications inaccessible and only the phone and short message applications are accessible.
  • the freeze instruction receiving module 102 is further configured to: in the first operating system, broadcast the freeze instruction to the second operating system by using an Intent mechanism.
  • the defrosting instruction receiving module 106 is further configured to: in the security operating system, broadcast the freeze instruction to the second operating system by using an Intent mechanism.
  • the freezing instruction can be directly sent to the system that needs to be frozen in the current system, and the related application of the system is directly frozen to avoid
  • it is necessary to freeze the system that needs to be frozen one by one in the system thereby reducing the number of operations of the user when freezing the system or the application, and improving the operation of the system freeze based on the multi-system mobile terminal. Sex.
  • the user can only wake up or unfreeze the frozen system in a secure operating system with administrator rights, so that the frozen system cannot be freely thawed, and the security of the user data is improved.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)

Abstract

本发明实施例公开了一种多系统的冻结与唤醒方法，包括：在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。另外，本发明实施例还相应地公开了一种多系统的冻结与唤醒装置。采用本发明，可提高基于多系统的移动终端的系统的冻结与唤醒的操作便利性。

Description

一种多系统的冻结与唤醒方法及装置
本申请要求于2016年03月24日提交中国专利局，申请号为201610173367.2、发明名称为“一种多系统的冻结与唤醒方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计算机技术领域，尤其涉及一种多系统的冻结与唤醒方法及装置。
背景技术
随着计算机技术的发展，在移动智能终端上集成的功能越来愈多，手机用户使用手机的频率越来越高。多系统终端(例如双系统终端)很好的解决了用户对终端的多层次需求。
在现有的多系统智能终端(例如安装了安全系统和普通系统的双系统终端)中，用户在发现某一个系统出现安全问题时或者其他不想继续运行该系统的情况下，只能在对应的系统中手动的在某个应用中冻结该应用，或者在该系统设置中关闭该应用的相关数据；也就是说，用户不能直接对你某一个系统进行冻结。进一步地，用户在发现某一个系统出现安全问题的情况下，但是不知道是该系统下的哪一个应用或者程序出现问题，无法选择具体需要冻结的应用，只能选择逐一将该系统中的每一个应用进行冻结。
也就是说，现有的多系统终端中，应用程序或者操作系统的冻结需要进行多次操作，存在操作的便利性不足的技术问题。
发明内容
基于此，为解决传统技术中的多系统终端的应用程序以及操作系统的冻结因为需要进行多次操作而存在的操作的便利性不足的技术问题，特提出了一种多系统的冻结与唤醒方法。
一种多系统的冻结与唤醒方法，包括：
在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；
在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
可选的，在其中一个实施例中，所述方法还包括：在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级；在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
可选的，在其中一个实施例中，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程的步骤具体为：所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
可选的，在其中一个实施例中，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒的步骤具体为：所述第二操作系统通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
可选的，在其中一个实施例中，所述访问权限等级至少包括全部应用不可访问和仅电话与短信应用可访问两个等级。
可选的，在其中一个实施例中，所述在所述第一操作系统中通知所述第二操作系统的步骤具体为：在所述第一操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统；所述在所述安全操作系统中通知所述第二操作系统的步骤具体为；在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
此外，为解决传统技术中的多系统终端的应用程序以及操作系统的冻结因为需要进行多次操作而存在的操作的便利性不足的技术问题，特提出了一种多系统的冻结与唤醒装置。
一种多系统的冻结与唤醒装置，包括：
冻结指令接收模块，用于在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；
冻结模块，用于在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
可选的，在其中一个实施例中，所述装置还包括解冻指令接收模块和解冻模块，其中：所述解冻指令接收模块用于在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级；所述解冻模块用于在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
可选的，在其中一个实施例中，，所述冻结模块还用于：所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
可选的，在其中一个实施例中，所述解冻模块还用于：所述第二操作系统通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
可选的，在其中一个实施例中，所述冻结指令接收模块还用于：在所述第一操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统；所述解冻指令接收模块还用于：在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
实施本发明实施例，将具有如下有益效果：
采用了上述多系统的冻结与唤醒方法和装置之后，对于安装了多系统的移动终端来讲，可以在多个系统运行的同时，在当前界面对应的系统中选择将其他系统进行冻结，并且，已经被冻结的系统只能由具有管理员权限的安全操作系统进行唤醒。也就是说，采用了上述针对多系统移动终端的系统冻结与唤醒的方法和装置之后，可以直接在当前系统中发送冻结指令给需要冻结的系统，直接将该系统的相关应用程序进行冻结，避免了传统技术中必须在该系统中必 须逐一将需要冻结的系统进行冻结的多次操作，减少了用户在冻结系统或应用时的操作次数，提高了基于多系统的移动终端的系统冻结的操作便利性。
进一步地，用户只能在具有管理员权限的安全操作系统中才能将已经冻结的系统进行唤醒或者解冻，从而使得已经被冻结的系统不能随意被解冻，提高了用户数据的安全性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
其中：
图1为一个实施例中一种多系统的冻结与唤醒方法的流程示意图；
图2为一个实施例中一种多系统的冻结与唤醒装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为解决传统技术中的多系统终端的应用程序以及操作系统的冻结因为需要进行多次操作而存在的操作的便利性不足的技术问题，在本实施例中，特提出了一种多系统的冻结与唤醒方法。该方法的实现可依赖于计算机程序，该计算机程序可运行于基于冯诺依曼体系的计算机系统之上。该计算机程序可以是系统的冻结与唤醒程序。需要说明的是，在本实施例中，上述多系统的冻结与唤醒方法是基于安装了多个系统的计算机设备，例如：安装了安全系统和普通系统的双系统手机，又例如安装了安全操作系统、第一操作系统和第二操作系统(第一操作系统和第二操作系统为普通系统)的三系统手机。
在本实施例中，智能终端的多系统是指该智能终端安装的操作系统不止一个，且其中一个特定的系统为具有管理员权限的操作系统，该系统可被称为管理操作系统或者安全操作系统，其他系统为权限平等的普通操作系统。需要说明的是，在本实施例中，多个系统是可以同时运行的，例如，对于安装了S、A、B三个操作系统的智能手机终端来讲，在终端的显示界面显示的为A操作系统，也就是说，当前显示界面显示的运行系统为A系统，但是同时系统S以及系统B也可以处于运行状态，用户可以通过系统切换操作来切换当前界面显示的操作系统。
具体的，如图1所示，上述多系统的冻结与唤醒方法包括如下步骤：
步骤S102：在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级。
冻结指令为用户通过终端输入的冻结指令，在该指令中携带了需要冻结的系统，即需要冻结的系统的标识。
在本实施例中，第一操作系统为发出冻结指令的操作系统，第二操作系统为需要被冻结的操作系统。需要说明的是，在本实施例中，发出冻结指令的第一操作系统的操作权限等级高于或者等于被冻结的第二操作系统的操作权限等级，也就是说，操作系统在发出冻结指令时，针对的被冻结的操作系统只能是操作权限等级相同或者操作权限等级更低的操作系统，不能冻结操作权限等级高于自身的操作系统。
在本实施例中，第一操作系统可以是具有管理员权限的安全操作系统(即第二操作系统的冻结指令是由安全操作系统发出的)，也可以是拥有普通权限的普通操作系统；而第二操作系统只能是拥有普通权限的普通操作系统而不能是安全操作系统。也就是说，在本身实施例中，具有管理员权限的操作系统可以冻结其他系统，但是其他普通系统无法冻结安全系统；而普通系统之间可以相互进行冻结。
在本实施例中，与终端当前的显示界面对应的操作系统为第一操作系统，并且在第一操作系统中的系统冻结应用或者系统冻结界面中输入冻结指令，并 选择需要冻结的操作系统，即在上述冻结指令中包含了需要冻结的操作系统的标识，即第二操作系统的标识。
需要说明的是，在本实施例中，第一操作系统与第二操作系统均处于运行状态，也就是说，发出冻结指令的操作系统与被冻结的操作系统均处于运行状态，即不处于运行状态的操作系统既无法发出冻结指令，也无法被冻结。
步骤S104：在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
在第一操作系统发出冻结指令之后，系统根据接收到的冻结指令以及获取到的冻结指令中的第二操作系统标识，在第一操作系统中通过第一操作系统向第二操作系统发送通知，在该通知中携带了相关的冻结指令信息。
具体的，在本实施例中，上述在所述第一操作系统中通知第二操作系统的步骤具体为：在第一操作系统中通过Intent机制的广播冻结指令给第二操作系统。
在本实施例中，Intent负责同一个终端上的Android系统与Android系统之间的通信，也就是说，第一操作系统与第二操作系统之间的数据的发送和传输是通过Intent提供的系统之间通信媒介实现的。第一操作系统可以通过Intent向第二操作系统发送数据。
需要说明的是，在本实施例中，第一操作系统通知第二操作系统的实现还可以通过其他方式实现两个操作系统之间的通信。例如，第一操作系统还可以通过广播的形式向各个操作系统发送广播，第二操作系统在接收到广播之后通过解析广播中的相关信息获知广播中的相关信息，例如，获知该广播是关于冻结系统的。需要说明的是，在本实施例中，在使用广播实现操作系统之间的通信的过程中，安全操作系统也可以接受相关的冻结广播，从而获知系统的冻结信息。
在第一操作系统通知第二操作系统需要将第二操作系统进行冻结之后，第二操作系统接收到相关的通知并解析通知中的相关信息，然后根据解析到的相关信息进行冻结系统的相关操作，即进行自冻结。在本实施例中，操作系统在被冻结之后还保留有唤醒监听进程或线程，以便操作系统在被冻结之后还可以被解冻或唤醒。
具体的，上述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程的步骤具体为：所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
访问权限等级为操作系统的所有应用(也就是全部应用)的可访问状态，例如，所有应用均不可访问，再例如，仅隐私应用不可访问等。在本实施例中，访问权限等级至少包括全部应用不可访问和仅电话与短信应用可访问两个等级，用户还可以根据需要设置其他访问权限等级。
在访问权限等级已知的情况下，可以通过访问权限等级获取与该访问权限等级对应的具体设置，即获取操作系统的应用的访问状态设置。然后根据访问权限等级中的应用的访问状态设置，将第二操作系统中的所有应用的运行时的数据进行缓存，也就是说，根据冻结指令将需要冻结的数据进行保存，以便在将系统进行解冻时根据冻结时保存的数据进行解冻。
在本实施例中，用户在输入冻结指令的时候可以选择对应的访问权限等级，并且该访问权限等级可以包含在冻结指令中；又或者，可以设定默认的访问权限等级，在不指定的情况下，默认将已设定的默认权限等级添加到冻结指令中去。
需要说明的是，因为在访问权限等级中包含了当前的系统需要冻结的应用，因此在访问权限等级为仅电话与短信应用可访问的情况下，上述操作即为将除了电话和短信应用之外的其他应用的数据进行保存，但保留运行唤醒监听进/线程。
被冻结的操作系统在被冻结之后，还需要在不要被继续冻结的时候进行解冻或者唤醒，以便用户可以继续使用该操作系统。在本实施例中，上述多系统的冻结与唤醒方法还包括了如下步骤S202-S204：
步骤S202：在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级。
在本实施中，不具有管理员权限的普通系统不具备解冻其他操作系统的权限，也就是说，操作系统的解冻只能由具有管理员权限的安全操作系统进行操作，因此，解冻指令的生成以及接收均只能是在安全操作系统中进行，即安全 操作系统的操作权限等级是高于普通系统的操作权限等级的。
解冻指令即为用户通过终端在安全操作系统中的操作系统解冻页面或者操作系统解冻应用，输入的解冻已经被冻结的第二操作系统的解冻指令，在该指令中携带了需要解冻的操作系统(即第二操作系统)的标识。
进一步地，终端接收到解冻指令之后，对该解冻指令进行解析，根据在解冻指令中包含的信息确定下一步操作，即步骤S204。
步骤S204：在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
在步骤S202之后，根据接收到的针对第二操作系统的解冻指令，在安全操作系统中通过安全操作系统向第二操作系统发送通知，在该通知中携带了与解冻指令对应的相关信息。
具体的，在本实施例中，上述在所述安全操作系统中通知所述第二操作系统的步骤具体为：在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
在本实施例中，Intent负责同一个终端上的Android系统与Android系统之间的通信，也就是说，安全操作系统与第二操作系统之间的数据的发送和传输是通过Intent提供的系统之间通信媒介实现的。安全操作系统可以通过Intent向第二操作系统发送数据。
需要说明的是，在本实施例中，安全操作系统通知第二操作系统的实现还可以通过其他方式实现两个操作系统之间的通信。例如，安全操作系统还可以通过广播的形式向各个操作系统发送广播，第二操作系统在接收到广播之后通过解析广播中的相关信息获知广播中的相关信息，例如，获知该广播是关于冻结系统的。
在安全操作系统通知第二操作系统需要将已经被冻结的第三操作系统进行解冻之后，第二操作系统通过唤醒监听进程/线程接收到安全操作系统发送的通知并解析该通知中的相关数据，然后根据解析到的相关数据对系统进行自解冻。在本实施例中，自解冻的过程即将冻结的过程中冻结的应用或者进程恢复运行。
具体的，上述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤 醒的步骤具体为：所述第二操作系统通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
如前所述，操作系统在被冻结的时候会将操作系统中的相关应用以及进程的数据进行保存，在本步骤中，操作系统进行解冻的过程中，将在操作系统冻结的过程中缓存的所有操作系统运行的所有数据进行恢复，也就是说，将缓存的所有应用以及进程/线程的运行数据从缓存中读取并进行恢复运行，这个过程即为自唤醒的过程，也即是已冻结系统的解冻或者唤醒过程。
此外，为解决传统技术中的多系统终端的应用程序以及操作系统的冻结因为需要进行多次操作而存在的操作的便利性不足的技术问题，在一个实施例中，还提出了一种多系统的冻结与唤醒装置。
具体的，如图2所示，上述多系统的冻结与唤醒装置包括冻结指令接收模块102、冻结模块104，其中：
冻结指令接收模块102用于在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；
冻结模块104用于在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
可选的，在一个实施例中，上述装置还包括了解冻指令接收模块106、解冻模块108，其中：所述解冻指令接收模块106用于在在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级；所述解冻模块108用于在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
可选的，在一个实施例中，上述冻结模块104还用于：所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
可选的，在一个实施例中，上述解冻模块108还用于：所述第二操作系统 通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
可选的，在一个实施例中，所述访问权限等级至少包括全部应用不可访问和仅电话与短信应用可访问两个等级。
可选的，在一个实施例中，上述冻结指令接收模块102还用于：在所述第一操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
可选的，在一个实施例中，上述解冻指令接收模块106还用于：在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
实施本发明实施例，将具有如下有益效果：
采用了上述多系统的冻结与唤醒方法和装置之后，对于安装了多系统的移动终端来讲，可以在多个系统运行的同时，在当前界面对应的系统中选择将其他系统进行冻结，并且，已经被冻结的系统只能由具有管理员权限的安全操作系统进行唤醒。也就是说，采用了上述针对多系统移动终端的系统冻结与唤醒的方法和装置之后，可以直接在当前系统中发送冻结指令给需要冻结的系统，直接将该系统的相关应用程序进行冻结，避免了传统技术中必须在该系统中必须逐一将需要冻结的系统进行冻结的多次操作，减少了用户在冻结系统或应用时的操作次数，提高了基于多系统的移动终端的系统冻结的操作便利性。
进一步地，用户只能在具有管理员权限的安全操作系统中才能将已经冻结的系统进行唤醒或者解冻，从而使得已经被冻结的系统不能随意被解冻，提高了用户数据的安全性。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本发明较佳实施例而已，当然不能以此来限定本发明之权利范围，因此依本发明权利要求所作的等同变化，仍属本发明所涵盖的范围。

Claims (11)

  1. 一种多系统的冻结与唤醒方法，其特征在于，包括：
    在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；
    在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
  2. 根据权利要求1所述的多系统的冻结与唤醒方法，其特征在于，所述方法还包括：
    在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级；
    在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
  3. 根据权利要求1或2所述的多系统的冻结与唤醒方法，其特征在于，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程的步骤具体为：
    所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
  4. 根据权利要求2所述的多系统的冻结与唤醒方法，其特征在于，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒的步骤具体为：
    所述第二操作系统通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
  5. 根据权利要求3所述的多系统的冻结与唤醒方法，其特征在于，所述访问权限等级至少包括全部应用不可访问和仅电话与短信应用可访问两个等 级。
  6. 根据权利要求2所述的多系统的冻结与唤醒方法，其特征在于，所述在所述第一操作系统中通知所述第二操作系统的步骤具体为：
    在所述第一操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统；
    所述在所述安全操作系统中通知所述第二操作系统的步骤具体为；
    在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
  7. 一种多系统的冻结与唤醒装置，其特征在于，包括：
    冻结指令接收模块，用于在第一操作系统中接收冻结指令，获取冻结指令对应的第二操作系统的标识，所述第一操作系统和所述第二操作系统均处于运行状态，所述第二操作系统的操作权限等级不高于所述第一操作系统的操作权限等级；
    冻结模块，用于在所述第一操作系统中通知所述第二操作系统，所述第二操作系统接收到所述通知之后自冻结但保留唤醒监听进/线程。
  8. 根据权利要求7所述的多系统的冻结与唤醒装置，其特征在于，所述装置还包括解冻指令接收模块和解冻模块，其中：
    所述解冻指令接收模块用于在安全操作系统中接收针对所述第二操作系统的解冻指令，所述安全操作系统的操作权限等级不低于所述第一操作系统的操作权限等级；
    所述解冻模块用于在所述安全操作系统中通知所述第二操作系统，所述第二操作系统通过唤醒监听进/线程接收所述通知之后自唤醒。
  9. 根据权利要求7所述的多系统的冻结与唤醒装置，其特征在于，所述冻结模块还用于：
    所述第二操作系统获取所述通知中包含的访问权限等级，根据所述访问权 限等级将所述第二操作系统运行时的数据缓存，但保留运行唤醒监听进/线程。
  10. 根据权利要求8所述的多系统的冻结与唤醒装置，其特征在于，所述解冻模块还用于：
    所述第二操作系统通过保留运行的唤醒监听进/线程接收所述通知，由缓存中恢复所述第二操作系统中运行时的数据。
  11. 根据权利要求8所述的多系统的冻结与唤醒装置，其特征在于，所述冻结指令接收模块还用于：
    在所述第一操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统；
    所述解冻指令接收模块还用于：
    在所述安全操作系统中通过Intent机制的广播所述冻结指令给所述第二操作系统。
PCT/CN2016/080623 2016-03-24 2016-04-29 一种多系统的冻结与唤醒方法及装置 Ceased WO2017161638A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610173367.2A CN105786607B (zh) 2016-03-24 2016-03-24 一种多系统的冻结与唤醒方法及装置
CN201610173367.2 2016-03-24

Publications (1)

Publication Number Publication Date
WO2017161638A1 true WO2017161638A1 (zh) 2017-09-28

Family

ID=56390841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080623 Ceased WO2017161638A1 (zh) 2016-03-24 2016-04-29 一种多系统的冻结与唤醒方法及装置

Country Status (2)

Country Link
CN (1) CN105786607B (zh)
WO (1) WO2017161638A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109992360A (zh) * 2017-12-29 2019-07-09 广东欧珀移动通信有限公司 进程处理方法和装置、电子设备、计算机可读存储介质
WO2025195433A1 (zh) * 2024-03-20 2025-09-25 北京地平线信息技术有限公司 基于虚拟机的操作系统热备份方法、装置、设备和介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106250483A (zh) * 2016-07-29 2016-12-21 宇龙计算机通信科技(深圳)有限公司 一种应用运行数据冻结的方法、装置以及终端
CN107066320B (zh) * 2017-01-19 2021-06-15 努比亚技术有限公司 一种Android进程冻结和解冻的装置及方法
CN108401455B (zh) * 2017-09-07 2021-10-01 深圳前海达闼云端智能科技有限公司 一种多系统控制方法、控制装置及移动终端
CN110032397B (zh) * 2018-01-10 2023-01-31 Oppo广东移动通信有限公司 应用处理方法和装置、电子设备、计算机可读存储介质
CN108280020B (zh) * 2018-01-23 2021-09-14 广州视源电子科技股份有限公司 计算机设备的监控方法、装置、终端及计算机存储介质
CN114201221B (zh) * 2020-09-02 2023-03-21 成都鼎桥通信技术有限公司 基于双系统的系统关闭方法、设备及存储介质
CN114721717B (zh) * 2020-12-22 2023-09-19 成都鼎桥通信技术有限公司 基于双系统的手机管理系统mdm指令调用方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1906583A (zh) * 2004-09-29 2007-01-31 索尼株式会社 信息处理设备、中断处理控制方法、以及计算机程序
CN101052949A (zh) * 2004-08-18 2007-10-10 扎鲁纳股份有限公司 操作系统
CN102043662A (zh) * 2009-10-23 2011-05-04 伟视科技股份有限公司 多操作系统的数据修改方法
CN103180829A (zh) * 2010-10-22 2013-06-26 三菱电机株式会社 中断信号接收装置及计算机装置
US20140075176A1 (en) * 2012-09-13 2014-03-13 Ricoh Company, Ltd. Information processing apparatus

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8621494B2 (en) * 2011-09-12 2013-12-31 Microsoft Corporation Managing processes within suspend states and execution states
CN103544027B (zh) * 2012-07-13 2017-05-24 联想(北京)有限公司 控制应用更新的方法及电子设备
CN103744681A (zh) * 2014-01-16 2014-04-23 广州市久邦数码科技有限公司 一种冻结/解冻程序的方法及系统
CN104142859B (zh) * 2014-07-31 2016-10-26 努比亚技术有限公司 一种双系统的快速切换方法、装置和移动终端
CN104965733A (zh) * 2015-06-11 2015-10-07 广州市久邦数码科技有限公司 一种批量禁用/停止应用程序的方法及其系统
CN105204932A (zh) * 2015-08-26 2015-12-30 北京元心科技有限公司 智能终端及其应用程序状态控制方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101052949A (zh) * 2004-08-18 2007-10-10 扎鲁纳股份有限公司 操作系统
CN1906583A (zh) * 2004-09-29 2007-01-31 索尼株式会社 信息处理设备、中断处理控制方法、以及计算机程序
CN102043662A (zh) * 2009-10-23 2011-05-04 伟视科技股份有限公司 多操作系统的数据修改方法
CN103180829A (zh) * 2010-10-22 2013-06-26 三菱电机株式会社 中断信号接收装置及计算机装置
US20140075176A1 (en) * 2012-09-13 2014-03-13 Ricoh Company, Ltd. Information processing apparatus

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109992360A (zh) * 2017-12-29 2019-07-09 广东欧珀移动通信有限公司 进程处理方法和装置、电子设备、计算机可读存储介质
WO2025195433A1 (zh) * 2024-03-20 2025-09-25 北京地平线信息技术有限公司 基于虚拟机的操作系统热备份方法、装置、设备和介质

Also Published As

Publication number Publication date
CN105786607A (zh) 2016-07-20
CN105786607B (zh) 2019-11-12

Similar Documents

Publication Publication Date Title
CN105786607B (zh) 一种多系统的冻结与唤醒方法及装置
RU2739290C1 (ru) Способ управления многоадресным однонаправленным каналом и оконечное устройство
US20210092634A1 (en) Method Of Processing Network Slice Based Congestion, Device And System Thereof
US9338642B2 (en) Method and apparatus for processing application program, and mobile terminal therefor
KR102725637B1 (ko) 사물 인터넷 통신 방법 및 그 전자 장치
CN107844342B (zh) 应用程序保活的管控方法、装置及存储介质和移动终端
EP3418892B1 (en) Method and device for managing and controlling broadcast, and terminal
US11096177B2 (en) Operation mode switching method and user equipment
US11895364B2 (en) Bluetooth connection method and television
CN113784369B (zh) 功率余量报告phr上报方法、装置及终端
US20230224216A1 (en) System and method for subscription limitation enforcement in distributed system
JP2021525494A (ja) Ｐｄｃｃｈブラインド検出方法、端末及びネットワーク側機器
CN103294562A (zh) 双操作系统共用周边装置的方法以及电子装置
WO2019238003A1 (zh) 进入低功耗状态的方法及装置、存储介质
US11816200B2 (en) Terminal and method for managing launch of an application of a terminal
US20140184394A1 (en) Communication device and method for controlling electronic device
WO2022017359A1 (zh) 直接通信启动控制方法及相关设备
WO2022033429A1 (zh) 数据发送处理方法、资源配置方法及相关设备
CN112770413B (zh) Rrc状态控制方法、装置、移动终端及可读存储介质
CN107844341B (zh) 进程启动的管控方法、装置及存储介质和移动终端
KR20230124733A (ko) 검색 공간 그룹 전환 방법 및 장치
CN110018905B (zh) 信息处理方法、装置、计算机设备和计算机可读存储介质
WO2021164593A1 (zh) 数据传输方法及装置
WO2020220868A1 (zh) 广播控制方法、终端及计算机可读存储介质
KR102514841B1 (ko) 기기의 어플리케이션에 선택적으로 네트워크 기능을 제공하는 기술 및 방법

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16894991

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16894991

Country of ref document: EP

Kind code of ref document: A1