System and method for controlling communication device use

Information

  • Patent Grant
  • 10993187
  • Patent Number
    10,993,187
  • Date Filed
    Wednesday, June 26, 2019
    5 years ago
  • Date Issued
    Tuesday, April 27, 2021
    3 years ago
Abstract
A computer implemented method is provided including establishing a value corresponding to a particular user of a device, receiving an indication of a triggering condition of the particular user of the device, the triggering condition being enabled by the device or measurable by the device, and determining the triggering condition has been met by the user via the device. The method further includes modifying the value responsive to determining the triggering condition has been met, determining when the value crosses a particular threshold, and disabling an application or a functional component of the device responsive to the value crossing the particular threshold. A system for implementing the method is also provided.
Description
BACKGROUND

With the advent of smartphones, laptops, tablets and other portable electronic devices, a child may now have un-tethered access to the Internet, various communication protocols (e.g. phone, video phone, email, text chatting, and text messaging) and a wide variety of digital entertainment. However, such devices may serve as a distraction which prevents a child from behaving responsibly. Parents are keen to keep an eye on their children's behavior including communication, travel and what media and information their children are exposed to. Further, parents may want to limit the amount of time their children spend exploring and consuming various electronic media (e.g. television and Internet content).


SUMMARY

This Summary introduces simplified concepts that are further described below in the Detailed Description of Illustrative Embodiments. This Summary is not intended to identify key features or essential features of the claimed subject matter and is not intended to be used to limit the scope of the claimed subject matter.


A computer implemented method of controlling device use is provided. The method includes receiving from a first user an indication of a schedule of required check-in communications, the schedule corresponding to a second user. The method further includes determining when a check-in communication has been initiated by the second user pursuant to the schedule, and disabling at least one of an application and a functional component of a device corresponding to the second user responsive to determining at least one check-in communication has not been received pursuant to the schedule.


Another computer implemented method of controlling device use is provided. The method includes receiving from a first user an indication of a required state of a device corresponding to a second user. The method further includes determining a current state of the device corresponding to the second user, and disabling at least one of an application and a functional component of the device responsive to the current state being inconsistent with the required state.


Another computer implemented method of controlling device use is provided. The method includes receiving from a first user an indication of a maximum allowed use of at least one device corresponding to a second user. The method further includes determining amount of use of the at least one device corresponding to the second user, and disabling at least one of an application and a functional component of the at least one device responsive to the at least one of the determined amount of use being greater than the indicated maximum allowed use.


Another computer implemented method of controlling device use is provided. The method includes receiving an indication from a first user of a geographic area and receiving an indication from the first user of a schedule corresponding to at least one time at which a second user is required to be present at the geographic area. The method further includes receiving location information of a device corresponding to the second user, determining whether the location information indicates that the second user is present at the geographic area at the at least one time, and disabling at least one of an application and a functional component of the device responsive to determining that the second user is not present at the geographic area at the at least one time.


Another computer implemented method of controlling device use is provided. The method includes establishing a value corresponding to a particular user of a device, receiving an indication of at least one triggering condition of the particular user corresponding to the device, the at least one triggering condition being at least one of enabled by the device and measurable by the device, and determining the at least one triggering condition has been met by the user via the device. The method further includes modifying the value responsive to determining the at least one triggering condition has been met, determining when the value crosses a particular threshold, and disabling at least one of an application and a functional component of the device responsive to the value crossing the particular threshold.





BRIEF DESCRIPTION OF THE DRAWING(S)

A more detailed understanding may be had from the following description, given by way of example with the accompanying drawings. The Figures in the drawings and the detailed description are examples. The Figures and the detailed description are not to be considered limiting and other examples are possible. Like reference numerals in the Figures indicate like elements wherein:



FIG. 1 shows a system for controlling use of a mobile device.



FIGS. 2-6 are diagrams showing methods for controlling use of a mobile device.



FIGS. 7A-7G show example screen displays enabled by the system of FIG. 1.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENT(S)

Embodiments are described below with reference to the drawing figures where like numerals represent like elements throughout.


Referring to FIG. 1, a system 10 is provided including a monitoring manager 20 used for controlling use of a monitored device 12. The monitoring manager 20 includes an enablement engine 22, a mapping engine 24, an overseeing user application 28, a monitoring application program interface (“API”) 32, a user datastore 34, a contributor application program interface (“API”) 36, and a carrier integration application 38. The monitoring manager 20 can be implemented on one or more network-connectable computing systems and need not be implemented on a single system at a single location. The monitoring manager 20 is configured for communication via a network 40 with other network-connectable computing systems including one or more devices 12 (“monitored devices”) corresponding to a monitored user and client devices 16 corresponding to a user who configures the monitoring manager 20. Alternatively, the monitoring manager 20 or one or more components thereof can be executed on the monitored device 12 or other system. The overseeing user application 28 includes a web application or other application enabled by the monitoring manager 20 and accessible to a client device 16 via a network and/or installed and executed on a client device 16.


The network 40 can include one or more wired or wireless networks, including for example the internet and wireless carrier systems. The monitored device 12, and the client devices 16 can include for example a smartphone, laptop computer or other wired or wireless terminal preferably configured to operate on a wired or wireless telecommunication network. The operation of the monitoring manager 20 is described herein with respect to the devices 12, 16. One skilled in the art will recognize that the monitoring manager 20 can operate with other suitable wired or wireless network-connectable computing systems.


Software and/or hardware residing on a monitored device 12 enables a monitoring agent 13 in the form of a client application which can provide device location information and device use information to the monitoring manager 20 via the monitoring API 32. In addition to components enabling data processing and wireless communication, the monitored device 12 includes a location determination system (“LDS”) 15, such as a global positioning system (“GPS”) receiver, from which the monitoring agent 13 gathers data used for determining location of the monitored device 12. A monitored user operates the monitored device 12 with the monitoring agent 13 active.


