WO2019200350A1 - System for reward-based device control - Google Patents

Abstract

A system for reward-based computer device control, with a parent interface and a child interface: the parent interface establishing locking and unlocking scheduling for the computer device and providing a list of chores for unlocking functionality of the computer device, and the child interface allowing the viewing and completion of the chores.

Description

System for Reward-based Device Control

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority to U.S. Provisional Patent Application No. 62/657,608 filed on April 13, 2018, the contents of which are hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to a system for controlling access to network enabled devices based on an automatically tracked reward system.

BACKGROUND OF THE INVENTION

[0003] A common problem facing parents these days is controlling the access their children have to network (internet or private network) enabled devices, such as phone, laptops, tablet devices, desktop PCs, game consoles, home routers, smart TVs, and smart TV boxes. One particular concern is balancing the amount of time they use these devices compared to other activities - schoolwork, chores, physical activities, for example - the children should be doing.

[0004] Typically, control is done manually. The parent simply physically withholds the device from the child. In some cases, the parents might use the parental locks on the devices instead of physically withholding the device, locking and unlocking the device at their discretion.

BRIEF SUMMARY OF THE INVENTION

[0005] The present disclosure provides an improved system for allowing parental control through an automated locking and unlocking of devices, involving an automatically tracked reward system the parent (or teacher or supervisor, etc.) can pre-establish, allowing the child (or device user) to work towards earning an“unlocked” status for one or more devices by completing tasks.

The present disclosure also provides for system for reward based control of computer devices, the system comprising: a server connected to a computer device through a network, the computer device having at least one function; and an application loaded on the computer device comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked.

[0006] The system also provides for a system for reward based control of computer devices, the system comprising: a computer device connectable to a server through a network, the device having at least one function; and an application loaded on the computer device comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked.

[0007] The system also provides for a system for reward based control of computer devices, the system comprising: a computer device connectable to a server through a network, the device having at least one function; and an application loaded on a computer device having at least one function and connected to a server through a network, the application comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked. [0008] One skilled in the art would recognize that the following disclosure includes other embodiments not expressly described above. The above descriptions are exemplary.

BRIEF DESCRIPTION OF DRAWINGS

[0009] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present disclosure and, together with the description of example embodiments, serve to explain the principles and implementations of the disclosure.

[0010] FIG. 1 shows an example networking diagram of the system.

[0011] FIG. 2 shows an example flowchart of a parent application onboarding (i.e. adding) a child to the system.

[0012] FIG. 3 shows an example flowchart of a parent application establishing the controls. [0013] FIG. 4 shows an example flowchart of a child interface.

[0014] FIG. 5 shows an example of the disable schedule flow.

[0015] FIG. 6 shows an example of a user interface for the system with time bank functionality.

[0016] FIG. 7 shows an example of a user interface for the task functionality.

[0017] FIG. 8 shows an example screen of a completed task.

[0018] FIG. 9 shows an example of a user interface for the time bank withdrawal screen.

[0019] FIG. 10 shows an example of a flowchart for a withdrawal from the time bank.

[0020] FIG. 11 shows an example of a scheduler to monitor the lock condition of the device.

[0021] FIG. 12 shows an example of the addition of a marketplace to the time bank.

[0022] FIG. 13 shows an example of an algorithm to lock and unlock functionality on a device.

DETAILED DESCRIPTION OF THE INVENTION

[0023] A solution for controlling someone else’s use of a computer device is to automatically tie the ability to use the device to the completion of certain chores or tasks or educational programs. A device can be set with a schedule indicating when certain functionality of the device is enabled (aka unlocked) or disabled (aka unlocked) for a user, a set of chores for the user to complete in order to unlock the functionality at a time it is normally locked, an interface for someone other than the user to establish the schedule and chores, and an interface for the user to indicate that the chores have be completed.

[0024] Herein, the party controlling the device will be referred to as the“parent” and the user of the device being controlled will be referred to as the“child”, but the parties do not need to have an actual parent-child relationship. For example, the“parent” can be an employer and the“child” can be an employee. Another example is a teacher (as“parent”) controlling the device of a student (as“child”).

