Lei Yu

20130191894, Jul 25, 2013

Jan 19, 2012

13/354324

Vadim Eydelman - Bellevue WA, US
Brian Kress - Woodinville WA, US
Matthias Leibmann - Woodinville WA, US
Moustafa Noureddine - Redmond WA, US
Lei Yu - Redmond WA, US
Haibo Luo - Kirkland WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 21/22

726 6, 726 3, 726 5, 726 8

Online and on-premise applications identify trusted authentication providers. The applications are configured with a list of trusted issuers of authentication credentials. When an application receives a request requiring authentication, the application returns a 401 response that includes the trusted issuer list. The requesting application compares the trusted issuer list from the 401 response to its own list of authentication providers. If there is a match between the two lists, then the requesting application creates a self-issued token for the authentication provider. The authentication provider uses the self-issued token to generate an authentication token for the requesting application. The requesting application may also directly create a token for a target partner application, without an authentication provider, if there is a direct trust between the two applications.

20220360546, Nov 10, 2022

May 23, 2022

17/664445

- Redmond WA, US
Chowdhury Sucharit BARUA - Redmond WA, US
Vasant Kumar TIWARI - Redmond WA, US
Lei YU - Sammamish WA, US

Microsoft Technology Licensing, LLC - Redmond WA

H04L 51/02
G06Q 30/00
H04L 51/046
H04L 51/18
H04W 4/12
H04L 51/56
H04L 51/58
H04L 67/564

Email has become commonplace as a means to communicate among parties non-synchronously by exchanging email messages. Some communications, however, may be more effective in real-time or in near real-time. For instance, service providers may offer a chat feature to accommodate real-time or near real-time help or service communications with customers. However, in this case, the user is likely required to enter credentials and/or context information to transition into a different communication type with the service provider. The present systems and methods provide a continuous conversation experience for the user whereby a message recipient of one message type (e.g., email, text, etc.) may continue a conversation in a different message type (e.g., a chat session, instant message, etc.) without manually providing message context for communicating via the second message type.

20210105232, Apr 8, 2021

Dec 15, 2020

17/122386

- Redmond WA, US
Chowdhury Sucharit BARUA - Redmond WA, US
Vasant Kumar TIWARI - Redmond WA, US
Lei YU - Sammamish WA, US

Microsoft Technology Licensing, LLC - Redmond WA

H04L 12/58
G06Q 30/00
H04W 4/12
H04L 29/08

Email has become commonplace as a means to communicate among parties non-synchronously by exchanging email messages. Some communications, however, may be more effective in real-time or in near real-time. For instance, service providers may offer a chat feature to accommodate real-time or near real-time help or service communications with customers. However, in this case, the user is likely required to enter credentials and/or context information to transition into a different communication type with the service provider. The present systems and methods provide a continuous conversation experience for the user whereby a message recipient of one message type (e.g., email, text, etc.) may continue a conversation in a different message type (e.g., a chat session, instant message, etc.) without manually providing message context for communicating via the second message type.

20190173811, Jun 6, 2019

Dec 4, 2017

15/831293

- Redmond WA, US
Chowdhury Sucharit BARUA - Redmond WA, US
Vasant Kumar TIWARI - Redmond WA, US
Lei YU - Sammamish WA, US

Microsoft Technology Licensing, LLC - Redmond WA

H04L 12/58
G06Q 30/00

Email has become commonplace as a means to communicate among parties non-synchronously by exchanging email messages. Some communications, however, may be more effective in real-time or in near real-time. For instance, service providers may offer a chat feature to accommodate real-time or near real-time help or service communications with customers. However, in this case, the user is likely required to enter credentials and/or context information to transition into a different communication type with the service provider. The present systems and methods provide a continuous conversation experience for the user whereby a message recipient of one message type (e.g., email, text, etc.) may continue a conversation in a different message type (e.g., a chat session, instant message, etc.) without manually providing message context for communicating via the second message type.

20180089165, Mar 29, 2018

Sep 26, 2016

15/275728

- Redmond WA, US
Lei Yu - Redmond WA, US
Victor Boctor - Redmond WA, US
Pretish Abraham - Sammamish WA, US
Raju Nagalinga S - Bangalore KA, IN

G06F 17/27
H04L 12/58
G06F 17/21
G06F 17/24

A message is received, that represents an action to be performed in a service. The message includes a natural language portion and an endpoint to interact with. The natural language portion is parsed to identify the action and the endpoint is interacted with to perform the action.