JP2021523451A - Device usage management - Google Patents

Abstract

The device receives a time-based limit for use by a first user for an application, website, or device-level feature. The device receives encrypted data indicating its use by a first user on a second device for an application, website, or device level feature. The device is subject to time-based limits at least one of the first user's use on the second device, or the first user's use on the device, for an application, website, or device-level feature. Determined to have violated. The device provides a notification that the first user is violating the time-based limit, depending on the determination.

Description

[Cross-reference of related applications]
This application is in the interest of US Patent Provisional Application Nos. 62 / 668,814 entitled "MANAGEING DEVICE USAGE TIME" filed May 8, 2018, and "MANAGEING DEVICE" filed June 3, 2018. It claims the interests of U.S. Patent Application No. 62 / 679,893 entitled "USAGE", each of which is incorporated herein by reference in its entirety and for all purposes. Consists of part of the application.

[Technical field]
This specification generally relates to the operation of a device, including managing device usage time.

As users spend more and more time interacting with computing devices, such as phones, tablets, computers, etc., the appropriate user should interact with their computing device (eg, per day). Concerns about the amount of time and possible concerns related to excessive use of computing devices will increase.

Some features of the subject technology are shown in the appended claims. However, for illustration purposes, some embodiments of the subject technology are shown in the figures below.

An exemplary network environment for managing device usage time with one or more implementations is shown.

Illustrative devices that can implement a system for managing device usage time with one or more implementations are shown.

An exemplary architecture of a system for managing personal device usage time with one or more implementations is shown.

Shown is an exemplary architecture of a system for managing device usage time of another user in one or more implementations.

Shown is an exemplary architecture of a system for managing personal device usage time based on time-based limits set by another user in one or more implementations.

Shown is an exemplary architecture of a system for managing device usage time in a corporate configuration with one or more implementations.

An exemplary architecture of a system for remote management of components for managing device time usage with one or more implementations is shown.

An exemplary process for managing device usage time with one or more implementations is shown.

Another exemplary process for managing device usage time with one or more implementations is shown.

Shown is an exemplary electronic system in which aspects of the subject technology can be implemented in one or more implementations.

The detailed description described below is intended as an explanation of the various configurations of the subject technology and is not intended to represent the only configuration in which the subject technology can be practiced. The accompanying drawings are incorporated herein and form part of a detailed description. The detailed description includes specific details to provide a complete understanding of the subject's technology. However, the art of the subject is not limited to the particular details presented herein and can be practiced using one or more other implementations. In one or more implementations, the structures and components are shown in block diagram format to avoid obscuring the concept of the subject technology.

The user may wish to use those electronic devices (s) to limit and / or manage the amount of time spent personally. For example, a user may use a particular application / website, a particular category of application / website, and / or a particular device-level feature (eg, device display, audio, microphone, camera, sensor, accessory and / or hardware. You may want to limit your personal use of resources). In addition, the user (eg, parent) has time for another user (eg, child) to use those electronic devices (s) for, for example, applications / websites, categories, and / or device-level features. Define limits and controls, and / or conditions or goals of use by other users (eg, an hour of educational reading on the device before access to other applications is granted). You may want to do it.

The subject system sets a time-based limit on the use of personal devices or the use of devices by others (eg, children). Time-based limits may be applied across multiple devices associated with a given user. For example, the first device receives a time-based limit on user use for applications / websites (eg, application and / or website categories), or device-level features. The first device receives encrypted data indicating the user's use on the second device for an application, website, or device level feature. The first device determines that the user's use on either or both of the first and second devices violates the time-based limit. The first device provides notification that the user is violating the time-based limit.

In addition, the subject system maintains time-based limits and privacy of usage data, thereby managing usage for authorized devices (eg, users' own devices for personal usage management and / or children). Only the parent / child device) can access the usage data. For example, data indicating usage and / or restrictions may be end-to-end encrypted when communicated between devices. In the parent-child example, privacy protection may be implemented by sending an end-to-end encrypted message directly between the parent device and the child device, the message indicating restrictions and use. Alternatively or additionally, in the case of the parent-child example, the server may store the restricted data and / or the data used in an encrypted manner, and the parent device and the child device can access the server. You can access the data based on each key that is not.

In the example of personal usage management, privacy protection may be implemented by storing usage data on the server that is only accessible to the device by a known encryption key and is not available to the server. good. Alternatively or additionally, restricted and / or personal use data may be synchronized across multiple devices of the user, for example using a device-to-device communication protocol such as Bluetooth that bypasses the server.

Unauthorized devices (including, for example, servers) that are controlled for use by others (eg, children) or personally controlled for use based on these privacy implementations. Access to restricted data and / or usage data is prevented.

FIG. 1 shows an exemplary network environment for managing device usage time with one or more implementations. However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

The network environment 100 includes electronic devices 102, 103, and 104 (hereinafter, 102 to 104), a network 106, and a server 108. The network 106 may, for example, communicatively (directly or indirectly) connect any two or more of the electronic devices 102-104 and / or the server 108. In one or more implementations, the network 106 may be a network of interconnected devices, including the Internet or communicatively coupled to the Internet. For illustration purposes, the network environment 100 is shown in FIG. 1 to include electronic devices 102-104 and a single server 108. However, the network environment 100 can include any number of electronic devices and any number of servers.

One or more of the electronic devices 102-104 are portable computing devices such as laptop computers, smartphones, peripheral devices (eg digital cameras, headphones), tablet devices, smart watches, wearable devices such as bands, etc. Or, for example, WLAN wireless communication, cellular wireless communication, Bluetooth® wireless communication, Zigbee® wireless communication, near field communication (NFC) wireless communication, and / or other wireless communications. It may be any other suitable device, including one or more wireless interfaces, such as. In FIG. 1, by way of example, the electronic device 102 is shown as a smartphone, the electronic device 103 is shown as a smartwatch, and the electronic device 104 is shown as a laptop computer. Each of the electronic devices 102-104 may be the device described below with respect to FIG. 2 and / or the electronic system described below with respect to FIG. 10 and / or may include all or part of them.

The server 108 may be the electronic system described below with respect to FIG. 10 and / or may include all or part thereof. The server 108 can include one or more servers, such as a cloud of servers, which can be used to facilitate limiting the use of electronic devices 102-104. The user has, for example, a registered user account (eg, a cloud-based service provider account that manages usage) and is logged in to that user account with two or more of electronic devices 102-104. In connection with, two or more of the electronic devices 102-104 can be used. Server 108 may store encrypted data that can be accessed via a key by each user's device in order to limit and / or manage personal device usage time.

In another embodiment, the first user (eg, the parent using the electronic device 104) is the device usage time of the second user (eg, the child using one or more of the electronic devices 102-103). Can be restricted and / or managed. The corresponding time limit and data usage information may be communicated between the electronic devices 102 to 104 in a private manner. For example, this information may be stored on the server 108 as encrypted data accessible via a key by electronic devices 102-104. Alternatively or additionally, such information may be transmitted directly between the electronic devices 102-104 using a message forwarding system, so that the information is not stored on the server 108.

For illustration purposes, a single server 108 is shown and described for various operations such as storing encrypted data associated with time-based limits and / or data use. However, these and other operations described herein may be performed by one or more servers, for example, in one or more different data centers, and each different operation may be performed on the same server or different servers. May be performed by.

FIG. 2 shows an exemplary device that can implement a system for managing device usage time in one or more implementations. For example, the device 200 of FIG. 2 can correspond to any of the electronic devices 102 to 104 of FIG. However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

The device 200 may include a host processor 202, a memory 204, and a communication interface 206. Host processor 202 may include suitable logic, circuits, and / or codes that allow it to process data and / or control the operation of device 200. In this regard, it may be possible for the host processor 202 to provide control signals to various other components of the device 200. Host processor 202 may also control data transfer over various sections of device 200. In addition, the host processor 202 can allow an operating system implementation or otherwise execute code to manage the operation of the device 200. In the subject system, the host processor 202 may implement a software architecture for managing device usage time, as further described below in connection with FIGS. 3-7.

Memory 204 may include appropriate logic, circuits, and / or codes that allow storage of various types of information such as received data, generated data, codes, and / or configuration information. Memory 204 can include, for example, random access memory (RAM), read-only memory (ROM), flash, and / or magnetic storage. In one or more implementations, memory 204 may store an application for managing personal device usage time and / or an application for managing device usage time for another user (eg, a child). ..

The communication interface 206 can include suitable logic, circuits, and / or codes that enable wired or wireless communication, such as between any of the electronic devices 102-104 and the server 108, over the network 106. .. The communication interface 206 may include, for example, one or more of a Bluetooth communication interface, a cellular interface, an NFC interface, a Zigbee communication interface, a WLAN communication interface, a USB communication interface, or generally any communication interface.

In one or more implementations, one or more of the host processor 202, memory 204, communication interface 206, and / or one or more parts thereof are implemented in hardware (eg, subroutines and code). Often, hardware (eg, Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Logic Device (PLD), controller , State machines, gate logic, discrete hardware components, or any other suitable device), and / or a combination of both.

FIG. 3 shows an exemplary architecture 300 of a system for managing personal device usage time in one or more implementations. For example, architecture 300, including its various components 302-334, is implemented by one or more software modules running on host processor 202 of electronic device 102 (or, for example, on any of electronic devices 102-103). Can be implemented. In another embodiment, architecture 300 can be implemented by one or more software modules implemented by custom hardware (eg, one or more coprocessors). However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

Architecture 300 includes database 320, which has a database used 322 and a configuration database 326. The usage database 322 may store usage data corresponding to the usage time by the user of the electronic device 102 with respect to the application, website, application and / or website and / or device level function category. The displayed applications, websites, applications and / or website categories, and / or device-level features (eg, which application, website, application and / or website category, and / or device the user has. It may be preselected by the user (if specifying whether to display the level function). For example, the displayed applications, websites, applications and / or website categories, and / or device-level features can be registered user accounts (s) (eg, cloud-based service provider accounts that manage usage). ), And may be preselected by the user based on different categories associated with the user account (s) (eg, work, individual). Alternatively, all applications, websites, applications and / or website categories associated with use, and / or device-level features may be displayed.

The configuration database 326 refers to the electronic device 102 (eg, in connection with a registered user account) for one or more applications, websites, application and / or website categories, and / or device-level features. Time-based limits set by the user (eg, quotas and / or time limits) can be stored. In one or more implementations, the database 320 can be used to synchronize usage time and time-based limits across multiple devices associated with a user (eg, electronic devices 102-103). Cloud mirroring component 324 including.

The personal configuration editor 318 may provide a user interface for setting and / or adjusting time-based limits. The user interface provided by the Personal Configuration Editor 318 sets individual (eg different) time-based limits for applications, websites, categories (eg, applications and / or websites), and / or device-level features. It may include a user interface element to do so.

In this regard, the time-based limit may correspond to the quota, and the user specifies, through the user interface, a certain amount of time that is allowed to be used. The usage time by the user is applied to the quota and determines when the quota is reached. Alternatively or additionally, time-based limits may correspond to time limits, where the user specifies, through the user interface, how long personal use is permitted and prohibited. Examples of time-based time limits include daily limits (eg, daily limited use from 10 pm to 2 pm), weekly limits (eg, the entire specific day of the week (s). , Or a limited use of a specified time), a monthly limit (eg, the entire specific day (s) of a month, or a limited use of a specified time), etc. Not limited to these. In addition, time-based time limits may be set on an iterative basis or a single occurrence basis.

In addition, the limit may be based on quantity (eg, as opposed to a predetermined time). For example, the limit can specify the number of specific applications, websites, categories, and / or device-level features. In another embodiment, the limit is the default number of times a particular action for an application, website, category, and / or device-level feature can be performed (eg, receive notifications, send messages, pick up devices). It can be set to specify the number of times, etc.).

