Mobile device storage with screentime gamification

Abstract

A system for mobile device storage with screentime gamification includes a storage containers and one or more mobile devices. Controllers of the storage container communicate with the one or more mobile devices via input / output (I / O) ports. Memory of the controller stores control logic, including a screentime reduction application (SRA), which is executed by a processor of the controller. The storage container includes an access hatch, and a compartment for storing mobile devices therein. The compartment is lockable and includes electromagnetic (EM) frequency blocking materials that prevent wireless communications from reaching or being transmitted outside the compartment when mobile devices are stored within the compartment and the access hatch is closed. The SRA includes a limited local network between the mobile devices and the storage container, and the SRA increases user engagement, positively reinforces user behavior, provides storage for and limits access to mobile devices, thereby prioritizing user sleep quality.

Description

MOBILE DEVICE STORAGE WITH SCREENTIME GAMIFICATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of the filing date of U.S. Provisional Patent Application No. 63 / 751,528, filed January 30, 2025. The contents of which are incorporated herein by reference in their entirety.INTRODUCTION

[0002] The present disclosure relates to mobile devices, and more specifically to systems and methods of reducing screentime and improving bedtime routines of mobile device users. Time locks and time-accessible containers having access at predetermined times have been developed to accomplish a variety of tasks, such as limiting the frequency of smoking by making cigarettes unavailable, limiting the frequency of eating by preventing access to food, and dispensing medicines. In addition, mobile apps have been developed to support users in establishing bedtime routines by reminding them to wind down and preventing screen-based overstimulation before bed.

[0003] Such devices typically have a means for locking the container against unrestricted access to the interior of the container, and mechanisms for setting a predetermined time at which the container may be opened. However, the functions limit the capabilities of such locking enclosures or containers. Thus, for devices designed to limit access to cigarettes, the user is locked out of the container for a period of time. Similarly, for devices designed to dispense medicines, the user is limited to setting access times up to a preset time limit. Further, app-based solutions for preventing overstimulation of mobile device users and supporting bedtime routinesreside on the same mobile devices that are the sources of overstimulation, thereby reducing efficacy of screentime reduction.

[0004] While current storage devices and methods of use associated therewith achieve their intended purpose, there is a need for a new and improved system and method for mobile device storage with screentime and bedtime gamification that increase user engagement, positively reinforce user behavior to support healthy bedtime routines, provide a means for storing and limiting access to mobile devices to minimize overstimulation and prioritize user sleep quality, and offer a variety of distinct formfactors and interactive features while utilizing substantially identical componentry in each of the various form factors, thereby reducing system component complexity and providing simplified, portable, and modular physical and logical construction.SUMMARY

[0005] According to several aspects, of the present disclosure a system for mobile device storage with screentime and bedtime gamification as shown and described. The system for mobile device storage with screentime and bedtime gamification includes one or more storage containers adapted to receive one or more mobile devices. The one or more storage containers have an access hatch, and a compartment for receiving and at least partially containing the one or more mobile devices therein. The system further includes one or more sensors detecting system user data, and one or more human-machine interfaces (HMIs) providing a tactile interface for users to interact with the storage container. The system further includes one or more controllers of the storage container in communication with the one or more mobile devices, the one or more sensors, and the one or more HMIs via input / output (I / O) ports of the controller. The one or more controllers further include a memory storingprogrammatic control logic, a processor that executes the programmatic control logic. The programmatic control logic includes at least a screentime reduction application (SRA). The SRA includes at least first, second, third, fourth and fifth control logics. The first control logic recognizes a digital boundary action (DBA) performed by a system user. Upon recognition of the DBA, the second control logic initiates a communications handshake between the storage container and the one or more mobile devices upon receipt of the one or more mobile devices by the one or more storage containers. The third control logic generates secure, non-spoofable electronic validation of a connection between the one or more mobile devices and the one or more storage containers. The fourth control logic launches a mobile application stored or accessed at least partially within memory of the one or more mobile devices. The fifth control logic causes the system to access the one or more HMIs, including one or more screens or light sources, and depict system-state graphics comprising: a shutdown tracker, a streak tracker, screen-free user performance, a pixel pet, and a dynamically adjusted state of the pixel pet. The SRA increases user engagement with the system, positively reinforces user behavior by reducing screentime utilization, provides storage for the one or more mobile devices, limits access to and prevents overstimulation from the one or more mobile devices, and supports healthy bedtime routines by prioritizing user sleep quality and quantity.

[0006] In another aspect of the present disclosure the one or more sensors include: sensors for detecting user inputs to the system, including one or more of: haptic sensors, piezoresistive sensors, piezoelectric sensors, optical sensors, capacitive sensors, and elastoresistive sensors; and sensors for detecting user motions including one or more of: optical sensors, cameras, infrared sensors, and motion tracking sensors.

[0007] In yet another aspect of the present disclosure the one or more HMIs further include at least one screen and a knob, wherein the screen and knob communicate user inputs to the controller. The screen displays a variety of information, including: clock time, alarm clock time, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity, suggestions to improve sleep, and the pixel pet.

[0008] In still another aspect of the present disclosure the compartment is selectively lockable via a latch mechanism. The latch mechanism includes one or more of: a flush fitting latch, an under center latch, a spring-loaded latch, a rigid claw, a flexible fastener, a slide bolt latch, a sprung safety latch, a sprung slide bolt latch, a tight hold draw latch, a magnetic push latch, and a touch latch. The latch mechanism further includes a latch receiver with a movable portion slidably or rotatably retained within a latch housing. The movable portion includes one or more hinged jaws, the one or more hinged jaws rotatably connected via hinges to a spring-loaded sliding assembly within the latch housing, the one or more hinged jaws sized and shaped to receive and selectively retain the latch.

[0009] In still another aspect of the present disclosure the storage container includes electromagnetic field (EMF) shielding or blocking materials that prevent wireless communications from reaching into or being transmitted from within the compartment to outside the compartment when the one or more mobile devices are stored within the compartment and the access hatch is closed.

[0010] In still another aspect of the present disclosure the DBA includes: physical placement of a mobile device within or entry of the mobile device into a docking arrangement with the storage container, or compliance with a context-aware schedule, such as docking the mobile device or storing the mobile device within thestorage container after a bedtime alarm. The SRA includes a limited local network between the one or more mobile devices and the storage container, where the limited local network provides for electronic communication between the storage container and the one or more mobile devices when the one or more mobile devices are stored within the compartment and the access hatch is closed.

[0011] In still another aspect of the present disclosure the SRA further includes: a sixth control logic defining a gamification engine. The gamification engine includes logic for incrementing a shutdown streak, granting rewards, and requiring realtime authentication of a hardware validated session start (HVSS) signal before any reward logic may be executed, and for displaying a shutdown screen a passive shutdown tracker and / or an active pixel pet animation. The pixel pet defines an onscreen, gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar, or an animated device selected by the user from a predetermined group of pixel pets stored in the memory with which the user may interact. A current state of a pixel pet is determined by a state machine whose primary inputs are an unplug streak counter and total screen-free minutes obtained from the shutdown tracker. The pixel pet includes modular digital assets including: skins, accessories, and evolutions that are associated with a user profile based on achieving specific HVSS validated milestones.

[0012] In still another aspect of the present disclosure, the sixth control logic further includes control logic for displaying a current state of the pixel pet based on user inputs to the system. User inputs are classified as positive or non-positive. Positive user inputs are interactions that reduce user screentime from a first level to a second level lower than the first by gamification of behavior that makes the pixel pet happy. Positive user inputs include: play or caring, touching or petting the pixel pet,feeding or watering the pixel pet, and / or giving toys or gifts to the pixel pet. Positive user inputs cause the pixel pet to be displayed in a happy animated state. Non-positive user inputs are interactions that do not reduce user mobile device screentime consumption or adherence to desired bedtime routines. Non-positive interactions include: opening the compartment to access the one or more mobile devices before a wakeup time has been reached, or failure to place mobile devices within the compartment and closing the access hatch at or before a scheduled shutdown time. The non-positive user inputs cause the pixel pet to be displayed in a sad, depressed, or otherwise negative animated state.

[0013] In still another aspect of the present disclosure the SRA includes a seventh control logic for preparing for shutdown by automatically selecting and displaying on the one or more HMIs, one of several pixel pet animations including: the pixel pet mimicking putting a mobile device into the storage container, waving or pointing to a shutdown time display, displaying the pixel pet in a tired state with animations of rubbing eyes, yawning, and / or stretching. The seventh control logic further includes generating an audiovisual and / or tactile alarm to the user indicating that the shutdown time has been reached and displaying a pixel pet animation in an impatient mode, tapping feet, or crossing arms until the one or more mobile devices are detected within the storage container by the one or more sensors. The seventh control logic further includes control logic for, upon determining that the one or more mobile devices have been placed within the storage container and the access hatch has been closed, incrementing the shutdown streak and generating and displaying an on-screen depiction of the incrementing of the shutdown streak. The seventh control logic further includes control logic for selecting and displaying on the one or more HMIs, an animation of the pixel pet getting ready to sleep, and control logic for causing systemto enter a sleep idle state where the pixel pet is displayed on the one or more HMIs in a sleeping state with a ZZZ animation, or a ZZZ icon. The sleep idle state is indicated when the user’s mobile devices are stored within the compartment and the access hatch is closed for predetermined quantity of time.

[0014] In still another aspect of the present disclosure the SRA includes an eighth control logic for determining when a user accesses the one or more mobile devices while the sleep idle state is engaged, and upon determining that the one or more mobile devices have been removed from the storage container, displaying the pixel pet on the one or more HMIs in a wakened state with grumpy, disgruntled, or otherwise displeased appearance. The eighth control logic further includes control logic for depicting, via the one or more HMIs, a loss of an active shutdown streak, and resetting a shutdown streak counter to zero.

[0015] In still another aspect of the present disclosure a method for mobile device storage with screentime and bedtime gamification includes: receiving one or more mobile devices within one or more storage containers adapted to receive the one or more mobile devices, the one or more storage containers having an access hatch, and a compartment for receiving and at least partially containing the one or more mobile devices therein. The method further includes detecting user data with one or more sensors, and providing a tactile interface via one or more human-machine interfaces (HMIs) for users to interact with the storage container. The method further includes executing, via processors of one or more controllers, programmatic control logic stored within memory of one or more controllers. The one or more controllers further include one or more input / output (I / O) ports in communication with the one or more mobile devices, the one or more sensors, and the one or more HMIs. The programmatic control logic including at least a screentime reduction application (SRA) having control logicfor: recognizing a digital boundary action (DBA) performed by a user, and upon recognition of the DBA, initiating a communications handshake between the storage container and the one or more mobile devices upon receipt of the one or more mobile devices by the one or more storage containers. The SRA further includes control logic for generating secure, non-spoofable electronic validation of a connection between the one or more mobile devices and the one or more storage containers, and for launching a mobile application stored or accessed at least partially within memory of the one or more mobile devices. The SRA further includes control logic for accessing the one or more HMIs, including one or more screens or light sources, and depicting system-state graphics comprising: a shutdown tracker, a streak tracker, screen-free user performance, a pixel pet, and a dynamically adjusted state of the pixel pet. The SRA increases user engagement with the one or more storage containers from a first level to a second level greater than the first, positively reinforcing user behavior by reducing screentime utilization, providing storage for the one or more mobile devices, limiting access to and preventing overstimulation from the one or more mobile devices, and supporting healthy bedtime routines by prioritizing user sleep quality and quantity.

[0016] In still another aspect of the present disclosure the method further includes detecting user inputs via one or more of: haptic sensors, piezoresistive sensors, piezoelectric sensors, optical sensors, capacitive sensors, and elastoresistive sensors; and detecting user motions via one or more of: optical sensors, cameras, infrared sensors, and motion tracking sensors.

[0017] In still another aspect of the present disclosure the method further includes communicating user inputs to the controller via at least one screen and a knob, wherein the screen displays a variety of information, including: clock time, alarm clocktime, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity, suggestions to improve sleep, and the pixel pet.

[0018] In still another aspect of the present disclosure the method further includes selectively locking the compartment via a latch mechanism. The latch mechanism includes one or more of: a flush fitting latch, an under center latch, a spring-loaded latch, a rigid claw, a flexible fastener, a slide bolt latch, a sprung safety latch, a sprung slide bolt latch, a tight hold draw latch, a magnetic push latch, and a touch latch. The latch mechanism further includes a latch receiver with a movable portion slidably or rotatably retained within a latch housing. The movable portion includes one or more hinged jaws, the one or more hinged jaws rotatably connected via hinges to a spring-loaded sliding assembly within the latch housing, the one or more hinged jaws sized and shaped to receive and selectively retain the latch.

[0019] In still another aspect of the present disclosure the method further includes preventing, via electromagnetic field (EMF) shielding or blocking materials, wireless communications from reaching into or being transmitted from within the compartment to outside the compartment when the one or more mobile devices are stored within the compartment and the access hatch is closed.

[0020] In still another aspect of the present disclosure the method further includes physically placing a mobile device within or entry of the mobile device into a docking arrangement with the storage container, or complying with a context-aware schedule, such as docking the mobile device or storing the mobile device within the storage container after a bedtime alarm. The method further includes establishing a limited local network between the one or more mobile devices and the storage container, wherein the limited local network provides for electronic communicationbetween the storage container and the one or more mobile devices when the one or more mobile devices are stored within the compartment and the access hatch is closed.

