Patent Description:
In person presentations are typically displayed on a single screen using a projector so that attendees may see the presentation. Such presentations use specialized equipment which can be expensive and is often not available. Some software programs allow screens to be shared with meeting attendees. However, it may be cumbersome for attendees to login to the software programs to view the presentation. Furthermore, it may be difficult for the presenter to gauge the interest of attendees, particularly when attendees are viewing remotely over a screen-sharing program. <CIT> describes methods and devices for facilitating presentation feedback during a local presentation. <CIT> describes sensing and analyzing reaction information of participants to an interaction. <CIT> describes techniques and apparatuses for determining an audience's state or interest.

Aspects of the invention are in accordance with the appended claimsA method may comprise transmitting, by a presenting device, presentation content to an attendee device, wherein the presenting device and the attendee device are in electronic communication; receiving, by the presenting device, sensor data from the attendee device, wherein the sensor data is captured by the attendee device in response to the presentation content being displayed on the attendee device; and displaying, by the presenting device, the sensor data on the presenting device, wherein the sensor data is displayed with the presentation content on the presenting device.

In various embodiments, the method may comprise analyzing, by the presenting device, the sensor data; generating, by the presenting device, analyzed data based on the sensor data, wherein the analyzed data is generated using sensor data processing software; and displaying, by the presenting device, the analyzed data on the presenting device, wherein the sensor data is displayed with the presentation content. The sensor data processing software may comprise at least one of a facial recognition software, a voice analysis software, or a thermal analysis software. The method may comprise displaying, by the presenting device, the analyzed data overlaid on the presentation content. The sensor data may comprise the sensor locations where an attendee is looking on the attendee device. The method may comprise generating, by the presenting device, a heatmap based on the locations; and displaying, by the presenting device, the heatmap overlaid on the presentation content. The method may comprise displaying, by the presenting device, a number of attendees currently viewing the presentation content based on the locations. The method may comprise determining, by the presenting device and based on the sensor data, a change in the number of attendees viewing the presentation content. The presentation content may be simultaneously displayed on the attendee device and the presenting device.

In various embodiments, a computer-based system may comprise a processor, and a tangible, non-transitory memory configured to communicate with the processor, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising: transmitting, by the processor, presentation content to an attendee device, wherein the computer-based system and the attendee device are in electronic communication via a network; receiving, by the processor, sensor data from the attendee device, wherein the sensor data is captured by the attendee device in response to the presentation content being displayed on the attendee device; and displaying, by the processor, the sensor data, wherein the sensor data is displayed with the presentation content.

In various embodiments, the operation of transmitting the presentation content may comprise streaming the presentation content to the attendee device via a system for peer to peer communications such as described in <CIT> entitled Systems and Methods for Peer to Peer Communication which is herein incorporated by reference in its entirety. In various other embodiment, other networks may be used. The network may be provided by a travel wireless router. The network may comprise the internet or a local area network (LAN). The sensor data may be captured by at least one of a camera, a microphone, or a thermal imaging sensor. The computer-based system may also comprise a local storage in electronic communication with the processor, wherein the local storage is configured to store the presentation content. The computer-based system may also comprise a portable storage device in electronic communication with the processor, wherein the portable storage device is configured to store the presentation content. The portable storage device may be configured to communicate wirelessly via the network to the attendee device and the computer-based system.

In various embodiments, a method may comprise discovering, by a computer-based system, an attendee device in electronic communication with a network, wherein the network is a local area network (LAN); transmitting, by the computer-based system, an invitation to the attendee device to view presentation content; transmitting, by the computer-based system, the presentation content to the attendee device in response to the attendee device accepting the invitation, wherein the presentation content comprises a presentation and an engagement feedback tool; and displaying, by the computer-based system, the presentation content, wherein in response to the presentation content being displayed, the presentation content is displayed on the attendee device.

In various embodiments, the invitation may comprise an authentication control. The engagement feedback tool may comprise at least one of a live poll, a question and answer feature, a chat feature, a contact information exchange feature, a screen sharing feature, or a hand raising functionality.

A more complete understanding may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures.

The detailed description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show various embodiments by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the scope of the disclosure. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.

The present disclosure relates to systems, methods, and computer program products. In the detailed description herein, references to "various embodiments," "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Systems and methods are disclosed herein for providing real-time feedback during a presentation. A presenting device may share content with one or more attendee devices. The attendee devices may comprise sensors which collect data from the attendees, such as where the eyes of the attendees are looking. The sensor data may by analyzed, and the presenting device may display the analyzed data to the presenter.

The systems and methods disclosed herein may enable communication between devices without connection to the Internet or other networks using a standardized communication system ("SCS"). An SCS may be operable on the computing devices of the present disclosure. The SCS may comprise any combination of hardware and/or software. The SCS may utilize existing physical components of the device, such as <NUM> or <NUM>(<NUM>) wireless chips and Bluetooth® systems in order to communicate with other devices. The SCS may be suitable for any communication protocol, such as IP, TCP/UDP, Bluetooth®, raw Manchester encoding, and any other form of wireless communication.

Referring to <FIG>, a system <NUM> for transmitting content is illustrated according to various embodiments. A first device <NUM> comprising an SCS <NUM> and a second device <NUM> comprising an SCS <NUM> are illustrated according to various embodiments. In various embodiments, SCS <NUM> and SCS <NUM> may be aftermarket software programs installed on first device <NUM> and second device <NUM>. For example, a user may download an SCS app onto a smartphone or other device. However, in various embodiments, SCS <NUM> and SCS <NUM> may be embedded into a chip, such as an <NUM> wireless chip, in first device <NUM> and/or second device <NUM>.

In various embodiments, the SCS may implement a standardized communication protocol ("SCP") on a device. The SCP may attach an SCP header <NUM> to a packet in order to identify a datagram <NUM> as an SCP datagram. First device <NUM> may communicate with second device <NUM> via SCP. The SCS may recognize the SCP header and may follow the SCP. The SCP may define the ability for devices to discover one another, to request the transfer of raw data, to transmit confirmations on receipt of data, and to perform any other steps involved with transmitting data.

In various embodiments, the SCS may be implemented at the network layer in the Open Systems Interconnection ("OSI") model (or the Internet layer in the TCP/IP model). Regardless of the protocol being used at the transport layer (e.g. TCP, UDP, SCTP, DCCP), the SCP header may allow devices comprising an SCS to communicate via SCP.

In various embodiments, at least one of first device <NUM> and second device <NUM> may comprise a smartphone. However, in various embodiments, first device <NUM> and second device <NUM> may comprise any type of device capable of transmitting and/or receiving data.

Referring to <FIG>, a process <NUM> for transmitting data between devices is illustrated according to various embodiments. In various embodiments, a first user may wish to transmit data from first device <NUM> to second device <NUM>. The data may comprise any type of data, such as a text message, image, video, text document, or any other type of file.