Referring to FIG. 2, a method 100 for controlling communication device use is shown. The method 100 is described with reference to the components shown in the system 10 of FIG. 1, including the monitoring manager 20 and monitoring agent 13, which are preferably configured for performing the method 100 and include or have access to suitable non-transitory data storage including instructions for performing the method 100. The method 100 may alternatively be performed by the monitoring agent 13 alone, the monitoring manager 20 alone, or via other suitable systems and devices. The method 100 is not limited to the components shown in FIG. 1 which are merely exemplary.


In a step 102, the monitoring manager 20 receives from a first user (hereinafter “monitoring user”) an indication of a schedule of required check-in communications, the schedule corresponding to a second user (hereinafter “monitored user”). The monitoring user can correspond for example to a parent, and the monitored user can correspond to a child of the parent for whom the parent desires to control or limit mobile device use. The monitoring user can provide the indication via the overseeing user application 28 using a client device 16. The indication can be provided in the form of a request to enable or disable use by the monitored user of one or more particular applications and/or one or more particular functional components of the monitored device 12 based on the whether a check-in communication is received from the monitored user. The monitoring manager 20 can store check-in scheduling requirements provided via the overseeing user application 28 in the user datastore 34.


A scheduled check-in can be time based. For example the monitoring manager 20 can implement a timer that counts down from the most recently received check-in to determine a time for a subsequent required check-in, for example two hours from the most recent check-in. Alternatively, a user can be required to check-in at particular times (e.g. 4:00 pm, 5:15 pm, and 8:00 pm). The monitoring user can alternatively specify scheduled check-ins to be location based. For example, the monitored user can indicate that the monitoring user is required to check-in at each new location they arrive at, for example as determined by the monitoring agent 13 via the LDS 15 on the monitored device 12 or by the mapping engine 24 of the monitoring manager 20 via a PDE 45. Alternatively, check-in requirements can be both time and location based. For example, based on a particular scheduling requirement provided by monitoring parent via the overseeing user application 28, the monitoring agent 13 can initiate a timer as soon as a monitored child carrying the monitored device 12 is determined to have left her school's grounds. The monitored child is required to check-in before the timer runs out to avoid one or more functional components and applications of the monitored device 12 being disabled by the monitoring agent 13 or monitoring manager 20.


A functional component is a hardware or software component of the monitored device 12 which enables a particular functionality such as electronic messaging, photo messaging, telephone communication, internet usage, camera usage, video camera usage, application execution, access to a graphic user interface, or other device feature. An application can include for example a gaming application, a social networking application, a video playing application, or any application executable using the monitored device 12.


In a step 104 of the method 100, a determination is made of whether a check-in communication has been initiated by the monitored user pursuant to the prescribed schedule. The monitoring agent 13 can be used by the monitored user (e.g. a monitored child) to initiate the check-in. The monitoring agent 13 facilitates packaging and sending information from the monitored user to the monitoring user (e.g. a parent), which information can include for example the monitored user's location and a message from the monitored user indicating what the monitored user is doing (e.g. practicing violin with her classmate). The monitoring agent 13 permits a user to perform the check-in via a user interface 17 where details of the monitored user's activities can be entered. The monitoring agent 13 sends the check-in communication to the monitoring manager 20, and the monitoring manager 20 forwards the check-in communication or renders the check-in communication accessible to the client device 16 of the monitoring user via suitable protocol. Alternatively, the monitoring agent 13 transmits the check-in communication directly to the monitoring user via suitable protocol and provides notification of the check-in communication to the monitoring manager. Suitable protocols can include for example SMS, email, phone or communication via the overseeing user application 28.


In an alternative implementation, the monitoring agent 13 determines whether a check-in communication has been initiated through other means. For example, the monitoring agent 13 can monitor outgoing phone calls and text messages on the monitored device 12 to determine if the monitored user is checking in with the monitoring user. For example, the monitoring agent 13 can monitor a datastore 21 of outgoing SMS, email, and phone communications on the monitored device 12.


In another alternative implementation, an application such as the overseeing user application 28 executed on the monitoring user's client device 16 can monitor the client device 16 for evidence of communication from the monitored user. For example, the monitoring agent 28 can monitor incoming phone calls and text messages on the client device 16 to determine if the monitored user is checking in with the monitoring user.


In another alternative implementation, the monitoring manager 20 can interface with an application program interface (“API”) 49 enabled by a telecommunication carrier providing network service to the monitoring or monitored user to monitor for evidence of communication from the monitored user to the monitoring user, which communication can be initiated without the monitoring agent 13 or monitoring manager 20. For example, the monitoring manger 20 can enable a carrier integration application 38 integrated with the telecommunication carrier infrastructure to monitor phone calls and text messages at a network level in order to determine whether the monitored user is checking in with the monitoring user.


Referring further to FIG. 2, if a check-in communication is determined not to have been initiated pursuant to the prescribed schedule in step 104, one or more applications and functional components of the monitored device 12 are disabled (step 106). The monitoring agent 13 residing on the monitored device 12 can for example lock features of the monitored device. Alternatively, a lock can be initiated by the carrier integration application 36 integrated with the telecommunication carrier infrastructure via the carrier API 49. For example, the carrier interface application 36 can provide instructions via the carrier API 49 to lock device features at a network level based on a determination by the enablement engine 22. A notification of the lock can be provided by the monitoring agent 13 via the device user interface 17. An example notification message 62 on a display 60 of a monitored device 12 is shown in FIG. 7A which reads “Select device features have been locked since you failed to check-in with mom. Call mom to re-enable locked features.”


If a check-in communication is determined to be initiated pursuant to the schedule in step 104, one or more applications and functional components of the monitored device 12 are enabled (step 108) if not already enabled. Alternatively, step 108 can be omitted, and once an application or functional component is disabled based on a failure to check-in, subsequent check-in communications do not function to re-enable such application or functional component. In such case the step 104 repeats itself until it is determined that a check-in communication has not been initiated pursuant to a prescribed schedule. For example, a late check-in can be insufficient to enable the one or more applications and functional components.


