BACKGROUND

[0001] Large interactive displays are can be utilized to provide enhanced workspaces for one or more users. A large interactive display can include one or more displays or presentation devices such as a monitor or multiple monitors. Devices can also include one or more input mechanisms such as a touch sensor(s), gesture sensor(s), camera(s), infrared camera(s), microphone(s), input device connection(s), etc. Further, information, such as media content can be presented on large interactive displays to users. Due to their size, large interactive displays are well-suited for interacting with multiple users. As such, service providers and manufacturers of such large interactive displays are challenged to provide new and compelling user experiences for use with large interactive displays.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] The following detailed description references the drawings, wherein:

[0003] FIG. 1 is a block diagram of a computing device for providing a user interface on a multi-user large interactive display based on a saved session, according to one example;

[0004] FIGs. 2A and 2B are block diagrams of devices for presenting a multi-user interactive interface based on a stored session, according to various examples;

[0005] FIG. 3 is a flowchart of a method for storing session information associated with a multi-user large interactive display, according to one example;

[0006] FIG. 4 is a flowchart of a method for utilizing session information on a large interactive display, according to one example; [0007] FIG. 5 is a flowchart of a method for providing a multi-user interactive interface based on a saved session, according to one example;

[0008] FIG. 6 is a block diagram of a system of including users utilizing sessions on a large interactive display, according to one example; and

[0009] FIG. 7 is a block diagram of an example user interface utilizing sessions on a multi-user interactive display, according to one example.

DETAILED DESCRIPTION

[0010] Advancements in device technologies are creating new devices, such as large interactive devices, that enable new usage models and user experiences. Traditional usage models and user experiences can be inadequate for utilization of these devices. This brings about opportunities for device manufacturers and service providers to provide new or improved devices and services. Device technologies have advanced in the areas of display size and user interactions. This leads to new usage models where multiple people can interact with a large interactive display at one time.

[0011] Multi-user interactive displays can be utilized to provide information to users as well as to generate information. In certain embodiments, a multi-user, multi- session interface system can be provided to enable social collaboration experiences that involve multiple users. Advances in technology have allowed users to utilize new ways to collaborate and communicate. With the evolution of such technologies, large interactive displays (LIDs) are being utilized by consumers. In certain embodiments, a LID is a display large enough to allow multiple users to interact with it at the same time. Further, in certain embodiments, LIDs have large display surfaces, which can be a single large display, a number of tiled smaller displays, etc. Moreover, LIDs may include various input user interfaces, such as touch enabled input, multi-touch enabled input, gesture-based input, audio/video input, or the like. Further, LIDs can include interactive projection displays (e.g., a display to a projection screen or wall), liquid crystal displays (LCDs), etc. [0012] Multi-user interactive interfaces can be utilized in collaborations between users to generate content (e.g., a digital white board) in settings such as meeting rooms, offices, lobbies, hallways, and homes. As such, multi-user interactive interfaces can be utilized to present content to users, for example, a map or user directory displayed at a building lobby, classroom presentations, attendee information or maps at conferences or meetings, etc.

[0013] However, computing devices have been generally been designed to be used by one user at a time. To provide a compelling user experience for multiple users, various embodiments disclosed herein relate to support for multiple sessions on one or more LIDs at once. In certain embodiments, a session is a semipermanent interactive information exchange between a computer or LID and a user or users. Multiple sessions can be provided to one or more users of a LID. As such, social collaboration experiences can be provided for LIDs. Further, the sessions can be saved and/or restored at another device, such as another LID. Technical challenges exist for creating efficient mechanisms to save and/or restore session information on a LID. Data structures for storing session information and/or session content can be utilized to save and/or restore session information for LIDs. Further, a session organizer can be utilized to store session information and/or session content for users of LIDs. Moreover, multiple sessions as well as multiple session organizers can be utilized to provide a compelling user experience to users of the LIDs.

