WO2015081678A1 - User interface loading method and apparatus and thin terminal - Google Patents
User interface loading method and apparatus and thin terminal Download PDFInfo
- 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
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
Description
用户接口界面加载方法、 装置和痩终端 技术领域 本发明涉及通信领域， 具体而言， 涉及一种用户接口界面加载方法、 装置和瘦终 The present invention relates to the field of communications, and in particular to a user interface interface loading method, device, and thin end
背景技术 瘦终端是一种使用云端服务器资源的用户设备， 一般是一个内嵌了独立的嵌入式 操作系统， 可以通过各种协议连接到运行在服务器上的桌面的设备， 为了充分利用已 有资源， 实现 IT资产的最大化应用， 架构中也支持对传统桌面做一些改造， 安装一些 插件， 使得它们也有能力连接到运行在服务器上的桌面。 现有的瘦终端可以采用的操 作系统平台包括：安卓（Andorid)平台、微软的视窗嵌入式标准 7 (Windows Embedded Standard 7, 简称为 WES7)平台、 Ubuntu平台等， 并在一些情况下可以支持对本地和 云端的应用程序和功能的执行处理。 在云计算环境中， 瘦终端的一个重要的功能就是支持多用户登录， 实现对各用户 的权限管理， 最大化共享软件资源， 并保护自己的私有数据。 早期的携带式设备较少存在一台设备上要求有多个账号登录的需求。 但其他桌面 终端， 如电脑， 平板等， 却较常与家人、 同事、 朋友共享使用。 以早期的使用安卓系 统的设备为例， 这些早期的安卓系统的设备没有对多用户登录的支持， 以及对多用户 的权限控制， 从而可能导致用户资料的泄露和对设备的非法使用。 自安卓系统的 4.2版本后， 安卓正式加入了多用户登陆功能， 可限制不同用户登 录后的权限。 目前这一功能仅适用于采用安卓系统的平板电脑， 其中， 各个用户的应 用软件和数据相互隔离。 即， 每个用户拥有独立的账号、应用、 系统设置和数据文件， 切换用户后无法对其他用户的应用进行共享。 发明人发现， 在存储空间充裕的平板电脑中， 采用各个用户的应用软件和数据相 互隔离的方式时， 用户在使用过程中可能并不会感觉到明显的不便； 但是， 在存储空 间有限的携带式设备（例如手机）， 或者企业级应用的瘦终端设备中， 随着用户数的增 多以及用户数据的不断增加， 必将导致存储资源的浪费和不便， 另一方面也使得设备 存储数据的成本上升。 针对相关技术中的多用户登录功能采用各个用户的应用软件和数据相互隔离导致 的存储资源的浪费的问题， 目前尚未提出有效的解决方案。 发明内容 本发明实施例提供了一种用户接口界面加载方法、 装置和瘦终端， 以至少解决上 述问题。 根据本发明实施例的一个方面， 提供了一种用户接口界面加载方法， 包括： 根据 用户设备当前合法的第一鉴权信息， 确定所述第一鉴权信息对应的可用功能和应用程 序； 加载第一用户接口界面， 其中， 所述第一用户接口界面用于提供执行所述第一鉴 权信息对应的可用功能和应用程序的接口。 优选地， 在加载所述用户接口界面之后， 所述方法还包括： 接收用户输入的第二 鉴权信息； 判断所述第二鉴权信息是否合法； 在判断结果为合法的情况下， 确定所述 第二鉴权信息对应的可用功能和应用程序； 加载第二用户接口界面， 其中， 所述第二 用户接口界面用于提供执行所述第二鉴权信息对应的可用功能和应用程序的接口。 优选地，判断所述第二鉴权信息是否合法包括： 发送所述第二鉴权信息至服务端， 其中， 所述服务端设置为对所述第二鉴权信息的合法性进行判断， 并返回判断结果； 接收所述服务端返回的所述判断结果； 根据所述判断结果， 判断所述第二鉴权信息是 否合法。 优选地， 判断所述第二鉴权信息是否合法包括： 判断所述第二鉴权信息与所述用 户设备的本地保存的鉴权信息是否一致， 其中， 在判断结果为一致的情况下， 确定所 述第二鉴权信息为合法。 优选地， 根据预定策略与服务端同步所述本地保存的鉴权信息， 其中， 所述本地 保存的鉴权信息是用户在所述用户设备上登录过的鉴权信息。 优选地，所述第一鉴权信息是根据用户输入的鉴权信息进行鉴权后确定的，或者， 所述第一鉴权信息是所述用户设备在系统启动后自动加载的。 根据本发明实施例的另一个方面， 还提供了一种用户接口界面加载装置， 包括： 确定模块， 设置为根据用户设备当前合法的第一鉴权信息， 确定所述第一鉴权信息对 应的可用功能和应用程序； 加载模块， 设置为加载第一用户接口界面， 其中， 所述第 一用户接口界面用于提供执行所述第一鉴权信息对应的可用功能和应用程序的接口。 优选地， 所述装置还包括： 接收模块， 设置为接收用户输入的第二鉴权信息； 判 断模块， 设置为判断所述第二鉴权信息是否合法； 第二确定模块， 设置为在判断结果 为合法的情况下，确定所述第二鉴权信息对应的可用功能和应用程序；第二加载模块， 设置为加载第二用户接口界面， 其中， 所述第二用户接口界面用于提供执行所述第二 鉴权信息对应的可用功能和应用程序的接口。 优选地， 所述判断模块包括： 发送单元， 设置为发送所述第二鉴权信息至服务端， 其中， 所述服务端设置为对所述第二鉴权信息的合法性进行判断， 并返回判断结果； 接收单元， 设置为接收所述服务端返回的所述判断结果； 判断单元， 设置为根据所述 判断结果， 判断所述第二鉴权信息是否合法。 根据本发明实施例的另一个方面， 还提供了一种瘦终端， 包括上述的用户接口界 面加载装置。 通过本发明实施例， 采用根据用户设备当前合法的第一鉴权信息， 确定第一鉴权 信息对应的可用功能和应用程序； 加载第一用户接口界面， 其中， 该第一用户接口界 面用于提供执行第一鉴权信息对应的可用功能和应用程序的接口的方式， 解决了多用 户登录功能采用各个用户的应用软件和数据相互隔离导致的存储资源的浪费的问题， 避免了存储资源的浪费， 有效地实现了对存储资源的合理利用。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据本发明实施例的用户接口界面加载方法的流程示意图； 图 2是根据本发明实施例的用户接口界面加载装置的结构示意图； 图 3是根据本发明实施例的用户接口界面加载装置的优选结构示意图一； 图 4是根据本发明实施例的用户接口界面加载装置的优选结构示意图二； 图 5是根据本发明实施例的用户接口界面加载装置的优选结构示意图三； 图 6是根据本发明优选实施例的用户权限初始化的流程示意图； 图 7是根据本发明优选实施例的普通用户权限切换的流程示意图； 图 8是根据本发明优选实施例的管理员用户权限切换的流程示意图。 具体实施方式 需要说明的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相 互组合。 下面将参考附图并结合实施例来详细说明本发明。 在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执 行， 并且， 虽然在流程图中示出了逻辑顺序， 但是在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤。 本实施例提供了一种用户接口界面加载方法， 图 1是根据本发明实施例的用户接 口界面加载方法的流程示意图， 如图 1所示， 该流程包括如下步骤： 步骤 S102, 根据用户设备当前合法的第一鉴权信息， 确定第一鉴权信息对应的可 用功能和应用程序； 步骤 S104， 加载第一用户接口界面， 其中， 该第一用户接口界面用于提供执行第 一鉴权信息对应的可用功能和应用程序的接口。 通过上述步骤， 根据移动终端当前合法的第一鉴权信息确定对应的可用功能和应 用程序， 并加载用于提供这些可用功能和应用程序的接口的第一用户接口界面。 相比 于相关技术中的多用户登录功能采用各个用户的应用软件和数据相互隔离的方式， 在 本实施例中采用用户接口界面向用户提供执行可用功能和应用程序的接口， 从而使得 应用软件和数据可以共享， 解决了多用户登录功能采用各个用户的应用软件和数据相 互隔离导致的存储资源的浪费， 避免了存储资源的浪费， 有效地实现了对存储资源的 合理利用。 优选地， 该第一用户接口界面是用户设备的唯一的用户接口界面， 或者被设置为 多个用户界面中强制默认显示的用户接口界面。 在鉴权信息对应的权限没有相应的操 作权限的情况下，该用户接口界面被设置为用户无法退出或切换到其他用户接口界面。 优选地， 用户可以在根据第一鉴权信息加载了第一用户接口界面之后， 更换已登 录的 （即当前合法的） 鉴权信息用户设备接收用户输入的第二鉴权信息之后， 判断第 二鉴权信息是否合法， 并在判断结果为合法的情况下， 确定第二鉴权信息对应的可用 功能和应用程序， 以及加载第二用户接口界面， 该第二用户接口界面用于提供执行第 二鉴权信息对应的可用功能和应用程序的接口。 通过该方式， 实现了用户的更换。 在 更换用户之后， 用户通过新的用户接口界面对新的应用程序和可用功能进行操作。 在判断鉴权信息的合法性的情况下， 可以采用云端验证、 本地验证或者云端验证 与本地验证相结合的方式。 优选地，在采用云端验证的情况下，用户设备可以发送第二鉴权信息至服务端（即 云端）； 服务端对接收到的第二鉴权信息的合法性进行判断， 并返回判断结果； 用户设 备接收到服务端返回的判断结果后， 根据该判断结果， 判断第二鉴权信息是否合法。 通过该方式， 可以实现云端对用户鉴权信息的统一管理， 并且使用同一个云端的多个 用户设备之间可以共享鉴权信息， 从而实现在多个用户设备之间的数据共享。 优选地， 在判断结果中可以携带有与第二鉴权信息对应的应用程序信息和可用功 能信息， 需要说明的是： 与第二鉴权信息对应的应用程序信息和可用功能信息也可以 是保存在用户设备的本地， 并通过预定策略与服务端进行同步的。 优选地， 在采用本地验证的情况下， 例如在云端与用户设备没有建立连接的情况 下采用本地验证， 用户设备可以判断第二鉴权信息与用户设备本地保存的鉴权信息是 否一致， 并在判断结果为一致的情况下， 确定第二鉴权信息为合法。 采用该方式， 用 户设备可以在离线状态下实现临时鉴权， 该鉴权的权限下用户可以使用用户设备本地 保存的应用程序和可用功能。 优选的， 在用户需要执行云端的应用程序和可用功能的 情况下， 用户设备可以提供一个接口设置为建立用户设备与云端的连接， 并通过云端 验证的方式进行鉴权， 在鉴权后， 用户可以通过用户设备执行云端的应用程序或可用 功能。 优选地， 本地保存的鉴权信息根据预定策略与服务端保持同步。 例如： 在用户设 备与服务端建立了连接的情况下， 可以通过定期或者不定期的方式同步用户设备中本 地保存的鉴权信息和服务端中的鉴权信息。优选地， 该鉴权信息采用加密存储， 并且， 还可以随鉴权信息同时保存对应的应用程序信息和可用功能的信息。 优选的， 本地保 存的鉴权信息是用户在该用户设备上登录过的鉴权信息。 优选地，第一鉴权信息可以是根据用户输入的鉴权信息进行鉴权后确定的，或者， 第一鉴权信息也可以是用户设备在系统启动后自动加载的， 例如， 第一鉴权信息可以 是系统默认的鉴权信息， 对应于基本的应用程序和基本的可用功能， 其中， 在使用该 默认的鉴权信息时， 用户对移动终端的操作权限为最低。 优选地， 鉴权信息与应用程序和可用功能之间的对应关系可以是根据用户的配置 进行设置的。 一般而言， 操作权限越低， 可执行的应用程序和可用功能越少； 例如， 在鉴权信息具有管理员权限时可以执行几乎所有的应用程序和可用功能， 而为了保障 系统的安全， 对于非管理员权限的鉴权信息， 应该屏蔽系统设置、 进程管理、 文档管 理等功能和应用程序的操作接口。 本实施例还提供了一种用户接口界面加载装置， 该装置用于实现上述用户接口界 面加载方法， 该装置的功能实现已经在上述方法实施例中进行了说明，在此不再赘述。 图 2是根据本发明实施例的用户接口界面加载装置的结构示意图， 如图 2所示， 该装置包括： 确定模块 22和加载模块 24， 其中， 确定模块 22， 设置为根据用户设备 当前合法的第一鉴权信息， 确定第一鉴权信息对应的可用功能和应用程序； 加载模块 24耦合至确定模块 22， 设置为加载第一用户接口界面， 其中， 第一用户接口界面用于 提供执行第一鉴权信息对应的可用功能和应用程序的接口。 本发明的实施例中所涉及到的模块、 单元可以通过软件的方式实现， 也可以通过 硬件的方式来实现。本实施例中的所描述的模块、单元也可以设置在处理器中， 例如， 可以描述为： 一种处理器包括确定模块 22、 加载模块 24。 其中， 这些模块的名称在某 种情况下并不构成对该模块本身的限定， 例如， 确定模块 22还可以被描述为 "设置为 根据用户设备当前合法的第一鉴权信息确定第一鉴权信息对应的可用功能和应用程序 的模块"。 图 3是根据本发明实施例的用户接口界面加载装置的优选结构示意图一， 如图 3 所示， 优选地， 该装置还包括： 接收模块 32， 设置为接收用户输入的第二鉴权信息； 判断模块 34耦合至接收模块 32， 设置为判断第二鉴权信息是否合法； 第二确定模块 36耦合至判断模块 34， 设置为在判断结果为合法的情况下，确定第二鉴权信息对应的 可用功能和应用程序； 第二加载模块 38耦合至第二确定模块 36， 设置为加载第二用 户接口界面， 其中， 第二用户接口界面用于提供执行第二鉴权信息对应的可用功能和 应用程序的接口。 优选的，确定模块 22和第二确定模块 36可以为同一个模块，加载模块 24和第二 加载模块 38可以为同一个模块。 图 4是根据本发明实施例的用户接口界面加载装置的优选结构示意图二， 如图 4 所示， 优选地， 判断模块 34包括： 发送单元 342， 设置为发送第二鉴权信息至服务端， 其中， 服务端设置为对第二鉴权信息的合法性进行判断， 并返回判断结果； 接收单元 344通过服务端与发送单元 342耦合， 设置为接收服务端返回的判断结果； 第一判断 单元 346耦合至接收单元 344， 设置为根据判断结果， 判断第二鉴权信息是否合法。 图 5是根据本发明实施例的用户接口界面加载装置的优选结构示意图三， 如图 5 所示， 优选地， 判断模块 34包括： 第二判断单元 348， 设置为判断第二鉴权信息与用 户设备的本地保存的鉴权信息是否一致， 其中， 在判断结果为一致的情况下， 确定第 二鉴权信息为合法。 优选地， 该装置还包括： 同步模块， 设置为根据预定策略与服务端同步本地保存 的鉴权信息， 其中， 本地保存的鉴权信息是用户在用户设备上登录过的鉴权信息。 优选地， 第一鉴权信息是根据用户输入的鉴权信息进行鉴权后确定的， 或者， 第 一鉴权信息是用户设备在系统启动后自动加载的。 本实施例还提供了一种瘦终端， 包括上述的用户接口界面加载装置。 下面结合优选实施例， 以瘦终端为例进行描述和说明。 本优选实施例提供了一种实现 Android瘦终端多用户权限切换的方法， 涉及基于 云计算环境下的 Android瘦终端权限控制的多用户切换方法。 本优选实施例提供的一种云计算环境下 Android瘦终端中多用户切换方法包括： 步骤一、 瘦终端默认以初始化账号启动， 例如： ①瘦终端开机启动时， 以预设的特定初始化账号登陆。 该账号具有最低的操作权 限， 只能操作最常用的部分应用程序。 BACKGROUND 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. To maximize the application of IT assets, 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. In the cloud computing environment, 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. For example, in the early devices using Android, 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. Currently, this feature is only available for tablets with Android, where each user's application software and data are isolated from each other. That is, each user has an independent account, application, system settings, and data files, and cannot switch to other users' applications after switching users. The inventor found that in a tablet with sufficient storage space, when the application software and data of each user are isolated from each other, the user may not feel obvious inconvenience during use; however, the storage space is limited. Devices (such as mobile phones), or thin-end devices in enterprise-level applications, as the number of users increases and the number of users increases, it will inevitably lead to waste and inconvenience of storage resources, and on the other hand, the cost of storing data by devices. rise. For the multi-user login function in the related art, the problem of waste of storage resources caused by the isolation of application software and data of each user is adopted, and an effective solution has not been proposed yet. SUMMARY OF THE INVENTION Embodiments of the present invention provide a user interface interface loading method, apparatus, and thin terminal to solve at least the above problems. According to an aspect of the embodiments of the present invention, a user interface interface loading method is provided, 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. Preferably, after loading the user interface, 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 . Preferably, 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. Preferably, 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. Preferably, 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. Preferably, 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. According to another aspect of the present invention, a user interface interface loading apparatus is further provided, 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. Preferably, 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. Preferably, 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. According to another aspect of an embodiment of the present invention, a thin terminal is provided, including the user interface interface loading device described above. 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 legalized by the user equipment, and the first user interface is loaded, where the first user interface is used. The method of performing the function of the first authentication information and the interface of the application is provided, which 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 waste of storage resources. , effectively realize the rational use of storage resources. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic flowchart of a user interface interface loading method according to an embodiment of the present invention; 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. The steps illustrated in the flowchart of the figures may be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, may differ from this The steps shown are performed in the order shown or described. This embodiment provides a user interface interface loading method. 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. 1 , the process includes the following steps: 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. Compared with the multi-user login function in the related art, the application software and the data of each user are isolated from each other. In this embodiment, 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. Preferably, 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. Preferably, after the first user interface is loaded according to the first authentication information, 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. After the user is replaced, the user operates the new application and available functions through the new user interface interface. In the case of judging the legitimacy of the authentication information, cloud authentication, local authentication, or a combination of cloud authentication and local authentication may be adopted. Preferably, in the case of adopting cloud authentication, 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. In this way, unified management of user authentication information in the cloud can be implemented, and authentication information can be shared among multiple user devices in the same cloud, thereby implementing data sharing among multiple user devices. Preferably, 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. Preferably, in the case of using local authentication, for example, if the cloud does not establish a connection with the user equipment, 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. Preferably, in the case that the user needs to execute the application and the available functions of the cloud, 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. Preferably, the locally saved authentication information is synchronized with the server according to a predetermined policy. For example, when the user equipment establishes a connection with the server, the authentication information stored locally in the user equipment and the authentication information in the server may be synchronized periodically or irregularly. Preferably, 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. Preferably, the locally saved authentication information is authentication information that the user has logged in on the user equipment. Preferably, 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. Preferably, 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. The function implementation of the device has been described in the foregoing method embodiments, and details are not described herein. 2 is a schematic structural diagram of a user interface interface loading apparatus according to an embodiment of the present invention. As shown in FIG. 2, 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. The described modules and units in this embodiment may also be disposed in a processor. For example, it may be described as follows: 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. For example, 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. 3, 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. FIG. 4 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. 4, 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. 5, 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. Preferably, 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. Preferably, 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 following describes the description and description of the thin terminal as an example in conjunction with the preferred embodiment. 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.
②系统开机启动后， 不进入 android桌面， 而进入多用户权限管理程序， 并初始化 应用快捷方式列表。 该管理程序要求全屏显示； 提供权限相对应的应用快捷方式的列 表， 用户可通过点击快捷方式运行相关的程序； 提供账号切换功能， 允许通过用户切 换获取不同的应用操作权限。 普通权限用户无法退出权限管理程序， 也不能将其手动 切换到后台而操作 android原始桌面。管理员用户则可根据需要选择是否退出权限管理 程序， 返回到 android原始桌面。 步骤二、 初始化或普通权限用户向其他权限账号切换， 例如： 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:
①初始化或普通权限用户进入账号切换模块， 输入相关的账号和密码后， 向云服 务端发起认证请求。 云服务端对该账号和密码进行鉴权认证， 并将结果返回给瘦终端 权限管理程序。 ②如认证成功， 则判断当前用户权限。 如切换到普通用户， 则权限管理程序刷新 程序快捷方式列表， 提供相关的应用操作入口。 如切换到管理员用户， 则权限管理程 序列出所有应用快捷方式，并开启可退出功能后， 自动退出当前程序进入 android原始 桌面。进入 android原始桌面后，管理员用户可以运行当前 android系统中的任何应用。 ③如认证失败， 云终端仅给予相关提示， 而不进行其他操作。 步骤三、 管理员用户向其他权限账号切换， 例如： 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. 2 If the authentication is successful, 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. 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:
①管理员用户运行 android桌面中的多用户权限管理程序，进入账号切换模块，输 入相关的账号和密码， 并向云服务端发起认证请求。 1 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.
②如认证成功， 且则判断当前用户权限。 如切换到另一管理员用户， 则更新应用 快捷方式列表， 并自动退出当前权限管理应用。 如切换到普通用户， 则根据权限更新 应用快捷方式列表， 并关闭退出功能。 2 If the authentication is successful, and then determine the current user rights. If you switch to another administrator user, the application shortcut list is updated and the current rights management application is automatically logged out. If you switch to a normal user, the application shortcut list is updated according to the permission, and the exit function is turned off.
③如认证失败， 云终端仅给予相关提示， 而不进行其他操作。 下面结合附图对本优选实施例的上述三个步骤进行说明。 图 6是根据本发明优选实施例的用户权限初始化的流程示意图， 如图 6所示， 该 流程包括： 步骤 S602, 开机启动， 默认以初始化账号登陆。 步骤 S604, 系统启动成功后， 多用户权限管理程序自动运行。 普通用户无法退出 该程序， 也无法将该程序切换到系统后台运行。 步骤 S606, 多用户权限管理程序根据用户权限， 提供相应的应用程序快捷方式列 表。 图 7是根据本发明优选实施例的普通用户权限切换的流程示意图， 如图 7所示， 该流程包括： 步骤 S72， 普遍用户进入多用户权限切换模块， 输入账号信息， 向云服务端发起 认证请求。 步骤 S74， 认证成功。 如切换到另一普通用户， 则刷新应用列表， 提供权限相应 的应用程序快捷方式。 如切换到管理员， 同样更新相应的应用列表， 且开启多用户权 限管理程序可退出功能后， 退出该程序。 步骤 S76， 认证失败， 则显示相关提示。 图 8是根据本发明优选实施例的管理员用户权限切换的流程示意图，如图 8所示， 该流程包括如下步骤： 步骤 S82， 管理员用户进入多用户权限切换模块， 输入账号信息， 向云服务端发 起认证请求。 步骤 S84， 认证成功。 如切换到另一管理员用户， 则更新应用列表， 退出多用户 权限管理程序。 如切换到普通用户， 则更新应用列表,同时关闭可退出功能。 步骤 S86， 认证失败， 则显示相关提示。 综上所述， 通过本优选实施例， 采用自定义的多用户管理程序和云服务端鉴权认 证的方法， 使得 Android瘦终端可以为不同权限的用户提供不同的应用， 并使得多个 用户间可以相互切换。 本方法默认使用初始化用户权限， 有效保证基本应用操作需求 的同时， 又可以通过多用户切换， 实现不同权限下的应用访问控制。 采用本方法的瘦 终端能够满足当前云计算环境下多用户权限切换和应用共享的需求。 工业实用性 通过本发明实施例， 采用根据用户设备当前合法的第一鉴权信息， 确定第一鉴权 信息对应的可用功能和应用程序； 加载第一用户接口界面， 其中， 该第一用户接口界 面用于提供执行第一鉴权信息对应的可用功能和应用程序的接口的方式， 解决了多用 户登录功能采用各个用户的应用软件和数据相互隔离导致的存储资源的浪费的问题， 避免了存储资源的浪费， 有效地实现了对存储资源的合理利用。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 或者将它们分别制作成各个集成电路模 块， 或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明 不限制于任何特定的硬件和软件结合。 以上上述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。 3 If the authentication fails, the cloud terminal only gives relevant prompts and does not perform other operations. The above three steps of the preferred embodiment will be described below with reference to the accompanying drawings. 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. As shown in FIG. 7, the process includes: Step S72: A universal user enters a multi-user right switching module, inputs account information, and initiates authentication to a cloud server. request. In 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. In 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. 8, the process includes the following steps: 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. In 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. In step S86, if the authentication fails, a related prompt is displayed. In summary, with the preferred embodiment, 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. By default, 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. The waste of resources effectively realizes the rational use of storage resources. Obviously, those skilled in the art should understand that the above 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. Thus, 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.
Claims
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310659645.1A CN104700039A (en) | 2013-12-06 | 2013-12-06 | User interface loading method and device as well as thin terminal |
| CN201310659645.1 | 2013-12-06 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015081678A1 true WO2015081678A1 (en) | 2015-06-11 |
Family
ID=53272816
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2014/079522 Ceased WO2015081678A1 (en) | 2013-12-06 | 2014-06-09 | User interface loading method and apparatus and thin terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104700039A (en) |
| WO (1) | WO2015081678A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107797721B (en) * | 2016-09-07 | 2020-10-09 | 腾讯科技（深圳）有限公司 | Interface information display method and device |
| CN108920202B (en) * | 2018-05-15 | 2020-09-15 | Oppo广东移动通信有限公司 | Application preloading management method, device, storage medium and intelligent terminal |
| CN111309242A (en) * | 2020-02-12 | 2020-06-19 | 深圳市丰巢科技有限公司 | Intelligent cabinet screen display method and device, server and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101072129A (en) * | 2007-06-25 | 2007-11-14 | 北京邮电大学 | JMX based network service management method and its application system |
| CN101123756A (en) * | 2007-09-29 | 2008-02-13 | 北京邮电大学 | Multi-Service Generation System Supporting Application Programming Interface |
| CN101207864A (en) * | 2006-12-20 | 2008-06-25 | 中兴通讯股份有限公司 | A method for realizing multi-user management and information hiding in mobile phone |
| CN101815116A (en) * | 2009-02-20 | 2010-08-25 | 中兴通讯股份有限公司 | Mobile telephone method and device based on multi-user |
| CN103024022A (en) * | 2012-12-06 | 2013-04-03 | 中国电信股份有限公司云计算分公司 | Controlling and management system and method of virtual machine application service |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100223579A1 (en) * | 2009-03-02 | 2010-09-02 | Schwartz Gerry M | Iphone application disguiser |
-
2013
- 2013-12-06 CN CN201310659645.1A patent/CN104700039A/en active Pending
-
2014
- 2014-06-09 WO PCT/CN2014/079522 patent/WO2015081678A1/en not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101207864A (en) * | 2006-12-20 | 2008-06-25 | 中兴通讯股份有限公司 | A method for realizing multi-user management and information hiding in mobile phone |
| CN101072129A (en) * | 2007-06-25 | 2007-11-14 | 北京邮电大学 | JMX based network service management method and its application system |
| CN101123756A (en) * | 2007-09-29 | 2008-02-13 | 北京邮电大学 | Multi-Service Generation System Supporting Application Programming Interface |
| CN101815116A (en) * | 2009-02-20 | 2010-08-25 | 中兴通讯股份有限公司 | Mobile telephone method and device based on multi-user |
| CN103024022A (en) * | 2012-12-06 | 2013-04-03 | 中国电信股份有限公司云计算分公司 | Controlling and management system and method of virtual machine application service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104700039A (en) | 2015-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3465430B1 (en) | Virtual browser integration | |
| KR102048111B1 (en) | Secure firmware updates | |
| EP3049985B1 (en) | A separate, disposable execution environment for accessing unverified content | |
| JP5881835B2 (en) | Web-based interface to access basic input / output system (BIOS) functionality | |
| EP3179697B1 (en) | Validating the identity of a mobile application for mobile application management | |
| US9319380B2 (en) | Below-OS security solution for distributed network endpoints | |
| US9495560B2 (en) | Polymorphic virtual appliance rule set | |
| EP2973147B1 (en) | Policy-based secure web boot | |
| RU2456662C2 (en) | Matching startup between several devices capable of startup | |
| US9215225B2 (en) | Mobile device locking with context | |
| CN102495750A (en) | Virtual desktop configuration and operation techniques | |
| US12015687B2 (en) | Securing communications in a network function virtualization (NFV) core network | |
| WO2015188442A1 (en) | Password management method and device | |
| US9135436B2 (en) | Execution stack securing process | |
| WO2015081678A1 (en) | User interface loading method and apparatus and thin terminal | |
| 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 (en) | Virtualization apparatus and server for securly executing applications and method therefor | |
| US20150135304A1 (en) | Electronic apparatus and control method thereof | |
| CN110365756B (en) | Access method, electronic device and computer storage medium | |
| Bricker | Unified extensible firmware interface (UEFI) and secure boot: Promise and pitfalls | |
| WO2015196526A1 (en) | Operating system start method, device, and terminal | |
| JP2013074329A (en) | Portable electronic apparatus and control method |
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 |