Patent Description:
With recent advances in information and communication technologies, many kinds of portable electronic devices such as smart phones and tablet PCs have proliferated. Various applications for SNS, games, photography, etc. have been implemented in a typical device.

Generally, devices such as smart phones and the like have employed a screen lock function. The term "screen lock" refers to a locked screen condition in which only predetermined information is displayed without the performance of most functions. A screen lock occurs after the passage of predetermined time following no detected user input to the device when no applications are running that normally prevent the screen lock from occurring (such as a broadcast reception application). The screen lock function restricts telephony and prevents the exposure of a user's personal information including pictures, a list of text message transmissions, and the like.

Conventionally, if a password protection is set up for the device, a method for releasing the screen lock requires the input of a predetermined password such as a pattern of numbers or touch patterns. That is, when the correct password is input, a device releases the screen lock and enables a user to use various applications which are executable in the device.

A problem arises, however, in a situation where the device is shared by multiple users. That is, when all users have authority to use all applications available in the device, personal information of each user is exposed to other users. Further, when parents and children use the device together, there is a problem in that inappropriate information might be inadvertently viewable by young children.

<CIT>, is about a multiple-access-level lock screen system that allows different levels functionality to be accessed on a computing device. For example, when a device is in a locked state, a user can select (e.g., by making one or more gestures on a touchscreen) a full-access lock screen pane and provide input that causes the device to be fully unlocked, or a user can select a partial-access lock screen pane and provide input that causes only certain resources (e.g., particular applications, attached devices, documents, etc.) to be accessible. Lock screen panes also can be selected (e.g., automatically) in response to events. For example, when a device is in a locked state, a messaging access lock screen pane can be selected automatically in response to an incoming message, and a user can provide input at the messaging access lock screen pane that causes only a messaging application to be accessible.

<CIT>, is about a method, apparatus, and system for accessing at least a portion of a device based upon an access input. An access input is received. The access input includes information for gaining access to one or more functions of the device. A user access mode of the device is changed from a first access mode to a second access mode based upon at least in part on the access input. An application is selected in the device in response to changing from the first access mode to the second access mode. At least a portion of the output of the selected application is provided.

Disclosed herein is a method for configuring authority in an electronic device to use at least one application differently for a plurality of users.

In one aspect, a method of configuring a password in an electronic device is provided. User inputs are received to set passwords for respective user levels, where each user level is associated with a different authority to access applications. The passwords are registered for the respective user levels. At least one application is associated with one of the user levels.

In another aspect, a method of releasing a lock in an electronic device is provided. The method includes: receiving an input password for releasing the lock; comparing the input password with configured passwords for a plurality of user levels associated with different authority for at least one application; and releasing the lock in consideration of a user level for the input password when the input password matches any one of the configured passwords.

Apparatus for implementing the methods are also described.

Implementations may have the advantage of preventing certain users from accessing inappropriate information and contents.

The above and other aspects, features, and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, a detailed description of known functions and configurations incorporated herein will be omitted to avoid obscuring the subject matter of the present invention.

As described above, a method for releasing a lock according to the conventional art has a disadvantage in that private information on a certain person may be exposed to others, or inappropriate contents may be obtainable by a certain person when plural users use a device.

The present invention addresses these problems by providing a scheme in which a plurality of user levels are configured in order to permit each user to access applications depending on his/her level, thereby preventing private information and inappropriate contents from being exposed to others.

An electronic device ("device") in embodiments described herein can be a portable information or communication device such as a smart phone, a tablet PC, a cell phone, an e-book, a camera, a game player, a music player, an Internet device or any other processing device with a display. The electronic device can also be a fixed device, such as a display device integrated with a home appliance.

<FIG> are flowcharts illustrating respective methods 100a, 100b of setting a password, and releasing a lock, according to embodiments of the present invention.

Referring to <FIG>, in step 101a, a device enables a user to select applications which are available in each one of multiple user levels that are predefined. Each user level is designated with a different authority to use at least one application that operates differently as a function of the operational user level. For instance, a music player application may automatically avoid playing songs that are rated for a mature listener when a current user is recognized as a low level user (e.g., a child level). Accordingly, one or more applications may be available in each user level, and may be selected for execution at various user levels.

Next, in step 103a, upon receiving different user inputs for setting passwords at each user level, the device proceeds to step 105b. In one embodiment, each password may be settable in a form of numerals or a pattern or combination of thereof.

In step 105a, the device registers the input password for each user level and the selected application for a corresponding user level. Such registered information is used when an operation of releasing a lock is executed later.

<FIG> is a flowchart illustrating a method, 100b, of releasing a lock according to embodiments of the present invention. In step 101b, when the device is in a locked state and a user inputs a password to release the lock, then at step 103b, the device determines whether the input password matches any of the registered passwords corresponding to one of the user levels. If the password matches, then in step 105b, the device carries out releasing the lock in consideration of the user level corresponding to the password. That is, the device releases the lock so that the user is enabled to use only the applications which are registered in the corresponding user level. In an implementation, releasing the lock can also enable a user to use all applications registered in the corresponding user level and in one or more user levels lower than the corresponding user level. In other words, the device releases the lock so that the user in a higher user level is enabled to have authority to use the applications registered in the lower user level.

Accordingly, when passwords for different user levels of a common device are registered as just described, users assigned different levels have different authority from one another in order to access applications. Therefore, there is an advantage in that inappropriate information can be blocked from being provided to a certain user.

<FIG> is a flowchart illustrating a more specific method, <NUM>, of setting a password according to an embodiment of the present invention. In step <NUM>, the device determines whether a user makes a request for setting a plurality of user levels. This refers to a request for setting passwords respectively corresponding to each user level, where available applications depend on each user level. The request may be selectively achieved through predesignated menus.

When the request is received, in step <NUM>, the device receives a user input designating the number of user levels. Here, the device can provide the user with a guide screen so that the user inputs the number of the user levels. An example of the guide screen is shown in <FIG>.

It is noted that step <NUM> may be omitted according to a setting manner. For example, a device designer, a software developer, etc. can pre-set the number of the user levels as a default. In this case, the device may not prompt the user to input a number of user levels.

In step <NUM>, the device provides the user with a guide screen so that the user sets detail specifications relating to each user level. That is, the device provides the user with the guide screen in order that the user selects available applications in each user level and sets a password relating to the corresponding user level. Examples of these screens will be described with reference to <FIG>.

In the screen examples <FIG>, the example of setting three user levels is illustrated. However, the number of the user levels can be variable according to the selection or setting of the user.

As shown in <FIG>, the device can provide the user with menus 302a, 302b and 302c which are used for selecting available applications in each user level, and menus 304a, 304b and 304c which are used for inputting a password corresponding to each user level.

Where the user selects a menu 302a in order to select available applications in a user level <NUM>, the device can guide categories of applications to the user as shown in <FIG>. When the user selects one or more categories, the device registers the applications, which belong to the selected categories, as the available applications in the user level <NUM>. For example, when the user selects a category of "web browser" as a category of the available application in the user level <NUM>, the device analyzes the category of the applications stored therein and registers the applications included in "web browser" as the application to be available in the user level <NUM>.

Categories of the respective applications can be identified in various ways. For example, the device may analyze meta data of each application, thereby identifying a category of the corresponding application. As shown in <FIG>, on the other hand, the device may identify the category of the corresponding application by analyzing a download page thereof or a page linked to the download page. Thus the device parses the meta data, the download page, or the like and analyzes words inserted in a certain tag, so as to identify the category of the corresponding application. For example, the device parses the meta data of each application or the download page and identifies a property value of a certain tag, so as to identify the category of the corresponding application. In a case that a category <NUM> in the property value of the certain tag indicates a game <NUM>, the device determines that the category of the corresponding application is a "game". For instance, the device can request an application provider to transmit information on the category of the corresponding application to the device while transmitting a title of the application to the application provider. Then, the device may analyze information received from the application provider, and identify the category of each application.

