Configuring context-based restrictions for computing devices

The remote configuration and control of satellite equipment by mode controller equipment solves the problem of managing the use of mobile devices in a specific context, realizes effective restrictions and management of equipment use, and improves the reliability and security of equipment.

CN119026157APending Publication Date: 2024-11-26APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411249937.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-04-29
Filing Date
2020-04-30
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The prior art is difficult to effectively manage and limit the use of mobile devices, especially in specific contexts, such as when children are in school, it is difficult for parents to remotely control and restrict the use of their children's equipment, resulting in distraction and management difficulties.

Method used

With the mode controller device, parents can remotely configure and control the satellite device, limiting their use in a specific context, such as disabling all functions except basic functions during school time periods, providing a mode exit process to prevent accidental unlocking, and through Server devices transfer configuration data to manage multiple devices.

Benefits of technology

It realizes effective management of the use of children's equipment by parents, reduces management burden, improves the reliability and battery life of the equipment, reduces bandwidth and processor usage, and ensures the safety and availability of the equipment in restricted mode.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119026157A_ABST
    Figure CN119026157A_ABST
Patent Text Reader

Abstract

The subject matter of the application is to configure context-based restrictions for a computing device. In some implementations, a computing device may limit use of another computing device in certain contexts. For example, a parent may wish to use the parent's computing device to restrict their child from using the child's computing device while the child is going to school when the child should participate in some other activities. For example, the parent's controller device may be enabled to remotely configure and control the use of the satellite device without physical access to the satellite device. The parents may implement restrictions, licenses, or different policies that may manage, for example, the ability of satellite devices to communicate with other devices, perform various application functions, run any particular software, and manage their own settings.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with international application number PCT / US2020 / 030709, international application date April 30, 2020, application number 202080033778.6, and invention name “Configuring background-based restrictions for computing devices”, which entered the Chinese national phase on November 5, 2021. Technical Field

[0002] The present disclosure relates generally to operating computing devices, and particularly to remotely limiting usage of a device in a particular context. Background Art

[0003] Modern mobile devices often distract users during the day when users of such devices should be focusing on productive activities, such as working, studying, or engaging in some other productive activity. Summary of the invention

[0004] In some implementations, one computing device can restrict the use of another computing device in certain contexts. For example, a parent may wish to restrict the use of the parent's computing device by their child when the child is in school and when the child should be participating in some other activity. For example, the parent's controller device can be enabled to remotely configure and control the use of a satellite device without physically accessing the satellite device. The parent can implement restrictions, permissions, or different policies that govern, for example, the satellite device's ability to communicate with other devices, perform various application functions, run any specific software, and manage its own settings.

[0005] Specific implementations provide at least the following advantages. Parents can remotely limit functions at a child's device without physically accessing the child's device. This facilitates parental management of the child's device use and reduces the burden of device management for parents, particularly because parents can create restricted mode configurations for multiple devices without configuring each device individually. Particular benefits also include a mode exit process that makes it obvious that a child is trying to exit restricted mode. This improves the effectiveness of restricted mode and reduces the parent's configuration burden, because if the mode exit process is cumbersome and will alert another person, the child is likely to avoid removing the restricted mode configuration. Parents are reminded of any functional usage at the child's device, thereby further improving reliability, because the child knows that circumvention attempts will be reported to the parents, so that the child may not make such attempts. The child's satellite device stays longer in restricted mode and therefore uses less battery power, bandwidth, and processor cycles. This also improves device quality and reliability, and also reduces the costs associated with bandwidth (e.g., data connection) usage and power usage. In addition, the satellite device can still perform certain functions when in restricted mode, such as emergency communications or contacting the child's parents, thereby further improving device availability.

[0006] The details of one or more specific implementations are set forth in the following drawings and detailed description. Other features, aspects, and potential advantages will be apparent in the detailed description and drawings, and in the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a block diagram of an exemplary system for configuring context-based restrictions for a computing device.

[0008] Figure 2 is a system interaction diagram for configuring restricted mode configurations for a computing device and transmitting those configurations via a server device.

[0009] Figure 3 is a system interaction diagram for configuring restricted mode configurations for a computing device and transmitting those configurations directly to the computing device.

[0010] Figure 4 A process for creating a restricted mode configuration for a computing device is shown.

[0011] Figure 5 is a calendar view that indicates various dates and times that a person can use to create restricted mode configurations for a computing device.

[0012] Figures 6a to 6c Several display stages of a satellite device configured with a restricted mode configuration are shown.

[0013] Figure 7is a system interaction diagram illustrating a trusted third party configuring a computing device with a restricted mode configuration.

[0014] Figure 8 is a flow chart illustrating another process used by a computing device to enforce context-based restrictions on itself.

[0015] Fig. 9 is a flow chart illustrating another process used by a computing device to determine whether a sender of restricted mode configurations is authorized to implement those configurations on the computing device.

[0016] Fig.10 It is achievable Figures 1 to 9 A block diagram of an exemplary computing device illustrating features and processes of the invention.

[0017] Like reference symbols in the various drawings indicate like elements. DETAILED DESCRIPTION

[0018] Figure 1 1 is a block diagram of an exemplary system 100 for configuring context-based restrictions for a computing device. In some embodiments, system 100 enables a person to remotely restrict the use of another person's device. The use of a computing device can be restricted in different ways to specific usage scenarios or contexts. For example, a parent may wish to configure a child's device for a restricted mode in certain contexts. A child may go to school during the day and carry a computing device (referred to herein as a "satellite device") with him to school. The parent can remotely configure the satellite device to be in a restricted mode, for example, which disables nearly all functionality of the satellite device until the child leaves school.

[0019] refer to Figure 1 In some embodiments, the system 100 may include a mode controller device 140, a satellite device 138, and a server device 110. Either of the mode controller device 140 and the satellite device 138 may be a laptop computer, a desktop computer, a smart phone, a tablet computer, a smart watch device, other wearable devices, or any other computing device. For example, the system 100 may be a restricted mode configuration system that provides an operator of the mode controller device 140 with the ability to remotely restrict the use of the satellite device 138 for a defined period of time using a network 120 (e.g., a local area network, a wide area network, the Internet, etc.) and a server device 110.

[0020] Restricted mode configurations (e.g., configurations based on time, geographic location, device environment / conditions, etc.) that may be specified by the user and any communications corresponding to those configurations may be encrypted in an end-to-end encrypted manner as described herein. In this way, the configuration data can only be accessed by devices associated with the user (e.g., and / or the child) and not by a server (e.g., server 110), thereby protecting user privacy.

[0021] A parent or guardian user may use the mode controller device 140 to generate a restricted mode configuration to manage a child's use of the satellite device 138 in a particular context. The restricted mode configuration may remotely restrict the use of the satellite device 138. For example, the restricted mode configuration may completely restrict the use of the satellite device 138 except for basic purposes (e.g., display time). The restricted mode configuration may limit or disable one or more functions or features of an application of the satellite device 138 (e.g., communication features). The restricted mode configuration may limit or disable device features of the satellite device 138 (e.g., volume / sound settings).

[0022] As used herein, "context" may refer to a specific location, a specific time, or a specific combination of location and time corresponding to a usage environment that affects how a device can be used. A specific location may correspond to a specific usage context. For example, a person is able to freely use a computing device at home, but may need to disable one or more features when in the office where he or she works. For example, a person may need to disable any audio output from the device to prevent others from being distracted. Similarly, a specific time may correspond to a specific usage context. For example, a child may be able to use the audio, video, and text features of a computing device at night, but may be prohibited from using any of the above features during school hours. In addition, a combination of location and time may also correspond to a specific context. For example, when on an airplane during a flight, a child may be able to use any audio or visual features of a computing device (e.g., to watch a movie), but may be prohibited from using communication features due to electronic interference problems that may be caused on the airplane. Similarly, a person may need to disable one or more audio or display features in a movie theater during a movie screening.

[0023] Mode controller device 140 can execute a management application 145 that a user (e.g., a parent) can use to generate a restricted mode configuration. Management application 145 can provide various interfaces or controls for parents to create a restricted mode configuration. Management application 145 can output a restricted mode configuration that includes a plurality of settings that restrict satellite device 138 according to parental preferences.