First device <NUM> may discover available devices (step <NUM>). First device <NUM> may attempt to discover other devices by a variety of methods. In various embodiments, first device <NUM> may discover other devices via a camera or other optical device. In various embodiments, second device <NUM> may display a symbol, such as a QR-code, a barcode, or text. The symbol may comprise identifying characteristics about second device <NUM>. For example, in various embodiments the identifying characteristics may comprise at least one of a device name, an IP address of the device, an owner name, an endpoint of the device, and the available transport layers on the device. First device <NUM> may scan the symbol using a camera. First device <NUM> may obtain the identifying characteristics from the symbol and use the identifying characteristics in order to transmit data to second device <NUM>.

In various embodiments, the SCS on first device <NUM> may search for other devices using a wireless chip in first device <NUM>. Devices comprising an SCS may transmit a broadcast message. The broadcast message may comprise the identifying characteristics of the device. In various embodiments, first device <NUM> may be within transmission range of second device <NUM>. The transmission range may depend on the specific type of wireless chips in first device <NUM> and second device <NUM>. However, in various embodiments, the transmission range may be up to about <NUM> feet - <NUM> feet. The SCS may open a socket on first device <NUM> to listen for broadcast messages. The broadcast message may be sent by a variety of hardware. For example, the broadcast message may be transmitted via an <NUM> wireless chip, Bluetooth® chip, or NFC.

In various embodiments, first device <NUM> and second device <NUM> may not be within transmission range of each other. However, an intermediary device, such as a smartphone equipped with hotspot technology, may be within transmission range of first device <NUM>. First device <NUM> may search for available devices by transmitting a message to intermediary device, instructing intermediary device to look for available devices. Intermediary device may receive a broadcast message from second device <NUM>, and intermediary device may transmit the broadcast message to first device <NUM>. Thus, first device <NUM> may discover second device <NUM> without connecting to the internet or a cellular network even though first device <NUM> may not be within transmission range of second device <NUM>. In various embodiments, any number of intermediary devices may be daisy-chained, such that first device <NUM> may discover second device <NUM> from miles apart by transmitting data via a series of intermediary devices.

First device <NUM> may display a list of all discovered devices to the user. The user may select second device <NUM> in order to transmit data to second device <NUM>. The user may select a file or message to be transmitted to second device <NUM>.

The SCS <NUM> on first device <NUM> may determine the transmission hardware to utilize for the transmission (step <NUM>). In various embodiments, first device <NUM> and second device <NUM> may each have only one type of transmission hardware, such as an <NUM> wireless chip, and the SCS <NUM> may thus select the <NUM> wireless chip to transmit the data. However, in various embodiments, multiple transmission paths may be available between first device <NUM> and second device <NUM>. For example, first device <NUM> and second device <NUM> may each comprise an <NUM> wireless chip and a Bluetooth® chip. In various embodiments, the SCS <NUM> may determine the fastest transmission path, and may select the fastest transmission path to transmit the data. In various embodiments, the transmission path may be selected by default settings. For example, SCS <NUM> may always select an <NUM> wireless path for transmission when available, and if the <NUM> wireless path is not available, SCS <NUM> may select a Bluetooth® path. However, in various embodiments, the SCS <NUM> on first device <NUM> may transmit a speed test message to second device <NUM> via each available transmission path, and the SCS <NUM> may select the fastest transmission path based on the speed test results.

In various embodiments, the SCS <NUM> may instruct first device <NUM> to send the data to second device <NUM> via multiple transmission paths. A message may be divided into multiple packets. SCS <NUM> may analyze the available transmissions paths and send the message over multiple transmission paths in order to expedite transmission of the entire message. For example, SCS <NUM> may determine that the fastest method of transmitting the message may be to transmit <NUM>% of the packets via an <NUM> wireless path, and <NUM>% of the packets over a Bluetooth® path. SCS <NUM> may attach an SCP header to each packet being transmitted to second device <NUM>, whether via <NUM> wireless or Bluetooth®. Thus, SCS <NUM> on second device <NUM> may recognize the packets as being received by SCP, and SCS <NUM> may reassemble the packets in order to recreate the entire message. In various embodiments, SCS <NUM> may analyze all transmission paths available, including but not limited to multiple <NUM> wireless chips, Bluetooth® chips, NFC, PDQ, or any other transmission paths in order to select the fastest transmission method. The SCS on first device <NUM> may initiate a file send protocol and transmit the data to second device <NUM> (step <NUM>).

In various embodiments, first device <NUM> and second device <NUM> may be connected to the same local network. First device <NUM> may transmit a link, such as a QR-code, over a cellular network or the local network to second device <NUM>. In various embodiments, the link may comprise 10kb or less of data. Second device <NUM> may use the link to request or accept a file transfer. First device <NUM> may transmit a file over the local network. In various embodiments, the file may be transferred using TCP/IP directly over the local network.

In various embodiments, second device <NUM> may have access to an internet connection. First device <NUM> may transmit a link over a cellular transmission path to second device <NUM>, and second device <NUM> may use the link to download a file stored on the cloud and/or on a server over the internet. In various embodiments, second device <NUM> may download the file using TCP/IP.

In various embodiments, first device <NUM> may sync its contents with a cloud database. In various embodiments, first device <NUM> may comprise an SCS folder, and only files stored in the SCS folder may be synced with the database. First device <NUM> may transmit a link over a cellular transmission path to second device <NUM> identifying a file stored on the database. In various embodiments, second device <NUM> may not have access to an <NUM> wireless network at the time second device <NUM> receives the link. Second device <NUM> may use the link to access the file whenever second device <NUM> gains access to an <NUM> wireless network in order to prevent cellular data charges. In various embodiments, second device <NUM> may use the link to access the file over the cellular network. In various embodiments, second device <NUM> may stream all or part of the file over either the cellular network or an <NUM> wireless network.

In various embodiments, first device <NUM> may share an online folder with second device <NUM>. First device <NUM> may indicate that second device <NUM> may have access to an online folder. First device <NUM> may sync with the online folder to upload files stored on first device <NUM> to the online folder. Second device <NUM> may sync with the online folder to download files stored in the online folder to second device <NUM>.

Referring to <FIG>, a portable storage device ("PSD") <NUM> is illustrated according to various embodiments. The PSD <NUM> may be a wearable device, such as a wrist band or bracelet. However, PSDs may be any type of portable device which is capable of storing information. For example, a PSD may comprise a watch, necklace, phone case, smartphone, implanted chips, clothing item, wallet, etc..