[0021] In still another aspect of the present disclosure the method further includes defining a gamification engine. The gamification engine includes logic for incrementing a shutdown streak, granting rewards, and requiring real-time authentication of a hardware validated session start (HVSS) signal before any reward logic may be executed. The method further includes displaying a shutdown screen a passive shutdown tracker and / or an active pixel pet animation. The pixel pet is an onscreen, gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar, or an animated device selected by the user from a predetermined group of pixel pets stored in the memory with which the user may interact. A current state of a pixel pet is determined by a state machine whose primary inputs are an unplug streak counter and total screen-free minutes obtained from the shutdown tracker, the pixel pet includes modular digital assets including: skins, accessories, and evolutions that are associated with a user profile based on achieving specific HVSS validated milestones.

[0022] In still another aspect of the present disclosure the method further includes displaying the current state of the pixel pet based on user inputs. User inputs are classified as positive or non-positive. Positive user inputs are interactions that reduce user screentime from a first level to a second level lower than the first by gamification of behavior that makes the pixel pet happy. Positive user inputs include: play or caring, touching or petting the pixel pet, feeding or watering the pixel pet, giving toys or gifts to the pixel pet, and positive user inputs cause the pixel pet to be displayed in a happy animated state. Non-positive user inputs are interactions that do not reduce user mobile device screentime consumption or adherence to desired bedtime routines.Non-positive interactions include: opening the compartment to access the one or more mobile devices before a wakeup time has been reached, or failure to place mobile devices within the compartment and closing the access hatch at or before a scheduled shutdown time. The non-positive user inputs cause the pixel pet to be displayed in a sad, depressed, or otherwise negative animated state.

[0023] In still another aspect of the present disclosure the method further includes preparing for shutdown by automatically selecting and displaying, on the one or more HMIs, one of several pixel pet animations including: the pixel pet mimicking putting a mobile device into the storage container, waving or pointing to a shutdown time display, displaying the pixel pet in a tired state with animations of rubbing eyes, yawning, and / or stretching. The method further includes generating an audiovisual and / or tactile alarm to the user indicating that the shutdown time has been reached and displaying a pixel pet animation in an impatient mode, tapping feet, or crossing arms until the one or more mobile devices are detected within the storage container by the one or more sensors. Upon determining that the one or more mobile devices have been placed within the storage container and the access hatch has been closed, the method increments the shutdown streak and generates and displays an on-screen depiction of the incrementing of the shutdown streak. The method further includes selecting and displaying, on the one or more HMIs, an animation of the pixel pet getting ready to sleep; and causing the storage container to enter a sleep idle state where the pixel pet is displayed on the one or more HMIs in a sleeping state with a ZZZ animation, or a ZZZ icon. The sleep idle state is indicated when the user’s mobile devices are stored within the compartment and the access hatch is closed for predetermined quantity of time.

[0024] In still another aspect of the present disclosure the method further includes determining when a user accesses the one or more mobile devices while thesleep idle state is engaged, and upon determining that the one or more mobile devices have been removed from the storage container, displaying the pixel pet on the one or more HMIs in a wakened state with grumpy, disgruntled, or otherwise displeased appearance. The method further includes control logic for depicting, via the one or more HMIs, a loss of an active shutdown streak, and resetting a shutdown streak counter to zero.

[0025] Further areas of applicability will become apparent from the description provided herein. It should be understood that the description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are for illustration purposes only and are not intended to limit the scope of the present disclosure in any way.

[0027] FIG. 1A is a perspective front view of a system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0028] FIG. IB is a perspective front view of the system for mobile device storage with screentime gamification of FIG. 1A in a closed state according to an exemplary embodiment;

[0029] FIG. 1C is a partial side view of a knob of the system for mobile device storage with screentime gamification of FIGS. 1A and IB according to an exemplary embodiment;

[0030] FIG. 2A is a perspective front view of a first form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0031] FIG. 2B is a perspective front view of a second form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0032] FIG. 2C is a perspective front view of a third form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0033] FIG. 2D is a perspective front view of a fourth form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0034] FIG. 2E is a perspective front view of a fifth form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0035] FIG. 2F is a perspective front view of a sixth form factor of the system for mobile device storage with screentime gamification in an open state according to an exemplary embodiment;

[0036] FIG. 2G is a perspective front view of a seventh form factor of the system for mobile device storage with screentime gamification, where the mobile device protrudes partially and defines an interactive screen of the system;

[0037] FIG. 2H is a perspective front view of an eighth form factor of the system for mobile device storage with screentime gamification, where the system defines a piece of furniture;

[0038] FIG. 21 is a perspective front view of a ninth form factor of the system for mobile device storage with screentime gamification, where the system is capable of housing and charging multiple mobile devices;

[0039] FIG. 2J is a perspective front view of a tenth form factor of the system for mobile device storage with screentime gamification, where the system defines an interactive plushie with electronically interactive features;FIG. 3A is a partial perspective top view of a latch of the system for mobile device storage with screentime gamification in the open state of FIG. 1A according to an exemplary embodiment;

[0040] FIG. 3B is a partial perspective top view of a latch of the system for mobile device storage with screentime gamification in the closed state of FIG. IB according to an exemplary embodiment;

[0041] FIG. 3C is a partial is a perspective side view of a latch of the system for mobile device storage with screentime gamification in the open state of FIG. 3 A, including a locking assembly according to an exemplary embodiment;

[0042] FIG. 3D is a partial side view of an alternate version of a latch of the system for mobile device storage with screentime gamification of FIGS. 1A and IB, where the latch is depicted in both open and closed positions according to an exemplary embodiment;

[0043] FIG. 3E is a partial perspective side view of an alternate version of a latch of the system for mobile device storage with screentime gamification of FIGS.1A, including a locking assembly according to an exemplary embodiment;

[0044] FIG. 4A is a partial perspective top view of the system for mobile device storage with screentime gamification of FIG. 1A, including a view of a compartment and chargers disposed therein according to an exemplary embodiment;

[0045] FIG. 4B is a partial perspective top side view of the system for mobile device storage with screentime gamification of FIG. 1A, including a view of a compartment, chargers disposed therein, and the latch according to an exemplary embodiment;

[0046] FIG. 5 is a flowchart depicting a logical steps for interacting with knob and a screen of the system for mobile device storage with screentime gamification of FIGS. 1A, IB, and 1C according to an exemplary embodiment;

[0047] FIG. 6 is a flowchart depicting a series of operations of a screentime reduction application (SRA) of the system for mobile device storage with screentime gamification according to an exemplary embodiment;

[0048] FIG. 7A is a flowchart depicting logical steps of an idle state management portion of the SRA of FIG. 6 according to an exemplary embodiment;

[0049] FIG. 7B is a flowchart depicting logical steps of a shutdown preparation portion of the SRA of FIG. 6 according to an exemplary embodiment;

[0050] FIG. 7C is a flowchart depicting logical steps of a shutdown process portion of the SRA of FIG. 6 according to an exemplary embodiment;

[0051] FIG. 7D is a flowchart depicting logical steps of a sleep idle state portion of the SRA of FIG. 6 according to an exemplary embodiment; and

[0052] FIG. 7E is a flowchart depicting logical steps of a wake up process portion of the SRA of FIG. 6 according to an exemplary embodiment.DETAILED DESCRIPTION

[0053] The following description is merely exemplary in nature and is not intended to limit the present disclosure, application, or uses.

[0054] Referring to FIGS. 1 A, IB, and 1C a system 10 for mobile device 12 storage and screentime gamification is shown. The system 10 includes a mobile device 12 storage container 14 having an access hatch 16, and one or more human-machine interfaces (HMIs) 18. The storage container 14 may be formed of or otherwise made from any of a wide variety of materials and / or combinations of materials. In some examples, the storage container 14 is made of metal, plastic, wood, bamboo, paper products, textiles, or the like. The storage container 14 broadly defines abstract forms such as a box, clamshell, or figurative forms, such as animal characters, or the like. However, departures from the box or clamshell shape are intended to be within the scope of the present disclosure, without limitation.

[0055] Referring now to FIGS. 2A, 2B, 2C, 2D, 2E, 2F, 2G, 2H, 21, and 2J and with continuing reference to FIGS. 1A, IB, and 1C, a variety of distinct formfactors of the storage container 14 are shown in additional detail. It should be appreciated that each of the storage containers 14 depicted in FIGS. 2A - 2J is merely an exemplary representation of a possible non-limiting type of storage container 14 of the system 10 described herein. Departures from the types of storage containers 14 shown in FIGS. 2A - 2J and elsewhere in the figures and description are intended to be within the scope and intent of the present disclosure, however, some specific examples are contemplated herein. In the non-limiting examples shown in FIGS. 2A-2J, defines a first form factor of the system 10 for mobile device 12 storage with screentime gamification that is substantially shaped as a rectilinear box with a lid in an open state, FIG. 2B is a variation of the box of FIG. 2 A where the system 10 for mobile device 12 storage is shown in a vertical orientation with a front-opening flap. FIG. 2C is a perspective front view of a third form factor of the system 10 for mobile device 12 storage with screentime gamification in a form-factor that is similar to a traditional slot-style bread toaster. FIG. 2D is a perspective front view of a fourth form factor of the system 10 for mobile device 12 storage with screentime gamification that is similar in most aspects to the first form factor shown in FIG. 2A, but where the storage container 14 is a substantially ovoid three-dimensional solid or spherical in shape. The storage container 14 of FIG. 2E is broadly similar to the storage container 14 of FIG. 2B, but with a trapezoidal prismatic shape, and FIG. 2F depicts the storage container 14 as a substantially rectilinear solid shape. FIG. 2G is a variation of the storage container 14 where the mobile device 12 protrudes partially and defines an interactive screen of the system 10, while FIG. 2H depicts the storage container 14 as a portion of a nightstand or other similar piece of furniture. FIG. 21 depicts the storage container 14 in a form broadly similar to that in FIG. 2A, but where the system 10 is capable of housing and charging multiple mobile devices 12 simultaneously. Finally, FIG. 2 J is a depiction of a variation of the system 10, where the system 10 defines an interactive plushie 15 with electronically interactive features, including a screen or light source. The plushie 15 may vary in size, type, form-factor, or the like without departing from the scope or intent of the present disclosure. In some non-limiting examples, the plushie 15 may be a soft toy with a sensor tag approximately the size of a mobile device 12, such as a mobile phone, or the plushie 15 may be significantly larger.

[0056] In the non-limiting example of FIGS. 1A and IB, the storage container 14 is a rectilinear box having a bottom 20, a plurality of sides 22A, 22B, 22C, 22D, and a lid 24. The lid 24 forms the access hatch 16 of the system 10 of FIG. 1 , and the lid 24 is rotatably attached to one or more of the plurality of sides 22A, 22B, 22C, 22D by a hinge 26. The hinge 26 may be any of a wide variety of known types, including butt hinges, butterfly hinges, flush hinges, tee hinges, barrel hinges, piano hinges, spring hinges, multiple joint hinges, multi-axis hinges, friction hinges, or thelike. In further examples, the hinge 26 may be formed of the same or a part of the same material as the rest of the storage container 14, and may be physically continuous with the storage container 14. That is, in some examples, the hinge 26 may be a flexible portion of the material forming the storage container 14, such that that the hinge 26 of the storage container 14 is a flexible component allowing the lid 24 or access hatch 16 of the system 10 to rotate or move in a hinged fashion relative to other portions of the storage container 14. The access hatch 16 or lid 24 is movable relative to other portions of the storage container 14 between at least a closed position 28 and an open position 30.

[0057] The storage container 14 further includes one or more biasing members 32. The biasing member or members 32 of some non-limiting examples, link the access hatch 16 or lid 24 to the storage container 14, and bias the access hatch 16 or lid 24 toward and / or into the open position 30. The biasing member or members 32 may include any of a variety of different types of biasing members 32 without departing from the scope or intent of the present disclosure. In some examples, the biasing member or members 32 includes one or more of: a linear spring, a coil spring, an extension spring, a compression spring, a spiral spring, a torsion spring, a wave spring, a clock spring, a volute spring, a molded spring, or the like. The biasing member or members 32 may be formed of a wide variety of materials including but not limited to: metals, plastics, shape memory alloys, ceramics, and the like. The biasing member or members 32 may be formed integrally with the storage container 14 and / or the lid 26, and may interconnect the storage container 14 and lid 26, making use of the flexural material properties (i.e. the bending coefficient or flexibility) of the materials forming the storage container 14 and lid 26, and causing the materials forming the storage container 14 and lid 26 to operate, at least in a designated region, as the biasing memberor members 32. In additional examples, the biasing member or members 32 may be co-located and / or integrated into the hinge 26, while in other examples, the biasing member or members 32 may be distinct or separate from the hinge 26. In some nonlimiting examples, the biasing members 32 may include dampers or damping mechanisms that alter or control a rate at which the lid 26 or access hatch 16 open and / or close. Such dampers or damping mechanisms may include mechanical, magnetic, viscous damping, friction damping, mechanical stop, gas-assisted damping, and / or spring-loaded damping mechanisms, and the like. In additional examples, the biasing members 32 may define motors or motorized assemblies, with or without gear reduction, to open and / or close the lid 24 or access hatch 16.

[0058] Referring now to FIGS. 3A, 3B, 3C, 3D, and 3E and with continuing reference to FIGS. 1A - 1C, and 2A - 2J, the storage container 14 further includes a latch mechanism 34 that selectively retains the access hatch 16 or lid 24 in the closed position 28. The latch mechanism 34 may define any of a wide variety of different mechanisms without departing from the scope or intent of the present disclosure. The latch mechanism 34 selectively retains the access hatch 16 or lid 24 in the closed position 28. In some non-limiting examples, the latch mechanism 34 is a spring latch, touch latch, or other such push latch that selectively retains the access hatch 16 or lid in the closed position 28, and when actuated from the closed position 28, causes the access hatch 16 or lid 24 to move towards or into the open position 30. The latch mechanism 34 consists primarily of two components: a latch 36 and a latch receiver 38.

[0059] In some examples, the latch mechanism 34 is spring-loaded. The latch 36 may include a magnetic portion sized, shaped, and located to interact with a paired magnetic component of the latch receiver 38 disposed on or formed integrally with the access hatch 16 or lid 24. In alternate examples, the latch 36 may be locatedon or formed integrally with the access hatch 16 or lid 24, and sized, shaped, and located to interact with a latch receiver 38 disposed on or formed integrally with the storage container 14 itself. The latch 36 and latch receiver 38 may vary substantially from application to application without departing from the scope or intent of the present disclosure. Exemplary non-limiting latch mechanisms 34 may include flush fitting latches, under center latches, flexible fasteners, adjustable fasteners, spring-loaded latches, rigid claws, slide bolt latches, sprung safety latches, sprung slide bolt latches, tight-hold draw latches, magnetic push latches, touch latches, and the like. In several aspects, the latch mechanism 34 is a one-touch push latch opening mechanism that allows access to a compartment 42 formed within the storage container 14.

[0060] In a specific, but non-limiting example, the latch receiver 38 includes a movable portion 44 slidably and / or rotatably retained within a latch housing 46. The movable portion 44 includes one or more jaws 48 sized and shaped to receive and selectively retain the latch 36. The jaws 48 of the example shown in FIGS. 3A -3C are rotatably connected via hinges 50 to a spring-loaded sliding assembly 52 within the latch housing 46. The spring-loaded sliding assembly 52 is attached at a distal end 54 to a spring 56 which is also disposed within the latch housing 46. The distal end 54 of the spring-loaded sliding assembly 52 is opposite the jaws 48. A guide rod 58, located coaxially within the spring 56 is affixed to the spring-loaded sliding assembly 52 at a first end, and to a locking pin 60 at a second end distal to the first end. The locking pin 60 selectively rides within an aperture 62 formed in a side of the latch housing 46. The aperture 62 may take a variety of different shapes without departing from the scope or intent of the present disclosure. However, in an exemplary nonlimiting embodiment, the aperture 62 defines a Z-shaped opening. As the latch receiver 38 is depressed into the latch housing 46, the locking pin 60 enters the aperture 62 at afirst end 64. The spring 56 biases the latch receiver 38 and locking pin 60 towards an open-latch position 66. However, the Z-shaped aperture 62 limits movement of the locking pin 60 towards the open-latch position 66 at a first detent 68. When the locking pin 60 is located at the first detent 68 the jaws 48 of the latch receiver 38 are in a closed-latch position 70, and thereby positioned to retain the latch 36 between and within the jaws 48. A press of the latch 36 axially towards the distal end 54 of the spring-loaded sliding assembly 52 causes the locking pin 60 to ride towards a second detent 72, which limits travel of the spring-loaded sliding assembly 52 within the latch housing 46, and the spring 56 subsequently biases and pushes the spring-loaded sliding assembly 52 and locking pin 60 towards a second end 74 of the aperture 62, thereby causing the jaws 48 to open and for the latch 36 to be released from the jaws 48.

[0061] In additional examples, such as those shown in FIGS. 3D and 3E, the latch mechanism 34 may, rather than having jaws 48, utilize a roller assembly 76 that interacts and selectively latches or locks with a hook-shaped latch 36. It will be appreciated that other types of latch mechanisms 34 and latch 36 and latch receiver 38 shapes and configurations are within the scope and intent of the present disclosure. The roller assembly 76 of such examples is on an articulating arm 78, truncating in a roller 79, that is operable between at least the closed-latch position 70 and the open-latch position 66. A torsion spring 80, or similar biasing member, biases the articulating arm 78 towards the open-latch position 66, while a locking plate 82 selectively retains the articulating arm 78 in the closed-latch position 70, while an opening plate 84 is actuated by pressing the latch 36 towards the articulating arm 78, whereupon the articulating arm 78 is released from the closed-latch position 70 thereby allowing the latch 36 and latch receiver 38 to physically be separated from one another.

[0062] In further non-limiting examples, the latch mechanism 34 may further include a locking assembly 86 that selectively prevents the locking pin 60 or locking plate 82 from releasing the latch 36 until the locking assembly 86 is activated. The locking assembly 86 may include a mechanical, electromechanical, pneumatic, hydraulic, magnetic, electromagnetic, or other such actuator that may be selectively activated or actuated to engage the locking pin 60, the locking plate 82, the opening plate 84, or other such portion of the latch mechanism 34, and to thereby selectively release the latch mechanism 34 into the open-latch position 66. Likewise, the locking assembly 86 may, when not activated, prevent the system 10 from releasing the latch mechanism 34, thereby preventing user access to the compartment 42 and any mobile devices 12 stored therein.

[0063] Turning now to FIGS. 4A and 4B, and with continuing reference to FIGS. 1 A - 1C, 2A - 2J, and 3A-3E, the compartment 42 is sized and shaped to at least temporarily house a mobile device 12 such as a cellular phone, tablet, or other such portable computing device fully within the compartment 42 such that the access hatch 16 or lid 24 selectively fully encloses the compartment 42 when the access hatch 16 or lid 24 is in the closed position 28. In some non-limiting examples, the access hatch 16 or lid 24 may be in the form of a sliding, rotating, or otherwise movable drawer 87, or the like. In some examples, the compartment 42 may define a rectilinear prism-shaped void within the storage container 14, however, other compartment 42 shapes are contemplated. In addition, the compartment 42 may be sized and shaped to house and at least temporarily fully enclose only a single mobile device 12, or may be sized and shaped to house and fully and / or partially enclose multiple mobile devices 12, without departing from the scope or intent of the present disclosure. In some non-limiting examples, the compartment 42 may be sized and shaped to precisely fit a particularmodel of mobile device 12, or may be designed to more universally accept, house, and store a variety of mobile devices 12 from a variety of different manufacturers. In some examples, compartment 42 may be provided with a variety of differently sized adapters sized, shaped, and designed to interact with and connect various specific different types of mobile devices 12.

[0064] The compartment 42 may, in some non-limiting examples, be constructed of or lined with materials that define an electromagnetic field (EMF) shield or Faraday cage, such that when the mobile device(s) 12 are stored within the compartment 42, and the access hatch 16 or lid 24 are in the closed position 28, the compartment 42 blocks wireless electromagnetic (EM) signals to and from the mobile device(s) 12, where the wireless EM signals originate from or are transmitted to sources external to the system 10. Such signals may include radio-frequency (RF) transmissions, and the like. Faraday cage materials block EM radiation, including but not limited to cellular, Bluetooth, and WiFi communications. Exemplary, non-limiting conductive materials that may be used to construct a Faraday cage within the compartment 42 include but are not limited to: metals and / or alloys of metals including copper, aluminum, silver, steel, stainless steel, and the like, and / or Faraday fabrics, hardware cloths, and the like.

[0065] The system 10 further includes one or more controllers 100. Each of the controllers 100 is a non-generalized, electronic control device having a preprogrammed digital computer or processor 102, non-transitory computer readable medium or memory 104 used to store data such as control logic, software applications, instructions, computer code, data, lookup tables, etc., and a transceiver or input / output (I / O) ports 106. Computer readable medium or memory 104 includes any type of medium capable of being accessed by a computer, such as read only memory (ROM),random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory 104. A “non-transitory” computer readable memory 104 excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable memory 104 includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device. Computer code includes any type of program code, including source code, object code, and executable code. The processor 102 is configured to execute the code or instructions.

[0066] The controller 100 may be a dedicated Wi-Fi controller, an actuator control module, an infotainment control module, a display control module, or the like. The transceiver or I / O ports 106 are configured to wirelessly communicate using WiFi protocols under IEEE 802.1 lx, or the like.

[0067] The memory 104 further stores one or more applications 108. An application 108 is a software program configured to perform a specific function or set of functions. The application 108 may include one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The applications 108 may be stored within the memory 104 or in additional or separate memory. Examples of the applications 108 include audio or video streaming services, games, browsers, social media, and the like.

[0068] In some non-limiting examples, the system 10 further includes one or more sensors 107 in communication with the one or more controllers 100 via the I / O ports 106. The sensors 107 may include any of a wide variety and quantity of sensors 107 including but not limited to: haptic sensors, motion sensors, cameras, infraredsensors, tactile sensors including piezoresistive, piezoelectric, optical, capacitive and / or elastoresistive sensors, Hall effect sensors 107 and the like. In some examples, the system 10 may utilize motion tracking sensors to track user sleep movements and activities. The sensors 107 may further be linked to and in communication with one or more light sources 109. The light sources 109 may include light-emitting diodes (LEDs), incandescent bulbs, electroluminescent sources, or the like without departing from the scope or intent of the present disclosure. In some examples, the light sources 109 define backlighting for the screen 118 of the system 10, while in others, the light sources 109 may be standalone sources of illumination positioned at locations other than the screen 118. In additional examples, the light sources 109 may be in communication with the sensors 107 and the controllers 100 such that when user movement is detected by the sensors 107 the system 10 causes the light sources 109 to illuminate in a nightlight mode. By operating in a nightlight mode, the light sources 109 of the system 10 reduce the potential of user injury when the user would otherwise be moving in the dark. The illumination of the light sources 109 may also be linked to user interaction with the system 10.

[0069] One or more of the sensors 107 may be integrated into a touch-sensitive portion 111 of the system 10. The touch-sensitive portion 111 may include a touch bar, a touch-sensitive strip of material, a touch sensitive surface separable from or integrated directly into an exterior surface or aspect of the system 10, or the like. The touch-sensitive portion 111 may be a tactile sensor 107 including piezoresistive, piezoelectric, optical, capacitive and / or elastoresistive sensor 107, or the like. In several aspects, the touch-sensitive portion 111 may be used to access various functions of the system 10, including alarm functionality, snooze functionality, and any of a variety of additional functions that are described in additional detail herein.

[0070] In several aspects despite the presence and use of a Faraday cage, the mobile device 12 storage container 14 is in either wired or wireless communication with the wireless device(s) 12 stored within the compartment 42. To achieve such connectivity, any Faraday cage componentry of the storage container 14 is constructed to allow a limited local network between the mobile device 12 and the storage container 14, thereby allowing the mobile device 12 and storage container 14 to exchange information. The mobile device 12 storage container 14, therefore, includes a plurality of electrical components, including the controller 100. Electrical energy is provided to the electrical components of the storage container 14 via one or more of an on-board battery, and an electrical cord connecting the storage container 14 to an external power supply (not specifically shown). As the mobile device storage container 14 of some examples includes a mobile device 12 charging apparatus 110, the compartment 42 is equipped with one or more of a wireless charger 112 or wired charging ports 114. The mobile device 12 may further be connected via wired and / or wireless connections to the I / O ports 106 of the controller 100 for data transfer or communications. Thus, the mobile device 12 may be charged and / or linked to controllers 100 of the storage container 14 while the mobile devices 12 are stored within the compartment 42.

[0071] The storage container 14 further includes one or more humanmachine interfaces 18. The HMIs 18 may vary substantially from application to application, without departing from the scope or intent of the present disclosure. In some non-limiting examples, the HMIs 18 include at least a screen 118 and a knob 120. As the precise form factor of the system 10 may vary from application to application, the screen 118 and knob 120 may be located at various different positions on or within the system 10, and in some examples, the screen 118 and knob 120 may be combined with or accessed through a digital tactile interface, such as a touchscreen. That is, insome examples, the screen 118 itself may be a touchscreen and the system 10 may not include a physical knob 120, but rather, the knob 120 may be a graphical user interface (GUI) that lets the user interact with the system 10 and storage container 14 to adjust system 10 settings and otherwise interact with the system 10 as will be discussed in additional detail herein.. In additional examples, the knob 120 may include a screen 118 or touchscreen interface through which system 10 functions or applications 108 may be accessed. Similarly, the access hatch 16 or lid 24 may be located at various different positions or in various orientations on the system 10, depending on the particular form factor of the storage container 14.

[0072] The screen 118 displays information generated by the controller 100 and transmitted through wired and / or wireless connections to and from the I / O ports 106 thereof. Likewise, the knob 120 communicates user inputs to the controller 100 via the I / O ports 106 via wired and / or wireless connections. In some examples, the knob 120 includes one or more screens 90, and may display a variety of different types of information, including but not limited to: clock time, alarm clock time, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity and / or to improve sleep, or the like. The knob 120 may further display information, including daytime and nighttime indicators 122, 124.

