[go: up one dir, main page]

WO2015081678A1 - Procédé et appareil de chargement d'interface utilisateur et terminal mince - Google Patents

Procédé et appareil de chargement d'interface utilisateur et terminal mince Download PDF

Info

Publication number
WO2015081678A1
WO2015081678A1 PCT/CN2014/079522 CN2014079522W WO2015081678A1 WO 2015081678 A1 WO2015081678 A1 WO 2015081678A1 CN 2014079522 W CN2014079522 W CN 2014079522W WO 2015081678 A1 WO2015081678 A1 WO 2015081678A1
Authority
WO
WIPO (PCT)
Prior art keywords
authentication information
user
interface
user interface
legal
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/CN2014/079522
Other languages
English (en)
Chinese (zh)
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2015081678A1 publication Critical patent/WO2015081678A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN

Definitions

  • the present invention relates to the field of communications, and in particular to a user interface interface loading method, device, and thin end
  • a thin terminal is a user equipment that uses a cloud server resource, and is generally a built-in independent embedded operating system, which can be connected to a desktop device running on a server through various protocols, in order to fully utilize existing resources.
  • the architecture also supports some modifications to the traditional desktop, installing some plug-ins, so that they also have the ability to connect to the desktop running on the server.
  • the operating system platforms that can be used in existing thin terminals include: Android (Andorid) platform, Microsoft Windows Embedded Standard 7, (WES7) platform, Ubuntu platform, etc., and in some cases can support Execution processing of local and cloud applications and features.
  • an important function of the thin terminal is to support multi-user login, achieve rights management for each user, maximize sharing of software resources, and protect their own private data.
  • In the early days of portable devices there was less need for multiple accounts to be logged in on one device. But other desktop terminals, such as computers, tablets, etc., are more commonly shared with family, colleagues, and friends.
  • these early Android devices did not support multi-user login and control the permissions of multiple users, which may lead to leakage of user data and illegal use of the device. Since the 4.2 version of Android, Android has officially joined the multi-user login function, which can restrict the permissions of different users after login.
  • a user interface interface loading method including: determining, according to a first authentication information that is currently legally determined by a user equipment, an available function and an application corresponding to the first authentication information;
  • the first user interface interface is configured to provide an interface for performing an available function and an application corresponding to the first authentication information.
  • the method further includes: receiving second authentication information input by the user; determining whether the second authentication information is legal; and determining that the result is legal, determining An available function and an application corresponding to the second authentication information; loading a second user interface, wherein the second user interface is configured to provide an interface for executing an available function and an application corresponding to the second authentication information .
  • determining whether the second authentication information is legal comprises: sending the second authentication information to the server, where the server is configured to determine the legality of the second authentication information, and Returning the judgment result; receiving the judgment result returned by the server; and determining, according to the judgment result, whether the second authentication information is legal.
  • determining whether the second authentication information is legal comprises: determining whether the second authentication information is consistent with the locally saved authentication information of the user equipment, where, if the determination result is consistent, determining The second authentication information is legal.
  • the locally saved authentication information is synchronized with the server according to a predetermined policy, where the locally saved authentication information is authentication information that the user has logged in on the user equipment.
  • the first authentication information is determined after the authentication is performed according to the authentication information input by the user, or the first authentication information is automatically loaded by the user equipment after the system is started.
  • a user interface interface loading apparatus including: a determining module, configured to determine, according to the first authentication information that is currently legally determined by the user equipment, the first authentication information An available function and an application; a loading module, configured to load a first user interface interface, wherein the first user interface interface is configured to provide an interface for executing an available function and an application corresponding to the first authentication information.
  • the device further includes: a receiving module, configured to receive second authentication information input by the user; a determining module, configured to determine whether the second authentication information is legal; and a second determining module, configured to determine the result In the case of being legal, the available functions and applications corresponding to the second authentication information are determined; the second loading module is configured to load the second user interface, wherein the second user interface is used to provide an execution The available functions corresponding to the second authentication information and the interface of the application.
  • a receiving module configured to receive second authentication information input by the user
  • a determining module configured to determine whether the second authentication information is legal
  • a second determining module configured to determine the result In the case of being legal, the available functions and applications corresponding to the second authentication information are determined
  • the second loading module is configured to load the second user interface, wherein the second user interface is used to provide an execution The available functions corresponding to the second authentication information and the interface of the application.
  • the determining module includes: a sending unit, configured to send the second authentication information to the server, where the server is configured to determine the legality of the second authentication information, and return a determination unit; the receiving unit is configured to receive the determination result returned by the server; and the determining unit is configured to determine, according to the determination result, whether the second authentication information is legal.
  • a thin terminal is provided, including the user interface interface loading device described above.
  • the first authentication information corresponding to the first authentication information is determined according to the first authentication information that is currently legalized by the user equipment, and the first user interface is loaded, where the first user interface is used.
  • FIG. 2 is a schematic structural diagram of a user interface interface loading device according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a preferred structure of a user interface interface loading device according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a preferred structure of a user interface interface loading device according to an embodiment of the invention.
  • FIG. 6 is a schematic flowchart of user authority initialization according to a preferred embodiment of the present invention
  • FIG. 7 is a schematic flowchart of normal user rights switching according to a preferred embodiment of the present invention
  • FIG. 8 is a schematic flow chart of administrator user authority switching according to a preferred embodiment of the present invention.
  • FIG. 1 is a schematic flowchart of a user interface interface loading method according to an embodiment of the present invention. As shown in FIG.
  • Step S102 According to a current user equipment
  • the first authentication information is used to determine the available functions and applications corresponding to the first authentication information.
  • Step S104 The first user interface is loaded, where the first user interface is configured to provide the first authentication information.
  • the available features and interfaces to the application Through the above steps, the corresponding available functions and applications are determined according to the first authentication information currently validated by the mobile terminal, and the first user interface interface for providing the interfaces of the available functions and applications is loaded.
  • the application software and the data of each user are isolated from each other.
  • the user interface is used to provide an interface for the user to execute the available functions and applications, thereby enabling the application software and The data can be shared, and the multi-user login function is used to waste the storage resources caused by the isolation of application software and data of each user, thereby avoiding waste of storage resources and effectively realizing the rational use of storage resources.
  • the first user interface interface is a unique user interface interface of the user equipment, or is set as a user interface interface that is forced to be displayed by default in the plurality of user interfaces. In the case that the authority corresponding to the authentication information does not have a corresponding operation authority, the user interface interface is set such that the user cannot exit or switch to another user interface interface.
  • the user may replace the logged-in (ie, currently legal) authentication information, and the user equipment receives the second authentication information input by the user, and then determines the second Whether the authentication information is legal, and if the judgment result is legal, determining the available functions and applications corresponding to the second authentication information, and loading the second user interface interface, where the second user interface is used to provide the second execution
  • the available functions corresponding to the authentication information and the interface of the application In this way, user replacement is achieved.
  • the user operates the new application and available functions through the new user interface interface.
  • cloud authentication, local authentication, or a combination of cloud authentication and local authentication may be adopted.
  • the user equipment may send the second authentication information to the server (ie, the cloud); the server determines the legality of the received second authentication information, and returns a determination result; After receiving the judgment result returned by the server, the user equipment determines whether the second authentication information is legal according to the judgment result.
  • the application information and the available function information corresponding to the second authentication information may be carried in the determination result, and the application information and the available function information corresponding to the second authentication information may also be saved. Local to the user device and synchronized with the server through a predetermined policy.
  • the user equipment can determine whether the second authentication information is consistent with the authentication information saved locally by the user equipment, and If the judgment result is consistent, it is determined that the second authentication information is legal. In this manner, the user equipment can implement temporary authentication under the offline state, and the user can use the application and the available function saved locally by the user equipment under the authority of the authentication.
  • the user equipment can provide an interface setting to establish a connection between the user equipment and the cloud, and perform authentication by means of cloud authentication. After the authentication, the user is authenticated.
  • the cloud application or available functionality can be executed through the user device.
  • the locally saved authentication information is synchronized with the server according to a predetermined policy.
  • the authentication information stored locally in the user equipment and the authentication information in the server may be synchronized periodically or irregularly.
  • the authentication information is stored in an encrypted manner, and the corresponding application information and the information of the available functions may also be saved along with the authentication information.
  • the locally saved authentication information is authentication information that the user has logged in on the user equipment.
  • the first authentication information may be determined after the authentication is performed according to the authentication information input by the user, or the first authentication information may also be automatically loaded by the user equipment after the system is started, for example, the first authentication.
  • the information may be the default authentication information of the system, corresponding to the basic application and the basic available functions, wherein when the default authentication information is used, the user has the lowest operating authority for the mobile terminal.
  • the correspondence between the authentication information and the application and the available functions may be set according to the configuration of the user. In general, the lower the operating permissions, the fewer executable applications and available functions; for example, when the authentication information has administrator privileges, almost all applications and available functions can be executed, and System security, for authentication information of non-administrator rights, the system settings, process management, document management and other functions and application operation interfaces should be blocked.
  • the embodiment also provides a user interface interface loading device, which is used to implement the user interface interface loading method.
  • FIG. 2 is a schematic structural diagram of a user interface interface loading apparatus according to an embodiment of the present invention.
  • the apparatus includes: a determining module 22 and a loading module 24, wherein the determining module 22 is set to be legal according to the user equipment.
  • the first authentication information is used to determine the available functions and applications corresponding to the first authentication information.
  • the loading module 24 is coupled to the determining module 22, and is configured to load the first user interface, where the first user interface is used to provide the first An available function corresponding to the authentication information and an interface of the application.
  • the modules and units involved in the embodiments of the present invention may be implemented by software, or may be implemented by hardware.
  • a processor includes a determining module 22 and a loading module 24.
  • the name of these modules does not constitute a limitation on the module itself in some cases.
  • the determining module 22 may also be described as "set to determine the first authentication according to the first authentication information currently legalized by the user equipment. The information corresponds to the available functions and modules of the application.”
  • FIG. 3 is a schematic diagram of a preferred structure of a user interface interface loading apparatus according to an embodiment of the present invention. As shown in FIG.
  • the apparatus further includes: a receiving module 32, configured to receive second authentication information input by a user;
  • the determining module 34 is coupled to the receiving module 32, and is configured to determine whether the second authentication information is legal.
  • the second determining module 36 is coupled to the determining module 34, and configured to determine, corresponding to the second authentication information, that the second authentication information is valid.
  • the second loading module 38 is coupled to the second determining module 36, configured to load the second user interface interface, wherein the second user interface is configured to provide the available functions and applications corresponding to the second authentication information.
  • the interface of the program Preferably, the determining module 22 and the second determining module 36 may be the same module, and the loading module 24 and the second loading module 38 may be the same module.
  • the determining module 34 includes: a sending unit 342, configured to send second authentication information to a server, The server is configured to determine the validity of the second authentication information, and returns a determination result.
  • the receiving unit 344 is coupled to the sending unit 342 by the server, and is configured to receive the determination result returned by the server.
  • the first determining unit 346 The method is coupled to the receiving unit 344, and is configured to determine whether the second authentication information is legal according to the determination result.
  • FIG. 5 is a schematic diagram of a preferred structure of a user interface interface loading apparatus according to an embodiment of the present invention. As shown in FIG.
  • the determining module 34 includes: a second determining unit 348, configured to determine second authentication information and a user. Whether the authentication information saved locally is consistent, and if the judgment result is consistent, the second authentication information is determined to be legal.
  • the device further includes: a synchronization module, configured to synchronize the locally saved authentication information with the server according to the predetermined policy, wherein the locally saved authentication information is the authentication information that the user logs in on the user equipment.
  • the first authentication information is determined after the authentication is performed according to the authentication information input by the user, or the first authentication information is automatically loaded by the user equipment after the system is started.
  • This embodiment also provides a thin terminal, including the user interface interface loading device described above.
  • the preferred embodiment provides a method for implementing multi-user rights switching of an Android thin terminal, and relates to a multi-user switching method based on Android thin terminal permission control in a cloud computing environment.
  • the multi-user switching method in the Android thin terminal in the cloud computing environment provided by the preferred embodiment includes the following steps: Step 1: The thin terminal is started by an initial account by default, for example: 1 When the thin terminal is booted, the specific initial account is logged in. . This account has the lowest operational privileges and can only operate some of the most commonly used applications.
  • Step 2 After the system is booted, it does not enter the android desktop, but enters the multi-user rights management program and initializes the application shortcut list.
  • the management program requires full-screen display; a list of application shortcuts corresponding to the rights is provided, and the user can click the shortcut to run the related program; and the account switching function is provided to allow different application operation rights to be obtained through user switching.
  • Normally privileged users cannot exit the rights management program, nor can they manually switch to the background to operate the android raw desktop. The administrator user can choose whether to exit the rights management program and return to the android original desktop.
  • Step 2 Initialize or normal rights users switch to other rights accounts, for example:
  • Step 1 Initialize or normal access user enters the account switching module, enters the relevant account and password, and then initiates an authentication request to the cloud server.
  • the cloud server authenticates the account and password, and returns the result to the thin terminal rights management program.
  • the current user authority is determined. If you switch to a normal user, the rights management program refreshes the program shortcut list and provides related application operation entries. If you switch to the administrator user, the rights management program lists all application shortcuts, and when you can open the exit function, automatically exit the current program and enter the android original desktop. After entering the android original desktop, the admin user can run any application in the current android system.
  • Step 3 If the authentication fails, the cloud terminal only gives relevant prompts and does not perform other operations. Step 3: The administrator user switches to another rights account, for example:
  • the administrator user runs the multi-user rights management program in the android desktop, enters the account switching module, inputs the relevant account and password, and initiates an authentication request to the cloud server.
  • FIG. 6 is a schematic flowchart of user rights initialization according to a preferred embodiment of the present invention. As shown in FIG. 6, the process includes: Step S602, booting up, and initializing an account login by default. Step S604, after the system is successfully started, the multi-user rights management program runs automatically. Ordinary users cannot exit the program, nor can they switch the program to run in the background. Step S606, the multi-user rights management program provides a corresponding application shortcut list according to the user rights.
  • FIG. 7 is a schematic flowchart of a common user rights switching according to a preferred embodiment of the present invention.
  • Step S72 A universal user enters a multi-user right switching module, inputs account information, and initiates authentication to a cloud server. request.
  • step S74 the authentication is successful. If you switch to another normal user, the application list is refreshed, and the application shortcut corresponding to the permission is provided. If you switch to the administrator, also update the corresponding application list, and open the multi-user rights management program to exit the function, then exit the program.
  • step S76 if the authentication fails, a related prompt is displayed.
  • FIG. 8 is a schematic flowchart of an administrator user rights switching according to a preferred embodiment of the present invention. As shown in FIG.
  • Step S82 An administrator user enters a multi-user rights switching module, and inputs account information to the cloud.
  • the server initiates an authentication request.
  • step S84 the authentication is successful. If you switch to another administrator user, update the application list and exit the multi-user rights management program. If you switch to a normal user, the application list is updated and the exit function is closed.
  • step S86 if the authentication fails, a related prompt is displayed.
  • a customized multi-user management program and a cloud server authentication method are adopted, so that the Android thin terminal can provide different applications for users with different rights and make multiple users. Can switch to each other.
  • the method uses the initialization user authority to effectively ensure the basic application operation requirements, and can also implement application access control under different permissions through multi-user switching.
  • the thin terminal adopting the method can meet the requirements of multi-user rights switching and application sharing in the current cloud computing environment.
  • Industrial Applicability According to the embodiment of the present invention, the first authentication information corresponding to the first authentication information is determined according to the first authentication information that is currently legally determined by the user equipment; and the first user interface is loaded, where the first user interface is The interface is used to provide an interface for performing the function and the application corresponding to the first authentication information, and solves the problem that the multi-user login function wastes the storage resources caused by the isolation of the application software and data of each user, thereby avoiding the storage.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de chargement d'interface utilisateur et un terminal mince. Le procédé consiste à : déterminer, conformément à des premières informations d'authentification indiquant qu'un équipement d'utilisateur actuel est autorisé, une fonction et une application disponibles correspondant aux premières informations d'authentification ; et charger une première interface utilisateur, la première interface utilisateur étant utilisée pour fournir une interface d'exécution de la fonction et de l'application disponibles correspondant aux premières informations d'authentification. La présente invention résout un problème de gaspillage d'une ressource mémoire provoqué par un isolement mutuel, appliqué par une fonction de connexion multi-utilisateur, de logiciel d'application et de données d'utilisateurs, évite un gaspillage d'une ressource mémoire, et met en œuvre efficacement une utilisation correcte d'une ressource mémoire.
PCT/CN2014/079522 2013-12-06 2014-06-09 Procédé et appareil de chargement d'interface utilisateur et terminal mince Ceased WO2015081678A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310659645.1A CN104700039A (zh) 2013-12-06 2013-12-06 用户接口界面加载方法、装置和瘦终端
CN201310659645.1 2013-12-06

Publications (1)

Publication Number Publication Date
WO2015081678A1 true WO2015081678A1 (fr) 2015-06-11

Family

ID=53272816

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/079522 Ceased WO2015081678A1 (fr) 2013-12-06 2014-06-09 Procédé et appareil de chargement d'interface utilisateur et terminal mince

Country Status (2)

Country Link
CN (1) CN104700039A (fr)
WO (1) WO2015081678A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107797721B (zh) * 2016-09-07 2020-10-09 腾讯科技（深圳）有限公司 一种界面信息显示方法及其装置
CN108920202B (zh) * 2018-05-15 2020-09-15 Oppo广东移动通信有限公司 应用预加载管理方法、装置、存储介质及智能终端
CN111309242A (zh) * 2020-02-12 2020-06-19 深圳市丰巢科技有限公司 一种智能柜屏幕显示方法、装置、服务器及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072129A (zh) * 2007-06-25 2007-11-14 北京邮电大学 基于jmx的网络业务管理方法及其应用系统
CN101123756A (zh) * 2007-09-29 2008-02-13 北京邮电大学 支持应用程序接口的多业务生成系统
CN101207864A (zh) * 2006-12-20 2008-06-25 中兴通讯股份有限公司 一种实现手机内多用户管理及信息隐藏的方法
CN101815116A (zh) * 2009-02-20 2010-08-25 中兴通讯股份有限公司 基于多用户的移动电话管理方法与装置
CN103024022A (zh) * 2012-12-06 2013-04-03 中国电信股份有限公司云计算分公司 一种虚拟机应用服务的管控系统和方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100223579A1 (en) * 2009-03-02 2010-09-02 Schwartz Gerry M Iphone application disguiser

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207864A (zh) * 2006-12-20 2008-06-25 中兴通讯股份有限公司 一种实现手机内多用户管理及信息隐藏的方法
CN101072129A (zh) * 2007-06-25 2007-11-14 北京邮电大学 基于jmx的网络业务管理方法及其应用系统
CN101123756A (zh) * 2007-09-29 2008-02-13 北京邮电大学 支持应用程序接口的多业务生成系统
CN101815116A (zh) * 2009-02-20 2010-08-25 中兴通讯股份有限公司 基于多用户的移动电话管理方法与装置
CN103024022A (zh) * 2012-12-06 2013-04-03 中国电信股份有限公司云计算分公司 一种虚拟机应用服务的管控系统和方法

Also Published As

Publication number Publication date
CN104700039A (zh) 2015-06-10

Similar Documents

Publication Publication Date Title
EP3465430B1 (fr) Intégration de navigateur virtuel
KR102048111B1 (ko) 보안 펌웨어 업데이트 기법
EP3049985B1 (fr) Environnement d'exécution séparé jetable pour accéder à un contenu non vérifié
JP5881835B2 (ja) 基本入出力システム（ｂｉｏｓ）の機能にアクセスするウェブベースのインターフェース
EP3179697B1 (fr) Validation de l'identité d'une application mobile de gestion d'applications mobiles
US9319380B2 (en) Below-OS security solution for distributed network endpoints
US9495560B2 (en) Polymorphic virtual appliance rule set
EP2973147B1 (fr) Amorçage web sécurisé basé sur une politique
CN102495750A (zh) 虚拟桌面配置和操作技术
US20140331285A1 (en) Mobile Device Locking with Context
US12015687B2 (en) Securing communications in a network function virtualization (NFV) core network
WO2015188442A1 (fr) Procédé et dispositif de gestion de mots de passe
US9135436B2 (en) Execution stack securing process
WO2015081678A1 (fr) Procédé et appareil de chargement d'interface utilisateur et terminal mince
Bae et al. Spacelord: Private and secure smart space sharing
US8646068B2 (en) Home image content securely isolated from corporate IT
Song et al. App’s auto-login function security testing via Android OS-level virtualization
KR101223981B1 (ko) 안전한 애플리케이션 실행을 위한 가상화 장치, 서버 및 방법
US20150135304A1 (en) Electronic apparatus and control method thereof
CN110365756B (zh) 一种访问方法、电子设备及计算机存储介质
Bricker Unified extensible firmware interface (UEFI) and secure boot: Promise and pitfalls
WO2015196526A1 (fr) Procédé de démarrage de système d'exploitation, dispositif et terminal
JP2013074329A (ja) 携帯電子機器及び制御方法

Legal Events

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

Ref document number: 14867899

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14867899

Country of ref document: EP

Kind code of ref document: A1