In one or more implementations, the additional restrictions may be based on the geographic location of the electronic device. For example, restrictions on specific device-level features (eg, cameras, microphones) may be specified based on geofencing to a given location (eg, museums, cinemas). Geography-based restrictions may also be specified for applications, websites, and / or categories (eg, social networking in public parks). In one or more implementations, geography-based restrictions specify the location associated with the user (eg, work, school) based on information local to the user's device (eg, contact address information). May be done. However, the identities and / or associations of those locations are not provided or otherwise shared with the server (eg, server 108) to protect the privacy of the user.

In addition, limits may be specified, for example, with respect to device-related environmental conditions. For example, if a WiFi connection is not available (for example, indicating that a device will be needed to use cellular data for network-based features), the user disables network activity (for example). For example, you can choose to set restrictions on (connecting to the Internet for applications and / or websites). In another embodiment, if the electronic device 102 detects an unknown (eg, not the user's contact) nearby device (eg, via near field communication, Bluetooth), the user has the device level capability. May have restrictions specified to disable or otherwise adjust (eg, disable wireless file transfer or limit file transfer to contacts). In another embodiment, the user should or should disable the use of the device based on the power status of the device (eg, low battery, plugged in, or unplugged). You may specify to limit it.

In addition, the user specifies contact-based restrictions on a user's specific contacts (for example, for personal management) or another user's specific contacts (for example, for child management). You may. For example, a user may specify not to communicate with a particular contact (eg, for either personal management or a child), or (eg, for a particular application, website, category, and / or). Communication with specific contacts may be encouraged (as a goal / condition before allowing device-level features).

In one or more implementations, the various types of restrictions described above can be combined to form compound restrictions. For example, using any two or more of the limits (eg, time, quantity, geographic location, device environment / conditions, and / or contacts), each limit (s) for each type of limit. ), A compound restriction can be formed. For example, a user can specify a compound limit that does not communicate with a particular contact, based on a time-based time limit (eg, prohibition of communication with person X from 10 pm to 2 am). In another embodiment, the user may specify a compound restriction that prohibits social networking between 10 am and 2 pm on Sundays when geo-fenced in a public park.

Various limits that may be specified by the user (eg, time, quantity, geographic location, device environment / conditions, contact-based limits), and any use corresponding to those limits are described herein. As such, it may be synchronized by end-to-end encryption across multiple devices of the user and / or family devices (eg, for child-based restrictions). In this way, the restriction and / or usage data is only accessible by the device associated with the user (eg, and / or children) and not by the server (eg, server 1018). Protect user privacy.

The user interface provided by the Personal Configuration Editor 318 is a time-based limit (eg, quota and / or time limit) for specific applications, websites, applications and / or website categories, and / or device-level features. Allows the user to set. For applications and / or websites, users may specify their respective time-based limits for different applications and / or websites. For example, the user can specify a two-hour quota for the first social networking application and / or a time limit for the first news website (eg, no use from 11:00 pm to 5:00 am). Can be defined. In one or more implementations, when time-based limits are set for a particular application (eg, a first social networking application), Architecture 300 is a website version of the application and / or an extension application of the application. The same time-based limits can be automatically applied to versions. Similarly, time-based limits for a particular website can be automatically applied to the application version and / or extended application version of the website. In doing so, Architecture 300 can determine that the website (eg, the domain hosting the website) corresponds to the application and / or extension. In addition, websites are described herein with respect to device time management, website usage limits, and time-based limit settings, but such controls, limits, and time-based settings are described on the Web. It may be applied to the domain hosting the site.

With respect to categories, the user interface provided by the Personal Configuration Editor 318 allows users to specify time-based limits (eg, quotas or time limits) for application and / or website categories. Categories correspond to logical grouping of applications and / or websites. Examples of categories are books, business, catalogs, education, entertainment, finance, food & drinks, games, health & fitness, lifestyle, medical care, music, navigation, news, photos & videos, productivity, references, social networking. , Sports, travel, utilities, and weather (eg, in one or more geographic areas), but not limited to these. In this way, the user can specify a time-based quota and / or a time-based time limit for a particular category, such as social networking. Time-based quotas or time limits may apply to applications, websites, and / or extended applications (and combinations thereof) that are classified as social networking applications.

In addition to the categories mentioned above, applications and / or websites may be categorized based on one or more broad topics associated with the user, such topics, for example, without identifying the user. , Roughly correlates with user interests. Thus, the user may specify a time-based quota and / or a time-based time limit (eg, via the user interface provided by the personal configuration editor 318) for a particular topic, eg, a sport. can. Time-based quotas or time limits may apply to content within applications, websites, and / or extended applications (and combinations thereof) that are classified as sports.

In one or more implementations, the application and / or website classification is to the default information provided by the application / website developer (eg, as part of the application installation or as one of the default website information. It may be based on (as a part). Alternatively or additionally, application and / or website classifications may be specified by the user (eg, user classification of applications on the device, user-defined bookmarks).

The user interface provided by the personal configuration editor 318 can further allow the user to specify time-based limits (eg, quotas or time limits) for device-level features. For example, device-level features can be one or more of overall device usage and / or use of specific device features (eg, displays, audio, microphones, cameras, sensors, accessories, and / or hardware resources). May be related. In this way, the user is time-based for a particular device-level feature, eg, total audio time (eg, 3 hours per day), or audio-based time limit (eg, no audio after 11 pm). You can specify the quota. Therefore, time-based quotas and / or time limits can be applied to audio output. In addition to the quota or time limit, the user interface can limit the number of times content (eg, audio or music video) is consumed. In addition, different limits can be set for different hardware components (eg, 1 hour for earphones, 2 hours for phone speakers).

A device-level framework may be used to implement time-based limits for device-level features. For example, a module may be implemented that provides permission for each application to use the corresponding device-level features (eg, audio, video). In this regard, the module can provide device-level functionality based on its limited range of use. For example, when an audio module reaches a time-based limit based on usage time, it can define output levels (eg, maximum and minimum volume levels) rather than simply turning audio on and off. .. In one or more implementations, device-level features may be grouped with applications and / or websites such that time-based limits and use of device-level features are based on their respective applications and / or websites. Good (for example, set a time-based limit for the video / audio features of a music application).

After the user sets time-based limits via the user interface, those time-based limits may be written to the configuration database 326. In addition, the personal configuration editor 318 accesses the configuration database 326 to display the currently set time-based limits for the user and / or the time-based entered by the user via the user interface. The configuration database 326 can be updated based on adjustments to the limits of.

Architecture 300 further includes a personal use viewer 316 that is coupled to the usage management module 328 and may provide a user interface for viewing usage times. For example, the user interface provided by the Personal Use Viewer 316 may include overall device usage time, applications (s) (eg, per application), websites (eg, per website), device level features (eg, per website). It is possible to indicate the usage time for each function) and / or for one or more of the application / website categories (for example, for each category). The user interface provided by the personal use viewer 316 can display usage for each time-based limit (eg, based on configuration database 326).

For example, usage times for applications, websites, device-level features, and / or categories may be displayed as usage rates relative to time-based quotas (eg, in graph and / or text format). In one or more implementations, the user interface provided by the Personal Use Viewer 316 is also summary information such as, but not limited to, applications, websites, and / or categories ranked by usage time. Social network application A can display 3 hours, website B can display 2 hours). Thus, the user can be aware of which applications and categories are most used, and the user can set time-based limits accordingly.