The PSD <NUM> may comprise a storage module <NUM>, a communication module <NUM>, a processor <NUM>, and a battery <NUM>. The storage module <NUM> may comprise a memory card. For example, the storage module <NUM> may comprise an SD card, an xD card, a CompactFlash card, or any other suitable memory card. The storage module <NUM> may comprise an internal memory, such as iSSD, SSD, iNAND, or flash SD. The communication module <NUM> may comprise one or more components capable of wireless communication. For example, the communication module may comprise an <NUM> or <NUM>(<NUM>) wireless chip, a Bluetooth® chip, an NFC chip, etc. The processor <NUM> may comprise any combination of hardware and/or software capable of providing instructions to the storage module <NUM> and the communication module <NUM>. In various embodiments, the storage module <NUM>, the communication module <NUM>, and the processor <NUM> may be embedded within the PSD <NUM>, such that the PSD <NUM> does not have any visible electronic components. In various embodiments, the PSD <NUM> may comprise a waterproof coating, such as rubber or silicone.

The PSD <NUM> may comprise a standard communication system ("SCS") as previously described herein. The SCS may be any combination of hardware and/or software which is capable of communicating via a standard communication protocol ("SCP") as previously described herein. In various embodiments, the SCS may be implemented on at least one of the storage module <NUM>, the communication module <NUM>, or the processor <NUM>.

The PSD <NUM> may wirelessly receive and transmit files and communications from other devices, such as smartphones, televisions, game consoles, tablets, personal computers, printers, etc. Due to the SCS, the PSD <NUM> may not be limited to communicating with any particular brand or manufacturer of device. In contrast, the PSD <NUM> may communicate across platforms, such as with Apple® devices, Android® devices, Windows® devices, UNIX® devices, or any other suitable devices.

In various embodiments, the PSD <NUM> may allow a user to access their files wherever the user goes. For example, a user may have a document stored on a laptop computer. The user may transmit the document from the laptop computer to the PSD <NUM> using the SCS. The PSD <NUM> may store the document in the storage module <NUM>. The user may then transmit the document from the PSD <NUM> to another device, such as a smartphone, using the SCS.

In various embodiments, the PSD <NUM> may communicate directly with other devices without using a network. Thus, information may be transmitted securely between the PSD <NUM> and other devices. However, in various embodiments, the PSD <NUM> may communicate over a network using a wireless chip in the communication module <NUM>. The communication module <NUM> may comprise two wireless chips, allowing the PSD <NUM> to simultaneously communicate over a network on a first wireless chip and directly to another device on a second wireless chip.

In various embodiments, the PSD <NUM> may allow data to be transferred from a device to the PSD <NUM> without storing the data on the device. For example, a smartphone may capture a picture and transmit the picture directly to the PSD <NUM> using the smartphone's RAM without storing the picture on the hard drive of the smartphone. Thus, the smartphone may be lost, stolen, sold, or donated without risk of a third-party obtaining the picture, or other data which is stored on the PSD <NUM> and not the smartphone. Similarly, a user may initiate an SCS on a device, such as a laptop, and open a file stored on the PSD <NUM> using the device. The user may edit the file on the device and save the edited file directly on the PSD <NUM> without saving the edited file on the device.

A user may use the PSD <NUM> to store all of the user's files. Regardless of what device a user is using to access the files on the PSD <NUM>, the user may create, edit, and delete files directly on the PSD <NUM> using another device, such as a personal computer.

In various embodiments, the PSD <NUM> may emulate a network drive. Thus, the PSD <NUM> may be able to communicate with devices which are not capable of downloading or installing custom software. For example, the PSD <NUM> may emulate a DLNA media service, or a Windows® network. The PSD <NUM> may require a password to be entered on the device, and the device may then access files stored on the PSD <NUM>.

Referring to <FIG>, a portable storage device <NUM> for use with modular components is shown, in accordance with various embodiments. Portable storage device <NUM> may include features and functionality described herein. Portable storage device <NUM> may have a housing <NUM>. Housing <NUM> may be made from materials including metals, plastics, and/or rubbers. For example, housing <NUM> may be made from stamped and fused sheets of aluminum, molded plastic, or other suitable materials. Housing <NUM> may also be made from thermally conductive materials to enhance heat dissipation.

In various embodiments, electronic interface panel <NUM> may further comprise a data port <NUM> exposed from housing <NUM>. Data port <NUM> may be configured to transmit power and/or signals over electronic connections in a predetermined format. For example, data port <NUM> may use a protocol such as USB, firewire, lightning cable, SATA, PCIe, or other suitable cable interface for data and/or power transfer. Data port <NUM> may also use a proprietary pin configuration and slot geometry.

Referring to <FIG>, a case <NUM> for a mobile computing device is shown as a portable storage assembly <NUM>, in accordance with various embodiments. Case <NUM> may fit on a portable computing device such as, for example, a tablet, smartphone, smart watch, laptop, or other suitable computing device. Case <NUM> may have an interior contour matching that of a computing device to retain the computing device. Case <NUM> may define cavity <NUM> with a shape suitable to receive and retain with portable storage device <NUM>. In that regard, portable storage device <NUM> may be removably coupled to case <NUM>, and cavity <NUM> may have a geometry mirroring <NUM> sides of the portable storage device with an opening shaped like a surface of the portable storage device. The cavity may thus be defined by five orthogonal surfaces. The portable storage device may lie with a surface flush with the interior of case <NUM>.

In various embodiments, case <NUM> may include interface <NUM> suitable for communication with data port <NUM> or conductive pads <NUM> (of <FIG>). Interface <NUM> may by electronically coupled to a data plug <NUM> by an electrical conduit <NUM> such as a wire. Data plug <NUM> may interface with a corresponding data port on a computing device retained within case <NUM>. Data plug <NUM> may thus plug into the bottom port on a smartphone to electrically couple case <NUM> to the smartphone, for example. Case <NUM> may further include a protrusion <NUM> configured to house the PCBs and power supplies described herein as well as the cavity <NUM>.

In various embodiments, case <NUM> may enable physical electronic communication between portable storage device <NUM>, a power supply (e.g., power supply <NUM> as shown in <FIG>), a PCB, or other electronic devices retained within case <NUM>. Case <NUM> may further enable electronic communication of power and/or data to and/or from the mobile device retained within case <NUM>. Portable storage device <NUM> may also be in wireless communication with the mobile device retained within case <NUM> as described herein.

Referring to <FIG>, a modular portable storage system <NUM> is shown, in accordance with various embodiments. Modular portable storage system <NUM> may include case <NUM>, portable storage device <NUM>, power supply <NUM>, and/or external housing <NUM>. In various embodiments, the portable storage device <NUM> may be inserted within the external housing <NUM>. The power supply <NUM> may also be inserted within external housing <NUM> to power the portable storage device <NUM>. The various components described herein may be removable and interchangeably coupled to one another electronically and mechanically. In that regard, portable storage device <NUM> may be utilized in various configurations to augment functionality of computing devices in communication with portable storage device <NUM>. For further description of portable storage devices and their communication abilities, see <CIT> titled "PORTABLE STORAGE DEVICE WITH MODULAR POWER AND HOUSING SYSTEM," and filed on July <NUM>, <NUM>, <CIT> titled "SYSTEMS AND METHODS FOR PEER TO PEER COMMUNICATION" and filed on January <NUM>, <NUM>, and <CIT> titled "SYSTEMS AND METHODS FOR PORTABLE STORAGE DEVICES," and filed on June <NUM>, <NUM> the contents of all of which are incorporated by reference herein in their entirety.

