Managing grouped student devices with timed locks
First Claim
1. A system comprising:
- at least one processor; and
at least one non-transitory computer-readable medium including instructions, which when executed by the at least one processor, cause the at least one processor to perform stages including;
executing a calendar application for scheduling future events;
receiving, at the calendar application, a lock request to schedule a lock to be applied to at least one user device, the lock request including at least one user identifier identifying the at least one user device, an asset identifier, and timing information, the lock request identifying a function of the at least one user device to disable while the at least one user device is locked into an asset associated with the asset identifier; and
transmitting the lock request to a management server causing the at least one user device to be locked into the asset associated with the asset identifier for a duration, the duration being based, at least in part, on the timing information.
3 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods presented here can allow a teacher to schedule the locking of one or more student devices into an asset at some time in the future. A teacher device can be used to configure lock information, including student identifying information, lock type information, asset information, and lock timing information. The lock information can be transmitted to the student devices for local storage. The lock can then initiate on the student device at the scheduled time even in instances when the student device is not connected to a communication network. After lock expiration, an updated asset can be stored at the student device in conjunction with lock confirmation information. When the student device detects a network connection, the updated asset and the lock confirmation information can be transmitted to a management server where it can be accessed and evaluated by the teacher.
-
Citations
20 Claims
-
1. A system comprising:
-
at least one processor; and at least one non-transitory computer-readable medium including instructions, which when executed by the at least one processor, cause the at least one processor to perform stages including; executing a calendar application for scheduling future events; receiving, at the calendar application, a lock request to schedule a lock to be applied to at least one user device, the lock request including at least one user identifier identifying the at least one user device, an asset identifier, and timing information, the lock request identifying a function of the at least one user device to disable while the at least one user device is locked into an asset associated with the asset identifier; and transmitting the lock request to a management server causing the at least one user device to be locked into the asset associated with the asset identifier for a duration, the duration being based, at least in part, on the timing information. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A non-transitory, computer-readable medium including instructions, the instructions causing a processor to execute stages including:
-
receiving lock information including at least one user identifier associated with at least one user device, an asset identifier, and timing information, the lock information identifying a function of the at least one user device to disable while the at least one user device is locked into an asset associated with the asset identifier; displaying, within a calendar, a scheduled lock indicia, the scheduled lock indicia appearing in the calendar at a time period corresponding with the timing information; and transmitting at least a portion of the lock information to a management server causing the at least one user device to be locked into the asset corresponding to the asset identifier for a duration, the duration being based, at least in part, on the timing information. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A method comprising:
-
receiving lock information including at least one user identifier associated with at least one user device, an asset identifier, and timing information, the lock information identifying a function of the at least one user device to disable while the at least one user device is locked into an asset associated with the asset identifier; displaying, within a calendar, a scheduled lock indicia, the scheduled lock indicia appearing in the calendar at a time period corresponding with the timing information; transmitting at least a portion of the lock information to a management server causing the at least one user device to store the lock information locally; and causing the at least one user device to be locked into the asset associated with the asset identifier for a period of time based, at least in part, on the timing information. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification