Microsoft Technology Licensing, LLC

Joseph Alton Schrader

Joseph H Matthews, Iii

Raman Kumar Sarin

Ted Tai-Yu Chen

Shawn M Thomas

Shai Guday

Sharad Agarwal

Joseph Spencer King

Lavanya Vasudevan

Jeffrey C Fong

Todd San Jule

Thomas Henry Taylor

Mark D Schwesinger

Bin Lin

John Yovin

Aaron DeYonker

Nishad Mulye

Zhike Kong

Mark G Young

Rowland W Yerkes

Xinli Zou

David B Delp

Garth A Lewis

Allyson M Krieger

Eric Emil Kattwinkel

Aaron Naoyoshi Sheung Yan Woo

Ashish Gupta

Andrew Paul Begun

Michael Burt Goulding

Jared Frew

David A Braun

Alice Jane Brush

Alan Bennett Auerbach

Melissa Nicole Lim

John D Skovron

Andrew Haon

Shawn Cantin Callegari

Terri L Chudzik

Todd Myles Derksen

Bernardo Iturriaga Dubost

Tyler N Jensen

Renle Xia

Jennifer Anne Karr

John D Skovorn

Iii Joseph H Matthews

Embodiments of the disclosure aggregate and present event information relating to a calendar event associated with an application executing on a computing device. In some embodiments, data relating to the calendar event is obtained from a content source that is outside an execution context of the application. The data relating to the calendar event is obtained and/or presented intermittently in a user interface element associated with the application. The content source that is outside the execution context of the application may be within an execution context of one or more other applications, an operating system of the computing device, and/or a web service.

Aggregating and presenting event information

In embodiments of a hub key service, a device includes a communication interface for communication coordination with one or more associated devices of the device, and the associated devices correspond to hub members. A hub manager is implemented to generate an electronic key that includes access permissions, which are configurable to enable controlled access for the hub members, such as to a building, vehicle, media device, or location. The hub manager can then correlate the electronic key with the device to enable access to the building, vehicle, media device, or location with the device utilized as the electronic key.

Hub key service

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.

Mobile device safe driving

A mobile device has memory storage to maintain hub data that is associated with a private interaction hub, where the hub data includes multiple types of displayable data that is editable by different types of device applications. The memory storage at the device also maintains private data that is displayable and is viewable with one of the device applications. The mobile device also includes a display device to display the multiple types of the hub data in a hub user interface of a hub application. The display device can also display the private data and a subset of the hub data that are both associated with a device application in a device application user interface.

Private interaction hubs

In embodiments of restricted execution modes, a mobile device can display a device lock screen on an integrated display device, and transition from the device lock screen to display a shared space user interface of a shared space. The transition to display the shared space user interface is without receiving a PIN code entered on the device lock screen. The mobile device implements a restricted execution service that is implemented to activate a restricted execution mode of the mobile device, and restrict access of a device application to device content while the restricted execution mode is activated. The restricted execution service can also allow a shared device application that is included in the shared space access to the device content while the restricted execution mode is activated.

Restricted execution modes

Mobile device emergency service techniques are described. In embodiments, a client device includes one or more modules implemented at least partially in hardware and configured to implement an emergency service. The emergency service configured to support operations including generating a user interface for display on a display device, receiving one or more inputs usable to form an emergency contacts list that includes a plurality of emergency contacts, and causing the emergency contacts list to be communicated to one or more other client devices for use in generating a message to be communicated automatically and without user intervention to the emergency contacts in the emergency contacts list responsive to a trigger.

Mobile device emergency service

In embodiments of mobile devices control, a mobile device includes a communication interface for control communication with associated devices of the mobile device, and the associated devices correspond to members of a private interaction hub. A device control service is implemented to determine that the mobile device is moving in a vehicle based on motion data, and can generate a device quiet control to restrict at least audible outputs from one or more of the associated devices that are in the vehicle with the mobile device. The device control service can then initiate communication of the device quiet control to the associated devices in the vehicle to quiet the associated devices that are controllable from the mobile device.

Mobile devices control

In implementations of a hub coordination service, a device includes a communication interface for communication coordination with one or more associated devices of the device, and the associated devices correspond to hub members. A hub manager is implemented to receive a task input to create a task for one or more of the hub members to complete. The hub manager can register the task in a hub that is a private, shared space of the hub members, and then initiate communication of the task to respective associated devices of the one or more hub members for notification of the task to be completed.

Hub coordination service

Thumbnail images representative of recorded TV programs are generated and presented to aid a user in browsing the recorded TV programs. In one implementation, a temporary thumbnail image is generated when a TV program first starts recording. The temporary thumbnail is used to populate any user interface (UI) screens that reference the recoded TV program. Once the TV program has reached a threshold amount of recording (e.g., a prescribed duration of recording, or completion of the recording), a permanent thumbnail image is generated and associated with the TV program. The permanent thumbnail is then presented in any subsequent UI screens, replacing the temporary thumbnail. In another implementation, display of the thumbnail images in the UI screens may be further controlled by setting preferences, such as parental controls.

Thumbnail generation and presentation for recorded TV programs

In embodiments of private interaction hubs, a mobile device has memory storage to maintain hub data that is associated with a private interaction hub, where the hub data includes multiple types of displayable data that is editable by different types of device applications. The memory storage at the device also maintains private data that is displayable and is viewable with one of the device applications. The mobile device also includes a display device to display the multiple types of the hub data in a hub user interface of a hub application. The display device can also display the private data and a subset of the hub data that are both associated with a device application in a device application user interface.

A favorite channel list for a media system is generated by observing the viewing, surfing, and recording habits of a user. The viewing habits may include the duration and frequency of viewing a channel. A user's surfing habits, including navigation habits of a guide, the method used for navigation to a channel, and information queries made during a surfing session may be used to determine which channels may be added to a favorites list. When the user has an ability to record a program and view the program later, the user's behavior in selecting programs for recording, and the behaviors of playing back and archiving recorded shows may also be used to identify favorite channels. In some embodiments, the favorites list may be customized for a user or node of a playback system, as well as time of day.

Automatically generated TV favorites list

Growing community of inventors

Kirkland, WA, United States of America

Joseph Alton Schrader