Referring to FIG. 7A, and in accordance with various embodiments, a system <NUM> for presenting content is disclosed. System <NUM> may be configured to connect presenters and attendees to enable the presenter to present content to the various attendees. System <NUM> may also enable the attendees to interact with the presenter through various engagement feedback tool including, for example, live polls, direct questions, discrete question and answers, downloading the presented content, screensharing, exchange of contact information, and/or the like.

In various embodiments, system <NUM> may allow the presenter and/or the attendees to use any suitable computing device (having any suitable operating system) to present and view the presented content, including, for example, a smartphone, laptop, desktop computer, internet of things (IoT) device, and/or any other suitable computing device having network communication capabilities. The presented content may be transmitted to the attendees without requiring the use of additional software, mobile application, or the like. System <NUM> may allow the presenter to connect with the attendees over any suitable network that the devices are connected to (e.g., the internet, a local area network (LAN), a wide area network (WAN), a portable travel network router, etc.). In that regard, system <NUM> may be configured to allow the presenter to present content to any desired number of attendees, dependent on the strength and capabilities of the network, and without requiring the use of the internet. In various embodiments, system <NUM> may also enable the presenter to receive feedback from one or more attendees, either through active feedback or passive feedback, as discussed further herein.

System <NUM> may comprise a presenting device <NUM> and one or more attendee devices <NUM>. Presenting device <NUM> and attendee devices <NUM> may be in electronic communication via a system as described in <CIT> or other networks such as a network <NUM>. Network <NUM> may comprise any suitable network discussed herein, including, for example, the internet, a local area network (LAN), a wide area network (WAN), or the like.

In various embodiments, a user (e.g., a presenter) may interface with presenting device <NUM> to present content to one or more attendee devices <NUM>. Presenting device <NUM> may include any device which communicates, in any manner discussed herein, with attendee devices <NUM>, via network <NUM> or any other network or protocol discussed herein. For example, presenting device <NUM> may comprise a computing device such as a server, laptop, notebook, hand held computer, cellular phone, smart phone (e.g., IPHONE®, BLACKBERRY®, ANDROID®, etc.), tablet, wearable (e.g., smart watches, smart glasses, smart rings, etc.), internet of things (IoT) device, or any other similar device. Presenting device <NUM> may comprise software configured to aid presenting device <NUM> in interacting with system <NUM>, such as, for example, an internet browser (e.g., MICROSOFT INTERNET EXPLORER®, GOOGLE CHROME®, etc.), mobile application, or the like. Practitioners will appreciate that presenting device <NUM> may or may not be in direct electronic communication with network <NUM>. For example, presenting device <NUM> may access the network <NUM> through another server or network, which may have a direct or indirect connection to an internet server. Practitioners will further recognize that presenting device <NUM> may present interfaces associated with a software application or module that are provided to presenting device <NUM> via application graphical user interfaces (GUIs) or other interfaces and are not necessarily associated with or dependent upon internet browsers or internet specific protocols.

For example, and in accordance with various embodiments, presenting device <NUM> may display or be in communication with a presentation user interface (UI) <NUM>. Presentation UI <NUM> may be configured to enable the user to view, select, transfer, and/or otherwise interact with the presented content. In various embodiments, presentation UI <NUM> may comprise a split-screen, or multi-screen, experience to enable the user to view the presented content, presentation notes, questions, attendee feedback, or the like at the same time. For example, presentation UI <NUM> may allow the user to toggle between different screens or select one or more screens to display content at a single time.

In various embodiments, the content may be a file, or a plurality of files, stored locally on presenting device <NUM>. In various embodiments, and with reference to <FIG> the content may be stored on a separate storage device, such as portable storage device <NUM> (e.g., as described in <FIG>), which may be separate from, electronically connected, or physically connected to presenting device <NUM>. In various embodiments, portable storage device <NUM> may be configured to directly transmit the content to one or more attendee devices <NUM>. In that respect, portable storage device <NUM> may be in electronic communication with network <NUM>. In various embodiments, the content may be located on a remote server or cloud computing system, and presenting device <NUM> may access the content using a URL, file system, or other method. The content may be stored in temporary memory on the presenting device <NUM> or portable storage device <NUM>. For further information on streaming content between devices, see <CIT>, the contents of which are incorporated by reference herein in their entirety. In yet other embodiments, devices such as disclosed in <CIT> entitled Systems and Methods for Portable Storage Devices, the contents of which are herein incorporated by reference in their entirety may be used in accordance with various embodiments of the present invention.

With reference again to FIG. 7A, and in accordance with various embodiments, one or more second users (e.g., attendees) may interface with attendee device <NUM> to view content presented by presenting device <NUM>. Attendee device <NUM> may include any device which communicates, in any manner discussed herein, with presenting device <NUM>, via network <NUM> or any other network or protocol discussed herein. For example, attendee device <NUM> may comprise a computing device such as a server, laptop, notebook, hand held computer, cellular phone, smart phone (e.g., IPHONE®, BLACKBERRY®, ANDROID®, etc.), tablet, wearable (e.g., smart watches, smart glasses, smart rings, etc.), internet of things (IoT) device, or any other similar device. Attendee device <NUM> may comprise software configured to aid attendee device <NUM> in interacting with system <NUM>, such as, for example, an internet browser (e.g., MICROSOFT INTERNET EXPLORER®, GOOGLE CHROME®, etc.), mobile application, or the like. Practitioners will appreciate that attendee device <NUM> may or may not be in direct electronic communication with network <NUM>. For example, attendee device <NUM> may access the network <NUM> through another server or network, which may have a direct or indirect connection to an internet server. Practitioners will further recognize that attendee device <NUM> may present interfaces associated with a software application or module that are provided to attendee device <NUM> via application graphical user interfaces (GUIs) or other interfaces and are not necessarily associated with or dependent upon internet browsers or internet specific protocols.

For example, and in accordance with various embodiments, attendee device <NUM> may display or be in communication with a presentation user interface (UI) <NUM>. Presentation UI <NUM> may be configured to enable the second user to view and otherwise interact with the presented content. In various embodiments, presentation UI <NUM> may comprise a split-screen, or multi-screen, experience to enable the second user to view the presented content and provide active feedback (e.g., via a poll, question or chat interface, etc.), or the like at the same time. For example, presentation UI <NUM> may allow the second user to toggle between different screens or select one or more screens to display content at a single time.