As the user continues to use the electronic device 102 (eg, by using applications, websites, and / or device-level features), its usage time is within database 320 (eg, as part of database 322 used). ) Updated and the user interface provided by the personal use viewer 316 can be altered to indicate the updated usage time. In one or more implementations, usage time is based on the time each application or website is in the foreground on an electronic device. In addition, usage time may be determined based on whether the user is interacting with the application / web content or is passively consuming the content. For example, the subject system may be passive consumption of the game (eg, the game is paused and / or the user is not interacting with the game), or (eg, there is no user dialogue, but the social network is still It can be determined that the usage time (eg, count against quota) does not apply to the passive consumption of the social network (in the foreground). However, usage time can be applied to the passive consumption of media content (eg, video or music content that typically may not require consumed user dialogue).

The user interface provided by the Personal Use Viewer 316 may be displayed as part of or separately from the user interface provided by the Personal Configuration Editor 318. Therefore, the user interface (s) provided by the Personal Use Viewer 316 and Personal Configuration Editor 318 allows the user to set time-based limits (eg, categories, applications, websites, and / or device-level features). , View the current usage time for that time-based limit, modify the time-based limit, and otherwise manage your own usage time.

Architecture 300 may operate in conjunction with each other to track usage time (eg, across multiple devices) against a time-based limit set by the user, personal organization controller 302, device management module 330, usage tracking module. It further includes 332, a usage monitoring module 334, and a usage management module 328.

In one or more implementations, the configuration data persistence module 312 can access the configuration database 326 to obtain configuration data corresponding to time-based limits. The configuration data persistence module 312 may pass configuration data via the server conduit 310, the internal transfer unit 308, the client conduit 306, and the configuration source module 304. The configuration source module 304 can then pass rules (eg, declarations, commands) to the device management module 330 based on the configuration data. Therefore, the personal organization controller 302 detects changes made to the time-based limits (eg, via the configuration data persistence module 312) and communicates these detected changes to the device management module 330. It is configured.

In addition to receiving time-based limits, the device management module 330 may be configured to access usage data across multiple devices of the user. In this regard, the usage monitoring module 334 may be configured to synchronize user activity data across multiple devices without aggregating user activity on the server (eg, server 108). In this way, user privacy can be maintained while providing the benefit of the user having his or her previous activity on any of his or her electronic devices.

Architecture 300 maintains time-based limits and privacy of usage data so that only authorized devices (eg, electronic devices 102-103) can access usage data. For example, data indicating use and / or restriction may be end-to-end encrypted when communicated between electronic devices 102-103. For example, privacy can be implemented by storing usage data on a server (eg, server 108), and usage data is only accessed by devices with encryption keys, eg, keys that are not available on the server. It is possible. Alternatively or additionally, restricted and / or personal use data may be synchronized across multiple devices of the user using inter-device communication protocols. Based on these privacy implementations, access to restricted data and / or usage data by unauthorized devices (including, for example, server 108) can be prevented.

In one or more implementations, the usage tracking module 332 may implement deduplication of device usage. The usage tracking module 332 can receive synchronized usage data from the usage monitoring module 334 and aggregate (eg, deduplication) that data with any local usage data. In this regard, if the user uses two devices at the same time (eg, associated with a registered user account), the usage tracking module 332 duplicates so that simultaneous usage times across multiple devices are not counted twice. Elimination may be performed. Concurrent use can be detected, for example, based on the time stamp data when each application is in the foreground on each electronic device. For websites, domain usage timestamp data can be used to determine when a website was visited.

The usage tracking module 332 can determine that simultaneous use of the same application (eg, or category) across different devices should not be repeatedly (eg, double) counted against a time-based quota. .. However, if each device uses a different application (eg, or category), the budget may be fully applied to the respective time-based limits for each application / category. If, in addition to certain application-based limits, time-based limits are set for overall device usage, deduplication does not have to double count the use of separate devices. In this way, if a user uses multiple different applications across multiple devices for 24 hours in a row, the subject system may be able to determine the overall device usage as 24 hours, while , The total time for each individual application can exceed 24 hours.

In one or more implementations, deduplication may be implemented at the application level and / or category level. For example, if the user is simultaneously accessing the first social network application on the electronic device 102 and the second social network application on the electronic device 103, the usage tracking module 332 is within the same category of social networking. It can be determined that the use of different applications in the social networking category should not be double counted against the time-based quotas in the social networking category.

The timing of synchronization of the user device (s) may be based on the synchronization policy. For example, if a user is associated with only a single electronic device (eg, electronic device 102), the synchronization policy may or may not synchronize with an infrequent rhythm (eg, once a week or less). It can be specified not to let. If the user is associated with multiple electronic devices (eg, electronic devices 102-103), the synchronization policy can be specified to perform synchronization more frequently (eg, once an hour). If a user is associated with multiple electronic devices and has set a time-based limit on usage time, the synchronization policy can be specified to perform synchronization more frequently (eg, once every 30 minutes). .. In addition, if the user's usage time approaches the time-based limit (for example, the difference between the aggregated usage time and the time-based quota is less than the default value), the synchronization policy becomes even more frequent (for example). For example, you can specify to perform synchronization (once every 10 minutes). Further, if it is determined that the user is accessing the user interface (s) provided by the personal use viewer 316 and / or the personal configuration editor 318 (eg, the user is viewing the use). And / or suggesting that you are adjusting time-based limits), the synchronization policy will either perform an immediate synchronization or otherwise as soon as the device (s) become available to synchronize. Can be specified to synchronize with.

As mentioned above, synchronization of usage time between multiple devices of a user can be achieved by storing encrypted data representing the usage time on the server, and multiple devices access the encrypted data. Each key has its own key for, and each key is not accessible to the server. Alternatively or additionally, the synchronization policy in some cases can specify device-to-device synchronization between multiple devices.

For example, if the user's usage time approaches a time-based limit (eg, based on meeting a default difference between two values), the synchronization policy will take into account any nearby, already awakened device (for example, based on meeting a default difference between the two values). For example, it can be specified to perform device-to-device synchronization with the electronic device 103). For example, device-to-device synchronization may be performed using protocols for nearby communication, including but not limited to Bluetooth, Near Field Communication (NFC), Wi-Fi, and the like. However, synchronization policies may not always provide to wake up nearby devices that are not awake.

On the other hand, if the user is accessing (determined to be) the user interface (s) provided by the personal use viewer 316 and / or the personal configuration editor 318 on the electronic device 102, for example, the user is currently using it. (Suggesting that you are browsing and / or adjusting time-based limits), the synchronization policy wakes up all nearby devices associated with the user and devices with those devices. You can specify to perform inter-synchronization. In one or more implementations, device-to-device synchronization can be associated with less power usage and / or less latency for server-based synchronization. In addition, even if device-to-device synchronization is performed (eg, every 10 minutes), the synchronization policy still specifies the corresponding server-based synchronization that is performed (eg, every hour). be able to.

With respect to user monitoring of usage time, the device management module 330 may provide configuration source module 304 (eg, associated with a registered user account) with usage time related status, event, or message data. can. The configuration source module 304 may pass this data to the client conduit 306, the internal transfer unit 308, the server conduit 310, and the used data persistence module 314. The usage data persistence module 314 stores data records (s) indicating each user's usage time (s) for applications, websites, categories, and / or device-level features and uses those records. It can be stored in the database 322. In this way, usage data across multiple devices of the user can be maintained. The user can view the usage time information, for example, by calling the interface (s) provided by the personal organization controller 302 and the personal configuration editor 318.

In one or more implementations, the client conduit 306, internal transfer unit 308, and server conduit 310 are used data (eg, personal use described with respect to architecture 300, another described below with respect to FIGS. 4-5. It can be configured to process different sources of user data and / or in-house usage data described below with respect to FIG. For example, the client conduit 306, the internal transfer unit 308, and the server conduit 310 can provide scaling and flexibility for different sources of data used. Sources of different data are further described below with respect to FIG.

In addition, the device management module 330, which works with the usage tracking module 332, may be configured to detect the time at which a time-based limit breach has occurred. As mentioned above, the device management module 330 and the usage tracking module 332 may have access to aggregated (deduplicated) usage data for multiple devices of the user (eg, configuration source). It may have access to time-based limits (received from module 304). The device management module 330 and the usage tracking module 332 increase the time-based limit based on the aggregated usage time in order to detect when a time-based limit violation occurs in consideration of the aggregated usage time. It is configured to apply. For example, a breach can be detected if the usage time exceeds the quota or if the usage time is not within the time limit. If a breach is detected, the device management module 330 can facilitate providing notification of the breach and / or prohibit further use of applications, websites, categories, or device-level features.

With respect to notifications, the device management module 330 may provide the electronic device 102 with a display of notifications indicating that personal usage time has been reached for each application, website, or category. The notification may include an interface element for directing the user to the user interface provided by the personal configuration editor 318. In this way, the user can modify the time-based limit in response to the notification, for example by increasing the quota or adjusting the time range of the time limit.

In response to the breach, the device management module 330 can further prevent users from accessing their respective applications (or extended applications), websites, categories, and / or device-level features. For example, the device management module 330 can block access to the corresponding application (or extension), website, or device level function. By doing so, the device management module 330 can display an icon (eg, an overlay such as a shield icon) that visually indicates that access is not permitted. In one or more implementations, blocks and / or icons may be implemented for multiple input points to an application or website (eg, a shield on the application launch interface, URL launch interface, extended launch interface). Overlay on). In this way, the icon (eg, shield) can track applications, websites, categories, and / or device-level features across the operating systems of a user's multiple devices. In one or more implementations, the icon is for unblocking applications, websites, categories, and / or device-level features (eg, by directing the user to the user interface provided by Personal Configuration Editor 318). It may be displayed with a user interface element.

In one or more implementations, block exceptions may apply to a default set of applications, websites, and / or time-based limits, even if they violate time-based limits. For example, if a user specifies a time-based limit on overall device usage, the applications in the default set (eg, system applications such as phones, alarm clocks, maps, etc.) remain available to the user and block. It may not be done. The default set of applications is at the application, website, and / or device level where the user (eg, associated with a category), even if the usage time violates the corresponding time-based limit. It may be user-selectable so that you can specify whether the feature should be blocked.

In one or more implementations, the usage monitoring module 334 can detect user deletion of the application. The electronic device 102 can remove local data that identifies the application (eg, removes the application ID, activates event information, and so on). However, the personal organization controller 302 may modify or otherwise maintain a record of usage time (eg, interval / duration) for the category corresponding to the application.

Alternatively or additionally, the usage monitoring module 334 may detect user deletions in the browser history corresponding to the website. The electronic device 102 can remove local data that identifies the browser history corresponding to the website (eg, remove domain name data). However, the personal organization controller 302 may modify or otherwise maintain a record of usage time (eg, interval / duration) for the category corresponding to the website.

In one or more implementations, it is possible to associate a particular device with multiple users. For example, the electronic device 104 (eg, exemplified as a laptop) may be shared by multiple users, with each user having their own user account (eg, a cloud-based service provider account that manages usage). Have. Thus, if a first user logs in to their respective cloud-based account using the electronic device 104, Architecture 300 can manage personal device usage time for that first user. .. Further, if the second user then logs in to his cloud-based account using the electronic device 104, the architecture 300 can manage the personal device usage time for that second user.

Alternatively or additionally, the electronic device 104 can perform local management of personal device usage time, for example, if the user does not log in to his or her cloud-based account using the electronic device 104. For example, electronic device 104 can implement software configured to manage one or more local user accounts for local management of personal usage time. Therefore, if a third user simply uses the device (for example, by logging in to their cloud-based account rather than just logging in to the device), they can set local restrictions on the device. .. Restrictions on applications, application categories, device-level features, and general web browser use, for example, for local use on electronic device 104 (eg, not across multiple devices and / or specific online use). Can be set. In one or more implementations, software for local usage management provides a user account that is local to the electronic device 104 (for example, if the child logs in to the device but not to its own cloud-based account). / Based on the profile, parents (plural) can set restrictions on their children (plural). Usage data may be tracked locally with respect to local limits. In addition, corresponding notifications, usage statistics, interfaces, application blocks, category and / or device level features, budget growth requirements, etc. may apply as described herein, but to the use of local devices. Can be limited.

In one or more implementations, one or more of the components 302 to 334 of the architecture 300, when executed by the host processor 202, causes the host processor 202 to perform a particular function (s), memory 204. Implemented via software instructions stored in.

In one or more implementations, one or more of the components 302 to 334 of the architecture 300 are software (eg, subroutines and codes), hardware (eg, application specific integrated circuits (ASICs), field programmable gates). It may be implemented in an array (FPGA), programmable logic device (PLD), controller, state machine, gate logic, discrete hardware component, or any other suitable device), and / or a combination of both. In one or more implementations, some or all of the illustrated components may share hardware and / or circuitry, and / or one or more of the illustrated components are dedicated. Hardware and / or circuits may be used. This disclosure further describes further features and functions of these modules in various aspects of the subject technology.

