Microsoft Technology Licensing, LLC

Deepak Rao

Stephane Taine

Vadim Eydelman

Dhigha D Sekaran

Anthony C Romano

Robert W Young

Ganesh Sridharan

Giridhar Kalpathy Narayanan

Yves Pitsch

Mattia Tocco

Bimal Kumar Mehta

Sankaran Narayanan

Paul D Tidwell

Xin Guo

Dhruv Chopra

Neeraj Garg

Krishnamurthy Ganesan

Sundar Anantharaman

Aidan Downes

Satya Kondepudi

Rastan Boroujerdi

Shaun David Cox

Pradipta Kumar Basu

Nirav A Kamdar

Amit A Sehgal

Anand Lakshminarayanan

Lei Tan

Girija Bhagavatula

Shahzaib Younis

Michael K W Tsu

Rahul Thatte

Santhosh Kopparapu

Yong Lim

Calin M Popa

Alex Edelsburg

A join service joins first and second computerized meetings. The join service receives information about the first and second computerized meetings from respective first and second meeting services. In response to a request from one of the first and second services to join the meetings, the join service translates audio, video, and data signaling between the first computerized meeting service and the second computerized meeting to join participants in the first computerized meeting and participants in the second meeting in a combined computerized meeting. An alternative join service obtains a uniform resource indicator (URI) for an agent of the first meeting. In response to a request from a participant in the second meeting to access the first meeting, the join service provides the URI to the second meeting service to allow the second meeting service to join the second meeting to the first meeting.

Binding separate communication platform meetings

A first meeting of a first network service is connected to a second meeting of a second network service by sending data identifying the first network service to the second network service and receiving, from the second network service, a key that is associated with the first network service. The first network service then sends information identifying the second meeting and a link to the first meeting to the second network service using an address for second network service that includes the key. The first network service then receives a second meeting link to the second meeting from the second network service and providing devices participating in the first meeting with the second meeting link. These devices activate the second meeting link to access resources of the second meeting.

Binding seperate communication platform meetings

Described herein are various aspects pertaining to generating web tickets for use with authenticating computing devices to a computing system. Symmetric keys are used when generating the web tickets, wherein a symmetric key is valid for use when generating web tickets for a first period of time, and a web ticket generated based upon the symmetric key is valid for use when authenticating a computing device for a second period of time that is longer than the first period of time. Thus, the symmetric key is used for authenticating computing devices after it has ceased being used to generate web tickets.

Web ticket based upon a symmetric key usable for user authentication

Binding of separate communication platform meetings is provided. Video conference service interconnection with online meeting service may be achieved by allowing the online meeting service to provide a tenant identifier to the video conference service, which may be associated with the tenant and used in a key that is used by the video conference service to schedule and initiate meetings. The online meeting service may also include the key in metadata used by its scheduling service. The tenant identifier and/or the key may be used by the components involved in initiating and, facilitating various meetings by users of the online meetings (and by users of the video conference service).

Described herein are various aspects pertaining to a web ticket that is used in connection with authenticating a user. The web ticket is generated through use of a symmetric key, and is less than two hundred bytes in size. A ticket issuer executing on a first computing device generates the web ticket responsive to receiving authentication data from a client computing device, and transmits the web ticket to such client computing device. The client computing device includes the web ticket in requests for data transmitted to a second server computing device that is in communication with the ticket issuer. The second server computing device includes a validator that validates the web ticket using the symmetric key, which is shared between the first server and the second server.

A centralized service communicatively links an application provider to a plurality of different message forwarding services. The centralized service receives a request and authenticates the application provider associated with the request. Further, the centralized service delivers a message embodied by the request to a first message forwarding service with a first protocol and/or to a second message forwarding service with a second protocol different than the first protocol.

Centralized service for distributed service deployments

Techniques to recursively discover services in a distributed environment may include receiving a request, including a unique client identifier, from a client device to access a home resource at a services site. The services site may identify which services site is mapped to the client domain of the unique client identifier in the request. If the services site that received the request is not the services site identified by the client domain, the services site that received the request may provide a redirect token that includes a link to the identified services site to the client device. Otherwise, the services site that received the request may provide one or more links to resources in a cluster within the services site. The links to resources may include a link to the requested home resource. Other embodiments are described and claimed.

Techniques to discover services recursively in a distributed environment

A method, system, and architecture for providing a conference system that effectively achieves high availability conferencing is provided. The conference system architecture provides a conference system that comprises a set of stateless conference servers and a shared conference store to provide highly available conferencing to its users. The conference servers serve (host) conferences (meetings) that allow users to conduct distributed conferences. Each conference server generally performs conference provisioning operations and conference control operations. The shared conference store provides for the storage of conference state information, thus allowing the conference servers in the conference server pool to be stateless by maintaining conference state information on the shared conference store. A stateless conference server may also locally maintain, for example, in cache memory, some of the conference state information that is maintained on the shared conference store.

High availability conferencing

The embodiments described herein generally relate to methods and systems for tunneling arbitrary binary data between an HTTP endpoint and an arbitrary destination. Such tunneling of data is valuable in an environment, for example, in which a browser-based client communicates in the HTTP protocol and desires to exchange data with a remote endpoint understanding non-HTTP communications. A relay server is used as a 'middle man' to connect the client to the destination, and components supporting the necessary protocols for data exchange are plugged into the relay server. To achieve reliable and ordered transmission of data, the relay server groups sessions through the assignment of session identifiers and tracks the exchange of messages through the assignment of sequence and acknowledgment numbers. Further, the relay server provides for authenticating the HTTP endpoint with the destination and for handling other operations not available in the constrained environment of the Web-based client.

Method and system for reliable protocol tunneling over HTTP

A communications manager of an enterprise receives an add-conference request to host a conference by the enterprise from an organizer client, wherein the conference to enable an anonymous user that does not have enterprise credentials to join the conference. The communications manager sends an add-conference response to the organizer client indicating that the conference is organized.

Distributed secure anonymous conferencing

Architecture for seamless role switching in application sharing. A multipoint control unit (MCU) can be used for connecting multiple clients over a network. An application sharing component establishes an application sharing session over the MCU, and application content is exchanged from a sharer client to one or more viewer clients. Each client can communicate a media connection preference to the session. Client sharer and viewer roles are defined during creation of the application sharing session. A client can seamlessly switch roles during the session from a viewer to a sharer, and vice-versa, so that different application content can be shared to the session viewers. The session can be restricted to only one sharer so that the viewing clients view one sharer client at a time.

Signaling support for sharer switching in application sharing

Endpoints are enabled to facilitate desktop and/or application sharing in enhanced communication systems using Session Initiation Protocol (SIP) and Remote Desktop Protocol (RDP) protocols by tunneling RDP packets through an Interactive Connection Establishment (ICE) channel built-in within the Real-time Transport Protocol (RTP), thus allowing RDP sessions to traverse Network Address Translators (NATs) or firewalls.

Tunneling of remote desktop sessions through firewalls

Extensible architecture for template-baser user setting management by creating logical groupings of per-user settings using different template types. A manageable way to assign templates to sets of users based on different criteria is provided. Templates can be defined in a declarative format (e.g., XML), which declarative format is developed such that various user interface (UI) pieces, third-party applications, and different client types can easily understand the templates. Extensibility of the architecture is supported for defining the templates such that external third-party application writers can make use of the provided infrastructure to add to existing templates or create new template types, and to seamlessly integrate into the existing infrastructure. Additionally, the per-user settings within the templates can be enforced on the server side, including the enforcement of future settings and template types.

Growing community of inventors

Bellevue, WA, United States of America

Deepak Rao