[0073] The knob 120 may have any of a variety of different form-factors without departing from the scope or intent of the present disclosure. In some examples, the knob 120 is substantially cylindrical in shape, and may have a grippy or ribbed texturized circumferential portion 126 optimally shaped to be grasped by and manipulated by a user’s hand. In additional examples, the knob 120 may have a smooth circumferential portion 126. In further examples, the knob 120 may, rather than being cylindrical in general shape, be of any other shape without departing from the scope orintent of the present disclosure. The knob 120, or a portion of the knob may be movable in at least two directions: an axial direction 100, and a rotational direction 102. In additional examples, the knob 120 may only move in the rotational direction 102, and rather than also moving in an axial direction, the knob 120 may have one or more buttons or touch-screen interfaces disposed on an outward-facing surface 104.

[0074] The system 10 of the present disclosure provides system 10 users a way to control a quantity of screentime consumed by providing a lockable, gamified storage container 14 for the user’s mobile devices 12, and thereby both reducing screentime, and increasing the quality and quantity of rest, sleep, or screen-free time. To achieve these goals, a variety of system 10 functions are accessible via the screen 118, and the knob 120.

[0075] Referring once more to FIGS. 2A-2J, and more specifically to FIG.2G, the system 10 may store one or more mobile devices 12 by only partially enclosing the mobile devices 12, such as within a phone dock or speaker dock 117. While the speaker dock 117 version of the system 10 depicted in FIG. 2G is substantially spherical and includes a slot-like aperture into which the mobile device 12 may be placed, it should be appreciated that other form factors are intended to be within the scope of the present disclosure, without reservation. In such non-limiting examples in which the mobile device 12 protrudes at least partially from the storage container 14 or dock, the system 10 utilizes the screen 118 or at least a portion of the screen 118 of the mobile devices 12 to display information to system 10 users. That is, upon placing a mobile device 12 within or docking the mobile device 12 with the gamified storage container 14, the mobile device 12 electronically links with the storage container 14, and the system 10 utilizes the screen 118 of the mobile devices 12 as the system displays.

[0076] The mobile device 12 may further be connected via wired and / or wireless connections to the I / O ports 106 of the controller 100 for data transfer or communications. Thus, the mobile device 12 may be charged and / or linked to controllers 100 of the storage container 14 while the mobile devices 12 are stored or docked at least partially within the compartment 42.

[0077] In several non-limiting examples, the user may perform a digital boundary action (DBA) designed to be low-effort, either by physical placement of the mobile device 12 within or entry of the mobile device 12 into a docking arrangement with the storage container 14. In additional non-limiting examples, the DBA may define compliance with a context-aware schedule, such as docking the mobile device 12 or storing the mobile device 12 within the storage container 14 after abedtime alarm, or the like. In an exemplary non-limiting DBA, the user seats their mobile device 12 into or onto a dedicated storage location, such as the compartment 42, or a docking port of the storage container 14 and the controller 100 verifies the connection via the I / O ports 106. The controller 100 detects successful establishment of a persistent electrical or data connection, such as confirmation of a Qi charging power draw, a hard-wired data handshake signal such as a USB-C data handshake, a mechanical switch, or an NFC tag from the mobile device 12, confirming correct placement. In several nonlimiting aspects, the persistency of an electrical or data connection may vary from application to application and depending on mobile device 12 and / or controller 100 hardware capabilities. In some examples, the persistency may be defined as a predetermined duration or quantity of time where an electrical and / or data connection has been established, and / or by the establishment or completion of certain security validations, such as a hardware validated session start (HVSS) signal, or the like.

[0078] Validation of the connection between the mobile device 12 and the storage container 14 may be performed by HVSS signals, serving as secure, non-spoofable electronic proof that the DBA is properly being enforced. The hardware controller 100 generates an authenticated electronic signal that serves as the system’s 10 official record that the mobile device 12 is now physically contained, docked, or otherwise disabled in a specified resting mode. The controller 100 then transmits the HVSS signal to the mobile device 12 via a local limited network or direct connection. Transmission of the HVSS signal triggers the initialization or start of a mobile application 128 to execute a specific routine, such as launching from the background, overriding a lock screen display, or the like, and the mobile application 128.

[0079] In some examples, the mobile application 128 moves the gamification display or screen 118 fully or partially from the storage container 14 to the mobile device 12 or mobile devices 12 all while maintaining the non-spoofable hardware validation between the mobile devices 12 and the storage container 14. In a non-limiting example where the mobile device 12 defines the screen 118 of the system 10, the mobile application 128 is responsible for receiving the HVSS signal from the storage container 14 hardware and taking control of the mobile device’s 12 screen 118 interface. In other non-limiting examples where the mobile device 12 does not operate as the screen 118 of the system 10, the mobile application 128 communicates with the storage container 14 itself and causes the screen 118 of the storage container 14 to depict various system-state graphics, such as a shutdown tracker, gamified aspects of the mobile application 128, including but not limited to a pixel pet and development of the pixel pet, as will be described in additional detail below, or the like. Where the mobile application 128 displays system-state graphics on the mobile device 12 screen 118, the display may include the shutdown tracker, gamified aspects of the mobileapplication 128, including the pixel pet, or the like, in response to receiving an external hardware validation signal.

[0080] The mobile application 128 further includes a gamification engine that runs the pixel pet’s state machine and shutdown streak logic locally on the mobile device 12. The gamification engine includes logic for incrementing a shutdown streak appropriately, granting rewards, and may be disabled by default, requiring real-time authentication of the HVSS signal before any reward logic may be executed. The display or screen 118 interface defines the output display for the gamification engine. Upon receiving an HVSS signal, the mobile application 128 displays the appropriate shutdown screen and either a passive shutdown tracker or an active pixel pet animation. In some non-limiting examples, the shutdown tracker may be an on-screen 118 depiction, graphical representation, or other such image that informs a user of their success in meeting daily unplug and recharging goals. In some aspects, the shutdown tracker may assist adults individuals, in particular, to keep at a certain level of unplug / recharge time each day, and may positively influence or “nudge” the user into a more desirable pattern of mobile device 12 usage.

[0081] In several aspects, a user may interact with the knob 120 in at least three distinct ways. First, the user may interact with the system 10 and storage container 14 manually, where the knob 120 may be turned to access core functions of the storage container. Second, upon pairing the storage container 14 and mobile device 12 via Bluetooth, or the like, the user may place their mobile device 12 within the storage container 14, thereby utilizing the storage container 14 as a concealed charger and clock. The mobile device 12 may ring at a specified alarm time within the storage container 14, or may utilize a Bluetooth-connected speaker within the storage container 14. The user may also set up an automation on their mobile device 12 to turn off thealarm when the mobile device 12 is removed from the storage container 14. Finally, the user may interact with the system 10 via the mobile application 128 to access various system 10 controls and settings, as well as remote monitoring of unplugging successes (i.e. parental supervision of child-screentime utilization).

[0082] Turning now to FIG. 5, an exemplary, non-limiting knob 120 interaction flowchart 200 depicting a plurality of logical steps of applications 108 accessible through the knob 120 are shown. The system 10 of the present disclosure offers both a lockable, gamified storage container 14 for user’s mobile devices 12, and clock and alarm clock functionality as well. In additional examples, the system 10 may be equipped with one or more speakers, light sources, vibration motors, or the like to provide audible, visual, and tactile responses to user inputs, as well as alarm, whitenoise emission, and the like, without limitation. The knob 120 may be manipulated to access each of the various applications 108 of the system 10.

[0083] Knob 120 interaction begins at block 202 while the system 10 is in an idle state. At blocks 204, 206, 208 and 210, distinct functions or applications 108 of the system are accessed by manipulation of the knob 120. Specifically, at block 204 when the user provides a single long press of the knob 120, a clock settings application 212 is initialized. The single long press of the knob 120 may vary from application to application, and from system 10 to system 10. However, in a non-limiting example, the single long press is contemplated as extending for at least five seconds. The single long press may also be accomplished by axial depression of the knob 120, or by similar tactile long presses on a touch-screen version of the system 10, or the like. Once the clock settings application 212 has been initialized, the user is prompted, via information displayed on the screen 118, to select a desired time zone UTC. At block 214, the user turns or rotates the knob 120 to change from one time zone to another until the desiredtime zone UTC is displayed on the screen 118. Once the desired time zone UTC is displayed, the user selects the desired time zone UTC by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration.

[0084] Once the desired time zone UTC has been selected at block 214, the clock settings application 212 proceeds to block 216 where the user is prompted, via information displayed on the screen 118, to select a desired date. At block 216, the user rotates the knob 120 to change from one date to another until the desired date is displayed on the screen 118. Once the desired date is displayed, the user selects the desired date by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration.

[0085] Once the desired date has been selected at block 216, the clock settings application 212 proceeds to block 218 where the user is prompted, via information displayed on the screen 118, to select a desired time format in a twelve-hour or twenty-four hour (12h / 24h) binary selection. In additional examples, the desired time format may vary from twelve-hour or twenty-four hour formats to include binary time displays, analog clock displays, and the like. At block 218, the user rotates the knob 120 to change from one time format to another until the desired time format is displayed on the screen 118. Once the desired time format is displayed, the user selects the desired time format by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration.

[0086] Once the desired time format has been selected at block 218, the clock settings application 212 proceeds to block 220 where the user is prompted, via information displayed on the screen 118, to select a desired time in hours and minutes. At block 220, the user rotates the knob 120 to change from one time to another until the desired time is displayed on the screen 118. Once the desired time is displayed, the user selects the desired time by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration.

[0087] Subsequently at block 222, the user is prompted, via information displayed on the screen 118 to select a brightness setting for the screen 118. The brightness settings may include manual brightness, auto-dimming, and auto-on, each having distinct sub-settings. At block 222, the user rotates the knob 120 to change between at least manual brightness settings, auto-dimming settings, and auto-on settings, sub-menus for each of which are subsequently accessed by a brief axial press of the knob 120. Specifically at block 224, when the user selects manual brightness settings, the user is subsequently prompted to rotate the knob 120 to select a screen 118 brightness setting, which is then stored in memory upon receipt of a brief axial press of the knob 120. By contrast, when at block 226, the user selects auto-dimming, a submenu is presented on the screen 118 in which the user is prompted to select a quantity of time after which an auto-dimming of the screen 118 will occur after a system 10 shutdown. The quantity of time before auto-dimming occurs is selected by the user via rotation of the knob 120 and a subsequent short press of the knob 120. Similarly, at block 228, when the user selects auto-on settings, a sub-menu for auto-on before wakeup is presented on the screen 118. The auto-on submenu provides the user a selectable quantity of time during which illumination of the screen 118 occurs beforean audible or tactile wake-up alarm is emitted by the system 10. In some examples, when the system 10 begins an auto-on process before wake-up, the screen 118 progressively illuminates from a state with zero or very low illumination levels to a fully lit illumination level.

[0088] Referring once more to block 206, when the user provides a single intermediate length press of the knob 120, an alarm settings application 250 is initialized. The single intermediate length press of the knob 120 may vary from application to application, and from system 10 to system 10. However, in a nonlimiting example, the single intermediate length press is contemplated as extending for about two seconds. The single intermediate length press may also be accomplished by axial depression of the knob 120, or by similar tactile long presses on a touch-screen version of the system 10, or the like. Furthermore, at block 250, within the alarm settings application, the user is prompted, via information displayed on the screen 118, to select a desired shutdown alarm on / off state. At block 250, the user rotates the knob 120 to change from shutdown alarm on to shutdown alarm off, or vice-versa until desired shutdown alarm on / off state is displayed on the screen 118. Once the desired shutdown alarm on / off state is displayed, the user selects the desired shutdown alarm on / off state by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration. The shutdown alarm of the system 10 includes an audio, visual, and / or tactile output from the system 10 that indicates to the user that it is time for the user to cease screentime usage and to transition to resting, sleeping, or the like.

[0089] At block 252, the user is subsequently prompted, via information displayed on the screen 118, to select a desired shutdown alarm time in hours andminutes. At block 252, the user rotates the knob 120 to change shutdown alarm time settings in hours / minutes until a desired shutdown alarm time setting is displayed on the screen 118. Once the desired shutdown alarm time setting is displayed, the user selects the desired shutdown alarm time setting by a single short press of the knob 120.

[0090] At block 254, the user rotates the knob 120 to change from wakeup alarm on to wakeup alarm off, or vice-versa until desired wakeup alarm on / off state is displayed on the screen 118. Once the desired wakeup alarm on / off state is displayed, the user selects the desired wakeup alarm on / off state by a single short press of the knob 120. The single short press may vary in length depending on system 10 componentry, hardware, versions, and the like, but should be appreciated to be less than one second in duration. The wakeup alarm of the system 10 includes an audio, visual, and / or tactile output from the system 10 that indicates to the user that it is time for the user to wake up, cease resting, or the like. In several aspects, once the wakeup alarm time is achieved, the lid 24 or the access hatch 16 of the system 10 opens and allows the user access to the user’s mobile device 12.

[0091] At block 256, the user is subsequently prompted, via information displayed on the screen 118, to select a desired wakeup alarm time in hours and minutes. At block 256, the user rotates the knob 120 to change wakeup alarm time settings in hours / minutes until a desired wakeup alarm time setting is displayed on the screen 118. Once the desired wakeup alarm time setting is displayed, the user selects the desired wakeup alarm time setting by a single short press of the knob 120.

[0092] At block 258, the user is prompted to select an alarm snooze on / off state. The user rotates the knob 120 to change snooze states between on and off, and may additionally select a snooze alarm length of time by rotation of the knob 120 and subsequent short-presses of the knob 120.