[0014] Referring now to the drawings, FIG. 1 is a block diagram of a computing device for providing a user interface on a multi-user large interactive display based on a saved session, according to one example. The computing device 100 includes, for example, a processor 110, and a machine-readable storage medium 120 including instructions 122, 124 for providing a user interface including user interface elements based on a saved session. Computing device 100 may be, for example, a notebook computer, a slate computing device, a mobile device, a LID, a multi-user interactive interface, or any other computing device capable of executing the instructions 122,

124. Further, the computing device 100 may be connected to a presentation output (e.g., a display) and/or sensors. As such, the computing device 100 may be a processing component of a system enabling a multi-user interactive interface. In certain examples, computing device 100 may be connected to additional devices, such as sensors, displays, etc. to implement the processes of FIGs. 3 - 5.

[0015] Processor 110 may be, at least one central processing unit (CPU), at least one semiconductor-based microprocessor, at least one graphics processing unit (GPU), other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 120, or combinations thereof. For example, the processor 110 may include multiple cores on a chip, include multiple cores across multiple chips, multiple cores across multiple devices (e.g., if the computing device 100 includes multiple node devices), or combinations thereof. Processor 110 may fetch, decode, and execute instructions 122, 124 to implement use of multiple sessions on LIDs. As an alternative or in addition to retrieving and executing instructions, processor 110 may include at least one integrated circuit (IC), other control logic, other electronic circuits, or combinations thereof that include a number of electronic components for performing the functionality of instructions 122, 124.

[0016] Machine-readable storage medium 120 may be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Thus, machine-readable storage medium may be, for example, Random Access Memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage drive, a Compact Disc Read Only Memory (CD-ROM), and the like. As such, the machine-readable storage medium can be non-transitory. As described in detail below, machine-readable storage medium 120 may be encoded with a series of executable instructions for providing a user interface on a multi-user large interactive display based on a saved session.

[0017] Moreover, the instructions 122, 124, when executed by a processor (e.g., via one processing element or multiple processing elements of the processor) can cause the processor to perform processes, for example, the processes of FIG. 3 - FIG. 5. For example, session manager instructions 122 can be utilized to cause the processor 110 to determine a saved session. The saved session can then be loaded for display on a multi-user large interactive display. Presentation instructions 124 can be utilized to provide a user interface including a user interface element or multiple user interface elements based on the saved session.

[0018] A multi-user interactive interface can be provided to users via a LID. The LID can be provided via an input/output interface component and the computing device 100. When a user interacts with the interface, the processor 110 can determine that a user is present. The user may be identified or anonymous. In certain examples, the user is identified via an authentication process. For example, an identifier associated with the user may be determined based on a username, a username/password combination, a radio-frequency identification (RFID) method, user recognition, etc. Further, in certain examples, a user or set of users can be determined based on a determination that input was received.

[0019] In response to the input, the processor 110 can determine to initiate a session (e.g., a session for the user, a session for an anonymous user, a session for multiple users, etc.). The input can include a specific request to initiate the session or the initiation can occur implicitly based on the received input. The presentation instructions 124 can then be utilized to provide user interface elements. In certain scenarios, a user interface element is a graphical object that can be presented to the user. Examples of graphical user interface elements include structural elements such as windows, menus, icons, controls, widgets, tabs, etc., and interaction elements such as a cursor, a pointer, a selection tool, an adjustment handle, or the like. The session can be provided a portion of the display or presentation. Other sessions can additionally be provided at the same time to the user(s) or to other users.

[0020] The processor 1 10 can provide information via applications. As such, the presentation can be associated with an application. In certain examples, the user may utilize the application to generate content (e.g., an image such as a vector drawing, video, audio, text, etc.). In other examples, the user may utilize an application to link to or view content, services, etc.