On the other hand, when the user selects a menu 304a (see <FIG>) in order to set a password for the user level <NUM>, the device provides the user with a screen as shown in <FIG> on which the user inputs the password. <FIG> shows an example of inputting the password in a pattern manner, where the user drags a touch input between different grid points. When the user inputs a pattern, which is formed by crossing two grid points 306a and 306b of plural grid points, as a password, for example, the device registers the input password as a password with respect to the user level <NUM>. Alternatively, the device can be designed to receive a password input via numeric keys of the device.

The processes described above with reference to <FIG> can be executed identically when details relating to other user levels are set.

Returning to <FIG>, in step <NUM>, the device determines whether the user requests the device to store the details of the user levels and passwords input in the prior steps. If so, then in step <NUM>, the device identifies whether inappropriate details are included in the details input by the user. Examples of inappropriate details are conditions where: <NUM>) the user does not set a password for a certain user level; <NUM>) the user does not select an application for a certain user level; <NUM>) a password for a higher user level is lower in complexity (or security) than a lower user level; <NUM>) passwords of different user levels are identical to one another, or <NUM>) selected applications relating to different user levels are identical to one another. Other conditions may also be predefined.

Regarding the third condition above, i.e., the complexity criteria, this can be predefined, for example, on the basis of the number of grid points in a case of inputting a password in a pattern manner. For instance, a pattern crossing three grid points has a higher complexity than a pattern crossing two grid points. Further, in a case of inputting numerals as a password, the complexity criteria may be based on the number of numerals / characters to be input. For example, a password including three numerals has a higher complexity than a password including two numerals.

As a result of the determination of step <NUM>, when it is determined that inappropriate details exist, the device proceeds to step <NUM> and provides a guide screen in order for the user to reset details relating to the corresponding user level.

For example, as shown in <FIG>, it is assumed that a password relating to a user level <NUM> is input in a form of a pattern crossing five grid points, and a password relating to a user level <NUM> is input in a form of a pattern crossing four grid points as shown in <FIG>. In this case, since the complexity of the password for a high-rank user level (user level <NUM>) is lower than that of a low-rank user level (user level <NUM>) as described above, the device determines that inappropriate details exist (and may display text information explaining why) and requests the user to input a password of any user level again. <FIG> shows an example of a case that the device enables the user to input a password again by requesting the user to input the password for the user level <NUM> again.

If at step <NUM>, the device determines that the inappropriate details do not exist, the process moves to step <NUM> so as to store the details input by the user.

As mentioned above, the selection of one or more applications for each user level by selecting predetermined categories has been described as an example. As shown in <FIG>, however, certain applications may be adapted to two or more user levels. In this case, each user level may be selected from an application list stored in the device.

Further, the method of inputting the password using a pattern has been described above. However, a password may be input by using numerals instead of patterns.

As mentioned above, a method of setting the details for each user level according to an embodiment of the present invention has been described with reference to <FIG> and <FIG>. Subsequent entry of a correct password for a corresponding user level is of course necessary for releasing a lock for that level, as described in connection with <FIG>. Releasing a lock in consideration of a user level for a corresponding password means that the lock may be released in order for a user to use only applications registered in a corresponding user level. For example, as shown in <FIG>, it is assumed that a category of "web browser" for a user level <NUM> is registered as a category of an available application and a category of "telephony" for a user level <NUM> is registered as a category of an available application. When a password for the user level <NUM> is input, a device can display an icon <NUM> as shown in <FIG> of the application corresponding to the category of "telephony" which is registered in the user level <NUM>. In one implementation, icons for applications for lower rank user levels are also displayed and made available. For instance, as in <FIG>, a category of "web browser" and a category of "telephony" are registered for user levels <NUM> and <NUM>, respectively. When a password for the user level <NUM> is input, then as shown in <FIG>, a device can display both an icon <NUM> of the application corresponding to the category of "web browser" registered in the user level <NUM> and an icon <NUM> of the application corresponding to the category of "telephony" registered in the user level <NUM>.

