Microsoft Technology Licensing, LLC

Microsoft Corporation

Amritansh Raghav

Eran Shtiegman

Rajesh Ramanathan

Sira P Rao

Ankur Chavda

Setty Venkateshaiah

Nikhil P Bobde

Jonathan Jay Cadiz

Danny Levin

Parag Samdadiya

Gurdeep Singh Pall

Paul D Tidwell

Venkateshaiah Setty

Craig M Combel

Michael Trommsdorff

Andreas Strebel

Amit Gupta

Anton W Krantz

Joseph T Fletcher

Rui Liang

Lokesh Srinivas Koppolu

Lisa C Anderson

Sriram K Parameswar

Pradipta Kumar Basu

Cindy Kwan

Arulkumar Elumalai

Dena Osherovich

Dejun Zhou

Sira Rao

Setty Venky

Systems, methods, and software technology for providing access control with respect to bots is disclosed herein. In an implementation, an access control service monitors a location of a device with respect to a geographic area. In response to when the device has entered the geographic area, the service grants a bot associated with the geographic area with access to the device. The service may grant the bot with continued access to the device if an end-user conversed with the bot while it had access. However, the service may deny the bot the continued access to the device if the end-user did not converse with the bot.

Location based access control for artificial conversational entities

A presence aggregation system provides a presence aggregation server that allows for the publication of presence state of a publisher from the publisher's multiple endpoints. A presence state includes an availability value and an activity. An activity may include an activity token and/or a custom string. When any one of the publisher's endpoints makes a presence state publication on the presence aggregation server, the presence aggregation server generates an aggregated state of the publisher (i.e., the availability of the publisher aggregated across all of the publisher's endpoints) and publishes the generated aggregated state to each of the publisher's endpoints. The presence aggregation server may also provide the publisher's aggregated state to the subscribers of the publisher's aggregated state information.

User presence aggregation at a server

In one embodiment, a user may transfer a multimodal conversation. A multimodal conversation may have a first mode communication session and a second mode communication session. A first user point of presence may execute a first transfer of the first mode communication session with a first partner point of presence from the first user point of presence to a first target point of presence. A second user point of presence may execute a second transfer of the second mode communication session with a second partner point of presence from the second user point of presence to a second target point of presence.

Multimodal conversation transfer

Systems, methods, and software technology for providing access control with respect to messaging bots is disclosed herein. In an implementation, an access control service associates various messaging bots with various geographic areas. The system monitors a location of messaging clients with respect to the geographic areas and, in response to when at least one of the messaging clients has entered one of the geographic areas, grants an associated messaging bot with initial access to the messaging client to converse with an end user. Subsequent access is granted based on a level of engagement reached with respect to the messaging conversation.

In one embodiment, a user may transfer multimodal conversation. A multimodal conversation may have a first mode communication session and a second mode communication session. A first user point of presence may execute a first transfer of the first mode communication session with a first partner point of presence from the first user point of presence to a first target point of presence. A second user point of presence may execute a second transfer of the second mode communication session with a second partner point of presence from the second user point of presence to a second target point of presence.

Architecture that facilitates the conveyance of a trust level when the caller makes a call, the trust level in dependence on the state of the caller system. The callee (call recipient) receives notification of the trust level and can use this information in the communication such as to request verification from the caller and/or initiate other modes of communication. A caller can authenticate the caller identity in different ways to a communication server. Based on that, the server can assign an appropriate server-verified trust level to the caller. Further, an unsecured phone controller can indicate a lower client-side defined trust level. The server verified and client-side trust levels are then sent to the callee, where the callee determines whether to allow caller access to one or more secured features based on the feature values and the trust level imposed by the callee to access those features.

Access control to secured application features using client trust levels

A method and system for providing context of a caller to a callee when a call is initiated is provided. The context system executing on the calling device collects context for the call. The calling device initiates the call and sends a message to the callee that includes the context. Upon receiving the message, the callee device notifies the caller that a call has been initiated and displays the received context. The callee can decide based on the received context whether to answer the call or not answer the call.

Augmenting a call with context

A client-side signaling mechanism that allows a client to control how a telephone call is handled on a call server. The client user can create call routing rules on the client device using a client control component that manages session protocol messages. Once created, the call routing rule(s) created on the client are transmitted to the call server where a call routing component of the call server processes the rule(s) for a call related to the client. When the server receives the rule(s) and determines that the rule(s) are related to an existing call (incoming or currently in-process), the server halts current normal server rules processing for that call and executes the client-created rule(s). In one example, SIP session messages are employed for client control of server-side call forwarding.

Client controlled dynamic call forwarding

Context-based call routing is provided in a unified communication system by enabling subscribers to define a routing document, which is published by the communication system to callers who subscribe to a presence of the called party. Through publication of the context-based routing information, callers are enabled to make selections between call destination options as defined by the caller and provide a subject for the requested call. The call is then routed by the system according to the caller selection allowing efficient facilitation of the communication between the caller and the called party or their designees.

Contextual call routing by calling party specified information through called party specified form

A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Aggregating user presence across multiple endpoints

Growing community of inventors

Seattle, WA, United States of America

Amritansh Raghav