[0025] Mobile device management (MDM) herein refers to a system that allows for the control by one party over a mobile device used by another party. For example, a company might want to restrict the use of smartphones used by their employees. The company can implement an MDM solution to lock out certain functions or even the entire device, either continuously or over certain time periods. One implementation of MDM is server-client based, where the server can send commands to the device to control usage. This is enabled by the device’s OS (operating system) provider by way of an MDM license key that allows the server to send control commands, in the form of an MDM request, to the device.

[0026] Related to MDM, there is mobile application management (MAM), which allows control of individual applications on mobile devices by application wrapping. Both MDM and MAM enabling software will be referred to as“control software” and the keys will be referred to as“control keys”.

[0027] To control the access (e.g. locking and unlocking of functionalities) of device functionality, Service Agent software is installed on such devices. The agent receives commands from the server and initiates locking and unlocking of functionalities on the installed device on behalf of the server when the server provides lock and unlock command codes to the device. The Service Agent typically starts when the device turns on and continues to run in the background. The Service Agent can have an interface for set up and configuration.

[0028] A Service Agent can be installed by running an executable installer file. For example, for WindowsOS™ the installer installs the Service Agent as a Windows Service Application and executes it as a Windows Service app in the background. During the installation, the installer sets the Service Agent to automatically launch on startup. To prevent Service Agent termination by the user, the Installer sets an escalated administrator permission via the Windows Service Permissions settings. The installer also installs two executable interfaces. One for the first user (the parent) and the other for the second user (the child). At the end of the installation, the parent interface is launched so that the parent can configure the device with their service account and choose which child on their account will use this device. Upon installation completion, the Service Agent locks the access to the computer programs and websites selected by the parent and executes the child interface. The child interface allows the child to enter completion of the available chores and tasks to earn time or points, and to unlock the device if they have earned enough time or points. The Service Agent uses Group Policy API (application programming interface) to block and unblock access to the applications on the computer (lock and unlock). The same approach can be used for other operating systems with appropriate API, such as for Apple Mac™ computers running macOS™, but using macOS™ available API.

[0029] The control software includes two forms of user interface: a“parent interface” that allows a parent to establish the schedule and chores, and a“child interface” that allows a child to review the schedule and chores and to indicated completion of chores.

[0030] As used herein,“locking” can refer to disabling a device, disabling a device with exceptions (such as the ability to make calls, or the ability to use the parent and child interfaces), disabling a particular device function (such as access to the Internet or WiFi), or disabling specified applications on the device. All of these are referred to herein collectively as“device functionality”. An embodiment of locking includes limiting device to voice calls to certain contacts on the device and the use of the control software (parent and child interfaces). The parent and child can use the interfaces on the device being locked/unlocked, or they can use an interface on a different device or on a separate computer which remotely controls the locking/unlocking of the device.

[0031]“Unlocking” refers to re-enabling something that was locked. Locking can be performed on-command, during a set time period, or in response to a condition (such as the child going over a threshold amount of time for: using the device, or using a particular functionality of the device, or using particular applications on the device). Unlocking can be performed at a specified time, at the request of the parent through the parent interface, or upon the child completing conditions set in a schedule. The amount of time a device or application remains unlocked can be a preset amount of time, an amount of time until the next“locking” event, an amount of time proportional to the time spent on chores and tasks, an amount of time proportional to the amount of points earned in a task, or a combination of any of these.

[0032] A“device” herein (or“computing device”) refers to a computing device used by a user (“child”) of the system, including smart phones, tablets, PCs, laptops, gaming consoles, portable gaming devices, smart TVs, smart TV boxes, home routers, etc.

[0033] A“mobile device” herein refers to any computing device small enough to be held in the hands and having a network (e.g. Internet) connection. Examples include, but are not limited to, smartphones, mobile game devices, computer tablets, and wearable devices.