The method 100 facilitates monitoring of users such as children by other users such as their parents. The method 100 through incentivizing enables monitoring users to determine whether those under their care are safe and to determine their location and what they are doing.


Referring to FIG. 3, a method 200 for controlling communication device use is shown. The method 200 is described with reference to the components shown in the system 10 of FIG. 1, including the monitoring manager 20 and monitoring agent 13, which are preferably configured for performing the method 200 and include or have access to suitable non-transitory data storage including instructions for performing the method 200. The method may alternatively be performed by the monitoring agent 13 alone, the monitoring manager 20 alone, or via other suitable systems and devices. The method 200 is not limited to the components shown in FIG. 1 which are merely exemplary.


In a step 202, the monitoring manager 20 receives from a first user (hereinafter “monitoring user”) an indication of a required state of a mobile device corresponding to a second user (hereinafter “monitored user”). The monitoring user can correspond for example to a parent, and the monitored user can correspond to a child of the parent for whom the parent desires to control or limit mobile device use. The monitoring user can provide the indication via the overseeing user application 28 using a client device 16. The indication can be provided in the form of a request to enable or disable the use by the monitored user of one or more particular applications and/or one or more particular functional components of the monitored device 12 based on the whether the current state of the mobile device is inconsistent with the required state. The monitoring manager 20 can maintain store requirements provided via the overseeing user application 28 in the user datastore 34.


The indication of the state can include an indication of a minimum battery charge of the monitored device 12. For example, a parent may want to be certain that her child carrying a mobile monitored device 12 is contactable, in which case the mobile device should have sufficient battery charge to remain operable. The indication of the state can alternatively include a requirement that a particular functional component such as a GPS receiver or WiFi protocol transceiver be on and enabled on the monitored device 12. For example, a parent may want to include such requirement to be certain that applications such as the monitoring agent 13 which can use GPS or WiFi protocol for tracking the location of their child remain operable.


It is determined in a step 204 if the current state of the monitored device 12 is consistent with the required state. The current state is consistent with the required state for example if a battery charge of the monitored device 12 is at a level greater than a particular required minimum charge. In another example, the current state is consistent with the required state if a GPS receiver or WiFi transceiver of the monitored device 12 is enabled. In yet another example, the current state is consistent with the required state if a phone ringer or other audible or vibratory notifier of an incoming communication of the monitored device 12 is enabled.


If the current state is determined to be inconsistent with the required state, for example the battery charge is at a level less than an indicated minimum or the GPS receiver, WiFi transceiver, or phone ringer is disabled, one or more application and/or one or more functional components of the monitored device 12 are disabled (step 206). One or both of the monitoring agent 13 and the monitoring manager 20 can initiate a lock to disable an application or functional component of the monitored device 12. A notification of the lock can be provided by the monitoring agent 13 via the device user interface 17. An example notification message 64 on the display 60 of the monitored device 12 is shown in FIG. 7B which reads “Select device features have been locked since your battery charge is less than 15%. Charge your device to re-enable locked features.” If the current state is determined to be consistent with the required state, one or more applications and/or one or more functional components are enabled if not already enabled (step 208) and the method returns to step 204 after a particular period of time Δt (step 210) to again determine the current state. Alternatively, step 208 can be omitted, wherein once an application or functional component is disabled in step 206 the process ends, and from step 204 the method skips to step 210 if a current state is determined to be consistent with a required state.


Referring to FIG. 4, a method 300 for controlling communication device use is shown. The method 300 is described with reference to the components shown in the system 10 of FIG. 1, including the monitoring manager 20 and monitoring agent 13, which are preferably configured for performing the method 300 and include or have access to suitable non-transitory data storage including instructions for performing the method 300. The method 300 may alternatively be performed by the monitoring agent 13 alone, the monitoring manager 20 alone, or via other suitable systems and devices. The method 300 is not limited to the components shown in FIG. 1 which are merely exemplary.


In a step 302, the monitoring manager 20 receives from a first user (hereinafter “monitoring user”) an indication of maximum allowed use of a monitored device 12 corresponding to a second user (hereinafter “monitored user”). The monitoring user can correspond for example to a parent, and the monitored user can correspond to a child of the parent for whom the parent desires to control or limit mobile device use. The monitoring user can provide the indication via the overseeing user application 28 using a client device 16. The indication can be provided in the form of a request to enable or disable the use by the monitored user of one or more particular applications and/or one or more particular functional components of the monitored device 12 based on the amount of use of particular applications or functional components of the monitored device 12. The monitoring manager 20 can store indications of maximum allowed use provided via the overseeing user application 28 in the user datastore 34.


The maximum allowed use can correspond to maximum allowed communication use such as a maximum allowed number of transmitted Short Message Service (SMS) messages and maximum quantity or duration of phone use. Alternatively, the maximum allowed use can correspond to a maximum allowed use of one or more applications such as gaming or social networking applications. A parent for example may want to limit their child's transmitted text messages to 100 per day or limit use by their child of one or more gaming applications to 2 hours a day.


An amount of use of the at least one device is determined in a step 304, for example the number of transmitted Short Message Service (SMS) messages or quantity or duration of phone use. If the amount of use is less than or equal to the maximum allowed use, the method returns to step 304 after a particular period of time Δt (step 306) to again determine the amount of use. If the determined amount of use is greater than the maximum allowed use, one or more applications and/or one or more functional components of the monitored device 12 are disabled (step 308). One or both of the monitoring agent 13 and the monitoring manager 20 can initiate a lock to disable an application or functional component of the monitored device 12. The monitoring agent 13 residing on the monitored device 12 can for example lock features of the mobile device. Alternatively, a lock can be initiated by the carrier integration application 38 integrated with the telecommunication carrier infrastructure via the carrier API 49. For example, the carrier integration application 38 can provide instructions to the carrier API 49 to lock phone features at a network level. A notification of the lock can be provided by the monitoring agent 13 via the device user interface 17. An example notification message 66 on the display 60 of the monitored device 12 is shown in FIG. 7C which reads “Select device features have been locked since transmitted SMS messages have exceeded 50 today.”


