US 8,874,162 B2Grant
Mobile device safe driving
Issue Date:2014-10-28
•20 Claims
•18 Drawing Sheets
Abstract
In embodiments of mobile device safe driving, a mobile device can display a device lock screen on an integrated display device, and transition from the device lock screen to display a driving mode lock screen. The transition to display the driving mode lock screen occurs without receiving a PIN code entered on the device lock screen. The mobile device implements a safe driving service that is implemented to activate a safe driving mode of the mobile device, and disable features of the mobile device while the safe driving mode is activated.
Metadata
Assignee
- Microsoft Corporation
Inventors
- Joseph A. Schrader
- Raman K. Sarin
- Ted Tai-Yu Chen
- Sharad Agarwal
- Joseph H. Matthews, III
- Shai Guday
- Joseph Spencer King
Application Information
Application Number:US 13/726,097
Filing Date:2012-12-22
Priority Date:2011-12-23
Art Unit:2642
Classifications
IPC:
H04M1/00H04W4/04
Field of Search:
H04M 1/72519H04M 1/6091H04W 8/245G01P 1/11
Patent Drawings (18 sheets)
Description
Related Applications
[0001] This application claims priority under 35 U.S.C. Section 119(e) to U.S. Provisional Application Ser. No. 61/580,131 filed Dec. 23, 2011 entitled “Mobile Device Safe Driving”, the disclosure of which is incorporated by reference herein in its entirety. This application also claims priority under 35 U.S.C. Section 119(e) to U.S. Provisional Application Ser. No. 61/695,294 filed Aug. 30, 2012 entitled “Mobile Device Kid Space”, the disclosure of which is incorporated by reference herein in its entirety.
Background
[0002] Many types of devices, such as mobile phones, tablet devices, and other computing, communication, and entertainment devices increasingly offer more functions, applications, and features which are beneficial to a user, and can enhance one's personal time as well as work and social activities. For example, not only can a mobile phone be used for text, email, and voice communications, but may also be used for entertainment, such as to listen to music, surf the Internet, watch video content, gaming, and for photo and video imaging. Similarly, a portable tablet device may be utilized for email, browser, navigation, and other computing applications, as well as for the various entertainment and photo features. A significant trend and increasing problem with these always-connected mobile devices is distracted driving. Many drivers, and particularly teenage drivers, are tempted to send a quick text, make a call, or check a voice message while driving, which may lead to an accident.
Summary
[0003] This Summary introduces features and simplified concepts of mobile device safe driving, which is further described below in the Detailed Description and/or shown in the Figures. This Summary should not be considered to describe essential features of the claimed subject matter, nor used to determine or limit the scope of the claimed subject matter.
[0004] Mobile device safe driving is described. In embodiments, a mobile device can display a device lock screen on an integrated display device, and transition from the device lock screen to display a driving mode lock screen. The transition to display the driving mode lock screen is without receiving a PIN code or other authentication credential entered on the device lock screen. The mobile device implements a safe driving service that is implemented to activate a safe driving mode of the mobile device, which disables features of the mobile device while the safe driving mode is activated.
[0005] In embodiments, the safe driving service is implemented to register safe driving events and unsafe driving events associated with use of the mobile device by a user of the mobile device driving. The safe driving service is configured to aggregate the safe driving events and generate a safe driving report that indicates safe driving and/or unsafe driving. The safe driving service can also communicate the safe driving report to an associated device of the mobile device. The safe driving report can indicate that the features of the mobile device were enabled by user override of a safe driving mode while the mobile device was moving in a vehicle.
[0006] In embodiments, the mobile device includes a communication interface for notification communication with associated devices of the device. The safe driving service can initiate communication of an unsafe driving notification to the associated devices. The device that is moving in the vehicle may include an audio sensor to detect audio in the vehicle, and the safe driving service can generate an unsafe driving notification to indicate that the audio in the vehicle is a driver distraction. The safe driving service can also generate an unsafe driving notification to indicate that the features of the device have been enabled by user override of a safe driving mode while the device is moving in the vehicle and the user of the device is driving the vehicle. The driver of a vehicle may be identified with a vehicle camera, or vehicle sensors, such as to detect voice ID, other biometric ID (e.g., a fingerprint reader integrated into the steering wheel), and/or other types of sensors within the vehicle that report back to the device to indicate that the user of the device is driving the vehicle. Other types of sensors may include seat sensors, and heat and/or contact sensors integrated into the steering wheel of a vehicle.
[0007] The safe driving service can also be implemented to determine that vehicle motion is erratic based on the motion data, and then generate an unsafe driving notification to indicate to users of the associated devices that the vehicle motion is erratic. The safe driving service is also implemented to determine that at least one of the associated devices is proximate the device in the vehicle, and determine that the associated device corresponds to an adult user. The safe driving service can then enable the features of the device when the associated device is proximate the device in the vehicle and corresponds to the adult user.
[0008] The safe driving service is also implemented to receive speed limit data that corresponds to a location of the vehicle, and communicate a vehicle speed limit to the vehicle to control vehicle speed at the location of the vehicle. The safe driving service is also implemented to determine that the vehicle has stopped at an unknown location and determine the location of the vehicle from the location data. The safe driving service can then generate an unsafe driving notification to indicate that the vehicle has stopped at the unknown location.
[0009] In other embodiments, a safe driving system includes a network service (e.g., a network of one or more server devices) that executes computer instructions as a safe driving service. The safe driving service is implemented to receive an unsafe driving notification from a device that is moving in a vehicle when a user of the device is driving the vehicle. The safe driving notification may indicate a driving condition. The safe driving service can then determine associated devices of the device based on identifiers of the device and the associated devices, and communicate the safe driving notification received from the device to the associated devices. The safe driving service can also receive a vehicle notification from the vehicle and communicate the vehicle notification to the associated devices. The safe driving service can also be implemented to receive location data that indicates a location of the vehicle, receive speed limit data that corresponds to the location of the vehicle, and communicate a vehicle speed limit to the vehicle to control vehicle speed at the location of the vehicle.
Brief Description of the Drawings
[0010] Embodiments of mobile device safe driving are described with reference to the following Figures. The same numbers may be used throughout to reference like features and components that are shown in the Figures:
[0011] FIG. 1 illustrates an example of mobile device safe driving in accordance with one or more embodiments.
[0012] FIG. 2 illustrates examples of safe driving mode in accordance with one or more embodiments.
[0013] FIG. 3 illustrates an example system in which embodiments of mobile device safe driving can be implemented.
[0014] FIG. 4 illustrates example method(s) of mobile device safe driving in accordance with one or more embodiments.
[0015] FIG. 5 illustrates example method(s) of mobile device safe driving in accordance with one or more embodiments.
[0016] FIG. 6 illustrates an example system in which embodiments of mobile device safe driving can be implemented.
[0017] FIG. 7 illustrates example method(s) of mobile device safe driving.
[0018] FIG. 8 illustrates an example of restricted execution modes.
[0019] FIG. 9 illustrates an example system in which embodiments of restricted execution modes can be implemented.
[0020] FIG. 10 illustrates example method(s) of restricted execution modes in accordance with one or more embodiments.
[0021] FIG. 11 illustrates example method(s) of restricted execution modes in accordance with one or more embodiments.
[0022] FIG. 12 illustrates example method(s) of restricted execution modes in accordance with one or more embodiments.
[0023] FIG. 13 illustrates an example system in which embodiments of private interaction hubs can be implemented.
[0024] FIG. 14 illustrates an example system in which embodiments of mobile device safe driving can be implemented.
[0025] FIG. 15 illustrates various client device services and features in accordance with one or more embodiments.
[0026] FIG. 16 illustrates examples of a family hub in accordance with one or more embodiments.
[0027] FIG. 17 illustrates an example system with an example device that can implement embodiments of mobile device safe driving.
Detailed Description
[0028] Embodiments of mobile device safe driving are described and provide a safe driving service that can be implemented as a mobile device service or application, such as in a mobile phone, portable tablet device, or other type of computing and/or communication device. Sensor systems may be implemented in an effort to determine whether a user owner of a mobile phone is both using the phone device and driving at the same time. However, this may be difficult to accurately detect, and the likelihood of false-positives can lead to incorrect determinations and false reporting. One solution for improving driving safety is to make it easier for a driver to be more responsible, with less possibility of distraction.
[0029] A safe driving mode places a mobile phone in a mode that minimizes distraction, and can help a driver be safer and more responsible while driving. A core goal of safe driving mode is not to attract attention to the device screen, or divert a driver's attention from the road. If drivers can simply initiate a safe driving mode without having to first enter a PIN code on a device lock screen, it is likely the drivers will choose the safer option and use the service. Additionally, the safe driving service can override the safe driving mode and return the device to normal user mode operation, such as when the device moved in manner that indicates use of the device is safe, such as when determining that driving has stopped. Further, a user of the device can easily override the safe driving mode to reactivate normal user mode operation, such as with a user input to the device (e.g., an input to the device power button) that quickly overrides and exits the safe driving mode.
[0030] A safe driving service can also be implemented to provide safe driving phone reports, such as a safe driving report for a teenage driver that is sent to a parent's device, for accountability and reporting. The reporting may also be via a cloud-based data service that aggregates the data in the cloud and generates a driving report for distribution to designated devices, such as to the parent of a teenage driver. A driving report may indicate successful and/or safe driving, such as a notice of “no recorded unsafe use of a phone when driving”. Similarly, a driving report may indicate unsafe driving or an “unlock phone” override event, in which case the safe driving service can log the next actions or events to determine whether a driving mode violation occurred. A parent of a teenage driver, for example, can determine unsafe driving habits and behavior in a transparent manner, which provides the parent a reporting tool and an opportunity for a safety-minded conversation. This approach may be a preferable alternative to completely locking or disabling the teenage driver's phone.
[0031] While features and concepts of mobile device safe driving can be implemented in any number of different devices, systems, environments, and/or configurations, embodiments of mobile device safe driving are described in the context of the following example devices, systems, and methods.
[0032] FIG. 1 illustrates an example of user interfaces for mobile device safe driving. An example mobile device 100 may be any one or combination of a mobile phone, tablet device, computing device, communication, entertainment, gaming, navigation, and/or other type of portable electronic device. The example mobile device 100 includes an integrated display device 102 on which user interfaces can be displayed, such as a device lock screen 104 that indicates the device is locked at 106. For example, a user owner of the mobile device may set-up the device to lock when not in use so that someone else cannot access the device.
[0033] As a driver of a vehicle, the user owner of the mobile device 100 can initiate activation of safe driving mode without having to unlock the device from the device lock screen 104. As shown in the example 108, the user can swipe the device lock screen with a gesture input to transition the display to a driving mode lock screen 110, which is illustrated at 112 when displayed on the display device. The transition to the driving mode lock screen 110 can be initiated without a PIN code or other authentication credential entered on the device lock screen 104. In implementations, the gesture input may be any type of user and/or gesture input in any direction on the integrated display device 102 of the mobile device. Alternatively or in addition, any type of device, button, and/or gesture inputs may be utilized effective to transition from the device lock screen 104 to the driving mode lock screen 110. When a safe driving mode is activated on the mobile device 100, the aspects and features described herein for restricted execution modes (e.g., FIGS. 8-12 ) may be utilized to support and implement the safe driving mode as a restricted execution mode.
[0034] FIG. 2 illustrates examples 200 of safe driving mode user interfaces, such as a lock screen 202 displayed on a mobile phone 100 when the safe driving mode is active. Another lock screen 204 is an example of a display that indicates the phone is locked, but capable of enabling critical functionality like emergency calls or calls to a “white list” of important contacts. In an example, safe driving mode settings 206 are illustrated for a teenager in two different years. As shown in a user interface for the first year of driving 208, the teen is a new driver and has access only to the family car. In his first year, his parents have used a settings user interface to restrict his usage and lock the phone completely unless a parent is also in the car. As shown in a user interface for the second year of driving 210, the teen has his own car and his parents have allowed him to move up to hands-free operation with both vehicles.
[0035] Embodiments of mobile device safe driving incorporate bi-directional communication with a vehicle, or can be implemented for no communication with the vehicle. Mobile device safe driving can also be implemented to limit vehicle speed so that a teenage driver cannot exceed a designated speed limit, such as in a school zone. Safe driving can also communicate car service reminders to the driver, such as to change the oil, wiper blades, etc. At the time of a crash, the phone device can automatically report its status, send messages, alert emergency services, etc. An emergency may be based on crash impact data, or based on erratic inputs (e.g., due to a diabetic episode, heart attack, blown tire, etc.). For some emergencies, the safe driving service can slow the vehicle down, such as for a blown tire. For other emergency alert scenarios, the safe driving service can initiate a safety timer and/or initiate sending a text or other type of message. The safe driving service can initiate the safety timer as a display on the mobile device, such as “Emergency Detected: Sending an Alert in N seconds” and start a countdown, which provides the user of the device an opportunity to cancel the alert before a message is automatically sent. An emergency and/or other possible alert situation may also be based on a vehicle breakdown when the vehicle is pulled over to the side of the road at a detected location that would not typically be a stopping location.
[0036] Safe driving features and modes can be implemented for different levels of permissions for family members, to loan a car to a friend, for valet monitoring, etc. The vehicle that is associated with a mobile phone and user can communicate independently of the device, such as indirectly through a cloud-based service to communicate safe driving mode notifications to a parent and/or family members. A safe driving mode notification may alert a driver that he or she is going to be late for an appointment based on the current route of travel and destination. A message can then be generated to inform the driver to re-route, edit an errand list, update GPS, etc. For example, a driver may be on a list of errands for Mom with mom's car. When mom cancels one of the errands from the shared calendar, GPS informs the Kid driver to skip the next errand stop.
[0037] Safe driving features and mode implementations can also be utilized to manage a fleet of any type vehicles. As a driver approaches a vehicle, the driver's phone is identified to the vehicle and can be paired with the vehicle, such as via Bluetooth, WiFi, or other addressable device. This may be integrated with a key fob location proximate the ignition switch in a vehicle and/or setup for different profiles based on the vehicle and phone to checkout a vehicle.
[0038] In a safe driving mode, a kid's phone can become a communication channel that a parent can open with his or her phone, such as to activate the kid's phone to record video and/or audio at its current location. This may also be auto-activated, such as when the kid's phone is in another car that has been detected driving erratically or at excessive speed to send a safe driving mode notification to the parent's phone device. Safe driving features and modes are not limited to the control of a parent over a teenage driver. Any person that wants to drive safer can initiate the safe driving features and modes on his or her device. For example, a rental car company can discount a driver if the driver implements safe driving mode while driving a rented car.
[0039] Safe driving features and modes can also provide warnings, messages, and notifications when driving in other countries or regions (e.g., regional or country specific safe driving), such as notifications of different road rules when driving in different countries. Safe driving features may also be implemented to recognize road and/or weather conditions, and provide warnings and notifications. Safe driving mode notifications can be filtered and optionally programmed. For events of a certain type, an immediate message may be generated, such as any one of an SMS, MMS, or instant message. Alternatively or in addition, a daily or weekly driving report can be generated and communicated.
[0040] Mobile device safe driving can utilize phone device sensors and features, such as to determine if a user is traveling on a train as a passenger, or determine bus pass information. A user passenger status may also be determined from audio and/or camera images used to determine one's space in car, train, or other vehicle. Features may also be implemented to determine media access control (MAC) address ranges to identify proximate conveyances (e.g., not just passing cars).
[0041] A safe driving application may be implemented in the vehicle for the bulk of the data processing, and the phone device is then a client device to the vehicle. Safe driving features can incorporate a theft deterrent in the vehicle application that identifies only those phone devices that, when proximate or in the vehicle, allow the vehicle to start and be driven. Near field communication (NFC) tags can be implemented in a vehicle, such as in the doors of the vehicle, to identify proximate phone devices of associated users in the seats of the vehicle.
[0042] Safe driving features reduce and/or eliminate the distractions associated with a mobile device while driving. A mobile device, such as a mobile phone, can be synced with the automobile being driven, and based on geo-location and/or acceleration rates, functions of the mobile phone can be disabled or partially disabled (e.g., when a safe driving mode is activated). A safe driving implementation may be an application that can not be uninstalled from a mobile device, such as when implemented as part of the operating system of a device. Alternatively, a safe driving application may be downloaded to a mobile device as an aftermarket, first-party, or third-party application. Embodiments of safe driving include any one or combination of implementation features, such as described in the following paragraphs.
[0043] A safe driving disabled mode is an example of a safe driving feature that can be implemented for a mobile device when a user is operating a vehicle with a wireless beacon device associated with the vehicle (e.g., a Bluetooth hands-free speaker/microphone device). Mobile device safe driving provides that a restrictive disabled mode is turned-off or deactivated when a mobile device is in the presence of both a vehicle wireless beacon device and another mobile device owned by an associated parent or guardian. In this manner, the solution does not present as a failure to the owner of the device. If the device owner is a teenager and Mom is driving, the teenager has normal access to the device capabilities. If the device owner is a teenager and he or she is driving, the safe driving mode can be disabled, but the solution relies on the presence of Mom to reinforce and/or remind the teenager of good driving habits. Safe driving mode implementations can dynamically change behaviors based on who is in the vehicle.
[0044] Devices and/or device accounts can be associated within a set of devices or device accounts (e.g., a family phone account, live accounts, a connected set of devices, etc.), and all or a subset of the devices or accounts can communicate with other devices or accounts. Mobile device safe driving can be implemented to restrict access to a phone based on GPS acceleration data, distinguished from the physical act of driving with car monitors. Safe driving is not necessarily tied to a particular vehicle, and can be related to other contextual information that is not registered by car monitors, such as loud music, distracting friends in the car, or other sources of distraction that range from passive to active behaviors. Safe driving information can be used to counter insurance claims of unsafe driving and rate increases, and not just for teenagers, but also senior citizens, drivers with DUI's, etc.
[0045] A safe driving mode user interface is implemented from which safe driving mode settings can be enabled and disabled, and there may be many levels of disabling device capabilities. For example, a safe driving mode can render the device completely disabled, or just text messaging is disabled to eliminate texting while driving, but not texting while a passenger in the vehicle. A device in safe driving mode can display an indication that a safe driving mode is enabled, such as an icon next to the current time/day and/or the words “Safe Driving Mode On” on a device home screen or lock screen. Safe driving mode settings can associate one or more vehicles to any user and/or number of devices. The safe driving mode settings can all be set remotely from an authoritative phone device, such as a parent's mobile phone.
[0046] FIG. 3 illustrates an example system 300 in which embodiments of mobile device safe driving can be implemented. The example system includes the mobile device 100 as described with reference to FIG. 1 , with the integrated display device 102 on which a user interface can be displayed, such as the driving mode lock screen 110. Additionally, the mobile device can be implemented with various components, such as a processor and/or memory system, as well as any number and combination of differing components as further described with reference to the example device shown in FIG. 12 to implement embodiments of mobile device safe driving.
[0047] The mobile device 100 includes a safe driving service 302, such as a software application implemented as executable instructions that are stored on computer-readable storage media, such as any suitable memory device or electronic data storage. Additionally, the safe driving service 302 can be executed with a processing system at the mobile device to implement embodiments of mobile device safe driving as described herein. The safe driving service 302 may be implemented as an independent device application that is executable on the device to interface with the many applications, features, and functions of the device.
[0048] The example system 300 also includes a cloud storage and service 306 that can include any type of cloud-based (e.g., network-based) data services 308 used to store or maintain driving reports 310, which are an aggregate of safe driving events and unsafe driving events, and the reports indicate safe driving and/or unsafe driving. A safe driving report can also indicate that the features of a mobile device were enabled by user override while the mobile device was moving in a vehicle.
[0049] Any of the devices and services (e.g., implemented as server devices) described herein can communicate via a network 312, which can be implemented to include a wired and/or a wireless network. The network can also be implemented using any type of network topology and/or communication protocol, and can be represented or otherwise implemented as a combination of two or more networks, to include IP-based networks and/or the Internet. The network may also include mobile operator networks that are managed by a mobile network operator and/or other network operators, such as a communication service provider, mobile phone provider, and/or Internet service provider. Alternatively or in addition, peer-to-peer communication techniques may be utilized, such as multiple devices connected using a peer-to-peer communication network.
[0050] The safe driving service 302 is implemented to activate a safe driving mode 314 when a user of the device transitions to the driving mode lock screen 110, and the safe driving service disables features of the mobile device while the safe driving mode is activated. Features of the mobile device can include the communication features of the device, such as any one or combination of text messaging, instant messaging, and voice communication, as well as the integrated display device 102, which may be temporarily disabled from displaying distracting information.
[0051] The safe driving service 302 is implemented to register safe driving events 316 and unsafe driving events 318 associated with use (or non-use) of the mobile device by a user who is currently driving. Generally, it is unsafe to use a mobile device in any manner that averts driver attention from looking at the road to looking at the device. In some instances, the mobile device may be used in safe manner while driving, such as when listening to turn-by-turn navigation directions, or when text messages are converted to audio so that the driver can listen to incoming text messages while maintaining focus on the road. Accordingly, a reported safe event can be based on detection that a user is driving a vehicle and a safe driving mode 314 has been activated on his or her mobile device, or when the user overrides the safe driving mode to use the device, but the vehicle has stopped moving. Reported unsafe events can include a teenage driver using his or her mobile device while driving and when the vehicle is in motion, manually overriding the safe driving mode to use the device while the vehicle is moving, disabling the safe driving lock screen, or any other combination of a user driving and using a mobile device at the same time.
[0052] The safe driving service 302 can then aggregate the safe driving events 316 and the unsafe driving events 318 to generate a safe driving report 320 that indicates safe driving and/or unsafe driving based on the safe and unsafe driving events. A safe driving report can include a summary of the safe driving events and the unsafe driving events, as well as statistical indications of safe driving events to unsafe driving events (e.g., an 80% safe driver). The safe driving service can communicate (or initiate communication thereof) a safe driving report 320 to an associated device of the mobile device.
[0053] The mobile device 100 may include a positioning unit 322, such as a Global Positioning System (GPS), Assisted-GPS (A-GPS), or similar geographical positioning unit, to determine geographic location data 324 and motion data 326 that indicates the device is moving and possibly the speed or acceleration at which the device is moving, such as in a vehicle. The mobile device also includes a driver determination sensor 328, such as an integrated camera that generates a digital image. A vehicle may also include a camera that communicates with the mobile device 100 as a position sensor to indicate the location of a user of the device in the vehicle. A vehicle may also include other features to detect that a user with a device in close proximity is driving the vehicle.
[0054] A driver determination sensor 328 may also be implemented as any other type of sensor that indicates whether a user of the device is driving a vehicle or is a passenger in the vehicle. For example, a driver determination sensor may be implemented for any type of wireless communication, such as near field communication (NFC) with the vehicle, and the safe driving service can determine whether the user of the device is driving the vehicle or is a passenger in the vehicle based on the wireless and/or near-field communication. Other types of vehicle sensors may detect voice ID or other biometric ID (e.g., a fingerprint reader integrated into the steering wheel). Other types of sensors within the vehicle that report back to the device to indicate that the user of the device is driving the vehicle may include seat sensors, and heat and/or contact sensors integrated into the steering wheel of the vehicle.
[0055] The safe driving service 302 is implemented to determine that the mobile device is moving in a vehicle based on the motion data 326, and determine that the user of the device is driving the vehicle based on sensor data from the driver determination sensor 328, such as based on a digital image from the integrated camera, based on a digital image from a camera integrated with the vehicle, wireless sensor communication, and/or based on NFC. The safe driving service can then disable features of the device, such as the communication features, when the mobile device is moving in the vehicle and the user of the device is driving the vehicle, e.g., by entering a safe driving mode automatically. As described further herein, a user may also voluntarily elect to enter a safe driving mode that disables features of the device without the input of sensors, e.g., by inputting an input to a lock screen. The communication features of the device can include any one or combination of text messaging, instant messaging, and voice communication, as well as the integrated display device 102, which may be temporarily disabled from displaying messages and alerts, or from turning on. The safe driving service can also determine that the user of the mobile device is a passenger in the vehicle, and then determine that safe driving mode should not be entered and/or should be exited in order to enable the features of the device.
[0056] The safe driving service 302 is also implemented to initiate communication of safe driving notifications 330 to other devices that are associated with the mobile device. For example, the mobile device may include an audio sensor to detect an audio level in the vehicle, and the safe driving service can generate an unsafe driving notification to indicate that the audio level in the vehicle is a driver distraction. The safe driving notification can then be communicated to associated devices of the device to inform the users of the other devices. Although a safe driving report 320 may be generated based on an aggregate of the safe driving events 316 and the unsafe driving events 318 over time, an unsafe driving notification 330 can be reported out immediately. For example, although a safe driving report that indicates an audio level distraction in a vehicle two days ago may be useful for discussion with a young driver, an unsafe driving notification can be generated during the unsafe distraction in an effort to correct the current unsafe driving condition. The safe driving service can also generate an unsafe driving notification to indicate that the features of the device, such as the communication features, have been enabled by user override while the device is moving in a vehicle and the user of the device is driving the vehicle. This type of action may be reported as both an unsafe driving event 318 in a subsequent safe driving report 320, and as an immediate safe driving notification, such as to a parent of the driver.
[0057] The safe driving service 302 can also be implemented to determine that vehicle motion is erratic based on the motion data 326, and then generate an unsafe driving notification to indicate to users of the associated devices that the vehicle motion is erratic. The safe driving service can also determine that at least one of the associated devices is proximate the mobile device 100 in the vehicle, determine that the associated device corresponds to an adult user, and then enable the features of the mobile device of the driver of the vehicle.
[0058] The safe driving service 302 is also implemented to receive speed limit data that corresponds to a location of the vehicle, and communicate a vehicle speed limit to the vehicle to control vehicle speed at the location of the vehicle. The safe driving service can also determine that the vehicle has stopped at an unknown location, such as beside the road somewhere, and determine a location of the vehicle from the location data 324. The safe driving service can then generate an unsafe driving notification 330 to indicate that the vehicle has stopped at the unknown location at the determined position of the vehicle to inform users of associated devices.
[0059] Example methods 400, 500, and 700 are described with reference to respective FIGS. 4 , 5, and 7 in accordance with one or more embodiments of mobile device safe driving. Generally, any of the services, components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Example methods may be described in the general context of executable instructions stored on computer-readable storage media that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like.
[0060] FIG. 4 illustrates example method(s) 400 of mobile device safe driving. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0061] At 402, a device lock screen is displayed on an integrated display device of a mobile device. For example, the mobile device 100 (FIG. 1 ) displays a device lock screen 104 on the integrated display device 102 of the mobile device. At 404, the display is transitioned from the device lock screen to display a driving mode lock screen without a PIN code or other authentication credential entered on the device lock screen. For example, an input system of the mobile device 100 receives an input, such as a gesture input or device selectable control input, and the input is effective to transition from displaying the device lock screen 104 to display the driving mode lock screen 110 without a PIN code entered on the device lock screen.
[0062] Alternatively or in addition, the display of the mobile device may be automatically transitioned from the device lock screen to display a driving mode lock screen without manual user intervention, such as if the device determines that the user has begun driving based on detected sensor data, such as a seat sensor, heat and/or contact sensors integrated into the steering wheel, or a fingerprint reader integrated into the steering wheel. Driver determination sensor data may also be determined from near field communication (NFC) within the vehicle that indicates whether the user of the device is driving the vehicle or is a passenger in the vehicle.
[0063] At 406, a safe driving mode of the mobile device is activated, either in response to user input or automatically as described at 404. For example, the safe driving service 302 (FIG. 3 ) at the mobile device 100 activates the safe driving mode 314 of the mobile device. At 408, features of the mobile device are disabled while the safe driving mode is activated. For example, the safe driving service 302 at the mobile device 100 disables features of the mobile device while the safe driving mode 314 is activated, such as the communication features of the device (e.g., to include any one or combination of text messaging, instant messaging, and voice communication), as well as the integrated display of the device, which may be temporarily disabled from displaying messages and alerts, or from turning on at all.
[0064] At 410, safe driving events and unsafe driving events associated with use of the mobile device by a user of the mobile device driving are registered. For example, the safe driving service 302 at the mobile device 100 registers the safe driving events 316 and the unsafe driving events 318 associated with use of the mobile device by a user who is determined to be concurrently driving. A safe driving event can include a driver having a safe driving mode 314 activated on his or her mobile device while driving a vehicle, or stopping the vehicle before manually overriding the safe driving mode to use the device. Unsafe driving events can include a teenage driver using his or her mobile device while driving and when the vehicle is in motion, manually overriding the safe driving mode to use the device while the vehicle is moving, disabling the safe driving lock screen, or any other combination of a user driving and using a mobile device at the same time.
[0065] At 412, the safe driving events and the unsafe driving events are aggregated. For example, the safe driving service 302 at the mobile device 100 aggregates the safe driving events and the unsafe driving events. At 414, a safe driving report that indicates safe driving and/or unsafe driving is generated. For example, the safe driving service 302 at the mobile device 100 generates a safe driving report 320 that indicates safe driving and/or unsafe driving. A safe driving report can include a summary of the safe driving events and the unsafe driving events, as well as statistical indications of safe driving events to unsafe driving events (e.g., an 80% safe driver).
[0066] At 416, the safe driving report is communicated to another device that is associated with the mobile device. For example, the safe driving service 302 at the mobile device 100 communicates the safe driving report is communicated to an associated device of the mobile device.
[0067] FIG. 5 illustrates example method(s) 500 of mobile device safe driving. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0068] At 502, a determination is made that a device is moving in a vehicle based on location data and motion data that indicates the device is moving. For example, the positioning unit 322 (e.g., a GPS unit and/or other type of positioning system component) at the mobile device 100 (FIG. 3 ) determines that the mobile device 100 is moving in a vehicle based on geographic location data and motion data that indicates the device is moving.
[0069] At 504, a determination is made as to whether a user of the device is driving the vehicle, e.g., based on sensor data from a driver determination sensor. For example, the safe driving service 302 at the mobile device 100 determines whether a user of the device is driving the vehicle based on sensor data from a driver determination sensor. If the user of the device is a passenger in the vehicle (i.e., no from 504), then at 506, a safe driving mode on the mobile device is deactivated the features of the device are enabled. For example, the safe driving service 302 at the mobile device 100 enables the features of the device, such as the communication features and/or the integrated display, responsive to the determination that the user of the device is a passenger in the vehicle.
[0070] If the user of the device is driving the vehicle (i.e., yes from 504), then at 508, the safe driving mode is activated, which disables distracting features of the mobile device. For example, the safe driving service 302 at the mobile device 100 activates the safe driving mode, which disables distracting features of the device (e.g., communication features that include text messaging, instant messaging, and voice communication) responsive to the determinations that the device is moving in the vehicle (at 502) and the user of the device is driving the vehicle (at 504). In implementations, some features of the device can be disabled, while others remain enabled. For example, text messaging may be disabled, while hands-free calls to or from designated numbers remains enabled as well as a feature of the device that converts a text message to audio so that a driver can focus on driving while listening to incoming text messages.
[0071] At 510, a user interface is displayed on an integrated display of the device to indicate a safe driving mode of the device has been activated. For example, the mobile device 100 includes the integrated display device 102 on which a safe driving lock screen 110 is displayed to indicate a safe driving mode of the device has been activated.
[0072] At 512, an unsafe driving notification of an unsafe driving event is generated to indicate an unsafe driving condition. For example, the safe driving service 302 at the mobile device 100 generates an unsafe driving notification 330 to indicate that an unsafe driving condition currently exists in a vehicle (or having to do with a vehicle). For example, unlike a safe driving report 320 that may be generated based on an aggregate of the safe driving events 316 and the unsafe driving events 318 over time, an unsafe driving notification 330 can be reported out immediately, such as during the unsafe distraction in a vehicle in an effort to correct the current unsafe driving condition. The safe driving service can also generate an unsafe driving notification to indicate that the features of the device, such as the communication features, have been enabled by user override while the device is moving in a vehicle and the user of the device is driving the vehicle.
[0073] At 514, the unsafe driving notification is communicated to one or more other devices that are associated with the mobile device. For example, the safe driving service 302 at the mobile device 100 initiates communication of the unsafe driving notification to the other devices that are associated with the mobile device. At 516, a determination is made that at least one of the other devices is proximate the device in the vehicle. For example, the safe driving service 302 at the mobile device 100 determines that at least one of the other devices that is associated with the mobile device is proximate the mobile device in the vehicle.
[0074] At 518, a determination is made that the other device corresponds to an adult user or other supervisory user. For example, the safe driving service 302 at the mobile device 100 determines that the other device that is associated with the mobile device and proximate the mobile device in the vehicle, corresponds to an adult user or other supervisory user. Responsive to the determinations that the other associated device is proximate the mobile device in the vehicle (at 516) and corresponds to an adult user (at 518), the safe driving service 302 deactivates the safe driving mode on the device and enables the features of the mobile device 100 at 510.
[0075] FIG. 6 illustrates an example system 600 that includes mobile devices 602 and 604 that are examples of the mobile device 100 as described with reference to the previous FIGS. 1-5 . In embodiments, the mobile devices 602 and 604 can each be associated with a different user, and the users may be defined members of private interaction hub, which may include two or more associated devices. The mobile devices each include an implementation of the safe driving service 302 as described with reference to the previous FIGS. 1-5 . In the example system 600, multiple devices can be interconnected through a central computing device or system, which may be local to the multiple devices or may be located remotely from the multiple devices.
[0076] In embodiments, the central computing device may be a cloud 606 of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link. In embodiments, this interconnection architecture enables functionality across multiple devices to provide a networked service environment of the multiple devices. Each of the devices may have different physical configurations and capabilities, and the central computing device can utilize a platform 608 to maintain associated devices identifiers 914, and implement the coordination architecture 922 and/or the safe driving service 302 in embodiments of mobile device safe driving.
[0077] The cloud 606 includes and/or is representative of the platform 608 for the networked service components (e.g., the safe driving service 302) that implements embodiments of mobile device safe driving. The platform abstracts underlying functionality of hardware, such as server devices, and/or software resources of the cloud. The networked service components may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the mobile devices 602 and 604.
[0078] In embodiments, the safe driving service 302 at the platform 608 is implemented to receive an unsafe driving notification from a mobile device 602 when an unsafe driving notification is initiated from the device. The safe driving service can then determine associated devices of the device based on the associated devices identifiers 914, and communicate the unsafe driving notification received from the device 602 to the other device 604 (and to any other associated devices). Additionally, the safe driving service can communicate the safe driving notification to the other devices in multiple formats, such as a text message, an instant message, an audible message, as a hub message, or as an image for display at the associated devices. The safe driving service 302 at the platform 608 can also receive safe driving events 316 and unsafe driving events 318 from the mobile devices, and aggregate the driving events to generate a safe driving report 320 that is communicated out to the associated devices. The safe driving service 302 at the platform 608 can also implement any of the embodiments and features of mobile device safe driving as described herein.
[0079] FIG. 7 illustrates example method(s) 700 of mobile device safe driving. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0080] At 702, an unsafe driving notification is received from a mobile device that is moving in a vehicle when a user of the device is driving the vehicle. For example, the safe driving service 302 implemented as part of the platform 608 (FIG. 6 ) receives an unsafe driving notification from the mobile device 602 that is moving in a vehicle when a user of the device is driving the vehicle. The unsafe driving notification indicates a driving condition of the vehicle and the unsafe driving notification can be communicated to associated devices of the device to inform users of the associated devices. Similar to the safe driving service 302 implemented at the mobile device 100 (FIG. 3 ), the safe driving service 302 implemented as part of the platform 608 also receives safe driving events 316 and unsafe driving events 318 from the mobile devices.
[0081] At 704, other devices that are associated with the mobile device are determined based on identifiers of the mobile device and the other associated devices. For example, the safe driving service 302 at the platform 608 determines the associated devices, such as mobile device 604, based on the associated devices identifiers 914. At 706, the unsafe driving notification received from the mobile device is communicated to the other devices that are associated with the mobile device. For example, the safe driving service 302 at the platform 608 initiates communication of the safe driving notification that is received from the mobile device 602 to the associated device 604.
[0082] At 708, a vehicle notification is received from the vehicle. For example, the safe driving service 302 at the platform 608 receives a vehicle notification from the vehicle (rather than from the mobile device) that the mobile device 602 is moving in when a user of the device is driving the vehicle. A mobile device that is traveling in a vehicle can be paired with the vehicle, and the vehicle itself can take on the role of a safe driving service to register and communicate safe driving events, unsafe driving events, and unsafe driving notifications. At 710, the vehicle notification received from the vehicle is communicated to the other devices that are associated with the mobile device. For example, the safe driving service 302 at the platform 608 initiates communication of the vehicle notification that is received from the vehicle to the associated device 604.
[0083] At 712, location data is received that indicates a location of the vehicle. For example, the safe driving service 302 at the platform 608 receives location data, such as from a GPS system, that indicates a location of the vehicle that the mobile device 602 is moving in when a user of the device is driving the vehicle. At 714, speed limit data that corresponds to the location of the vehicle is received. For example, the safe driving service 302 at the platform 608 receives speed limit data that corresponds to the location of the vehicle (as determined from the location data at 712). At 716, a vehicle speed limit is communicated to the vehicle to control vehicle speed at the location of the vehicle. For example, the safe driving service 302 at the platform 608 communicates a vehicle speed limit to the vehicle to control vehicle speed at the location of the vehicle that the device 602 is moving in when a user of the device is driving the vehicle.
[0084] FIG. 8 illustrates an example of user interfaces of a restricted execution mode. An example mobile device 800 may be any one or combination of a mobile phone, tablet device, computing device, communication, entertainment, gaming, navigation, and/or other type of portable electronic device. A shared space can be implemented for user access to functionality of device applications without a password, as well as for access to any applications, functions, and features of the mobile device 800 that are designated by the user in the shared space.
[0085] The example mobile device 800 includes an integrated display device 802 on which user interfaces can be displayed, such as a device lock screen 804 that indicates the device is locked at 806. For example, a user owner of the mobile device may set-up the device to lock when not in use so that someone else cannot access the full functionality of applications, such as email and text, and/or have access to the Internet via a browser application without providing authentication credentials such as a personal identification number (PIN), login, or other authentication credential.
[0086] The user owner of the mobile device 800 can allow another person to use the phone, and hand the phone over without having to unlock the device from the device lock screen 804 by entering a PIN or other credential. As shown in the example 808, a person that has borrowed the phone can swipe the device lock screen with a gesture input to access a shared space user interface 810, which is illustrated at 812 when displayed on the display device, and which provides access to a limited subset of application functionality. The borrower does not enter a PIN or other credential to access the shared space user interface. In implementations, the gesture input may be any type of user and/or gesture input in any direction on the integrated display device 802 of the mobile device. Alternatively or in addition, any type of device, button, and/or gesture inputs may be utilized effective to transition from the device lock screen 804 to the shared space user interface 810.
[0087] Restricted execution modes enable implementation of a shared space on a device where a user owner can include device applications that a guest or child can access without requiring a password, and the device applications will be programmatically prevented from being able to access other private device content on the device.
[0088] There may be situations when a user owner of a device may want to have access to some content or applications on their mobile phone without unlocking the phone with a PIN code or other authentication credential. Restricted execution modes enable the user owner to make some experiences available without password access, and without compromising the security of sensitive personal or corporate data. In implementations, restricted execution modes allow applications to run, but restricts access to sensitive data or experiences using several mechanisms, such as security capabilities, blocked navigation, and application origin. If an application has a particular security capability, a runtime check is made centrally when the application attempts to access a protected resource, and if the application is running in a restricted execution zone, an error is returned that can be handled by the application. When a device is running in a restricted execution mode, a device application may be referred to as running in a restricted execution “zone”.
[0089] For the blocked navigation security capability, applications often take advantage of built in tasks to complete user actions like sending an email, making a phone call, etc. When the restricted execution mode is activated on a device, the origination of a device application task at run-time is what is considered to determine whether the device application, and more specifically, whether the task will be allowed. An application task, which is generally synonymous to an application programming interface (or API) call, may include aspects of a data access API call, but it also includes a request to initiate a particular action or actions different than data access, and the task request may incorporate metadata associated with the action of the requested task. The level of functionality is provided on a task-by-task basis to determine whether the action or actions of a requested task will be available in the restricted execution mode during run-time origination of a task request. A device application can be executed by the device, but only some functions of the device application will execute when the restricted execution mode is activated on the device.
[0090] Examples of restricting the functionality of a device application may include not permitting the device application to be launched altogether or limiting the device application to calling only a restricted subset of API calls that is narrower than the normal set of API calls available to the application when the mobile device is running in normal user mode. Restricting access to device content also may include disallowing certain API calls that provide access to particular sets of data or content. In many examples, restricting functionality or access does not include analyzing or changing Access Control Lists (ACLs), Access Control Entries (ACEs), or similar file-system access control metadata maintained by a file system. For example, a device application can be restricted from access to device content while a restricted execution mode is activated on a device.
[0091] When running in a restricted execution zone, all application requested navigations are screened and only those allowed by the system can continue. Others fail in a backwards compatible way so that legacy applications do not need to be updated to run in the restricted execution zone. For the application origin security capability, only applications that originate and/or have been downloaded from a first-party provider can run (e.g., execute) in a restricted execution mode. This ensures that applications which have not been security checked, and may access sensitive and/or private data on a device, do not run without the user unlocking the device first.
[0092] FIG. 9 illustrates an example system 900 in which embodiments of restricted execution modes can be implemented. The example system includes the mobile device 800 as described with reference to FIG. 8 , with the integrated display device 802 on which a user interface can be displayed, such as the shared space user interface 810 that is representative of a shared space on the device. Additionally, the mobile device can be implemented with various components, such as a processor and/or memory system, as well as any number and combination of differing components as further described with reference to the example device shown in FIG. 17 to implement embodiments of restricted execution modes.
[0093] The mobile device 800 includes a restricted execution service 902 that can be implemented as a software application (e.g., executable instructions) stored on computer-readable storage media, such as any suitable memory device or electronic data storage. Additionally, the restricted execution service 902 can be executed with a processing system at the mobile device to implement embodiments of restricted execution modes as described herein. The restricted execution service 902 may be implemented as an independent device application that is executable on the device to interface with the many applications, features, and functions of the device.
[0094] The example system 900 may also include a cloud storage and service 906 that can include any type of cloud-based (e.g., network-based) data services 908 used to store or maintain accessible data 910 (e.g., data accessible by device applications on the mobile device 800). Any of the devices and services (e.g., implemented as server devices) described herein can communicate via a network 912, which can be implemented to include a wired and/or a wireless network. The network can also be implemented using any type of network topology and/or communication protocol, and can be represented or otherwise implemented as a combination of two or more networks, to include IP-based networks and/or the Internet. The network may also include mobile operator networks that are managed by a mobile network operator and/or other network operators, such as a communication service provider, mobile phone provider, and/or Internet service provider. Alternatively or in addition, peer-to-peer communication techniques may be utilized, such as multiple devices connected using a peer-to-peer communication network.
[0095] The restricted execution service 902 is implemented to manage a restricted execution mode 914 of a shared space 916, such as to limit and/or restrict device applications 918 and shared device applications 920 that are included in the shared space 916 that is accessible without a PIN or authentication credential. The device applications 918 can include any type of software applications, and the functions and features thereof, that run on the device, such as for user interaction with messaging, gaming, media playback, document viewing, and communication applications. The device applications may also include system-level components that users of a device generally do not access or utilize, but that typically run in the background while the device is operational. The shared device applications can include any subset of the device applications, and are designated as a shared device application when included in the shared space 916 for limited and/or restricted functionality when a restricted execution mode 914 is activated on the device.
[0096] A user owner of the mobile device 800 can choose the device applications and features, and/or device content, that can be included in the shared space and accessed by a child or guest while the restricted execution mode is activated. Further, a device application may be allowed a restricted level of functionality while running in the shared space (i.e., the application may be executed), yet generally cannot access device content 922 that is restricted from access, such as contacts, email, and calendar databases, as well as limited access to the device file system.
[0097] The content databases, device file system, Internet access, and other device content and features can be protected from device application access when the restricted execution mode is activated. For example, a device application that can access the Internet, email, contacts, etc. when a device is unlocked and operating in a normal user mode will be automatically restricted when the restricted execution mode is activated, such as if the device application has been added to the shared space and is allowed limited functionality in the shared space. As an example, a digital camera application that has been added to the shared space may allow a user to take and view new photos, but previous photos will be restricted from viewing the restricted execution mode is activated on the device.
[0098] The shared space user interface 810 of the shared space is customizable by the user owner of the device. For example, the user owner can add applications, such as games and music applications, to the shared space so that the applications are recognized and can be launched in the shared space, perhaps with limited functionality. However applications that are not recognized in the shared space cannot be launched in the shared space. For example, if a game application that is pinned or recognized in the shared space attempts to itself launch a browser application (e.g., as part of the game's execution), the restricted execution service 902 will check if the browser application is pinned and recognized in the shared space. If the browser application is not recognized in the shared space, then the restricted execution service will fail to launch the application, or if the browser application is recognized, then the browser application can be launched in the shared space by the game application.
[0099] As described with reference to FIG. 8 , an input can be received, such as a gesture input or device selectable control input, and the restricted execution service 902 initiates a transition from displaying the device lock screen 804 to display the shared space user interface 810 of the shared space 916 without receiving a PIN code or other authentication credential entered on the device lock screen. The restricted execution service 902 is implemented to manage the shared space 916 when the restricted execution mode 914 is activated. The restricted execution service 902 can activate the restricted execution mode 914 of the mobile device 800, and restrict access of a device application 918 to the device content 922, to a file system of the mobile device, and/or to limit the application to a limited set of functionality or tasks while the restricted execution mode is activated.
[0100] The shared space 916 can include a shared device application 920, and the restricted execution service 902 can allow the shared device application access to the device content 922 while the restricted execution mode 914 is activated. The restricted execution service 902 can determine whether a device application 918 is implemented or designed so that a user can designate to allow the device application access to the device content if the device application is included in the shared space 916 as a shared device application. Alternatively, a device application may be designed as not to be allowed access to the device content even if the device application is included in the shared space. Additionally, this type of a device application may also be implemented as not even being eligible for user-designation to be included in the shared space.
[0101] In restricted modes, a configuration of a device application may be designed or programmed to indicate whether the device application is ever to be allowed to run (e.g., execute) in a restricted mode, irrespective of user choice. For example, a confidential corporate application or another application downloaded from a third-party application store that may access private corporate data can be configured to never be allowed to run (e.g., execute) in any restricted mode, even if a user would like it to do so. A configuration of some device applications may be user-controlled to indicate whether the device application is to be allowed to run in a particular restricted mode, such as allowing a subset of games or applications in a kid zone restricted mode, or allowing a subset of camera lens applications to run when the phone is locked.
[0102] The restricted execution service 902 can also be implemented to validate whether or not a given device application can be navigated to regardless of the reason for the navigation request, taking into account the current restricted mode and the target application's system and user configuration. Additionally, a separate navigation stack can be maintained for a normal mode user experience and for the current restricted execution mode. The restricted execution service 902 is also implemented to allow or disallow migration of applications from the normal mode stack to the restricted mode stack or vice-versa based on scenario needs, and to determine when to close applications on each stack based on available resources and transitions into and out of a restricted mode.
[0103] A device application 918 may initiate a task call to a shared device application 920 with a request for the device content 922, and the restricted execution service 902 can restrict the device application access to the device content via the shared device application while the restricted execution mode 914 is activated. The device application may also initiate a task call to the operating system 904 to request device content access, and the restricted execution service can restrict the access to the device content based on one or more device application tasks being designated as restricted while the restricted execution mode is activated.
[0104] Alternatively, the device application 918 can initiate a task call to the shared device application 920 with a request for the device content 922, and the request includes a request token that indicates the device application is permitted to access the device content via the shared device application in the shared space 916. The restricted execution service 902 can then allow the device application access to the device content via the shared device application based on the request token while the restricted execution mode is activated. The restricted execution service can also deactivate the restricted execution mode 914 responsive to a PIN code or authentication credential entered on the device lock screen, and return to a normal user mode of the mobile device in which the device application 918 has unrestricted access to the device content 922.
[0105] The restricted execution service 900 implements a mechanism to indicate in which restricted modes a device application can run (e.g., execute) based on a task information field of a device application task. The task information field indicates whether a specific task can be allowed to execute in a shared space when the restricted execution mode is activated. This new field will be a bit mask, which a navigation server will use to compare to the navigation filter mask that MobileUI will give to it when a restricted mode is entered. These are marked per task instead of by application because some first-party device applications have tasks that can be allowed to function in a child share space (e.g., Kid's Corner), but not all of the application functionality is allowed while a restricted execution mode is activated on a device. If a device application is allowed to run in a shared space, the restricted execution service can trace an API task call through the application layer from an originator (e.g., device application) that initiates the task call based on a token that is passed along to a core system component that would not otherwise be able to determine whether the task call was originated from a device application running in the shared space. The token can be utilized to determine if the task call is protected from a restricted execution mode.
[0106] FIG. 10 illustrates example method(s) 1000 of restricted execution modes. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0107] At 1002, a device lock screen is displayed on an integrated display device of a mobile device. For example, the mobile device 800 (FIG. 8 ) displays a device lock screen 804 on the integrated display device 802 of the mobile device. At 1004, the display is transitioned from the device lock screen to display a shared space user interface of a shared space without a PIN code or other authentication credential entered on the device lock screen. For example, an input system of the mobile device 800 receives an input, such as a gesture input or device selectable control input, and the input is effective to transition from displaying the device lock screen 804 to display the shared space user interface 810 of a shared space 916 without a PIN code or other authentication credential entered on the device lock screen.
[0108] At 1006, a restricted execution mode of the mobile device is activated. For example, the restricted execution service 902 at the mobile device 800 activates the restricted execution mode 914 of the mobile device in response to entering the shared space. At 1008, access of a device application to device content is restricted while the restricted execution mode is activated. For example, the restricted execution service 902 at the mobile device 800 restricts access of a device application 918 to the device content 922 while the restricted execution mode 914 is activated.
[0109] At 1010, the restricted execution mode is deactivated responsive to a PIN code or other authentication credential entered on the device lock screen. For example, the restricted execution service 902 at the mobile device 800 deactivates the restricted execution mode responsive to a PIN code or other authentication credential entered on the device lock screen. At 1012, the device returns to a user mode of the mobile device in which the device application has unrestricted access to the device content. For example, the restricted execution service 902 at the mobile device 800 returns to a user mode of the mobile device in which the device application 918 has unrestricted access to the device content 922.
[0110] FIG. 11 illustrates example method(s) 1100 of restricted execution mode. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0111] At 1102, a shared device application that is included in the shared space is allowed access to the device content while the restricted execution mode is activated. For example, the restricted execution service 902 (FIG. 9 ) at the mobile device 800 allows access to the device content 922 to a shared device application 920 that is included in the shared space 916 while the restricted execution mode is activated.
[0112] At 1104, the device application that requests access to the device content via the shared device application is restricted while the restricted execution mode is activated on the device. For example, restricted execution service 902 at the mobile device 800 restricts a device application 918 task call to the shared device application 920 with a request to access the device content 922 while the restricted execution mode is activated on the device.
[0113] At 1106, the device application is allowed access to the device content via the shared device application while the restricted execution mode is activated based on a request token that the device application includes in a task call to the shared device application for the device content. For example, restricted execution service 902 at the mobile device 800 allows access to the device content 922 by the device application 918 via the shared device application while the restricted execution mode is activated based on a request token that the device application includes in a task call to the shared device application for the device content. The request token indicates that the device application is permitted to access the device content via the shared device application in the shared space.
[0114] FIG. 12 illustrates example method(s) 1200 of restricted execution modes. The order in which the method is described is not intended to be construed as a limitation, and any number or combination of the method operations can be combined in any order to implement a method, or an alternate method.
[0115] At 1202, access to the device content is restricted based on device application tasks being designated as restricted while the restricted execution mode is activated, where the device application initiates a task call to access the device content. For example, restricted execution service 902 (FIG. 9 ) at the mobile device 800 restricts access to the device content 922 based on device application tasks being designated as restricted while the restricted execution mode 914 is activated, where a device application 918 initiates task calls to access the device content.
[0116] At 1204, the device application is restricted from a file system of the mobile device while the restricted execution mode is activated. For example, restricted execution service 902 at the mobile device 800 restricts a device application 918 from a file system of the mobile device while the restricted execution mode is activated.
[0117] At 1206, the device application is determined as user-designated to allow the device application access to the device content in a restricted execution mode if the device application is included in the shared space as a shared device application. Alternatively, at 1208, the device application is determined as designed as not to be allowed access to the device content even if the device application is included in the shared space. For example, restricted execution service 902 at the mobile device 800 can determine whether a device application user-designated to allow the device application access to the device content in a restricted execution mode if the device application is included in the shared space as a shared device application. The restricted execution service 902 may also determine that a device application is designed (e.g., programmed) as not to be allowed access to the device content even if the device application is included in the shared space. Additionally, this type of a programmed device application may also be implemented as not even being eligible for user-designation to be included in the shared space.
[0118] Although described herein as a single restricted execution mode, in some examples, a device provides multiple restricted execution modes, such as a first restricted execution mode associated with a child shared space for facilitating sharing a mobile device with a child and a second restricted execution mode associated with a safe driving shared space for facilitating safer driving by a user of a mobile device. These various restricted execution modes may each impose a different set of limitations on the functionality of the device. For example, the child-related execution mode might block access to email data, changes to device settings, or in-app purchases, while the second driving safety restricted execution zone might block graphical user interfaces that could distract a driver from the road.
[0119] From the lock screen displayed on a device, without entering a PIN or other authentication credentials, a user may be able to reach different shared spaces, each of which has a different restricted execution mode associated with it. For example, from the lock screen, a user might enter a first gesture (e.g., a left swipe) to reach a first shared space having a first restricted execution mode and a second different gesture (e.g., a right swipe) to reach a second, different shared space having a second restricted execution mode. In some examples, a shared space associated with a restricted execution mode may be accessed from different entry points than receiving an input (e.g., a gesture input) on the lock screen.
[0120] FIG. 13 illustrates an example system 1300 in which embodiments of private interaction hubs, mobile device safe driving, and restricted execution modes can be implemented. The system 1300 includes an example mobile device 1302, which may be any one or combination of a wired or wireless device, such as a mobile phone, tablet, computing, communication, entertainment, gaming, media playback, and/or other type of device. Any of the devices can be implemented with various components, such as a processing system and memory, as well as any number and combination of differing components as further described with reference to the example device shown in FIG. 17 . As such, the mobile device 1302 may implement techniques previously described in whole in or part, such as the techniques described with reference to the safe driving service 302 and/or the restricted execution service 902.
[0121] The mobile device 1302 includes an integrated display device 1304 on which user interfaces can be displayed, such as a hub user interface 1306 of a hub application 1308. The hub user interface offers a unified interactive view of the hub data 1310 for a single, private interaction hub and the hub application 6013 aggregates disparate types of the hub data 1310 originating from the various member users of the private interaction hub. For example, the hub user interface may provide a single unified access point to shared hub messages, status updates, check-ins, hub calendar events, hub media, hub applications, and other types of hub content. As described above, a private interaction hub (or simply “hub”) is a private network or association of member users who voluntarily elect to privately interact and collaborate with each other in a bi-directional manner. The hub data 1310 includes any shared data or metadata that is used to facilitate the interaction and collaboration between the members of a private interaction hub, and may include shared data for messaging, notes, contact management, documents, tasks, location updates, photos, calendar events, applications (to include collaborative gaming applications), and/or other media content, such as any type of audio, music, video, and/or image data that may be available or accessed from any source.
[0122] The basic functionality of an example private interaction hub is shown as a golf hub displayed in the hub user interface 1306 of the hub application 1308. For example, the hub user interface can include various selectable user interface tiles 1312, such as a members tile that is selectable to initiate a display of the constituent members of the private interaction hub. The user interface tiles 1312 may also include hub chat and/or messages tiles to allow a hub member to participate in shared messaging threads with the other member users of the hub. For example, as shown, the member “Bob” has asked “Anyone up for a round right now?” The user interface tiles 1312 may also include a photo album tile that is selectable to view photos shared by any of the hub members with the hub, and a shared notebook tile from which the hub members can view shared notes. For example, the golf hub may include a shared notes document that compiles the hub members' collective research of new golf equipment. The hub user interface 1306 may also display a shared calendar that allows a member of the hub to view, edit, and post calendar events that will be shared with all of the other hub members. For example, the calendar tile shows an upcoming tee time at St. Andrews on Saturday at 9:00 a.m. for all of the members. When a user selects a group item (e.g., the message from Bob) or tile (e.g., the messaging tile), further details about the selected item or group items related to the selected tile may be displayed by the hub application itself or the hub application may call (e.g., a task call) a different device application 1336 (e.g., a messaging application) to display further details about the item(s).
[0123] When a user selects or otherwise engages with a piece of displayed hub data, such as the golf message from Bob, the hub application may provide additional details or options to the user to permit the user to interact further with the hub data. For example, the hub application may display controls to allow the user to edit or reply to Bob's message. Alternatively or in addition, when a user selects or otherwise engages with a piece of displayed hub data (e.g., Bob's message), the hub application may launch or call (e.g., a task call) another device application to permit the user to further interact with the piece of hub data (e.g., the hub application may call a native messaging application).
[0124] The hub user interface 1306 of the hub application 1308 can also include user-selectable access to third-party applications, such as when an application is “pinned” to, or otherwise shared with a private interaction hub. A pinned third-party application may also utilize the shared hub data, such as shared application preferences or shared application state data. For example, the golf hub shown displayed in the hub user interface 1306 includes a live tile representing a third-party weather application that the members of the hub can quickly access to check the weather forecast at their local golf club, such as when planning an upcoming golf outing. A user of the mobile device 1302 can also customize display aspects of a hub user interface, such as the content of the user interface and how the elements of the hub user interface are arranged. Another example of a hub user interface of the hub application 1308 is a panoramic hub user interface, such as for a family-centric private interaction hub as shown and described in greater detail with reference to FIG. 16 .
[0125] The example system 1300 also includes a hub management service 1314, and a cloud storage and service 1316. The hub management service 1314 manages the formation and maintenance of private interaction hubs 1318. The hub management service can correlate or associate member users of a hub by associating account identifiers 1320 of the members with one or more of the private interaction hubs. The account identifier 1320 of a member user may be associated with an identifier of a private interaction hub 1318 in a data table that the hub management service maintains to correlate the hub members with one or more of the private interaction hubs. The hub management service 1314 may also associate devices that correspond to hub members based on device identifiers. The account identifiers 1320 can include user membership identifiers and/or sign-on credentials, such as an email and password combination, or a username and password combination. The sign-on credentials may be single sign-on (“SSO”) credentials that are utilized for authentication purposes at a number of Web services, including the cloud storage and service 1316.
[0126] The cloud storage and service 1316 can include any type of cloud-based (e.g., network-based) data and messaging services 1322. The messaging services may include any type of email, text (e.g., SMS, MMS), and/or instant messaging services. The data services may include any type of calendar, photo album, file or document sharing, location, mapping, music sharing, video sharing, gaming, contacts management, and/or notebook services, as well as any other type of services that can be used to share stored hub data 1324. The stored hub data can include any form of messages, updates, events, content, media, and information that is maintained for the private interaction hubs 1318, and is accessible from the mobile device 1302, either upon a request from a device and/or upon a data “push” to the device. The cloud storage and service 1316 also maintains stored hub metadata 1326 that includes settings and information pertaining to the private interaction hubs 1318, such as the name of a hub, the background image or photo of the hub, and an association of the hub members.
[0127] Although shown together as data and messaging services 1322, various application data services and various messaging services may be operated on separate devices and/or operated by separate, distinct entities. Additionally, although the hub management service 1314 and the cloud storage and service 1316 are shown as independent services, they may be implemented together as a single service. Further, a server device (or group of server devices) can include implementations of both the hub management service 1314 and the cloud storage and service 1316, representative of a single entity that may be the same server system, company system, domain, and the like.
[0128] The cloud storage and service 1316, and its constituent data and messaging services 1322, interchange the stored hub data 1324 and the stored hub metadata 1326 between the mobile devices that are associated with member users of a private interaction hub 1318. For example, a data and/or messaging service of the cloud storage and service 1316 can receive a copy of hub data 1310 and/or hub metadata 1328 from the mobile device 1302 that is used by a hub member, store this hub data and hub metadata in the cloud storage as the respective stored hub data 1324 and stored hub metadata 1326, and then distribute the stored hub data and stored hub metadata to other mobile devices associated with other member users of the same private interaction hub, as well as to other mobile devices associated with the same hub member. The stored hub metadata 1326 can include membership information pertaining to the member users of a private interaction hub, hub identifiers that correlate a piece of hub data to a particular private interaction hub, user identifiers that correlate a piece of hub data to a particular member user, modification dates, and/or other metadata.
[0129] The cloud storage and service 1316, and its constituent data and messaging services 1322, may utilize single sign-on (“SSO”) credentials for authentication purposes to limit the dissemination of the stored hub data 1324 and the stored hub metadata 1326 to only the authorized devices of hub members. Additionally, any of the devices and services (e.g., implemented as server devices) described herein can communicate via a network 1330, which can be implemented to include a wired and/or a wireless network. The network can also be implemented using any type of network topology and/or communication protocol, and can be represented or otherwise implemented as a combination of two or more networks, to include IP-based networks and/or the Internet. The network may also include mobile operator networks that are managed by a mobile network operator and/or other network operators, such as a communication service provider, mobile phone provider, and/or Internet service provider.
[0130] The mobile device 1302 includes an operating system 1332 of the device, and the operating system includes a hub operating system service 1334 that is implemented to integrate cloud-based services, a hub application 1308, and local device applications 1336 with the operating system to implement aspects of the private interaction hubs 1318. The aspects that may be implemented include hub formation and membership maintenance, synchronizing the hub data 1310 on the mobile device with the stored hub data 1324, and the hub metadata 1328 with the stored hub metadata 1326, with the cloud storage and service 1316, and providing the hub application 1308 and the local device applications 1336 on the mobile device 1302 with access to the hub data 1310 and the hub metadata 1328. For example, the hub operating system service 1334 may directly access the stored hub metadata 1326 at the cloud storage and service 1316.
[0131] The hub operating system service 1334 (or alternatively, the hub application 1308) may also determine and maintain a local copy of the membership associations of member users account identifiers 1320 and identifiers of the private interaction hubs. The hub operating system service 1334 may also synchronize the stored hub data 1324 from the cloud storage and service 1316 with the hub data 1310 at the mobile device 1302, and synchronize the stored hub metadata 1326 from the cloud storage and service with the hub metadata 1328 at the mobile device. The hub operating system service 1334 may also synchronize with the cloud storage and service 1316 (e.g., by sending changes or additions to hub data 1310 and hub metadata 1328 to the cloud storage and service 1316). Such data synchronizations may occur in response to a user launching the hub application.
[0132] The mobile device 1302 includes the device applications 1336 that permit a user of the mobile device to access, create, and/or modify the hub data 1310, private data 1338 of the user, as well as the stored hub data 1324 that is managed by any of the data and messaging services 1322 at the cloud storage and service 1316. Some or all of the device applications 1336 may be implemented as client-side components or modules of any of the data and messaging services 1322, or may be implemented as standalone, native applications (e.g., local device applications) at the mobile device. The device applications 1336 typically each consume and provide access to only a portion or subset of the hub data 1310 and the private data 1338, such as only a single type of hub data and private data (e.g., only messaging data, but not calendar data). The device applications also typically present the consumed hub data to a user in conjunction with the private data 1338. Private data is data or metadata that is not associated with a private interaction hub and that has not been shared with other members of the hub (e.g., data that has not been shared via the cloud storage and service 1316).
[0133] The device applications 1336 at the mobile device 1302 may include a native or third-party messaging application that provides a user with messaging alerts and access to messaging threads. The messaging application provides access to both shared message threads shared with a private interaction hub and private message threads between a user of the mobile device and others who are not members of the hub. The messaging application also allows a user to send a message to all of the hub members without accessing a hub user interface of the hub application. The messaging application may not provide user access to other types of the hub data 1310, other than the hub messages. For example, the messaging application may not provide access to the shared calendar events or shared photo albums of the hub.
[0134] The device applications 1336 may also include a native or third-party calendaring application that provides scheduling alerts and access to a visual calendar. The calendaring application provides user access to both shared calendar events that are shared with hub members, and private calendar events (e.g., Exchange calendar events) that have not been shared with other members of the hub. The calendaring application also allows a user to create and/or share a calendar event to all members of the hub without accessing a hub user interface of the hub application. The application may not provide user access to other types of the hub data 1310, other than the hub calendar events. For example, the calendaring application may not provide access to the shared message threads or shared photo albums of the hub.
[0135] The device applications 1336 may also include a native or third-party media viewing and/or editing application that provides access to photo albums of digital photos or other digital media. The media application provides user access to both shared media files (e.g., photos, videos, and/or music) shared with a private interaction hub, and private media files that have not been shared with other members of the hub. The media application also allows a user to share media files with all members of the hub without accessing a hub user interface of the hub application. The media application may not provide user access to other types of hub data 1310, other than hub media files. For example, the media application may not provide access to the shared message threads or shared calendar events of the hub.
[0136] The hub operating system service 1334 can expose one or more Application Programming Interfaces (“APIs”), application binary interfaces, and/or other types of interfaces 1340 to the hub application 1308 and to the device applications 1336 on the mobile device 1302 to allow these applications to access, generate, and/or modify the hub data 1310 and/or the hub metadata 1328, as described herein. The hub operating system service 1334 can be implemented as an integrated software component or module of the operating system 1332. The hub operating system service can be maintained at the mobile device 1302 as executable instructions that are stored on computer-readable storage media, such as any suitable memory device or electronic data storage as described with reference to the example device shown in FIG. 17 . Additionally, the hub operating system service can be executed with a processing system at the mobile device to implement aspects of private interaction hubs.
[0137] In embodiments, the hub operating system service 1334 can initiate the hub management service 1314 to provision a private interaction hub 1318. A user of the mobile device 1302 can start a private interaction hub 1318 and also invite others to join an existing private interaction hub. For example, the hub user interface 1306 of the hub application 1308 may provide an existing hub member with the option to add a new member to the hub, and the user may identify the prospective member by providing either a mobile device number, or by selecting an existing contact from one of their social networks or other contacts.
[0138] The hub operating system service 1334 can receive the request from an existing member user of the device and, in response, the hub operating system service 1334 and/or the hub management service 1314 communicates an invitation to join the hub as an SMS, MMS, or instant message sent to the prospective member's mobile device that may include a link to a registration site or other registration instructions. The hub operating system service 1334 and/or the hub management service 1314 receives (e.g., via a registration website) an acceptance to the invitation to join the private interaction hub that includes at least an account identifier (such as an SSO credential), and associates the new member with the existing hub at the hub management service 1314. Updated membership information, including the new member's account identifier 1320 may also be propagated to other mobile devices of other members in the private interaction hub from the hub management service 1314. When the new member user joins the hub, he or she may be prompted to download and/or install various applications configured to provide access to the stored hub data 1324 and the stored hub metadata 1326, such as the hub application 1308 and/or the any of the device applications 1336. The hub application 1308 may also be the entry point by which a user creates a new hub and/or modifies the membership of an existing hub.
[0139] A private interaction hub 1318 can be provisioned for any association of people, such as family members, coworkers, friends, neighbors, and any other people that may be associated together in a hub. Additionally, a member user of one private interaction hub may also be a member of multiple hubs, which can be based on a single member sign-on that identifies the member to the hub operating system service 1334 and/or to the hub management service 1314. For example, a person may be a member of a family hub that associates members of the person's family, as well as a member of a neighborhood hub that associates members of the person's neighborhood, and a golf hub that associates the person's friends that often golf together.
[0140] The integration of the hub application 1308 with the operating system 1332 of the mobile device provides that a user of the device can view a message or update on the hub user interface 1306 and in an application user interface of an application that is associated with the message or the update. For example, a hub calendar is integrated with the calendar application (e.g., a device application 1336) on the mobile device 1302, and a calendar update that is displayed in the hub user interface 1306 can be selected by the user to initiate the update being displayed in a calendar user interface of the calendar application. Alternatively, the user may view the calendar user interface and select a calendar event that is associated with a private interaction hub to initiate a display of the hub calendar, which includes the calendar event for the members of the hub. As another example, a hub calendar event can be displayed in a hub user interface, and the device calendar application can access and display the hub calendar event along with any private data calendar events that only the user of the device has access to view in a user interface of the device calendar application. The hub application 1308 and the device application 1336 both acquire the same hub calendar event data (e.g., the same hub data 1310 stored on the mobile device). The two different user interfaces (e.g., a hub user interface and a device application user interface) display the same calendar event data.
[0141] In another example, the hub messages and chat features are integrated with messaging applications (e.g., the device applications 1336) on the mobile device 1302, and an email, text, or instant message that is displayed in the hub user interface 1306 can be selected by the user of the mobile device 1302 to initiate the message being displayed in a messaging application user interface. Alternatively, the user may view a recent message from a member of a private interaction hub in a messaging application user interface, and select the message to initiate a display of the hub messages interface, such as to view the discussion thread associated with the recent message.
[0142] In embodiments, the hub operating system service 1334 at the mobile device 1302 can receive social network updates for the member users of a private interaction hub 1318, such as when two or more of the members of a hub are also “friends” on a public social network site, such as (e.g., FACEBOOK®, TWITTER®, or LINKEDIN®). The social network updates can be pulled from a social network site based on the established association of the account identifiers 1320 of the hub members of a private interaction hub 1318 at the hub management service 1314. The hub operating system service 1334 can then aggregate the social network updates for a particular hub for display in the hub user interface 1306 or on a homepage “live tile” associated with the hub. The hub operating system service 1334 at the mobile device 1302 can also be implemented to coordinate multi-user interactive updates to an event that is managed in a private interaction hub. For example, several members of a hub may participate in a multi-player interactive game, and each successive interactive update from a member of the hub is initiated by the member at a respective associated mobile device.
[0143] FIG. 14 illustrates an example system 1400 in which various embodiments of private interaction hubs, mobile device safe driving, restricted execution modes, and/or family coordination can be implemented. The example system includes a client device 1402, which may be any one or combination of a mobile phone 1404, tablet device 1406, computing device 14013, communication, entertainment, gaming, navigation, and/or other type of portable electronic device. Any of the client devices 1410 can be implemented with various components, such as a processor and/or memory system, as well as any number and combination of differing components as further described with reference to the example device shown in FIG. 12 .
[0144] The example system 1400 includes a device association service 1412 that associates or correlates the client devices 1410 by device identifiers 1414, user identifiers 1416, and/or by any other type of identifiable association. Any of the devices and services can communicate via a network 14113, which can be implemented to include wired and/or wireless networks. The network can also be implemented using any type of network topology and/or communication protocol, and can be represented or otherwise implemented as a combination of two or more networks, to include IP-based networks and/or the Internet. The network may also include mobile operator networks that are managed by mobile operators, such as a communication service provider, cell-phone provider, and/or Internet service provider. A mobile operator can facilitate mobile data and/or voice communication for any type of a wireless device or mobile phone.
[0145] The client devices 1410 can each be associated with a different user, and the users are defined members of a family 1420. The example client device 1402 is representative of the various client devices 1410 in the family. Any of the client devices in the family can include services, such as software applications (e.g., computer-executable instructions), that can be executed by a processor or processor system to implement the embodiments described herein. In this example, the client device 1402 includes a family coordination architecture 1422 that implements features of a family hub; a parental control service 1424 that implements features of a parent dashboard; a family check-in service 1426; a device quiet service 14213 that implements features of quiet time and quiet zone; a safe driving service 1430; and a device sharing service 1432. The client device services are further described with reference to FIG. 15 .
[0146] Additionally, any one or combination of the various client device services may be abstracted for implementation by a network service provider, such as the device association service 1412. For example, the client devices 1410 that are associated in the family 1420 can be interconnected through a central computing device or system (e.g., may be one of the client devices 1410), which may be local to the multiple devices or may be located remotely from the devices. In embodiments, the central computing device may be a cloud service of one or more server computers that are connected to the multiple devices via the network 14113 or other communication link. The interconnection architecture enables functionality across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the client devices may have different physical configurations and capabilities, and the central computing device implements a platform to enable delivery of an experience that is both tailored to a particular device and yet common to all of the devices.
[0147] FIG. 15 further illustrates the various client device services that are described with reference to FIG. 14 . The client device 1402 includes the family coordination architecture 1422, the parental control service 1424, the family check-in service 1426, the device quiet service 14213, the safe driving service 1430, and the device sharing service 1432. In implementations, the device sharing service 1432 can embody the safe driving service 302 described with reference to FIGS. 1-7 and/or embody the restricted execution service 902 described with reference to FIGS. 9-12 , such as to implement a safe driving mode. In embodiments, the family coordination architecture 1422 may generally be implemented as a service, as described herein. Generally, any of the described services may be implemented and/or described in the general context of software, firmware, hardware (e.g., fixed logic circuitry), manual processing, applications, routines, programs, objects, components, data structures, procedures, modules, functions, or any combination thereof. A software implementation represents program code that performs specified tasks when executed by a computer processor. In embodiments, any of the processing, computation, filtering, code execution, etc. can be implemented with distributed computing services and/or devices, such as on a client device, a server device, and/or network-based service.
[0148] In this example of the client device services, the family coordination architecture 1422 includes a family hub manager 1500 that implements, coordinates, and/or manages various family features, such as family calendar 1502, family chat 1504, family shared contacts 1506, family journal and memories 15013, tasks and chores 1510, family keys 1512, and family budget 1514. The parental control service 1424 implements features such as a parent dashboard manager 1516, age appropriate content control 15113, and safe social networking 1520. The device quiet service 14213 implements features such as quiet time 1522 and quiet zone 1524. The various client device services and features are further described throughout the document.
[0149] Any of the client device services can include, be integrated with, or implement any of the other client device services and applications. For example, the family coordination architecture 1422 can include any one or combination of the parental control service 1424, the family check-in service 1426, the device quiet service 14213, the safe driving service 1430, and the device sharing service 1432. In embodiments, the family coordination architecture may be implemented for the coordination of time, messaging, data, activities, and any other shared services. The shared services may be any of the client device services and/or any type of shared services that may be associated with a service and/or multi-system operator (MSO) devices. Further, the parental control service can be implemented to throttle, expand, manage, and/or reallocate data sharing of the client device services.
[0150] Any of the family features and/or applications of the family coordination architecture can be implemented as private, some private and some public, or private with optional user control to share information and data with public third-party services and applications. Similarly, any of the client device services and applications described herein may be private, public, sharable, user-controllable, and/or any combination thereof. In embodiments, the family coordination architecture and/or the family hub manager can be implemented as an overall managing architecture, a collective embodiment of, and/or integration of any of the client device services and/or applications that may be implemented for expandability and instantiated together as the family coordination and/or the family hub architecture. Further, any of the client device services can include, be integrated with, or implement any of the other client device services and applications, and collectively may be embodied as a family hub and/or coordination architecture or service.
[0151] FIG. 16 is an example of a system 1600 showing two different examples of hub user-interfaces 1602, 1604 for a family-orientated hub. The description, layout, orientation, features, and organization of the text, images, photos, graphics, links, data, information, and presentation features shown with reference to the hub user interfaces, as well as with reference to any other user interfaces described herein and/or shown in the figures, are merely examples that may be altered in any aspect for various embodiments and/or implementations of mobile device check-in.
[0152] The hub is a central space for membership-orientated coordination of communications, activities, information, and integration. Designated member relationships can be utilized to define how the data and information is managed, and can be implemented to leverage the social contract, such as between members of a defined familial group in the illustrated example. In one or more implementations, the hub is implemented as a user interface (e.g., via a client device application) for integration and aggregation of the membership-orientated communications, activities, and information. A hub can be implemented as a private, shared space between defined members. The hub contains links to other members' profiles, and based on restriction settings, allows aggregation for visibility of some of other members' data and information within the hub. The hub shares a group calendar which can be viewed and edited, a common text message window, a posting board, a shared photo album, a check-in feature, and any other type of shared information.
[0153] Devices and/or device accounts can be associated within a set of devices or device accounts (e.g., a family phone account, user accounts, a connected set of devices, and so on), and all or a subset of the devices or accounts can communicate with other devices or accounts. The members of a hub can be defined by any number of different classes of people, such as Junior, Teen, Mom, Dad, (or Parent), Grandparent, Nanny, Life-Coach, and so on for the illustrated example of a family. Further, the members of a family can be defined to distinguish a live-in Nanny from a Babysitter, for example.
[0154] Additionally, membership of the hub as well as use of the hub by the members can be controlled by a select collection of users, such as one or two mobile phones by the associated users of the client devices. For example, one of the members in the hub can be the designated control person, such as Mom who runs the household, employer, and so on.
[0155] From a single configuration of the members, the hub can be provisioned, setup, and propagated out, e.g., automatically. The features and configuration of a hub may default to an automatic, easy setup, but any rule, feature, or configuration aspect can be readily modified by a user. Provisioning a hub may be based on billing, e.g., a family or corporate billing plan. However, if a phone device is changed to a different carrier, for example, the phone device can still receive texts related to the hub. Alternatively or in addition, provisioning a hub can be based on email addresses, phone numbers, user account identifiers, or any other identifier.
[0156] A retail person selling a new phone package, for instance, can easily identify the members each to their new phone devices and initiate the hub being instantiated. From a consumer perspective, it just works and members can walk out of the store all set up. All of the data and information can be shared with a single selection, and thus the members do not have to share each item (e.g., a grocery list, photos, calendar, etc.) individually and separately.
[0157] The hub user interface may act as a shared space that is customizable and provides for user-generated and shared content. Some information can be shared, while other information is not. For example, Mom's complete Christmas list is not viewable by the other family members, but Dad and Kids can add to the list (and only view their contribution). Hub setup may be performed “a la carte,” meaning only the features that members want displayed on the hub wall can be selected. For example, Mom wants to see the shopping list, whereas Dad does not shop and so wants to avoid having the list displayed on his device, yet he could still access the shopping list to add items when desired.
[0158] The hub user interface integrates functions, calendar functionality, event and/or data summaries (i.e., on the “wall”), as well as content that is shared between the members of the hub (e.g., lists, documents, etc.). For example, the hub user interface may include a “family check-in” or “check-in” option. The hub user interface may also include a chat section where location check-ins messaged are displayed along with other messages interchanged between the members of the hub. The hub “wall” is representative of an area via which members of the group may add to as desired, like a lunchroom bulletin board, family refrigerator, and so on. In implementations, the information can be aggregated in pillars or columns and shown on the hub wall as illustrated. The hub wall can also represent an interrelation between any of the information and data that appears on the wall and its placement in time. The hub settings provide that a user can control which functions are integrated and displayed within the hub, such as on the wall.
[0159] The hub information may also be context relevant to the members of the hub, and the calendar includes shared hub events. Calendar updates can be posted as notice events on the wall, and a user can look at the wall to see upcoming hub events, or the events that pertain to one or more other members of the hub. Messaging may also be performed that is private among the members of the hub. A member can instant text (or other communication) to all other members in the hub. Texting—such as for a work meeting—can divide each members' display on their respective devices into individual screens for each member.
[0160] The hub may also be extensible, and may link to a hard drive on a home computer, or sync to just one of the other devices, the manager, or cloud control (e.g., from a network-based service). The hub may also be extensible to third parties that add a note on the hub wall, such as implemented with application program interfaces (APIs) for functions to post data to the hub. A third-party application, however, would not have access to the context of the hub wall, such as to obtain or display hub data. The private information and hub data could be encrypted and only decrypted by the phone devices that are associated with the hub.
[0161] Thus, the hub supported by a hub coordination architecture may be thought of as a central space for coordination of communications, activities, information, and integration of members of the hub. Hubs may be defined to support a variety of different membership, such as for family members, coworkers, friends, acquaintances, fan clubs, and so forth. Therefore, although examples are discussed that relate to a family in the following discussion it should be readily apparent that membership in the hub may be defined in a variety of other ways without departing from the spirit and scope thereof. Accordingly, the hub coordination architecture may be used to support a variety of different functionality. An example of this functionality is described herein as hub safe driving service, and further aspects of private interaction hubs are also described herein.
[0162] FIG. 17 illustrates an example system 1700 that includes an example device 1702, which can implement embodiments of mobile device safe driving. The example device 1702 can be implemented as any of the devices, services, and/or servers described with reference to the previous FIGS. 1-16 , such as any type of client or mobile device, mobile phone, tablet, computing, communication, entertainment, gaming, media playback, and/or other type of device. For example, the mobile device 100 shown in FIGS. 1 and 3 , and the mobile device 800 shown in FIGS. 8 and 9 , may be implemented as the example device 1702.
[0163] The device 1702 includes communication devices 1704 that enable wired and/or wireless communication of device data 1706, such as media content and the shared messages, updates, and events data at the device. The media content can include any type of audio, video, and/or image data. The communication devices 1704 can also include transceivers for cellular phone communication and/or for network data communication.
[0164] The device 1702 also includes input/output (I/O) interfaces 17013, such as data network interfaces that provide connection and/or communication links between the device, data networks, and other devices. The I/O interfaces can be used to couple the device to any type of components, peripherals, and/or accessory devices. The I/O interfaces also include data input ports via which any type of data, media content, and/or inputs can be received, such as user inputs to the device, as well as any type of audio, video, and/or image data received from any content and/or data source.
[0165] The I/O interfaces 17013 also support natural user interface (NUI) inputs to the device 1702, such as any interface technology that enables a user to interact with a device in a “natural” manner, free from artificial constraints imposed by input devices such as mice, keyboards, remote controls, and the like. Examples of natural user interface inputs may rely on speech recognition, touch and stylus recognition, gesture recognition on-screen and motion gesture recognition proximate the device, head, eye, and environment recognition and tracking, augmented reality and virtual reality systems, and any other type of audible, vision, touch, gesture, and/or machine intelligence that may determine user input intentions.
[0166] The device 1702 includes a processing system 1710 that may be implemented at least partially in hardware, such as with any type of microprocessors, controllers, and the like that process executable instructions. The processing system can include components of an integrated circuit, programmable logic device, a logic device formed using one or more semiconductors, and other implementations in silicon and/or hardware, such as a processor and memory system implemented as a system-on-chip (SoC). Alternatively or in addition, the device can be implemented with any one or combination of software, hardware, firmware, or fixed logic circuitry that may be implemented with processing and control circuits. The device 1702 may further include any type of a system bus or other data and command transfer system that couples the various components within the device. A system bus can include any one or combination of different bus structures and architectures, as well as control and data lines.
[0167] The device 1702 also includes computer-readable storage media 1712, such as data storage devices that can be accessed by a computing device, and that provide persistent storage of data and executable instructions (e.g., software applications, programs, functions, and the like). Examples of computer-readable storage media include volatile memory and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data storage that maintains data for computing device access. The computer-readable storage media can include various implementations of random access memory (RAM), read-only memory (ROM), flash memory, and other types of storage media in various memory device configurations.
[0168] Generally, computer-readable storage media is representative of media and/or devices that enable persistent and/or non-transitory storage of data in contrast to mere signal transmission, carrier waves, or signals per se. A computer-readable signal media may refer to a signal-bearing medium that transmits instructions, such as via a network. The signal media can embody computer-readable instructions as data in a modulated data signal, such as carrier waves or other transport mechanism.
[0169] The computer-readable storage media 1712 provides storage of the device data 1706 and various device applications 1714, such as an operating system that is maintained as a software application with the computer-readable storage media and executed by the processing system 1710. In this example, the device applications also include a device share service 1716 that implements embodiments of mobile device safe driving, such as when the example device 1702 is implemented as the mobile device 100 shown in FIG. 1 . An example of the safe driving service 1716 is the safe driving service 302 that is integrated with the operating system 304 at the mobile device 100, as described with reference to FIG. 3 .
[0170] The device applications 1714 can also include any of the services and applications 17113 that implement embodiments of mobile device safe driving. The example device 1702 also includes a family coordination architecture 1720, which may be implemented in the general context of software, firmware, hardware (e.g., fixed logic circuitry), or any combination thereof to support embodiments of mobile device safe driving and/or mobile devices family coordination. The device 1702 can also include a positioning system 1722, such as a GPS transceiver, or similar positioning system components, that can be utilized to determine a global or navigational position of the device.
[0171] The device 1702 also includes an audio and/or video system 1724 that generates audio data for an audio device 1726 and/or generates display data for a display device 17213. The audio device and/or the display device include any devices that process, display, and/or otherwise render audio, video, display, and/or image data. In implementations, the audio device and/or the display device are integrated components of the example device 1702. Alternatively, the audio device and/or the display device are external, peripheral components to the example device.
[0172] In embodiments, at least part of the techniques described for mobile device safe driving may be implemented in a distributed system, such as over a “cloud” 1730 in a platform 1732. The cloud 1730 includes and/or is representative of the platform 1732 for services 1734 and/or resources 1736. For example, the services 1734 may include the cloud storage and service 306, and any of the data services 3013 as described with reference to FIG. 3 . Additionally, the resources 1736 may include the driving reports 310 as described with reference to FIG. 3 .
[0173] The platform 1732 abstracts underlying functionality of hardware, such as server devices (e.g., included in the services 1734) and/or software resources (e.g., included as the resources 1736), and connects the example device 1702 with other devices, servers, etc. The resources 1736 may also include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the example device 1702. Additionally, the services 1734 and/or the resources 1736 may facilitate subscriber network services, such as over the Internet, a cellular network, or Wi-Fi network. The platform 1732 may also serve to abstract and scale resources to service a demand for the resources 1736 that are implemented via the platform, such as in an interconnected device embodiment with functionality distributed throughout the system 1700. For example, the functionality may be implemented in part at the example device 1702 as well as via the platform 1732 that abstracts the functionality of the cloud 1730.
[0174] Although embodiments of mobile device safe driving have been described in language specific to features and/or methods, the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of mobile device safe driving.
Claims
The invention claimed is:
1. A mobile device, comprising:
a display device; and
a processing system to implement a safe driving service that is configured to perform operations comprising:
determining whether a user of the mobile device is driving a vehicle or is a passenger in the vehicle;
responsive to the determining that the user is driving the vehicle, activating a safe driving mode of the mobile device to cause the display device to transition to a driving mode lock screen without entry of an authentication credential; and
disabling features of the mobile device while the safe driving mode is activated.
2. A mobile device as recited in claim 1, wherein the safe driving service is configured to register safe driving events and unsafe driving events associated with use of the mobile device by a user of the mobile device driving.
3. A mobile device as recited in claim 2, wherein the safe driving service is configured to aggregate the safe driving events and the unsafe driving events to generate a safe driving report that indicates one of safe driving or unsafe driving.
4. A mobile device as recited in claim 1, further comprising:
a communication interface for communicating with one or more other devices that are associated with the mobile device; and
wherein the safe driving service is configured to communicate a safe driving report to an associated device of the mobile device.
5. A mobile device as recited in claim 4, wherein the safe driving service is configured to generate the safe driving report to indicate that the features of the mobile device were enabled by user override of a safe driving mode while the mobile device was moving in a vehicle.
6. A mobile device as recited in claim 1, further comprising:
an integrated digital camera of the mobile device that generates a digital image; and
wherein the safe driving service is configured to determine whether the user of the mobile device is driving or is a passenger in the vehicle based on the digital image.
7. A mobile device as recited in claim 1, further comprising:
an audio sensor configured to detect audio in the vehicle; and
wherein the safe driving service is configured to generate an unsafe driving notification to indicate that the audio in the vehicle is a driver distraction.
8. A mobile device as recited in claim 1, wherein the safe driving service is configured to:
determine that the mobile device has stopped in a vehicle at an unknown location;
determine a position of the mobile device based on location data; and
generate an unsafe driving notification to indicate that the vehicle has stopped at the unknown location.
9. A method, comprising:
displaying a device lock screen on an integrated display device of a mobile device;
receiving user input entered on the device lock screen without receiving an authentication credential;
transitioning from displaying the device lock screen to displaying a driving mode lock screen;
activating a safe driving mode of the mobile device; and
disabling features of the mobile device while the safe driving mode is activated.
10. A method as recited in claim 9, further comprising:
registering safe driving events and unsafe driving events associated with use of the mobile device by a user of the mobile device driving.
11. A method as recited in claim 10, further comprising:
aggregating the safe driving events and the unsafe driving events; and
generating a safe driving report that indicates at least one of safe driving or unsafe driving.
12. A method as recited in claim 11, further comprising:
communicating the safe driving report to an associated device of the mobile device.
13. A method as recited in claim 9, further comprising:
generating a safe driving report that indicates the features of the mobile device were enabled by user override of a safe driving mode while the mobile device was moving in a vehicle.
14. A method as recited in claim 13, further comprising:
determining that a user of the mobile device is driving the vehicle based on sensor data from a driver determination sensor;
generating an unsafe driving notification to indicate that the user is using the mobile device while driving the vehicle; and
communicating the safe driving notification to one or more other devices that are associated with the mobile device.
15. A method as recited in claim 9, further comprising:
determining that the mobile device has stopped in a vehicle at an unknown location; and
generating an unsafe driving notification to indicate that the vehicle has stopped at the unknown location.
16. A method as recited in claim 9, further comprising:
detecting an audio level in a vehicle; and
generating an unsafe driving notification to indicate that the audio level in the vehicle is a driver distraction.
17. A method as recited in claim 9, further comprising:
determining that a user of the mobile device is a passenger in a vehicle; and
enabling the features of the mobile device responsive to the determination that the user of the device is the passenger in the vehicle.
18. A method, comprising:
displaying a device lock screen on an integrated display device of a mobile device;
determining whether a user of the mobile device is driving a vehicle or is a passenger in the vehicle;
responsive to the determining that the user is driving the vehicle, activating a safe driving mode of the mobile device to cause the display device to transition to a driving mode lock screen without entry of an authentication credential; and
disabling features of the mobile device while the safe driving mode is activated.
19. A method as recited in claim 18, further comprising:
determining that the features of the mobile device were enabled by user override of a safe driving mode while the mobile device was moving in a vehicle; and
generating a safe driving report to indicate that the features of the mobile device were enabled by user override of a safe driving mode while the mobile device was moving in a vehicle.
20. A method as recited in claim 18, further comprising:
determining that the mobile device has stopped in a vehicle at an unknown location;
determining a position of the mobile device based on location data; and
generating an unsafe driving notification to indicate that the vehicle has stopped at the unknown location.
Patent Citations (214)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5883598(A) | 1999-03-01 | Parl et al. | Applicant |
| US6286001(B1) | 2001-09-01 | Walker et al. | Applicant |
| US6339826(B2) | 2002-01-01 | Hayes et al. | Applicant |
| US6405033(B1) | 2002-06-01 | Kennedy et al. | Applicant |
| US6446069(B1) | 2002-09-01 | Yaung et al. | Applicant |
| US6504480(B1) | 2003-01-01 | Magnuson et al. | Applicant |
| US6546002(B1) | 2003-04-01 | Kim | Applicant |
| US6549768(B1) | 2003-04-01 | Fraccaroli | Applicant |
| US6564149(B2) | 2003-05-01 | Lai | Applicant |
| US6650189(B1) | 2003-11-01 | Romao | Applicant |
| US6662023(B1) | 2003-12-01 | Helle | Applicant |
| US6678508(B1) | 2004-01-01 | Koilpillai et al. | Applicant |
| US6799047(B1) | 2004-09-01 | Bahl et al. | Applicant |
| US6847892(B2) | 2005-01-01 | Zhou et al. | Applicant |
| US6920455(B1) | 2005-07-01 | Weschler | Applicant |
| US6941134(B2) | 2005-09-01 | White | Applicant |
| US7058659(B2) | 2006-06-01 | Ryu | Applicant |
| US7076797(B2) | 2006-07-01 | Loveland | Applicant |
| US7096030(B2) | 2006-08-01 | Huomo | Applicant |
| US7142848(B2) | 2006-11-01 | Owen et al. | Applicant |
| US7161914(B2) | 2007-01-01 | Shoaib et al. | Applicant |
| US7171557(B2) | 2007-01-01 | Kallahalla et al. | Applicant |
| US7212613(B2) | 2007-05-01 | Kim et al. | Applicant |
| US7222360(B1) | 2007-05-01 | Miller | Applicant |
| US7272388(B2) | 2007-09-01 | Andrew et al. | Applicant |
| US7274925(B2) | 2007-09-01 | Chaar et al. | Applicant |
| US7302272(B2) | 2007-11-01 | Ackley | Applicant |
| US7308255(B2) | 2007-12-01 | Loveland | Applicant |
| US7321774(B1) | 2008-01-01 | Lau et al. | Applicant |
| US7346921(B2) | 2008-03-01 | Murren et al. | Applicant |
| US7359713(B1) | 2008-04-01 | Tiwari | Applicant |
| US7366798(B2) | 2008-04-01 | Nordstrom et al. | Applicant |
| US7408506(B2) | 2008-08-01 | Miller | Applicant |
| US7471929(B2) | 2008-12-01 | Fujioka et al. | Applicant |
| US7530099(B2) | 2009-05-01 | Flurry et al. | Applicant |
| US7634455(B1) | 2009-12-01 | Keene et al. | Applicant |
| US7668830(B2) | 2010-02-01 | Hakala | Applicant |
| US7680882(B2) | 2010-03-01 | Tiu, Jr. et al. | Applicant |
| US7714778(B2) | 2010-05-01 | Dupray | Applicant |
| US7796944(B2) | 2010-09-01 | Eaton et al. | Applicant |
| US7809350(B2) | 2010-10-01 | Buckley et al. | Applicant |
| US7869792(B1) | 2011-01-01 | Zhou et al. | Applicant |
| US7898428(B2) | 2011-03-01 | Dietz et al. | Applicant |
| US7958562(B2) | 2011-06-01 | Gaucas | Applicant |
| US7961651(B2) | 2011-06-01 | Kim et al. | Applicant |
| US8046839(B2) | 2011-10-01 | Lo | Applicant |
| US8244272(B2) | 2012-08-01 | Morgan et al. | Applicant |
| US8275352(B2) | 2012-09-01 | Forstall et al. | Applicant |
| US8311730(B2) | 2012-11-01 | Neff | Applicant |
| US8355751(B2) | 2013-01-01 | Dietz et al. | Examiner |
| US8385039(B2) | 2013-02-01 | Rothkopf | Applicant |
| US8437779(B2) | 2013-05-01 | Phukan | Applicant |
| US8549657(B2) | 2013-10-01 | Karlson et al. | Applicant |
| US8657743(B2) | 2014-02-01 | Rietzel et al. | Applicant |
| US8706172(B2) | 2014-04-01 | Priyantha et al. | Applicant |
| US2001/0005681(A1) | 2001-06-01 | Kim | Applicant |
| US2002/0044149(A1) | 2002-04-01 | McCarthy et al. | Applicant |
| US2003/0003907(A1) | 2003-01-01 | Lai et al. | Applicant |
| US2003/0139192(A1) | 2003-07-01 | Chmaytelli et al. | Applicant |
| US2003/0187803(A1) | 2003-10-01 | Pitt | Applicant |
| US2004/0015940(A1) | 2004-01-01 | Heisey et al. | Applicant |
| US2004/0039909(A1) | 2004-02-01 | Cheng | Applicant |
| US2004/0192352(A1) | 2004-09-01 | Vallstrom et al. | Applicant |
| US2004/0203576(A1) | 2004-10-01 | Droste et al. | Applicant |
| US2005/0037775(A1) | 2005-02-01 | Moeglein et al. | Applicant |
| US2005/0070276(A1) | 2005-03-01 | McGarry | Applicant |
| US2005/0107114(A1) | 2005-05-01 | Ocock et al. | Applicant |
| US2005/0138110(A1) | 2005-06-01 | Redlich et al. | Applicant |
| US2005/0143171(A1) | 2005-06-01 | Loose | Applicant |
| US2005/0210104(A1) | 2005-09-01 | Torvinen | Applicant |
| US2006/0053389(A1) | 2006-03-01 | Michelman | Applicant |
| US2006/0099969(A1) | 2006-05-01 | Staton et al. | Applicant |
| US2006/0246872(A1) | 2006-11-01 | Tarkkala | Applicant |
| US2006/0253570(A1) | 2006-11-01 | Biswas et al. | Applicant |
| US2006/0256005(A1) | 2006-11-01 | Thandu et al. | Applicant |
| US2006/0271797(A1) | 2006-11-01 | Ginggen et al. | Applicant |
| US2007/0028176(A1) | 2007-02-01 | Perdomo et al. | Applicant |
| US2007/0032225(A1) | 2007-02-01 | Konicek et al. | Applicant |
| US2007/0042790(A1) | 2007-02-01 | Mohi et al. | Applicant |
| US2007/0046423(A1) | 2007-03-01 | Baucom | Applicant |
| US2007/0067655(A1) | 2007-03-01 | Shuster | Applicant |
| US2007/0072616(A1) | 2007-03-01 | Irani | Applicant |
| US2007/0091037(A1) | 2007-04-01 | Lee | Applicant |
| US2007/0111726(A1) | 2007-05-01 | Lanbert et al. | Applicant |
| US2007/0150826(A1) | 2007-06-01 | Anzures et al. | Applicant |
| US2007/0150842(A1) | 2007-06-01 | Chaudhri et al. | Applicant |
| US2007/0180509(A1) | 2007-08-01 | Swartz et al. | Applicant |
| US2007/0218938(A1) | 2007-09-01 | Carter | Applicant |
| US2007/0245398(A1) | 2007-10-01 | Roden | Applicant |
| US2007/0264981(A1) | 2007-11-01 | Miller | Applicant |
| US2008/0014964(A1) | 2008-01-01 | Sudit et al. | Applicant |
| US2008/0020803(A1) | 2008-01-01 | Rios et al. | Applicant |
| US2008/0032703(A1) | 2008-02-01 | Krumm et al. | Applicant |
| US2008/0051079(A1) | 2008-02-01 | Forsgren | Applicant |
| US2008/0080688(A1) | 2008-04-01 | Burgan et al. | Applicant |
| US2008/0082693(A1) | 2008-04-01 | Meijer et al. | Applicant |
| US2008/0101658(A1) | 2008-05-01 | Ahern et al. | Applicant |
| US2008/0111698(A1) | 2008-05-01 | Atherton | Applicant |
| US2008/0154780(A1) | 2008-06-01 | Soukup et al. | Applicant |
| US2008/0254767(A1) | 2008-10-01 | Jin | Applicant |
| US2008/0268870(A1) | 2008-10-01 | Houri | Applicant |
| US2008/0305808(A1) | 2008-12-01 | Chan et al. | Applicant |
| US2008/0318595(A1) | 2008-12-01 | Rofougaran | Applicant |
| US2009/0005061(A1) | 2009-01-01 | Ward et al. | Applicant |
| US2009/0005080(A1) | 2009-01-01 | Forstall et al. | Applicant |
| US2009/0006566(A1) | 2009-01-01 | Veeramachaneni et al. | Applicant |
| US2009/0089886(A1) | 2009-04-01 | Cheng et al. | Applicant |
| US2009/0093688(A1) | 2009-04-01 | Mathur | Applicant |
| US2009/0116703(A1) | 2009-05-01 | Schultz | Applicant |
| US2009/0119590(A1) | 2009-05-01 | Kondziela et al. | Applicant |
| US2009/0157560(A1) | 2009-06-01 | Carter et al. | Applicant |
| US2009/0158389(A1) | 2009-06-01 | Waltenberg et al. | Applicant |
| US2009/0170532(A1) | 2009-07-01 | Lee et al. | Applicant |
| US2009/0201896(A1) | 2009-08-01 | Davis et al. | Applicant |
| US2009/0224931(A1) | 2009-09-01 | Dietz et al. | Examiner |
| US2009/0265794(A1) | 2009-10-01 | Apelqvist | Applicant |
| US2009/0278738(A1) | 2009-11-01 | Gopinath | Applicant |
| US2009/0282473(A1) | 2009-11-01 | Karlson et al. | Applicant |
| US2010/0020035(A1) | 2010-01-01 | Ryu et al. | Applicant |
| US2010/0056124(A1) | 2010-03-01 | Keating et al. | Applicant |
| US2010/0066821(A1) | 2010-03-01 | Rosener et al. | Applicant |
| US2010/0074450(A1) | 2010-03-01 | Liao | Applicant |
| US2010/0115610(A1) | 2010-05-01 | Tredoux et al. | Applicant |
| US2010/0134310(A1) | 2010-06-01 | Zheng et al. | Applicant |
| US2010/0167714(A1) | 2010-07-01 | Howarter et al. | Applicant |
| US2010/0210301(A1) | 2010-08-01 | Dietz et al. | Examiner |
| US2010/0216509(A1) | 2010-08-01 | Riemer et al. | Applicant |
| US2010/0253503(A1) | 2010-10-01 | Juang | Applicant |
| US2010/0255856(A1) | 2010-10-01 | Kansal et al. | Applicant |
| US2010/0268779(A1) | 2010-10-01 | Rao | Applicant |
| US2010/0285815(A1) | 2010-11-01 | Treu et al. | Applicant |
| US2010/0302028(A1) | 2010-12-01 | Desai et al. | Applicant |
| US2010/0306832(A1) | 2010-12-01 | Mu et al. | Applicant |
| US2010/0311336(A1) | 2010-12-01 | Huotari et al. | Applicant |
| US2010/0313050(A1) | 2010-12-01 | Harrat et al. | Applicant |
| US2010/0321155(A1) | 2010-12-01 | Ballard | Applicant |
| US2010/0324819(A1) | 2010-12-01 | Nurminen et al. | Applicant |
| US2011/0010340(A1) | 2011-01-01 | Hung et al. | Applicant |
| US2011/0021213(A1) | 2011-01-01 | Carr | Applicant |
| US2011/0021234(A1) | 2011-01-01 | Tibbitts et al. | Applicant |
| US2011/0063098(A1) | 2011-03-01 | Fischer et al. | Applicant |
| US2011/0065419(A1) | 2011-03-01 | Book et al. | Applicant |
| US2011/0070829(A1) | 2011-03-01 | Griffin et al. | Applicant |
| US2011/0093161(A1) | 2011-04-01 | Zhou et al. | Applicant |
| US2011/0111728(A1) | 2011-05-01 | Ferguson et al. | Applicant |
| US2011/0167344(A1) | 2011-07-01 | Pan | Applicant |
| US2011/0169654(A1) | 2011-07-01 | Ketari | Applicant |
| US2011/0171958(A1) | 2011-07-01 | Hua et al. | Applicant |
| US2011/0197160(A1) | 2011-08-01 | Kim et al. | Applicant |
| US2011/0215903(A1) | 2011-09-01 | Yang et al. | Applicant |
| US2011/0215952(A1) | 2011-09-01 | Aria et al. | Applicant |
| US2011/0237221(A1) | 2011-09-01 | Prakash et al. | Applicant |
| US2011/0241827(A1) | 2011-10-01 | Varoglu | Applicant |
| US2011/0244837(A1) | 2011-10-01 | Murata et al. | Applicant |
| US2011/0247045(A1) | 2011-10-01 | Rajagopal et al. | Applicant |
| US2011/0250840(A1) | 2011-10-01 | Lee et al. | Applicant |
| US2011/0254792(A1) | 2011-10-01 | Waters et al. | Applicant |
| US2011/0264246(A1) | 2011-10-01 | Pantoja et al. | Applicant |
| US2011/0267171(A1) | 2011-11-01 | Li et al. | Applicant |
| US2011/0275321(A1) | 2011-11-01 | Zhou et al. | Applicant |
| US2011/0276901(A1) | 2011-11-01 | Zambetti et al. | Applicant |
| US2011/0283185(A1) | 2011-11-01 | Obasanjo et al. | Applicant |
| US2011/0299422(A1) | 2011-12-01 | Kim et al. | Applicant |
| US2011/0307166(A1) | 2011-12-01 | Hiestermann et al. | Applicant |
| US2011/0319051(A1) | 2011-12-01 | Reitnour | Applicant |
| US2011/0319094(A1) | 2011-12-01 | Usui et al. | Applicant |
| US2012/0046020(A1) | 2012-02-01 | Tomasini | Applicant |
| US2012/0084691(A1) | 2012-04-01 | Yun | Applicant |
| US2012/0084737(A1) | 2012-04-01 | Gimpl et al. | Applicant |
| US2012/0089217(A1) | 2012-04-01 | Mews et al. | Examiner |
| US2012/0098768(A1) | 2012-04-01 | Bendewald et al. | Applicant |
| US2012/0100895(A1) | 2012-04-01 | Priyantha et al. | Applicant |
| US2012/0115512(A1) | 2012-05-01 | Grainger et al. | Applicant |
| US2012/0144468(A1) | 2012-06-01 | Pratt et al. | Applicant |
| US2012/0234058(A1) | 2012-09-01 | Neil et al. | Applicant |
| US2012/0242906(A1) | 2012-09-01 | Shintani et al. | Applicant |
| US2012/0244883(A1) | 2012-09-01 | Tibbitts et al. | Applicant |
| US2012/0268249(A1) | 2012-10-01 | Kansal et al. | Applicant |
| US2012/0282887(A1) | 2012-11-01 | Khoo et al. | Applicant |
| US2013/0023246(A9) | 2013-01-01 | Ellingham et al. | Applicant |
| US2013/0031601(A1) | 2013-01-01 | Bott | Applicant |
| US2013/0036211(A1) | 2013-02-01 | Messer et al. | Applicant |
| US2013/0040629(A1) | 2013-02-01 | Sprigg et al. | Applicant |
| US2013/0040711(A1) | 2013-02-01 | Kim et al. | Applicant |
| US2013/0072172(A1) | 2013-03-01 | Chang et al. | Examiner |
| US2013/0084847(A1) | 2013-04-01 | Tibbitts et al. | Examiner |
| US2013/0093707(A1) | 2013-04-01 | Park et al. | Examiner |
| US2013/0225151(A1) | 2013-08-01 | King | Applicant |
| US2013/0225152(A1) | 2013-08-01 | Matthews, III | Applicant |
| US2013/0227431(A1) | 2013-08-01 | Vasudevan | Applicant |
| US2013/0295872(A1) | 2013-11-01 | Guday et al. | Examiner |
| US2013/0295913(A1) | 2013-11-01 | Matthews | Applicant |
| US2013/0298037(A1) | 2013-11-01 | Matthews | Applicant |
| US2013/0305319(A1) | 2013-11-01 | Matthews | Applicant |
| US2013/0305354(A1) | 2013-11-01 | King et al. | Applicant |
| CN1984402 | 2007-06-01 | Applicant | |
| CN101112072 | 2008-01-01 | Applicant | |
| CN101778165 | 2010-07-01 | Applicant | |
| CN101828162 | 2010-09-01 | Applicant | |
| EP2169946 | 2010-03-01 | Applicant | |
| EP2293016 | 2011-03-01 | Applicant | |
| EP2469442 | 2012-06-01 | Applicant | |
| JP7203015 | 1995-08-01 | Applicant | |
| JP2002530783 | 2002-09-01 | Applicant | |
| JP2003032353 | 2003-01-01 | Applicant | |
| KR20050037613 | 2005-04-01 | Applicant | |
| KR20100083396 | 2010-07-01 | Applicant | |
| KR20110093528 | 2011-08-01 | Applicant | |
| WO-2006088273 | 2006-08-01 | Applicant | |
| WO-2006099535 | 2006-09-01 | Applicant | |
| WO-2007130123 | 2007-11-01 | Applicant | |
| WO-2009105666 | 2009-08-01 | Applicant | |
| WO-2011135359 | 2011-11-01 | Applicant | |
| WO-2013061156 | 2013-05-01 | Applicant |
Non-Patent Literature (153)
- “Welcome to Sprint Drive First”, Retrieved at <<https://drivefirst.sprint.com/welcome.htm>> on Nov. 20, 2013, 2 pages.Applicant
- Samberg, David “Stay Focused While Driving”, Retrieved from <<http://www.verizonwireless.com/news/2012/09/safely-do-driving-app.html>> on Nov. 20, 2013, (Sep. 13, 2012), 5 pages.Applicant
- “Mobile Task Tracker Screen Shots”, Retrieved from <http://www.mobiletasktrackercom/Screen%20Shots.html>, (Jul. 13, 2011), 4 Pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2012/071545, (Mar. 28, 2013), 9 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2012/071559, (Mar. 28, 2013), 10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2012/071555, (Apr. 25, 2013), 9 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2012/071546, (Apr. 29, 2013), 10 pages.Applicant
- Cui, Yanqing “Facilitating Consumption of Online Social Networking Services on Mobile Devices”, Proceedings of the 13th international conference on Ubiquitious Computing, (Sep. 17, 2011), 4 Pages.Applicant
- Niino, Junichi “There was free enterprise microblogging, Japanese were developed “youRoom!” Free plan upgrade just mutter”, Retrieved from <http://www.publickey1.jp/blog/10/youroom.html>, (Dec. 21, 2010), 4 Pages.Applicant
- “International Search Report”, Mailed Date: Mar. 28, 2013, Application No. PCT/US2012/071545, Filed date: Dec. 23, 2012, pp. 9.Applicant
- “EP Search Report”, EP Application No. 09747072.8, Jan. 17, 2003, 5 Pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/194,213, Sep. 20, 2011, 11 Pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/417,752, Jul. 17, 2013, 18 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/417,752, Sep. 13, 2012, 18 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/912,456, Jan. 9, 2013, 21 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/912,456, Sep. 6, 2013, 22 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 13/090,474, Nov. 21, 2013, 12 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 13/222,538, May 28, 2013, 43 pages.Applicant
- “Foreign Office Action”, CN Application No. 200980128048.8, May 6, 2013, 7 Pages.Applicant
- “Foreign Office Action”, CN Application No. 200980128048.8, Dec. 2, 2013, 7 pages.Applicant
- “Foreign Office Action”, CN Application No. 200980128048.8, Dec. 19, 2012, 11 Pages.Applicant
- “Foreign Office Action”, CN Application No. 201110317851.5, Dec. 4, 2013, 14 pages.Applicant
- “Ignite Where & Launch Pad”, O'Reilly, Where 2.0 Conference 2008, retrieved from <http://en.oreilly.com/where2008/public/schedule/detail/2572> on Feb. 5, 2009,May 2008, 4 pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2013/050963, Nov. 8, 2013, 14 pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2011/049614, Mar. 26, 2012, 7 pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2009/039509, Nov. 18, 2009, 8 Pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2012/071557, Mar. 28, 2013, 9 pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2012/071562, Apr. 24, 2013, 9 pages.Applicant
- “International Search Report and Written Opinion”, Application No. PCT/US2012/034598, Oct. 12, 2012, 9 pages.Applicant
- “iPad Parental Control (restricting app access)”, iPad Reviews, Jailbreak Guides; last retrieved from http://ipaded.net/ipad/parental-control/ on Feb. 29, 2012, 5 pages.Applicant
- “No Tech Panacea for Tech-Distracted Driving”, http://mobile.slashdot.org/story/12/06/11/0556231/no-tech-panacea-for . . . , Dec. 6, 2011, 30 Pages.Applicant
- “Non Final Office Action”, U.S. Appl. No. 12/417,752, Jun. 28, 2011, 14 pages.Applicant
- “Non Final Office Action”, U.S. Appl. No. 13/222,538, Feb. 14, 2013, 33 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/194,213, Mar. 17, 2011, 11 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/417,752, Feb. 25, 2014, 22 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/417,752, Oct. 29, 2013, 16 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/417,752, May 24, 2013, 17 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/897,586, May 8, 2014, 12 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/912,456, May 4, 2012, 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/912,456, May 29, 2013, 20 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/912,456, Sep. 11, 2012, 15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/090,474, Apr. 26, 2013, 11 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/222,538, Oct. 11, 2013, 38 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/328,312, Aug. 6, 2013, 18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/726,099, Mar. 18, 2014, 8 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/875,139, Oct. 3, 2013, 12 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/194,213, May 31, 2013, 11 Pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/194,213, Jun. 27, 2012, 16 Pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/194,213, Dec. 21, 2012, 13 Pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/912,456, Jan. 7, 2014, 9 Pages.Applicant
- “Restrict Access to Applications using AppLocker”, Retrieved from: <http://www.dq.winsila.com/tips-tricks/restrict-access-to-applications-using-applocker.html> on Feb. 13, 2012, Jan. 5, 2012, 2 pages.Applicant
- “Setting Up Simple Restricted Access”, Retrieved at: http://support.webvanta.com/support—article/615777-setting-up-simple-restricted-access—on Feb. 29, 2012, 3 Pages.Applicant
- “Supplementary Search Report”, EP Application No. 11831134.9, Apr. 3, 2014, 3 pages.Applicant
- “What's an Android? And Other Smart(phone) Questions”, Retrieved from: <http://bestbuybusinessdistrict.com/knowlege-center/58-what%27s-an-android-and-other-smart-phone-questions> on Feb. 7, 2011, Sep. 6, 2010, 4 pages.Applicant
- Aalto, et al.,′ “Bluetooth and WAP Push Based Location-Aware Mobile Advertising System”, ACM, MobiSYS '04, Jun. 6-9, 2004, Boston, MA, retrieved from <http://www.mediateam.oulu.fi/publications/pdf/496.pdf> on Feb. 5, 2009,Jun. 6, 2004, 10 pages.Applicant
- Abdelzaher, et al.,′ “Mobiscopes for Human Spaces”, IEEE Pervasive Computing, vol. 6, No. 2, Apr. 2007, 11 pages.Applicant
- Abdesslem, et al.,′ “Less is More: Energy-Efficient Mobile Sensing with SenseLess”, MobiHeld An ACM SIGCOMM workshop, Aug. 17, 2009, pp. 61-62.Applicant
- Agarwal, et al.,′ “Somniloquy: Augmenting Network Interfaces to Reduce PC Energy Usage”, Symposium on Networked Systems Design and Implementation (NSDI), 2009, available at <http://www.usenix.org/events/nsdi09/tech/full—papers/agarwal/agarwal.pdf>,Apr. 23, 2009, pp. 365-380.Applicant
- Aventail, et al.,′ “Aventail and Trust Digital Launch Integrated Secure Mobile Access Solution”, http://findarticles.com/p/articles/mi—pwwi/is—200602/ai—n16063742/?tag=content;col1, Last accessed May 14, 2008,Feb. 2006, 3 Pages.Applicant
- Azizyan, et al.,′ “SurroundSense: Mobile Phone Localization Using Ambient Sound and Light”, retrieved from <http://synrg.ee.duke.edu/papers/surroundsense-poster.pdf> on Feb. 5, 2009, 9/22/208, 1 page.Applicant
- Bahl, et al.,′ “Radar: An In-Building RF-based User Location and Tracking System”, Microsoft Research, Proceedings of IEEE Infocom 2000, Tel-Aviv, Israel, retrieved from <https://3 research.microsoft.com/en-us/um/people/padmanab/papers/infocom2000.pdf> on Feb. 5, 2009,Mar. 2000, 10 pages.Applicant
- Balakrishnan, et al.,′ “ITR: Scalable Location-Aware Monitoring (SLAM) Systems”, Laboratory for Computer Science & Department of EECS, MIT, Cambridge, MA, retrieved from <http://nms.lcs.mit.edu/projects/slam/prop.pdf> on Feb. 5, 2009,Nov. 9, 2001, 31 pages.Applicant
- Barroso, et al.,′ “The Case for Energy-Proportional Computing”, IEEE Computer Society, vol. 40. No. 12, Dec. 2007, pp. 33-37.Applicant
- Branscombe, “Kids Corner and Wallet”, Retrieved from <http://www.techradar.com/reviews/pc-mac/software/operating-systems/windows-phone-8-1086692/review/6>, Jan. 25, 2012, 7 pages.Applicant
- Burke, et al.,′ “Participatory Sensing”, WSW at SenSys, Oct. 31, 2006, 5 pages.Applicant
- Campbell, et al.,′ “Biometrically Enhanced Software-Defined Radios”, Proc. Software Defined Radio Technical Conf, Orlando, Florida, Nov. 2003, 6 Pages.Applicant
- Chiu, et al.,′ “Playful Bottle: A Mobile Social Persuasion System to Motivate Healthy Water Intake”, Proceedings of the 11th international conference on Ubiquitous computing, 2009, 10 pages.Applicant
- Consolvo, “Flowers or a Robot Army?: Encouraging Awareness & Activity with Personal, Mobile Displays”, Proceedings of the 10th International Conference on Ubiquitous Computing, vol. 12, No. 4, Publisher: ACM Press, Sep. 2008, 10 pages.Applicant
- Constandache, et al.,′ “Energy-Aware Localization Using Mobile Phones”, retrieved from <http://www.cs.duke.edu/˜ionut/2008—mobisys.pdf> on Feb. 5, 2009, Jun. 2008, 1 page.Applicant
- Constandache, et al.,′ “Energy-efficient Localization Via Personal Mobility Profiling”, In Proceedings of MobiCASE 2009, Available at <http://synrg.ee.duke.edu/papers/mobicase09.pdf>,Oct. 2009, pp. 1-20.Applicant
- Covington, et al.,′ “Parameterized Authentication”, Proc. 9th European Symposium on Research Computer Security, Lecture notes in Computer Science, Sep. 2004, 18 Pages.Applicant
- Flinn, “Extending Mobile Computer Battery Life through Energy-Aware Adaptation”, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA, retrieved from <http://reports-archive.adm.cs.cmu.edu/anon/2001/CMU-CS-01-171.pdf> from Feb. 5, 2009, Dec. 2001, 165 pages.Applicant
- Foster, et al.,′ “Precision and accuracy of an ankle-worn accelerometer-based pedometer in step counting and”, Preventive Medicine, vol. 41, No. 3-4, Oct. 2005, pp. 778-783.Applicant
- Gaonkar, et al.,′ “Micro-Blog: Sharing and Querying Content through Mobile Phones and Social Participation”, ACM, MobiSys 2008, Jun. 17-20, 2008, Breckenridge, CO, retrieved from <http://www.cs.duke.edu/˜Ipcox/romit-microblog.pdf> on Feb. 5, 2009,Jun. 17, 2008, 13 pages.Applicant
- Hoffmann, et al.,′ “Multilateral Security in Mobile Applications and Location Based Services”, https://users.cs.jmu.edu/bernstdh/web/CS685/papers/hoffman-et-al-2002.pdf, Last accessed May 14, 2008,2002, 18 Pages.Applicant
- Hoh, et al.,′ “Virtual Trip Lines for Distributed Privacy-Preserving Traffic Monitoring”,, Proceedings of the 6th International Conference on Mobile Systems, Applications, and Services, Jun. 2008, 14 pages.Applicant
- Hull, et al.,′ “CarTel: A Distributed Mobile Sensor Computing System”, Proceedings of the 4th international conference on Embedded networked sensor systems, Nov. 2006, 14 pages.Applicant
- Jagadeesan, et al.,′ “A Novel Approach to Design of User Re-Authentication Systems”, Proc. 3rd IEEE Intl. Conf. on Biometrics: Theory, Applications and Systems, Sep. 2009, 6 Pages.Applicant
- Kang, et al.,′ “A Scalable and Energy-Efficient Context Monitoring Framework for Mobile Personal Sensor Networks”, IEEE Transactions on Mobile Computing, vol. 9, No. 5, May 2010, pp. 686-702.Applicant
- Kansal, et al.,′ “Location and Mobility in a Sensor Network of Mobile Phones”, Microsoft Research, Microsoft Corporation, retrieved from <http://research.microsoft.com.com/apps/pubs/default.aspx?id=70416> on Feb. 5, 2009,Jun. 4, 2007, 1 pages.Applicant
- King, et al.,′ “Mobile Device Child Share”, U.S. Appl. No. 13/726,095, Mar. 21, 2013, 57 Pages.Applicant
- Klosterman, et al.,′ “Secure Continuous Biometric-Enhanced Authentication”, Technical Report, May 2000, 25 Pages.Applicant
- Kottahachchi, et al.,′ “Access Controls for Intelligent Environments”, In: Proceedings of ISDA '04: 4th Annual International Conference on Intelligent Systems Design and Applications. Budapest, Hungary (2004), 6 Pages.Applicant
- Krumm, et al.,′ “Predestination: Inferring Destinations from Partial Trajectories”, UbiComp 2006: The Eighth International Conference on Ubiquitous Computing, Sep. 17-21, 2006, Orange County, CA, retrieved from <http://research.microsoft.com/en-us/um/people/horvitzlpredestination.pdf> on Feb. 5, 2009,Sep. 17, 2006, 18 pages.Applicant
- Krumm, et al.,′ “RightSPOT: A Novel Sense of Location for a Smart Personal Object”, Proceedings of Ubicomp 2003, Seattle, WA, retrieved from <http://research.microsoft.com/en-us/um/people/horvitz/rightspot. htm> on Feb. 5, 2009,2003, 1 pages.Applicant
- Lamarca, et al.,′ “Place Lab: Device Positioning Using Radio Beacons in the Wild”, In Proceedings of Pervasive 2005, Munich, Germany, retrieved from <http://www.placelab.org/publications/pubs/pervasive-placelab-2005-final.pdf> on Feb. 5, 2009,2005, 18 pages.Applicant
- Lester, et al.,′ “Validated Caloric Expenditure Estimation using a Single Body-Worn Sensor”, Proceedings of the 11th international conference on Ubiquitous computing, Oct. 2009, 10 pages.Applicant
- Lester, et al.,′ “A Practical Approach to Recognizing Physical Activities”, Pervasive Computing in Pervasive Computing, vol. 3968, 2006, 17 pages.Applicant
- Liao, et al.,′ “Extracting Places and Activities from GPS Traces Using Hierarchical Conditional Random Fields”, The International Journal of Robotics Research, vol. 26, No. 1, 119-134, retrieved from <http://ijr.sagepub.com/cgi/content/26/1/119> on Feb. 5, 2009,2007, 20 pages.Applicant
- Lin et al.,′ “Enabling Energy-Efficient and Quality Localization Services”, National Taiwan University, retrieved from <http://nslab.ee.ntu.edu.tw/publication/conf/qols-percom06.pdf> on Feb. 5, 2009,2006, 4 pages.Applicant
- Lin, et al.,′ “Energy-Accuracy Trade-off for Continuous Mobile Device Location”, In Proceedings of ACM Mobisys 2010, Available at <http://research.microsoft.com/apps/pubs/default.aspx?id=120831>,Jun. 15, 2010, pp. 1-14.Applicant
- Liu, et al.,′ “xShare: Supporting Impromptu Sharing of Mobile Phones”, In Proceedings of the 7th international conference on Mobile systems, applications, and services, Jun. 22, 2009, pp. 15-28.Applicant
- Lu, et al.,′ “Sound Sense: Scalable Sound Sensing for People-Centric Sensing Applications on Mobile Phones”, Proceedings of the 7th international conference on Mobile systems, applications, and services, Jun. 2009, 14 pages.Applicant
- McGlaun, “Fixes for Distracted Driving Remain Unclear”, http://www.dailytech.com/article.aspx?newsid=24903, Jun. 12, 2012, 2 Pages.Applicant
- Mohan, et al.,′ “Nericell: Rich Monitoring of Road and Traffic Conditions using Mobile Smartphones”, Proceedings of the 6th ACM conference on Embedded network sensor systems, Nov. 2008, 14 pages.Applicant
- Moran, et al.,′ “Getting Started with Windows 7”, 2009, 412 pages.Applicant
- Oliver, et al.,′ “Health Gear: A Real-Time Wearable System for Monitoring and Analyzing Physiological Signals”, Apr. 2006, pp. 1-4.Applicant
- Paek, et al.,′ “Energy-Efficient Rate-Adaptive GPS-based Positioning for Smartphones”, In Proceedings of MobiSys 2010, Available at <http://enl.usc.edu/papers/cache/Paek10a.pdf>,Jun. 2010, 16 pages.Applicant
- Peng, et al.,′ “BeepBeep: A High Accuracy Acoustic Ranging System Using COTS Mobile Devices”, ACM, SenSys 2007, Nov. 6-9, 2007, Sydney, Australia, retrieved from <http://research.microsoft.com/en-us/groups/wn/sensys106-beepbeep.pdf> on Feb. 5, 2009,Nov. 6, 2007, 14 pages.Applicant
- Pering, et al.,′ “The PSI Board: Realizing a Phone-Centric Body Sensor Network”, In 4th International Workshop on Wearable and Implantable Body Sensor Networks, 2007, 6 pages.Applicant
- Person, “Writing Your Own GPS Applications: Part 2”, The Code Project, retrieved from <http://www.codeproject.com/KB/mobile/WritingGPSApplications2.aspx> on Feb. 5, 2009,Dec. 20, 2004, 13 pages.Applicant
- Quick, “BizzTrust for Android splits a single smartphone into two virtual phones”, http://www.gizmag.com/bizztrust-for-android/20114/, Retrieved on Jan. 10, 2012,Oct. 2011, 4 Pages.Applicant
- Riva, et al.,′ “The Urbanet Revolution: Sensor Power to the People!”, IEEE Pervasive Computing, vol. 6, No. 2, Apr. 2007, pp. 41-49.Applicant
- Ruairi, et al.,′ “An Energy-Efficient, Multi-Agent Sensor Network for Detecting Diffuse Events”, IJCAI-07—retrieved from <http://www.aaai.org/Papers/IJCAI/2007/IJCAI07-224.pdf> on Feb. 5, 2009, 2007, pp. 1390-1395.Applicant
- Schindler, et al.,′ “City-Scale Location Recognition”, IEEE Computer Society Conference on Computer Vision and Pattern Recognition (CVPR), retrieved from <http://www.cc.gatech.edu/˜phlosoft/files/schindler07cypr2.pdf> on Feb. 5, 2009,2007, 7 pages.Applicant
- Shin, et al.,′ “DEAMON: Energy-efficient sensor monitoring”, 6th Annual IEEE Communications Society Conference on Sensor, Mesh and Ad Hoc Communications and Networks, Jun. 22, 2009, 9 pages.Applicant
- Simonite, “One Smart Phone, Two Personalities”, http://www.technologyreview.com/communications/38865/, Retrieved Jan. 10, 2012,Oct. 13, 2011, 3 Pages.Applicant
- Smailagic, et al.,′ “Location Sensing and Privacy in a Context-Aware Computing Environment”, IEEE Wireless Communications—retrieved from <http://diuf.unifr.ch/pai/education/2002—2003/sem inar/winter/telecom/01043849.pdf> on Feb. 5, 2009, Oct. 2002, pp. 10-17.Applicant
- Stajano, “One user, many hats; and, sometimes, no hat?towards a secure yet usable pda”, Security Protocols Workshop, Springer Verlag, 2004, 14 Pages.Applicant
- Sun, et al.,′ “Signal Processing Techniques in Network-aided Positioning”, IEEE Signal Processing Magazine—Available at <http://www.cspl.umd.edu/sig/publications/sun—survey—200507.pdf>, Jul. 2005, pp. 12-23.Applicant
- Talbot, “App Battles Driver Distraction but Spares Passengers”, Technology Review India published by MIT, http://www.technologyreview.in/news/426889/app-battles-driver-distraction-but-spares-passengers,Feb. 14, 2012, 2 pages.Applicant
- Temporale, “Removing Application Lock on Windows Mobile Standard Devices”, http://www.mobilejaw.com/articles/2009/09/removing-application-lock-on-windows-mobile-standard-devices/, Retrieved on Oct. 13, 2011,Sep. 4, 2009, 10 Pages.Applicant
- Wang, et al.,′ “A Framework of Energy Efficient Mobile Sensing for Automatic User State Recognition”, Proceedings of the 7th international conference on Mobile systems, applications, and services, Jun. 2009, 14 pages.Applicant
- Weilenmann, et al.,′ “Local Use and Sharing of Mobile Phones”, In B. Brown, N. Green & R. Harper (Eds.) Wireless World: Social and Interactional Aspects of the Mobile Age. Godalming and Hiedleburg: Springer Verlag, 2001, pp. 99-115.Applicant
- Woodman, et al.,′ “Pedestrian Localisation for Indoor Environments”, Proceedings of the 10th international conference on Ubiquitous computing, Sep. 2008, 10 pages.Applicant
- Youssef, et al.,′ “The Horus WLAN Location Determination System”, Department of Computer Science, University of Maryland, retrieved from <http://www.cs.umd.edu/˜moustafa/papers/horus—usenix.pdf> on Feb. 5, 2009,2005, 14 pages.Applicant
- Yu, et al.,′ “Personalized Awareness and Safety with Mobile Phones as Sources and Sinks”, Proceedings of Urbansense, workshop held in conjunction with SenSys, Nov. 4, 2008, pp. 26-30.Applicant
- Zaplata, “Context-based Cooperation in Mobile Business Environments—Managing the Distributed Execution of Mobile Processes”, Business & Information Systems Engineering, Apr. 2009, pp. 301-314.Applicant
- Zhang, et al.,′ “The Two Facets of the Exploration-Exploitation Dilemma”, Proceedings of the IEEE/WIC/ACM International Conference on Intelligent Agent Technology (IAT '06), retrieved from <http://ieeexplore.ieee.org/ielx5/4052878/4052879/04052945.pdf?tp=> on Feb. 5, 2009,2006, 7 pages.Applicant
- Zhuang, et al.,′ “Improving Energy Efficiency of Location Sensing on Smartphones”, In Proceedings of MobiSys 2010—Available at <http://www.deutsche-telekom-laboratories.com/˜kyuhan/papers/MobiSys10Kim.pdf>, Jun. 2010, 15 pages.Applicant
- “BroadCloud FamilyCenter”, BroadSoft Data Sheet, retrieved from <http://www.broadsoft.com/pdf/datasheet-broadcloud-familycenter.pdf> on Dec. 13, 2011, 1 page.Applicant
- “Distracted Driving Information Clearinghouse”, Retrieved from <http://www.fcc.dov/encyclopedia/distracted-driving-information-clearinghouse>, (Jul. 27, 2011), 4 pages.Applicant
- “iCloud: What You Need to Know”, MacWorld.com, retrieved from <http://www.macworld.com/article/160380/2011/06/icloud—what—you—need—to—know.html> on Dec. 13, 2011,(Jun. 8, 2011), 16 pages.Applicant
- “Parental Control Software for Cell Phones”, retrieved from <http://www.parentalcontrolcellphones.com/> on Dec. 8, 2011,(Apr. 30, 2010), 5 pages.Applicant
- “Safe Driving System”, Retrieved from <http://web.archive.org/web/20100512220953/http://key2safedriving.com/>, (May 12, 2010), 2 pages.Applicant
- “Your Very Own Support Geek”, retrieved from <http://yoursupportgeek.info/miscellaneous-geek-stuff/t-mobile-uk-to-offer-icd-vega-15-inch-tegra-android-tablet-in-2010> on Dec. 13, 2011,(Jan. 7, 2010), 2 pages.Applicant
- Bilderbeek, PIM “From Unified to Social Communications and Collaboration”, retrieved from <http://www.themetisfiles.com/2011/10/from-unified-to-socialcommunications-and-collaboration/> on Dec. 13, 2011,(Oct. 25, 2011), 4 pages.Applicant
- Davies, Chris “T-Mobile UK to Offer ICD Vega 15-inch Tegra Android Tablet in 2010”, Retrieved from <http://www.slashgear.com/t-mobile-uk-to-offer-icd-vega-15-inch-tegra-android-tablet-in-2010-0768671/> on Mar. 11, 2013, (Jan. 7, 2010), 7 pages.Applicant
- Dipane, Jared “Sprint to Bring Parental Locks to Android Phones to Prevent Use While Driving”, retrieved from <http://www.androidcentral.com/sprint-bring-parental-locks-android-phones-prevent-use-while-driving> on Dec. 8, 2011,(Mar. 22, 2011), 7 pages.Applicant
- Kharif, Olga “Parental Controls for Mobile Phones? You Bet”, Tech Beat, retrieved from <http://www.businessweek.com/the—thread/techbeat/archives/2005/08/parental—contro.html> on Dec. 8, 2011,(Aug. 16, 2005),12 pages.Applicant
- Leblanc, Brandon “The Device Experience in Windows 7—Updated”, Windows 7 Team Blog, retrieved from <http://windowsteamblog.com/windows/archive/b/windows7/archive/2009/09/01/the-device-experience-in-windows-7-updated.aspx> on Dec. 13, 2011,(Sep. 1, 2009), 14 pages.Applicant
- Mui, Chunka “The Lifesaving Smartphone Feature That We Need: Driving Mode”, Retrieved from <http://www.forbes.com/sites/chunkamui/2011/12/19/the-smart-phone-feature-that-we-need-driving-mode/>, (Dec. 19, 2011), 4 pages.Applicant
- Nasar, Jack et al., “Mobile Telephones, Distracted Attention, and Pedestrian Safety”, Accident Analysis & Prevention, retrieved from <http://facweb.knowlton.ohiostate.edu/jnasar/crpinfo/research/MobilePhones—AAP—2007. pdf> on Dec. 8, 2011,(Jan. 2008), pp. 69-75.Applicant
- Patten, Christopher J., et al., “Using Mobile Telephones: Cognitive Workload and Attention Resource Allocation”, Accident Analysis and Prevention, retrieved from <http://beta.nsc.org/safety—road/Distracted—Driving/Documents/Using%20mobile%20telephones,%20cognitive%20workload%20and%20attention%20resource%20allocation.pdf> on Dec. 8, 2011,(May 2004), pp. 341-350.Applicant
- Saenz, Aaron “Unlock Your Door with Your Phone, Text a Key to a Friend—Lockitron is Awesome (video)”, Retrieved from: <http://singularityhub.com/2011/05/24/unlock-your-door-with-your-phone-text-a-key-to-a-friend-lockitron-is-awesome-video/> on Feb. 10, 2012,(May 24, 2011), 4 pages.Applicant
- Tiemann, Amy “AT&T Adds Parental Control Options to Cell Phones”, CNET News, retrieved from <http://news.cnet.com/8301-13507—3-9770506-18.html> on Dec. 8, 2011,(Sep. 7, 2007), 1 pages.Applicant
- Warren, Tom “Microsoft Flaunts Metro Style PowerPoint Live Tiles”, WinRumors, retrieved from <http://www.winrumors.com/microsoft-flaunts-metro-style-powerpoint-live-tiles-video/> on Dec. 13, 2011,(Jul. 11, 2011), 12 pages.Applicant
- Williams, Harold “AT&T Drive Mode, The Anti-Texting While Driving Mobile Solution (video)”, Retrieved from <http://www.talkandroid.com/66579-att-drive-mode-the-anti-texting-while-driving-mobile-solution-video/>, (Oct. 13, 2011), 6 pages.Applicant
- Wood, Molly “Hey, Phone Makers: Where's ‘Driving Mode’?”, Retrieved from <http://news.cnet.com/8301-31322—3-20003824-256.html>, (Apr. 29, 2010), 3 pages.Applicant
- “Foreign Office Action”, CN Application No. 201110317851.5, May 8, 2014, 10 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/090,474, May 6, 2014, 12 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 13/875,139, May 9, 2014, 15 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/726,027, Jun. 24, 2014, 17 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/726,090, Jun. 24, 2014, 28 pages.Applicant
- “Foreign Office Action”, EP Application No. 11831134.9, May 9, 2014, 3 Pages.Applicant
- “Foreign Office Action”, AU Application No. 2011312743, Jun. 20, 2014, 4 Pages.Applicant
- “Restriction Requirement”, U.S. Appl. No. 13/726,048, Jun. 20, 2014, 5 pages.Applicant
- “Restriction Requirement”, U.S. Appl. No. 13/726,049, Jul. 1, 2014, 6 pages.Applicant
- “Foreign Notice of Allowance”, CN Application No. 200980128048.8, Jun. 28, 2014, 6 Pages.Applicant
- “Final Office Action”, U.S. Appl. No. 13/726,099, Aug. 29, 2014, 10 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/726,095, Aug. 15, 2014, 12 pages.Applicant
- Lifehacker, “Get the Most Out of Your iPhone's Notification Center, from Beginner to Jailbreaker”, Available online at <http://lifehacker.com/5882947/get-the-most-out-ofios-Ss-notification-center-frombeginner-to-jailbreakerl>, retrieved on Jul. 29, 2014, Feb. 7, 2012, 8 pages.Applicant
- Osxdaily, “How to Use the lock Screen Camera in iOS 5.1”, Available online at <http://osxdaily.com/2012/03/08/lock-screen-camera-ios-5-1>, retrieved on Jul. 29, 2014, Mar. 8, 2012, 10 pages.Applicant