[0034] Herein a“schedule” is a database of devices, applications, times for locking, chores and tasks, and conditions for unlocking that a parent can set for a child. Some time intervals for“locked” can be“unbreakable”: that is, no amount of completing chores or tasks will unlock the device/application during that time interval. Other time intervals can be set to be unlocked once the child has completed the conditions set in the schedule. Other time intervals can be set to“free time”, where the child can access all the applications on the device without completing any conditions. Conditions can include completing a chore, completing a set number of chores, completing all chores, earning a threshold number of points, earning any points, withdrawing a set number of points from a time bank, or any combination of these.

[0035] Relating the chores/tasks to unlocking functionality can be set in a number of ways, either individually or in combination. One way is to establish a minimum number of chores to be indicated as“completed”, either by entry by the child or by automatic detection (e.g. “tasks”), in order for the functionality to be temporarily unlocked. A default can be set such that if all chores are completed, the functionality is unlocked even if it is below the threshold number. Another way is to provide a point value for each chore, then only unlocking the functionality once a minimum point value is reached. Another way is to unlock progressively in proportion to the work done, wherein each chore, or each set of points, unlocks functionality for a short period of time, based on a value given to the chore by the parent.

[0036] One particular embodiment of the control software is a connection to educational software. An educational software application can be provided with an API (application programming interface) to the control software such that the control software automatically fills in the completion or point information for completed tasks performed by the child for the educational software program. This has a benefit of encouraging the child to use the device for education by automatically providing a reward in the unlocking of other functionality for the device.

[0037] Herein a“chore” is an activity that the parent sets up in a schedule for the child to complete in order to work towards unlocking a device, functionality, application(s), or rewards. In one embodiment, this is done by accumulated points earned by the chores, which can then be redeemed/withdrawn to unlock the device for a period of time. A chore can be a physical activity (such as cleaning a room), an educational activity (such as completing a homework assignment), a social activity (such as spending time with a specific person), an economic activity (such as earning a set amount of money), or any other activity or goal designated by the parent. Additional functionality can be added, such as the ability for a parent, through the parent interface, adding a photo to the chore to help the child understand the chore.

[0038] Herein a“task” is a special type of chore, where the chore is performed on the device or on a server in communication with the device and automatically indicates to the control software an indication of completion. The task might also send other information, such as time spent on performing the task, or points accumulated in the task. The automatic indication can be done by built-in API (application programming interface) between the task software and the control software, or the control software can be configured to look for files created by the task software, such as certificates of completion. For example, a task software can be a language tutorial software, where completing portions of a language tutorial has the task software send the control software data that indicates that the child completed a task towards unlocking functionality for the device, for example using a video application to watch videos for entertainment, for a certain amount of time as determined by the schedule.

[0039] Additional functionality can be added to the system such that the child can provide proof of completion of the chore. For example, if the device has a camera, the child can take a photo of the evidence that the chore is completed and upload it to the control software through the child interface, and the parent can review the proof through the parent interface. The control software can also be configured to require a step of the parent, through the parent interface, approving the completion of the chore before the system unlocks the functionality. Alternatively, the system can automatically unlock the functionality without parent intervention.

[0040] Figure 1 shows an example of the system in place in a network. The individual devices (101A, 101B, 101C) have the control software installed and have connection to a network (110), such as the Internet or an intranet. At least one of the devices (101 A) has two interfaces (100P, 100C) installed as software: one for the parent (100P) to onboard a child, provide a schedule of tasks and control of the device (e.g. application lockout) and/or to control other devices (101B, 101C) through a server (102) in the network (110); and one for a child (100C) to provide chore completion information, or to initiate software tasks, to unlock the apps or device. There can be multiple instances of the child interface if there are multiple users for the device. The device (101 A, 101B, 101C) communicates (112) with the server (102) for multiple device control but can also work independently of the server if the device is only controlling itself. The server (102) can also provide control keys (115) to the devices.