Presenting device <NUM> may transmit an invitation to attendee devices <NUM> to view the content. One or more of the attendee devices <NUM> may be located in close proximity to presenting device <NUM>, such as in the same room. However, one or more of attendee devices <NUM> may be located remotely, such as in a different room, building, city, state, or country. In various embodiments, the invitation may comprise a link, a URL, or the like, and the invitation may be transmitted via email, SMS, push notification, verbally transmitted, etc. In various embodiments, and with reference again to <FIG>, portable storage device <NUM> and/or presenting device <NUM> may discover one or more attendee devices <NUM>, and the user may select the attendee devices <NUM> from a list provided by portable storage device <NUM> and/or presenting device <NUM>. The attendees may accept the invitation in order to view the content. In various embodiments, the invitation may comprise (and be protected by) an authentication control, such as, for example, a user name and password, a unique passphrase, and/or the like.

Presenting device <NUM>, attendee devices <NUM>, and/or portable storage device <NUM> may communicate using any equipment and protocols known in the art. For example, the various components may communicate over the internet, using wireless chips, via cellular towers, via satellite communications, etc..

Presenting device <NUM> may transmit the content to attendee devices <NUM>. In various embodiments, the content may be transmitted directly, via network <NUM>, via portable storage device <NUM>, and/or through any other suitable transmission method. The content may be streamed to attendee devices <NUM>. For example, the content may comprise a MICROSOFT POWERPOINT®, APPLE KEYNOTE®, or PREZI® presentation, and as the user changes slides on presenting device <NUM> (e.g., via presentation UI <NUM>), attendee devices <NUM> (e.g., via presentation UI <NUM>) may show the slides as they change. The content may comprise any suitable or desired static or dynamic content.

In various embodiments, attendee devices <NUM> may comprise one or more sensors <NUM>. For example, sensors <NUM> may comprise one or more cameras, microphones, thermal imaging sensors, accelerometers, compasses, etc. The sensors <NUM> may be configured to detect actions of the attendees, capture feedback from the attendees, and/or the like. In various embodiments, the sensors <NUM> may comprise a camera which captures still images or video of attendees. The sensors <NUM> may comprise a microphone which detects audio, such as words, tones, or sounds. The sensors <NUM> may comprise a thermal imaging (e.g., infrared) sensor which detects the number and/or locations of persons in view of the sensor.

In various embodiments, one or more of presenting device <NUM>, attendee devices <NUM>, or portable storage device <NUM> may comprise sensor data processing software. The sensor data processing software may be configured to analyze the data captured by the sensors <NUM> and present the data to the presenter. The analyzed data may be presented to the presenter using any suitable technique. For example, the analyzed data may be presented to the presenter in real time via presentation UI <NUM>. The analyzed data may also be presented in a generated report and transmitted via email, SMS, or the like.

In various embodiments, the sensor data processing software may comprise facial recognition software. The facial recognition software may be configured to detect where the attendee's eyes are looking, or the number or location of persons or faces in view of the sensor <NUM> (e.g., a camera). The facial recognition software may detect particular locations on attendee devices <NUM> where the attendees are looking, which may indicate which portion of the content the attendees are currently viewing (or not viewing). For example, a presenter may be talking about a first bullet point on a slide for several minutes, but the facial recognition software may detect that <NUM>% of attendees were viewing a subsequent bullet point, indicating that the attendees were moving faster through the content than the presenter. Additionally, the facial recognition software may determine what portion of the attendees are looking at the attendee devices <NUM> versus a different location entirely (e.g., five attendees were present and one was looking at attendee device <NUM>).

In various embodiments, the sensor data processing software may comprise voice analysis software. The voice analysis software may be configured to analyze the words, tones, or sounds captured by the sensors <NUM> (e.g., a microphone). For example, the voice analysis software may detect words typically associated with a positive attendee response, such as "interesting," "great," "ground-breaking," or the like. The voice analysis software may detect words typically associated with a negative attendee response, such as "boring," "outdated," "whatever," and/or the like. Additionally, the voice analysis software may detect the tone of attendee voices to determine the general mood or interest level of attendees. The voice analysis software may also detect noises such as coughs or snoring, which may indicate a negative attendee response to the content, or other noises which indicate a positive attendee response. In various embodiments, the voice analysis software may calculate an interest score, such as from <NUM>-<NUM>, with a score of <NUM> indicating that all attendees are engaged in the content, and a score of <NUM> indicating that the attendees are ignoring or reacting negatively to the content.

In various embodiments, the voice analysis software may implement various artificial intelligence, machine learning, and/or statistical analysis techniques to aid in calculating the interest score. Artificial intelligence may refer generally to the study of agents (e.g., machines, computer-based systems, etc.) that perceive the world around them, form plans, and make decisions to achieve their goals. Foundations of AI include mathematics, logic, philosophy, probability, linguistics, neuroscience, and decision theory. Many fields fall under the umbrella of AI, such as computer vision, robotics, machine learning, and natural language processing. For example, and in accordance with various embodiments, the voice analysis software may implement machine learning algorithms and models to aid in calculating the interest score. The voice analysis software may implement any suitable machine learning model or algorithm, statistical data model, or the like, and may be supervised or unsupervised. For example, exemplary unsupervised models may include clustering and dimensionality reduction, LDA topic modeling, and/or any other unsupervised machine learning model. For example, exemplary supervised models may include classification models, regression models, sentiment analysis techniques, and/or any other supervised machine learning model. In various embodiments, machine learning networks and/or subject matter experts may initially supervise the model. In various embodiments, the machine learning model may comprise random forest models, gradient boosting models, or any other suitable or desired model. In various embodiments, machine learning service <NUM> may also implement reinforcement learning techniques to enhance the machine learning algorithm and/or statistical data models.

In various embodiments, the sensor data processing software may comprise thermal analysis software. The thermal analysis software may be configured to analyze the sensor data to provide feedback to the presenting device <NUM>. For example, the thermal analysis software may detect the number of attendees or individuals in a room, as well as an increase or decrease in the number of individuals in the room. The thermal analysis software may determine the distance, and change in distance, between attendees, which may indicate that attendees are coming together or drifting apart. Additionally, the thermal analysis software may detect attendee interest in the presentation, such as by detecting an increase (or decrease) in surface body temperature in attendees, which may indicate an increased (or decreased) heart rate and increased (or decreased) interest in the presented content.

In response to the sensor data processing software generating the feedback, the sensor data processing software may transmit or display the feedback on the presenting device <NUM>. The feedback may be transmitted or displayed in real time, or near real time. In various embodiments, the feedback may be transmitted or displayed as textual feedback, such as the number of attendees viewing the content. In various embodiments, the feedback may be transmitted or displayed graphically, such as in a heatmap showing where on the screen attendees are looking. In various embodiments, the feedback may also include active feedback transmitted by one or more attendee devices <NUM>, via presentation UI <NUM>. For example, the active feedback may comprise questions transmitted by one or more attendees, a live poll, and/or the like.