[0093] Referring once more to block 208, the user may access context specific actions within the system 10 via manipulation of the knob 120 as well. Within a settings display of the screen 118, for example, the user may perform a short duration press or push of the knob 120 to change between distinct options or settings of the system 10. In some specific non-limiting examples, the knob 120 may be pressed to enter a settings mode 260 and cycle through a series of options 262 within the settings mode 260. Likewise, the knob 120 may be pressed when the alarm is ringing 264 to turn the alarm off 266, or when an on-screen pixel pet 300 is active 268, interact 270 with the pixel pet 300. Additionally, in some examples, the alarm may be silenced, snoozed, or disabled by opening the access hatch 16 or lid 24. The pixel pet 300 is an on-screen gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar, or an animated device selected by the user from a predetermined group of pixel pets stored in the memory 104, or the like, with which users may interact. In additional situations where no alarm is active 272, the user may press the knob 120 to cause the system 10 to display or show a current date 274 on the screen 118. It should be appreciated that while in the foregoing the terms “long press”, “intermediate press” and “short press” have been defined and used in relation to specific actions, departures from these long, intermediate and short press durations are contemplated as being within the scope of the present disclosure. Moreover, it should be appreciated that a long press could be replaced by a short press or an intermediate press, or by a multiplicity of presses of various different or identical durations, or by fewer presses of any of the above kinds in a given system 10, or according to a user’s preferred interaction methodology. That is, the explanations of “long press”, “intermediate press”, and “short press” in connection with the actions described herein should be understood to be merelyexemplary, but non limiting, and that variations, combinations, or permutations of presses of different types and durations are intended to be within the scope of the present disclosure.

[0094] In additional examples, beginning at block 210, the knob 120 may be turned by the user to cause the system 10 to execute additional context-specific actions including but not limited to: entering a settings sub-menu 276 and setting parameters 278 within the settings sub-menu 276 of the system 10; when the pixel pet 300 is active 280, interacting 282 with the pixel pet 300; setting screen 118 brightness 284, or the like. A period of extended inactivity may define a time-out function, during which the screen 118 reverts to an off state, or a default display state, depending on which user-selected options are currently stored as preferences in memory 104, and subsequently ending 286 and / or returning to the start or beginning 202 of the knob 120 interactions.

[0095] It should be noted that while the events depicted in the flowchart 200 of FIG. 5 are represented as occurring in a particular order, other orders or sequences of events that depart from those shown and described are intended to be within the scope of the present disclosure.

[0096] The system 10 may include a variety of operating modes, including at least elevated “administrator” modes and non-administrative, i.e. “user” modes. In the elevated modes, which may be accessible directly on the system 10, or via a screentime reduction application (SRA) 400 on an administrative user’s mobile device 12. Both the administrator and user modes are accessible via a login prompt within the SRA 400. Upon logging into the SRA 400 with elevated administrator credentials, a main dashboard of the SRA 400 is displayed on the logged-in person’s mobile device 12 and / or on the screen 118 of the system 10.

[0097] The main dashboard of the SRA 400 includes user profile control functionality, where the administrative user can create and / or remove administrative and non-administrative user profiles from the system 10. In addition, the main dashboard offers the administrative user animation and reward control settings. Animation control settings are used to alter or customize the pixel pet 300, including altering an appearance of the pixel pet 300, setting interaction modes, and enabling or disabling artificial intelligence (Al) aspects of the pixel pet 300. The pixel pet’s 300 current visual state (e.g. happy, sleeping, deteriorating, evolving, or the like) is determined by a state machine whose primary inputs are an unplug streak counter and the total screen-free minutes from the tracker. The pixel pet 300 may include a variety of different modular digital assets. Modular digital assets associated with the pixel pet 300, including but not limited to accessories, skins, and evolutions. The modular digital assets may be associated with a user profile based on achieving specific HVSS-validated milestones, such as a 30-day streak, or the like. The administrative user may further access shutdown streak settings, including setting streak goals, setting streak rewards, resetting a non-elevated user’s streak, and setting streak values. In further aspects, the SRA 400 may be used to continuously aggregate and store objective metrics relating to screen-free user performance, such as total accumulated screen-free minutes, average nightly unplugged time, and the like. The SRA 400 further provides a strict logic module that increments only once per twenty-four hour period, following the successful receipt of an HVSS signal. The counter resets to zero when or if the DBA is not validated within the required time window.

[0098] Alarm clock settings are also available via the main dashboard. The alarm clock settings may include time zone, date settings, alarm and time formats (12h / 24h), alarm times for both shutdown and wakeup, including configurations forshutdown times and sounds, wake-up times and sounds, and the ability to configure additional alarms and sounds, without limitation. The alarm clock and snooze functionality may also be enabled or disabled from within the administrative main dashboard.

[0099] In addition to the above, from within the administrative account, the main dashboard may be used to alter screen 118 brightness, auto-dimming timing and settings (i.e. on / off), display settings such as font size and styles, and the like. Administrative access within the main dashboard also includes the ability to alter wireless communication (WiFi) and Bluetooth settings, wireless / wired charger 112, 114 type and settings, as well as altering backlight control for the screen 118, including a night light function, wake-up light function, and light color preferences. Sound control, including volume settings, and UI sound effects are also accessible through the main dashboard in the administrator accounts. In some examples, the system 10 may be equipped with microphone sensors 107 which may receive voice commands from users both administrative and non-elevated. In the administrator main dashboard, administrative users may activate or disable voice commands, configure voice commands, and activate or deactivate smart speaker functionality.

[0100] Administrative users may also access user analytics, such as usage statistics, usage limits, goals, and rewards, and notifications and alerts relevant to all or a subset of system 10 users. Such information may also be exported to the administrative user’s mobile device 12, to an email account, or the like. Individual user analytics, including personal usage statistics, the achievement of various badges or rewards, and personal reports are also available within the administrative main dashboard. In some non-limiting examples, the analytics may be sent directly from one or more mobile devices 12 to the storage container 14 and subsequently from thestorage container 14 to the administrative access portion of the main dashboard. In other non-limiting examples, the analytics may be transmitted to a remote server, such as a cloud-based computing device, or the like, and then retrieved by the administrative access portion of the main dashboard upon receipt of an appropriately authorized user request.

[0101] In some examples, the system 10 may allow for community interactions with users of other storage containers 14 in the system 10. That is, each of the storage containers 14 may be wirelessly enabled and in communication with a remote computing device that provides for anonymized and / or attributed collaboration and competition between system 10 users. In some examples, the administrative main dashboard allows administrative users to view other users’ profiles, add / remove friends, share in activities and social games, such as competing or achieving badges or goals with friends, and / or creating and trading pixel pets 300 among connected users, as well as the ability to send and receive messages to and from other system 10 users.

[0102] By contrast, the non-elevated “user” mode also has access to a user main dashboard that provides some of the same, but more limited access to functions described above in the administrative main dashboard. For example, the user main dashboard may provide animation reward and control settings for the pixel pet 300, including: pixel pet 300 customization options, interaction mode settings, and enabling / disabling Al pixel pet 300 functionality. Shutdown streak settings, including setting streak goals and rewards, and enabling / disabling pixel pet 300 animations are also available options within the user main dashboard. The user main dashboard also provides access to alarm clock settings, including: time zone, date, time format (12h / 24h), alarm times for both shutdown and wakeup, as well as sound configurationsettings for alarms, and on / off settings for both alarms and snooze functions of the system 10.

[0103] In additional examples, the user main dashboard provides access to settings for the screen 118, WiFi, Bluetooth, charger 112, 114, backlight control, sound control, voice control, smart speaker settings, and the like, as well as analytic information. The analytic information accessible via the user main dashboard may include personal usage statistics, badges and reward achievements, and personal reports. Moreover, the user main dashboard may provide access to community interactions, where allowed by the administrative main dashboard. Such community interactions may include, but are not limited to: sending and receiving messages, shared activities including joint animations and events, social gaming, and the ability to add / remove friends and view other user profiles.

[0104] Turning now to FIG. 6, and with continuing reference to FIGS. 1 A-1C, 2A-2J, 3A-3E, 4A, 4B, and 5, a flowchart depicting additional system 10 functions accessible through the 400 are shown. The SRA 400 is an application 108 stored in memory 104 of the controller or controllers 100 of the system 10. Operation of the SRA 400 reinforces and promotes positive user behaviors, such as reducing screen time from a first quantity to a second quantity less than the first quantity of screen time, and improving sleep quality and quantity from a first level to a second level greater than the first level through positive reinforcement and gamification of the positive user behaviors. The flowchart depicting use of the SRA 400 in FIG. 6 is intended to be an exemplary, non-limiting set of examples of how a user may interact with the system 10, though variations from the examples shown are to be considered within the scope and intent of the present disclosure. More specifically, FIG. 6 depicts information displayedon the screen 118 of the storage container 14 during use of the storage container 14 at a variety of different times, in response to user actions, and the like.

[0105] The flowchart in FIG. 6 begins at 402 where on a first day 403, the storage container 14 is in the closed position 28. During daylight hours, while it may be desirable to reduce screentime on user mobile devices 12, user activity on mobile devices 12 is less deleterious to use health and well-being than during nighttime hours. In the example shown at 402, a user-selected shutdown time 404, and a wakeup time 406 are shown. A pixel pet 300 may be displayed on the screen 118, and while the storage container 14 is in the closed position 28, during daytime, and while no user’s mobile device(s) 12 are stored therein, the pixel pet 300 is shown in a sleeping or otherwise dormant state.

[0106] Subsequently, at 408, as evening hours are entered, the pixel pet 300 is displayed on the screen 118 in a waking state, and once the shutdown time 404 has been reached, the shutdown alarm is engaged. In some examples, the shutdown alarm is an audiovisual notification that may be both displayed in an active (e.g. blinking) state on the screen 118, as well as being emitted as an audio alarm and / or vibration alarm. In addition to engaging the shutdown alarm, the storage container 14 automatically and or manually transitions to the open position 30, thereby providing user access to the compartment 42 within the storage container 14.

[0107] At 410, the user places their mobile device(s) 12 inside the compartment 42 within the storage container 14, and closes the access hatch 16 or lid 24. Upon closing the access hatch 16 or lid 24 with the mobile device 12 inside the compartment 42, the shutdown alarm stops, and the pixel pet 300 is animated to celebrate. In some examples, the celebration may include a sound effects audible to the user. In addition to the pixel pet 300 celebration, a streak counter 412 is incrementedby one. In the examples shown in the figures, the streak counter 412 includes both a numerical counter and a flame icon 413, however, the streak counter 412 may be displayed in a variety of ways without departing from the scope or intent of the present disclosure. In several aspects the streak counter 412 provides a numerical tabulation of a quantity of consecutive and / or non-consecutive days during which a system 10 user has successfully utilized the system 10 to improve screen time utilization statistics from a first level to a second level better than (i.e. indicating less screen-time) than the first level. However, when at 410, the user does not place their mobile device(s) 12 within the compartment 42 and close the access hatch or lid 16, 24, the shutdown alarm stops after a predetermined period of time, and the streak counter 412 is not incremented. In some examples, the predetermined period of time after which the shutdown alarm stops may be up to five minutes. In other examples, the user may, of their own volition and without prompting, place their mobile device(s) 12 within the compartment 42 and close the access hatch or lid 16, 24. In such unprompted examples, the shutdown alarm is disabled, and the streak counter 412 is automatically incremented once the shutdown time is reached. When, after the user has placed their mobile device(s) 12 within the compartment 42 and closed the access hatch or lid 16, 24, the shutdown alarm is reactivated.

[0108] In some non-limiting examples, the streak counter 412 may further be augmented by the addition of a streak saver or skip feature whereby a user may keep their streak active even though the user knows they will miss something. Such streak saver and / or skip features allow a certain amount of missed streak day foregiveness and may further increase interaction with the system 10 and reinforce positive and healthy screentime utilization practices.

[0109] At 414, while the user’s mobile device(s) 12 are stored within the compartment 42 with the access hatch or lid 16, 24 closed, the pixel pet 300 is displayed in a sleeping state. In some examples, the pixel pet 300 icon may be displayed with a ZZZ animation, static ZZZ icon, or the like, however departures from the above are intended to be within the scope and intent of the present disclosure.

[0110] At 416, under some circumstances, the storage container 14 may be opened prematurely, before the wakeup alarm. In such instances, the pixel pet 300 is displayed dynamically as in a wakened, but unsatisfied state, such as: rubbing its eyes, looking sad, or otherwise expressing fatigue, discomfort, disappointment, or displeasure. Furthermore, the system 10 may emit an “Oh No" sound effect, or the like, and the streak counter 412 is reset to zero (0).

[0111] A second day 417 of system 10 usage is depicted in the second row of the flowchart in FIG. 6. Beginning at block 418, the storage container 14 is in the open position 30, and the shutdown alarm is active and blinking, as the shutdown time 404 has been reached. The streak counter 412 indicates a one day streak of successful system 10 use, and the pixel pet 300 is awake and seated.

[0112] At 420, system 10 depicts on-screen 118 that the user has successfully stored their mobile device(s) 12 within the compartment 42 of the storage container 14. The successful use is shown by depicting the pixel pet 300 in a celebratory state, and incrementing the streak counter 412 by one (i.e. a 2-day streak). At 422, the storage container 14 remains in the closed position 28 with the user’s mobile device(s) 12 stored within the compartment 42, and the pixel pet 300 is shown in a sleeping or otherwise dormant state.