FIG. 4 shows an exemplary architecture of a system for managing device usage time of another user in one or more implementations. For example, architecture 400, which includes its various components 402-430, is one or more running on host processor 202 of electronic device 104 to manage another user's device usage time with respect to electronic devices 102-103. It can be implemented by a software module. In another embodiment, architecture 400 can be implemented by one or more software modules implemented by custom hardware (eg, one or more coprocessors). However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

In one or more implementations, at least a portion of the architecture 400 may be mounted on the parent electronic device 104 to manage device use of the child electronic devices 102-103. Architecture 400 is not limited to the use of children of parent-managed devices and may apply to other scenarios in which a user manages another user's device usage. Thus, while architecture 400 is described for a "parent" user (eg, electronic device 104) and a "child" user (eg, electronic devices 102-103), the architecture is generally any two. Can be applied to users of.

In one or more implementations, the parent-child relationship may be predefined, for example, by a system that defines the roles of the parent (plural) and the child (plural). Roles may be defined based on configuration data set by the parent user. For example, the roles of parent and child may be defined by the registered user accounts of the parent (plurality) and the child (plurality), and each user account indicates a parent-child relationship. In this regard, the devices associated with the parent (s) and / or child (s) registered accounts (eg, based on login to the registered account) are grouped and grouped into family units (eg,). , Part of the circle of trust, or as a trusted group of devices). As described herein, the device can access encrypted usage data and / or time-based restricted data via a key that is only accessible by trusted devices. In one or more implementations, if a trusted device is removed from the group, the key (s) can be regenerated for the remaining trusted devices.

Architecture 400 includes a database 422 with a database used 424 and a configuration database 428. The usage database 424 may store usage data corresponding to usage time by child users of electronic devices 102-103 regarding applications, websites, applications and / or website categories, and / or device-level functions. In addition, the configuration database 428 may store time-based limits (eg, quotas and / or time limits) set by the parent user of electronic device 104. Time-based limits apply to child users of electronic devices 102-103 for their respective applications, websites, application and / or website categories, and / or device-level features. In one or more implementations, database 422 can be used to synchronize usage time and time-based limits across multiple devices associated with both parent and child (eg, electronic devices 102-104), cloud mirroring. Includes component 426.

The family structure editor 420 may provide a user interface for setting and / or adjusting time-based limits. The user interface provided by the Family Configuration Editor 420 may include user interface elements for setting individual (eg, different) time-based limits. Time-based limits may correspond to quotas (s) or time limits (s), for example, as described above with respect to FIG. 3, but for child users. In addition, the Family Configuration Editor 420, as described above with respect to FIG. 3, but with respect to child users, has other types of restrictions (eg, time, quantity, geographic location, device environment / conditions, contact-based restrictions). , And compound restrictions may be provided. In addition, the Family Configuration Editor 420, for example, as described above with respect to FIG. 3, but with respect to child users, user-selected applications, websites, categories (eg, applications and / or websites), and / or It may include user interface elements for setting (eg, time-based) limits on device-level features. In one or more implementations, the user interface provided by Family Configuration Editor 420 is before child users are allowed access to other applications, websites, categories, and / or device-level features. User interface elements for setting goals that work with time-based limits so that they may be required to perform a first time-based goal (eg, one hour of educational reading on a device). It may be included.

Architecture 400 further includes other usage viewers 418 that can communicate with the usage management module 430 and provide the parent with a user interface for viewing usage time by child users. For example, the user interface provided by another usage viewer 418 is as described above with respect to FIG. 3, but for child users, overall device usage time, applications (s), applications (eg, per application), websites. It can indicate the usage time for each one or more of (eg, per website), device level features (eg, per feature), and / or application / website categories (eg, per category). In addition, the user interface provided by the other usage viewer 418, as described above with respect to FIG. 3, however, displays usage for each time-based limit for child users (eg, based on configuration database 428). can do.

Architecture 400 further includes a family organization controller 402, including a server conduit 404, a message (“MSG”) system transfer module 408, a cloud channel 410, a configuration data persistence module 412, and a usage data persistence module 406. The configuration data persistence module 412 can access the configuration database 428 to obtain configuration data corresponding to the time-based limitation, for example, as described above with respect to FIG. The usage data persistence module 406 stores data records (s) indicating each child's usage time (s) for applications, websites, categories, and / or device-level features, eg, with respect to FIG. As mentioned above, those records can be stored in the usage database 424.

The MSG system transfer module 408 may correspond to a transfer module configured to communicate usage via a message (eg, a device-to-device message). Therefore, the MSG system transfer module 408 can synchronize the child usage data associated with the electronic devices 102-103 and allow access by the parent via the electronic device 104. Therefore, if there are changes in usage time based on usage activity by the child, the MSG system transfer module 408 works with the child module 416 to synchronize those changes to the parent device (eg, electronic device 104). In one or more implementations, the MSG system transfer module 408 works in conjunction with the MSG system transfer module 508 (as discussed below with respect to FIG. 5) to end-to-end between the parent device and the child device. You can send encrypted messages.

In addition, the MSG system transfer module 408 can work with other parent modules 414 to synchronize their changes to other electronic devices (s) (not shown) of the second parent. In one or more implementations, the architecture 400 may also be implemented on the second parent's electronic device (s) so that the second parent can view the child's usage time. And can make changes to the time-based limits for children. The other parent module 414 is configured to synchronize changes with respect to child usage time and / or time-based limits (eg, as set by either parent).

In one or more implementations, one or more of the components 402-430 of the architecture 400 causes the host processor 202 to perform a particular function (s) when executed by the host processor 202, the memory 204. Implemented via software instructions stored in.

In one or more implementations, one or more of the components 402-430 of the architecture 400 are software (eg, subroutines and code) and / or hardware (eg, application specific integrated circuits (ASICs)). Implemented in field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, or any other suitable device), and / or a combination of both. May be good. In one or more implementations, some or all of the illustrated components may share hardware and / or circuitry, and / or one or more of the illustrated components are dedicated. Hardware and / or circuits may be used. This disclosure further describes further features and functions of these modules in various aspects of the subject technology.

FIG. 5 shows an exemplary architecture of a system for managing personal device usage time based on time-based limits set by another user in one or more implementations. For example, architecture 500, including its various components 502-544, can be implemented by one or more software modules running on host processor 202 (eg, or electronic device 103) of electronic device 102. In another embodiment, architecture 500 can be implemented by one or more software modules implemented by custom hardware (eg, one or more coprocessors). However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

In one or more implementations, at least a portion of the architecture 500 personalizes device usage time, taking into account any time-based limits set by the parent via the electronic device 104, as described above with respect to FIG. It may be implemented on the child electronic device 102 for management. However, architecture 500 is not limited to child device usage and may be applied to other scenarios in which a user's usage time is managed by another user. Thus, while architecture 500 is described for "child" users (eg, electronic devices 102-103) and "parent" users (eg, electronic device 104), the architecture is generally any two users. Can be applied to.

Architecture 500 includes database 530, which has a database used 532 and a configuration database 536. The usage database 532 may store usage data corresponding to usage time by child users of electronic devices 102-103 with respect to applications, websites, applications and / or website categories, and / or device-level features. In addition, the configuration database 536 may store time-based limits (eg, quotas and / or time limits) set by the parent user of electronic device 102. Time-based limits apply to child users of electronic devices 102-103 for their respective applications, websites, application and / or website categories, and / or device-level features. In one or more implementations, database 530 can be used to synchronize usage time and time-based limits across multiple devices (eg, electronic devices 102-104) associated with both parents and children. Includes mirroring component 534.

The personal configuration editor 514 may provide a user interface for setting and / or adjusting time-based limits. The user interface provided by the personal configuration editor 514 may include user interface elements for setting each (eg, different) time-based limit. Time-based limits may correspond, for example, to setting personal quotas (s) or time limits (s), as described above with respect to FIG. In addition, Personal Configuration Editor 514 provides other types of restrictions (eg, time, quantity, geographic location, device environment / conditions, contact-based restrictions), as well as compound restrictions, as described above with respect to FIG. You may. In addition, the personal configuration editor 514, for example, as described above with respect to FIG. 3, is for personal (eg, application and / or website) categories and / or device-level features of the selected application, website. For example, it may include a user interface element for setting (time-based) limits.

In this regard, the personal configuration editor 514 may be used by the child user, taking into account the time-based limits set by the parent user via the electronic device 104. For example, the user interface provided by the personal configuration editor 514 can display current time-based limits (eg, set by the parent), allowing child users to make those time-based limits more restrictive. Can be made possible. For example, if the parent sets a time-based quota of 2 hours for applications, websites, and / or categories, the child users will be time-based via the user interface provided by the personal configuration editor 514. You can browse the restrictions. The child may modify the time-based limit to be more restrictive, for example, by changing the 2-hour quota to 1 hour via the user interface provided by the personal configuration editor 514. Such changes are reflected in the configuration database 536 and synchronized with the parent electronic device 104 (eg, via the MSG transfer system 508 and the parent module 510, as described below). However, the time-based limits set by the parent may be less restrictive than the time-based limits set by the child (s). In other words, the parental limit (s) can outweigh the child's limit if the child attempts to set the limit (s) to be less restrictive.

Architecture 500 further includes a personal use viewer 512 that may provide a user interface for viewing personal use time. For example, the user interface provided by the Personal Use Viewer 512 may include overall device usage time, applications (s) (eg, per application), websites (eg, per website), as described above with respect to FIG. ), Device-level features (eg, by feature), and / or application / website categories (eg, by category), each of which can indicate usage time. In addition, the user interface provided by the Personal Use Viewer 512 can display usage for each time-based limit (eg, based on the configuration database 536), as described above with respect to FIG.

