Microsoft Technology Licensing, LLC

Shawn M Thomas

Joseph H Matthews, Iii

Raman Kumar Sarin

Joseph Alton Schrader

Ted Tai-Yu Chen

Lavanya Vasudevan

Jesse M Dougherty

Sara L Manning

Yamin Wang

Nathan Waddoups

Gautam Pulla

Shai Guday

Sharad Agarwal

Joseph Spencer King

Malcolm Erik Pearson

Aaron Naoyoshi Sheung Yan Woo

Jeffrey B Kay

Andrew Paul Begun

John Yovin

Michael Burt Goulding

David A Braun

Alan Bennett Auerbach

Andrew Haon

Steve Clagg

Todd Myles Derksen

Bernardo Iturriaga Dubost

Jason Craig Nelson

Kerry Woolsey

Rowan Forster

Syed Mansoor Jafry

John D Skovron

Peter M Bergler

Daniel Godbout

Jiaming Wang

Elroy Dyksen

Durlabh Malik

Naveen Chand

Philip Y Chan

John D Skovorn

Jennifer Anne Karr

Kerry D Woolsey

A system for identifying attributes associated with content of an e-mail message and alerting a user includes a client device programmed to allow a user to create an e-mail message including at least one recipient and a message content, a server programmed to check an attribute of the e-mail message, and to send the e-mail message, and one or more information stores in communication with the server, the information stores including information about the e-mail message. The server is programmed to query the information stores to obtain information about the e-mail message as the message is being composed by the user, and the server sends a mail tip to the client regarding the e-mail message. The client is programmed to provide the mail tip to the user, the mail tip being formatted and positioned by the client so that it is integrated within a header section of the e-mail message.

Pre-send evaluation of E-mail communications

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

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

A messaging application running on a computing device utilizes a navigation model that exposes user interfaces (UIs) which implement a messaging conversation history in a minimized form so that a user can quickly jump to a desired conversation displayed on a chat card without having to toggle back and forth between a conventional messaging list view and chat card views. The minimized conversation history can be implemented using a scrollable carousel of images that is persistently displayed on the UI. The images represent messaging participants (i.e., contacts) that are arranged in an ordered display according to conversation history. The particular contact that is associated with the currently displayed chat card is highlighted in the carousel using color and/or other graphic treatments. As messaging activities occur and new messages come in and are sent out, the carousel is dynamically updated to show the contacts in the appropriate sorted historical order.

Quick navigation of message conversation history

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

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.

In embodiments of mobile device child share, a mobile device can display a default device lock screen on an integrated display device, and receive an input effective to transition from the default device lock screen to display a child lock screen without receiving a PIN code entered on the default device lock screen. The mobile device can receive a second input effective to transition from the child lock screen to display a child space. The mobile device implements a device share service that activates a child share mode of the mobile device, and restricts functionality of device applications and access to device content based on designated restriction limits.

Mobile device child share

A method for moderating an electronic message includes intercepting the electronic message at a server computing device, and evaluating content of the electronic message at the server computing device to determine if the electronic message is required to enter a moderation workflow prior to delivering the electronic message to at least one recipient. The method also includes sending an approval request message from the server computing device to at least one moderator device, receiving a first moderation decision message at the server computing device from the at least one moderator, sending an update message from the server computing device to the at least one moderator to update the approval request message to include one or more properties of the first moderation decision, and removing the approval request message from the moderation workflow.

Moderating electronic communications

Disclosed herein are representative embodiments of tools and techniques for updating services in sharing-experience sessions during communications calls. According to one exemplary technique, a first computing device initiates a communications call and receives capability information for a second computing device. The capability information for the second computing device includes information indicating attributes of a service supported by the second computing device. Additionally, the first computing device evaluates the capability information to determine that the service is supported by the first and second computing devices. The first computing device initiates a sharing-experience session that includes the service. An update message comprising update information for the service is received, and based on the received update information, content of the service is updated.

Updating services during real-time communication and sharing-experience sessions

Techniques for reconciliation and remediation of messages sent by a server for storage in an archive are described. Some techniques may comprise receiving a message to be reconciled corresponding to a message sent by a server to be stored in an archive. The received message may be categorized for reconciliation, and a delivery confirmation query may be issued to the archive according to categorization of the message for reconciliation. Based on the response to the delivery confirmation query, it can be determined with certainty whether the message sent to the archive for storage is indeed stored at the archive. Other embodiments are described and claimed.

Reconciliation and remediation with communication archives

Architecture that facilitates cross-boundary message tracking based on a trust relationship in existence between a sender network and a recipient network. A tracking service is deployed in each network as a proxy to obtain message events for each hop that passes the message on to the recipient. Tracking can include a search task and a get task. Messages can be found in reports that match message search criteria. The search task returns an array of search results objects, each object identifying a single tracking report. A selected object is pipelined into the get task to return the detailed tracking report for the selected message.

Message tracking between organizations

Growing community of inventors

Redmond, WA, United States of America

Shawn M Thomas