[0113] Subsequently, at 424, the wakeup alarm time 406 has been reached, and the wakeup alarm is activated. The wakeup alarm may include audiovisualprompts, including a flashing on-screen 118 prompt, such as “Wake Up”, or the like. Moreover, upon reaching the wakeup alarm time 406, the system 10 automatically opens the access hatch or lid 16, 24 and grants the user access to the mobile device(s) 12 stored within the compartment 42. At 426, the wake up alarm continues in conjunction with on-screen animations of the pixel pet 300 awakening until the user silences the wakeup alarm through an interaction with the system 10 such as pressing a button, pressing the knob 120, or closing the access hatch or lid 16, 24.

[0114] An exemplary seventh day 428 of system 10 usage is depicted in the third row of the flowchart in FIG. 6, and includes a streak tracker 430 in addition to, or as a part of the streak counter 412. Beginning at block 432, the storage container is in the open position 30 and the shutdown alarm is active and blinking, as the shutdown time 404 has been reached. The streak counter 412 indicates a three-day streak of successful system 10 use, and the pixel pet 300 is awake and seated. In addition, the streak tracker 430 depicts a fourth consecutive flame icon 413 that is blinking. Upon successfully enclosing one or more mobile devices 12 within the compartment 42 and closing the access hatch or lid 16, 24, the pixel pet 300 is depicted in celebration, and the streak counter 412 is incremented to show a fourth consecutive successful use of the system 10. In some examples, the system 10 may display or provide graphical space on the screen 118 for a seven day streak or seven flame icons 413 to be displayed. Upon reaching a seven day streak, the system 10 may display a milestone reward, such as causing the pixel pet 300 to dance or otherwise engage in a specialized animation, gift, or other such reward.

[0115] Turning now to FIGS. 7A, 7B, 7C, 7D, and 7E and with continuing reference to FIGS. 1A-1C, 2A-2J, 3A-3E, 4A, 4B, 5 and 6, logical processes of the SRA 400 are shown in various aspects, in flowchart form. With particular reference toFIG. 7 A, an idle state management portion 500 of the SRA 400 is shown in additional detail. In several aspects, the idle state management portion 500 of the SRA 400 manages pixel pet 300 on-screen displayed behaviors. The pixel pet 300 is an animated creature that may take a variety of different forms without departing from the scope or intent of the present disclosure. In additional examples, the pixel pet 300 may be a pre-set, preselected, or otherwise predetermined animated creature or device that is not user selectable. In still further examples, the pixel pet 300 may be a user-defined or user-created animated device, or an Al-generated creature. The pixel pet 300 may be displayed in a variety of different states, including but not limited to: awake; asleep; waking up; falling asleep; mimicking storing the user’s mobile device 12 in the storage container 14; waving or pointing at a shutdown time to raise user attention; showing tired animations such as rubbing eyes, yawning and stretching; waking animations such as yawning, stretching, and getting out of bed; displaying affirmation such as thumbs-up gestures, clapping, raising or other such rewarding or joyous, positive gestures; mimicking opening the lid 24 or access hatch 16; sleeping animations such as snoring, zzz’s, or repositioning; grumpy animations; impatient animations such as tapping feet and / or crossing arms, and the like.

[0116] The idle state management portion 500 begins at block 502. At block 504, the SRA 400 determines whether a time update is required. Time updates may be initialized by user inputs, and / or by automatic wireless time-keeping inputs, such as wireless connections to time-servers, RF communications to atomic timekeeping facilities or mechanisms, or the like. Upon determining at block 504 that a time update is required, SRA 400 proceeds to block 506 where the SRA 400 causes the screen 118 to display an animation moving time settings and applying the necessary changes. Subsequently, the SRA 400 returns to block 502. Likewise, when at block504, the SRA 400 determines that a time update is not required, the SRA 400 proceeds back to block 502.

[0117] At block 508, the SRA 400 determines whether idle animations are being displayed on the screen 118. Upon determining that idle animations are being displayed, the SRA 400 proceeds to block 510. At block 510, the system 10 and SRA 400 may operate in one of at least two different manners: a manual interaction mode, or an automatic mode. In the manual interaction mode, the user is prompted to select one or more on-screen 118 options, including a leave screen animation 512, or a variety of pixel pet 300 animations including a stretching animation 514, a turn-around animation 516, a passing time animation 518, a prompt to play animation 520, or the like. In the automatic mode, the system 10 and SRA 400 automatically randomly selects one of the animations or cycles through each of the different animations. In some non-limiting examples, the system 10 and SRA 400 operate in the automatic mode when no user interaction is received after a predetermined quantity of time, or the like. Upon either automatic selection or user selection of one of the variety of pixel pet animations 300, the SRA 400 returns to block 502. By contrast, when the user selects the leave screen animation 512, the SRA 400 proceeds to block 522, where the screen 118 turns off. From block 522, the SRA 400 initiates a timer and determines at block 524 whether a user input has been received, and at block 526 whether any such user input has been received before a predefined quantity of time has passed. When a user input is received and / or the predefined quantity of time has passed, the SRA 400 combines the results of blocks 524 and 526 at block 528 and proceeds to block 530 where the SRA 400 causes the screen 118 to return to an animated state before proceeding once more to block 502. However, when no user input is received at block 524 and / or the predefined quantity of time has not passed, the SRA 400 maintains thescreen 118 in an off state unless and until the results of blocks 524 and 526 indicate otherwise, as described above.

[0118] At block 532, the SRA 400 determines whether the user is interacting with or otherwise playing with one or more of the HMIs 18 of the system 10. Upon determining that the user is not so interacting, the SRA 400 returns to block 502. Upon determining that the user is interacting with one or more of the HMIs 18 of the system 10, the SRA 400 proceeds to block 534 where the SRA 400 determines whether the interaction is positive. When the interaction is positive, the screen 118 displays the pixel pet 300 in a happy animated state at block 536, and increases a satisfaction level 538 of the user and / or an estimated satisfaction level 538 within the SRA 400. Positive interactions may take a variety of forms without departing from the scope or intent of the present disclosure. In some non-limiting examples, positive user interactions, such as “play” or “caring” may include: playing on-screen 118 games (e.g. ping pong, pong, or the like), touching or petting the pixel pet 300, feeding or watering the pixel pet 300, giving toys or gifts to the pixel pet 300 or other similar user / pixel pet 300 interactions. Positive interactions should generally be understood to mean interactions that reduce user screentime by gamification of behavior that makes the pixel pet 300 happy by use of the compartment 42 for user mobile device 12 storage. By contrast, at block 534 when the SRA 400 determines that the interaction is not positive, the SRA 400 proceeds to block 540 where the SRA 400 causes the screen 118 to display the pixel pet 300 in a sad, depressed, or otherwise negative animated state, and a decreased satisfaction level 542 is indicated. Interactions that are not positive may vary, but should generally be understood to be interactions with the system 10 that do not reduce user mobile device 12 screentime consumption and / or adherence to bedtime desired routines. Such non-positive interactions may include, but are notlimited to: opening the compartment 42 to access mobile devices 12 before the wakeup time 406 has been reached, or user failure to place mobile devices 12 within the compartment 42 and closing the access hatch 16 or lid 24 at or before the scheduled shutdown time 404. Results from blocks 538 and 542 are combined at block 544, after which the SRA 400 returns to block 502.

[0119] From block 502, the SRA 400 may also proceed to block 550, where the SRA 400 determines whether it is time for shutdown preparation to occur. Upon determining that it is not yet time for shutdown preparation to occur, the SRA 400 returns once more to block 502. However, upon determining that it is time for shutdown preparation to occur, the SRA 400 proceeds to block 552 where shutdown preparation is initiated. Shutdown preparation is initiated upon arriving at or approaching the shutdown time 404 selected by the user, or recommended by the system 10 and SRA 400.

[0120] Referring now more specifically to FIG. 7B, the shutdown preparation at block 552 of FIG. 7A is shown in additional detail in flowchart form.Shutdown preparation starts at block 554. At block 556, the SRA 400 automatically selects one of several distinct on-screen 118 pixel pet 300 animations. Specifically, the pixel pet 300 animations may include, at block 558, mimicking putting a mobile device 12 away or into the storage container 14; at block 560, waving or pointing to the shutdown time 404 display in an attempt to draw the user’s attention; and at block 562 displaying the pixel pet 300 in a tired state via animations of rubbing eyes, yawning, stretching, or the like. The pixel pet 300 animations at blocks 558, 560, and 562 may be randomly selected, may be Al-generated, may be user selected, and may be displayed alone or in any sequence without departing from the scope or intent of the present disclosure.

[0121] Once the pixel pet 300 animations at one or more of blocks 558, 560 and 562 have been displayed, the shutdown preparation portion of the SRA 400 proceeds to block 564 where the SRA 400 determines whether it is currently time for the shutdown process to occur. Upon determining at block 564 that it is not yet time for the shutdown process, the SRA 400 proceeds back to block 554, whereas when it is time for the shutdown process to occur, the SRA 400 proceeds to block 570.

[0122] Referring now to FIG. 7C, the shutdown process at block 570 of FIG.7B is shown in further detail in flowchart form.

[0123] The shutdown process begins at block 572. At block 574, the SRA 400 causes the system 10 to generate an audiovisual and / or tactile alarm to the user. At block 576, the SRA 400 causes the pixel pet 300 to be displayed pushing the access hatch 16 or lid 24 into the open position 30, and the access hatch 16 or lid 24 of the system 10 is opened. At block 578, daytime text or other daytime animations are removed or pushed off the screen 118, and at block 580, the SRA 400 waits for mobile devices 12 to be detected. In some examples, the SRA 400 may detect the presence of a mobile device 12 by a Hall effect sensor, or the like. While the SRA 400 waits for mobile devices 12 to be detected within the compartment 42, the pixel pet 300 is animated and displayed in an impatient mode, tapping feet, crossing arms, or the like. Upon determining at block 582 that a mobile device 12 has not been placed in the compartment 42, the SRA 400 returns to block 580. Upon determining at block 582 that a mobile device 12 has been placed in the compartment 42, the SRA 400 proceeds to block 584, increments the streak and provides an animation of the streak update. From block 584, the SRA 400 proceeds to block 586 where the screen 118 displays an animation of the access hatch 16 or lid 24 being closed, and at block 588, the SRA 400 waits for the access hatch 16 or lid 24 to be closed. At block 590, the system 10 andSRA 400 determines whether the access hatch 16 or lid 24 has been closed, and upon determining that the access hatch 16 or lid 24 is not closed, returns to block 588. However, when at block 590, the system 10 and SRA 400 determine that the access hatch 16 or lid 24 has been closed, the SRA 400 proceeds to block 592 where the alarm is stopped, after which, at block 594, the pixel pet 300 is animated getting ready to sleep (i.e. yawning, stretching, and / or moving to a bed). The SRA 400 subsequently proceeds to block 600 where a sleep idle state is entered.

[0124] Referring now to FIG. 7D the sleep idle state depicted at block 600 of FIG. 7C is shown in further detail in flowchart form.

[0125] In the sleep idle state, the pixel pet 300 is depicted on the screen 118 initially lying down or curled up in a sleeping state with a ZZZ animation, static ZZZ icon, or the like. Starting at block 602, the sleep idle state of the SRA 400 proceeds to block 604 where the system 10 and SRA 400 determine whether idle animations of the pixel pet 300 are indicated. Idle animations are indicated when the user’s mobile devices 12 are stored within the compartment 42, optionally charging, and with the access hatch or lid 16, 24 in the closed position 28 for a predetermined quantity of time. The predetermined quantity of time may vary from application to application, and from clock time to clock time without departing from the scope or intent of the present disclosure. In some examples, the predetermined quantity of time is determined experimentally, automatically, or manually, based on a variety of factors that may include data from additional sleep-tracking devices that may be paired with the system 10, scientific research regarding a quantity of time before a majority of people fall asleep after getting into bed, or the like. That is, the system 10 may be paired with wearable external sleep trackers for analytics and to provide customized gamification interventions and pixel pets 300. Upon determining at block 604 that the predeterminedquantity of time has not elapsed, the sleep idle state of the SRA 400 returns to block 602. However, when at block 604, the predetermined quantity of time has elapsed, the system 10 and SRA 400 proceed to block 606 where the SRA 400 causes the pixel pet 300 to be displayed with sleeping animations including but not limited to: snoring, animated or static ZZZs, and occasional twitches or repositioning. From block 606, the sleep idle state portion of the SRA 400 returns to block 602.

[0126] In some situations, the user may open the access hatch or lid 16, 24 to retrieve or manipulate the mobile device 12 stored within the compartment 42. In such situations, the sleep idle state portion of the SRA 400 proceeds from block 602 to block 608. At block 608, the system 10 and SRA 400 determine whether the access hatch or lid 16, 24 has been opened and / or whether the mobile device 12 stored in the compartment 42 has been removed. If no such activity has occurred, the system sleep idle state portion of the SRA 400 returns to block 602. However, when at block 608, the system 10 and SRA 400 determine that the access hatch or lid 16, 24 has been opened and / or the mobile device 12 has been removed from the compartment 42, the sleep idle state portion of the SRA 400 proceeds to block 610. At block 610, the SRA 400 causes the pixel pet 300 to be displayed in a wakened state with grumpy, disgruntled, or otherwise displeased appearance. From block 610, the SRA 400 proceeds to block 612 where the screen 118 displays an animation depicting the loss of the user’s active streak, via the streak counter 412, and the user’s active streak is then reset to zero. Subsequently, at block 614, the SRA 400 depicts an animation of the pixel pet 300 returning to sleep before returning to block 602.