Architecture 500 further includes a personal organization controller 516, including a configuration data persistence module 526, a data persistence module 528 used, a server conduit 524, an internal transfer module 518, a client conduit 520, and a configuration source 522. The configuration data persistence module 526 can access the configuration database 536 to obtain configuration data corresponding to the time-based limitation, for example, as described above with respect to FIG. The usage data persistence module 528 stores data records (s) indicating each child's usage time (s) for applications, websites, categories, and / or device-level features, eg, with respect to FIG. As mentioned above, those records can be stored in the usage database 532.

The configuration data persistence module 526, for example, via the server conduit 524, the internal transfer module 518, the client conduit 520, the configuration source 522, the usage management module 538, and the device management module 540, as described above with respect to FIG. , Corresponding to the time-based limits set by the parent and / or child). Further, the device management module 540, as described above with respect to FIG. 3, works with the usage tracking module 542 and the usage monitoring module 544 for a plurality of users for applications, websites, categories, and / or device level functions. Access and aggregate (deduplication) usage data across devices, maintain user privacy across multiple users' devices (eg, electronic devices 102-103), aggregate usage data (eg, cloud-based synchronization) Synchronize data between multiple child devices and detect time-based violations based on synchronization policies (and / or using device-to-device synchronization) for each application, website, category, and / or device. Deletion of applications and / or websites (eg, by removing identification data while maintaining an extracted record of usage data) by notifying and / or blocking level functionality (eg, with default exceptions). It can be performed.

In addition, architecture 500 includes a family organization controller 502 that includes an MSG system transfer module 508, a client conduit 504, and a configuration source module 506. The MSG system transfer module 508 synchronizes the child usage data associated with the electronic devices 102-103 and allows access by the parent on the electronic device 102 via the parent module 510. Therefore, if there are changes in usage time based on usage activity by the child, the MSG system transfer module 508 makes those changes via the parent module 510 and in conjunction with the MSG system transfer module 408. For example, it is synchronized with the electronic device 102).

The MSG system transfer module 508 can work with the MSG system transfer module 408 to send an end-to-end encrypted message between the parent device and the child device, and the message is the time associated with the child. Indicates the base limit and / or usage time. Further, in response to device management module 540 detecting a time-based limit violation (in conjunction with usage tracking module 542 and usage monitoring module 544), the child device via the MSG system transfer module 508. The violation can be notified to the parent.

As mentioned above, parents can set time-based goals for their children (eg, one hour of reading is required before other device activity). Therefore, the device management module 540 is configured to detect that a time-based goal has been reached before allowing the child to use other applications, websites, categories, and / or device-level features. You may.

In one or more implementations, the aspects of the synchronization policy described above with respect to FIG. 3 may also be applied to synchronization between a child device and a parent device. For example, if the child has multiple electronic devices instead of a single device, the synchronization frequency can be increased, the child is subject to time-based limits (eg, quotas), and the child's usage time is User interactions are detected with respect to approaching time-based limits (eg, quotas) and / or viewing usage time and / or adjusting time-based limits. The type of synchronization may be based on message forwarding (eg, via MSG system forwarding module 508). Alternatively or additionally, the synchronization between the child device and the parent device may be server-based.

In this regard, the server (eg, server 108) can store restricted and / or used data in an encrypted manner, with parent and child devices at their respective keys inaccessible to the server. Access to the data is provided based on. In addition, the server stores usage data for the domain hosting the website (eg, domain "xyz.com") rather than for a particular website and / or its corresponding web page (eg, xyz.com/123). can do. In an exemplary implementation, the server-based sharing mechanism is one or more encrypted data containers that are only accessible by the child device (eg, electronic device 102-103) and the parent device (eg, electronic device 104). May be implemented by. For example, an encrypted data container may be a logical container for storing encrypted data corresponding to different user accounts (eg, one or more logical containers associated with parent and / or child user accounts). good. Access to the logical container is restricted to devices registered with the parent and / or child (eg, with respect to restricted and / or usage data) and can be accessed through their respective keys stored on the registered device. be. In this regard, the server 108 may not have access to encrypted data stored on the container (eg, for use and / or time-based restrictions). By storing the encrypted data on the server, the child device can access the time-based limit even if the parent device (s) are offline. In addition, the parent device may be used to set limits when the child device is offline. In addition, message forwarding systems can implement time-to-live (TTL) for messages related to usage time and / or time-based limits, but TTL is not applied in server-based implementations. May be good.

In one or more implementations, the child user can require the parent to increase the budget with respect to time-based limits. If the time-based limit corresponds to the quota, the child device can present a user interface for requesting an increase in quota. If the time-based limit corresponds to the time limit, the child device can present a user interface for requesting an extension of the time range of use. These interfaces for requesting an increased budget may be called by child users via the interface provided by the personal configuration editor 514. Alternatively or additionally, an interface for requesting an increase in budget is automatically called (eg, by device management module 540 and usage tracking module 542) when it detects that a time-based breach has occurred. May be good. It may also call the interface when it detects that a time-based violation is likely to occur, for example, when the usage time is approaching the time-based limit.

In response to a child requesting an increase in budget, the parent device may be provided with a corresponding request to increase the budget. Accordingly, the parent user can increase the child budget (eg, via the user interface provided by the family structure editor 420). Alternatively or additionally, the child budget is the child device itself (eg, electronic devices 102-103) by entering a restriction code that allows the user (eg, the parent) to increase the budget. Can be increased directly above.

In one or more implementations, time-based limited applications on the child device may not exist (eg, are not installed) on the parent device. To provide a visual context for such an application, the parent device may be configured to retrieve an icon representing the application from a public data source such as a public endpoint associated with an online application store. Therefore, the parent device (eg, electronic device 104) does not need to provide any identification information in order to acquire the icon. For example, the electronic device 104 can access the application catalog associated with a public data source to obtain the name and / or icon of the application without providing identification information. In this way, for example, the privacy of the parent and / or child device is protected because no information about the child identity or parent identity is revealed. The icon is for increasing the budget for a time-based breach, for example, in the user interface provided by the Family Configuration Editor 420, in the notification provided to the parent user when a time-based breach occurs. It may be displayed in the notification request from the child device.

In one or more implementations, one or more of the components 502 to 544 of Architecture 500, when executed by the host processor 202, causes the host processor 202 to perform a particular function (s), memory 204. Implemented via software instructions stored in.

In one or more embodiments, one or more of the components 502 to 544 of the architecture 500 are software (eg, subroutines and code) and / or hardware (eg, application specific integrated circuits (ASICs)). Implemented in field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, or any other suitable device), and / or a combination of both. May be good. In one or more implementations, some or all of the illustrated components may share hardware and / or circuitry, and / or one or more of the illustrated components are dedicated. Hardware and / or circuits may be used. This disclosure further describes further features and functions of these modules in various aspects of the subject technology.

FIG. 6 shows an exemplary architecture of a system for managing device usage time in an enterprise configuration with one or more implementations. For example, architecture 600 can be implemented by one or more software modules running on the host processor 202 of any of the electronic devices 102-104. In another embodiment, the architecture 600 can be implemented by one or more software modules implemented by custom hardware (eg, one or more coprocessors). However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

Architecture 600 includes an enterprise organization controller 602 that includes a client conduit 604, a configuration source module 606, and a hypertext transfer protocol (HTTP) transfer module 608. Architecture 600 further includes a device management module 612, a usage tracking module 614, and a usage monitoring module 616. Components 602-616 may implement similar functionality as described above with respect to FIGS. 3-5, but within the context of the enterprise. Examples of businesses include, but are not limited to, businesses, schools, entrepreneurship, social enterprises, and / or other types of organizations. In this regard, the enterprise organization controller 602 (eg, based on time, quantity, geographic location, device environment / conditions, contacts, and / or compound limits) via the HTTP transfer module 608 and server module 610. It may be configured to manage limits set on devices in the enterprise.

In one or more implementations, one or more of the components 602-616 of the architecture 600, when executed by the host processor 202, causes the host processor 202 to perform a particular function (s), memory 204. Implemented via software instructions stored in.

In one or more implementations, one or more of the components 602-616 of the architecture 600 are software (eg, subroutines and code) and / or hardware (eg, application specific integrated circuits (ASICs)). Implemented in field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, or any other suitable device), and / or a combination of both. May be good. In one or more implementations, some or all of the illustrated components may share hardware and / or circuitry, and / or one or more of the illustrated components are dedicated. Hardware and / or circuits may be used. This disclosure further describes further features and functions of these modules in various aspects of the subject technology.

FIG. 7 shows an exemplary architecture of a system for remote management of components for managing device time usage in one or more implementations. For example, the remote management architecture 700 can be implemented by one or more software modules running on the host processor 202 of any of the electronic devices 102-104. In another embodiment, the architecture 700 can be implemented by one or more software modules implemented by custom hardware (eg, one or more coprocessors). However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. Modifications of component configurations and types can be made without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

The example in FIG. 7 shows that device management (eg, time-based limits on usage time) may be implemented for different sources on the same device (eg, electronic device 102). The remote management architecture 700 is described herein with respect to the child. However, the remote management architecture 700 is not limited to children and may instead be applied to the parent or any other user.