Referring to <FIG>, a feedback screen <NUM> is illustrated according to various embodiments. The feedback screen <NUM> may comprise a heatmap. The heatmap may be displayed on the presenting device and show the presenter where attendees are looking on the attendee devices. In various embodiments, the locations where attendees are looking may be showed in different colors, shading patterns, or with contour lines. The heatmap may be overlaid over the content, so that the presenter can easily view the content being presented simultaneously as the feedback. For example, the content may comprise three bullet points, and the contour lines may indicate that the majority of attendees are viewing the third bullet point.

The feedback screen may also contain textual data. The textual data may include, for example, the interest score from the voice analysis software, as well as the number of attendees and an increase or decrease in the number of attendees from the thermal analysis software. The feedback screen may also include the words most frequently being spoken by attendees viewing the content.

Referring to <FIG>, a series of audio clips is illustrated according to various embodiments. The audio clips show differences in mood between audio clips. Each section shows the same speaker saying the word "yes" three times, with the exception of the "flat" section, which shows the speaker saying the word "yes" four times. As illustrated, the vertical axis represents frequency, the horizontal axis represents time, and the color represents volume, where black is quiet and grey or white is loud. The "flat" section is a control section to show a normal flat voice. The "interested" section shows the most general complete filling of the natural voice range (the most grey or white filled in between <NUM>-<NUM>). The "excited" section shows a spikey and rapid change in frequency in the <NUM>-<NUM> range, exemplified by larger grey and white lines going from left to right. The "sad" section illustrates more harmonic series amplitude in the <NUM>-<NUM> range. The "angry" section shows more harmonic series amplitude in the <NUM>-<NUM> range. These are a few basic examples of how the voice analysis software may detect moods. In various embodiments, any suitable voice analysis software may be used, and the voice analysis software may detect moods using any suitable technique or process.

Referring to <FIG>, a flowchart <NUM> of a process for presenting content is illustrated according to various embodiments. A presenting device may initiate a presentation of content (step <NUM>). In various embodiments, the content may be stored on the presenting device, a portable storage device, or a remote server. The content may comprise static content or dynamic content. The presenting device may transmit an invitation to attendee devices (step <NUM>). For example, the user of the presenting device may enter email addresses, phone numbers, names, or select attendees from a list of nearby devices discovered by the presenting device or a portable storage device. The presenting device may transmit presentation content to the attendee devices (step <NUM>). In various embodiments, the presentation content may be transmitted or streamed to the attendee devices from or via the presenting device or the portable storage device. In that regard, the presenting device (or the portable storage device) and the attendee devices may be in communication via a common network. The network may comprise the internet. The network may also comprise a local area network (LAN) or may be made available via a travel network router (e.g., travel wireless router) or through any other suitable means. The presentation content displayed on the attendee devices may mirror the presentation content on the presenting device. In various embodiments, the presentation content displayed on the attendee devices may be controlled by the presenting device, such that the presentation content displayed on the attendee device may not mirror the presentation content display on the presenting device.

In various embodiments, the presenting device may also provide the presented content in downloadable form to the attendee devices. In various embodiments, the presented content may be displayed to each attendee device together with one or more engagement feedback tools. For example, an engagement feedback tool may comprise a live poll, a question and answer feature, a chat feature, a contact information exchange feature, a screen sharing or hand raising functionality, and/or the like. In that regard, the engagement feedback tool may allow communications between the presenting device and each respective attendee device.

Sensors on the attendee devices may capture data from the attendees (step <NUM>). In various embodiments, the attendee may be prompted for permission to share sensor data with the presenting device. The attendee devices may transmit the sensor data to the presenting device. The sensors may capture and transmit the senor data to the presenting device in real time, or near real time. In various embodiments, the attendee devices may transmit the sensor data to the portable storage device. In various embodiments, the attendee devices may transmit the sensor data at regularly scheduled intervals, such as once per second, or once per tenth of a second. In various embodiments, the captured data may also include data captured from the engagement feedback tool.

Sensor data processing software may analyze the sensor data and generate an output of analyzed data (step <NUM>). The sensor data processing software may be located on the portable storage device, the presenting device, one or more attendee devices, or a cloud computing system. If the sensor data processing software is located in a cloud computing system, the portable storage device or presenting device may transmit the sensor data to the cloud computing system and receive the analyzed data. The presenting device may display the analyzed data (step <NUM>). Thus, the presenter may view the analyzed data while presenting the content, which may allow the presenter to modify the current presentation or modify subsequent presentations. The portable storage device or the presenting device may store the analyzed data for future reference for the presenter.

In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.

For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein.

As used herein, "transmit" may include sending at least a portion of electronic data from one system component to another. Additionally, as used herein, "data," "information," or the like may include encompassing information such as commands, queries, files, messages, data for storage, and the like in digital or any other form.

As used herein, "electronic communication" may comprise a physical coupling and/or non-physical coupling capable of enabling system components to transmit and receive data. For example, "electronic communication" may refer to a wired or wireless protocol such as a CAN bus protocol, an Ethernet physical layer protocol (e.g., those using 10BASE-T, 100BASE-T, 1000BASE-T, etc.), an IEEE <NUM> interface (e.g., FireWire), Integrated Services for Digital Network (ISDN), a digital subscriber line (DSL), an <NUM>. 11a/b/g/n/ac signal (e.g., Wi-Fi), a wireless communications protocol using short wavelength UHF radio waves and defined at least in part by IEEE <NUM>. <NUM> (e.g., the BLUETOOTH® protocol maintained by Bluetooth Special Interest Group), a wireless communications protocol defined at least in part by IEEE <NUM>. <NUM> (e.g., the ZIGBEE® protocol maintained by the ZigBee alliance), a cellular protocol, an infrared protocol, an optical protocol, or any other protocol capable of transmitting information via a wired or wireless connection.

One or more of the system components may be in electronic communication via a network. As used herein, the term "network" may further include any cloud, cloud computing system, or electronic communications system or method that incorporates hardware and/or software components. Communication amongst the nodes may be accomplished through any suitable communication channels such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (personal digital assistant, cellular phone, kiosk, tablet, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using Internetwork Packet Exchange (IPX), APPLETALK® program, IP-<NUM>, NetBIOS, OSI, any tunneling protocol (e.g., IPsec, SSH, etc.), or any number of existing or future protocols. If the network is in the nature of a public network, such as the internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein.

"Cloud" or "Cloud computing" includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include locationindependent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing.

The various system components may be independently, separately or collectively suitably coupled to the network via data links which includes, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, DISH NETWORKS®, ISDN, DSL, or various wireless communication methods. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.

A network may be unsecure. Thus, communication over the network may utilize data encryption. Encryption may be performed by way of any of the techniques now available in the art or which may become available-e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), HPE Format-Preserving Encryption (FPE), Voltage, Triple DES, Blowfish, AES, MD5, HMAC, IDEA, RC6, and symmetric and asymmetric cryptosystems. Network communications may also incorporate SHA series cryptographic methods, elliptic-curve cryptography (e.g., ECC, ECDH, ECDSA, etc.), and/or other post-quantum cryptography algorithms under development.

