SHARING DATA WITHIN AN INSTANT MESSAGING SESSION
Sharing data within an instant messaging session is described. A user participating in an instant messaging session may request a data access key. The key, which provides access to data associated with the user, may then be transmitted via the instant messaging session to one or more other participants in the instant messaging session. The other instant messaging session participants can then use the key to access, via the instant messaging session, the data associated with the user.
Latest Microsoft Patents:
- SYSTEMS AND METHODS FOR IMMERSION-COOLED DATACENTERS
- HARDWARE-AWARE GENERATION OF MACHINE LEARNING MODELS
- HANDOFF OF EXECUTING APPLICATION BETWEEN LOCAL AND CLOUD-BASED COMPUTING DEVICES
- Automatic Text Legibility Improvement within Graphic Designs
- BLOCK VECTOR PREDICTION IN VIDEO AND IMAGE CODING/DECODING
This application is a continuation of and claims priority to U.S. patent application Ser. No. 12/645,054, filed Dec. 22, 2009, which claims priority to U.S. Pat. No. 7,660,904, filed May 11, 2004 and issued on Feb. 9, 2010, the disclosures of which are incorporated by reference herein.
TECHNICAL FIELDThis invention relates to instant messaging, and more specifically to sharing data within an instant messaging session.
BACKGROUNDElectronic calendars have become a common tool used by individuals to track meetings, appointments, and other scheduled events. When scheduling an event that is to include multiple individuals, the person scheduling the event may or may not have access to view calendars or schedules associated with the other individuals to be invited to the event. When a user schedules an event, indicating one or more other individuals to be in attendance, an email message is typically sent to the other users, and the other users can each either accept or decline the meeting request. Because of the delay that may occur between the time that one user schedules an event and the time at which the other attendees have checked their email and responded to the meeting request, it is possible that either the scheduled meeting time will have passed or that one or more of the attendees may have scheduled or been invited to attend a conflicting event. If this happens, the meeting may then need to be re-scheduled, and the scheduling process must be started again. In addition, because the initiating user may not get an answer right away, he typically needs to also schedule personal time to check for email responses to determine whether the meeting has been accepted or if it needs to be rescheduled.
Instant messaging is an increasingly popular communication tool that enables two or more users to exchange real-time text messages via a network or peer-to-peer connection. Instant messaging differs from email in that instant messages are exchanged in real-time between two users who are online at the same time. On the other hand, email messages may be exchanged between one user who is online at the time the message is created and another user who may not be online to check email until much later.
While instant messaging is an effective tool for communication, it does not support some of the other tasks that may naturally flow from a real-time communication. For example, if two users are engaged in an instant messaging conversation, and decide to schedule a time to meet in person, each user may need to consult a personal calendar, and a significant amount of time may be spent exchanging scheduling information before being able to identify a time that both users are available to meet. This scenario becomes even more difficult if more than two individuals are participating in an instant messaging conversation and want to schedule a time to get together in person.
Accordingly, a need exists for an instant messaging session tool that enables users to easily share information, such as calendar data, in real-time.
SUMMARYTechniques for enabling data sharing within an instant messaging session are described. Users participating in an instant messaging session can submit through the instant messaging session, a request for a data access key that provides access to a user's data, such as personal calendar data. The keys are then exchanged between the users through the instant messaging session. The key exchange enables the users participating in the instant messaging session to access one another's data.
When users have access to one another's data, other tasks may also be performed. For example, in addition to viewing one another's calendar data, users may also schedule a meeting to be added to the instant messaging session participants' calendars. Meeting invitations are distributed and users can accept or decline the meeting within the instant messaging session.
The embodiments described below provide techniques for sharing data within an instant messaging session. The described exemplary implementation enables users to share calendar data and schedule meetings within an instant messaging session. It is recognized, however, that the techniques described herein are not limited to enabling the sharing of calendar data, but that they may be used to enable other types of data sharing and related tasks that may also be performed via an instant messaging session.
In the described exemplary implementation, when two users are communicating via an instant messaging session, one of the users can initiate a calendar sharing request that, if accepted by the other user, causes the instant messaging user interface to display calendar information associated with both users. Both users are then able, within the instant messaging user interface, to browse both users' calendars simultaneously. Either user is then also able to schedule a meeting to be attended by both users. Because the meeting is scheduled through an instant messaging session, both users can accept the meeting, and the meeting is promptly scheduled in both users' calendars.
Access to a user's calendar data is controlled by the use of an encrypted key. When a user requests a key to access their personal calendar data, the key can then be given to another user to grant the other user permission to view the calendar data. By exchanging data access keys within an instant messaging session, a user can give another user temporary access to their calendar data. That is, the key that is shared can be configured to expire at a pre-determined time, or based on some other criteria (e.g., when the instant messaging session is closed). Because the data is shared within an instant messaging session, communication based on the shared data can also be facilitated. For example, when scheduling a meeting to be added to another user's calendar, a meeting invitation can be sent and a confirmation can be received via instant messaging, rather than through email.
Instant Messaging ScenarioAlthough illustrated and described with only two individuals participating in an instant messaging session, it is recognized that the techniques described herein may also be applied to scenarios in which three or more individuals are participating in an instant messaging session.
User InterfaceIn an exemplary implementation, if the instant messaging session includes three or more individuals, calendar sharing invitations may be sent to each of the users. Alternatively, a user may specify which instant messaging session participants to include in a calendar sharing session.
In the illustrated example, shared calendar area 412 has a “Shared Calendars” heading. In an alternate implementation, the heading may be dynamically generated to include, for example, the name or names of users whose calendar data is being displayed.
Menu bar 406 may include several selectable items, such as new meeting item 416, day item 418, week item 420, go to date item 422, and sharing item 424. In an exemplary implementation, when a user selects new meeting item 416, a screen is displayed that enables a user to schedule a new meeting to be added to the displayed calendars. Selection of new meeting item 416 is described in further detail below with reference to
Day item 418 and week item 420 enable a user to toggle the calendar display between a day-at-a-time view and a week-at-a-time view. The illustrated examples are shown with day item 418 selected.
Selection of go to date item 422 enables a user to select another day's calendar information to be displayed. Similarly, selection of the arrows on either side of date indicator 408 cause a next or previous day's calendar information to be displayed (or the next/previous week's information, if the current view is a week view). Selection of go to date item 422 is described in further detail below with reference to
Selection of sharing item 424 enables a user to select a level of detail associated with their calendar that is displayed to others. Selection of sharing item 424 is described in further detail below with reference to
As described above,
In the display being shown to Adam (illustrated in
If calendar data associated with three or more individuals is shared through an instant messaging session, current user calendar area 410 displays the calendar data associated with the current user and shared calendar area 412 displays the collective calendar data associated with all of the other users.
It is recognized that in alternate implementations, sharing menu 602 may include more or fewer options than those illustrated. For example, a read/write menu item, when selected, may grant other users permission to directly modify a user's calendar data, without requiring specific confirmation from the data owner.
Menu bar 802 includes a send option and a cancel option. When a user selects the send option, an invitation to accept the new meeting is sent via the instant messaging session to the other individuals who are participating in the current instant messaging calendar sharing session. When a user selects the cancel option, the user's request to schedule a new meeting is cancelled.
Meeting definition area 804 includes tools that enable a user to define a subject, location, start date and time, and end date and time to be associated with a new meeting. Meeting definition area 804 may also include tools that enable a user to record additional notes about the meeting and specify a category for the meeting (e.g., personal or business). Furthermore, meeting definition area 804 may also include tools that enable a user to specify how the meeting is to appear to the user and to any other users with whom the user shares his calendar. For example, the show time as drop down list allows the user to select how the meeting time is to appear on the user's calendar. Options may include, for example, busy, out of the office, free, or tentative. Another example may be a private checkbox that, if checked, indicates that the meeting is not to appear to other users with whom the user's calendar may be shared.
Reminder area 806 includes tools that enable the user to indicate whether and how the user wants to be reminded of the meeting. For example, a user may choose to be reminded by email (at a specified email address) a particular period of time before the meeting is scheduled to begin. Additionally, a user may choose to be reminded via an online alerts system a specified period of time before the meeting is scheduled to begin.
Recurrence area 808 includes tools that enable a user to indicate a frequency with which a recurring meeting is to occur. Example frequencies may include, but are not limited to, daily, weekly, monthly, and yearly. Additional choices may also be available. For example, if the user selects monthly, additional choices may allow the user to specify that the meeting is to occur on a particular date every month (e.g., the 5th of every month), or a particular day every month (e.g., the second Tuesday of every month).
Once the user has defined the meeting, the user can select the send option in menu bar 802, to cause an invitation to the meeting to be sent to other participants of the current instant messaging calendar sharing session.
Adam causes a calendar sharing request to be sent from client device 1206 to client device 1208, as represented by arrow 1302.
In the described implementation, Adam and Bob each have calendar data stored on calendar server 1204. In the described exemplary implementation, the calendar data is password protected to ensure that only authorized individuals can view and/or modify an individual's calendar. Accordingly, after an invitation to begin a calendar sharing session has been sent and accepted, instant messaging applications on client devices 1206 and 1208 each transmit a request to share each respective user's calendar data to calendar server 1204. For example, as represented by arrow 1306, client device 1208 sends a calendar sharing request to calendar server 1204. Similarly, as represented by arrow 1308, client device 1206 sends a calendar sharing request to calendar server 1204. Calendar server 1204 sends back to client device 1208, an encrypted key that can be used to access Bob's calendar data (represented by arrow 1310). Similarly, calendar server 1204 sends back to client device 1206, an encrypted key that can be used to access Adam's calendar data (represented by arrow 1312). The encrypted keys are then exchanged via the instant messaging session, as represented by arrows 1314 and 1316, thereby granting each user access to the other's calendar data. That is, Adam's key is transmitted to Bob, thereby granting Bob access to Adam's calendar information; and Bob's key is transmitted to Adam, thereby granting Adam access to Bob's calendar information. If three or more users are participating in the calendar sharing session, then data access keys may be exchanged among all of the participants. After the keys are exchanged, the keys are registered with calendar server 1204. For example, the instant messaging application on client 1208 sends a request 1318 to calendar server 1204. The request 1318 includes an access control list (ACL), which is a store of keys, along with the new key, which provides access to Adam's calendar. In an exemplary implementation, the ACL is stored and transmitted as a cookie, and the new key is transmitted as part of a URL. Calendar server 1204 updates the received ACL, removing any expired keys and adding the new key. Calendar server 1204 then returns an updated ACL cookie, represented by arrow 1320. A similar exchange occurs between client device 1206 and calendar server 1204, as illustrated by arrows 1322 and 1324. In the described exemplary implementation, the key registration is performed by calendar server 1204 because, for security reasons, the client is not trusted with the information necessary to decode and encode individual keys or sets of keys in the ACL cookie.
Although not illustrated in
Arrow 1504 represents transmission of data from calendar server 1204 to client device 1206 that directs client device 1206 to display a user interface screen that enables a user to define a new meeting. An example of such a user interface screen is described above with reference to
As described above with reference to
A meeting invitation (represented by arrow 1510) is then transmitted from client device 1206 to client device 1208 via the previously established instant messaging session. When client device 1208 receives the meeting invitation data, the data is forwarded to calendar server 1204 (as represented by arrow 1512). Calendar server then uses the meeting invitation data to look up the meeting details, and, as represented by arrow 1514, transmits back to client device 1208, data to generate a meeting RSVP user interface screen. An example meeting RSVP user interface screen is described above with reference to
As described above with reference to
In the illustrated example, Bob accepts a meeting that has been scheduled by Adam. For example, Bob may select the accept button 902 as described above with reference to
When calendar server 1204 receives the meeting acceptance notification, calendar server updates data associated with both users' calendars to indicate that the meeting has been scheduled and accepted. Calendar server 1204 then transmits meeting summary data to client device 1208, as represented by arrow 1606. The received meeting summary data may then be displayed, for example, as illustrated in
When client device 1206 receives the meeting acceptance notification (represented by arrow 1604), client device 1206 transmits a request for a meeting summary (represented by arrow 1608) to calendar server 1204. In response to receiving the request for a meeting summary, calendar server 1204 transmits meeting summary data to client device 1206, as represented by arrow 1610. The received meeting summary data may then be displayed, for example, as illustrated in
In the illustrated example, Bob declines a meeting that has been scheduled by Adam. For example, Bob may select the decline button 906 as described above with reference to
When client device 1206 receives the meeting declination notification 1704, client device 1206 transmits a request to delete the meeting (represented by arrow 1708) to calendar server 1204. In response to receiving the request to delete the meeting, calendar server 1204 removes the meeting from Adam's and Bob's calendars, and transmits summary data associated with the declined meeting to client device 1206, as represented by arrow 1710. The received meeting summary data may then be displayed, for example, as illustrated in
Communication interface 1806 enables client device 1802 to communicate with other computing systems, such as instant messaging server 1202 and calendar server 1204. In an exemplary implementation, communication interface 1806 supports communication via an HTTP protocol.
Instant messaging application 1814 is configured to communicate (via communication interface 1806) with instant messaging server 1202 to establish an instant messaging session among two or more users. Instant messaging application 1814 is further configured to communicate with calendar server 1204 when a user, through an established instant messaging session, requests to participate in a calendar sharing session. In an exemplary implementation, instant messaging application 1814 includes or utilizes an HTTP client that is capable of receiving, storing, and sending cookies. Instant messaging application 1814 provides a user interface that enables a user to send and receive instant messaging communications. Instant messaging application 1814 also provides a user interface that enables a user to participate in a calendar sharing session within an established instant messaging session.
Calendar ServerCommunication interface 1904 enables calendar server 1204 to communicate with other computing devices, such as client device 1802.
Calendar data repository 1912 is stored in memory 1906 and maintains calendar data for users of calendar server 1204. For example, a calendar data service supported by calendar server 1204 may be offered as a subscription service.
Data access authenticator 1910 verifies that users requesting access to calendar data stored in calendar data repository 1912 are authorized to access the data they are requesting. In an exemplary implementation, data access authenticator 1910 authenticates a user via a user name and password, or some other technique. Once a user is authenticated, the user can access their own calendar data and/or request encrypted keys to share their calendar data with others. Upon request, data access authenticator 1910 generates encrypted keys for authenticated users of calendar server 1204. The encrypted keys can then be shared with other users. The encrypted keys can then be included in any user request to access data stored in calendar data repository 1912. When a user request is received to access another user's data in calendar data repository 1912, data access authenticator 1910 verifies that the request includes a valid key before granting the user access to the requested data.
In an exemplary implementation, data access authenticator 1910 generates an encrypted key when a user submits a calendar share request. The encrypted key may be set to expire after a specific period of time, such as 30 minutes. Additionally, the encrypted key may be associated with the current instant messaging session, so that when a user leaves the instant messaging session, any keys to other user's calendars that the user obtained while in the instant messaging session become invalid.
Data access authenticator 1910 may be configured to direct a client instant messaging application to automatically request a new key if a key expires while the user is still participating in the instant messaging session. Similarly, data access authenticator 1910 may be configured to direct a client instant messaging application to automatically request a new key if user-configured permissions are changed. For example, if a user has distributed keys to other users and then changes permissions such that other users can see full details of the user's calendar, rather than indicators of whether the user is free or busy, new keys may be automatically requested and re-distributed.
In an exemplary implementation, keys are stored in a cookie that is maintained on the client devices. When an instant messaging application requests data from calendar server 1204, the cookie is sent with the request. Data access authenticator 1910 may be configured to add keys to a user's cookie, thereby granting the user access to additional data. Additionally, data access authenticator 1910 may be configured to remove expired keys from a user's cookie.
Calendar Sharing MethodAt blocks 2002 and 2004, an instant messaging session is established between User A and User B. For example, User A may initiate an instant messaging session with User B through an instant messaging client that is installed on User A's computer system. Alternatively, User B may initiate the instant messaging session. Techniques for establishing an instant messaging session are well-known to those skilled in the art.
At block 2006, User A invites User B to participate in a calendar sharing session. For example, as described above with reference to
At block 2008, User B accepts the invitation to participate in a calendar sharing session. For example, as described with reference to
At block 2010, User A's client device requests and receives a key that can be used to access User A's calendar data. For example, as represented by arrow 1308 in
Similarly, at block 2012, User B's client device requests a key that can be used to access User B's calendar data. For example, as represented by arrow 1306 in
At blocks 2014 and 2016, the keys are exchanged. That is, at block 2014, User A's key is sent through the instant messaging session to User B. Similarly, at block 2016, User B's key is sent through the instant messaging session to User A.
At blocks 2018 and 2020, the exchanged keys are registered. For example, as described above with reference to
In an exemplary implementation, display preferences associated with the initiating user (e.g., User A) may be applied to data displayed to User B. In such an implementation, although not illustrated in
At blocks 2022 and 2024, User A's client device and User B's client device each request calendar data from the calendar server. Such requests are illustrated in
At blocks 2026 and 2028, calendar data is returned from the calendar server in response to the requests. An example of this data transmission is illustrated in
At blocks 2102 and 2104, an instant messaging calendar sharing session is established between User A and User B. For example, an instant messaging calendar sharing session may be established as described above with reference to
At block 2106, User A schedules a meeting via the calendar sharing session. For example, as described above with reference to
At block 2108, User A's client device uses the established instant messaging session to transmit an invitation to attend the meeting to User B. For example, when User A selects a Send button (as described above with reference to
At block 2110, User B receives the meeting invitation via the instant messaging session, as illustrated by arrow 1510 in
At block 2112, User B accepts the meeting invitation. For example, as described above with reference to
At block 2114, User A receives notification that User B has accepted the scheduled meeting. For example, as illustrated in
At blocks 2116 and 2118, User A and User B each receive summary data associated with the scheduled meeting. For example, as illustrated in
At blocks 2202 and 2204, an instant messaging calendar sharing session is established between User A and User B. For example, an instant messaging calendar sharing session may be established as described above with reference to
At block 2206, User A schedules a meeting via the calendar sharing session. For example, as described above with reference to
At block 2208, the established instant messaging session is used to transmit an invitation to attend the meeting to User B. For example, when User A selects a Send button (as described above with reference to
At block 2210, User B receives the meeting invitation via the instant messaging session, as illustrated with arrow 1510 in
At block 2212, User B declines the meeting invitation. For example, as described above with reference to
At block 2214, User A receives notification that User B has declined the scheduled meeting. For example, as illustrated in
At block 2216, User A receives summary data associated with the declined meeting. For example, as illustrated in
At block 2218, User B receives shared calendar data. For example, as illustrated in
At block 2302, a calendar server receives a request on behalf of a first user for a key to access data associated with the first user. For example, as described above with respect to
At block 2304, calendar server 1204 authenticates the received request. For example, a user name and password may be required to verify that the user requesting the key is the user who is associated with the data that can be accessed with the key. It is recognized that any type of user authentication may be used to verify the identity of the user for whom the request is being submitted.
At block 2306, calendar server 1204 determines whether or not the request has been authenticated. If the request is not authenticated (the “No” branch from block 2306), then at block 2308, calendar server 1204 returns an error.
On the other hand, if the request is authenticated (the “Yes” branch from block 2306), then at block 2310, calendar server 1204 generates a key that enables access to data associated with the authenticated user. For example, as illustrated in
At block 2312, calendar server 1204 transmits the generated key to the requesting application. For example, if the request is received from an instant messaging application, the generated key is transmitted back to the instant messaging application.
After some period of time, at block 2314, calendar server 1204 receives a request for data from a second user. The request includes the key that was generated to enable access to the first user's data.
At block 2316, calendar server 1204 validates the key. For example, calendar server 1204 may verify that an expiration period associated with the key has not passed.
At block 2318, calendar server 1204 determines whether or not the key is valid. If calendar server 1204 determines that the key is not valid (the “No” branch from block 2318), then at block 2320, calendar server 1204 returns an error. In an exemplary implementation, if the key was submitted as part of a cookie, then calendar server 1204 may modify the cookie to remove the invalid key. Alternatively, calendar server 1204 may also return data that instructs the requesting application to request a new, valid key.
On the other hand, if calendar server 1204 determines that the key is valid (the “Yes” branch from block 2318), then at block 2322 calendar server 1204 returns the requested data associated with the first user in response to the request received on behalf of the second user.
CONCLUSIONThe techniques described above enable data sharing and support for related tasks within an instant messaging session. Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.
Claims
1. A method comprising:
- establishing an instant messaging session between a first client device and a second client device;
- sending a request from the first client device to a calendar server for a first key to access calendar data of a first user associated with the first client device;
- receiving the first key at the first client device from the calendar server;
- transmitting the first key via the instant messaging session from the first client device to the second client device;
- receiving a second key from the second client device via the instant messaging session, the second key permitting the first client device to access calendar data of a second user associated with the second client device;
- receiving, from the second client device, display preferences specifying a manner of displaying the calendar data of the second user on a display interface of the first client device;
- applying the display preferences specifying the manner of displaying the calendar data of the second user to the calendar data of the first user; and
- simultaneously displaying the calendar data of the first user and the calendar data of the second user on the display interface of the first client device.
2. The method of claim 1, wherein the display preferences include language, time zone, week start day, start hour for a day view, end hour for the day view, or a combination thereof.
3. The method of claim 1, wherein the display interface further includes shared calendar data of one or more additional users involved in the instant messaging session.
4. The method of claim 1, further comprising providing an instant messaging user interface at the first client device, the instant messaging user interface including an instant messaging conversation, at least a portion of the calendar data of the first user, at least a portion of the calendar data of the second user, a meeting definition area, a reminder area, or a combination thereof.
5. The method of claim 4, wherein the instant messaging user interface includes a private checkbox that when checked, indicates that particular information is not to appear to additional users, wherein the first user is sharing calendar data with the additional users.
6. The method of claim 4, wherein the reminder area includes a selectable option to remind the first user of a meeting via email.
7. The method of claim 4, wherein the reminder area includes a selectable option to remind the first user of a meeting via an online alerts system.
8. The method of claim 4, wherein the meeting definition area allows the first user to schedule a meeting.
9. The method of claim 1, further comprising automatically changing the simultaneous display of the calendar data of the first user and the calendar data of the second user on the display interface of the first client device in accordance with a calendar navigation implemented by the second user.
10. The method of claim 1, wherein the calendar data of the first user and the calendar data of the second user are displayed in separate areas of the display interface.
11. One or more computer-readable media comprising computer-readable instructions that, when executed, perform operations comprising:
- establishing an instant messaging session between a first client device and a second client device;
- sending a request from the first client device to a calendar server for a first key to access calendar data of a first user associated with the first client device;
- receiving the first key at the first client device from the calendar server;
- transmitting the first key via the instant messaging session from the first client device to the second client device;
- receiving a second key from the second client device via the instant messaging session, the second key permitting the first client device to access calendar data of a second user associated with the second client device;
- receiving, from the second client device, display settings for the calendar data of the second user;
- applying the display settings for the calendar data of the second user to the calendar data of the first user; and
- simultaneously displaying the calendar data of the first user and the calendar data of the second user on a display interface of the first client device.
12. The one or more computer-readable media of claim 11, wherein the display settings include a language setting, a time zone setting, a week start day setting, a start hour for a day view setting, an end hour for the day view setting, or a combination thereof.
13. The one or more computer-readable media of claim 11, wherein the display interface further includes shared calendar data of one or more additional users involved in the instant messaging session.
14. The one or more computer-readable media of claim 11, further comprising providing an instant messaging user interface at the first client device, the instant messaging user interface including an instant messaging conversation, at least a portion of the calendar data of the first user, at least a portion of the calendar data of the second user, a meeting definition area, a reminder area, or a combination thereof.
15. The one or more computer-readable media of claim 14, wherein the instant messaging user interface includes a private checkbox that when checked, indicates that particular information is not to appear to additional users, wherein the first user is sharing calendar data with the additional users.
16. The one or more computer-readable media of claim 11, further comprising automatically changing the simultaneous display of the calendar data of the first user and the calendar data of the second user on the display interface of the first client device in accordance with a calendar navigation implemented by the second user.
17. The one or more computer-readable media of claim 11, wherein the calendar data of the first user and the calendar data of the second user are displayed in non-overlapping areas of the display interface.
18. A system comprising:
- one or more processors; and
- a memory coupled to the one or more processors, the memory storing instructions executable by the one or more processors to: establish an instant messaging session between the system and a computing device; send a request from the system to a calendar server for a first key to access calendar data of a first user associated with the system; receive the first key at the system from the calendar server; transmit the first key via the instant messaging session from the system to the computing device; receive a second key from the computing device via the instant messaging session, the second key permitting the system to access calendar data of a second user associated with the computing device; receive, from the computing device, display settings for the calendar data of the second user; apply the display settings for the calendar data of the second user to the calendar data of the first user; and simultaneously display the calendar data of the first user and the calendar data of the second user on a display interface of the system.
19. The system of claim 18, wherein the display settings include a language setting, a time zone setting, a week start day setting, a start hour for a day view setting, an end hour for the day view setting, or a combination thereof.
20. The system of claim 18, wherein the calendar data of the first user and the calendar data of the second user are displayed in separate areas of the display interface.
Type: Application
Filed: Jul 30, 2012
Publication Date: Nov 15, 2012
Applicant: MICROSOFT CORPORATION (Redmond, WA)
Inventors: Imran Qureshi (Milpitas, CA), Evan Gridley (Sunnyvale, CA)
Application Number: 13/561,343
International Classification: G06F 15/16 (20060101); G06F 3/01 (20060101);