[0021] Moreover, a session organizer can be provided for the session. The session organizer can be utilized to manage the session as well as to document or save the session as a saved session. In certain embodiments, a "saved session" is session information that is stored on a non-volatile memory. Session information can include content information from which a user interface element (e.g., an image) can be based. In certain scenarios, content information includes generated information, saved internet information, image information, audio information, video information, saved application content information, combinations thereof, etc. Thus, content information can include media content (e.g., text, documents, images, video, etc.). It can also include information from social networking services such as Twitter® or Facebook®, from search services such as Google®, Bing®, or Twitter® search, and location based services such as Yelp®, Foursquare®, two way communications (e.g., one or more videoconferences between a user and a remote party), Google Maps®, etc. Saved application content information may include content associated with a particular application that when loaded via an instance of the application can be utilized to cause a presentation. Such information can include vector drawing information or vector graphics information. Vector graphics can include, for example, graphical information that can include pieces that can be grouped, augmented, moved, etc. Further, session information can be saved in a data structure (e.g., as saved state information, as a saved image, saved vector graphics information, saved video information, etc.). The data structure may include, for example, an identifier of a processing application (e.g., an application that can load associated content) and content from the session. Further, in certain examples, image information can include one of many different types of image formats, such as Joint Photographic Experts Group (JPEG), bitmap format, etc. Further, various application formats, such as PowerPoint® can be utilized as application information. [0022] In certain scenarios, the saved session can be stored at the computing device 100 or storage associated with the LID. Further, the saved session can be stored in a cloud or transmitted to another device. Storage settings can be set for where to save the session information (e.g., a location on the cloud, a device, a storage location, etc.). A communication network can utilize wired communications, wireless communications, or combinations thereof to connect the computing device 100 to other devices and/or the cloud. Further, the communication network can include multiple sub communication networks such as data networks, wireless networks, telephony networks, etc. Such networks can include, for example, a public data network such as the Internet, local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), cable networks, fiber optic networks, combinations thereof, or the like. In certain examples, wireless networks may include cellular networks, satellite communications, wireless LANs, etc. In one example, the transferring of the saved session information can be implemented by generating a message, such as an electronic mail message. The generated message (e.g., including header information as well as the session information payload) can then be transmitted to the cloud or to another device via the cloud.

[0023] Thus, variations of computing models can be based on cloud computing. For example, the computing device 100 can utilize components that are located on the device itself or components that are located on a remote device in the cloud. For example, the processor 110, session manager instructions 122 and presentation instructions 124 maybe located on a remote device in the cloud, though inputs and outputs are presented through the multi-user large interactive display.

[0024] Further, the computing device 100 can receive the saved session or another saved session (e.g., via a message). The computing device 100 can receive the saved session(s) from the cloud or another device. In certain scenarios, the saved session can be loaded from an internal memory associated with the computing device 100. Thus, the saved session can be determined at the computing device 100. [0025] The saved session can then be loaded for use with a multi-user large interactive display. The loading can occur automatically based on an association (e.g., identification or authentication) of a user with the saved session. Further, the loading can occur based on a received input (e.g., opening of a message, a request to load the session, etc.). Other sessions can also be active on the multi-user large interactive display. When the saved session is loaded, the session manager instructions 122 can cause the processor 110 to determine content to present based on the saved session.

[0026] Then, the presentation instructions 124 can cause the processor 110 to provide a user interface including multiple user interface elements based on the saved session. The user interface elements can include a session organizer as well as windows and other user interface elements associated with information stored in the session. Moreover, the user interface elements can be organized based on information stored in the session (e.g., state information including the location of user interface elements). User interface elements can additionally be organized based, at least in part, on space available on the multi-user LID. As other sessions may be utilized simultaneously, some of the space available on the LID may be appropriated to those sessions. The processor 110 can thus determine a portion of the LID to associate with the session. The saved session information can then be presented in the portion. Further, the processor 110 can scale presented content based, at least in part, on the portion and/or the session.