In this regard, the child device (eg, any of the electronic devices 102-103) includes a personal organization controller 702 corresponding to the personal organization controller 516, a family organization controller 714 corresponding to the family organization controller 502, and ( For example, it may include a corporate organization controller 728 corresponding to the corporate organization controller 602 (if the child is a student and the school company has set a time-based limit on the student's device).

In this regard, the personal organization controller 702 includes a configuration source module 704, a server conduit 706, a client conduit 708, a configuration data persistence module 710, and a usage data persistence module 712 that roughly corresponds to the components of the personal organization controller 516. May include. In addition, the family organization controller 714 is used roughly corresponding to the components of the configuration source module 716, the server conduit 718, the client conduit 720, the MSG system transfer 722, the configuration data persistence module 724, and the family organization controller 502. It may include a data persistence module 726 and. Further, the corporate organization controller 728 may include a configuration source module 730, a server conduit 732, a client conduit 734, and an HTTP transfer module 736 that roughly corresponds to the components of the corporate organization controller 602.

The remote management architecture 700 may further include a personal use viewer 738, a personal configuration editor 740, a family use viewer 742, and a family configuration editor 744 that generally corresponds to the components of architecture 500. In addition, the remote management architecture 700 may include databases 746, databases used 748 and 750, configuration databases 752 and 754, and a cloud mirroring module 756 that generally corresponds to the components of architecture 500.

Thus, each of the personal organization controller 702, the family organization controller 714, and the enterprise organization controller 728 can represent data originating from different sources (eg, individuals, families, businesses). Each conduit (eg, 706-708, 718-720, and 732-734) facilitates control of general data flow, eg, with respect to inbound / outbound usage data and / or time-based limits. can do. In addition, each persistence module (eg, 710-712, 724-726) may provide persistence of data. In the corporate case, there is no persistence layer and time-based limits may be transmitted via the HTTP transfer module 736.

In one or more embodiments, one or more of the components 702-756 of the remote management architecture 700 causes the host processor 202 to perform a particular function (s) when executed by the host processor 202. It is implemented via software instructions stored in memory 204.

In one or more implementations, one or more of the components 702-756 of the remote management architecture 700 are software (eg, subroutines and code) and / or hardware (eg, application specific integrated circuits (ASICs)). ), Field Programmable Gate Array (FPGA), Programmable Logic Device (PLD), Controller, State Machine, Gate Logic, Discrete Hardware Components, or any other suitable device), and / or a combination of both. May be done. In one or more implementations, some or all of the illustrated components may share hardware and / or circuitry, and / or one or more of the illustrated components are dedicated. Hardware and / or circuits may be used. This disclosure further describes further features and functions of these modules in various aspects of the subject technology.

FIG. 8 shows an exemplary process for managing device usage time with one or more implementations. For illustration purposes, process 800 will be described herein primarily with reference to electronic devices 102-104 and server 108 of FIG. However, process 800 is not limited to the electronic devices 102-104 and server 108 of FIG. Further, one or more blocks (or operations) of process 800 may be performed by one or more other components of server 108 and / or by other suitable devices. Further, for reference, the blocks of process 800 are described herein as occurring sequentially or linearly. However, multiple blocks of process 800 may occur in parallel. In addition, the blocks of process 800 need not be executed in the order shown, and / or one or more blocks of process 800 need not be executed and / or be replaced by other actions. Can be done.

Electronic device 102 (eg, first device) receives a time-based quota for use by a first user for a category of application, website, or device-level function (802). Categories may be based on a particular topic or may include a default set of one or more applications, websites, or device-level features that correspond to a particular topic.

The time-based quota may be set by the first user. Alternatively or additionally, the time-based quota may be set by a second user (eg, the parent of the first user) associated with a third device (eg, electronic device 104). ..

When a second user (eg, a parent) sets a time-based quota, receiving the time-based quota may include receiving encrypted data indicating the time-based quota. Its access is restricted to electronic devices 102-104. Encrypted data indicating the time-based quota may be received from the electronic device 104 via the message forwarding system. Alternatively or additionally, the encrypted data indicating the time-based quota may be stored in the server 108, and the electronic device 102 accesses the encrypted data indicating the time-based quota from the server 108. You may memorize the key to do so.

The electronic device 104 is now required to obtain a graphical icon from a public data source (eg, a public endpoint associated with an online application store) that represents an application that is associated with aggregated use and is not installed on the electronic device 104. It may be configured in. For example, the graphical icon may provide a context within a user interface indicating the use of the parent user of the electronic device 104 (eg, provided by another usage viewer 418).

Electronic device 102 provides encrypted data indicating use by a first user on electronic device 103 (eg, a second device of a first user) for an application, website, or device-level function within a category. Receive (804). The encrypted data indicating use may be end-to-end encrypted between the electronic device 102 and the electronic device 103. For example, access to encrypted data indicating use may be restricted to electronic devices 102-103 and / or electronic device 104 (eg, if a second user sets a time-based limit).

The encrypted data indicating the use by the first user on the electronic device 103 may be stored in the server 108, and the electronic device 102 holds a key for accessing the encrypted data indicating the use from the server 108. You may remember. For example, the encrypted data indicating the use by the first user on the electronic device 103 is at least one encrypted data container corresponding to the use by the first user across a plurality of devices (eg, electronic devices 102 to 103). It may be stored in the server 108 in association with. Alternatively or additionally, the electronic device 102 can receive encrypted data from the electronic device 103 via an inter-device communication protocol.

Receiving encrypted data indicating use may be performed in association with a synchronization policy indicating when the use between the electronic device 102 and the electronic device 103 is synchronized. For example, a synchronization policy is to synchronize usage more often when the first user is associated with multiple devices instead of a single device, as aggregated usage approaches time-based quotas. At the current time (eg, immediately or based on device availability), if user interaction is detected with respect to the user interface associated with synchronizing usage more frequently and / or time-based quota for usage. Can indicate one or more of synchronization (as soon as possible).

The electronic device 102 is based on the first user's use on the electronic device 103 and the first user's use on the electronic device 102 for an application, website, or device level feature within the category. Determine aggregated use (806). Determining aggregated use deduplications of concurrent use by a first user on electronic device 102 and electronic device 103 that correspond to the same application, the same website, or the same device-level features in the category. May include that.

If a second user (eg, parent) sets a time-based quota (eg, via electronic device 104), electronic device 102 limits access to aggregated use to electronic devices 102-104. As such, encrypted data indicating aggregated use can be provided to the electronic device 104. Encrypted data indicating aggregated use may be provided to electronic device 104 via a message forwarding system. Alternatively or additionally, the encrypted data indicating aggregated use may be stored in the server 108 for the electronic device 104 to access the encrypted data indicating aggregated use from the server 108. You may memorize the key of.

Electronic device 102 determines that aggregated use has reached a time-based quota for a category (808). If the second user (eg, the parent) sets the time-based quota (eg, via the electronic device 104), the electronic device 102 will, for example, increase the time-based quota by the first user. Upon request, an authorization instruction by a second user can be received to adjust the time-based quota. Upon receiving the instruction, the electronic device 102 can adjust the time-based quota. The electronic device 102 can locally receive authorization instructions as user input for authentication (eg, entered by the parent on the child electronic device 102) to allow time-based quota adjustments. For example, authentication can correspond to entering a registration code or other credentials such as biometrics (eg, fingerprint scanning, face recognition). Alternatively or additionally, the electronic device 102 may receive an authorization instruction from the electronic device 104 by a second user (eg, a parent) to adjust the time-based quota.

In response to determining that the aggregated usage has reached the time-based quota, the electronic device 102 provides a notification that the first user has reached the time-based quota for the category (810). ). The electronic device 102 can also prevent a first user from accessing an application, website, or device-level feature within the category.

In one or more implementations, the electronic device 102 can detect the deletion of an application in the category. Upon detecting the deletion, the electronic device 102 may remove the data on the electronic device 102 that identifies the application and maintain a record of use for the category corresponding to the application. Alternatively or additionally, the electronic device 102 may detect the deletion of the browser history corresponding to the website in the category. In response to detecting the deletion, the electronic device 102 identifies the browser history corresponding to the website and maintains a record of usage for the category corresponding to the browser history corresponding to the website Data on the electronic device 102. Can be removed.

FIG. 9 shows another exemplary process for managing device usage time with one or more implementations. For illustration purposes, process 900 will be described herein primarily with reference to electronic devices 102-104 and server 108 of FIG. However, process 900 is not limited to the electronic devices 102-104 and server 108 of FIG. Further, one or more blocks (or operations) of process 900 may be performed by one or more other components of server 108 and / or by other suitable devices. Further, for illustration purposes, the blocks of process 900 are described herein as occurring sequentially or linearly. However, multiple blocks of process 900 may occur in parallel. In addition, the blocks of process 900 need not be executed in the order shown, and / or one or more blocks of process 900 need not be executed and / or replaced by other actions. Can be done.

The electronic device 102 (eg, the first device) receives a time-based limit for use by the first user for an application, website, or device-level feature (902). Time-based limits may be set by the first user. Alternatively or additionally, the time-based limit may be set by a second user (eg, the parent of the first user) associated with the third device (eg, electronic device 104).

If a second user (eg, a parent) sets a time-based limit, receiving the time-based limit may include receiving encrypted data indicating the time-based limit, the access of which is , Limited to electronic devices 102-104. The encrypted data indicating the time-based limit may be received from the electronic device 104 via the message forwarding system. Alternatively or additionally, the encrypted data indicating the time-based limit may be stored in the server 108, and the electronic device 102 may access the encrypted data indicating the time-based limit from the server 108. You may memorize the key.

Electronic device 102 receives encrypted data indicating use by a first user on electronic device 103 (eg, a second device of a first user) with respect to applications, websites, and device-level features (904). ). The encrypted data indicating use may be end-to-end encrypted between the electronic device 102 and the electronic device 103. For example, access to encrypted data indicating use may be restricted to electronic devices 102-103 and / or electronic device 104 (eg, if a second user sets a time-based limit).

The encrypted data indicating the use by the first user on the electronic device 103 may be stored in the server 108, and the electronic device 102 holds a key for accessing the encrypted data indicating the use from the server 108. You may remember. For example, the encrypted data indicating the use by the first user on the electronic device 103 is at least one encrypted data container corresponding to the use by the first user across a plurality of devices (eg, electronic devices 102 to 103). It may be stored in the server 108 in association with. Alternatively or additionally, the electronic device 102 can receive encrypted data from the electronic device 103 via an inter-device communication protocol.

Receiving encrypted data indicating usage may be performed in association with a synchronization policy indicating when the usage between the electronic device 102 and the electronic device 104 is synchronized. For example, a synchronization policy is to synchronize usage more often when a first user is associated with multiple devices instead of a single device, and usage (eg, aggregated usage) is time-based. Synchronize usage more often as you approach the limit (eg, quota) and / or synchronize at the current time if user interaction is detected with respect to the user interface associated with the time-based limit on usage. Can indicate one or more of.

The electronic device 102 is time-based at least one of the first user's use on the electronic device 103 or the first user's use on the electronic device 102 with respect to an application, website, or device level function. (906). In this regard, the time-based limit may correspond to a time limit (eg, a time frame with limited use) on either the first device or the second device during the time frame. Use by a first user of can violate the time limit. Alternatively or additionally, the time-based limitation may correspond to a budget (eg, the total amount of permitted use), which uses the aggregated time of the first and second devices. Beyond that, you can violate your budget. Determining aggregated use deduplications of concurrent use by a first user on electronic device 102 and electronic device 103 that correspond to the same application, the same website, or the same device-level features in the category. May include that.