The monitoring manager 20 can further receive from the monitoring user indications of exceptions including for example white-listed contacts or applications. Communications with a contact indicated as an exception are not used in determining the amount of use of the monitored device 12 or in determining whether use has exceeded the maximum allowed use. For example, a parent may not want to discourage communication with their child's grandparent, so the grandparent can be indicated as an exception. Executed applications indicated as exceptions are not counted in determining the amount of use or in determining whether use has exceeded the maximum allowed use. For example, a parent may want to encourage use of certain educational applications, so such educational applications can be indicated as exceptions.


Referring to FIG. 5, a method 400 for controlling communication device use is shown. The method 400 is described with reference to the components shown in the system 10 of FIG. 1, including the monitoring manager 20 and monitoring agent 13, which are preferably configured for performing the method 400 and include or have access to suitable non-transitory data storage including instructions for performing the method 400. The method 400 may alternatively be performed by the monitoring agent 13 alone, the monitoring manager 20 alone, or via other suitable systems and devices. The method 400 is not limited to the components shown in FIG. 1 which are merely exemplary.


In a step 402, the monitoring manager 20 receives from a first user (hereinafter “monitoring user”) an indication of a geographic area. In a step 404, the monitoring manager 20 receives an indication from the monitoring user of a schedule corresponding to one or more times at which a particular second user (hereinafter “monitored user”) is required to be present at the geographic area. The indication of the geographic area can correspond to an address, a geographic coordinate, a name corresponding to a particular location, or any suitable description of a geographic area.


The monitoring user can provide the indications via the overseeing user application 28 using a client device 16. The indications can be provided in the form of a request to enable or disable the use by the monitored user of one or more particular applications and/or one or more particular functional components of the monitored device 12 based on failure of the monitored user to arrive a particular geographic area at a particular time. The monitoring manager 20 can store indications provided via the overseeing user application 28 in the user datastore 34.


In a step 406, location information of the monitored device 12 corresponding to the monitored user is received. Location information can be received by the monitoring agent 13 and/or the monitoring manager 20 via the LDS 15, via a network accessible position determining entity (PDE) 45, or via other suitable source. In a step 408, it is determined whether the location information indicates that the monitored user is present at the geographic area at a time required by the schedule provided by the monitoring user. The determination can be made by the monitoring manager 20 for example via the mapping engine 24 or via the monitoring agent 13. If it is determined that the monitored user is not present as required by the schedule, one or more applications and/or one or more functional components of the monitored device 12 are disabled (step 410) if not already disabled. A notification that such applications or functional components are disabled can be provided by the monitoring agent 13 via the device user interface 17. An example notification message 68 on the display 60 of the monitored device 12 is shown in FIG. 7D which reads “Select device features have been locked since you arrived late to school today.”


If it is determined that the monitored user is present at the designated geographic area as required by the schedule, one or more applications and/or one or more functional components of the device are enabled (step 412) if not already enabled, and the process returns to step 406 after a period of time Δt (step 414). Accordingly, an incentive is provided for the monitored user to arrive at a particular location at a time designated by the monitoring user, and a disincentive is provided for the monitored user to arrive late to a particular location after a time designated by the monitoring user.


Alternatively, step 412 can be omitted, wherein once an application or functional component is disabled in step 410 the process ends, and from step 408 the method skips to step 414 if the monitored user is determined to be present at the designated geographic area pursuant to the indicated schedule. In such case, once an application or functional component is disabled based on the monitored user's failure to be present at a particular geographic area at a scheduled time, such application or functional component is not re-enabled based on the monitored user's presence at a particular location at a future time according to the indicated schedule.


By the method 400 a user can be reprimanded or rewarded with more or less restricted use of their mobile device. For example, a parent can provide an indication of a time required for their child to arrive at school in an effort to incentivize arriving on time to school, wherein if the child arrives to school on time a particular day, all functional components and applications on the child's mobile phone are enabled after the school day. If the child arrives late to school, one or more functional components and/or applications on the mobile phone can be disabled and remain disabled after the school day.


Two or more of the methods 100, 200, 300 and 400 can be operated concurrently in controlling use of a particular device. These methods can operate independently via the monitoring manager 20 and monitoring agent 13. For example, features of the monitored device 12 are unlocked if battery charge is above a particular threshold and locked if battery charge is below a particular threshold without regard to other behavior of the monitored user. Alternatively, criteria set forth for triggering disabling and enabling functional components and applications are combined into a system of multipliers in which a monitored user has a depletable reserve of unrestricted use of her monitored device 12. A value of the reserve can for example decay based on passage of time, based on use of the monitored device 12, or based on a determination of undesirable user behavior, for example failure to check-in with a monitoring user. The reserve can be replenished for example by the passing of time (e.g. a daily reset of the value of the reserve) or based on a determination of desirable user behavior (e.g. checking in with a monitoring user). The monitoring agent 13 can enable a user interface 17 to provide a monitored user a view of their current reserve value, an indication of past actions contributing to the rise and fall of the reserve value, and an indication of suggested actions which can most effectively increase the current reserve value to permit enablement of functional components or applications.


Referring to FIG. 6, a method 500 for controlling communication device use based on particular triggering conditions is shown. The method 500 is described with reference to the components shown in the system 10 of FIG. 1, including the monitoring manager 20 and monitoring agent 13, which are preferably configured for performing the method 100 and include or have access to suitable non-transitory data storage including instructions for performing the method 500. The method 500 may alternatively be performed by the monitoring agent alone, or the monitoring manager via other suitable systems and devices. The method 500 is not limited to the components shown in FIG. 1 which are merely exemplary.


In a step 502, the monitoring manager 20 establishes a value corresponding to a particular user of a monitored device 12. In a step 504, the monitoring manager 20 receives an indication of one or more triggering conditions of the particular user corresponding to the monitored device 12, the one or more triggering conditions being at least one of enabled by the monitored device 12 and measurable by the monitored device 12. The indications of triggering conditions can be provided for example by a parent of the particular user via the overseeing user application 28. The established values and the indications of triggering conditions can be stored in the user datastore 34.