According to another embodiment of the present invention, releasing a lock in consideration of a user level for a corresponding password means that a device displays all icons of applications stored therein but only enables a user to use applications registered in the user level for a corresponding password, or applications in that user level and lower rank user levels. For example, when the input password identifies a level <NUM> user, the device displays all icons of the applications stored therein as shown in <FIG>, but does not enable the user to execute an application <NUM> registered for a user level <NUM>.

According to still another implementation, releasing the lock after password entry is implemented by displaying all icons of the applications stored in the device; however, icons of the applications registered in the user level for the corresponding password are displayed in a different state from that of icons of the remaining applications. For instance, applications that are unavailable due to the current user level being too low are displayed in a distinguishing manner. Examples of this approach are illustrated in <FIG>, in which a different opacity is used for the icons of the unavailable applications ("apps"); and in <FIG>, where icons of unavailable apps are replaced with predetermined images <NUM> and in <FIG>, where predetermined images <NUM> are superposed with the icons of the unavailable apps.

Further, in a case of only one application being registered in a user level for a corresponding password, after the correct password is entered, the application may be executed immediately. For example, when only one application, which belongs to a category of "web browser", is registered in a user level <NUM> and a password input by a user in order to release a lock is matched with the user level <NUM>, a device can execute the corresponding application immediately, as shown in <FIG>.

Methods of releasing the lock according to embodiments of the present invention have been described with reference to <FIG>. User levels for each application can be subsequently changed. For example, as described above with reference to <FIG>, upon selecting a category of applications and an application adapted to each user level, a user can designate separately and set the respective applications to belong to respective user levels different from one another, even though the applications are included in the identical category. Hereinafter, processes of changing the user levels for each application will be described with reference to <FIG>.

<FIG> is a flowchart illustrating an example process <NUM> of changing user levels for each application according to an embodiment of the present invention.

When receiving a user request in step <NUM> for a change of the user levels, i.e. a request to change user levels for each application, a device proceeds to step <NUM> and receives a password input by the user.

The device identifies whether the password input by the user is matched with a top-rank user level in step <NUM>. If not, user levels are not changeable and the device remains in a waiting mode for the correct top-rank password (indicated by flow line back to <NUM> query). If the input password is matched with the top-rank user level, the device proceeds to step <NUM> where the device enables the user, who belongs to the top-rank user level, to change the user level for each application.

The device provides a guide screen so that the user can change the user level for each application, in step <NUM>. For example, the device can display a list of the applications registered in each user level, as shown in <FIG>. Accordingly, the user may select any one of the applications and change the user level for the corresponding application, as shown in <FIG>. According to embodiments of the present invention, the device can display a level of each application in a form of an image <NUM> (see <FIG>), and the user can change the user level for each application by swiping the corresponding image <NUM> (e.g., lengthening the level indicator, as indicated by the arrowed line). Where the user level for any one of the applications is changed from a user level <NUM> to a user level <NUM> as shown in <FIG>, the device registers the corresponding application as an application to be available in the user level <NUM>.

Once the user is satisfied with the user level changes, the user can request that the changes be stored via suitable input command in step <NUM>, whereupon the device finally stores the changes in step <NUM>.

An embodiment in which only the user belonging to the top-rank user level changes the user level for each application, has been described with reference to <FIG>. In an alternative embodiment, users who do not belong to the top-rank user level are permitted to change the user level for each application.

The embodiment of changing the user level for each application has been described with reference to <FIG>. The technique of this embodiment can be identically applied to a case of changing the available applications for each user level, or a case of changing the password for each user level. That is, when the device receives a request from the user, the device can provide a guide screen so that a user changes details for each user level, for example passwords and available applications, through the guide screen, as shown in <FIG>.

Referring to <FIG>, the device provides a menu so that the user adds or deletes a user level through the menu. In an embodiment, when any user level is deleted, the device can register applications, which are included in the user level to be deleted, in the lowest rank user level among higher user levels than that of the deleted user level. For example, when a user level <NUM> is deleted, the applications included in a user level <NUM> can be registered in a user level <NUM> which is the lowest rank user level of a user level <NUM> and a user level <NUM> which are higher level than the user level <NUM>. According to this embodiment, in a state that the user levels <NUM> to <NUM> are set, when the user level <NUM> is deleted, the user level <NUM> may be changed into the user level <NUM>, and the user level <NUM> may be changed into the user level <NUM>.

Methods of changing various details related to the user level according to embodiments have been described with reference to <FIG> and <FIG>. After the user levels are set and a new application is to be downloaded, it is desirable to automatically set a user level for the new application. Hereinafter, processes of automatically setting user levels for a downloaded application will be described.

<FIG> is a flowchart illustrating an example process, <NUM>, of automatically setting user levels for a new downloaded application ("app") according to an embodiment of the present invention. In the embodiment to be described with reference to <FIG>, it is assumed that a selection of an app for each user level can be achieved by selecting a category of the app as described with reference to <FIG>.

A device identifies whether an app is downloaded in step <NUM>. If so, the device identifies a category of the downloaded app in step <NUM>. Here, the category of the downloaded app can be identified in different ways. For example, the device analyzes meta data of the downloaded app, so as to identify the app's category. In another approach, as shown in <FIG>, the device can analyze a page linked to a download page of the corresponding app so as to identify the app's category. That is, the device can parse the meta data, the download page, or the like and analyze words inserted in a certain tag, so as to identify the app's category. For example, the device can parse the meta data or the download page of the downloaded app and analyze a property value of the certain tag to identify the app's category. If the property value of the certain tag is category <NUM> and game <NUM>, the device determines that the app's category is "game". In another example, the device transmits information of the app, for example the app's title, to an application provider, while requesting the application provider to transmit category information for the corresponding app to the device. Then, the device may analyze information received from the application provider to identify the app's category.

Returning to <FIG>, the device registers the downloaded app as an available application in a user level which includes the identified category.

The methods of setting passwords for plural user levels respectively and of releasing a lock have been described with reference to <FIG>. Hereinafter, the configuration of a device to which the embodiments of the present invention are applied will be described with reference to <FIG>.

<FIG> is a block diagram illustrating an electronic device, <NUM>, to which embodiments of the present invention can be applied. Device <NUM> conveniently performs both functions of a device for setting a password and a device for releasing a lock. It should be noted, at least one of structural elements according to the embodiment shown in <FIG> may be omitted.

Device <NUM> includes a controller <NUM>, an input unit <NUM>, an output unit <NUM>, a memory <NUM> and a communication unit <NUM>.

Controller <NUM> controls the various operations described above in connection with <FIG>. Thus, at the time of setting a password, the controller <NUM> enables a user to select one or more applications to be used in each user level through the input unit <NUM> with relation to a plurality of user levels respectively having an authority to use one or more applications, and receives a password to be used for releasing a lock in each user level through the input unit <NUM>. At this time, the controller <NUM> enables a user to select at least one category among the plural categories set for an application. As a result, the user can select at least one application to be used in each user level. Further, the controller <NUM> enables the user to individually select at least one application to be used in each user level from a list of the applications stored in the memory <NUM>.

Controller <NUM> registers the input password for each user level and the selected application for the corresponding user level. In order to register the password and the application, the controller <NUM> can display a guide screen on the output unit <NUM> for the user to select and input the details for each user level, i.e. the password and the application.

Before the controller <NUM> enables the user to select at least one application to be used in each user level, on the other hand, it receives the number of the user levels through the input unit <NUM>. Accordingly, the controller <NUM> displays the guide screen on the output unit <NUM> in order for the user to select the number of the user levels.

In cases that the complexity of the input password for any one user level is lower than that of a password for a low-rank user level, the complexity of the input password for any one user level is higher than that of a password for a high-rank user level, or the complexity of the input password for any one user level is identical to that of a password for another user level, the controller <NUM> receives a password for the corresponding user level input by the user again. Accordingly, the controller <NUM> displays the guide screen on the output <NUM> in order for the user to input a password for the corresponding user level again.