[0127] As the clock time approaches the wakeup time 406, the sleep idle state portion of the SRA 400 proceeds to block 616, where the system 10 and SRA 400 determine whether it is currently time to initiate a wakeup process portion of the SRA400. Upon determining that it is not yet time to initiate the wakeup process portion of the SRA 400, the sleep idle state portion of the SRA 400 returns to block 602. However, when at block 616, the system 10 and SRA 400 determine that it is currently time to initialize the wakeup process portion, the SRA 400 proceeds to block 700 where the wakeup process begins.

[0128] Turning now more specifically to FIG. 7E, the wakeup process portion of the SRA 400 starting at block 700 in FIG. 7D is shown in additional detail in flowchart form.

[0129] The wakeup process portion of the SRA 400 begins at block 702. At block 704, the wakeup process portion of the SRA 400 causes the system 10 to activate the wakeup alarm, including audiovisual and / or haptic feedback to the user indicating that it is time to wake up. At block 706, the SRA 400 animates the pixel pet 300 to depict waking animations such as yawning, stretching, getting out of bed, or the like. At block 708, the SRA 400 depicts the pixel pet 300 pushing the access hatch 16 or lid 24 open, and the SRA 400 simultaneously activates the access hatch 16 or lid 24 into the open position 30. At block 710, the SRA 400 causes the screen 118 to display daytime text, and at block 712, the SRA 400 may depict an animation of a user retrieving a mobile device 12 from the compartment 42. At block 714, the system 10 and SRA 400 determine whether the user’s mobile device 12 was left alone and untouched overnight. Upon determining that the user’s mobile device 12 was untouched overnight, the SRA 400 proceeds to block 716 where the screen 118 displays a positive animation, such as a thumbs up, clapping, or other such rewarding animation. Such positive animations may be presented via pixel pet 300 animations and / or alternate animations on the screen 118. By contrast, when the system 10 and SRA 400 determine that the user’s mobile device 12 was not left alone and untouched overnight,the system 10 and SRA 400 proceed to block 718 where a disappointment animation is depicted on-screen 118. The disappointment animation may be presented via animations of the pixel pet 300 or other animations showing sadness, unhappiness, thumbs down, or the like. From either of block 716 or 718, the system 10 and SRA 400 proceed to block 720. Subsequently, at block 722, the system 10 and SRA 400 determine whether the user’s mobile device 12 has been removed from the compartment 42, since the compartment 42 is now in the open position 30. Upon determining that the mobile device 12 is still present in the compartment 42 (i.e. that the user has not removed the mobile device 12), the SRA 400 returns to block 720 where mobile device 12 monitoring continues. However, when at block 722, the SRA 400 determines that the mobile device 12 has been removed from the compartment 42, the SRA 400 proceeds to block 724 where the wakeup alarm is terminated. From block 724, the SRA 400 proceeds to block 726 where the SRA 400 presents an animation onscreen 118 depicting the access hatch 16 or lid 24 being closed, and the system 10 waits for the access hatch 16 or lid 24 to be closed. At block 726, the system 10 and SRA 400 determines whether the access hatch 16 or lid 24 has been closed. When the access hatch 16 or lid 24 has not been closed, the system 10 and SRA 400 return to block 724 where access hatch 16 or lid 24 position monitoring continues. Upon determining at block 726 that the access hatch 16 or lid 24 has been closed, the SRA 400 proceeds to block 728 where the idle state management portion 500 of the SRA 400 is re-entered.

[0130] In additional non-limiting examples, the system 10 may operate in a variety of different types of screen-free session modes, such as temporary modes that promote focus or productivity. Temporary modes, such as screen-free session modes for increasing productivity and focus may include a shutdown timer that is displayed on-screen 118, or via the mobile application 128. Such temporary modes are software-defined modes that initiate shorter temporary screen-free sessions that generate the HVSS signal for accountability but do not increment the unplug streak counter, as the session is not a full-night’s rest. Similarly, the system 10 may differentiate between a primary boundary action (a nightly goal that updates a streak), and a secondary boundary action (a productivity goal that does not update a streak). The SRA 400 includes pre-session reminder logic that checks if the DBA has been completed before a scheduled time. Upon determining that the DBA is pending, the SRA 400 triggers a soft notification such as changing an ambient lighting on a screen 118 or light source 109, or changing a quantity or color of light emitted via the light source 109 within the plushie 15 version of the system 10 depicted in FIG. 2 J. In several aspects, the plushie 15 may be utilized by parents of younger children to assist in establishing healthy bedtime routines for pre-cellphone users, serving as an early behavior intervention that seamlessly continues once a child’s favorite soft toy (plushie 15 ) is replaced by their personal mobile device 12. Such seamless intervention assists children in learning separation / unplugging routines even before mobile device 12 ownership.

[0131] Additionally, in the foregoing, the system 10 and storage container 14 have been described as having both pixel pet 300 and streak counter 412 displayed on the screen 118. However, it should be appreciated that variations where only one of the pixel pet 300 and streak counter 412 are displayed are intended to be within the scope of the present disclosure. That is, a user may determine that they wish only to see the pixel pet 300 on screen 118, or that only the streak counter 412 should be displayed while the passive “unplug” tracker is running in the background and may be visible or accessible via the mobile application 128.

[0132] A system 10 and method of mobile device 12 storage with screentime gamification of the present disclosure offers several advantages. Theseinclude: mobile device 12 storage with screentime gamification that increases user engagement from a first engagement level to a second engagement level greater than the first, positively reinforces user behavior, provide a means for storing and limiting access to mobile devices 12 to prioritize user sleep quality and quantity, providing behavior intervention for users that reduces screentime utilization from a first level to a second level lower than the first, and that encourages users to adopt healthier bedtime routines and lifestyles. Moreover, the system 10 offers a variety of distinct formfactors, utilizing substantially similar or identical componentry in each of the various form factors, thereby reducing system 10 component complexity and providing simplified, portable, and modular physical and logical construction.

[0133] The description of the present disclosure is merely exemplary in nature and variations that do not depart from the gist of the present disclosure are intended to be within the scope of the present disclosure. Such variations are not to be regarded as a departure from the spirit and scope of the present disclosure.

Claims

CLAIMSWhat is claimed is:

1. A system for mobile device storage with screentime and bedtime gamification, the system comprising:one or more storage containers adapted to receive one or more mobile devices, the one or more storage containers having an access hatch, and a compartment for receiving and at least partially containing the one or more mobile devices therein; one or more sensors detecting system user data;one or more human-machine interfaces (HMIs) providing a tactile interface for users to interact with the storage container;one or more controllers of the storage container in communication with the one or more mobile devices, the one or more sensors, and the one or more HMIs via input / output (I / O) ports of the controller, the one or more controllers further including a memory storing programmatic control logic, a processor that executes the programmatic control logic, the programmatic control logic including at least a screentime reduction application (SRA), wherein the SRA comprises:a first control logic for recognizing a digital boundary action (DBA) performed by a system user;a second control logic for, upon recognition of the DBA, initiating a communications handshake between the storage container and the one or more mobile devices upon receipt of the one or more mobile devices by the one or more storage containers;a third control logic for secure, non-spoofable electronic validation of a connection between the one or more mobile devices and the one or more storage containers;a fourth control logic for launching a mobile application stored or accessed at least partially within memory of the one or more mobile devices; anda fifth control logic that causes the system to access the one or more HMIs, including one or more screens or light sources, and depict system-state graphics comprising: a shutdown tracker, a streak tracker, screen-free user performance, a pixel pet, and a dynamically adjusted state of the pixel pet,wherein the SRA increases user engagement with the system, positively reinforces user behavior by reducing screentime utilization, provides storage for the one or more mobile devices, limits access to and prevents overstimulation from the one or more mobile devices, and supports healthy bedtime routines by prioritizing user sleep quality and quantity.

2. The system of claim 1 , wherein the one or more sensors comprise:sensors for detecting user inputs to the system, including one or more of: haptic sensors, piezoresistive sensors, piezoelectric sensors, optical sensors, capacitive sensors, and elastoresistive sensors; andsensors for detecting user motions including one or more of: optical sensors, cameras, infrared sensors, and motion tracking sensors.

3. The system of claim 1 , wherein the one or more HMIs further comprise:at least one screen and a knob, wherein the screen and knob communicate user inputs to the controller, wherein the screen displays a variety of information, including:clock time, alarm clock time, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity, suggestions to improve sleep, and the pixel pet.

4. The system of claim 1, wherein the compartment is selectively lockable via a latch mechanism,wherein the latch mechanism comprises one or more of: a flush fitting latch, an under center latch, a spring-loaded latch, a rigid claw, a flexible fastener, a slide bolt latch, a sprung safety latch, a sprung slide bolt latch, a tight hold draw latch, a magnetic push latch, and a touch latch;wherein the latch mechanism further comprises:a latch receiver with a movable portion slidably or rotatably retained within a latch housing, andwherein the movable portion includes one or more hinged jaws, the one or more hinged jaws rotatably connected via hinges to a spring-loaded sliding assembly within the latch housing, the one or more hinged jaws sized and shaped to receive and selectively retain the latch.

5. The system of claim 1, wherein the storage container includes electromagnetic field (EMF) shielding or blocking materials that prevent wireless communications from reaching into or being transmitted from within the compartment to outside the compartment when the one or more mobile devices are stored within the compartment and the access hatch is closed.

6. The system of claim 5, wherein the DBA comprises:physical placement of a mobile device within or entry of the mobile device into a docking arrangement with the storage container, or compliance with a context-aware schedule, such as docking the mobile device or storing the mobile device within the storage container after a bedtime alarm; and wherein the SRA includes a limited local network between the one or more mobile devices and the storage container, wherein the limited local network provides for electronic communication between the storage container and the one or more mobile devices when the one or more mobile devices are stored within the compartment and the access hatch is closed.

7. The system of claim 1 , wherein the SRA further comprises:a sixth control logic defining a gamification engine, wherein the gamification engine includes logic for incrementing a shutdown streak, granting rewards, and requiring real-time authentication of a hardware validated session start (HVSS) signal before any reward logic may be executed, and displaying a shutdown screen a passive shutdown tracker and / or an active pixel pet animation, wherein the pixel pet comprises an on-screen, gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar or an animated device selected by the user from a predetermined group of pixel pets stored in the memory with which the user may interact; andwherein a current state of a pixel pet is determined by a state machine whose primary inputs are an unplug streak counter and total screen-free minutes obtained from the shutdown tracker,wherein modular digital assets associated with the pixel pet comprise: skins, accessories, and evolutions that are associated with a user profile based on achieving specific HVSS validated milestones.

8. The system of claim 7, further comprising:control logic for displaying a current state of the pixel pet based on user inputs to the system, wherein user inputs are classified as positive or non-positive, wherein positive user inputs are interactions that reduce user screentime from a first level to a second level lower than the first, by gamification of behavior that makes the pixel pet happy, wherein positive user inputs comprise: play or caring, touching or petting the pixel pet, feeding or watering the pixel pet, giving toys or gifts to the pixel pet, and wherein positive user inputs cause the pixel pet to be displayed in a happy animated state; andwherein non-positive user inputs are interactions that do not reduce user mobile device screentime consumption or adherence to desired bedtime routines, wherein non-positive interactions comprise: opening the compartment to access the one or more mobile devices before a wakeup time has been reached, or failure to place mobile devices within the compartment and closing the access hatch at or before a scheduled shutdown time, and wherein the non-positive user inputs cause the pixel pet to be displayed in a sad, depressed, or otherwise negative animated state.

9. The system of claim 8, wherein the SRA includes a seventh control logic, comprising:control logic for preparing for shutdown by automatically selecting and displaying on the one or more HMIs, one of several pixel pet animations including: the pixel pet mimicking putting a mobile device into the storage container, waving or pointing to a shutdown time display, displaying the pixel pet in a tired state with animations of rubbing eyes, yawning, and / or stretching;control logic for generating an audiovisual and / or tactile alarm to the user indicating that the shutdown time has been reached and displaying a pixel pet animation in an impatient mode, tapping feet, or crossing arms until the one or more mobile devices are detected within the storage container by the one or more sensors; and control logic for, upon determining that the one or more mobile devices have been placed within the storage container and the access hatch has been closed, incrementing the shutdown streak and generating and displaying an on-screen depiction of the incrementing of the shutdown streak;control logic for selecting and displaying, on the one or more HMIs, an animation of the pixel pet getting ready to sleep; andcontrol logic for causing system to enter a sleep idle state wherein the pixel pet is displayed on the one or more HMIs in a sleeping state with a ZZZ animation, or a ZZZ icon, wherein the sleep idle state is indicated when the user’s mobile devices are stored within the compartment and the access hatch is closed for predetermined quantity of time.

10. The system of claim 9, wherein the SRA includes an eighth control logic comprising:control logic for determining when a user accesses the one or more mobile devices while the sleep idle state is engaged, and upon determining that the one or more mobile devices have been removed from the storage container, displaying the pixel pet on the one or more HMIs in a wakened state with grumpy, disgruntled, or otherwise displeased appearance; andcontrol logic for depicting, via the one or more HMIs, a loss of an active shutdown streak, and resetting a shutdown streak counter to zero.