In a step 506, it is determined whether one or more of the triggering conditions have been met by the particular user via the monitored device 12. A triggering condition can correspond to an arguably undesirable behavior, for example a failure to perform a check-in communication according to a particular schedule using the monitored device 12, a failure to maintain a battery charge of the monitored device 12 above a particular threshold level, performing communication of quantity or duration greater than a particular maximum allowed threshold, and not being present at a particular geographic area at a particular specified time. Alternatively, the triggering condition can correspond to an arguably desirable behavior, for example performing a check-in communication according to a particular schedule using the mobile device, charging a battery to a particular threshold level, performing communication of quantity or duration less than a particular maximum allowed threshold over a period of time, and being present at a particular geographic area at a particular specified time. The particulars of the triggering conditions, including for example a schedule for performing check-ins, a threshold battery charge, an allowed communication threshold, and a schedule for being present at particular geographic areas, can be provided by a monitoring user such as a parent of the particular user via the overseeing user application 28.


If a triggering condition is not met, step 506 is repeated after a period of time Δt (step 508). If a triggering condition is met, the established value is modified (step 510). For example, the value can be decreased if a first triggering condition is met and the value can be increased if a second triggering condition is met, wherein for example the first triggering condition corresponds to undesirable behavior, and the second triggering condition corresponds to a desirable behavior. It is determined in a step 512 if the value crosses a particular threshold from a first direction, and if not, it is determined in a step 516 if the value crosses a particular threshold from a second direction. If it is determined in step 512 that the value crosses a particular threshold from the first direction, one or more particular applications and/or one or more functional components of the monitored device 12 are disabled (step 514), if not already disabled. The threshold can correspond for example to a numeric indicator such as 0 wherein the one or more applications and functional components are disabled responsive to the value dropping from a value above 0 to a value equal to or less than 0, the first direction being from positive value to zero value or from positive value to negative value. If it is determined in step 516 that the value crosses another particular threshold in a second direction, one or more applications and/or one or more functional components of the device 12 are enabled (step 518), if not already enabled. The other particular threshold can correspond for example to a numeric indicator such as 0 or other numeric count wherein the one or more applications and functional components are enabled responsive to the value increasing from a value less than or equal to 0 to a value greater than 0, the second direction being from negative or zero value to positive value. After enabling or disabling the one or more applications and functional components, the process returns to step 506 after a period of time Δt (step 508). The thresholds in steps 512 and 516 need not be of the same value. Further, steps 516 and 518 can be omitted, for example based on preference indication of a monitoring user, in which case step 512 skips to step 508 if the particular value does not cross the threshold, and the method ends after the one or more applications and functional components are disabled in step 514.


Different triggering conditions can be weighted differently, wherein when a particular triggering condition is met, a reserve value is modified based on the particular triggering conditions weighting. A monitoring user via the overseeing user application 28 is enabled to set and adjust the weights based on preference. For example failure to check-in may result in a 5 count decrease in reserve value, whereas failure to maintain battery charge may result in a 2 count decrease in reserve value.


Referring to FIG. 7E, an example notification message 70 indicating that one or more applications and functional components are disabled pursuant to the method 500 is shown on the display 60 of the mobile device 12. The message 70 further indicates behavior contributing to the disablement. The message reads “Select device features have been locked based on recent behavior including: 1. failure to check in, 2. arriving late to home, 3. excess SMS use.” Referring to FIG. 7F, an example notification message 72 indicating that one or more applications and functional components are disabled pursuant to the method 500 is shown on the display 60 of the mobile device 12. The message 72 further indicates behavior which can contribute to re-enablement of the applications or functional components. The message reads “Select device features have been locked based on recent behavior. Check in with Mom and charge device to unlock features.” Referring to FIG. 7G, an example notification message 74 indicating a monitored user's current reserve value pursuant to the method 500 is shown on the display 60 of the mobile device 12. The message 74 further indicates behavior which can contribute to an increase in the reserve value. The message reads “Your device reserve value is 12 points. Select features are locked when reserve value reaches 0. Arrive at school by 8:00 am to increase reserve value.”


Hooks are provided to allow for other applications or systems to call into the monitoring manager 20 or monitoring agent 13 to provide an indication of activity of the monitored user to the monitoring manager 20 to control functional components or applications or modify a value tied to control of functional components or applications on a monitored device 12. For example, educational games and other applications and systems, represented by contributing systems 47 and app 19 in FIG. 1, can be integrated with APIs enabled by the monitoring manager 20 or monitoring agent 13 to permit a monitored user to be rewarded for example for time spent or achievements earned using a particular application or participating in a particular activity.


Contributing systems 47 can include for example school information systems which can correlate a monitored child's completion of homework, grades and overall school performance with enablement of applications or functional components on the child's monitored device 12. The contributing systems 47 can further correspond for example to classroom teachers, babysitters, caregivers or others who look to incentivize desirable behavior with unrestricted or less restricted device use. The contributing systems 47 can further correspond for example to banking systems, wherein a monitored user is rewarded with unrestricted or less restricted device use or value corresponding to unrestricted or less restricted device use based on maintaining a particular bank balance. Contributing systems 47 or applications 19 corresponding to behaviors or activities of a monitored user can be selected by a monitoring user to tie into enablement of functional components and applications of a monitored device 12. The contributing systems 47 and applications 19 can provide indication of activity to the monitoring manager 20 or monitoring agent 13, wherein operability of functional components or applications or a value tied to such operability is controlled at least in part by such indication of activity.


Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. Methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor.


While embodiments have been described in detail above, these embodiments are non-limiting and should be considered as merely exemplary. Modifications and extensions may be developed, and all such modifications are deemed to be within the scope defined by the appended claims.

