Patent classifications
H04M1/72463
Data processing method and terminal device
A data processing method and a terminal device, where the method includes obtaining a speed of the terminal device, receiving a first communications service, disabling a preset reminder of the first communications service when the speed of the terminal device exceeds a first preset value, and enabling the preset reminder of the first communications service when the speed of the terminal device decreases to a second preset value, where the second preset value is less than or equal to the first preset value. The data processing method and the terminal device are used for a user reminder of a terminal device in a vehicle mode.
Data processing method and terminal device
A data processing method and a terminal device, where the method includes obtaining a speed of the terminal device, receiving a first communications service, disabling a preset reminder of the first communications service when the speed of the terminal device exceeds a first preset value, and enabling the preset reminder of the first communications service when the speed of the terminal device decreases to a second preset value, where the second preset value is less than or equal to the first preset value. The data processing method and the terminal device are used for a user reminder of a terminal device in a vehicle mode.
METHOD AND SYSTEM FOR PROVIDING TRAVEL TIME INFORMATION
Location technologies are combined with other information systems to provide augmented information for individuals such as a traveler in an automobile.
Device deactivation based on behavior patterns
Embodiments are described for a pattern-based control system that learns and applies device usage patterns for identifying and disabling devices exhibiting abnormal usage patterns. The system can learn a user's normal usage pattern or can learn abnormal usage patterns, such as a typical usage pattern for a stolen device. This learning can include human or algorithmic identification of particular sets of usage conditions (e.g., locations, changes in settings, personal data access events, application events, IMU data, etc.) or training a machine learning model to identify usage condition combinations or sequences. Constraints (e.g., particular times or locations) can specify circumstances where abnormal pattern matching is enabled or disabled. Upon identifying an abnormal usage pattern, the system can disable the device, e.g., by permanently destroying a physical component, semi-permanently disabling a component, or through a software lock or data encryption.
Device deactivation based on behavior patterns
Embodiments are described for a pattern-based control system that learns and applies device usage patterns for identifying and disabling devices exhibiting abnormal usage patterns. The system can learn a user's normal usage pattern or can learn abnormal usage patterns, such as a typical usage pattern for a stolen device. This learning can include human or algorithmic identification of particular sets of usage conditions (e.g., locations, changes in settings, personal data access events, application events, IMU data, etc.) or training a machine learning model to identify usage condition combinations or sequences. Constraints (e.g., particular times or locations) can specify circumstances where abnormal pattern matching is enabled or disabled. Upon identifying an abnormal usage pattern, the system can disable the device, e.g., by permanently destroying a physical component, semi-permanently disabling a component, or through a software lock or data encryption.
SYNCHRONIZATION OF NOTIFICATION ACTIONS ACROSS MULTIPLE ENROLLED DEVICES
Disclosed herein are examples of systems and methods for synchronizing notification actions across multiple enrolled devices. A management service can receive from a first client device metadata associated with a notification posted on the first client device. The management service can receive from the first client device an indication of an action performed with respect to the notification. The management service can determine whether to propagate a new notification state to a second client device based at least in part on a type of the action and a current notification state associated with the second client device. In response to determining to propagate the new notification state to the second client device, the management service can provide to the second client device a command to change the current notification state to the new notification state.
SYNCHRONIZATION OF NOTIFICATION ACTIONS ACROSS MULTIPLE ENROLLED DEVICES
Disclosed herein are examples of systems and methods for synchronizing notification actions across multiple enrolled devices. A management service can receive from a first client device metadata associated with a notification posted on the first client device. The management service can receive from the first client device an indication of an action performed with respect to the notification. The management service can determine whether to propagate a new notification state to a second client device based at least in part on a type of the action and a current notification state associated with the second client device. In response to determining to propagate the new notification state to the second client device, the management service can provide to the second client device a command to change the current notification state to the new notification state.
TAILORING NOTIFICATION POSTING BASED ON DEVICE ACTIVITY STATUS
Disclosed herein are examples of systems and methods for tailoring the posting of notifications based on device activity status. A client device can collect activity data associated with the client device. The client device can provide the activity data to a management service. The client device can receive from the management service a command to disable a capability of an application installed on the client device to post notifications. The client device can cause the capability of the application to post notifications to be disabled.
TAILORING NOTIFICATION POSTING BASED ON DEVICE ACTIVITY STATUS
Disclosed herein are examples of systems and methods for tailoring the posting of notifications based on device activity status. A client device can collect activity data associated with the client device. The client device can provide the activity data to a management service. The client device can receive from the management service a command to disable a capability of an application installed on the client device to post notifications. The client device can cause the capability of the application to post notifications to be disabled.
Device, system, and process for unlocking a wireless device
A wireless device configured to temporarily unlock includes a processor configured to execute an unlocking application and a lock mechanism. The processor implementing the unlocking application to control the lock mechanism to unlock based on one of the following: the location provided by a location determination device or based on a time and date provided from the transceiver and/or the processor. A process to temporarily unlock a wireless device is also disclosed.