When at least one application is downloaded, the controller <NUM> identifies a category of the downloaded application and registers the downloaded application as an application to be used in a user level to which the identified category belongs. At this time, the controller <NUM> analyzes at least one of meta data and the download page of the corresponding application and a page linked to the download page of the corresponding application and identifies the category of the downloaded application.

Upon receiving a request for user level change of at least one application, the controller <NUM> registers the corresponding application as an application to be used in the user level which is requested to be changed. Accordingly, the controller <NUM> displays a guide screen on the output unit <NUM> in order for the user to change a user level for each application.

Upon receiving a request for deletion of one user level, the controller <NUM> registers the application registered in the corresponding user level as an application to be used in the lowest-rank user level among high-rank user levels of the user level which is requested to be deleted. Accordingly, the controller <NUM> displays a guide screen on the output unit <NUM> in order for the user to delete or add a user level.

In releasing a lock, the controller <NUM> receives a password to release the lock through the input unit <NUM>, and compares the input password and the passwords stored in the memory <NUM>. Then, the controller <NUM> releases the lock in consideration of a user level for the corresponding password where the input password is identical to any one of the stored passwords.

In releasing the lock, the controller <NUM> can command the displaying of icons of applications to be used in the user level corresponding to the input password on the output unit <NUM>. Icons of applications to be unavailable in the corresponding user level can be displayed in a different state from the icons of the applications to be used in the corresponding user level. For example, the controller <NUM> commands the displaying of the icons of the applications to be unavailable in the corresponding user level in the different state from the icons of the applications to be used in the corresponding user level in any one manner of applying different opacities to the icons of the applications to be used in the corresponding user level and the icons of the applications to be unavailable in the corresponding user level, changing the icons of the unavailable applications to a predetermined image, and superposing predetermined image over the icons of the unavailable applications.

Further, the controller <NUM> may not display the icons of the applications to be unavailable in the corresponding user level.

On the other hand, where only one application is available in the user level corresponding to the password input by the user, the controller <NUM> may carry out an application immediately.

The input unit <NUM> transmits information input by the user to the controller <NUM>.

The output unit <NUM> displays various guide screens under the control of the controller <NUM>.

The input unit <NUM> and the output unit <NUM> preferably include a touch screen.

The memory <NUM> stores details for each user level.

The communication unit <NUM> communicates with external devices, preferably with the capability of using different communication mechanisms.

It will be appreciated that embodiments of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software. Where the embodiment of the present invention may be implemented in a software, the software can be executed by one or more processors using various operating systems or platforms. In addition, the software can be programmed by using any one of a variety of suitable programming languages, and also can be compiled into assembly codes or intermediate codes which can be carried out in a framework or a virtual machine.

Furthermore, embodiments of the present invention may be implemented by a processor-readable storage medium, for example a memory, a floppy disc, a hard disc, a compact disc, an optical disc or a magnetic tape, suitable for storing a program or programs including instructions for implementing the exemplary embodiments of the present invention.

Claim 1:
An electronic device (<NUM>) comprising:
a memory (<NUM>) storing a program including instructions;
a touchscreen (<NUM>, <NUM>); and
at least one processor (<NUM>),
wherein the instructions, when executed by the at least one processor (<NUM>), cause the electronic device (<NUM>) to:
store, via the memory, a password for allowing change of details including details of available applications related to a user level, the user level being associated with an authority to access applications;
receive a user request (<NUM>) for changing the details including details of available applications related to a user level;
in response to the received user request for changing the details including details of available applications related to a user level, control the touchscreen to display a password input screen;
receive a password input (<NUM>) through the password input screen;
compare the received password with the stored password;
if the received password does not correspond to the stored password, remain in a waiting mode for receiving a further password input;
if (<NUM>) the received password corresponds to the stored password, provide (<NUM>) on the touchscreen at least one guide screen for changing details including details of available applications related to the user level, the at least one guide screen comprising a list of the applications for each of which an access restriction option can be changed;
if the details including details of available applications related to the user level are changed, register (<NUM>) changed access configuration information in the memory; and
control the touchscreen to display icons of unavailable applications for the user level in a distinguishing manner from icons of applications authorized for access.