Claims
  • 1. A computer implemented method of controlling device use, the method comprising: receiving from a first user an indication of a maximum allowed use of at least one device corresponding to a second user;monitoring an amount of use of the of the at least one device;determining at a plurality of times that the monitored amount of use is greater than the maximum allowed use;modifying a value based at least on an aggregating of the determining at the plurality of times that the monitored amount of use is greater than the maximum allowed use;determining when the value crosses a particular threshold; andanddisabling at least one of a particular application or a particular functional component of the at least one device responsive to the value crossing the particular threshold.
  • 2. The computer implemented method of claim 1, wherein the maximum allowed use comprises a maximum allowed communication use.
  • 3. The computer implemented method of claim 2, wherein the maximum allowed use comprises a maximum allowed number of transmitted Short Message Service (SMS) messages.
  • 4. The computer implemented method of claim 2, wherein the maximum allowed use comprises a maximum allowed amount of phone use.
  • 5. The computer implemented method of claim 2, further comprising receiving an indication of at least one contact corresponding to an exception to the maximum allowed use, wherein communications with the at least one contact are not used in determining the amount of use of the at least one device.
  • 6. The computer implemented method of claim 1, wherein the maximum allowed use comprises a maximum allowed use of at least one certain application.
  • 7. The computer implemented method of claim 6, further comprising receiving an indication of at least one other application corresponding to an exception to the maximum allowed use, wherein use of the at least one other application is not considered in determining the amount of use of the at least one device.
  • 8. A computer implemented method of controlling device use, the method comprising: establishing a value corresponding to a particular user of a device;receiving an indication of at least one triggering condition of the particular user of the device, the at least one triggering condition comprising an amount of use by the particular user of the device being greater than a first threshold;determining at a plurality of times that the at least one triggering condition has been met by the particular user via the device;modifying the value based on an aggregating of the determining that the at least one triggering condition has been met at the plurality of times;determining when the value crosses a second threshold; anddisabling at least one of an application or a functional component of the device responsive to the value crossing the second threshold.
  • 9. The computer implemented method of claim 8, wherein the at least one triggering condition comprises a performing of communication of quantity greater than the first threshold using the device.
  • 10. The computer implemented method of claim 8, wherein the at least one triggering condition comprises a performing of communication of at least one of quantity and duration greater than the first threshold.
  • 11. A mobile communication device comprising a processor-enabled monitoring agent configured for: receiving an indication of a maximum allowed use of the mobile communication device;monitoring an amount of use of the of the mobile communication device;determining at a plurality of times that the monitored amount of use is greater than the maximum allowed use;modifying a value based at least on an aggregating of the determining at the plurality of times that the monitored amount of use is greater than the maximum allowed use;determining when the value crosses a particular threshold; anddisabling at least one of an application or a functional component of the mobile communication device responsive to the value crossing the particular threshold.
  • 12. The mobile communication device of claim 11, the processor-enabled monitoring agent further configured for: monitoring communications of the mobile communication device; andmodifying the value based on the communications exceeding at least one of a particular quantity or a particular duration.
  • 13. The mobile communication device of claim 11, the processor-enabled monitoring agent further configured for: monitoring communications of the mobile communication device; andmodifying the value based on the communications exceeding a particular duration.
CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No. 15/412,439, filed Jan. 23, 2017, which is a divisional of U.S. patent application Ser. No. 13/723,119, filed Dec. 20, 2012 (now U.S. Pat. No. 9,554,190) which applications are incorporated by reference as if fully set forth.

