Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/10—Office automation; Time management
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/451—Execution arrangements for user interfaces

Definitions

• a client computer executing the presentation client application receives a presentation and is assigned a role.
• the client computer then provides a user interface ("UI") for viewing and interacting with the presentation that is based upon the assigned role.
• the role might be a projector role, a presenter role, an attendee role, a moderator role, a notetaker role, or another type of role.
• the UI might also be customized for the particular type of client computer that it is displayed upon. For instance, the UI might be customized for the particular screen size, available user input devices, and other features of the client computer upon which it is presented.
• the projector role is assigned to a client computer that is connected to an external display device, such as a projector or large monitor.
• a client computer assigned the projector role is configured to display a presentation on the external display device.
• the portion of the presentation to be displayed by a client computer that has been assigned the projector role may be defined by a client computer that has been assigned a presenter role.
• a client computer that has been assigned a presenter role is configured to display a UI that includes the presentation.
• the UI might also include elements to assist a presenter, such as presenter notes, a timer, and other UI elements.
• a moderator role might be assigned to a client computer operated by a meeting moderator.
• the UI presented by a client computer that has been assigned the moderator role might display the presentation along with additional UI elements for assigning roles for the other client computers participating in the presentation.
• the roles assigned by the moderator may then be synchronized to the other client computers.
• a client computer receives a new role, it updates its UI to reflect the newly assigned role.
• Other roles such as the presenter role, might include UI for assigning roles to other client computers.
• a notetaker role might be assigned to a client computer operated by an individual that has been assigned the task of taking shared notes for the meeting.
• the UI provided by a client computer that has been assigned the notetaker role might display the presentation along with additional UI elements for receiving text notes.
• the text notes may be synchronized to the other client computers.
• the text notes might be synchronized to a client computer that has been assigned the projector role and thereby displayed to the meeting participants.
• FIGURE 1 is a network diagram showing aspects of the various software components provided herein in embodiments
• FIGURE 2 is a data structure diagram showing aspects of an illustrative presentation state data structure utilized in embodiments disclosed herein;
• FIGURE 4 is a flow diagram showing aspects of the operation of a presentation client application in one embodiment disclosed herein.
• FIGURE 5 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing the embodiments presented herein.
• a presentation state that includes a presentation and other information is synchronized between one or more client computers executing a presentation client application.
• a client computer executing the presentation client application receives the presentation state, including the presentation, and is assigned a role.
• the client computer then provides a user interface ("UI") for viewing and interacting with the presentation that is based upon the assigned role.
• the role might be a projector role, a presenter role, an attendee role, a moderator role, a notetaker role, or another type of role.
• the UI might also be customized for the particular type of client computer that it is displayed upon. Additional details regarding the presentation state, the operation of the client computers, and the various roles will be provided below with regard to FIGURES 1-5.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
• the presentation client application 114 is the POWERPOINT presentation client application from MICROSOFT CORPORATION of Redmond, Washington. It should be appreciated that other presentation client applications from other vendors might also be utilized. It should also be appreciated that while the embodiments described herein are discussed in the context of a presentation client application 114 that performs the functionality described herein, the functionality presented herein might be performed by other software components. For instance, a standalone software component may be provided for performing the various functions described herein. Alternately, a Web page viewable within a Web browser application might perform the functionality described herein for providing role-based presentation views. Other implementations will be apparent to those skilled in the art.
• a server computer 104 is utilized in various embodiments presented herein.
• the server computer 104 comprises a standard server computer and is configured to execute a presentation server application 120.
• the presentation server application 120 is configured to communicate with the presentation client applications 114A-114E (which may be referred to singularly as the presentation client application 114) executing on the client computers 102A-102E (which may be referred to singularly as a client computer 102), respectively.
• the presentation server application 120 is configured to synchronize a presentation state 116 to each of the client computers 102A-102E.
• the presentation state 116 includes a presentation to be displayed by the presentation client applications 114A-114E.
• the presentation state 116 might also include other data that is synchronized to the client computers 102A-102E and displayed by the presentation client applications 114A-114E depending upon a role assigned to the particular client computer 102A-102E. Additional detail regarding this process will be provided below.
• the client computers 102A-102E and the server computer 104 are interconnected by way of a network 108.
• the network 108 may comprise any suitable computing network for establishing a communications connection between the client computers 102A-102E and the server computer 104. It should also be appreciated that although a single network 108 has been shown in FIGURE 1, multiple networks might be utilized. For instance, several of the client computers 102A-102E may be connected by way of a wireless network. Other of the client computers 102A-102E and the server computer 104 might be connected by way of a local area network or a wide area network that is connected to the wireless network.
• one or more of the client computers 102A- 102E might be located in a common location, such as a meeting room where a presentation is being given, and other of the client computers 102A-102E and the server computer 104 might be remotely located. In this manner, users of the client computers 102A-102E may view and interact with the presentation in the manner described herein whether they are physically located at the site of a presentation or in a remote location.
• each of the client computers 102A-102E may be assigned a role 118.
• the role 118 assigned to each of the client computers 102A-102E may be determined based upon the type of involvement that a user of each of the client computers 102A-102E will have in the presentation.
• the role 118 might also be assigned to a particular client computer 102 depending on the role that the client computer 102 will have during the presentation. For instance, in the example shown in FIGURE 1 , the client computer 102A has been assigned a projector role 118A.
• the projector role 118A is assigned to client computer 102 A that will provide output of the presentation to a projector 110 or other type of external display device.
• the presentation state 116 is synchronized to the client computer 102 A, which has been assigned the projector role 118A, the presentation identified by the user of the client computer 102B would be displayed by the projector 110.
• the client computer 102A-102E that has been assigned the presenter role 118B will determine the presentation and, more particularly, the portion of the presentation that should be displayed by the client computer 102A that has been assigned the projector role 118A.
• the client computer 102D has been assigned an attendee role 118D.
• the attendee role 118D is assigned to one or more of the client computers 102A-102D, such as the client computer 102D, that are utilized by attendees at a presentation.
• the presentation client application 114D is configured to display a UI suitable for use by an attendee.
• the UI presented by the client application 114D on a client computer 102D that has been assigned an attendee role 118D includes a UI for displaying a presentation and for receiving text notes from a user that may or may not be shared with other users.
• the client computer 102E has been assigned the notetaker role 118E.
• the notetaker role 118E is assigned to a client computer 102E operated by an individual that has been assigned the task of taking notes during a presentation.
• the presentation client application 114E executing on a client computer 102E that has been assigned the notetaker role 118E is configured to provide a UI for viewing and interacting with a presentation that is suitable for use by a note taker.
• the presentation client application 114E is configured to display the presentation to a user of the client computer 102E and to provide a user interface for receiving text notes.
• the text notes are added to the presentation state 116, which is then synchronized between the client computers 102A-102E.
• the text notes might be displayed on the projector 110 by the presentation client application 114A executing on the client computer 102 A that has been assigned the projector role 118.
• the presentation client application 114E executing on a client computer 102E that has been assigned a note taker role 118E might also provide other UI elements suitable for use by an individual that has been assigned the task of taking notes during a presentation.
• the roles 118A-118E shown in FIGURE 1 are merely illustrative and that other roles might be assigned to the various client computers 102A-102E.
• the UI displayed by the presentation client application 114 might also be customized based upon the type of client computer 102A-102E upon which the presentation client application 114 is executing. For instance, the UI might be customized for the particular screen size, available user input devices, and other hardware and software features of the client computer 102 upon which it is executing.
• the UI presented to users of the client computers 102A-102E might be customized based upon the role 118 that has been assigned to the respective client computer 102A-102E, and upon the particular hardware or software characteristics of the respective client computer 102A-102E. It should also be appreciated that, according to embodiments, a client computer 102 or user might be assigned two or more roles. For instance, a client computer 102A might be assigned a presenter role and a projector and/or moderator role.
• the presentation state 116 includes a presentation 202.
• the presentation 202 might include one or more slide decks, each of which includes one or more slides.
• the presentation 202 might also include state data indicating which of the slides should be currently displayed.
• the presentation client application 114E might include functionality for allowing users of the client computers 102A-102E to chat with one another by typing text messages, exchanging audio, and/or audio/video. These messages, which might be referred to herein as chat data 212, may be included in the presentation state 116 and synchronized among the client computers 102A-102E.
• FIGURE 3 is a flow diagram showing a routine 300 that illustrates aspects of the operation of the presentation server application 120 in one embodiment disclosed herein.
• the routine 300 proceeds to operation 306, where the server computer 104 receives the presentation 202 from the client computer currently assigned the presenter role 118B. The routine 300 then proceeds to operation 308, where the server computer 104 assembles the presentation state 116. This might include adding the presentation 202, presentation collateral 204, notes 206, questions 208, attendee list 210, chat data 212, and annotations 214 to the presentation state 116.
• routine 300 proceeds to operation 314, where the presentation server application 120 determines whether the presentation state 116 has been changed. If the presentation state 116 has been changed, the routine 300 proceeds to operation 316 where the server computer 104 updates that presentation state 116. The routine 300 then proceeds from operation 316 to operation 310 where the updated presentation state 116 is transmitted to the client computers 102A-102E.
• the routine 300 proceeds from operation 314 to operation 318.
• the server computer 104 determines whether a request has been received to terminate the current presentation. If not, the routine 300 proceeds to operation 312, described above, where additional changes to the presentation state 116 may be received and synchronized to the client computers 102A-102E. If the presentation is to be ended, the routine 300 proceeds from operation 318 to operation 320 where the client computers 102A-102E are disconnected from the server computer 104. Operation of the presentation server application 120 may then terminated. From operation 320, the routine 300 proceeds to operation 322, where it ends.
• routine 400 illustrates operation performed by the presentation client application 114 executing on the client computers 102A-102B.
• the routine 400 begins at operation 402, where the presentation client application 114 connects to the server computer 104.
• the routine 400 then proceeds to operation 404 where the presentation client application 114 receives the presentation state 116 from the server computer 104.
• the presentation client application 104 also receives an assignment of a role 118 from the server computer 104.
• the role may be specified in an attendee list 210 contained in the presentation state 116.
• the role 118 may also be specified in another manner.
• the routine 400 proceeds to operation 408 where the presentation client application 114 provides a UI for viewing and interacting with the presentation 202 based upon the role 118 assigned to the client computer 102 upon which the presentation client application 114 is executing.
• the presentation client application 114 may provide a UI that is customized for the particular hardware or software of the client computer 102 upon which it is executing.
• the routine 400 proceeds to operation 410, where the presentation client application 104 determines whether changes have been made to the presentation state 116. For instance, the presentation client application 114 may determine that notes 206, questions 208, chat data 212, or annotations 214 have been added to the presentation state 116 by a user of the client computer 102 upon which it is executing. If so, the routine 400 proceeds to operation 412 where the updated presentation state 116 may be transmitted to the server computer 104. Alternately, only the changed data may be transmitted to the server computer 104 for inclusion in the presentation state 116. If no changes have been made, the routine 400 proceeds to operation 414.
• the presentation client application 114 determines whether a new role has been received from the server computer 104. For instance, a presentation state 116 may be received with an updated attendee list 210 that indicates that the role for a particular client computer 102 has been changed. If the role has been changed, the routine 400 proceeds to operation 416, where the presentation client application 114 updates the user interface for viewing and interacting with the presentation 202 based upon the newly assigned role 118. For instance, during a presentation, an individual at the presentation may be an attendee for most of the presentation. During this time, the client computer 102D which they are operating will be assigned an attendee role 118D. At some point during the presentation, the attendee may be asked to become the presenter.
• the client computer 102D utilized by the attendee will be assigned the presenter role 118B.
• the UI provided by the presentation client application 114D will be modified to reflect the newly assigned role. In this manner, a user of the client computer 102D will be provided a UI suitable for presenting a presentation. It should be appreciated that other role changes may be processed in a similar fashion.
• routine 400 proceeds to operation 418 where a determination is made as to whether a user has requested to shut down the presentation client application 114. If not, the routine 400 proceeds to operation 410, described above, where the processing described above continues. If a request is received to shut down the presentation client application 114, the presentation client application 114 is disconnected from the server computer 104 and its execution is terminated. The routine 400 then proceeds to operation 420, where it ends.
• FIGURE 5 shows an illustrative computer architecture for a computer 500 capable of executing the software components described herein for role-based presentation views.
• the computer architecture shown in FIGURE 5 illustrates a conventional desktop, laptop computer, or server computer and may be utilized to execute the presentation client application 114 or any of the other software components described herein.
• the computer architecture shown in FIGURE 5 includes a central processing unit 502 ("CPU"), a system memory 508, including a random access memory 514 (“RAM”) and a read-only memory (“ROM”) 516, and a system bus 504 that couples the memory to the CPU 502.
• a basic input/output system (“BIOS”) containing the basic routines that help to transfer information between elements within the computer 500, such as during startup, is stored in the ROM 516.
• the computer 500 further includes a mass storage device 510 for storing an operating system 518, application programs, and other program modules, which will be described in greater detail below.
• the mass storage device 510 is connected to the CPU 502 through a mass storage controller (not shown) connected to the bus 504.
• the mass storage device 510 and its associated computer-readable media provide non-volatile storage for the computer 500.
• computer-readable media can be any available computer storage media that can be accessed by the computer 500.
• computer-readable storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data.
• computer- readable storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks ("DVD"), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 500.
• DVD digital versatile disks
• HD-DVD high definition digital versatile disks
• BLU-RAY blue ray
• computer-readable storage media does not encompass transitory signals.
• the computer 500 may operate in a networked environment using logical connections to remote computers through a network such as the network 520.
• the computer 500 may connect to the network 520 through a network interface unit 506 connected to the bus 504. It should be appreciated that the network interface unit 506 may also be utilized to connect to other types of networks and remote computer systems.
• the computer 500 may also include an input/output controller 512 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIGURE 5). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown in FIGURE 5).
• a number of program modules and data files may be stored in the mass storage device 510 and RAM 514 of the computer 500, including an operating system 518 suitable for controlling the operation of a networked desktop, laptop, or server computer.
• the mass storage device 510 and RAM 514 may also store one or more program modules.
• the mass storage device 510 and the RAM 514 may store the presentation client application 114, the presentation state 116, the role 118, and the other program modules and data described above.
• the mass storage device 510 and RAM 514 may also store other program modules and data.
• software applications or modules may, when loaded into the CPU 502 and executed, transform the CPU 502 and the overall computer 500 from a general- purpose computing system into a special-purpose computing system customized to perform the functionality presented herein.
• the CPU 502 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU 502 may operate as one or more finite-state machines, in response to executable instructions contained within the software or modules. These computer-executable instructions may transform the CPU 502 by specifying how the CPU 502 transitions between states, thereby physically transforming the transistors or other discrete hardware elements constituting the CPU 502.
• Encoding the software or modules onto a mass storage device may also transform the physical structure of the mass storage device or associated computer readable storage media.
• the specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer readable storage media, whether the computer readable storage media are characterized as primary or secondary storage, and the like.
• the computer readable storage media is implemented as semiconductor-based memory
• the software or modules may transform the physical state of the semiconductor memory, when the software is encoded therein.
• the software may transform the states of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory.
• the computer readable storage media may be implemented using magnetic or optical technology.
• the software or modules may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Business, Economics & Management (AREA)
• Strategic Management (AREA)
• Human Resources & Organizations (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Entrepreneurship & Innovation (AREA)
• General Engineering & Computer Science (AREA)
• Marketing (AREA)
• Data Mining & Analysis (AREA)
• Economics (AREA)
• Human Computer Interaction (AREA)
• Operations Research (AREA)
• Quality & Reliability (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• Software Systems (AREA)
• User Interface Of Digital Computer (AREA)
• Information Transfer Between Computers (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Priority Applications (12)

Applications Claiming Priority (2)

Publications (2)

Family

ID=45097254

Family Applications (1)

Country Status (16)

Families Citing this family (25)

Family Cites Families (14)

• 2010
  • 2010-06-15 US US12/815,404 patent/US20110307788A1/en not_active Abandoned
• 2011
  • 2011-05-26 AU AU2011265626A patent/AU2011265626B2/en not_active Ceased
  • 2011-05-26 WO PCT/US2011/038106 patent/WO2011159449A2/en not_active Ceased
  • 2011-05-26 RU RU2012154313/08A patent/RU2012154313A/ru unknown
  • 2011-05-26 BR BR112012031871A patent/BR112012031871A2/pt not_active IP Right Cessation
  • 2011-05-26 EP EP11796142.5A patent/EP2583165A4/en not_active Withdrawn
  • 2011-05-26 JP JP2013515359A patent/JP2013535056A/ja active Pending
  • 2011-05-26 CN CN2011800294917A patent/CN102947789A/zh active Pending
  • 2011-05-26 MX MX2012014200A patent/MX2012014200A/es active IP Right Grant
  • 2011-05-26 SG SG2012086211A patent/SG185721A1/en unknown
  • 2011-05-26 KR KR1020127032649A patent/KR20130086149A/ko not_active Withdrawn
  • 2011-05-26 CA CA2799617A patent/CA2799617A1/en not_active Abandoned
• 2012
  • 2012-11-16 ZA ZA2012/08634A patent/ZA201208634B/en unknown
  • 2012-11-18 IL IL223089A patent/IL223089A0/en unknown
  • 2012-12-11 CL CL2012003492A patent/CL2012003492A1/es unknown
• 2013
  • 2013-01-15 CO CO13006357A patent/CO6650365A2/es active IP Right Grant

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events