As used herein, "satisfy," "meet," "match," "associated with" or similar phrases may include an identical match, a partial match, meeting certain criteria, matching a subset of data, a correlation, satisfying certain criteria, a correspondence, an association, an algorithmic relationship and/or the like. Similarly, as used herein, "authenticate" or similar terms may include an exact authentication, a partial authentication, authenticating a subset of data, a correspondence, satisfying certain criteria, an association, an algorithmic relationship, and/or the like.

The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. As those skilled in the art will appreciate, a user computer may include an operating system (e.g., WINDOWS®, UNIX®, LINUX®, SOLARIS®, MACOS®, etc.) as well as various conventional support software and drivers typically associated with computers.

The present system, or any part(s) or function(s) thereof, may be implemented using hardware, software, or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations or any of the operations may be conducted or enhanced by artificial intelligence (AI) or machine learning. Artificial intelligence may refer generally to the study of agents (e.g., machines, computer-based systems, etc.) that perceive the world around them, form plans, and make decisions to achieve their goals. Foundations of AI include mathematics, logic, philosophy, probability, linguistics, neuroscience, and decision theory. Many fields fall under the umbrella of AI, such as computer vision, robotics, machine learning, and natural language processing. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.

Any communication, transmission, communications channel, channel, and/or the like discussed herein may include any system or method for delivering content (e.g. data, information, metadata, etc.), and/or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and/or capable of being presented electronically. For example, a channel may comprise a website, mobile application, or device (e.g., FACEBOOK®, YOUTUBE®, PANDORA®, APPLE TV®, MICROSOFT® XBOX®, ROKU®, AMAZON FIRE®, GOOGLE CHROMECAST™, SONY® PLAYSTATION®, NINTENDO® SWITCH®, etc.) a uniform resource locator ("URL"), a document (e.g., a MICROSOFT® Word™ or EXCEL®, an ADOBE® Portable Document Format (PDF) document, etc.), an "eBook," an "emagazine," an application or microapplication (as described herein), an SMS or other type of text message, an email, a FACEBOOK® message, a TWITTER® tweet, multimedia messaging services (MMS), and/or other type of communication technology. In various embodiments, a channel may be hosted or provided by a data partner. In various embodiments, the distribution channel may comprise at least one of a merchant website, a social media website, affiliate or partner websites, an external vendor, a mobile device communication, social media network, and/or location-based service. Distribution channels may include at least one of a merchant website, a social media site, affiliate or partner websites, an external vendor, and a mobile device communication. Examples of social media sites include FACEBOOK®, FOURSQUARE®, TWITTER®, LINKEDIN®, INSTAGRAM®, PINTEREST®, TUMBLR®, REDDIT®, SNAPCHAT®, WHATSAPP®, FLICKR®, VK®, QZONE®, WECHAT®, and the like. Examples of affiliate or partner websites include GROUPON®, LIVINGSOCIAL®, and the like. Moreover, examples of mobile device communications include texting, email, and mobile applications for smartphones.

Further, illustrations of the process flows and the descriptions thereof may make reference to user WINDOWS® applications, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of WINDOWS® applications, webpages, web forms, popup WINDOWS® applications, prompts, and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or WINDOWS® applications but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or WINDOWS® applications but have been combined for simplicity.

Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a webpage such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.

In various embodiments, components, modules, and/or engines of any system described herein, or one or more subcomponents of any system, may be implemented as microapplications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a WINDOWS® mobile operating system, an ANDROID® operating system, an APPLE® iOS operating system, a BLACKBERRY® operating system, and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.

In various embodiments, the system may implement middleware to provide software applications and services, and/or to bridge software components in the computer-based system, such as the operating system, database, applications, and the like. Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WEBSPHERE® MQTM (formerly MQSeries) by IBM®, Inc. (Armonk, NY) is an example of a commercially available middleware product. An Enterprise Service Bus ("ESB") application is another example of middleware.

Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term "web page" as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, JAVA® applets, JAVASCRIPT® programs, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous JAVASCRIPT and XML) programs, helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL and an IP address (i.e., <NUM>. The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communication means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art and are covered in many standard texts. As a further example, representational state transfer (REST), or RESTful, web services may provide one way of enabling interoperability between applications.

In various embodiments, one or more servers discussed herein may include application servers (e.g. WEBSPHERE®, WEBLOGIC®, JBOSS®, POSTGRES PLUS ADVANCED SERVER®, etc.). In various embodiments, the server may include web servers (e.g. Apache, IIS, GOOGLE® Web Server, SUN JAVA® System Web Server, JAVA® Virtual Machine running on LINUX® or WINDOWS® operating systems).

Users, systems, computer-based systems or the like may communicate with the server via a web client. The web client includes any device or software which communicates via any network such as, for example any device or software discussed herein. The web client may include internet browsing software installed within a computing unit or system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or set of computers, although other types of computing units or systems may be used, including personal computers, laptops, notebooks, tablets, smart phones, cellular phones, personal digital assistants, servers, pooled servers, mainframe computers, distributed computing clusters, kiosks, terminals, point of sale (POS) devices or terminals, televisions, or any other device capable of receiving data over a network. The web client may include an operating system (e.g., WINDOWS®, WINDOWS MOBILE® operating systems, UNIX® operating system, LINUX® operating systems, APPLE® OS® operating systems, etc.) as well as various conventional support software and drivers typically associated with computers. The web-client may also run MICROSOFT® INTERNET EXPLORER® software, MOZILLA® FIREFOX® software, GOOGLE® CHROME® software, APPLE® SAFARI® software, or any other of the myriad software packages available for browsing the internet.

As those skilled in the art will appreciate, the web client may or may not be in direct contact with the server (e.g., application server, web server, etc., as discussed herein). For example, the web client may access the services of the server through another server and/or hardware component, which may have a direct or indirect connection to an internet server. For example, the web client may communicate with the server via a load balancer. In various embodiments, web client access is through a network or the internet through a commerciallyavailable web-browser software package. In that regard, the web client may be in a home or business environment with access to the network or the internet. The web client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A web client may implement several application layer protocols including HTTP, HTTPS, FTP, and SFTP.

Any databases discussed herein may include relational, hierarchical, graphical, blockchain, object-oriented structure, and/or any other database configurations. In various embodiments, any database may also include a no-SQL database, a key-value database, an inmemory database, a GPU database, and/or the like. Any database may also include a flat file structure wherein data may be stored in a single file in the form of rows and columns, with no structure for indexing and no structural relationships between records. For example, a flat file structure may include a delimited text file, a CSV (comma-separated values) file, and/or any other suitable flat file structure. Common database products that may be used to implement the databases include DB2® by IBM® (Armonk, NY), various database products available from ORACLE® Corporation (Redwood Shores, CA), MICROSOFT ACCESS® or MICROSOFT SQL SERVER® by MICROSOFT® Corporation (Redmond, Washington), MYSQL® by MySQL AB (Uppsala, Sweden), MONGODB®, Redis, Apache Cassandra®, HBASE® by APACHE®, MapR-DB by the MAPR® corporation, or any other suitable database product. Moreover, any database may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields, or any other data structure.

Any database discussed herein may comprise a distributed ledger maintained by a plurality of computing devices (e.g., nodes) over a peer-to-peer network. Each computing device maintains a copy and/or partial copy of the distributed ledger and communicates with one or more other computing devices in the network to validate and write data to the distributed ledger. The distributed ledger may use features and functionality of blockchain technology, including, for example, consensus-based validation, immutability, and cryptographically chained blocks of data. The blockchain may comprise a ledger of interconnected blocks containing data. The blockchain may provide enhanced security because each block may hold individual transactions and the results of any blockchain executables. Each block may link to the previous block and may include a timestamp. Blocks may be linked because each block may include the hash of the prior block in the blockchain. The linked blocks form a chain, with only one successor block allowed to link to one other predecessor block for a single chain. Forks may be possible where divergent chains are established from a previously uniform blockchain, though typically only one of the divergent chains will be maintained as the consensus chain. In various embodiments, the blockchain may implement smart contracts that enforce data workflows in a decentralized manner. The system may also include applications deployed on user devices such as, for example, computers, tablets, smartphones, Internet of Things devices ("IoT" devices), etc. The applications may communicate with the blockchain (e.g., directly or via a blockchain node) to transmit and retrieve data. In various embodiments, a governing organization or consortium may control access to data stored on the blockchain. Registration with the managing organization(s) may enable participation in the blockchain network.

Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a "key field" in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out ("I/O") bottlenecks.

Terms and phrases similar to "associate" and/or "associating" may include tagging, flagging, correlating, using a look-up table, or any other method or system for indicating or creating a relationship between data elements. Moreover, the associating may occur at any point, in response to any suitable action, event, or period of time. The associating may occur at predetermined intervals, periodic, randomly, once, more than once, or in response to a suitable request or action. Any of the information may be distributed and/or accessed via a software enabled link, wherein the link may be sent via an email, text, post, social network input, and/or any other method known in the art.

One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers, or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database, system, device, server, and/or other component includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.

Encryption of data in one or more databases, may be performed by way of any of the techniques now available in the art or which may become available-e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), HPE Format-Preserving Encryption (FPE), Voltage, Triple DES, Blowfish, AES, MD5, HMAC, IDEA, RC6, and symmetric and asymmetric cryptosystems. The systems and methods may also incorporate SHA series cryptographic methods, elliptic-curve cryptography (e.g., ECC, ECDH, ECDSA, etc.), and/or other post-quantum cryptography algorithms under development.