[0041] Figure 2 shows an example of onboarding through the parent interface. The parent is authenticated (201), either signing on for the first time (onboarding parent) or signing on again to onboard a child. Once signed in, the parent can add a child (202) for scheduling. The schedule consists of data regarding when the device is locked or unlocked (time schedule), what functionality (e.g. applications, internet access, websites) are to be locked, and what chores and tasks are assigned to the child (202). After adding a child (202), the parent can either proceed to setting the schedule (206) or setting up control of the device (203). This can be control over the entire device, or control over one or more applications installed on the device. Getting control of the device/apps includes installing the requisite license keys (204) for the device/apps, thereby giving the control software the ability to lock and unlock functionality. Once the keys are installed, one or more chores can be selected with defaults (205) which then can be set in a schedule (206). Once the schedule is set (206), the software creates a profile for a child dashboard (207) so that the child can input completed tasks for the schedule. The schedule can include“free time” that allows access to the functionality without completing a chore or task. Special conditions can be attached to chores or tasks, such as how often the chore or task can be repeated, requiring that other set chores/tasks be completed before repeating the same chore or task, and/or a performance threshold at which a chore or task is considered complete.

[0042] Figure 3 shows an example flowchart for the parent dashboard. After authenticating into the main dashboard screen (301), the parent selects which child profile (302-1...302- N) to edit. For a given child (302-2), the parent can select a mode for the device (303). Modes can include unlocked, locked, or set by schedule, determining the lock status of the device: always unlocked (until changed), always locked (until changed), or locked and unlocked according to the schedule. Alternatively or in addition, the mode setting can presented as an option at the main dashboard (301). For a given child (302-2), the schedules (304) and chores/tasks (307) can be edited/created for the child. For the schedules (304), a new schedule can be created, or an existing schedule can be selected (305). Within that schedule, the days and times for the lock/unlock status can be set (306), either as one-time events or re-occurring windows of time. For the chores and tasks (307), the parent can again either create a new chore, or select a chore from a list of pre-existing chores. The parent then sets the options (309) for each chore/task (308), such as enabling the chore (i.e. allowing the child to use the chore/task towards unlocking functionality), setting how often the chore/task will be available to the child (e.g. once per day, once per week, etc.), setting a deadline for the chore/task (e.g. to be completed by the end of the week) if needed, and setting a number of points the chore/task is worth in terms of unlocking the functionality if applicable.

[0043] Figure 4 shows an example flowchart of a child interface for one embodiment. The child logs into the control software as a child (401). The set of chores and/or tasks available to that child are then presented as options (402). Optionally, the software can present further screens or pop-up windows showing details of the chore/task, such as instructions for completing the chore/task, point value, and deadline. The child can mark the chore complete (403), which either is used in calculating if the schedule is complete (405) or in adding to a running point total (404) if a point system is in use. If a task is selected, then it is marked complete when the child completes the task successfully. The software determines if the chore/task completion or point total is sufficient (405) to unlock the functionality (406). In one embodiment, this check is performed after the child withdraws the point total from a bank of points earned by the child. Once the functionality is unlocked (406), the software determines when (407) the functionality is re-locked (408), based either on a timer (407) or on a set time in the schedule.

Figure 5 shows an example disable schedule flow. Parents can set schedules for device functionality that allows access (unlock) depending on the time and day. First the server receives, from the control software of a device, the schedule records (501) indicating the device or devices to be enabled for locking/unlocking of functionality. Then the server sends a push notification (502) to a device to be enabled, with an MDM or Service Agent check-in. Once the device receives the push notification, it makes an MDM request, or Service Agent request, (503) to the server (102). In response, the server sends a push profile command (504) on device check-in with an enabled or disabled profile. In the case of an enabled device profile (505), the device unlocks functionality. In the case of a disabled device profile (506), the device locks functionality. In an embodiment, the functionality can be applications that are not considered“core” to the device (for example, applications other than the ones that come standard on the device) or applications that are not whitelisted by the parent.

Example 1

[0044] A teacher provides to his class computer tablets with two types of applications installed: an educational application that includes homework and reading assignments, and “fun” applications that run popular video games or other forms of entertainment. Also installed in each tablet is the control software as described herein. Using the parent interface, the teacher sets a schedule such that the“fun” applications are locked during the week and unlocked on the weekend. The teacher then sets the reading and homework assignments as chores (tasks) in the system, giving point values for each assignment and setting the system to unlock 15 minutes of time every time a student completes 25 points of assignments. The students use the child interface to see what the current assignments are. When the students complete the assignments, the educational application sends via API information of the completed assignments to the control software. The software then calculates the point totals for each student and temporarily unlocks the“fun” applications where the students meet the 25 point threshold.