[0027] FIGs. 2A and 2B are block diagrams of devices for presenting a multi-user interactive interface based on a stored session, according to various examples. Devices 200a, 200b include modules that can be utilized to present a multi-user interactive interface based on a stored session. The respective devices 200a, 200b may be a notebook computer, a slate computing device, a wireless device, a mobile device, a large interactive display, a server, a smart wall, or any other device that may be utilized to provide a multi-user interactive interface associated with a stored session. The device 200a, 200b can include a large interactive display 202. The large interactive display 202 can be connected to other portions of the device 200a, 200b via a communication network (e.g., a cable) or can be part of a single unit with the rest of the device 200a, 200b. A processor, such as a CPU, a GPU, or a microprocessor suitable for retrieval and execution of instructions and/or electronic circuits configured to perform the functionality of any of the modules 210 - 220 described below. In some embodiments, the devices 200a, 200b can include some of the modules (e.g., modules 210 - 212), the modules (e.g., modules 210 - 220) shown in FIG. 2B, and/or additional components.

[0028] As detailed below, devices 200a, 200b may include a series of modules 210 - 220 for utilizing sessions with the large interactive display 202. Each of the modules 210 - 220 may include, for example, hardware devices including electronic circuitry for implementing the functionality described below. In addition or as an alternative, each module may be implemented as a series of instructions encoded on a machine-readable storage medium of respective devices 200a, 200b and executable by a processor. It should be noted that, in some embodiments, some modules 210 - 220 are implemented as hardware devices, while other modules are implemented as executable instructions.

[0029] A presentation module 210 can be utilized to present user interfaces to users. The presentation module 210 can determine presentation information and transmit the presentation information to a presentation device, such as the large interactive display 202. The large interactive display 202 can include a projector, a monitor, an LCD, a television, etc. and can be associated with other devices that can in combination allow for interaction with the device 200a, 200b. In this manner, the presentation module 210 can be utilized to present a multi-user interactive interface to users.

[0030] A session manager module 212 can be utilized to organize and/or determine sessions. The sessions can be presented via the large interactive display 202. Further, the session manager module 212 can keep track of which users, application, services, etc. are associated with each session. Moreover, these sessions can be stored, transmitted, and restored on the device 200a, 200b or on other devices.

[0031] A space manager module 214 can manage space on the large interactive display 202 among various sessions, users, applications, services, etc. Further, the space manager module 214 can dynamically adapt the usage of space depending on the needs of users, sessions, space available, or the like. As such, the space manager module 214 can determine a portion of the large interactive display 202 to provide to users. In certain scenarios, sessions are associated with a user or multiple users.

[0032] A user manager module 216 can be utilized to determine users of the respective device 200a, 200b. For example, a user can be identified by processing information collected by sensors or other input mechanisms. A user profile can be associated with the user and may be customized based on user preferences. Further, an identifier of the user can be stored with the user profile. For example, the identifier can include information that may be utilized to determine the user from sensor information. In certain examples, the identifier can include facial recognition, a mechanism to tag the user (e.g., utilizing a particular color associated with the user), a tracking device, or the like. A user may also be identified by an authenticating device or object such as the user's cell phone or identification badge or finger print.

[0033] A sensor manager module 218 gathers the information from the sensors and provides the information to the user manager module 216, space manager module 214, session manager module 212, or other components of the device 200b. The sensor manager module 218 can utilize a processor 230 to store the information in a memory 232 that can be accessed by other modules of the device 200b. Further, the sensor manager module 218 can utilize input/output interfaces 234 to obtain the sensor information from an input device 240. In certain scenarios, an input device 240 can include a sensor, a camera, a keyboard, a mouse, a remote, a keypad, or the like. Sensors can be used to implement various technologies, such as infrared technology, touch screen technology, etc. In certain examples, camera technology can be utilized to track users and identify users as well as to generate content (e.g., via a video or image capture application).