[0024] In some embodiments, a parent creates a restricted mode configuration at the mode controller device 140 (e.g., using the management application 145). The restricted mode configuration may include various restrictions, settings, and specific specifications. Any of these restrictions, settings, and specifications may change one or more default behaviors or capabilities of the satellite device. For example, a parent may wish to restrict the satellite device at certain times and / or certain locations. At those times or locations, a parent may want to completely disable the satellite device (e.g., when the child is in school). Therefore, a parent may use the management application 145 to generate a restricted mode configuration that restricts the satellite device from providing interactive features or responses to user interactions for a limited time (e.g., during the child's school hours). For example, a satellite device may apply a restricted mode configuration to a touch-sensitive display screen to disable the display screen. When the satellite device is in restricted mode, the display screen may stop responding to touch inputs. Parents may also include exceptions to any configured restrictions. For example, a parent may specify specific applications that can still operate even if the satellite device is in restricted mode. For example, in a school context, a child may need the ability to use a calculator application in math class. The restricted mode configuration may disable all functions on the satellite device 138, except for the calculator application for a time period defined for the child's math class.

[0025] In some embodiments, the restricted mode configuration may also specify a mode exit process. The user of the satellite device may follow the mode exit process to exit the restricted mode and return the satellite device to full functionality or default settings. Parents may configure the mode exit process when creating the restricted mode configuration. In some embodiments, the mode exit process may be designed to make it clear to bystanders that the user is trying to exit the restricted mode. In addition, attempts to exit the restricted mode may be recorded at the satellite device and reported to the controller device. For example, a child may attempt to exit the restricted mode using the mode exit process. The process may require the child's full attention for a specific period of time. The process may require a lot of interaction with the satellite device, which makes it clear to the observer (i.e., the teacher) that the child is trying to exit the restricted mode.

[0026] In some embodiments, the restricted mode configuration can be a data structure or structured data object that includes all parental desired restrictions, settings, or exceptions. The satellite device can be configured to evaluate the contents of the data structure. The satellite device can identify each restriction and implement the restriction on the relevant application or component of the satellite device.

[0027] In addition, parents can view updates about the restricted mode configuration using the mode controller device 140. For example, when a child attempts to circumvent the configuration or use any restricted features, the mode controller device 140 can show a report of such actions to the parent.

[0028] In some embodiments, the parent may transmit these restricted mode configurations to the satellite device 138 via the server 110. In other embodiments, the mode controller device 140 may send these configurations directly to the satellite device 138 via a peer-to-peer connection (e.g., Bluetooth, peer-to-peer Wi-Fi, etc.) or via some other network connection that does not include the server 110.

[0029] In some embodiments, each computing device (e.g., mode controller device 140, satellite device 138) may be registered within a group of devices associated with each other (e.g., a family group). For example, each computing device may be associated with a different user account and each user account may be associated with a family group. For example, a user family (e.g., two parents and their children) may each have a specific user account. The user accounts of the family may be associated together in a user account family or a user account network. The associations between user accounts may be further defined. For example, when purchasing or activating a device, a parent may configure a user account as a parent account that can configure or control other user accounts or computing devices used with other user accounts. Similarly, a parent account may be authorized to control the use of any child account through the restricted mode configuration described herein. A parent account may be authorized so that any device associated with a parent account may change the functionality of any satellite device or any device associated with an account registered to a parent's child.

[0030] In some embodiments, each of the mode controller device 140 and the satellite devices 138 are included within an associated device family as described above. Figure 1 A mode controller device 140 is shown and satellite devices 138 may be included in device group 180. In other embodiments, these devices are not associated as devices, but the accounts associated with each device are associated together as a user account family, as described above. In some embodiments, satellite device 138 may receive a data message from a controller device that includes a restricted mode configuration for managing satellite device 138. The restricted mode configuration may be defined by a user of mode controller device 140. As described above, a parent may implement a restricted mode configuration for a child's satellite device. Satellite device 138 may be configured to identify an account identifier associated with mode controller device 140 based on the data message. Satellite device 138 may also be configured to determine an account identifier of a user of mode controller device 140.

[0031] Figure 1 Satellite device 138 is shown and may include management application 150, network interface 170, and user application 175. User application 175 is an example of an application that may be managed or disabled using the restricted mode configuration generated at mode controller device 140.

[0032] In some embodiments, the management application 150 at the satellite device 138 may be configured to implement the received restricted mode configuration. For example, the management application 150 may be configured to receive the restricted mode configuration and identify each configuration setting and its intended target (e.g., an application feature or a system setting). When the configuration is effective, the management application 150 may activate the restricted mode configuration. The activation of the restricted mode configuration may override the functionality of applications other than the management application. For example, when the management application 150 activates the restricted mode configuration, the management application 150 may be the only application actively executing. The satellite device 138 may have disabled all other applications. The management application 150 may be operating only to provide a mode exit process. The management application 150 may also be operable to track the current time so that the restricted mode can be released once the end time specified by the restricted mode configuration is reached.

[0033] In other embodiments, the restricted mode configuration may be designed to directly affect applications or functions at the satellite device without the presence of a management application. For example, a parent may generate a restricted mode configuration at the mode controller device 140. The generated restricted mode configuration may be designed to directly limit the functionality of the user application 175 without executing the management application 150.

[0034] In some embodiments, the restricted mode configuration may be such as completely disabling application functions for user applications 175. In other embodiments, the restricted mode configuration may allow some functions of user applications 175 to continue to run as background processes, but any display or output from satellite devices 138 to users may be disabled. For example, user application 175 may be a game application with a display icon. When the user clicks, taps or otherwise interacts with the display icon, user application 175 may be configured to display a game interface that can play the game. In some embodiments, when the restricted mode configuration is in effect, the display icon for user application 175 may disappear. In other embodiments, the display icon may continue to be displayed, but the interaction with the display icon may cause other interfaces of the application to be ineffective or not displayed. The restricted mode configuration may also disable user application 175 from presenting any notifications or messages to the user of satellite device 138 when the restricted mode is in effect.

[0035] In one embodiment, the restricted mode configuration may be implemented as a service or operating system code that, for example, disables the ability of user applications 175 to connect to network interface 170. In this embodiment, the restricted mode configuration may not require a management application to be executed on satellite device 138 in order to configure it, or may generate a restricted mode configuration that directly affects the functionality of satellite device 138 without involving an installed management application.

[0036] Satellite device 138 may be configured to determine that the account identifier is a member of a trusted group of account identifiers (e.g., a family group). For example, satellite device 138 may identify an account identifier of a parent. As another example, satellite device 138 may identify the account identifier as belonging to a family group of account identifiers (e.g., a user's family) that also includes a user account identifier currently in use at satellite device 138. In addition, mode controller device 140 may be associated with an account within the family group that has been authorized to configure satellite device 138. Thus, satellite device 138 may determine that the account identifier is for an account that is authorized to create a restricted mode configuration for satellite device 138. In response to determining that the account identifier associated with the received restricted mode configuration is authorized to create a restricted mode configuration, satellite device 138 may be configured to automatically apply the restricted mode configuration. In one embodiment, satellite device 138 implements a restricted mode configuration to limit user access to one or more features of satellite device 138.

[0037] The child may use the management application 150 on the satellite device 138 to review the restricted mode configuration and understand the details of the configured restrictions (eg, times when restrictions take effect, changes in application behavior and usage, exceptions, etc.).

[0038] For example, management application 150 may display all restrictions specified in the restricted mode configuration. For example, management application 150 may be configured to extract data from one or more data structures included in the restricted mode configuration. Management application 150 may then populate the display interface with the extracted data. The data may specify applications that should be disabled (e.g., social media applications), and thus a list of prohibited applications may be displayed. The data may specify restricted features (e.g., any video viewing feature may be disabled regardless of the application).

[0039] Similarly, the management application 150 may also display any permitted applications or exceptions to any restrictions. For example, a restricted mode configuration may permit a clock application to view the time. A restricted mode configuration may permit an interface for a mode exit process. A restricted mode configuration may permit applications that are critical to the health or safety of the child (e.g., a blood glucose monitoring application). A restricted mode configuration may specify certain contacts (e.g., the child's parents) that may communicate with the child even if communication applications are otherwise disabled.

[0040] On the satellite device 138, the management application 150 may be configured to provide notifications of attempts to circumvent the restricted mode configuration. Thus, when not in restricted mode, the child may use a management application 150 at the satellite device 138, similar to the management application 145 at the mode controller device 140, to review the received restricted mode configuration and understand how the configuration limits the functionality of the satellite device 138. However, when viewed at the satellite device 138, the restricted mode configuration settings may be read-only and non-editable. In some embodiments, the transmitted restricted mode configuration configures the satellite device 138 such that any attempt to circumvent the restricted mode configuration generates a notification that is transmitted to the mode controller device 140. In other embodiments, the parent may use the management application 145 at the mode controller device 140 to configure what notifications should be provided.

[0041] In addition, the satellite device 138 may also be configured to locally store data for each attempt to circumvent or exit the restricted mode configuration. For example, the satellite device 138 may record each attempt to disconnect the satellite device 138 from the communication network during the restricted mode. The satellite device 138 may also locally record each use of the mode exit process and what function was used. For example, if a child exits and then re-enters the restricted mode, a log of the child circumventing or exiting the restricted mode and any functions used may be stored locally on the satellite device 138. In some embodiments, a parent or teacher may view the local log on the satellite device 138. For example, a child may secretly exit the restricted mode during a test, use a social media application or a web browser application to find the test answers, and then re-enter the restricted mode. If a teacher suspects that a child has exited the restricted mode, the teacher is able to view the local log stored on the child's satellite device 138 and determine whether the child has exited the restricted mode and what function was used.

[0042] Figure 1 A server device 110 is shown that may include a configuration service 112 and a data store 132. The configuration service 112 may include a configuration communicator module 116. The data store 132 may include configuration data 122.

[0043] In some embodiments, when a new device is detected, server device 110 may automatically send a stored restricted mode configuration associated with a user account identifier to the new device associated with the user account identifier (e.g., associated with a child). The new device may then apply the restricted mode configuration settings appropriately on the new device. For example, because different devices have different capabilities, some restricted mode configuration settings specified for a previous device may not apply to a new device that may have different capabilities than the previous device. The new device may apply restricted mode settings related to the capabilities of the new device while ignoring settings for capabilities and / or features that are not supported by the new device.

[0044] The data storage 132 includes configuration data 122. The configuration data 122 may store a set of user account identifiers as user account families. The configuration data 122 may also store mappings between user account identifiers and device identifiers. For example, a user may have multiple devices. When the mode controller device 140 transmits the restricted mode configuration to the server device 110, the mode controller device 140 may include the user account identifier. The server device 110 may be configured to transmit the restricted mode configuration to all devices of the target user using the mapping stored in the configuration data 122. As previously described, the content of the restricted mode configuration and any other communication routed through the server device 110 between the mode controller device 140 and the satellite device 138 may be end-to-end encrypted. However, the user account identifier for the target user may not be encrypted so that the server device 110 can determine the target user and one or more of its devices. In addition, in the case where the server device 110 loses a network connection to, for example, the satellite device 138 via the network 120, the configuration data 122 may cache the restricted mode configuration in an encrypted form until a network connection is reestablished between the server device 110 and the satellite device 138.

[0045] Configuration service 112 includes configuration communicator module 116. In some embodiments, a parent may wish to reduce notifications to the parent's mode controller device 140 regarding each attempt to exit restricted mode on a child's satellite device 138. Configuration communicator module 116 may be configured to receive restricted mode configurations from mode controller device 140 and transmit them to a target satellite device (e.g., satellite device 138). In some embodiments, configuration communicator module 116 may receive a data transmission or message from mode controller device 140 that includes the restricted mode configuration and an identifier for a user account of the target satellite device. In some embodiments, mode controller device 140 may encrypt the restricted mode configuration instead of encrypting the user account identifier so that configuration communicator module 116 can transmit the restricted mode configuration to the correct user.

[0046] In one embodiment, mode controller device 140 may be configured to encrypt the restricted mode configuration and transmit it to server device 110 along with, for example, an identifier of satellite device 138. Server device 110 may then transmit the encrypted restricted mode configuration to satellite device 138. Satellite device 138 may be configured to decrypt the received restricted mode configuration and apply the settings specified therein on satellite device 138.

[0047] In one embodiment, the mode controller device 140 and the satellite device 138 may communicate with each other using an encrypted messaging service, whereby the server device 110 cannot decrypt or access the contents of any messages exchanged between the mode controller device 140 and the satellite device 138. In another embodiment, the mode controller device 140 and the satellite device 138 may exchange encryption keys using a peer-to-peer communication link that does not involve the server device 110. For example, a parent may use a peer-to-peer communication link to exchange encryption keys between the parent's mode controller device 140 and the satellite device 138. In this embodiment, the mode controller device 140 and the satellite device 138 may not use a messaging service that provides encryption, but may use separate encryption and decryption capabilities on the device to secure messages sent via the server device 110.

[0048] In some embodiments, the server device 110 cannot decrypt or access the contents of any restricted mode configuration. For example, although the satellite device 138 may have the key required to decrypt the encrypted restricted mode configuration, the server device 110 may not have the encryption key required to decrypt the encrypted restricted mode configuration. However, in some embodiments, the server device 110 may be configured to store a restricted mode configuration associated with an identifier of a user account family for a user including the mode controller device 140 and the satellite device 138. When a new device is associated with an account identifier, the server device 110 may be configured to search the stored user account and user account family. The server device 110 may then be configured to identify whether the new device is associated with a user account belonging to a particular user account family. The server device 110 may be configured to identify whether there is a user (e.g., a parent) in the user account family who is authorized to create a restricted mode configuration. If the server device 110 finds a user who is so authorized, the server device 110 may be configured to notify the user's controller device (e.g., mode controller device 140) and invite the user to provide a restricted mode configuration. Server device 110 may additionally or alternatively provide the user with existing restricted mode configurations and suggestions to implement one or more of these onto a newly activated device.

[0049] Figure 2 is a system interaction diagram 200 for configuring context-based restrictions for a computing device. Figure 2 Satellite device 138 , server device 110 , and mode controller device 140 are shown interacting with each other to generate, transmit, and implement a restricted mode configuration on satellite device 138 .

[0050] For example, a parent may use a mode controller device 140 while a child may use a satellite device 138. The child may use the device in a variety of contexts, such as at home, at school, and outdoors. When the child is at school, the parent may wish to limit some or all of the functions of the satellite device 138 so that the child can avoid distractions and focus on schoolwork. Therefore, and as shown at step 202, the parent may use the mode controller device 140 to generate a restricted mode configuration to limit one or more features of the child's satellite device 138. As another example, when the parent is at work, for example, the parent may implement a restricted mode on the parent's own device so the parent can focus on work and avoid being distracted by using another satellite device or even the mode controller device 140.

[0051] In some embodiments, a restricted mode configuration may include a plurality of settings, rules, or preferences. For example, a restricted mode configuration may include the times when restricted mode is in effect. For example, a parent may implement restricted mode on a child's device when the child is in school (e.g., from 9:00 a.m. to 3:00 p.m.).

[0052] The restricted mode configuration may define all functionality to be disabled on satellite device 138. For example, once restricted mode begins, the display of satellite device 138 may show a black screen or a generic, non-interactive image. When such full restrictions are configured, satellite device 138 may be functionally unavailable unless the child performs a mode exit process (described below with respect to Figures 6a to 6c describe).

[0053] The restricted mode configuration may also include settings regarding whether to fully or partially restrict satellite device 138 from performing any functions. For example, a parent may create a restricted mode configuration that imposes total restrictions on any functions of satellite device 138 until the restricted mode period ends. As another example, a parent may specify partial restrictions such that certain functions or features of satellite device 138 may still be permitted to perform.

[0054] Similarly, a parent may specify that a particular user application (e.g., user application 175) is permitted to be active. For example, user application 175 may be a health-related application that a child needs to maintain a stable health condition. For example, a health-related application may be used to monitor a child's vital statistics due to a disease that the child suffers from. A parent may specify that user application 175 should be permitted to have full functionality even when all other applications and system-level functionality are disabled. In this example, user application 175 may provide notifications, communicate with other devices, store data, receive input, and operate without any restrictions due to the restricted mode configuration.

[0055] The parent may specify that background processes (e.g., application updates, operating system updates, etc.) may continue to run during the restricted mode. For example, the parent may want to ensure that the child is able to receive notifications from the parent, especially if the parent has made multiple attempts to contact the satellite device 138. In this example, the communication functions of the satellite device 138 (e.g., network communication device, antenna, communication interface, etc.) may still be permitted to fully perform their functions.

[0056] Additionally, a restricted mode configuration may be generated to suppress all alerts or notifications (e.g., notifications of new text messages) from satellite device 138. In other words, during restricted mode, no notifications, alarms, pings, phone rings, or similar notification outputs may be generated at satellite device 138. In some embodiments, notifications from critical applications may still be permitted (such as in the health-related application example above).

[0057] At step 204, mode controller device 140 may transmit the generated restricted mode configuration to server device 110. In one embodiment, controller device 140 may be configured to encrypt the restricted mode configuration and transmit it to server device 110 along with, for example, an identifier of satellite device 138. Server device 110 may then transmit the encrypted restricted mode configuration to satellite device 138. Satellite device 138 may be configured to decrypt the received restricted mode configuration and apply the settings specified therein on satellite device 138.

[0058] Additionally, mode controller device 140 sends one or more identifiers for the target satellite devices to server device 110. In some embodiments, mode controller device 140 encrypts the restricted mode configuration without encrypting the identifiers for satellite devices 138 so that server device 110 can transmit the restricted mode configuration to the correct target devices.

[0059] Satellite device 138 receives the restricted mode configuration from server device 110. Additionally, satellite device 138 may receive a user account identifier for the user (eg, a parent) who created the restricted mode configuration.

[0060] In some embodiments, satellite device 138 may evaluate whether the account used to generate the restricted mode configuration is authorized to cause satellite device 138 to receive and apply the restricted mode configuration. More specifically, satellite device 138 may evaluate the user account identifier for the creator of restricted mode controller device 140. Satellite device 138 may determine whether the user account identifier has the correct permissions to implement the restricted mode configuration on satellite device 138. In one embodiment, satellite device 138 may retrieve family group data from server device 110, such as user account identifiers for each user account in the family and permissions associated with each user account identifier. Satellite device 138 may compare the family group data with the account identifier received with the restricted mode configuration.

[0061] As an example, a parent may send a restricted mode configuration to a satellite device 138 of their child. The child's satellite device 138 determines that the parent's user account identifier received with the restricted mode configuration is a user account identifier with the correct family group membership and permissions. For example, the child's satellite device 138 may check whether the account identifier is that of the child's parent based on the family group data. The child's satellite device 138 may also evaluate whether the account identifier has permissions to create and send the restricted mode configuration. If the child's satellite device 138 determines that the sender is in the correct family group and has the correct permissions, then the child's satellite device 138 may determine that the sender is authorized. In contrast, a teacher may transmit a restricted mode configuration to a child, where the teacher does not share any family group membership with the child. In this case, the child's satellite device 138 may not consider the sender to be authorized and ignore the restricted mode configuration.

[0062] Alternatively, in other embodiments, the server device 110 may determine whether the user account associated with the mode controller device 140 is authorized to implement the restricted mode configuration. For example, the server device 110 may evaluate the user account identifier or other account credentials associated with the mode controller device 140 and / or the received restricted mode configuration to determine whether the restricted mode configuration is received from an authorized user account or generated by an authorized user account. In some embodiments, the server device 110 may evaluate the account identifier transmitted from the mode controller device 140 and may determine whether the user of the controller device 140 is authorized to configure the restricted mode on the satellite device 138. The server device 110 may also receive an identifier for a target device to be managed using the restricted mode configuration. The server device 110 may evaluate whether the user account identifier associated with the controller device 140 is authorized to implement the restricted mode configuration on a specific satellite device that has been identified as a target. In some embodiments, if the server device 110 determines that the user account identifier associated with the restricted mode configuration is authorized, the server device 110 may transmit the restricted mode configuration received from the controller device 140 to the satellite device 138 at step 206. In some embodiments, server device 110 may also transmit an account identifier or a device identifier received in conjunction with the restricted mode configuration to satellite device 138 .

[0063] At step 208, satellite device 138 may be configured to implement a specified restricted mode. In one embodiment, the restricted mode configuration is implemented on satellite device 138 immediately. In another embodiment, the restricted mode configuration is not implemented until a time is reached to activate or switch to the restricted mode on satellite device 138. Implementing the restricted mode configuration means that satellite device 138 is ready to activate the restricted mode configuration at a specified time. For example, to implement the restricted mode configuration, the operating system of satellite device 138 or management application 150 may transmit commands to multiple applications operating on satellite device 138 to deactivate their display icons at a specified time in the future. The operating system may schedule the display screen of satellite device 138 to be disabled at the specified time. As described herein, implementing the restricted mode configuration prevents the child from attempting to circumvent one or more parameters of the restricted mode configuration before the restricted mode configuration takes effect.

[0064] At a time specified by the restricted mode configuration, at step 210, the satellite device 138 may be configured to transition to restricted mode. As described above, unless a specific mode exit process is followed to exit restricted mode, entering restricted mode may cause the satellite device 138 to deactivate some or all of its functions. In some embodiments, the satellite device 138 may also be configured to enter a low power consumption mode when the restricted mode is activated. In some embodiments, the satellite device 138 may be configured to maintain certain communication hardware (e.g., a cellular radio, antenna, or other mobile communication hardware) in an active state or an active but low power state so that the satellite device 138 can still receive important communications (e.g., emergency alerts).

[0065] During the time that satellite device 138 is in restricted mode, the user of satellite device 138 may attempt to circumvent restricted mode. For example, a child may disconnect satellite device 138 from the communication network (e.g., place the device in 'airplane mode') before the child knows that the restricted mode configuration will be received or will take effect, in an attempt to prevent restricted mode from being implemented or activated. In the case where satellite device 138 is a wearable device, the child may attempt to remove satellite device 138 or give it to someone else or drain its power. In other cases, the child may perform a mode exit process on satellite device 138 and exit restricted mode before the time for restricted mode to end is reached.

[0066] In some embodiments, any of the above or any other attempt to circumvent or remove restricted mode is reported by satellite device 138 back to mode controller device 140 (e.g., via server device 110) at step 212. In some embodiments, upon circumventing or exiting restricted mode, satellite device 138 may also report specific features or functions used at satellite device 138. In addition, satellite device 138 may be configured to transmit mode exit and feature usage reports in an encrypted form so that they can only be read by mode controller device 140.

[0067] In addition, in some embodiments, satellite device 138 may be configured to re-enter restricted mode shortly after exiting. For example, a child may exit restricted mode using a mode exit process. In some embodiments, a restricted mode configuration may define that restricted mode will be reactivated within a specific time (e.g., 5 minutes) after it exits. In other embodiments, a restricted mode configuration may define that restricted mode is reactivated based on certain gestures or movements. For example, satellite device 138 may be a wearable device that is sensitive to body movement. A wearable computing device (such as a watch) may detect when a user bends their arm to lift the watch (e.g., "watch up" position) and view the dial from the wrist, and may also detect when the user lowers their arm back to a relaxed position (e.g., "watch down" position). Therefore, satellite device 138 may be configured to detect whether to exit restricted mode when the watch is in the "watch up" position, and re-enter restricted mode once satellite device 138 reaches the "watch down" position.

[0068] At step 214, server device 110 may be configured to transmit mode exit and feature usage reports to mode controller device 140. In some embodiments, server device 110 receives mode exit and feature usage reports from satellite device 138 in encrypted form. In some embodiments, server device 110 may be configured to generate batch reports at periodic intervals (e.g., weekly) for transmission to mode controller device 140. In other embodiments, server device 110 may be configured to immediately forward any received mode exit or feature usage reports to mode controller device 140.

[0069] At step 216, mode controller device 140 may be configured to receive mode exit or feature usage reports and compile these mode exit or feature usage reports into a historical report of such events for the user of mode controller device 140. The historical report may be continually updated to account for new events. For example, a parent may be able to view a history of attempts to exit restricted mode on mode controller device 140, what features were used on satellite device 138, specific dates and times, and any specific patterns of such behavior. A longer term history enables a parent to customize the restricted mode configuration to better fit the child's schedule and discuss any relevant modes with the child.

[0070] Figure 3 3 is a system interaction diagram 300 for configuring context-based restrictions for a computing device. As shown, mode controller device 140 and satellite device 138 may interact with each other to establish a restricted mode configuration for satellite device 138.

[0071] At stage 310, the mode controller device 140 transmits the restricted mode configuration directly to the satellite device 138. Figure 2In contrast to the described embodiments, mode controller device 140 may communicate with satellite device 138 without server device 110 or another intermediary device. In some embodiments, mode controller device 140 establishes a direct connection with satellite device 138 to transmit the restricted mode configuration. For example, mode controller device 140 may initiate a peer-to-peer connection (e.g., Bluetooth, peer-to-peer Wi-Fi, etc.) with satellite device 138. Mode controller device 140 may be physically close to satellite device 138 and establish a proximity-based connection with satellite device 138. Satellite device 138 receives the restricted mode configuration at stage 320 and transmits the accepted content.

[0072] Figure 4 4 shows a set of user interface (UI) elements 400 that can be used to configure context-based restrictions for a computing device. In some embodiments, the mode controller device 140 ( Figure 1 ) may present a UI element 400 to a user to create a user interface for a satellite device 138 ( Figure 1 In some embodiments, these UI elements may appear on a single display screen or across multiple screen displays of the management application 145 of the mode controller device 140.

[0073] In some embodiments, mode controller device 140 may be configured to implement a restricted mode configuration in an asynchronous or synchronous manner. For example, a parent may create a restricted mode configuration at mode controller device 140 and then send it to satellite device 138 (e.g., via server device 110). This process may be referred to as asynchronous because the creation process at mode controller device 140 occurs at an earlier time than the specific implementation of the configuration at satellite device 138.

[0074] Mode controller device 140 may also be configured to perform a synchronized restricted mode configuration for satellite devices 138. In some embodiments, mode controller device 140 establishes a pairing relationship with satellite devices 138 to synchronize creation of a restricted mode configuration at satellite devices 138, as described further below.

[0075] In the asynchronous process, the management application 145 of the mode controller device 140 displays the UI element 400 for the user (e.g., a parent). Figure 4, UI element 402 shows a list of devices. In one embodiment, UI element 402 may identify a device by device name or a nickname given by a parent (e.g., "son's phone," "daughter's watch"). In another embodiment, UI element 402 may depict a list of contacts each associated with a particular device. As shown in UI element 402, the user selects a contact name "Jane" from the list. Management application 145 may also display UI element 404. In UI element 404, management application 145 displays a time selection control, enabling the parent to set a start time and an end time for the restricted mode to be implemented for Jane's device.

[0076] The management application 145 may also display a UI element 406 where the parent may select any exceptions to the restricted mode configuration. In other words, the parent may select any functions that the parent wishes to permit the satellite device 138 to continue to perform during the restricted mode. For example, the parent may wish to permit the satellite device 138 to continue to run background processes, or to continue to receive communications from other devices without notifying the child using the satellite device 138, etc. As shown in the UI element 406, the parent selects health-related user applications to continue to execute on the satellite device 138 even during the restricted mode. The child may have certain health issues that require monitoring of vital statistics or body chemistry, thereby requiring the health-related user application to continue to perform its functions (e.g., the satellite device 138 is a wearable device for the child).

[0077] After configuring any exceptions to the restricted mode configuration, the parent may receive a confirmation message from management application 150. For example, the message may state "Jane's watch will be in restricted mode from 9:00 AM until 3:00 PM," as shown at UI element 408. Management application 145 generates a restricted mode configuration (e.g., a data structure stored in a configuration file) and transmits it to satellite device 138. As previously described, the process just described is an asynchronous process for implementing the restricted mode configuration.

[0078] The mode controller device 140 may also use the synchronization process to create a restricted mode configuration for the satellite device 138. For example, the mode controller device 140 may establish a pairing relationship with the satellite device 138. Through the pairing relationship, the mode controller device 140 may view the user interface of the satellite device 138. These user interfaces of the satellite device 138 may also present Figure 4 4. In other words, a user of the mode controller device 140 is able to remotely configure context-based restrictions for the satellite device 138.

[0079] Parents can use mode controller device 140, but other satellite devices can also be used. Parents can pair mode controller device 140 with one of the parent's satellite devices. Pairing with a satellite device can enable parents to directly control the satellite device. For example, a parent can view the display or user interface of their own satellite device (e.g., smart watch) on their mode controller device 140 (e.g., smart phone). In this example, each of mode controller device 140 and parent's satellite device is associated with a parent's user account. But parents can also switch from the parent's satellite device to the child's satellite device 138 at mode controller device 140. Parents can view the user interface of satellite device 138 on mode controller device 140. Parents can use this function to create a restricted mode configuration using the application of satellite device 138. For example, the management application 150 of satellite device 138 can present the same UI element 400 that the management application 145 of mode controller device 140 displayed earlier in the asynchronous configuration process during this synchronization process.

[0080] In some embodiments, a parent may be able to control the applications of satellite devices 138 in a way that a child may not. For example, a parent may use the management application 150 of a satellite device 138 to create a restricted mode configuration (when a mode controller device 140 is paired with the satellite device 138), but a child may not be able to do so. This is because the parent's account may have more or higher levels of permissions. These permissions may enable the parent to remotely configure the satellite devices 138 using the applications or interfaces of the satellite devices 138 while viewing and controlling them from the mode controller device 140.

[0081] In addition, the parent can modify the restricted mode configuration while it is active on the satellite device 138. The child may not be able to modify the restricted mode configuration without performing a mode exit procedure. However, the parent can use the mode controller device 140 to switch to the satellite device 138 and modify the restricted mode configuration directly.

[0082] Figure 5 is a calendar view 500 indicating various dates and times at which a person may configure context-based restrictions for a computing device.

[0083] In some embodiments, a parent may wish to set a cyclic restricted mode configuration for a child. For example, a parent may wish to cyclically restrict the child's satellite device (e.g., Figure 1 The satellite device 138 shown in FIG. 1 implements a restricted mode. Therefore, Figure 5Day view 502, day view 504, day view 506, day view 508, day view 510, day view 512, and day view 514 are shown (e.g., for Monday through Sunday, respectively). Figure 4 In or in addition to the stage 404 shown in FIG. 4 , a calendar view 500 is also displayed. The parent can use the calendar view to highlight each day view and select the restricted mode for each weekday. Figure 5 Also shown are day views 512 and 514 that do not show restricted mode configurations. For example, a parent may not set a restricted mode for a child during the weekend when the child is not in school.

[0084] In some embodiments, the child may wish to request a modification of the recurring restricted mode configuration. For example, a parent may import or receive a school calendar for the child. The school calendar may indicate that Thursday, represented by day view 508, is a school holiday. In other words, the child may not be in school that day and may not need restricted mode. Due to the school holiday, the child may request to remove the restricted mode for Thursday. In response, the parent may modify the restricted mode configuration at mode controller device 140.

[0085] Similarly, a parent may generate different restricted mode configurations based on the usage context. A parent may generate one restricted mode configuration for a school usage context (e.g., between 9:00 a.m. and 3:00 p.m.) in which all functions on the satellite device 138 are disabled. A parent may generate another restricted mode configuration for an after-school usage context. For example, for an after-school music class from 3:00 p.m. to 4:00 p.m., a parent may generate a second restricted mode configuration that disables all functions except for the music or recording applications that the child needs to practice his or her music class.

[0086] Figures 6a to 6c A plurality of display stages 640 to 690 of a satellite device configured with a restricted mode configuration are shown. More specifically, Figures 6a to 6c Illustrated are satellite device displays as the satellite device enters and exits restricted mode.

[0087] like Figure 6a As shown in FIG. 6A , stage 640 shows the satellite device 138 (similar to Figure 1600 . In some embodiments, stage 640 may depict a child's satellite device (e.g., a wearable computing device or other mobile computing device) in a default operating mode. Stage 640 depicts various display icons, each representing a user application or other software that can be executed on satellite device 138. Stage 640 shows display icons representing phone application 604, mail application 606, video application 608, clock application 610, game application 612, and music application 614. In some embodiments, the display icons may represent a group of applications. Stage 640 also shows that satellite device 138 includes hardware controls 620 (e.g., buttons, dials, switches, etc.).

[0088] Each application of satellite device 138 may have different features that may be disabled or restricted by the restricted mode configuration. For example, phone application 604 may provide the ability to make and receive calls using satellite device 138. When a phone call is incoming, phone application 604 may output an audio notification (e.g., a ringing tone). Phone application 604 may update the display shown in stage 604 to a display interface showing an identifier and / or photo of the caller. Phone application may be configured to show notifications in the form of a banner, a tag, a modal window, etc. Similarly, mail application 606 may be configured to show new mail notifications. Video application 608 may be configured to show notifications. Game application 612 may be configured to show special notifications indicating, for example, when a new online game player is available, with which the user of satellite device 138 can play a game. Music application 614 may be configured to play music, show a small display, or not show a display but show display-specific controls (e.g., only show volume or random play controls without showing a complete display interface).

[0089] Each display icon can be interactive in a variety of ways. In some embodiments, the satellite device 138 may include a touch-sensitive surface. For example, each display icon can be tappable or clickable to access a first function. The touch-sensitive surface can handle multiple simultaneous input points, including processing data related to the pressure, degree, or position of each input point. Each display icon can respond to gestures performed using multiple fingers, including pinching and swiping to enable other functions. The touch-sensitive surface itself can be swiped to view a different display interface (e.g., with additional application icons or other displays).

[0090] In some embodiments, the satellite device 138 receives a restricted mode configuration from the controller device 140 at stage 640. For example, the current time at stage 640 may be 8:55 am. At this point, the parent may use the controller device 140 to transmit the restricted mode configuration to the child's satellite device 138. The restricted mode configuration may be configured to activate at 9:00 am and remain in effect until 3:00 pm. For example, the time period from 9:00 am to 3:00 pm may be the time when the child is in school, and the parent may wish to restrict the child's use of the satellite device 138 during this time period. In other embodiments, the parent may have established a restricted mode configuration for the satellite device 138 at an earlier time. The parent or guardian may schedule a restricted mode for the child's satellite device 138 for the entire work week. For example, the parent may wish to implement a restricted mode on the child's satellite device 138 from 9:00 am to 3:00 pm every day, Monday through Friday of a certain week. Thus, at the specified time, the satellite device 138 will automatically enter the restricted mode.

[0091] At the time indicated by the restricted mode configuration, the satellite device 138 automatically enters the restricted mode. In some embodiments, the satellite device 138 may be configured to display no content or only display wallpaper or generic images that may not respond to user interaction. In other embodiments, the satellite device 138 automatically switches to the stage 650 shown in Figure 6. When in restricted mode, the satellite device 138 may be configured to display certain display icons. For example, stage 650 depicts a clock application icon 610, similar to the clock application icon 610 displayed in stage 640. The clock application icon 610 can maintain the same size as in stage 640. As shown in stage 650, the clock application icon 610 looks larger than in stage 640 and occupies a larger screen area to indicate the state of the satellite device 138, which is limited to little or no function.

[0092] Stage 650 also shows a mode exit process control 616 and an emergency communication icon 618. In some embodiments, the display screen of the satellite device 138 may be rendered completely non-interactive or non-responsive, except for the ability for the user to interact with the mode exit process control 616 and the emergency communication icon 618. In other embodiments, the mode exit process control 616 may be the only visible icon, or other icons may be displayed but the mode exit process control 616 may be the only icon that responds to user interaction.

[0093] In some embodiments, once the restricted mode takes effect, multiple application interaction features become inactive or unavailable. As shown in stage 650, several display icons disappear from the display of satellite device 138. In some embodiments, display icons for phone application 604, mail application 606, video application 608, game application 612, and music application 614 are removed from the display of satellite device 138. In other embodiments, display icons for the above applications still appear on the display of satellite device 138, but the restricted mode configuration makes them non-interactive. For example, the icon for phone application 604 can still be displayed, but tapping it (e.g., on a touch-sensitive display) may not cause an obvious change in the display.

[0094] Satellite device 138 may be configured to determine additional actions for any actively running applications to maintain the expected user experience despite changes caused by the restricted mode configuration. For example, a child may be in the middle of a text messaging conversation when restricted mode begins. The recipients of the child's text messages may be unaware of the start of restricted mode. Thus, satellite device 138 may be configured to set a default outgoing message for any text messaging conversation participants. Participants in a conversation with the child may receive an automatically recorded message that the child's device is now in restricted mode. Gaming application 612 ( Figure 6a ) can be configured to automatically pause and resume at the same point in the game when restricted mode ends. Music application 614 can be configured to pause the output of a currently playing audio file and resume at the same point in the file when restricted mode ends, etc. In an alternative embodiment, satellite device 138 can be configured by the restricted mode configuration to provide a reminder to the child that restricted mode will begin soon (e.g., in five minutes) so that the child can manually pause or end any activity and minimize any interruption caused by the initiation of restricted mode.

[0095] In other embodiments, according to the restricted mode configuration, a subset of the displayed icons may disappear, but other icons may continue to be displayed and be available or interactive. For example, when the restricted mode configuration is implemented, icons for mail application 606, video application 608, game application 612 and music application 614 may disappear, but phone application 604 icons may continue to be displayed and interact with the user in case the user needs to make an emergency call. Such embodiments enable the user to still use satellite device 138 in a limited sense while implementing the desired restrictions of the control user. For example, the restricted mode may disable all functions from satellite device 138, so that the child can focus on schoolwork but still allow phone calls, so that the child can call parents or emergency contacts when necessary. Parents may be satisfied that phone application 604 is active, because even if it is available to the child, the child is unlikely to make a call during a class period with a teacher present. Similarly, the child's schoolwork may require some other applications. For example, video application 608 may be necessary for the child to view a learning video of a certain school subject.

[0096] Additionally, the restricted mode configuration may apply to certain functions at satellite device 138 for shorter periods than a full day. For example, a parent may enable certain applications based on specific time periods for a child. As in the example of video application 608, knowing the child's school schedule, a parent may enable certain applications during certain school hours based on the child's needs, while other applications (e.g., game application 612) may remain disabled for the duration of the school day.

[0097] The mode exit process control 616 can be configured to enable the user of the satellite device 138 to exit the implemented restricted mode. In some embodiments, the mode exit process control 616 can be the only icon displayed on the satellite device 138. In other embodiments, other icons or controls can be displayed, but the mode exit process control 616 can be the only icon or control that responds to the input. In other embodiments, no specific mode exit process icon may be displayed, but the entire display screen displays a default screen (e.g., a black screen or a generic wallpaper image), which, when tapped, initiates the mode exit process for the user to attempt to exit the restricted mode. In still other embodiments, all display icons (e.g., icons for the phone application 604, the mail application 606, etc.) can be displayed. However, when the user interacts with the display icon of any application, the mode exit process will be initiated to replace the default display or behavior of the application.

[0098] like Figure 6b, stage 660 shows the user attempting to exit restricted mode by selecting mode exit process control 616. For example, the time may be late afternoon (e.g., 1:00 p.m.), when the child is still in school and restricted mode is still active, but the child wishes to exit restricted mode. Selecting mode exit process control 616 at stage 660 causes satellite device 138 to transition to stage 670.

[0099] Stage 670 displays a warning notification 672, a confirmation control 674, and an exit cancel control 676. In some embodiments, the warning notification 672 may indicate to the user of the satellite device 138 that an attempt to exit restricted mode will be reported to the user who imposed the restricted mode configuration on the satellite device 138. For example, a child using the satellite device 138 will be warned that exiting restricted mode will be reported to his mother, the mother who imposed the restricted mode configuration. Stage 670 shows an exit cancel control 676, which, if selected, may restore the satellite device to restricted mode, as shown in stage 660. In some embodiments, selecting the exit cancel control 676 after initially selecting the mode exit process control 616 may not result in any notification to the user of the mode controller device 140 (e.g., a parent).

[0100] However, stage 670 shows the child proceeding to select confirmation control 674. Selecting confirmation control 674 may cause satellite device 138 to enter a mode exit process which, if completed, will disable restricted mode and restore satellite device 138 to its default operating mode with all of its functionality available.

[0101] In some embodiments, selecting the confirmation control 674 causes the satellite device 138 to display the stage 680 ( Figure 6c As described above, the mode exit process is designed to require the child to focus significantly on the satellite device 138 and also interact with the satellite device for a significant length of time so that it becomes obvious that the child is attempting to exit the restricted mode.

[0102] Stage 680 shows a mode exit process display that requires the user to accurately tap the screen a number of times. For example, a child may need to tap multiple moving objects (e.g., a moving ball) on the screen a number of times within a period of time. Stage 680 shows a text label 688, a timer 690, multiple moving objects 692 that require interaction (e.g., touch input), and an exit cancel control 694. The exit cancel control 694 may be similar to the exit cancel control 676 ( Figure 6b 670 of step 110), because both can cause satellite device 138 to return to restricted mode. In one embodiment, using either exit cancel control can result in no notification to the parents.

[0103] As shown in stage 680, the user must complete the mode exit process according to a certain time period. For example, the user may be required to tap all moving objects within a certain time limit (e.g., 1 minute) or the restricted mode may be reactivated. As another example, the user may be required to continue tapping each moving object with at least some level of accuracy for the length of time before the restricted mode can be exited.

[0104] In other embodiments, hardware control 620 can also be used to exit restricted mode. For example, a parent can specify a specific movement sequence for hardware control 620 that will result in exiting restricted mode. For example, where hardware control 620 is a crown, a parent can specify that hardware control 620 be rotated clockwise and / or counterclockwise by a precise amount in a specific sequence before restricted mode can be exited. In another embodiment, management application 150 of satellite device 138 can automatically generate a random rotation movement sequence that a child must perform in order to exit restricted mode. Instructions on how to rotate the crown can be simultaneously displayed on the display of satellite device 138.

[0105] In addition, parents can configure different mode exit processes in the restricted mode configuration depending on the usage context. For example, a mode exit process (such as the mode exit process shown in stage 680) can be configured for a classroom teaching period context, where a child's prolonged interaction with the satellite device 138 to exit the restricted mode will likely be noticed by the teacher. In an after-school usage context, the child may be allowed to use the satellite device 138 to, for example, view music clips required for music practice. In this latter context, the child can use the mode exit process of stage 680 to more conveniently exit the restricted mode without attracting attention, because the teacher may think that the child is viewing the music clips rather than trying to exit the restricted mode configuration. Therefore, a different mode exit process may be required for the above-mentioned after-school context, such as a mode exit process that requires physically shaking the satellite device 138 for a length of time before the restricted mode will be exited.

[0106] In some embodiments, once the user successfully completes the mode exit process, the satellite device 138 is restored to its default operating mode. As shown in stage 690, the satellite device 138 is restored to display multiple application icons. The satellite device 138 can be configured to reactivate any features, background processes, functions, or behaviors that were deactivated during the restricted mode. In addition, exiting the restricted mode may cause the user to receive any notifications received during the restricted mode but suppressed. As described above, if the restricted mode should be effective at this time, it may be reactivated after a certain interval (e.g., 5 minutes) or after a certain movement (e.g., "watch down") or after a period of inactivity. In addition, in each of the above embodiments of the mode exit process, the child needs to look at the satellite device 138 for a long time and interact significantly with the hardware controls or touch-sensitive surface to complete the mode exit process.

[0107] Figure 7 700 is a system interaction diagram illustrating a trusted third party configuring context-based restrictions for a computing device. In some embodiments, a user of mode controller device 140 may wish to delegate the ability to create restricted mode configurations for satellite devices 138 for a limited time or limited purpose. For example, a parent may allow a child's teacher to create restricted mode configurations for the child while the child is in school. The parent may configure the child's satellite device to respond to restricted mode configurations created by devices of other trusted individuals, such as the child's teacher.

[0108] In one embodiment, the child's satellite device 138 may electronically announce its ability to receive restricted mode configurations, and the teacher may use the teacher's device to detect the announcement and proceed to create and transmit the restricted mode configuration. In other embodiments, the teacher may announce the teacher's device as providing a restricted mode configuration. The child's satellite device 138 may respond to the announcement of the teacher's device by automatically accepting the restricted mode configuration or notifying the child to voluntarily enter restricted mode. A first teacher can implement a first restricted mode configuration specific to the first teacher's teaching period, while a second teacher can implement a second restricted mode configuration for the second teacher's teaching period.

[0109] like Figure 7 , the satellite device 138 first announces its availability for restricted mode configuration at step 702. For example, a child's satellite device may be in a classroom near a teacher's device. The child's satellite device 138 may broadcast a restricted mode availability token, which may be configured to be decipherable by a trusted device 130 (e.g., the teacher's device). At step 704, the trusted device 130 detects the restricted mode availability token.

[0110] A user of a trusted device 130 (e.g., a teacher) may wish to implement a restricted mode on an announcing satellite device 138. The user of the trusted device 130 may require authorization from a parent using a mode controller device 140. In some embodiments, the teacher has prior authorization from a parent using a mode controller device 140 to implement a restricted mode configuration on a satellite device 138. In other embodiments, the teacher first requests authorization using a trusted device 130 to implement a restricted mode on a satellite device 138, as shown at step 706. More specifically, the trusted device 130 communicates an authorization request to the server device 110 to implement a restricted mode configuration for a satellite device 138. The authorization request may include details of the restricted mode configuration, the target satellite device 138, the duration of the restricted mode, and one or more identifiers of the teacher using the trusted device 130.

[0111] In some embodiments, and as shown at step 708, server device 110 forwards the request to mode controller device 140. In some embodiments, mode controller device 140 may be configured to evaluate the authorization request from trusted device 130 at step 710. For example, a parent may have previously met with a teacher and authorized the teacher to impose a restricted mode configuration on the child's satellite device. Upon receiving the authorization request, the parent may compare the request with the parent's prior agreement with the teacher. The parent may determine whether the authorization request meets the parent's expectations in terms of the length of restricted mode on the child's device, the type of restrictions, etc.

[0112] At step 712, the parent may approve the authorization request and transmit an authorization approval message to the server device 110. In some embodiments, the authorization approval message may include an authorization token that the mode controller device 140 creates for the trusted device 130 to use when transmitting the restricted mode configuration to the satellite device 138. At step 714, the server device 110 may be configured to forward the authorization approval message with the authorization token to the trusted device 130. The trusted device 130 is capable of providing the authorization token received from the mode controller device 140 to the satellite device 138 so that the satellite device 138 recognizes the trusted device 130 as authorized and accepts the restricted mode configuration from the satellite device 138.

[0113] Trusted device 130 receives the authorization approval message and, at step 716, transmits the restricted mode configuration to satellite device 138. In some embodiments, satellite device 138 verifies (e.g., by evaluating the authorization token) that trusted device 130 is authorized to transmit the restricted mode configuration to satellite device 138. At the time specified in the restricted mode configuration received from trusted device 130, satellite device 138 activates the specified restricted mode.

[0114] In some embodiments, trusted device 130 may be configured to receive specific mode exit and feature usage history reports specific to the restricted mode configuration set by the user of trusted device 130. For example, a child's teacher may set a restricted mode configuration for the teacher's own one-hour teaching period on the school day. Thus, the teacher's trusted device 130 may receive reports on any attempts by the child to exit restricted mode or use any features that occurred during the teacher's one-hour teaching period. This enables the teacher to review these reports and address the child's behavior at the end of the teaching period, rather than needing to address each mode exit attempt in real time. The teacher may not receive mode exit and feature usage reports for any other time period.

[0115] In some embodiments, the satellite device 138 and the trusted device 120 may establish a trusted relationship that does not require the server device 110. For example, the child or the child's parent may have previously configured the child's satellite device 138 to accept any restricted mode configuration from the teacher's trusted device 120. Thus, the trusted device 120 may receive the restricted mode availability token at step 704 and immediately jump to 716 and transmit the restricted mode configuration created by the teacher. The satellite device 138 may be configured to accept the restricted mode configuration and activate the restricted mode at the specified time without further verification from the mode controller device 140 or the server device 110.

[0116] Example Process

[0117] In order to enable the reader to clearly understand the technical concepts described herein, the following process describes the specific steps performed in a specific order. However, one or more steps of a specific process can be rearranged and / or omitted while remaining within the expected scope of the technology disclosed herein. In addition, different processes and / or their steps can be combined, recombined, rearranged, omitted and / or performed in parallel to create different processing flows that are also within the expected scope of the technology disclosed herein. In addition, although for the sake of clarity, the following process can omit or briefly summarize some details of the technology disclosed herein, the details described in the above paragraphs can be combined with the process steps described below to obtain a more complete and comprehensive understanding of these processes and the technology disclosed herein.

[0118] Figure 8 8 is a flow chart illustrating an exemplary process 800 for configuring context-based restrictions for a computing device. For example, process 800 may be performed by satellite device 138 to receive and implement a restricted mode configuration.

[0119] As mentioned above about Figure 1As described, satellite devices 138 may be included in device group 180 along with mode controller device 140, such that controller mode device 140 may be used to implement restricted mode configurations on satellite devices 138. In addition, a parent may create a user account family that includes the parent's user account with permission to generate restricted mode configurations and implement those configurations on the child's satellite devices. The parent may configure the user account family so that any one used with the child's own user account becomes a satellite device. In some embodiments, the child's satellite device may only receive and apply restricted mode configurations from devices logged in using the parent's user account.

[0120] In some embodiments, satellite device 138 receives a restricted mode configuration that specifies a context for restricted mode. The restricted mode configuration may apply to a context defined by a specific time, a specific location, or a combination of time and location. For example, a restricted mode configuration may specify that a child's satellite device 138 enters restricted mode at a certain time of day (e.g., school time, such as 9:00 a.m. to 3:00 p.m.), at a certain location (e.g., a school building), or when there is a combination of a specific time and location (e.g., enter restricted mode when at school during school hours, but not enter restricted mode when at home during those same times, for example).

[0121] Based on the context, the restricted mode configuration may define certain restrictions to be implemented on the satellite device 138. For example, for a child in a school context, the restricted mode configuration may disable any application with a video playback feature on the child's satellite device 138.

[0122] At step 802 of process flow 800, satellite device 138 may be configured to receive a first data message that may include a restricted mode configuration. In some embodiments, satellite device 138 may receive the first data message from server device 110. As described above, server device 110 may receive the restricted mode configuration from mode controller device 140 and provide these restricted mode configurations to satellite device 138. In some embodiments, mode controller device 140 may encrypt these restricted mode configurations using a key that only satellite device 138 and mode controller device 140 have, but not server device 110. In other embodiments, satellite device 138 receives the first data message that includes the restricted mode configuration directly from mode controller device 140. In these embodiments, the first data message may or may not be encrypted.

[0123] In some embodiments, satellite device 138 may be configured to decrypt the first data message. Satellite device 138 may be configured to determine the context specified in the restricted mode configuration. For example, the restricted mode configuration may specify a time of day. Therefore, satellite device 138 may determine whether the current time corresponds to that time of day. As another example, the restricted mode configuration may specify a specific location as an appropriate context. Satellite device 138 may determine the specified location and evaluate whether the current location of satellite device 138 corresponds to the location specified in the restricted mode configuration.

[0124] In some embodiments, the restricted mode configuration may specify that the start time for satellite device 138 to enter restricted mode is immediate. In other words, regardless of the current time or location, as long as the restricted mode configuration is received, satellite device 138 may need to enter restricted mode.

[0125] In addition, the restricted mode configuration may specify features to disable, features to remain enabled, display behavior, limits on user notifications and alerts, logging and reporting preferences (e.g., for mode exit attempts), scheduling details (e.g., a restricted mode configuration may be set to repeat every weekday of the week), etc. As described above, the parameters of the restricted mode configuration are set by the user of the second device (e.g., a parent using mode controller device 140) and are remotely transmitted and applied to satellite device 138, rather than being native to satellite device 138. A parent may set multiple restricted modes on a child's satellite device 138 during a particular day or over the course of several days.

[0126] The start time may also be scheduled at a certain time. As an example, restricted mode may be set to start at 9:00 a.m. The current time may be 8:00 a.m. Therefore, satellite device 138 will enter restricted mode in one hour. As another example, restricted mode may be set to start at 9:00 a.m., but the current time may already be 9:30 a.m. In this example, satellite device 138 may determine that the current time is after the scheduled start time and immediately enter restricted mode. Therefore, and as shown at step 804, satellite device 138 determines that the current time is within the defined time period of the restricted mode configuration.

[0127] If satellite device 138 determines that the current time is within the restricted mode configuration time period, it automatically activates restricted mode, as shown at step 806. Activating restricted mode disables the features of satellite device 138 specified in the restricted mode configuration received from mode controller device 140. In some embodiments, the child cannot use the specified features unless the child first performs a mode exit procedure that significantly captures the child's attention for a specific length of time.

[0128] In some embodiments, when in restricted mode, satellite device 138 may be configured to continue to provide access to certain features different from those identified in the restricted mode configuration, as shown at step 808. For example, a restricted mode configuration may disable text message notifications from all contacts, but still allow text message notifications from emergency services. For example, local emergency personnel may send a text message warning of severe weather in the area. Satellite device 138 may be configured by the restricted mode configuration to allow notifications of such messages to be notified to a child. For example, a restricted mode configuration may configure a text messaging application on satellite device 138 to allow notifications originating from emergency service contacts or messages including specific content.

[0129] As another example, satellite device 138 may allow notifications from health-related applications. For example, satellite device 138 may be a wearable device that monitors certain vital statistics (e.g., blood pressure, heart rate, blood sugar, etc.). In the event that a certain vital statistic approaches a critical or concerning level, the health-related application may be configured by default to present a notification to the child to take certain actions or notify another party (e.g., a parent) regarding the relevant vital statistic level. During restricted mode, even if other applications are disabled from presenting notifications or communicating with other devices, the health-related application may be configured to continue presenting such notifications or communications to others.

[0130] In addition, if the communication notifications from other devices to the satellite device 138 are repeated attempts, the restricted mode configuration may allow these communication notifications to break through the restricted mode. For example, a parent may make a first phone call attempt to the satellite device 138 from, for example, the mode controller device 140. Since the restricted mode is active, the first call may be blocked. However, a second consecutive phone call from the same device within a threshold amount of time (e.g., 30 seconds) may break through the restricted mode. The satellite device 138 may allow the second phone call to present a notification on the display, which the child may see and interact with to answer the phone call or perform other actions (e.g., respond with a default text message or allow the phone call to go to voicemail). The restricted mode configuration may also allow repeated attempts of different communication types to break through. For example, a person may send a text message to a child soon after a phone call. The satellite device 138 may block the phone call, but if the text message arrives within a threshold time after the phone call, the text message may be allowed to be notified.

[0131] At step 810, satellite device 138 may be configured to determine that the current time is outside the time period defined by the restricted mode configuration. In some embodiments, satellite device 138 may receive the restricted mode configuration and store the end time of the restricted mode. When the restricted mode end time is reached, satellite device 138 may automatically disable the restricted mode, as shown in step 812. Disabling restricted mode removes all specified restrictions and allows the child to access the previously disabled feature set.

[0132] Fig. 9 9 is a flow chart illustrating another process 900 used by a computing device to enforce context-based restrictions on itself. For example, process 900 may be performed by a computing device (eg, satellite device 138).

[0133] As mentioned above about Figure 1 As described, satellite devices 138 may be included in device group 180 along with mode controller device 140 such that mode controller device 140 may be used to implement restricted mode configurations on satellite devices 138. In addition, a parent may create a user account family that includes the parent's user account with permission to generate restricted mode configurations and implement those configurations on the child's satellite devices. The parent may configure the user account family such that any device the child logs into with the child's own user account becomes a satellite device. In some embodiments, the child's satellite device may only receive and apply restricted mode configurations from devices logged into using the parent's user account.

[0134] Process flow 900 shows that at step 902, satellite device 138 receives a data message including a restricted mode configuration for managing satellite device 138. As described above, a parent may implement a restricted mode configuration for a child's satellite device. Satellite device 138 may receive the restricted mode configuration via server device 110, as described above with respect to Figure 2 Satellite device 138 may also receive a restricted mode configuration in response to a request from satellite device 138. For example, a user may activate satellite device 138 for the first time after manufacture or purchase. A user (e.g., a child) may log into satellite device 138 using a user account. Satellite device 138 may determine that the logged in user account belongs to a user who needs a restricted mode configuration for any of the user's devices or has been previously designated as a user who needs a restricted mode configuration for any of the user's devices.

[0135] Thus, satellite device 138 may request server device 110 to retrieve a restricted mode configuration using a specific controller device identifier associated with the child's logged-in user account or a parent's user account identifier. In other embodiments, mode controller device 140 will detect (or server device 110 will inform mode controller device 140) that a child has logged into satellite device 138 and that a restricted mode configuration should be used to manage the child's use. In still other embodiments, the restricted mode configuration may be transmitted directly from mode controller device 140 via a direct connection between mode controller device 140 and satellite device 138, as described above with respect to Figure 3 described.

[0136] In some embodiments, the satellite device 138 determines that the restricted mode configuration originated from the mode controller device 140 and was defined by a user of the mode controller device 140. The satellite device 138 may be configured to identify an account identifier associated with the mode controller device 140 for the parent based on the data message at step 904. In one embodiment, the satellite device 138 may determine the originating device that transmitted the restricted mode configuration. This may be, for example, the mode controller device 140. In the event that the mode controller device 140 has been identified, the satellite device 138 may be configured to determine the account identifier of the user of the mode controller device 140.

[0137] Satellite device 138 may be configured to determine that the account identifier is a member of a trusted group of account identifiers at step 906. For example, satellite device 138 may identify the parent's account identifier as part of the user account family described above that was established by the parent. Satellite device 138 may also recognize that the account identifier has associated permissions that enable it to apply the restricted mode configuration to satellite device 138. Satellite device 138 may further identify the account identifier as belonging to a trusted account identifier group (e.g., a user family) that also includes the user account identifier currently used to operate satellite device 138.

[0138] In response to determining that the account identifier associated with the received restricted mode configuration is authentic or authorized, satellite device 138 may be configured to automatically apply the restricted mode configuration at step 908. In one embodiment, satellite device 138 implements the restricted mode configuration to disable one or more features of the satellite device in certain contexts (e.g., during times of day when a child is at school).

[0139] Graphical User Interface

[0140] The present disclosure describes above various graphical user interfaces (GUIs) for implementing various features, processes, or workflows. These GUIs can be presented on various electronic devices, including but not limited to laptop computers, desktop computers, computer terminals, television systems, tablet computers, e-book readers, and smart phones. One or more of these electronic devices may include a touch-sensitive surface. The touch-sensitive surface can process multiple simultaneous input points, including processing data related to the pressure, degree, or position of each input point. Such processing can facilitate gestures performed using multiple fingers, including pinching and swiping.

[0141] When the present disclosure refers to "selecting" a user interface element in a GUI, these terms are understood to include clicking or "hovering" over a user interface element with a mouse or other input device, or touching, tapping, or gesturing on a user interface element with one or more fingers or a stylus. A user interface element may be a virtual button, menu, selector, switch, slider, brush, knob, thumbnail, link, icon, radio button, check box, and any other mechanism for receiving input from a user or providing feedback to a user.

[0142] privacy

[0143] As described above, one aspect of the present technology is to collect and use data available from specific and legitimate sources to configure context-based restrictions for computing devices. The present disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, data or records related to the user's health or fitness level (e.g., vital statistics measurements, medication information, exercise information), date of birth, or any other personal information.

[0144] Restricted mode configurations (e.g., configurations based on time, geographic location, device environment / conditions, etc.) that may be specified by the user and any communications corresponding to those configurations may be encrypted in an end-to-end encrypted manner as described herein. In this way, the configuration data can only be accessed by devices associated with the user (e.g., and / or the child) and not by a server (e.g., server 110), thereby protecting user privacy.

[0145] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to configure context-based restrictions for computing devices. Therefore, the use of such personal information data enables users to more conveniently configure context-based restrictions for computing devices. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used according to the user's preferences to provide insights into their overall health, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0146] This disclosure anticipates that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities will be expected to implement and consistently apply privacy practices that are generally recognized as meeting or exceeding the requirements of the industry or government that maintain user privacy. Such information about the use of personal data should be prominently accessible to users and should be updated as the collection and / or use of data changes. The user's personal information should be collected only for legitimate use. In addition, such collection / sharing should only occur after receiving user consent or other legal basis specified in applicable law. In addition, such entities should consider taking any necessary steps to defend and safeguard access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted for specific types of personal information data collected and / or accessed and made applicable to applicable laws and standards, including specific considerations that are exclusive to jurisdictions that can be used to impose higher standards. For example, in the United States, collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0147] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, in the case of configuring context-based restrictions for a computing device, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" to participate in the collection of personal information data during registration for a service or any time thereafter. In another example, a user may choose not to provide device data or account data for configuring context-based restrictions for a computing device. In yet another example, a user may choose to limit the length of time that device and account data are maintained or completely block the development of a restricted mode configuration. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the application accesses the personal information data, so as to configure context-based restrictions for the computing device.

[0148] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods such as differential privacy, where appropriate.

[0149] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, a restricted mode configuration may be delivered based on collected non-personal information data or minimal personal information, such as content that is processed only on the user's device or other non-personal information accessible to the restricted mode configuration creator's device.

[0150] Exemplary System Architecture

[0151] Fig.10 It is achievable Figures 1 to 91000. The computing device 1000 may include a memory interface 1002, one or more data processors, an image processor, and / or a central processing unit 1004, and a peripheral device interface 1006. The memory interface 1002, one or more processors 1004, and / or the peripheral device interface 1006 may be separate components or may be integrated into one or more integrated circuits. The various components in the computing device 1000 may be coupled via one or more communication buses or signal lines.

[0152] Sensors, devices, and subsystems can be coupled to the peripheral interface 1006 to facilitate a variety of functions. For example, a motion sensor 1010, a light sensor 1012, and a proximity sensor 1014 can be coupled to the peripheral device interface 1006 to facilitate orientation, lighting, and proximity functions. Other sensors 1016 can also be connected to the peripheral interface 1006, such as a global navigation satellite system (GNSS) (e.g., a GPS receiver), a temperature sensor, a biometric sensor, a magnetometer, or other sensing device to facilitate related functions.

[0153] The camera subsystem 1020 and optical sensor 1022 (e.g., a charge coupled device (CCD) or complementary metal oxide semiconductor (CMOS) optical sensor) may be used to facilitate camera functions, such as recording photos and video clips. The camera subsystem 1020 and optical sensor 1022 may be used to collect images of the user to be used during user authentication, for example, by performing facial recognition analysis.

[0154] Communication functions may be facilitated by one or more wireless communication subsystems 1024, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of communication subsystems 1024 may depend on the communication network over which computing device 1000 is intended to operate. For example, computing device 1000 may include a subsystem designed to communicate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth® network. TM The wireless communication subsystem 1024 may include a network-operated communication subsystem 1024. Specifically, the wireless communication subsystem 1024 may include a hosting protocol so that the device 1000 can be configured as a base station for other wireless devices.

[0155] The audio subsystem 1026 may be coupled to a speaker 1028 and a microphone 1030 to facilitate voice-enabled functions such as speaker recognition, voice replication, digital recording, and telephony functions. For example, the audio subsystem 1026 may be configured to facilitate processing voice commands, voiceprints, and voice authentication.

[0156] I / O subsystem 1040 may include touch surface controller 1042 and / or other input controller 1044. Touch surface controller 1042 may be coupled to touch surface 1046. Touch surface 1046 and touch surface controller 1042 may detect contact and movement or interruption thereof, for example, using any of a variety of touch-sensitive technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch surface 1046.

[0157] Other input controllers 1044 may be coupled to other input / control devices 1048, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointer devices such as styluses. One or more buttons (not shown) may include up / down buttons for volume control of the speaker 1028 and / or microphone 1030.

[0158] In one implementation, pressing the button for a first duration may unlock the touch surface 1046; and pressing the button for a second duration longer than the first duration may turn the power of the computing device 1000 on or off. Pressing the button for a third duration may activate a voice control or voice command module that enables a user to speak commands into the microphone 1030 to cause the device to execute the spoken commands. The user may customize the function of one or more buttons. For example, the touch surface 1046 may also be used to implement virtual or soft buttons and / or a keyboard.

[0159] In some implementations, the computing device 1000 can present recorded audio and / or video files, such as MP3, AAC, and MPEG files. In some implementations, the computing device 1000 can include an iPod, for example. TM MP3 player function.

[0160] The memory interface 1002 may be coupled to a memory 1050. The memory 1050 may include a high-speed random access memory and / or a non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and / or a flash memory (e.g., NAND, NOR). The memory 1050 may store an operating system 1052, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system, such as VxWorks.

[0161] The operating system 1052 may include instructions for handling basic system services and for performing hardware-related tasks. In some implementations, the operating system 1052 may be a kernel (e.g., a UNIX kernel). In some implementations, the operating system 1052 may include instructions for performing voice authentication. For example, the operating system 1052 may implement features for active change detection for geospatial entities, such as reference Figures 1 to 9 described.

[0162] The memory 1050 may also store communication instructions 1054 that facilitate communication with one or more additional devices, one or more computers, and / or one or more servers. The memory 1050 may include graphical user interface instructions 1056 that facilitate graphical user interface processing; sensor processing instructions 1058 that facilitate sensor-related processing and functions; phone instructions 1060 that facilitate phone-related processes and functions; electronic message processing instructions 1062 that facilitate electronic message processing-related processes and functions; web browsing instructions 1064 that facilitate web browsing-related processes and functions; media processing instructions 1066 that facilitate media processing-related processes and functions; GNSS / navigation instructions 1068 that facilitate GNSS and navigation-related processes and instructions; and / or camera instructions 1070 that facilitate camera-related processes and functions.

[0163] The memory 1050 may store software instructions 1072 that facilitate other processes and functions, such as processes and functions for active change detection of geospatial entities, such as reference Figures 1 to 9 described.

[0164] The memory 1050 may also store other software instructions 1074, such as network video instructions that facilitate processes and functions related to network video; and / or network shopping instructions that facilitate processes and functions related to network shopping. In some specific implementations, the media processing instructions 1066 are divided into audio processing instructions and video processing instructions to facilitate processes and functions related to audio processing and processes and functions related to video processing, respectively.

[0165] Each of the instructions and applications identified above may correspond to an instruction set for performing one or more of the functions described above. These instructions need not be implemented as separate software programs, processes, or modules. Memory 1050 may include additional instructions or fewer instructions. Furthermore, various functions of computing device 1000 may be implemented in hardware and / or software, including in one or more signal processing and / or application specific integrated circuits.

Claims

1. A method comprising: receiving, by a computing device, a first user input requesting to exit a restricted mode of the computing device, wherein one or more first features of the computing device are disabled during the restricted mode; In response to the first user input: displaying a first notification on a display of the computing device, the first notification indicating that an exit from the restricted mode will be reported to a controller device that enabled the restricted mode on the computing device; receiving, by the computing device, a second user input canceling an exit from the restricted mode; In response to the second user input: removing the first notification and continuing execution in the restricted mode; receiving, by the computing device, a third user input requesting to exit the restricted mode of the computing device; in response to the third user input: displaying a second notification on the display of the computing device, the second notification indicating that an exit from the restricted mode will be reported to the controller device that enabled the restricted mode on the computing device; receiving, by the computing device, a fourth user input confirming exiting the restricted mode; as well as In response to the fourth user input: initiating a restricted mode exit process to cause the computing device to exit from the restricted mode; as well as The exit from the restricted mode is reported to the controller device that enabled the restricted mode on the computing device. 2 . The method of claim 1 , wherein the first user input comprises selecting a restricted mode exit control from the display of the computing device. 3 . The method of claim 2 , wherein no controls on the display of the computing device other than the restricted mode exit control are responsive to user input while in the restricted mode.

4. The method of claim 2, wherein at least one additional control is displayed on the display of the computing device while in the restricted mode, and wherein selection of any particular one of the at least one additional control causes the notification to be displayed rather than launching an application associated with the particular control.

5. The method according to claim 1, further comprising: Upon completion of the restricted mode exit process: sending a usage report to the controller device indicating activities performed on the computing device after exiting from the restricted mode. The method of claim 1 , wherein at least one application is allowed to operate while the computing device is in the restricted mode.

7. A non-transitory computer readable medium comprising one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving, by a computing device, a first user input requesting to exit a restricted mode of the computing device, wherein one or more first features of the computing device are disabled during the restricted mode; In response to the first user input: displaying a first notification on a display of the computing device, the first notification indicating that an exit from the restricted mode will be reported to a controller device that enabled the restricted mode on the computing device; receiving, by the computing device, a second user input canceling an exit from the restricted mode; In response to the second user input: removing the first notification and continuing execution in the restricted mode; receiving, by the computing device, a third user input requesting to exit the restricted mode of the computing device; in response to the third user input: displaying a second notification on the display of the computing device, the second notification indicating that an exit from the restricted mode will be reported to the controller device that enabled the restricted mode on the computing device; receiving, by the computing device, a fourth user input confirming exiting the restricted mode; as well as In response to the fourth user input: initiating a restricted mode exit process to cause the computing device to exit from the restricted mode; as well as The exit from the restricted mode is reported to the controller device that enabled the restricted mode on the computing device. 8 . The non-transitory computer-readable medium of claim 7 , wherein the first user input comprises selecting a restricted mode exit control from the display of the computing device.

9. The non-transitory computer-readable medium of claim 8, wherein while in the restricted mode, no controls on the display of the computing device are responsive to user input except for the restricted mode exit control.

10. The non-transitory computer-readable medium of claim 8, wherein when in the restricted mode, at least one additional control is displayed on the display of the computing device, and wherein selection of any particular control of the at least one additional control causes display of the notification rather than launching an application associated with the particular control.

11. The non-transitory computer readable medium of claim 7, wherein the operations further comprise: Upon completion of the restricted mode exit process: sending a usage report to the controller device indicating activities performed on the computing device after exiting from the restricted mode.

12. A computing device comprising: one or more processors; as well as A non-transitory computer readable medium comprising one or more sequences of instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving a first user input requesting to exit a restricted mode of the computing device, wherein one or more first features of the computing device are disabled during the restricted mode; In response to the first user input: displaying a first notification on a display of the computing device, the first notification indicating that an exit from the restricted mode will be reported to a controller device that enabled the restricted mode on the computing device; receiving a second user input canceling an exit from the restricted mode; In response to the second user input: removing the first notification and continuing execution in the restricted mode; receiving, by the computing device, a third user input requesting to exit the restricted mode of the computing device; in response to the third user input: displaying a second notification on the display of the computing device, the second notification indicating that an exit from the restricted mode will be reported to the controller device that enabled the restricted mode on the computing device; receiving, by the computing device, a fourth user input confirming exiting the restricted mode; and In response to the fourth user input: initiating a restricted mode exit process to cause the computing device to exit the restricted mode; and The exit from the restricted mode is reported to the controller device that enabled the restricted mode on the computing device.