A firewall may include any hardware and/or software suitably configured to protect CMS components and/or enterprise computing resources from users of other networks. Further, the firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connecting through a web server. The firewall may reside in varying configurations including Stateful Inspection, Proxy based, access control lists, and Packet Filtering among others. The firewall may be integrated within a web server or any other CMS components or may further reside as a separate entity. The firewall may implement network address translation ("NAT") and/or network address port translation ("NAPT"). The firewall may accommodate various tunneling protocols to facilitate secure communications, such as those used in virtual private networking. The firewall may implement a demilitarized zone ("DMZ") to facilitate communications with a public network such as the internet. The firewall may be integrated as software within an internet server, any other application server components or may reside within another computing device or may take the form of a standalone hardware component.

The system and method may be described herein in terms of functional block components, screen shots, optional selections, and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, JAVA®, JAVASCRIPT®, JAVASCRIPT® Object Notation (JSON), VBScript, Macromedia COLD FUSION, COBOL, MICROSOFT® company's Active Server Pages, assembly, PERL®, PHP, awk, PYTHON®, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX® shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JAVASCRIPT®, VBScript, or the like.

In various embodiments, the software elements of the system may also be implemented using a JAVASCRIPT® run-time environment configured to execute JAVASCRIPT® code outside of a web browser. For example, the software elements of the system may be implemented using NODE. JS® components. JS® programs may implement several modules to handle various core functionalities. For example, a package management module, such as NPM®, may be implemented as an open source library to aid in organizing the installation and management of third-party NODE. JS® programs. JS® programs may also implement a process manager such as, for example, Parallel Multithreaded Machine ("PM2"); a resource and performance monitoring tool such as, for example, Node Application Metrics ("appmetrics"); a library module for building user interfaces, and/or any other suitable or desired module.

As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, a processing apparatus executing upgraded software, a stand-alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, any portion of the system or a module may take the form of a processing apparatus executing code, an internet-based embodiment, an entirely hardware embodiment, or an embodiment combining aspects of the internet, software, and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, SONY BLU-RAY DISC®, optical storage devices, magnetic storage devices, and/or the like.

The term "non-transitory" is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term "non-transitory computer-readable medium" and "non-transitory computer-readable storage medium" should be construed to exclude only those types of transitory computer-readable media which were found in In re Nuijten to fall outside the scope of patentable subject matter under <NUM> U.

The scope of the disclosure is accordingly limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more. " Moreover, where a phrase similar to `at least one of A, B, and C' or `at least one of A, B, or C' is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

Claim 1:
A method comprising:
transmitting, by a presenting device (<NUM>), a presentation content to an attendee device (<NUM>) via a standardized communication protocol, wherein the presenting device (<NUM>) and the attendee device (<NUM>) are in electronic communication;
receiving, by the presenting device (<NUM>), sensor data from the attendee device (<NUM>), wherein the sensor data is captured by the attendee device (<NUM>) in response to the presentation content being displayed on the attendee device (<NUM>);
displaying, by the presenting device (<NUM>), the sensor data on the presenting device (<NUM>), wherein the sensor data is displayed with the presentation content on the presenting device (<NUM>);
analyzing, by the presenting device (<NUM>), the sensor data;
generating, by the presenting device (<NUM>), an analyzed sensor data based on the sensor data, wherein the analyzed sensor data is generated using sensor data processing software; and
displaying, by the presenting device (<NUM>), the analyzed sensor data on the presenting device (<NUM>), wherein the sensor data is displayed with the presentation content,
wherein the receiving of the sensor data from the attendee device (<NUM>) is via the standardized communication protocol,
wherein each of the presenting device (<NUM>) and the attendee device (<NUM>) are configured to communicate via the standardized communication protocol by transmitting a standardized communication protocol header with at least one of a packet or datagram to identify the packet or datagram as following the standardized communication protocol, and
wherein the standardized communication protocol defines an ability for the presenting device (<NUM>) and the attendee device (<NUM>) to discover one another, to request the transfer of the presentation content and the sensor data, to transmit confirmations on receipt of the presentation content and the sensor data, and to transmit the presentation content and the sensor data.