Scheduling meetings via email clients is not intuitive or easy for email users. Typically, when an email client sends an appointment for a meeting, the user needs to know the meeting room name to search for it. Moreover, the meeting room name may not be labeled within the email system with a nomenclature that the user is aware of. That is, the meeting room may be labeled within the email system with a name that is different from how the employees of an enterprise refer to it as.
Further, even if the user knows the name of the meeting room, the user may not be aware of its location within the enterprise. Many modern enterprises span multiple buildings and multiple geographic locations. So, not being able to rapidly know the location of a meeting room can be a considerable amount of consternation for employees. Generally what happens in these situations is that an employee that desires to know the location of a meeting room locates the organizer's name in the employee directory and either calls the organizer or an assistant of the organizer to get directions to the meeting room. After about the second call received requesting the meeting room's location, the assistant usually sends out a global second email providing specific directions to all the members of the meeting. All this is time consuming and is a waste of enterprise resources.
Thus, what are needed are techniques that allow for improved meeting room integration within calendar systems.
In various embodiments, techniques for visual integration of meeting space in calendar systems are presented. More specifically, and in an embodiment, a method is provided visually integrating meeting space within a calendar system. That is, an interactive map of an enterprise is presented when a meeting room is requested for a meeting. The interactive map is presented within a calendar application of an email client. An availability of the meeting room is depicted within a calendar application; the meeting room is selected by the user from the interactive map. The meeting is scheduled with the meeting room for a time slot that includes the availability of the meeting room and other attendees to the meeting.
As used herein a “calendar application” and “calendar system” refer to a suite of executable software services that are integrated within an email client. The phrases “calendar application” and “calendar system” can be used interchangeably and synonymously herein. An email system includes one or more email servers that communicate with a plurality of email clients. Each user of an email system accesses the email system via an email client. The calendar application or system is integrated within the email clients of the email system.
A “map” refers to a graphical or image presentation of an enterprise and its facilities, such as buildings, rooms, cubicles, meeting rooms, parking lot, floors, hallways, restrooms, stairs, elevators, recreation rooms, boiler rooms, closets, etc. In a sense, the map may be viewed as a blueprint of a single building or an entire campus of buildings. One or more maps can be linked together so as to include streets and roadways between buildings or campuses or between a particular address to a particular room within a building of an enterprise.
An “interactive map” refers to hypertext linkages that are accessible by activating locations within a map. The linkages can refer to other maps or to information, such as text, other images, other graphical elements, video, and/or audio.
According to an embodiment, the techniques presented herein are implemented in products associated and distributed by Novell®, Inc. of Provo, Utah.
Of course, the embodiments of the invention can be implemented in a variety of architectural platforms, emails systems, and/or calendar systems. Any particular architectural layout or implementation presented herein is provided for purposes of illustration and comprehension only and is not intended to limit various aspects of the invention.
It is within this initial context, that various embodiments of the invention are now presented with reference to the
The calendar service presents the perspective of processing from when a user creates a calendar entry within a calendar system for a meeting.
At 110, the calendar service presents an interactive map of an enterprise when a meeting room is requested for a meeting. The interactive map is presented within a calendar application of an email client. That is, the calendar application is integrated and processes as a subservice within the email client.
According to an embodiment, at 111, the calendar service provides physical dimensions of the meeting room and/or seating capacity for the meeting room within the calendar application when the user selects of clicks the meeting room within the interactive map. So, a user can rapidly determine whether a particular enterprise meeting room has sufficient physical dimensions and seating capacity for a group that is to be invited to the proposed meeting being created via the calendar system with the assistance of the calendar service.
In another cases, at 112, the calendar service provides resources available with the meeting room. This is done within the calendar application when the user selects the meeting room. Some resources can include but are not limited to: a whiteboard, a teleconference line, a network connection, a wireless connection, a projector, a restroom, drinks, etc. In this manner, the interactive map can provide detail information about the proposed meeting room that is being scheduled with the proposed meeting.
In some cases, the interactive map may allow a user to right click or select an option that shows a calendar and booked and available time slots for days listed in the calendar. This visually allows a user to see when the meeting room is available and not available. This is a visual presentation that is activated from the interactive map and in some cases presented as an integrated view within the interactive map.
At 120, the calendar service depicts within the calendar application an availability of the meeting room, which is selected by the user from the interactive map. That is, the user clicks on the meeting room that is depicted within the interactive map to see the availability for a desired time slot that the user wants to use for the meeting. Typically, this is not the manner that a user selects a meeting room, with most traditional calendar systems the meeting room is listed as a contact with an enterprise calendar system and users have to know the contact name to select a particular meeting room. Moreover, there is usually few if any details listed with the meeting contact that provides sufficient location and other details that would be useful to a scheduler of a meeting. These problems are solved herein because the meeting room is selected via an interactive map. Once the selection is made the traditional or underlying contact name for the meeting room can be plugged into the calendar systems, but the user does not have to know the contact name for the meeting room a priori.
At 130, the calendar service schedules the meeting with the meeting room for a time slot that includes the availability of the meeting room and other attendees to the meeting.
According to an embodiment, at 131, the calendar service sends email invitations to other attendees when the meeting is scheduled via the email client and simultaneously books the time slot for the meeting room within the calendar system.
Continuing with the embodiment of 131 and at 132, the calendar service includes a link within the email invitations that provide the interactive map. So, each email invitation to a particular attendee of the meeting includes a link to the interactive map that the attendee can activate to see a map of the facilities for an enterprise and to see visually where the meeting room is located.
Also continuing with the embodiment of 131 and at 133, the calendar service customizes each email invitation to a particular attendee. Each customized email invitation includes directions from a particular location of a particular attendee to the meeting room. Thus, each attendee can receive text directions from their location to the meeting room. For example, an attendee in a first building of a campus can receive explicit written directions for attending the meeting to a different building within the campus. In some cases, an estimated travel time to the meeting based on the attendee's location can also be provided with the email invitation. In fact, this estimated travel time can even be integrated into the user's calendar system on the user's calendar so that the user receives a notice to leave for the meeting to account for the estimated travel time to the meeting room.
Still continuing with the embodiment at 131 and at 134, the calendar service presents the interactive map within the email invitations with the location of the meeting room highlighted within the presented interactive map. The interactive map can be graphically embedded in the email invitations. In some cases, a highlighted path can be shown from each particular attendee's present location to the meeting room location within the interactive map.
The email service represents a processing perspective from within an email system or more particularly an email client of a particular user. So, the calendar service of the method 100 from the
At 210, the email service receives, via an email, a meeting request for a time slot and at a particular meeting room. An attendee receives the email as a result of an invitation to a meeting that was created in the manner discussed above with reference to the method 100 of the
At 220, the email service permits a map to be viewed via the email. The map was generated with the meeting request from an enhanced calendar application, such as the calendar service discussed above with reference to the method 100 of the
For example, at 221, the email service provides text directions from a location of an attendee that is the recipient of the email to the particular meeting room location for the meeting room.
In another case, at 222, the email service provides the map as an attachment to the email or as a link that when activated presents the map within a World-Wide Web (WWW) browser.
In yet another situation, at 223, the email service provides the map as an interactive map that the recipient (attendee) of the email can interact with to gather additional information for the meeting room.
Continuing with the embodiment of 223 and at 224, the email service presents the physical dimensions and/or seating capacity for the meeting room when the attendee that receives the email clicks the map on a location that designates the meeting room.
Also continuing with the embodiment of 223 and at 225, the email service presents resources available within the meeting room when the attendee that receives the email clicks the map on a location that designates the meeting room.
In yet continuing with the embodiment of 223 and at 226, the email service permits an attendee to identify a present location for the attendee within the map and in response thereto the interactive map draws a path from the present location to a meeting room location that represents a geographical position within an enterprise for the meeting room. This can be done within the email or external from the email, such as when the interactive map is presented within a WWW browser.
The visual meeting space calendar system 300 includes an interactive map 301 and a calendar service 302. Each of these components and their interactions with one another will now be discussed in turn.
The interactive map 301 is implemented as instructions within a computer-readable storage medium that processes on a device of the network (such as a modern computer, etc.). Example aspects of the interactive map 301 and its features were discussed in detail above with reference to the methods 100 and 200 of the
The interactive map 301 is automatically activated within a calendar application of an email client by the calendar service 302. The interactive map 301 visually depicts the meeting rooms and other rooms and physical characteristics of an enterprise.
According to an embodiment, the interactive map 301 includes links to other interactive maps for other facilities of an enterprise. So, external geographical sites can be integrated via links from the interactive map 301 to other interactive maps.
In another case, the interactive map 301 includes at least one link to a video camera that provides a real-time feed to view the particular meeting room. Much like a live webcam, a user can, via the interactive map 301, see real time footage of the meeting room being used for a particular meeting.
In a particular situation, the interactive map 301 is included within emails sent to attendees for the particular meeting. Examples of this were presented above with reference to the method 200 of the
In still another situation, the interactive map 301 include links that when activated include information describing resources of each of the meeting rooms, seating capacities for each of the meeting rooms, and/or physical dimensions for each of the meeting rooms.
The calendar service 302 is also implemented as instructions within a computer-readable storage medium and processes on a device of the network. Example aspects of the calendar service 302 and its features were discussed in detail above with reference to the methods 100 and 200 of the
The calendar service 302 interacts with and depicts within the interactive map 301 meeting rooms of a facility for an enterprise. The calendar service 302 also depicts within the interactive map 301 availability of the meeting rooms and locations for the meeting rooms within the facility.
A scheduler (attendee or user creating a meeting) then selects a particular meeting room for a particular meeting being scheduled by the scheduler. This is done via the calendar application by activating a link for the particular meeting room at a particular time slot depicted and accessible from the interactive map. The scheduler visually sees the meeting room and picks a time slot for the meeting via the interactive map 301.
In an embodiment, the calendar application and the calendar service 302 are integrated within an email system.
The visual meeting space calendar system 400 is another and in some cases enhanced perspective to the visual meeting space calendar system 300 represented by the
The visual meeting space calendar system 400 includes an email client 401 and a calendar system 402. Each of these will now be discussed in turn.
The email client 401 is implemented in a computer-readable storage medium and processes on a machine (computer or processor-enabled device) of the network. Example aspects of the enhanced email client 401 were presented above with respect to the methods 100 and 200 of the
The email client 401 integrates the calendar system 402 into the email client 401. So, visual calendar features are available via the calendar system 402 that is integrated into the email client 401.
The calendar system 402 is implemented in a computer-readable storage medium and also processes on a device of the network. Example aspects of the enhanced calendar system 402 were presented above in detail with reference to the
The calendar system 402 permits a meeting room to be located, scheduled, and viewed via a map of a facility where that meeting room is physically located. The map shows the meeting room relative to all rooms of the facility.
In an embodiment, the map is an interactive map that permits a user to view an availability of the meeting room, discover resources associated with the meeting room, schedule the meeting room to a meeting for a particular time slot, and acquire directions from a present location to the meeting room.
In another case, the map is included with emails sent to attendees of a particular meeting that is scheduled via the calendar system 402 for the meeting room.
In still another situation, the emails include directions from locations of each of the attendees to a meeting room location for the meeting room and paths for the directions are highlighted within the map.
According to an embodiment, the calendar system 402 also includes a search facility/service/mechanism that a user to search for a particular meeting room that has user-defined criteria. The search criteria include such things as user-defined: meeting room seating capacity and/or meeting room equipment or resources available and desired by the user. The search results displayed by the calendar system 402 can assist the user in locating the closest meeting rooms meeting the user-defined search criteria within the map, such that by activating a highlighted link within the map the user can visually see the meeting room. In another case, the links can be presented in a text window that when activated takes the user to the map location for the desired meeting room and/or presents images of the meeting room.
The above description is illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of embodiments should therefore be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
The Abstract is provided to comply with 37 C.F.R. §1.72(b) and will allow the reader to quickly ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
In the foregoing description of the embodiments, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting that the claimed embodiments have more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Description of the Embodiments, with each claim standing on its own as a separate exemplary embodiment.
This application is a divisional of U.S. patent application Ser. No. 12/271,176, filed Nov. 14, 2008, now issued as U.S. Pat. No. 8,799,048, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4857840 | Lanchais | Aug 1989 | A |
5124912 | Hotaling et al. | Jun 1992 | A |
5948040 | DeLorme et al. | Sep 1999 | A |
6480830 | Ford et al. | Nov 2002 | B1 |
7027995 | Kaufman et al. | Apr 2006 | B2 |
7036128 | Julia et al. | Apr 2006 | B1 |
7231423 | Horstmann et al. | Jun 2007 | B1 |
7446766 | Moravec | Nov 2008 | B2 |
7707256 | Rollin et al. | Apr 2010 | B2 |
7720893 | Boudreau et al. | May 2010 | B2 |
7913179 | Sheha et al. | Mar 2011 | B2 |
8799048 | Bisht | Aug 2014 | B2 |
20020184063 | Kaufman et al. | Dec 2002 | A1 |
20030191772 | Schaumann et al. | Oct 2003 | A1 |
20030217073 | Walther et al. | Nov 2003 | A1 |
20030229441 | Pechatnikov et al. | Dec 2003 | A1 |
20040054428 | Sheha et al. | Mar 2004 | A1 |
20040153334 | Dione | Aug 2004 | A1 |
20040172277 | Dione | Sep 2004 | A1 |
20050149561 | Hodnett et al. | Jul 2005 | A1 |
20050190053 | Dione | Sep 2005 | A1 |
20050222890 | Cheng et al. | Oct 2005 | A1 |
20050227712 | Estevez et al. | Oct 2005 | A1 |
20050273372 | Bowne et al. | Dec 2005 | A1 |
20050289524 | McGinnes | Dec 2005 | A1 |
20060048066 | O'Rourke | Mar 2006 | A1 |
20060149778 | Clover | Jul 2006 | A1 |
20060288010 | Chen et al. | Dec 2006 | A1 |
20070136218 | Bauer et al. | Jun 2007 | A1 |
20070139191 | Quatro | Jun 2007 | A1 |
20070149214 | Walsh et al. | Jun 2007 | A1 |
20070197229 | Kalliola et al. | Aug 2007 | A1 |
20070233695 | Boudreau et al. | Oct 2007 | A1 |
20070264968 | Frank et al. | Nov 2007 | A1 |
20080036778 | Sheha et al. | Feb 2008 | A1 |
20080046170 | DeGrazia | Feb 2008 | A1 |
20080109718 | Narayanaswami | May 2008 | A1 |
20080114840 | Rollin et al. | May 2008 | A1 |
20080133524 | Ryan et al. | Jun 2008 | A1 |
20080147472 | Hitz | Jun 2008 | A1 |
20080183483 | Hart | Jul 2008 | A1 |
20080189197 | Allanson et al. | Aug 2008 | A1 |
20080195608 | Clover | Aug 2008 | A1 |
20090006994 | Forstall et al. | Jan 2009 | A1 |
20090024442 | Brink et al. | Jan 2009 | A1 |
20090055234 | Li et al. | Feb 2009 | A1 |
20090125367 | Brink et al. | May 2009 | A1 |
20090144143 | Iyer | Jun 2009 | A1 |
20090194137 | Friedman et al. | Aug 2009 | A1 |
20090307043 | Cholewinski | Dec 2009 | A1 |
20090327227 | Chakra et al. | Dec 2009 | A1 |
20100082239 | Hardy et al. | Apr 2010 | A1 |
20100125478 | Bisht | May 2010 | A1 |
Entry |
---|
Ashbrook, Daniel, and Thad Starner. “Using GPS to learn significant locations and predict movement across multiple users.” Personal and Ubiquitous Computing 7.5 (2003): 275-286. |
Ashbrook, Daniel, and Thad Starner. “Learning significant locations and predicting user movement with GPS.” Wearable Computers, 2002.(ISWC 2002). Proceedings. Sixth International Symposium on. IEEE, 2002. |
Kincaid, Christine M., Pierre B. Dupont, and A. Roger Kaye. “Electronic calendars in the office: an assessment of user needs and current technology.”ACM Transactions on Information Systems (TOIS) 3.1 (1985): 89-102. |
Tullio, Joe, et al. “Augmenting shared personal calendars.” UIST. vol. 2. 2002. |
Kjeldskov, Jesper, et al. “Designing TramMatena context-aware mobile system supporting use of public transportation.” Proceedings of the 2003 conference on Designing for user experiences. ACM, 2003. |
Knoblock, Craig A., et al. “Mixed-initiative, multi-source information assistants.”Proceedings of the 10th international conference on World Wide Web. ACM, 2001. |
Ashbrook, Daniel, et al., “Learning significant locations and predicting user movement with GPS”, Wearable Computers, Proceedings. Sixth International Symposium on. IEEE, (2002). |
Ashbrook, Daniel, et al., “Using GPS to learn significant locations and predict movement across multiple users”, Personal and Ubiquitous Computing 7.5, (2003), 275-286. |
Kincaid, Christine M, et al., “Electronic calendars in the office: an assessment of user needs and current technology”, ACM Transactions on Information Systems, (1985), 89-102. |
Kjeldskov, Jesper, et al., “Designing TramMatena context-aware mobile system supporting use of public transportation”, Proceedings of the 2003 conference on Designing for user experiences, (2003). |
Knoblock, Craig A, et al., “Mixed-initiative, multi-source information assistants”, Proceedings of the 10th international conference on World Wide Web, (2001). |
Tullio, Joe, et al., “Augmenting shared personal calendars”, UIST. vol. 2, (2002). |
Number | Date | Country | |
---|---|---|---|
20140343978 A1 | Nov 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12271176 | Nov 2008 | US |
Child | 14448562 | US |