11. A method for mobile device storage with screentime and bedtime gamification, the method comprising:receiving one or more mobile devices within one or more storage containers, the one or more storage containers having an access hatch, and a compartment for receiving and at least partially containing the one or more mobile devices therein; detecting system user data with one or more sensors;providing a tactile interface via one or more human-machine interfaces (HMIs) for users to interact with the storage container;executing, via processors of one or more controllers, programmatic control logic stored within memory of one or more controllers, the one or more controllers further including one or more input / output (I / O) ports in communication with the one or more mobile devices, the one or more sensors, and the one or more HMIs, the programmatic control logic including at least a screentime reduction application (SRA) comprising control logic for:recognizing a digital boundary action (DBA) performed by a user;upon recognition of the DBA, initiating a communications handshake between the storage container and the one or more mobile devices upon receipt of the one or more mobile devices by the one or more storage containers;generating secure, non-spoofable electronic validation of a connection between the one or more mobile devices and the one or more storage containers;launching a mobile application stored or accessed at least partially within memory of the one or more mobile devices; andaccessing the one or more HMIs, including one or more screens or light sources, and depicting system-state graphics comprising: a shutdown tracker, a streak tracker,screen-free user performance, a pixel pet, and a dynamically adjusted state of the pixel pet; andincreasing user engagement with the one or more storage containers from a first level to a second level greater than the first, positively reinforcing user behavior by reducing screentime utilization, providing storage for the one or more mobile devices, limiting access to and preventing overstimulation from the one or more mobile devices, and supporting healthy bedtime routines by prioritizing user sleep quality and quantity.

12. The method of claim 11, further comprising:detecting user inputs via one or more of: haptic sensors, piezoresistive sensors, piezoelectric sensors, optical sensors, capacitive sensors, and elastoresistive sensors; anddetecting user motions via one or more of: optical sensors, cameras, infrared sensors, and motion tracking sensors.

13. The method of claim 11, further comprising:communicating user inputs to the controller via at least one screen and a knob, wherein the screen displays a variety of information, including:clock time, alarm clock time, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity, suggestions to improve sleep, and the pixel pet.

14. The method of claim 11 , further comprising:selectively locking the compartment via a latch mechanism,wherein the latch mechanism comprises one or more of: a flush fitting latch, an under center latch, a spring-loaded latch, a rigid claw, a flexible fastener, a slide bolt latch, a sprung safety latch, a sprung slide bolt latch, a tight hold draw latch, a magnetic push latch, and a touch latch;wherein the latch mechanism further comprises:a latch receiver with a movable portion slidably or rotatably retained within a latch housing, andwherein the movable portion includes one or more hinged jaws, the one or more hinged jaws rotatably connected via hinges to a spring-loaded sliding assembly within the latch housing, the one or more hinged jaws sized and shaped to receive and selectively retain the latch.

15. The method of claim 11 , further comprising:preventing, via electromagnetic field (EMF) shielding or blocking materials, wireless communications from reaching into or being transmitted from within the compartment to outside the compartment when the one or more mobile devices are stored within the compartment and the access hatch is closed.

16. The method of claim 15, wherein the DBA comprises:physically placing a mobile device within or entry of the mobile device into a docking arrangement with the storage container, or complying with a context-aware schedule, such as docking the mobile device or storing the mobile device within the storage container after a bedtime alarm; andestablishing a limited local network between the one or more mobile devices and the storage container, wherein the limited local network provides for electroniccommunication between the storage container and the one or more mobile devices when the one or more mobile devices are stored within the compartment and the access hatch is closed.

17. The method of claim 11 , further comprising:defining a gamification engine, wherein the gamification engine includes logic for incrementing a shutdown streak, granting rewards, and requiring real-time authentication of a hardware validated session start (HVSS) signal before any reward logic may be executed;displaying a shutdown screen a passive shutdown tracker and / or an active pixel pet animation, wherein the pixel pet comprises an on-screen, gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar or an animated device selected by the user from a predetermined group of pixel pets stored in the memory with which the user may interact; andwherein a current state of a pixel pet is determined by a state machine whose primary inputs are an unplug streak counter and total screen-free minutes obtained from the shutdown tracker, andwherein modular digital assets associated with the pixel pet comprise: skins, accessories, and evolutions that are associated with a user profile based on achieving specific HVSS validated milestones.

18. The method of claim 17, further comprising:displaying the current state of the pixel pet based on user inputs, wherein user inputs are classified as positive or non-positive,wherein positive user inputs are interactions that reduce user screentime from a first level to a second level lower than the first, by gamification of behavior that makes the pixel pet happy, wherein positive user inputs comprise: play or caring, touching or petting the pixel pet, feeding or watering the pixel pet, giving toys or gifts to the pixel pet, and wherein positive user inputs cause the pixel pet to be displayed in a happy animated state; andwherein non-positive user inputs are interactions that do not reduce user mobile device screentime consumption or adherence to desired bedtime routines, wherein nonpositive interactions comprise: opening the compartment to access the one or more mobile devices before a wakeup time has been reached, or failure to place mobile devices within the compartment and closing the access hatch at or before a scheduled shutdown time, and wherein the non-positive user inputs cause the pixel pet to be displayed in a sad, depressed, or otherwise negative animated state.

19. The method of claim 18, further comprising:preparing for shutdown by automatically selecting and displaying, on the one or more HMIs, one of several pixel pet animations including: the pixel pet mimicking putting a mobile device into the storage container, waving or pointing to a shutdown time display, displaying the pixel pet in a tired state with animations of rubbing eyes, yawning, and / or stretching;generating an audiovisual and / or tactile alarm to the user indicating that the shutdown time has been reached and displaying a pixel pet animation in an impatient mode, tapping feet, or crossing arms until the one or more mobile devices are detected within the storage container by the one or more sensors; andupon determining that the one or more mobile devices have been placed within the storage container and the access hatch has been closed, incrementing the shutdown streak and generating and displaying an on-screen depiction of the incrementing of the shutdown streak;selecting and displaying on the one or more HMIs, an animation of the pixel pet getting ready to sleep;entering a sleep idle state wherein the pixel pet is displayed on the one or more HMIs in a sleeping state with a ZZZ animation, or a ZZZ icon, wherein the sleep idle state is indicated when the user’s mobile devices are stored within the compartment and the access hatch is closed for predetermined quantity of time;determining when a user accesses the one or more mobile devices while the sleep idle state is engaged, and upon determining that the one or more mobile devices have been removed from the storage container, displaying the pixel pet on the one or more HMIs in a wakened state with grumpy, disgruntled, or otherwise displeased appearance; andcontrol logic for depicting, via the one or more HMIs, a loss of an active shutdown streak, and resetting a shutdown streak counter to zero.

20. A system for mobile device storage with screentime and bedtime gamification, the system comprising:one or more storage containers adapted to receive one or more mobile devices, the one or more storage containers having an access hatch, and a compartment for receiving and at least partially containing the one or more mobile devices therein, wherein the compartment is selectively lockable via a latch mechanism, wherein the storage container includes electromagnetic field (EMF) shielding or blocking materialsthat prevent wireless communications from reaching into or being transmitted from within the compartment to outside the compartment when the one or more mobile devices are stored within the compartment and the access hatch is closed; wherein the latch mechanism comprises one or more of: a flush fitting latch, an under center latch, a spring-loaded latch, a rigid claw, a flexible fastener, a slide bolt latch, a sprung safety latch, a sprung slide bolt latch, a tight hold draw latch, a magnetic push latch, and a touch latch;wherein the latch mechanism further comprises:a latch receiver with a movable portion slidably or rotatably retained within a latch housing, wherein the movable portion includes one or more hinged jaws, the one or more hinged jaws rotatably connected via hinges to a spring-loaded sliding assembly within the latch housing, the one or more hinged jaws sized and shaped to receive and selectively retain the latch;one or more sensors detecting system user inputs to the system, including one or more of: haptic sensors, piezoresistive sensors, piezoelectric sensors, optical sensors, capacitive sensors, and elastoresistive sensors;sensors for detecting user motions including one or more of: optical sensors, cameras, infrared sensors, and motion tracking sensors;one or more human-machine interfaces (HMIs) providing a tactile interface for users to interact with the storage container, at least one screen and a knob, wherein the screen and knob communicate user inputs to one or more controllers, wherein the screen displays a variety of information, including: clock time, alarm clock time, user ideal sleep schedule information, suggestions to increase user wellbeing and productivity, suggestions to improve sleep, and a pixel pet;wherein the one or more controllers of the storage container are in communication with the one or more mobile devices, the one or more sensors, and the one or more HMIs via input / output (I / O) ports of the one or more controllers, the one or more controllers further including a memory storing programmatic control logic, a processor that executes the programmatic control logic, the programmatic control logic including at least a screentime reduction application (SRA), wherein the SRA comprises:a first control logic for recognizing a digital boundary action (DBA) performed by a system user, wherein the DBA comprises:physical placement of a mobile device within or entry of the mobile device into a docking arrangement with the storage container, or compliance with a context-aware schedule, such as docking the mobile device or storing the mobile device within the storage container after a bedtime alarm; and wherein the SRA includes a limited local network between the one or more mobile devices and the storage container, wherein the limited local network provides for electronic communication between the storage container and the one or more mobile devices when the one or more mobile devices are stored within the compartment and the access hatch is closed;a second control logic for, upon recognition of the DBA, initiating a communications handshake between the storage container and the one or more mobile devices upon receipt of the one or more mobile devices by the one or more storage containers;a third control logic for secure, non-spoofable electronic validation of a connection between the one or more mobile devices and the one or more storage containers;a fourth control logic for launching a mobile application stored or accessed at least partially within memory of the one or more mobile devices; anda fifth control logic that causes the system to access the one or more HMIs, including one or more screens or light sources, and depict system-state graphics comprising: a shutdown tracker, a streak tracker, screen-free user performance, the pixel pet, and a dynamically adjusted state of the pixel pet;a sixth control logic defining a gamification engine, wherein the gamification engine includes logic for incrementing a shutdown streak, granting rewards, and requiring real-time authentication of a hardware validated session start (HVSS) signal before any reward logic may be executed, and displaying a shutdown screen a passive shutdown tracker and / or an active pixel pet animation, wherein the pixel pet comprises an on-screen, gamified, graphical representation of a pet, a plant, an animal, a child, a mythical creature, a pet rock, a cloud, a robot, a fantasy creature, an avatar or an animated device selected by the user from a predetermined group of pixel pets stored in the memory with which the user may interact, wherein a current state of a pixel pet is determined by a state machine whose primary inputs are an unplug streak counter and total screen-free minutes obtained from the shutdown tracker, wherein modular digital assets associated with the pixel pet comprise: skins, accessories, and evolutions that are associated with a user profile based on achieving specific HVSS validated milestones;control logic for displaying a current state of the pixel pet based on user inputs to the system, wherein user inputs are classified as positive or non-positive, wherein positive user inputs are interactions that reduce user screentime from a first level to a second level lower than the first, by gamification of behavior that makes the pixel pet happy, wherein positive user inputs comprise: play or caring, touching orpetting the pixel pet, feeding or watering the pixel pet, giving toys or gifts to the pixel pet, and wherein positive user inputs cause the pixel pet to be displayed in a happy animated state;wherein non-positive user inputs are interactions that do not reduce user mobile device screentime consumption or adherence to desired bedtime routines, wherein nonpositive interactions comprise: opening the compartment to access the one or more mobile devices before a wakeup time has been reached, or failure to place mobile devices within the compartment and closing the access hatch at or before a scheduled shutdown time, and wherein the non-positive user inputs cause the pixel pet to be displayed in a sad, depressed, or otherwise negative animated state;a seventh control logic for preparing for shutdown by automatically selecting and displaying on the one or more HMIs, one of several pixel pet animations including: the pixel pet mimicking putting a mobile device into the storage container, waving or pointing to a shutdown time display, displaying the pixel pet in a tired state with animations of rubbing eyes, yawning, and / or stretching, wherein the seventh control logic further includes:control logic for generating an audiovisual and / or tactile alarm to the user indicating that the shutdown time has been reached and displaying a pixel pet animation in an impatient mode, tapping feet, or crossing arms until the one or more mobile devices are detected within the storage container by the one or more sensors;control logic for, upon determining that the one or more mobile devices have been placed within the storage container and the access hatch has been closed, incrementing the shutdown streak and generating and displaying an on-screen depiction of the incrementing of the shutdown streak;control logic for selecting and displaying, on the one or more HMIs, an animation of the pixel pet getting ready to sleep;control logic for causing system to enter a sleep idle state wherein the pixel pet is displayed on the one or more HMIs in a sleeping state with a ZZZ animation, or a ZZZ icon, wherein the sleep idle state is indicated when the user’s mobile devices are stored within the compartment and the access hatch is closed for predetermined quantity of time;an eighth control logic for determining when a user accesses the one or more mobile devices while the sleep idle state is engaged, and upon determining that the one or more mobile devices have been removed from the storage container, displaying the pixel pet on the one or more HMIs in a wakened state with grumpy, disgruntled, or otherwise displeased appearance;control logic for depicting, via the one or more HMIs, a loss of an active shutdown streak, and resetting a shutdown streak counter to zero; andwherein the SRA increases user engagement with the system, positively reinforces user behavior by reducing screentime utilization, provides storage for the one or more mobile devices, limits access to and prevents overstimulation from the one or more mobile devices, and supports healthy bedtime routines by prioritizing user sleep quality and quantity.

Images