[0034] The device 200b may include devices utilized for input and output (not shown), such as a touch screen interface, a networking interface (e.g., Ethernet), a wireless networking interface, etc. The presentation module 210 can additionally utilize input/output interfaces 234 to output the presentation to an output device 242, for example, on a display, via a projector, the large interactive display 202, or the like. Such a presentation can be geared towards multiple users (e.g., via a large interactive multi-user display, an interactive wall presentation, interactive whiteboard presentation, etc.).

[0035] An application manager module 220 can manage applications and/or services that can be used through the device 200b. Some applications may be used by different users and may be allocated to a specific portion of the multi-user interactive interface. Other applications may be presented across multiple portions and/or to a public area of the multi-user interactive interface. As such, the application manager module 220 can determine information for the user or multiple users of the device 200b. The information can include electronic mail information, messaging information (e.g., instant messenger messages, text messages, blog updates, social networking messages, social networking updates, etc.), control information, tool panel information (e.g., a color palate, a drawing tool bar, a back button on a browser, etc.), property information (e.g., attributes of content such as a video), calendar information (e.g., meeting information), or the like. Further, the session manager module 212 can be utilized to associate applications, instances of applications, processes associated with applications, or the like with a session or multiple sessions.

[0036] In one embodiment, the presentation module 210 presents a multi-user interactive interface on the large interactive display 202. The presentation can include a user interface or multiple user interfaces to the users. The presentation can additionally be associated with sessions. The session manager module 212 can determine the sessions. Further, the session manager module 212 can determine a public area associated with the large interactive display 202. The public area may be associated with a session open to multiple users.

[0037] One of the sessions can be based on a stored session. The stored session can be a saved session. In certain embodiments, the stored session is restored. As such, the presentation module 210 loads and presents a user interface based on the stored session. The stored session can include state information. The state information can include information about an application or multiple applications. Further, the state information can be utilized to provide a portion of the user interface. As previously noted, the application information can include an identifier of an application as well as content information associated with the application.

[0038] Moreover, in certain embodiments, the session manager module 212 is caused to determine another session of the sessions presented on the large interactive display 202. The presentation module 210 further causes presentation of another user interface associated with the other session. As such, multiple users can utilize the large interactive display 202 simultaneously. Further, the session manager module 212 can cause saving of a state of the other session. In this manner, multiple users can utilize and save sessions on the same large interactive display in parallel.

[0039] Further, use of sessions can be automated based on an association with a particular user. For example, a user of the large interactive display 202 can be determined using input or sensors (e.g., via facial recognition, authentication, RFID, etc.). Moreover, in certain examples, the session manager module 212 can automatically associate the user to a particular session (e.g., a last used session by the user). Then, as the user is determined, the session can be automatically loaded for the user without additional input. [0040] Additionally or alternatively, the session manager module 212 can dynamically change the size and/or scale of a user interface element associated with a session. For example, a flag can be provided in applications associated with the application manager module 220 that when triggered causes the augmentation in the user interface element. This may occur, for example, if a secure user interface element is provided. In certain scenarios, a secure user interface element can include a request for authentication information (e.g., a password) or information that can be flagged as secure.

[0041] In some examples, the session manager module 212 can be utilized to organize and/or manage content associated with applications. A session organizer interface that can organize session information and/or content associated with users can be provided to users, for example, as shown in FIG. 7. Content can be generated and/or utilized by one or more applications. The session organizer interfaces can then dynamically manage content by associating the content with one or more sessions.