Example 2

[0045] A mother gives her son a smartphone, but is concerned that he will spend time playing with the phone instead of doing household chores. She installs the control software and registers the software with the software provider’s server. She onboards herself as a parent and her son as a child in the software. She sets up a schedule of when the non-core services (i.e. everything except emergency calls, calender, calculator, and control software) are locked and unlocked. She makes 10PM to 7AM on weeknights unbreakable locks, and 4PM to 10PM breakable locks. The rest of the time is left as unlocked. She then sets a series of chores: cleaning room, washing dishes, practicing piano, and walking the dog. She sets the condition that, when all of the tasks are done for the day, the 4PM to 10PM time becomes unlocked for the day. The son then uses the child interface to check off the chores that he has completed. When all of the chores are checked off and the mother has given final approval through the parent interface, the phone automatically unlocks for the day. The server provides the phone with the MDM keys needed for the control software to lock and unlock the phone.

Example 3

[0046] A child has already used up (i.e. using the device functionality) the 2 hours he was previously given, either earned or given freely, on a Saturday during the open times of 8 AM to 10PM. He is then prompted to go to the provider’s server and is given a few options of modules (tasks) to perform: Math, Reading Comprehension, U.S. History, Science and Art/Music. He chooses U.S. History, reads the 10 pages, and takes a 10 question exam at the end of the reading. Depending on his score, he is given additional time to use his device (i.e. the server unlocks the device functionality). The child is allowed to retake the exam, to try and score higher, and receive more time if interested. Once the test is taken, that part of the module cannot be revisited for a preset time, e.g. 30 days. Additionally, now that History has been chosen, it cannot be chosen again until all of the other modules have been visited. The child must visit every module at least once before revisiting the same one.

The Time Bank

[0047] One embodiment of the system incorporates the concept of a“time bank” to keep track of the time a child (“user”) has“earned” and“spent”. The system keeps a running count of points that corresponds to an amount of time to be applied to unlocking the device, and these points can be“withdrawn” (i.e. used to unlock the device) or“deposited” (i.e. earned from tasks or chores). The points can be proportional to a unit of time: for examples: 5 points = 1 minute, or 1 point = 1 second, or some other ratio of points to time. In one embodiment, the child can also deposit unspent time back into the bank. For example, if the child withdraws two hours of time, but only uses one hour, the child can deposit one hour back into the bank to be used at a later time, or for other uses such as reward redemption.

[0048] Figure 6 shows an example of a user interface for the system as shown on a screen (602) of a device (601). The user interface can include a salutation that includes the user’s name (605), letting the user know that they are using the correct device and making the system more personal to the user. A running total of time available in the time bank (610) can be shown. The total can be of either the points available, or of the amount of time that corresponds to those points, or both. The time remaining for the device being unlocked (615) can be displayed. If the device is locked, then the time remaining will be 0. This can be displayed as all 0’s for the time (as shown), or with an alternative message, such as “Locked”. A display of how much time (620) and/or how many points the user earned that day can be displayed so that the user can see their progress. The user interface can include options for the user to change to other screens of the system to utilize the bank. This can include, for examples, buttons for entry to the time bank (625) to withdraw time to unlock the device, for entry to the chores list (630) to allow the user to earn points/time by completing chores, for entry to the learning system (635) to allow the user to earn points/time by completing learning tasks, and for entry to the user’s schedule (640) so the user can see when the device is scheduled for unlocking. Other embodiments for the user interface can include pull-down menus, voice control, or other standard selection mechanisms used for computing devices.

[0049] Figure 7 shows an example of the user interface screen for the learn option. The screen shows options (in this case, with buttons (701)) for learning tasks the user can complete to earn points/time for the time bank. The learning tasks can include any subject that can be tested on a computer device. For example, the tasks can include multiple choice questions that have to be correctly answered to award the user points. The tasks can be set to allow the user to be awarded points if the user correctly answers a threshold number of questions. If the user fails, the system can be set to allow the user to re-attempt the task. The system can be set to require a waiting period to pass before allowing the user to re- attempt the task, or the system can be set to allow the user to re-attempt right away.