US Referenced Citations (269)
Number Name Date Kind
3778809 Hawes Dec 1973 A
4956825 Wilts et al. Sep 1990 A
5434562 Reardon Jul 1995 A
5559862 Bhagat et al. Sep 1996 A
5673691 Abrams Oct 1997 A
5833479 Talbot Oct 1998 A
5882258 Kelly et al. Mar 1999 A
5907831 Lotvin May 1999 A
5973683 Cragun et al. Oct 1999 A
6011973 Valentine et al. Jan 2000 A
6023692 Nichols Feb 2000 A
6151507 Laiho et al. Nov 2000 A
6161008 Lee et al. Dec 2000 A
6587835 Treyz et al. Jul 2003 B1
6690940 Brown et al. Feb 2004 B1
6782266 Baer et al. Aug 2004 B2
7178720 Strubbe Feb 2007 B1
7181229 Singh et al. Feb 2007 B2
7257367 Etuk et al. Aug 2007 B2
7606772 Flinn et al. Oct 2009 B2
7729945 Katz et al. Jun 2010 B1
7849502 Bloch et al. Dec 2010 B1
7869792 Zhou et al. Jan 2011 B1
7899438 Baker et al. Mar 2011 B2
8010037 Bannwolf Aug 2011 B2
8073907 Roumeliotis et al. Dec 2011 B2
8095413 Beaven Jan 2012 B1
8121879 Cohen Feb 2012 B1
8135392 Marcellino Mar 2012 B2
8145240 Roumeliotis et al. Mar 2012 B2
8175642 Shah May 2012 B2
8193982 Kupfer Jun 2012 B2
8229421 Hotes et al. Jul 2012 B2
8244236 Roumeliotis et al. Aug 2012 B2
8270933 Riemer et al. Sep 2012 B2
8280438 Barbera Oct 2012 B2
8315905 Adair Nov 2012 B1
8348555 Rosen Feb 2013 B2
8384555 Rosen Feb 2013 B2
8401521 Bennett Mar 2013 B2
8412154 Leemet et al. Apr 2013 B1
8417268 Halferty et al. Apr 2013 B1
8447279 Peng et al. May 2013 B1
8527013 Guba et al. Sep 2013 B2
8620354 Beasley Dec 2013 B2
8621075 Luna Dec 2013 B2
8635708 Mahan Jan 2014 B2
8731530 Breed et al. May 2014 B1
8738688 Myers May 2014 B2
8761821 Tibbitts et al. Jun 2014 B2
8825035 Moton Sep 2014 B2
8849095 Hoofien Sep 2014 B2
8971927 Zhou et al. Mar 2015 B2
8982781 Starr Mar 2015 B2
9019068 Varoglu Apr 2015 B2
9042872 Breed et al. May 2015 B1
9124703 Tadayon Sep 2015 B2
20010023198 Muto Sep 2001 A1
20010029196 Wakamatsu Oct 2001 A1
20020012894 Becker Jan 2002 A1
20020016189 Sheynblat et al. Feb 2002 A1
20020049806 Gatz et al. Apr 2002 A1
20020116266 Marshall Aug 2002 A1
20020147037 Kwon Oct 2002 A1
20020169539 Menard et al. Nov 2002 A1
20020177475 Park Nov 2002 A1
20020178046 Lawrence Nov 2002 A1
20030005306 Hunt et al. Jan 2003 A1
20030064788 Walker et al. Apr 2003 A1
20030082508 Barney May 2003 A1
20030126267 Gutta et al. Jul 2003 A1
20030139175 Kim Jul 2003 A1
20030158609 Chiu Aug 2003 A1
20030211889 Walker et al. Nov 2003 A1
20030216960 Porstrel Nov 2003 A1
20040024569 Camillo Feb 2004 A1
20040030599 Sie et al. Feb 2004 A1
20040039624 Ikezawa et al. Feb 2004 A1
20040111479 Borden et al. Jun 2004 A1
20040161085 Horne Aug 2004 A1
20040166878 Erskine et al. Aug 2004 A1
20040186776 Llach Sep 2004 A1
20040219493 Phillips Nov 2004 A1
20040267607 Maddux Dec 2004 A1
20050003895 Nara Jan 2005 A1
20050039206 Opdyche Feb 2005 A1
20050096009 Ackley May 2005 A1
20050096030 Boyd May 2005 A1
20050195193 Lehman Sep 2005 A1
20050243771 Hardy et al. Nov 2005 A1
20050282559 Erskine et al. Dec 2005 A1
20050287502 Southard Dec 2005 A1
20060009234 Freer Jan 2006 A1
20060085547 Cormier Apr 2006 A1
20060089878 Roberts et al. Apr 2006 A1
20060117263 Locke Jun 2006 A1
20060135120 Likourezos Jun 2006 A1
20060184792 Berlin Aug 2006 A1
20060200435 Flinn et al. Sep 2006 A1
20060270476 Denkewicz Nov 2006 A1
20060276180 Henry Dec 2006 A1
20070039624 Roberts et al. Feb 2007 A1
20070088610 Chen Apr 2007 A1
20070100595 Earles et al. May 2007 A1
20070142068 Matsuo Jun 2007 A1
20070150567 Lamparello et al. Jun 2007 A1
20070203872 Flinn et al. Aug 2007 A1
20070208802 Barman Sep 2007 A1
20070232340 Yamauchi et al. Oct 2007 A1
20070243852 Gibbs Oct 2007 A1
20070282678 Dendi et al. Dec 2007 A1
20080005325 Wynn et al. Jan 2008 A1
20080066020 Boss et al. Mar 2008 A1
20080070588 Morin et al. Mar 2008 A1
20080077489 Gilley et al. Mar 2008 A1
20080146211 Mikan et al. Jun 2008 A1
20080146250 Aaron Jun 2008 A1
20080172317 Deibert et al. Jul 2008 A1
20080177834 Gruhl et al. Jul 2008 A1
20080183560 Kaplan et al. Jul 2008 A1
20080199199 Kato et al. Aug 2008 A1
20080201469 Reasor Aug 2008 A1
20080242311 Craine et al. Oct 2008 A1
20080246605 Pfeffer et al. Oct 2008 A1
20080270038 Partovi Oct 2008 A1
20080307243 Lee Dec 2008 A1
20090017750 Marcinkiewicz Jan 2009 A1
20090038005 Howarth Feb 2009 A1
20090055938 Samuel Feb 2009 A1
20090064316 Liao et al. Mar 2009 A1
20090089876 Finamore et al. Apr 2009 A1
20090098914 Martin-Cocher et al. Apr 2009 A1
20090125499 Cross et al. May 2009 A1
20090149203 Backholm et al. Jun 2009 A1
20090181356 Dasgupta Jul 2009 A1
20090203352 Fordon et al. Aug 2009 A1
20090204471 Elenbaas et al. Aug 2009 A1
20090251282 Fitzgerald et al. Oct 2009 A1
20090275367 Reinisch et al. Nov 2009 A1
20090286218 Johnson et al. Nov 2009 A1
20090295562 Shuster Dec 2009 A1
20090296904 Brewer et al. Dec 2009 A1
20090298019 Rogan et al. Dec 2009 A1
20100028844 Wiseman Feb 2010 A1
20100042493 Nino et al. Feb 2010 A1
20100058446 Thwaites Mar 2010 A1
20100077444 Forristal Mar 2010 A1
20100100618 Kuhlke et al. Apr 2010 A1
20100116884 Alderucci et al. May 2010 A1
20100125028 Heppert May 2010 A1
20100145976 Higgins et al. Jun 2010 A1
20100161369 Farrell et al. Jun 2010 A1
20100211694 Razmov et al. Aug 2010 A1
20100211887 Woolcombe Aug 2010 A1
20100216509 Riemer et al. Aug 2010 A1
20100235223 Lyman Sep 2010 A1
20100240399 Roumeliotis et al. Sep 2010 A1
20100241496 Gupta et al. Sep 2010 A1
20100246797 Chavez et al. Sep 2010 A1
20100250352 Moore Sep 2010 A1
20100268768 Kurtenbach et al. Oct 2010 A1
20100285871 Shah et al. Nov 2010 A1
20100306138 Hotes et al. Dec 2010 A1
20100317420 Hoffberg Dec 2010 A1
20100332233 Chen et al. Dec 2010 A1
20110029598 Arnold et al. Feb 2011 A1
20110047078 Ginter et al. Feb 2011 A1
20110070567 Linton Mar 2011 A1
20110092159 Park et al. Apr 2011 A1
20110124399 Dutilly et al. May 2011 A1
20110125844 Collier et al. May 2011 A1
20110145927 Hubner et al. Jun 2011 A1
20110218884 Kothari et al. Sep 2011 A1
20110228753 Polito et al. Sep 2011 A1
20110236872 Taylor Sep 2011 A1
20110244825 Ewell Oct 2011 A1
20110244837 Murata et al. Oct 2011 A1
20110250904 Valleta et al. Oct 2011 A1
20110252375 Chaudri Oct 2011 A1
20110302003 Shirish et al. Dec 2011 A1
20110302024 Gunawardana et al. Dec 2011 A1
20110320259 Roumeliotis et al. Dec 2011 A1
20120008526 Borghei Jan 2012 A1
20120036220 Dare et al. Feb 2012 A1
20120040761 Auterlo et al. Feb 2012 A1
20120047560 Underwood et al. Feb 2012 A1
20120058744 Felt et al. Mar 2012 A1
20120066088 Murset Mar 2012 A1
20120069131 Abelow Mar 2012 A1
20120072340 Amron Mar 2012 A1
20120084349 Lee et al. Apr 2012 A1
20120100866 Grossman et al. Apr 2012 A1
20120131161 Ferris et al. May 2012 A1
20120135705 Thaker May 2012 A1
20120143496 Chitre et al. Jun 2012 A1
20120151045 Anakata Jun 2012 A1
20120151046 Weiss Jun 2012 A1
20120151047 Hodges et al. Jun 2012 A1
20120151384 Stass Jun 2012 A1
20120157076 Choi Jun 2012 A1
20120166285 Shapiro et al. Jun 2012 A1
20120172027 Partheesh et al. Jul 2012 A1
20120172100 Colar et al. Jul 2012 A1
20120179767 Clarke et al. Jul 2012 A1
20120180135 Hodges Jul 2012 A1
20120202528 Roumeliotis et al. Aug 2012 A1
20120214472 Tadayon Aug 2012 A1
20120215328 Schmeizer Aug 2012 A1
20120215617 Shah et al. Aug 2012 A1
20120221877 Prabu Aug 2012 A1
20120233256 Shaham et al. Sep 2012 A1
20120237908 Fitzgerald et al. Sep 2012 A1
20120253918 Marois et al. Oct 2012 A1
20120254949 Mikkonen et al. Oct 2012 A1
20120260118 Jiang et al. Oct 2012 A1
20120271908 Luna Oct 2012 A1
20120280916 Xia et al. Nov 2012 A1
20120323990 Hayworth Dec 2012 A1
20120330702 Kowalski et al. Dec 2012 A1
20130040629 Sprigg et al. Feb 2013 A1
20130054674 Myers Feb 2013 A1
20130055267 Noro Feb 2013 A1
20130084847 Tibbitts Apr 2013 A1
20130091453 Kotler et al. Apr 2013 A1
20130102286 Toksvig et al. Apr 2013 A1
20130104246 Bear et al. Apr 2013 A1
20130111462 Umansky et al. May 2013 A1
20130111510 Baker et al. May 2013 A1
20130143512 Hernandez et al. Jun 2013 A1
20130143528 Randazzo et al. Jun 2013 A1
20130145007 Randazzo et al. Jun 2013 A1
20130150004 Rosen Jun 2013 A1
20130151628 Catalano et al. Jun 2013 A1
20130177006 Baek et al. Jul 2013 A1
20130198272 Shionoya Aug 2013 A1
20130198296 Roy et al. Aug 2013 A1
20130225151 King et al. Aug 2013 A1
20130282889 Tito Oct 2013 A1
20130303143 Schrader Nov 2013 A1
20130305384 Weiss Nov 2013 A1
20130316746 Miller et al. Nov 2013 A1
20130332886 Cranfil et al. Dec 2013 A1
20130339345 Soto et al. Dec 2013 A1
20130346333 Hassler et al. Dec 2013 A1
20140057610 Olincy et al. Feb 2014 A1
20140082065 Anakata et al. Mar 2014 A1
20140099921 Weiss Apr 2014 A1
20140108649 Barton et al. Apr 2014 A1
20140148192 Hodges et al. May 2014 A1
20140155094 Zises Jun 2014 A1
20140179261 Riggs Jun 2014 A1
20140180438 Hodges et al. Jun 2014 A1
20140187219 Yang Jul 2014 A1
20140194095 Wynne et al. Jul 2014 A1
20140258357 Singh et al. Sep 2014 A1
20140310327 Yip et al. Oct 2014 A1
20140310365 Sample et al. Oct 2014 A1
20140310403 Weiss et al. Oct 2014 A1
20140338006 Grkov et al. Nov 2014 A1
20140364153 Ren Dec 2014 A1
20140370857 Bovis Dec 2014 A1
20150040246 Yuen et al. Feb 2015 A1
20150079965 Mullins Mar 2015 A1
20150188777 Frost Jul 2015 A1
20150227752 Anakata Aug 2015 A1
20150350410 Weiss et al. Dec 2015 A1
20160014262 Hodges Jan 2016 A1
20170135045 Hodges May 2017 A1
20190028585 Weiss et al. Jan 2019 A1
Foreign Referenced Citations (3)
Number Date Country
2863439 Jun 2005 FR
1770969 Sep 2009 GB
WO2011137279 Nov 2011 WO
Non-Patent Literature Citations (3)
Entry
Loss leader, from Wikipedia, downloaded from https://en.wikipedia.org/wiki/Loss_leader on Aug. 25, 2015.
Coupon, from Wikipedia, downloaded from https://en.wikipedia.org/wiki/Coupon on Mar. 9, 2015.
Kohavi, “Emerging Trends in Business Analytics”, Communications of the ACM, Aug. 2002, vol. 45, No. 8, pp. 45-48.
Related Publications (1)
Number Date Country
20190320392 A1 Oct 2019 US
Divisions (1)
Number Date Country
Parent 13723119 Dec 2012 US
Child 15412439 US
Continuations (1)
Number Date Country
Parent 15412439 Jan 2017 US
Child 16453175 US