[0042] FIG. 3 is a flowchart of a method for storing session information associated with a multi-user large interactive display, according to one example. Although execution of method 300 is described below with reference to computing device 100, other suitable components for execution of method 300 can be utilized (e.g., device 200a, 200b). Thus, the devices 100, 200a, 200b can be considered means for implementing method 300 or other processes disclosed herein. Additionally, the components for executing the method 300 may be spread among multiple devices (e.g., a processing device in communication with input and output devices). In certain scenarios, multiple devices acting in coordination can be considered a single device to perform the method 300. Method 300 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as storage medium 120, and/or in the form of electronic circuitry. [0043] Method 300 may start at 302 and proceed to 304, where computing device 100 may determine active sessions associated with a multi-user large interactive display. The active sessions can include user interface elements presented on the multi-user LID. Further, active sessions can be determined by associating a portion of user interface elements presented on the LID with respective sessions. In certain scenarios, the grouping of a session can be determined based on input. For example, one of the active sessions can be determined by a processor 110 by initiating the session based on the input. For example, the associated user may request a new session or start utilizing a portion of the LID to generate a new session.

[0044] The computing device 100 provides a plurality of user interfaces respectively associated with the active sessions at 306. One of the user interfaces can be associated with the session. The user interface elements of the session can be determined automatically by determining a dynamic portion of the LID to associate with the session when initiated. Then, as a user or users utilize the session, the size of the session can expand and/or shrink. For example, if a user interface element is moved to a portion of the LID that is nearby the allocated portion, but not within the allocated portion, the allocated portion can grow to include the user interface element's new location. Further, a session organizer can be presented to users. As such, the user can add and/or subtract user interface elements from the session. Moreover, the user can be provided an option to hide a user interface element and/or a group of user interface elements.

[0045] At 308, the computing device 100 determines to store session information about the active session. This can occur in response to a request (e.g., by a save request associated with the session organizer). Further, the saving of the session information can occur based on a determination that the session is over. For example, the computing device 100 may utilize sensors to determine that a user associated with the session has left the area associated with the session. As this occurs, the session can be saved and stored for later use. Then, at 310, the method 300 stops. [0046] FIG. 4 is a flowchart of a method for utilizing session information on a large interactive display, according to one example. Although execution of method 400 is described below with reference to computing device 100, other suitable components for execution of method 400 can be utilized (e.g., device 200a, 200b). Additionally, the components for executing the method 400 may be spread among multiple devices (e.g., a processing device in communication with input and output devices). In certain scenarios, multiple devices acting in coordination can be considered a single device to perform the method 400. Method 400 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as storage medium 120, and/or in the form of electronic circuitry.

[0047] Method 400 may start at 402 and proceed to 404, where the computing device 100 may cause presentation of a session manager interface associated with an active session presented on a multi-user LID. As noted above, multiple active sessions can be presented simultaneously. As such, a first active session can be provided as described in method 300. Additionally a second active session can be provided. Further, a first session manager interface can be provided with the first active session and a second session manager interface can be provided (e.g., by causing presentation of user interface elements associated with the second session manager interface) for the second active session. In this manner, multiple users can, in parallel, utilize sessions, including session organizers.

[0048] Then, at 406, the computing device 100 receives input at a first portion of the presentation on the LID. The input can be a use of an application associated with the LID. For example, the application can be utilized to generate content. At 408, the input is associated with the first active session and/or the first session manager interface. Moreover, the computing device 100 may perform 406 and 408 for a second input that is determined to be associated with the second active session and/or the second session manager interface. As previously noted, the input can be associated with a particular session by determining a portion of the LID presentation associated with the input and/or an application associated with the input. For example, the computing device 100 can utilize a touch screen interface to collect the input information. Additionally, other types of input can be utilized. Associations of some input types can be based on a targeted user interface element (e.g., a user interface element that is worked upon via the input). As previously noted in method 300, the session information associated with the sessions can be saved. Further, in certain scenarios, the user input can be utilized to select session content that can be utilized to be included in saved session information as further detailed in FIG. 7.

[0049] In some embodiments, input can be utilized to customize a user interface element. At 410 the computing device 100 customizes interface options associated with the first session, the second session, other sessions, a user of one of the sessions, or a combination thereof. The customization of interface options can include, for example, saving a username or a search term associated with an application. Example applications include a messaging application, a social networking application, a browser application, or the like. As such, when the session is loaded at a later time, and the application is provided, the user can quickly login to the user's account. For example, when a first letter of a username is entered in a username field, a saved username is presented and/or pre-populated. Further, as the customized information is saved with session information, public users and/or users of other portions of the LID can be segregated, allowing for increased privacy.