[0050] Figure 8 shows an example screen for a completed task. The screen can show the number of points and/or time earned (805) by competing the task and can show the results of the task (810) in terms of which questions were answered correctly. The results (810) can also include additional data from the task, such as showing the correct answers to the questions, amount of time it took to complete the task, and/or how many attempts it took to complete the task.

[0051] Figure 9 shows an example screen for the time bank. The screen can show inputs (905) for the amount of time the user wishes to withdraw to unlock the device (or extend an unlock, if the device is already unlocked). Here the inputs (905) as buttons with increments of time (1 minute, 5 minutes, and 10 minutes) the user can increase the withdrawal by. Multiple increments can be used, for example pressing“1 minute” twice then“10 minutes” once selects a withdrawal of 12 minutes. The running total for the withdrawal (910) can be displayed. Further inputs (915) can be provided to allow the user to confirm the withdrawal or cancel the withdrawal.

[0052] Figure 10 shows an example of the system flowchart for withdrawal from the time bank. When a user withdraws time (1005) from the time bank, the system (server database) checks to see if the device is locked or not (1010). If the device is locked, the server sets the device to“unlocked” (1020). The server then sets the field for determining the unlock time (which can be a time of day or a countdown timer) to however much time has been withdrawn from the bank (1025). This might include a point-to-time conversion. Then the server sends a request to the device for MDM check-in (1030). When the device checks-in (1035), the server provides the device the unlock command (1040) which the device uses to unlock the apps for the user to use (1045). If the device is not locked, then the server just updates the unlock time by adding the new withdrawn amount (1015). In both cases, a scheduler (1105) runs to check and see when the unlock time has run out and the device needs to be locked again. Typically, the scheduler will run on its own thread parallel with the withdrawal thread.

[0053] Figure 11 shows an example of a scheduler (1105) to monitor the lock/unlock status of the device. The server can start by finding all the devices in the database that are both a) unlocked and b) have their unlock time either counted down to zero or have run past the present clock time (depending on how the unlock time is stored) (1110). Those devices have their status changed in the database to indicate that they are now locked (1115) and requests are sent to the devices to do an MDM check-in (1115). When the devices check in, the server sends a lock command to the devices (1125) which the devices use to lock themselves (1130). In one embodiment, this can include locking non-core applications on the device (e.g. social media, videos, games, some messaging). This lock can manifest as the icons for the applications being hidden from view on the device. It could also manifest as the icons being greyed out or marked to indicate that they are not accessible.

[0054] Figure 12 shows an example of the addition of a marketplace option to be used with the time bank. In place of directly going to a time bank to manage points/time, the system might have a general“rewards” section (1205) that includes both the time bank (1210) and a marketplace (1235). The time bank (1205) and marketplace (1235) could be on separate screens or shared on one screen. The time bank (1210) can have two options: withdrawal of time (1215) to unlock the device or extend a current unlock (1220), or a deposit of time (1225), where the user can deposit withdrawn time (1230) in exchange for points/time being added back to the bank (1230). This deposit can be at the same ratio of pointsdime as the withdrawal (1215, 1220), or it can be a different ratio. This deposit can result in the device going from unlocked to locked status at the time of deposit, if the deposit amount matches the current unlock time. These deposited points (as well as earned points) can then be used for future withdrawal (1215) or in the marketplace (1235). The marketplace (1235) is an option for the user to redeem earned and/or deposited points held in the time bank for rewards. Rewards can be anything that can be delivered electronically to the user. For example, rewards can be gift certificates to local business, gift certificates to on-line purchases, purchasable video content, purchasable games, etc. The user selects a reward to purchase (1240) with the points, the points are subtracted from the time bank (1245), and the server delivers the reward to the user (1250), by direct download, email, a code delivered by SMS (Short Message Service), or by any other electronic means. It could also electronically arrange delivery of a physical reward by mail or delivery service.

