WO2019200350A1 - Système de commande de dispositif basé sur la récompense - Google Patents
Système de commande de dispositif basé sur la récompense Download PDFInfo
- Publication number
- WO2019200350A1 WO2019200350A1 PCT/US2019/027374 US2019027374W WO2019200350A1 WO 2019200350 A1 WO2019200350 A1 WO 2019200350A1 US 2019027374 W US2019027374 W US 2019027374W WO 2019200350 A1 WO2019200350 A1 WO 2019200350A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- function
- chores
- tasks
- points
- 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
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- 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
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2149—Restricted operating environment
Definitions
- the present disclosure relates to a system for controlling access to network enabled devices based on an automatically tracked reward system.
- 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.
- network Internet or private network
- 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.
- control is done manually.
- the parent simply physically withholds the device from the child.
- the parents might use the parental locks on the devices instead of physically withholding the device, locking and unlocking the device at their discretion.
- 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.
- 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.
- 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.
- FIG. 1 shows an example networking diagram of the system.
- FIG. 2 shows an example flowchart of a parent application onboarding (i.e. adding) a child to the system.
- FIG. 3 shows an example flowchart of a parent application establishing the controls.
- FIG. 4 shows an example flowchart of a child interface.
- FIG. 5 shows an example of the disable schedule flow.
- FIG. 6 shows an example of a user interface for the system with time bank functionality.
- FIG. 7 shows an example of a user interface for the task functionality.
- FIG. 8 shows an example screen of a completed task.
- FIG. 9 shows an example of a user interface for the time bank withdrawal screen.
- FIG. 10 shows an example of a flowchart for a withdrawal from the time bank.
- FIG. 11 shows an example of a scheduler to monitor the lock condition of the device.
- FIG. 12 shows an example of the addition of a marketplace to the time bank.
- FIG. 13 shows an example of an algorithm to lock and unlock functionality on a device.
- 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.
- 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.
- the“parent” can be an employer and the“child” can be an employee.
- a teacher (as“parent”) controlling the device of a student (as“child”).
- MDM Mobile device management
- OS operating system
- MDM mobile application management
- 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.
- a Service Agent can be installed by running an executable installer file.
- the installer installs the Service Agent as a Windows Service Application and executes it as a Windows Service app in the background.
- the installer sets the Service Agent to automatically launch on startup.
- 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).
- 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.
- 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).
- Group Policy API application programming interface
- the same approach can be used for other operating systems with appropriate API, such as for Apple MacTM computers running macOSTM, but using macOSTM available API.
- 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.
- 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.
- 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.
- A“device” herein 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- a network 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.
- 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.
- 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).
- 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.
- one or more chores can be selected with defaults (205) which then can be set in a schedule (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.
- FIG 3 shows an example flowchart for the parent dashboard.
- the parent After authenticating into the main dashboard screen (301), the parent selects which child profile (302-1...302- N) to edit.
- 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.
- the mode setting can presented as an option at the main dashboard (301).
- the schedules (304) and chores/tasks (307) can be edited/created for the child.
- a new schedule can be created, or an existing schedule can be selected (305).
- the days and times for the lock/unlock status can be set (306), either as one-time events or re-occurring windows of time.
- the parent can again either create a new chore, or select a chore from a list of pre-existing chores.
- the parent 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.
- FIG 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).
- 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).
- this check is performed after the child withdraws the point total from a bank of points earned by the child.
- 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.
- 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.
- the server sends a push notification (502) to a device to be enabled, with an MDM or Service Agent check-in.
- the device receives the push notification, it makes an MDM request, or Service Agent request, (503) to the server (102).
- the server sends a push profile command (504) on device check-in with an enabled or disabled profile.
- 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.
- 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.
- the teacher sets a schedule such that the“fun” applications are locked during the week and unlocked on the weekend.
- the teacher 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.
- the educational application sends via API information of the completed assignments to the control software.
- the software calculates the point totals for each student and temporarily unlocks the“fun” applications where the students meet the 25 point threshold.
- 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.
- 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.
- 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.
- 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 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- Figure 10 shows an example of the system flowchart for withdrawal from the time bank.
- the system server database
- the server 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).
- the server just updates the unlock time by adding the new withdrawn amount (1015).
- 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.
- FIG 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).
- the server sends a lock command to the devices (1125) which the devices use to lock themselves (1130).
- 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.
- Figure 12 shows an example of the addition of a marketplace option to be used with the time bank.
- 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.
- 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.
- SMS Short Message Service
- FIG 13 shows an example flowchart for the lock/unlock algorithm.
- 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.
- selected applications e.g. non-core applications
- 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.
- the user application is refreshed (1330) to reflect the correct device status.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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).
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- General Engineering & Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Entrepreneurship & Innovation (AREA)
- Health & Medical Sciences (AREA)
- Game Theory and Decision Science (AREA)
- Computer Security & Cryptography (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Un système de commande de dispositif informatique basé sur la récompense comprend une interface parent et une interface enfant: l'interface parent établissant une programmation de verrouillage et de déverrouillage pour le dispositif informatique et fournissant une liste de corvées pour le déverrouillage de la fonctionnalité du dispositif informatique, et l'interface enfant permet la visualisation et l'achèvement des corvées.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201862657608P | 2018-04-13 | 2018-04-13 | |
| US62/657,608 | 2018-04-13 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2019200350A1 true WO2019200350A1 (fr) | 2019-10-17 |
Family
ID=68163782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2019/027374 Ceased WO2019200350A1 (fr) | 2018-04-13 | 2019-04-12 | Système de commande de dispositif basé sur la récompense |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2019200350A1 (fr) |
Cited By (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111148104A (zh) * | 2019-12-27 | 2020-05-12 | 联想(北京)有限公司 | 信息处理方法和网络设备 |
| US10936345B1 (en) | 2019-09-09 | 2021-03-02 | Apple Inc. | Techniques for managing display usage |
| US11042281B2 (en) | 2014-08-15 | 2021-06-22 | Apple Inc. | Weather user interface |
| US11061372B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | User interfaces related to time |
| US11080004B2 (en) | 2019-05-31 | 2021-08-03 | Apple Inc. | Methods and user interfaces for sharing audio |
| US11079894B2 (en) | 2015-03-08 | 2021-08-03 | Apple Inc. | Device configuration user interface |
| US11131967B2 (en) | 2019-05-06 | 2021-09-28 | Apple Inc. | Clock faces for an electronic device |
| WO2022000047A1 (fr) * | 2020-07-03 | 2022-01-06 | Ashley Carter | Système et procédé de contrôle du temps passé devant un écran d'un individu |
| US11301130B2 (en) | 2019-05-06 | 2022-04-12 | Apple Inc. | Restricted operation of an electronic device |
| US11327650B2 (en) | 2018-05-07 | 2022-05-10 | Apple Inc. | User interfaces having a collection of complications |
| US11327634B2 (en) | 2017-05-12 | 2022-05-10 | Apple Inc. | Context-specific user interfaces |
| US11372659B2 (en) | 2020-05-11 | 2022-06-28 | Apple Inc. | User interfaces for managing user interface sharing |
| US11393022B1 (en) * | 2019-12-30 | 2022-07-19 | United Services Automobile Association (Usaa) | Systems and methods for incentivizing saving |
| US11526256B2 (en) | 2020-05-11 | 2022-12-13 | Apple Inc. | User interfaces for managing user interface sharing |
| US11539831B2 (en) | 2013-03-15 | 2022-12-27 | Apple Inc. | Providing remote interactions with host device using a wireless device |
| US11580867B2 (en) | 2015-08-20 | 2023-02-14 | Apple Inc. | Exercised-based watch face and complications |
| US11586719B1 (en) | 2020-09-25 | 2023-02-21 | Wells Fargo Bank, N.A. | Apparatuses and methods for verified application access |
| US11604571B2 (en) | 2014-07-21 | 2023-03-14 | Apple Inc. | Remote user interface |
| US11609681B2 (en) | 2014-09-02 | 2023-03-21 | Apple Inc. | Reduced size configuration interface |
| US11694590B2 (en) | 2020-12-21 | 2023-07-04 | Apple Inc. | Dynamic user interface with time indicator |
| US11720239B2 (en) | 2021-01-07 | 2023-08-08 | Apple Inc. | Techniques for user interfaces related to an event |
| US11740776B2 (en) | 2014-08-02 | 2023-08-29 | Apple Inc. | Context-specific user interfaces |
| WO2023220771A1 (fr) * | 2022-05-18 | 2023-11-23 | LifeTech Balance Pty Ltd | Dispositif de contrainte de temps d'écran et procédé de contrainte |
| US11921992B2 (en) | 2021-05-14 | 2024-03-05 | Apple Inc. | User interfaces related to time |
| US11960701B2 (en) | 2019-05-06 | 2024-04-16 | Apple Inc. | Using an illustration to show the passing of time |
| US12019862B2 (en) | 2015-03-08 | 2024-06-25 | Apple Inc. | Sharing user-configurable graphical constructs |
| US12045014B2 (en) | 2022-01-24 | 2024-07-23 | Apple Inc. | User interfaces for indicating time |
| US12175065B2 (en) | 2016-06-10 | 2024-12-24 | Apple Inc. | Context-specific user interfaces for relocating one or more complications in a watch or clock interface |
| US12182373B2 (en) | 2021-04-27 | 2024-12-31 | Apple Inc. | Techniques for managing display usage |
| US12293407B1 (en) * | 2019-12-30 | 2025-05-06 | United Services Automobile Association (Usaa) | Systems and methods for incentivizing saving |
| US12386428B2 (en) | 2022-05-17 | 2025-08-12 | Apple Inc. | User interfaces for device controls |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080270240A1 (en) * | 2007-04-30 | 2008-10-30 | Viva Chu | Systems and methods of managing tasks assigned to an individual |
| US20110237227A1 (en) * | 2010-03-25 | 2011-09-29 | T-Mobile Usa, Inc. | Chore and Rewards Tracker |
| US20130080326A1 (en) * | 2011-03-28 | 2013-03-28 | Jeremy Joseph Jacola | Household payment management and tracking system |
| US20140308638A1 (en) * | 2013-04-16 | 2014-10-16 | Intrinsic Value Software, Inc. | Using an earned points system to provide internet access |
| US20150007307A1 (en) * | 2013-03-10 | 2015-01-01 | eBravium, Inc. | Method and System for Integration of Instruction and Task Completion Based Access to Mobile Device Operating Systems |
| US20150243175A1 (en) * | 2014-02-25 | 2015-08-27 | Kavita Raman | Automated disciplinary and motivational system |
-
2019
- 2019-04-12 WO PCT/US2019/027374 patent/WO2019200350A1/fr not_active Ceased
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080270240A1 (en) * | 2007-04-30 | 2008-10-30 | Viva Chu | Systems and methods of managing tasks assigned to an individual |
| US20110237227A1 (en) * | 2010-03-25 | 2011-09-29 | T-Mobile Usa, Inc. | Chore and Rewards Tracker |
| US20130080326A1 (en) * | 2011-03-28 | 2013-03-28 | Jeremy Joseph Jacola | Household payment management and tracking system |
| US20150007307A1 (en) * | 2013-03-10 | 2015-01-01 | eBravium, Inc. | Method and System for Integration of Instruction and Task Completion Based Access to Mobile Device Operating Systems |
| US20140308638A1 (en) * | 2013-04-16 | 2014-10-16 | Intrinsic Value Software, Inc. | Using an earned points system to provide internet access |
| US20150243175A1 (en) * | 2014-02-25 | 2015-08-27 | Kavita Raman | Automated disciplinary and motivational system |
Cited By (57)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11539831B2 (en) | 2013-03-15 | 2022-12-27 | Apple Inc. | Providing remote interactions with host device using a wireless device |
| US12093515B2 (en) | 2014-07-21 | 2024-09-17 | Apple Inc. | Remote user interface |
| US11604571B2 (en) | 2014-07-21 | 2023-03-14 | Apple Inc. | Remote user interface |
| US11740776B2 (en) | 2014-08-02 | 2023-08-29 | Apple Inc. | Context-specific user interfaces |
| US12430013B2 (en) | 2014-08-02 | 2025-09-30 | Apple Inc. | Context-specific user interfaces |
| US11922004B2 (en) | 2014-08-15 | 2024-03-05 | Apple Inc. | Weather user interface |
| US11550465B2 (en) | 2014-08-15 | 2023-01-10 | Apple Inc. | Weather user interface |
| US12229396B2 (en) | 2014-08-15 | 2025-02-18 | Apple Inc. | Weather user interface |
| US11042281B2 (en) | 2014-08-15 | 2021-06-22 | Apple Inc. | Weather user interface |
| US12164747B2 (en) | 2014-09-02 | 2024-12-10 | Apple Inc. | Reduced size configuration interface |
| US11609681B2 (en) | 2014-09-02 | 2023-03-21 | Apple Inc. | Reduced size configuration interface |
| US12019862B2 (en) | 2015-03-08 | 2024-06-25 | Apple Inc. | Sharing user-configurable graphical constructs |
| US11079894B2 (en) | 2015-03-08 | 2021-08-03 | Apple Inc. | Device configuration user interface |
| US11908343B2 (en) | 2015-08-20 | 2024-02-20 | Apple Inc. | Exercised-based watch face and complications |
| US12243444B2 (en) | 2015-08-20 | 2025-03-04 | Apple Inc. | Exercised-based watch face and complications |
| US11580867B2 (en) | 2015-08-20 | 2023-02-14 | Apple Inc. | Exercised-based watch face and complications |
| US12175065B2 (en) | 2016-06-10 | 2024-12-24 | Apple Inc. | Context-specific user interfaces for relocating one or more complications in a watch or clock interface |
| US11775141B2 (en) | 2017-05-12 | 2023-10-03 | Apple Inc. | Context-specific user interfaces |
| US11327634B2 (en) | 2017-05-12 | 2022-05-10 | Apple Inc. | Context-specific user interfaces |
| US12468434B2 (en) | 2017-05-12 | 2025-11-11 | Apple Inc. | Methods and user interfaces for editing a clock face |
| US11977411B2 (en) | 2018-05-07 | 2024-05-07 | Apple Inc. | Methods and systems for adding respective complications on a user interface |
| US11327650B2 (en) | 2018-05-07 | 2022-05-10 | Apple Inc. | User interfaces having a collection of complications |
| US11960701B2 (en) | 2019-05-06 | 2024-04-16 | Apple Inc. | Using an illustration to show the passing of time |
| US11340778B2 (en) | 2019-05-06 | 2022-05-24 | Apple Inc. | Restricted operation of an electronic device |
| US11301130B2 (en) | 2019-05-06 | 2022-04-12 | Apple Inc. | Restricted operation of an electronic device |
| US11340757B2 (en) | 2019-05-06 | 2022-05-24 | Apple Inc. | Clock faces for an electronic device |
| US11131967B2 (en) | 2019-05-06 | 2021-09-28 | Apple Inc. | Clock faces for an electronic device |
| US12265703B2 (en) | 2019-05-06 | 2025-04-01 | Apple Inc. | Restricted operation of an electronic device |
| US11714597B2 (en) | 2019-05-31 | 2023-08-01 | Apple Inc. | Methods and user interfaces for sharing audio |
| US11157234B2 (en) | 2019-05-31 | 2021-10-26 | Apple Inc. | Methods and user interfaces for sharing audio |
| US11080004B2 (en) | 2019-05-31 | 2021-08-03 | Apple Inc. | Methods and user interfaces for sharing audio |
| US12373079B2 (en) | 2019-09-09 | 2025-07-29 | Apple Inc. | Techniques for managing display usage |
| US10936345B1 (en) | 2019-09-09 | 2021-03-02 | Apple Inc. | Techniques for managing display usage |
| CN111148104A (zh) * | 2019-12-27 | 2020-05-12 | 联想(北京)有限公司 | 信息处理方法和网络设备 |
| US12293407B1 (en) * | 2019-12-30 | 2025-05-06 | United Services Automobile Association (Usaa) | Systems and methods for incentivizing saving |
| US11393022B1 (en) * | 2019-12-30 | 2022-07-19 | United Services Automobile Association (Usaa) | Systems and methods for incentivizing saving |
| US11061372B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | User interfaces related to time |
| US11442414B2 (en) | 2020-05-11 | 2022-09-13 | Apple Inc. | User interfaces related to time |
| US12008230B2 (en) | 2020-05-11 | 2024-06-11 | Apple Inc. | User interfaces related to time with an editable background |
| US12422977B2 (en) | 2020-05-11 | 2025-09-23 | Apple Inc. | User interfaces with a character having a visual state based on device activity state and an indication of time |
| US11526256B2 (en) | 2020-05-11 | 2022-12-13 | Apple Inc. | User interfaces for managing user interface sharing |
| US12099713B2 (en) | 2020-05-11 | 2024-09-24 | Apple Inc. | User interfaces related to time |
| US12333123B2 (en) | 2020-05-11 | 2025-06-17 | Apple Inc. | User interfaces for managing user interface sharing |
| US11372659B2 (en) | 2020-05-11 | 2022-06-28 | Apple Inc. | User interfaces for managing user interface sharing |
| US11822778B2 (en) | 2020-05-11 | 2023-11-21 | Apple Inc. | User interfaces related to time |
| US11842032B2 (en) | 2020-05-11 | 2023-12-12 | Apple Inc. | User interfaces for managing user interface sharing |
| WO2022000047A1 (fr) * | 2020-07-03 | 2022-01-06 | Ashley Carter | Système et procédé de contrôle du temps passé devant un écran d'un individu |
| US11803632B1 (en) | 2020-09-25 | 2023-10-31 | Wells Fargo Bank, N.A. | Apparatuses and methods for verified application access |
| US11586719B1 (en) | 2020-09-25 | 2023-02-21 | Wells Fargo Bank, N.A. | Apparatuses and methods for verified application access |
| US12456406B2 (en) | 2020-12-21 | 2025-10-28 | Apple Inc. | Dynamic user interface with time indicator |
| US11694590B2 (en) | 2020-12-21 | 2023-07-04 | Apple Inc. | Dynamic user interface with time indicator |
| US11720239B2 (en) | 2021-01-07 | 2023-08-08 | Apple Inc. | Techniques for user interfaces related to an event |
| US12182373B2 (en) | 2021-04-27 | 2024-12-31 | Apple Inc. | Techniques for managing display usage |
| US11921992B2 (en) | 2021-05-14 | 2024-03-05 | Apple Inc. | User interfaces related to time |
| US12045014B2 (en) | 2022-01-24 | 2024-07-23 | Apple Inc. | User interfaces for indicating time |
| US12386428B2 (en) | 2022-05-17 | 2025-08-12 | Apple Inc. | User interfaces for device controls |
| WO2023220771A1 (fr) * | 2022-05-18 | 2023-11-23 | LifeTech Balance Pty Ltd | Dispositif de contrainte de temps d'écran et procédé de contrainte |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019200350A1 (fr) | Système de commande de dispositif basé sur la récompense | |
| US12120108B2 (en) | Web integration, timing, access, and distribution control | |
| US20170178526A1 (en) | System and Method for Multi-Layered Education Based Locking of Electronic Computing Devices | |
| US9483805B1 (en) | Limited tokens in online education | |
| US20150007307A1 (en) | Method and System for Integration of Instruction and Task Completion Based Access to Mobile Device Operating Systems | |
| US20160293025A1 (en) | Attendance tracking mobile reader device and system | |
| US20170076623A1 (en) | System and method for a comprehensive integrated education system | |
| WO2016160959A1 (fr) | Systèmes et procédés de réglementation de l'utilisation d'un dispositif | |
| KR101602665B1 (ko) | 온라인 상의 학습 미션을 이용한 학습관리 방법 및 이에 사용되는 학습관리 서버 | |
| US20140308638A1 (en) | Using an earned points system to provide internet access | |
| US20190274612A1 (en) | System and Method for Real-time Reporting, Interacting, and Updating of Guardian Actions Within a School System | |
| US10133682B2 (en) | Managing grouped student devices with timed locks | |
| US20190026482A1 (en) | Device access control based on task completion | |
| US20210342424A1 (en) | System, platform and method for transfering users between virtual rooms | |
| EP3011469A2 (fr) | Mots de passe centrés sur une tâche | |
| US20190274611A1 (en) | System and Method for Real-time Reporting, Interacting, and Updating of Student, Guardian, Teacher, and Administrator Interactions Within a School System | |
| KR101639990B1 (ko) | 대학교 온라인 교육 서비스 제공 시스템 | |
| WO2014164567A1 (fr) | Verrouillage multi-niveaux de dispositifs informatiques sur des bases éducatives | |
| US11757958B1 (en) | Systems and methods for secure, controlled virtual visitation with confinement institution inmates | |
| US20140170630A1 (en) | Learning content-providing method | |
| CN112235588B (zh) | 直播中的预测互动处理方法、装置、电子设备及存储介质 | |
| JP4883646B2 (ja) | 可変通知システム、可変通知サーバ、可変通知方法及びコンピュータプログラム | |
| US20190274613A1 (en) | System and Method for Real-time Reporting, Interacting, and Updating of Student Actions Within a School System | |
| KR102831101B1 (ko) | 서베이에 대한 그룹 패널 운영 방법 및 디바이스 | |
| JP7634625B1 (ja) | 端末装置、入場登録方法、ならびに、プログラム |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19786251 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: 19786251 Country of ref document: EP Kind code of ref document: A1 |