[0050] At 412, the computing device 100 generates session information. The session information can be generated at the start of a session, updated based on user input, and stored in memory. Further, the session information may be saved in a non-volatile storage. A representation of the session information can additionally be presented to users via the session organizer. For example, an identifier of a corresponding user interface element can be presented via the session organizer. Further, a preview of the session information can be included in the representation of the session organizer. In certain embodiments, the session information is generated and formatted into an electronic message including the session information. For example, an electronic mail message can be generated and the session information or a representation of the session information can be attached.

[0051] In certain scenarios, at 414, the session information can be transmitted to another device. The other device may be a server, a computing device, a laptop, a desktop, a LID, etc. For example, the generated electronic message can be caused to be transmitted to the other device. The electronic message can be routed, for example, via a third device (e.g., an e-mail server) to the other device. When the session information is received at the other device, the session information can be presented. In certain scenarios, the computing device (e.g., a desktop device) can augment the session and store the session. The stored session can then later be restored (e.g., via method 500). Additionally or alternatively, a message can be utilized to store the session information in a cloud or at a server. Then, at 416, the method 400 stops.

[0052] FIG. 5 is a flowchart of a method for providing a multi-user interactive interface based on a saved session, according to one example. Although execution of method 500 is described below with reference to device 200b, other suitable components for execution of method 500 can be utilized (e.g., computing device 100 or device 200a). Additionally, the components for executing the method 500 may be spread among multiple devices (e.g., a processing device in communication with input and output devices). In certain scenarios, multiple devices acting in coordination can be considered a single device to perform the method 500. Method 500 may be implemented in the form of executable instructions stored on a machine- readable storage medium or memory 232, and/or in the form of electronic circuitry.

[0053] Method 500 may start in 502 and proceed to 504, where the session manager module 212 of device 200b may determine a saved session. As previously noted, the saved session can include session information, for example, the session information generated in method 400. Thus, the saved session can be received at the device 200b. The saved session can be saved at the device 200b or another device. In one example, the device 200b or other device can save the saved session to a cloud. Further, the other device can transmit the saved session (e.g., via an electronic mail message) to the device 200b.

[0054] At 506, the processor 230 loads the saved session for use with a large interactive display. The saved session can include content information associated with a previous session that has been saved. The content information can be utilized to provide a user interface including a plurality of user interface elements based on the saved session (508). The content information can further include at least one of generated information, saved internet information, image information, audio information, video information, and saved application content information. The content information can be stored in conjunction with an identifier of an associated application. For example, the session information can be stored in a data structure including an identifier of the application and the content information.

[0055] As noted in methods 300 and 400, the session can be initiated at the device 200b or another device. Further, the session can be associated with a user. As the session is associated with a user, when the user is identified (e.g., via facial recognition, login, RFID, etc.), the user manager module 216 can associate the user to an account or identifier. Then, a saved session (e.g., the saved session) associated with the user or account can be restored. In certain scenarios, the saved session is automatically restored upon determination of the user. Method 500 then stops at 510.

[0056] FIG. 6 is a block diagram of a system of including users utilizing sessions on a large interactive display, according to one example. A large interactive display 600 is provided to users 602a - 602n. When a user 602 interacts with the LID 600, a session can be initiated. Further, a session user interface 604a - 604n can be provided to the user. Multiple sessions can be initiated and provided for users 602. Further, session user interfaces (Uls) 604 can be utilized to determine to save the session. As such, a device associated with the LID 600 can associate portions of the LID 600 (e.g., screen or presentation space) with sessions. In ^' certain scenarios, portions of the LID 600 are considered a part of a public Ul 606. Users 602 can utilize content associated with the public Ul 606. Further, a user 602 can copy or move content from the public Ul 606 into the user's session Ul 604. As previously noted, space allocated to a session Ul 604 can be expanded or contracted dynamically.