[0055] Figure 13 shows an example flowchart for the lock/unlock algorithm. When the user’s device receives a lock or unlock command (1305), the server agent on the device uses the system API to lock (1310) or unlock (1320) access to selected applications (e.g. non-core applications) according to the set schedule. If the device is locked, the device might be configured to open, or bring into focus/front-most-view, the user application (1315) that displays, to the user, the tasks and/or chores the user can use to unlock the device. In either case, the user application is refreshed (1330) to reflect the correct device status.

[0056] In one embodiment, tasks can award points proportionately to the success of the task. For example, if a task has ten questions for the child to answer, and the child answers eight of them correctly, the system can award the child 80% of the total number of points the task is worth. In a further embodiment, the child can have the option of retaking the test to attempt to capture the remaining points. For example, if the child answered 70% of the questions correctly on the first attempt, receiving 70% of the points, the child can re- take the test. If the child then answers 90% of the questions correctly, a further 20% of the points is awarded (for a total of 90% of the points available from the task).

Example 4

[0057] The parent enters coupon-based rewards into the system: 15 coupons for free ice cream from a local ice cream shop, 20 coupons for free tacos at a local fast food restaurant, and 8 movie ticket coupons for the local theatre. The parent defines how much time, or points in a point system, each coupon is worth by inputting them into the parent interface. When the child earns enough points by completing chores or tasks, the child then will see the available coupons to choose from in the child interface. Upon choosing a reward, their total time in the time bank, or points in a point system, will be deducted by the amount of time, or points, this coupon (reward) is worth. Then, the child can take the device with the coupon displayed on the screen, or a print-out of the coupon, and present it to the chosen facility where this coupon can be redeemed for the reward (in this example, ice cream, taco, or movie ticket).

[0058] It is to be understood that the disclosure is not limited to particular methods or systems, which can, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the content clearly dictates otherwise. The term “plurality” includes two or more referents unless the content clearly dictates otherwise. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosure pertains.

Claims

CLAIMS What is claimed is:

1. A system for reward based control of computer devices, the system comprising: a server connected to a computer device through a network, the computer device having at least one function; and an application loaded on the computer device comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked.

2. The system of claim 1, wherein the server provides computer device management functionality to the computer device through the use of license keys.

3. The system of any of claims 1 and 2, wherein the application has an application programming interface with other software and the application is configured to receive information from the other software regarding completion of a chore of the chores.

4. The system of any of claims 1-3, wherein the application detects the presence of a certificate of completion generated by other software and to automatically update the completion of a chore of the chores based on the detection.

5. The system of any of claims 1-4, wherein the tasks comprise educational tests to be completed on the computer device.

6. The system of any of claims 1-5, further comprising a bank of points earned from the chores and/or the tasks, and an interface for the second user to withdraw points from the bank that unlocks the at least one function for an amount of time based on the withdrawn points.

7. The system of claim 6, further comprising functionality to allow the second user deposit points into the bank by forfeiting unlock time.

8. The system of claim 7, further comprising a marketplace function that allows the second user to purchase rewards using points from the bank.

9. The system of claim 8, wherein the rewards can be either electronic rewards or physical rewards.

10. The system of any of claims 1-8, wherein the computing device further comprises a service agent that locks or unlocks the at least one function when the server sends the computing device a corresponding lock or unlock command.

11. A system for reward based control of computer devices, the system comprising: a computer device connectable to a server through a network, the device having at least one function; and an application loaded on the computer device comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked.

12. A system for reward based control of computer devices, the system comprising: a computer device connectable to a server through a network, the device having at least one function; and an application loaded on a computer device having at least one function and connected to a server through a network, the application comprising code that: locks and unlocks the at least one function; enables a first user to establish a schedule of locking and unlocking the at least one function; enables the first user to establish chores or tasks that will unlock the at least one function; enables a second user, different from the first user, to enter completion of the chores or tasks; and

determines, based on the completion of the chores or tasks, a number of points to be awarded to the second user, said number of points corresponding to an amount of time that the at least one function would be unlocked.