If a second user (eg, the parent) sets a time-based limit (eg, via the electronic device 104), the electronic device 102 will have access to its use restricted to the electronic devices 102-104. , Encrypted data indicating use can be provided to the electronic device 104. Encrypted data indicating use may be provided to the electronic device 104 via a message forwarding system. Alternatively or additionally, the usage-indicating encrypted data may be stored in the server 108, and the electronic device 104 stores the key to access the aggregated usage-indicating encrypted data from the server 108. You may.

If the second user (eg, the parent) sets a time-based limit (eg, via the electronic device 104), the electronic device 102, for example, responds to a request by the first user to increase the time-based limit. Accordingly, it is possible to receive authorization instructions by a second user to adjust the time-based limit. Upon receiving the instruction, the electronic device 102 can adjust the time-based limit. The electronic device 102 may receive authorization instructions as user input for authentication (eg, a registration code or biometric entered by the parent on the child electronic device 102) to allow adjustment of time-based limits. can. Alternatively or additionally, the electronic device 102 may receive an authorization instruction from the electronic device 104 by a second user (eg, parent) to adjust the time-based limit.

Upon detecting the breach, the electronic device 102 provides a notification that the first user is breaching the time-based limit (908). The electronic device 102 can further prevent a first user from accessing an application, website, or device level feature.

In one or more implementations, the electronic device 102 can detect the deletion of an application in the category. Upon detecting the deletion, the electronic device 102 may remove the data on the electronic device 102 that identifies the application and maintain a record of use for the category corresponding to the application. Alternatively or additionally, the electronic device 102 may detect the deletion of the browser history corresponding to the website in the category. In response to detecting the deletion, the electronic device 102 identifies the browser history corresponding to the website and maintains a record of usage for the category corresponding to the browser history corresponding to the website Data on the electronic device 102. Can be removed.

As mentioned above, one aspect of the technology is, for example, collecting and using data available from a particular legitimate source to control the use of the device. The disclosure is intended, in some cases, to include personal information data that may be used to uniquely identify or identify a particular person. Such personal information data relates to demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, user health or fitness levels (eg, vital sign measurements, medication information, exercise information). It may contain data or records, date of birth, or any other personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be in the interest of the user. Furthermore, other uses for personal information data that benefit the user are also conceived by this disclosure. For example, according to user preference, health and fitness data can be used to provide general wellness insights or as positive feedback to individuals using techniques to pursue wellness goals. ..

This disclosure is intended to ensure that those entities involved in the collection, analysis, disclosure, transfer, storage, or other use of such personal information data comply with robust privacy policies and / or privacy practices. ing. Specifically, such entities are expected to implement and consistently apply privacy practices that are generally accepted to meet or exceed industry or government requirements for maintaining user privacy. There will be. Such information regarding the use of personal data should be noticeably and easily accessible by the user and should be updated as the collection and / or use of the data changes. Personal information from users should be collected only for legitimate use. In addition, such collection / sharing should take place after the consent of the user or on the basis of other legitimate grounds specified in applicable law. Furthermore, such entities protect and secure access to such personal information data and ensure that others with access to that personal information data comply with their privacy policies and procedures. You should consider taking all necessary steps to do so. In addition, such entities may be evaluated by a third party to prove their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to the specific type of personal information data collected and / or accessed, including jurisdiction-specific considerations that may be responsible for imposing higher standards. It should also comply with applicable laws and standards. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state law, such as the Health Insurance Portability and Accountability Act (HIPAA). Yes, on the other hand, health data in other countries may be subject to other regulations and policies and should be addressed accordingly.

Despite the above, the disclosure also envisions embodiments that selectively prevent the user from using or accessing the personal information data. That is, it is conceivable that the present disclosure may provide hardware and / or software elements to prevent or prevent access to such personal information data. The technology may be configured to allow the user to select "opt-in" or "opt-out" of participation in the collection of personal information data during or at any time thereafter during registration of the service. In addition to providing "opt-in" and "opt-out" options, the disclosure contemplates providing notices regarding access or use of personal information. For example, the user may be notified at the time of downloading the application that will access the user's personal information data, and then the user may be warned again just before the personal information data is accessed by the application.

Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a way that minimizes the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting it when it is no longer needed. Furthermore, where applicable, data de-identification can be used to protect user privacy in certain health-related applications. Non-specification is, where appropriate, the removal of identifiers, the control of the amount or specificity of stored data (eg, collecting location data at the city level rather than the address level), and the data being collected. It may be facilitated by controlling how it is stored (eg, aggregating data across users) and / or by other methods such as differential privacy.

Therefore, although the disclosure broadly covers the use of personal information data to implement one or more various disclosed embodiments, the disclosure also covers such personal information data. It is conceivable that it is also possible to implement those various embodiments without requiring access to. That is, various embodiments of the present technology are not impractical due to the lack of all or part of such personal information data. For example, managing device usage can be aggregated non-personal information data, such as content that is only handled on the user's device, or other available non-personal information, or minimal bare personal information. May be based on.

FIG. 10 shows an electronic system 1000 capable of implementing one or more implementations of a subject technology. The electronic system 1000 can be one or more and / or one or a server 108 of the electronic devices 102-104 shown in FIG. 1 and / or a part thereof. The electronic system 1000 can include various types of computer readable media and interfaces for other types of computer readable media. The electronic system 1000 includes bus 1008, one or more processing units (s) 1012, system memory 1004 (and / or buffer), ROM 1010, permanent storage device 1002, input device interface 1014, output device interface 1006, and 1 Includes one or more network interfaces 1016, or subsets and variants thereof.

Bus 1008 collectively represents all systems, peripherals, and chipset buses that communicatively connect a large number of internal devices of the electronic system 1000. In one or more implementations, bus 1008 connects one or more processing units (s) 1012 communicably with ROM 1010, system memory 1004, and permanent storage device 1002. From these various memory units, one or more processing units (s) 1012 retrieve instructions to be executed and data to be processed in order to perform the subject disclosure process. One or more processing units 1012 may be single processors or multi-core processors in different implementations.

The ROM 1010 stores static data and instructions required by one or more processing units 1012 and other modules of the electronic system 1000. On the other hand, the permanent storage device 1002 may be a read / write memory device. Permanent storage device 1002 may be a non-volatile memory unit that stores instructions and data, even if the electronic system 1000 is off. In one or more implementations, a large capacity storage device (such as a magnetic disk or optical disk and a corresponding disk drive) can be used as the permanent storage device 1002.

In one or more implementations, removable storage devices (floppy disks, flash drives, and corresponding disk drives, etc.) can be used as the permanent storage device 1002. Like the permanent storage device 1002, the system memory 1004 may be a read and write memory device. However, unlike the permanent storage device 1002, the system memory 1004 may be a volatile read and write memory, such as a random access memory. The system memory 1004 may store any of the instructions and data that may be required by one or more processing units 1012 at run time. In one or more implementations, the processes disclosed in the present application are stored in system memory 1004, permanent storage device 1002, and / or ROM 1010. From these various memory units, one or more processing units 1012 retrieve instructions to be executed and data to be processed in order to execute a process of one or more implementations.

Bus 1008 also connects to input device interface 1014 and output device interface 1006. The input device interface 1014 allows the user to communicate information and select commands to the electronic system 1000. Input devices that can be used with the input device interface 1014 can include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). The output device interface 1006 can, for example, enable the display of files generated by the electronic system 1000. Output devices that can be used with the output device interface 1006 include, for example, liquid crystal displays (LCDs), light emitting diode (LED) displays, organic light emitting diode (OLED) displays, flexible displays, flat panel displays, solid state displays, projectors. , Or display devices such as any other device for outputting information. One or more implementations can include devices that act as both input and output devices, such as touch screens. In these embodiments, the feedback provided to the user can be any form of sensory feedback such as visual feedback, auditory feedback, tactile feedback, etc., and the user input can be acoustic input, audio input, or It can be received in any form, including tactile input.

Finally, as shown in FIG. 10, the bus 1008 also connects the electronic system 1000 through one or more network interfaces (s) 1016 to one or more networks and / or the server 108 shown in FIG. Combine to one or more network nodes. In this way, the electronic system 1000 can be a computer network (such as a LAN or wide area network (“WAN”)), an intranet, or a network in a plurality of networks such as the Internet. Any or all components of electronic system 1000 can be used in conjunction with subject matter disclosure.

Implementations within the scope of the present disclosure partially use a tangible computer-readable storage medium (or one or more types of tangible computer-readable storage media) that encodes one or more instructions. It can be realized completely or completely. The tangible computer-readable storage medium may also be virtually non-temporary.

A computer-readable storage medium is any storage that can be read, written, or otherwise accessed by a general purpose or dedicated computing device, including any processing electronics and / or processing circuits capable of executing instructions. It can be a medium. For example, but not limited to, computer readable media can include any volatile semiconductor memory such as RAM, DRAM, SRAM, T-RAM, Z-RAM, and TTRAM. Computer-readable media can also be any arbitrary such as ROM, PROM, EPROM, EEPROM, NVRAM, flash, nvSRAM, FeRAM, FeTRAM, MRAM, PRAM, CBRAM, SONOS, RRAM, NRAM, racetrack memory, FJG, and millipede memory. Non-volatile semiconductor memory can be included.

Further, the computer-readable storage medium includes any non-semiconductor memory, such as an optical disk storage device, a magnetic disk storage device, a magnetic tape, another magnetic storage device, or any other medium capable of storing one or more instructions. be able to. In one or more implementations, the tangible computer-readable storage medium can be directly coupled to the computing device, and in other implementations, the tangible computer-readable storage medium is, for example, one or more wired. Connections can be indirectly coupled to computing devices via one or more wireless connections, or any combination thereof.

The instruction can be directly executable or can be used to develop an executable instruction. For example, an instruction can be implemented as executable or non-executable machine code, or as a high-level language instruction that can be compiled to generate executable or non-executable machine code. In addition, the instructions can also be implemented as data or include data. Computer-executable instructions can also be structured in any format, including routines, subroutines, programs, data structures, objects, modules, applications, applets, functions, and so on. As will be appreciated by those skilled in the art, details including, but not limited to, the number, structure, order, and structure of instructions can be significantly changed without changing the basic logic, functionality, processing, and output. Can be done.

The above discussion primarily refers to microprocessors or multi-core processors running software, but one or more implementations are run by one or more integrated circuits, such as ASICs or FPGAs (s). Will be done. In one or more implementations, such an integrated circuit executes instructions stored in the circuit itself.

