In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.
Drawings
Claims20
A computer-implemented method for providing cross-domain access to calendar availability, the computer-implemented method comprising:
receiving a request to schedule an event, the request comprising:
an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain;
generating, by a first token security authorization entity, a token describing the organizer user account;
authenticating, by a second token security authorization entity, the token describing the organizer user account with an authorization sent from a device associated with the invitee user account for the organizer user account to access electronic calendar information associated with the invitee user account;
providing the organizer user account with access to the electronic calendar information associated with the invitee user account based on the authentication;
determining an importance level of the organizer user account to the invitee user account;
determining, based on the importance level, that the organizer user account has access to an event in an electronic calendar associated with the invitee user account;
determining whether the event is a recurring meeting;
determining, based at least in part on the determination of whether the event is a recurring meeting, a relative importance of the event compared to the organizer user account;
and causing the event to be surfaced in an event scheduling assistant user interface associated with the organizer user account, wherein the event is surfaced with an indication corresponding to the relative importance of the event compared to the organizer user account.
7 more elements
A system for providing cross-domain access to calendar availability, comprising:
a memory for storing executable program code;
and one or more processors, functionally coupled to the memory, the one or more processors being responsive to computer-executable instructions contained in the program code and operative to:
receive a request to schedule an event, the request comprising:
an identity of a requestor user account, the requestor user account associated with a first domain, and an identity of a requestee user account, the requestee user account associated with a second domain generate, by a first token security authorization entity, a token describing the requestor user account;
authenticate, by a second token security authorization entity, the token describing the requestor user account with an authorization sent from a device associated with the requestee user account for the requestor user account to access electronic calendar information associated with the requestee user account;
provide the requestor user account with access to the electronic calendar information associated with the requestee user account based on the authentication;
determine an importance level of the requestor user account to the requestee user account;
determine, based on the importance level, that the requestor user account has access to an event in an electronic calendar associated with the requestee user accounts
determine whether the event is a recurring meeting;
determine, based at least in part on the determination of whether the event is a recurring meeting, a relative importance of the event compared to the requestor user account;
and cause the event to be surfaced in an email application user interface associated with the requestor user account, wherein the event is surfaced with an indication corresponding to the relative importance of the event compared to the requestor user account.
8 more elements
A computer-readable storage device comprising executable instructions that, when executed by one or more processors, assist with providing cross-domain access to calendar availability, the computer-readable storage device including instructions executable by the one or more processors for:
receiving a request to schedule an event, the request comprising:
an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain;
generating, by a first token security authorization entity, a token describing the organizer user account;
authenticating, by a second token security authorization entity, the token describing the organizer user account with an authorization sent from a device associated with the invitee user account for the organizer user account to access electronic calendar information associated with the invitee user account;
providing the organizer user account with access to the electronic calendar information associated with the invitee user account based on the authentication;
determining an importance level of the organizer user account to the invitee user account;
determining, based on the importance level, that the organizer user account has access to an event in an electronic calendar associated with the invitee user account;
determining whether the event is a recurring meeting;
determining, based at least in part on the determination of whether the event is a recurring meeting, a relative importance of the event compared to the organizer user account;
and causing the event to be surfaced in an event scheduling assistant user interface associated with the organizer user account, wherein the event is surfaced with an indication corresponding to the relative importance of the event compared to the organizer user account.
25 Mar 2040Estimated · howhide20 years from earliest known nonprovisional domestic filing plus recorded patent term adjustment, including 141 days of adjustment. Maintenance-fee lapses, terminal disclaimers and statutory extensions have not been checked. The continuity chain may be incomplete; this is not an enforceability determination.
Authentication, i.e. establishing the identity or authorisation of security principals: user authentication
Life of this patent
About 13 years 5 months of term left · ends 25 Mar 2040 (estimated)
Priority5 Nov 2019
Published6 May 2021
Granted12 Jul 2022
Today12 Oct 2026
Term ends25 Mar 2040
Priority5 Nov 2019
Granted12 Jul 2022
Term ends25 Mar 2040
Application filedUS 16/675,054
Assigned to Microsoft Technology Licensing, LLCassignment of assignor's interest
PublishedUS 2021/0133693 A1
GrantedUS 11,386,397 B2
TodayWithin its term
Term endsEstimated, includes 141 days of adjustment
Description10,000 words
Summary425 words
#Electronic calendars and messaging applications that are integrated with those electronic calendars are ubiquitous in business environments and are increasingly being used for the scheduling of personal events. A user in an organization may provide other users within that organization with access to her calendar. Those other users may then more easily determine when the user is available or busy for meeting booking purposes.
#It is with respect to this general technical environment that aspects of the present technology disclosed herein have been contemplated. Furthermore, although a general environment has been discussed, it should be understood that the examples described herein should not be limited to the general environment identified in the background.
#This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description section. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. Additional aspects, features, and/or advantages of examples will be set forth in part in the description which follows and, in part, will be apparent from the description or may be learned by practice of the disclosure.
Brief description of the drawings12 figures
#Non-limiting and non-exhaustive examples are described with reference to the following figures:
#FIG. 1 is a schematic diagram illustrating an example distributed computing environment for providing cross-domain access to calendar content.
#FIG. 2A illustrates a simplified diagram of a distributed computing environment for providing cross-domain access to calendar availability information.
Detailed description9,300 words
#Various embodiments will be described in detail with reference to the drawings, wherein like reference numerals represent like parts and assemblies throughout the several views. Reference to various embodiments does not limit the scope of the claims attached hereto. Additionally, any examples set forth in this specification are not intended to be limiting and merely set forth some of the many possible embodiments for the appended claims.
#Non-limiting examples of the present disclosure describe systems, methods and devices for providing cross-domain access to electronic calendars. As used herein, “domain” may refer to a user's electronic alias and/or a user's organization. For example, a first domain may comprise an email address with domain @[company1.com] and a second domain may comprise an email address with domain @[company2.com]. According to examples, a first user account may request access to an electronic calendar associated with a second user account. The request may originate from an electronic calendar application associated with the first user account, an event scheduling assistant associated with the first user account, a digital assistant, an email application associated with the first user account, or a stand-alone request interface, for example.
#In some examples, the second user account may have settings that have been interacted with by the second user that allow users outside of her domain to access certain electronic calendar details. Those calendar details may include whether the second user is free or busy for authorized time periods. In some examples, the details that a user may access from the second user's electronic calendar may be based on an importance level of a requesting user that is determined by a cross-domain calendar application service. The cross-domain calendar application service may analyze various factors in making a determination as to a requesting user's relative importance to a sharing user. Those factors may include collaboration signals (e.g., messages exchanged between users, meetings that include users, etc.), hierarchy of users in their respective organizations, and social media graphs, for example. Therefore, the cross-domain calendar application service may provide calendar event information from the sharing user's electronic calendar at a level that corresponds to a requesting user's determined importance level to the sharing user. The sharing user may manually adjust the sharing level and/or details that are shared with individual users and/or multiple users at a given time (e.g., users in a same domain, users in a same organization, users having similar characteristics, etc.).