[0057] FIG. 7 is a block diagram of an example user interface utilizing sessions oh a multi-user interactive display, according to one example. A multi-user interactive display 700 can be provided via a device. The multi-user interactive display 700 can be, for example, a LID. In this example, two sessions are utilized to present information to users for explanatory purposes. It is contemplated that additional sessions can be utilized on the multi-user interactive display 700.

[0058] A first user can utilize the multi-user interactive display 700 by initiating use of an application. Example applications that may be used on the multi-user interactive display 700 include a white board 702a, 702b, a blog viewing application 704, a widget, a messaging user interface 706, a web browser, a game, a documentation application (e.g., a text viewer or writer, a spreadsheet application, etc.), an information listing application (e.g., a phone directory, a building directory, etc.), a news service, a social networking service, etc. A processing component associated with the multi-user interactive display 700 can be utilized to group user interface elements 702, 704, 706 with portions of the multi-user interactive display 700. As such, sessions can be respectively associated with portions of the display 700.

[0059] The user interface elements and/or applications can include information, such as content information (e.g., drawing 1A 708, news 710, drawing 1 B 712, communication messages 714, etc.). A user or multiple users can utilize these user interface elements. As such, content information, such as drawing 1A 708 can be created, generated, modified, and deleted. Further, information from an application, such as a blog application 704 or multiple blogs can be provided via the display 700. Session information associated with such an application can include information as to the type of information being viewed (e.g., blog posting information, a website link, etc.), a cache of information being presented, settings associated with the application (e.g., window size, scaling parameters, update frequency information, etc.), or the like.

[0060] Further, a session organizer 716, 718 can be provided as an interface to users of the display 700. In this example, a first session is associated with session organizer 716. The session organizer can present information about applications and/or content information associated with the session. For example, a first user interface portion 720 can show an association of the white board 702a with drawing 1A 708, a second user interface portion 722 can show an association a blog application 704 with news 710. Additional session information can be presented on the session organizer 716. For example, an association with an instance of the blog application can be associated with a sports blog. As such, multiple instances or processes associated with applications can be provided to users via during a session. In this example, a third user interface portion 724 can be utilized to represent the blog and/or content. In this case, the application and/or content are not shown on the display as user interface elements 702a or 704. In certain scenarios, an option can be provided to users to view and/or hide parts of the active session. Further, a user interface can be provided for control of the session, for example, to save or load a particular session. The user interface elements, in certain scenarios, can be added to a session by, for example, dragging and dropping a representation of the user interface element to the session organizer.

[0061] A second organizer 718 is associated with a second session. In this session, white board 702b and a messaging user interface 706 are shown on the display 700. These applications can be represented by user interface portions 730 and 732. Further, a user interface portion 734 associated with a blog application and a user interface portion 736 associated with a user interface customization can be provided to the user. As noted previously, these user interface portions 734, 736 can represent applications and/or processes associated with presented user interfaces or other session information.

[0062] User interface portion 736 can be associated with customizations to the second session. As such, a user utilizing the second session can be provided these customizations while another user of the first session does not have these customizations. For example, the user can create a customized response for a gesture. Sensors can detect the gesture and the gesture can be a shortcut to do perform a particular action. In some examples, other customizations can be provided, such as a customization based on a voice command, a customization based on a drawing, etc. Other customizations can be included, such as saving keywords, search terms, or usernames that are used in a session or by a user.

[0063] With the above approaches, a multi-session user interface system can be provided via interactive displays. As such, multiple users can collaborate on one session or multiple sessions of the display. Further, with session customizations, different users can have unique user experiences in parallel while utilizing the same device. Further, as the sessions can be saved, restored, and/or transmitted, collaborative experiences can be shared quickly and made readily available via other user interfaces (e.g., a personal device).