Those skilled in the art may implement the various exemplary blocks, modules, elements, components, methods, and algorithms described herein as electronic hardware, computer software, or a combination thereof. Will understand. To demonstrate this compatibility of hardware and software, various exemplary blocks, modules, elements, components, methods, and algorithms have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the design constraints imposed on the particular application and the entire system. Those skilled in the art will be able to implement the functionality described in various ways for each particular application. The various components and blocks may be arranged differently (eg, arranged in different orders or divided in different ways) without departing from the scope of the subject matter at all.

It will be appreciated that any particular order or hierarchy of blocks in the disclosed process is an example of an exemplary approach. Based on the design choices, it is understood that the particular order or hierarchy of blocks in the process may be rearranged, or all the illustrated blocks may be executed. Both blocks may be executed at the same time. In one or more implementations, multitasking and parallel processing can be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations. It should be understood that the program components and systems described may be identified into a single software product or packaged into multiple software products.

As used herein and in any of the claims, the terms "base station", "receiver", "computer", "server", "processor", and "memory" are all used. Refers to electronic or other technical devices. These terms exclude a person or a group of people. For the purposes of this specification, the terms "display" or "displaying" mean displaying on an electronic device.

As used herein, the phrase "at least one" preceding a series of items, along with the terms "and" or "or" that separate any of the items, is an element of the list (ie, each item). Instead, qualify the list as a whole. The phrase "at least one" does not require at least one selection of each item listed, rather the phrase is at least one of any one of the items and / or of the item. Allows meaning to include at least one of any combination and / or at least one of each of the items. As an example, the phrases "at least one of A, B, and C" or "at least one of A, B, or C" are A only, B only, or C only, A, respectively. , B, and C, and / or at least one of each of A, B, and C.

The predicates "configured to", "operable to", and "programmed to" are tangible or peculiar to the object. It does not mean an intangible modification, but rather is intended to be used interchangeably. In one or more implementations, a processor configured to monitor and control an operation or component means that the processor is programmed to monitor and control the operation, or the processor monitors the operation. And it can also mean that it can operate to control. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute code or capable of operating to execute code.

One aspect, its aspect, another aspect, some aspects, one or more aspects, one mounting form, its mounting form, another mounting form, some mounting forms, one or more mounting forms, 1 One embodiment, its embodiment, another embodiment, some embodiments, one or more embodiments, one configuration, its configuration, another configuration, some configurations, one or more configurations, the subject matter. The technology, disclosures, present disclosures, other variants thereof, and similar phrases are for convenience only, and disclosures relating to such phrases (s) are essential to the subject technology, or such. It does not imply that the disclosure applies to all configurations of the subject technology. Disclosures relating to such phrases (s) may apply to all configurations, or to one or more constructs. Disclosure of such phrases (s) can provide one or more examples. A phrase such as an aspect or some aspects can refer to one or more aspects and vice versa, which applies like any other aforementioned phrase.

The word "exemplary" is used herein to mean "to act as an example, case, or example." Any embodiment described herein as "exemplary" or "example" should not necessarily be construed as preferred or advantageous over other embodiments. Further, as long as terms such as "include" and "have" are used in the specification or claims, such terms are interpreted when "provide" is used as a transitional term in the claims. As such, it is intended to be inclusive in a manner similar to the term "prepare".

All structural and functional equivalents to the elements of the various aspects described throughout this disclosure, which will be known to those of skill in the art or will become known later, are expressly incorporated herein by reference. And it is intended to be included in the scope of claims. Moreover, none of the disclosures herein are made publicly available, whether or not such disclosures are explicitly listed in the claims. Elements of any claim are either explicitly enumerated using the phrase "means for" or, in the case of a method claim, the element is the phrase "step for". Unless listed using, it should not be construed under the provisions of Article 112, paragraph 6 of the US Patent Act.

The above description is provided to allow one of ordinary skill in the art to implement the various aspects described herein. Various changes to these embodiments will be readily apparent to those of skill in the art, and the general principles defined herein can be applied to other embodiments as well. Therefore, the claims are not intended to be limited to the embodiments set forth herein, and the full scope of the claims in accordance with the wording should be accepted, and references to elements in the singular form should be accepted. Unless otherwise noted, it is not intended to mean "one and only one", but rather "one or more". Unless otherwise stated, the term "some" refers to one or more. Male pronouns (eg, he) include female and neutral genders (eg, she and her), and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the disclosure of the present application.

Claims (34)

It ’s a device
With at least one processor
It comprises a memory containing an instruction, and when the instruction is executed by the at least one processor, the instruction is sent to the at least one processor.
Receive a time-based quota for use by a first user for a category of application, website, or device-level feature.
Receive encrypted data indicating use by the first user on the second device for the application, website, or device level function within the category.
Based on said use by said first user on said second device and said used by said first user on said device with respect to said application, said website, or said device level feature within said category. To determine the aggregated use
Determine that the aggregated use has reached the time-based quota for the category.
A device that provides a notification that the first user has reached the time-based quota for the category. The encrypted data indicating the use ends between the device and the second device so that access to the encrypted data indicating the use is restricted to the device and the second device. The device of claim 1, which is two-end encrypted. The encrypted data indicating the use by the first user on the second device is stored on the server.
The device according to claim 1, wherein the device stores a key for accessing the encrypted data indicating the use from the server. The encrypted data indicating the use by the first user on the second device is associated with at least one encrypted data container corresponding to the use by the first user across a plurality of devices. The device according to claim 3, which is stored on the server. The device according to claim 1, wherein the device receives the encrypted data indicating the use from the second device via an inter-device communication protocol. The time-based quota is set by a second user associated with the third device.
Receiving the time-based quota includes receiving encrypted data indicating the time-based quota, the access to the device, the second device, and the third device. The device of claim 1, which is restricted. The device according to claim 6, wherein the encrypted data indicating the time-based allocation amount is received from the third device via a message forwarding system. The encrypted data indicating the time-based quota is stored on the server, and the device stores the key for accessing the encrypted data indicating the time-based quota from the server, billing. Item 6. The device according to item 6. The instruction further applies to the at least one processor.
Have the third device provide encrypted data indicating the aggregated use so that access to the aggregated use is restricted to the device, the second device, and the third device. , The device of claim 6. The device of claim 9, wherein the encrypted data indicating the aggregated use is provided to the third device via a message forwarding system. The encrypted data indicating the aggregated use is stored on the server, and the third device stores a key for accessing the encrypted data indicating the aggregated use from the server. The device according to claim 9. 9. The third device is configured to obtain a graphical icon from a public data source that represents an application that is associated with the aggregated use and is not installed on the third device. The device described in. The instruction further applies to the at least one processor.
Upon receiving the authorization instruction by the second user for adjusting the time-based quota,
The device according to claim 6, wherein the time-based quota is adjusted in response to receiving the instruction. Receiving the instructions
13. The device of claim 13, wherein the device comprises receiving an authentication user input for authorizing the adjustment of the time-based quota. Receiving the instructions
13. The device of claim 13, comprising receiving from the third device the instructions for authorization by the second user to adjust the time-based quota. The device of claim 1, wherein the category is based on a particular topic, which comprises a default set of one or more applications, websites, or device-level features corresponding to the particular topic. .. The instruction further tells the at least one of the processors.
Upon determining that the aggregated use has reached the time-based quota for the category, the first user is prevented from accessing the application or website within the category. The device according to claim 1. The first aspect of claim 1 is that receiving the encrypted data indicating the use is performed in association with a synchronization policy indicating when the use between the device and the second device is synchronized. Device. The device of claim 18, wherein the synchronization policy indicates that the first user synchronizes the use more frequently when the first user is associated with a plurality of devices rather than a single device. 15. The device of claim 18, wherein the synchronization policy indicates that the aggregated use synchronizes the use more frequently as it approaches the time-based quota. The device of claim 18, wherein the synchronization policy indicates that if a user interaction is detected with respect to the user interface associated with the time-based quota for use, it will synchronize at the current time. The instruction further applies to the at least one processor.
Detect the deletion of applications in the above category
In response to detecting the deletion
To remove the data on the device that identifies the application,
The device of claim 1, which maintains a record of use for the category corresponding to the application. The instruction further applies to the at least one processor.
Detect the deletion of the browser history corresponding to the website in the above category,
In response to detecting the deletion
To remove the data on the device that identifies the browser history corresponding to the website
The device of claim 1, which maintains a record of use for the category corresponding to the browser history corresponding to the website. Determining said aggregated use is simultaneous use by said first user on said device and said second device that corresponds to the same application, the same website, or the same device level functionality within the category. The device of claim 1, wherein the device comprises deduplication. A computer program product that includes a code stored in a tangible computer-readable storage medium, wherein the code is
A code for receiving a time-based limit for use by a first user on an application, website, or device-level feature on the first device.
A code for receiving encrypted data indicating use by the first user on the second device for the application, the website, or the device level function.
Of the use by the first user on the second device or the use by the first user on the first device for the application, the website, or the device level function. At least one is a code for determining that the time-based limit has been violated, and
A computer program product comprising, in response to the determination, a code for providing a notification that the first user has violated the time-based limit. Receiving a time-based limit for use by a first user with respect to a category of application, website, or device-level feature by the first device.
Receiving encrypted data indicating use by the first user on the second device for the application, website, or device level feature within the category.
The use by the first user on the second device or by the first user on the first device for the application, website, or device level function within the category. At least one of the uses is determined to have violated the time-based limit and
In response to the determination, providing a notification that the first user has violated the time-based limit.
Including methods. Receiving a time-based limit on the use of the first user for device-level features by the first device, and
Receiving encrypted data indicating the use of the first user on the second device with respect to the device level function.
At least one of the use by the first user on the second device or the use by the first user on the first device with respect to the device level function is time-based. Determining that the restrictions have been violated and
In response to the determination, providing a notification that the first user has violated the time-based limit.
Including methods. 27. The method of claim 27, wherein the device level function corresponds to overall device use. 27. The method of claim 27, wherein the device level function corresponds to a display, audio, sensor function, accessory, or resource of the device. 27. The method of claim 27, wherein the time-based limitation corresponds to a time-based quota for use corresponding to the device-level function. 27. The method of claim 27, wherein the time-based limit corresponds to a number-based quota that limits the number of uses corresponding to the device-level function. 27. The method of claim 27, further comprising limiting the use of the device-level features in response to the determination of the breach. 32. The method of claim 32, wherein the limitation makes it impossible to use the device level function. 32. The method of claim 32, wherein the limitation limits the output level for the device level function.

Images