Abstract:
The present invention is an event feedback networking system configured to facilitate intuitive participant response. The event feedback networking system utilizes novel distributed hardware components and novel data structures for obtaining, processing, analyzing, and displaying intuitive user feedback.

Description:
FIELD OF INVENTION 
       [0001]    The present invention is a computer apparatus for measuring, displaying and compiling data related to human cognitive reactions to a defined event. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0002]      FIG. 1  is an exemplary embodiment of an event feedback networking system. 
           [0003]      FIG. 2  illustrates an exemplary embodiment of a real-time event feedback system which provides two-way feedback to users. 
           [0004]      FIG. 3   a  illustrates an exemplary embodiment of an event feedback networking system with a closed group of participants. 
           [0005]      FIG. 3   b  illustrates an exemplary embodiment of an event feedback networking system with an open group of participants. 
           [0006]      FIG. 4  is an exemplary embodiment of an event feedback networking system which is capable of creating time-segmented event data. 
           [0007]      FIG. 5  illustrates an exemplary embodiment of an event feedback networking system in which data is processed and provided to data recipients correlated with sampled time units. 
           [0008]      FIG. 6  illustrates an exemplary revenue model with backend revenue processing. 
       
    
    
     GLOSSARY  
       [0009]    As used herein, the term “backend processor” refers to a computer processor configured with software for processing and recording payment transactions. 
         [0010]    As used herein, the term “data recipient” means an entity, individual or computer component that requests data. A data recipient may create a data request object and/or invoke functions for processing data. Data may include spontaneous user feedback, demographic data, or any other data capable of being received, collected or produced by the components of an event feedback networking system. 
         [0011]    As used herein, the term “distributed” means that physical components, data recipients, and/or participants may be in a single location or in multiple locations. 
         [0012]    As used herein, the term “event” means an experience which may be shared by more than one participant and for which a measurable, cognitive response may be elicited. An event may be experienced by each participant at different times, in different locations, in different formats or in different segments of the event. 
         [0013]    As used herein, the term “event feedback database” refers to stored event records, feedback records, and participant records. An event feedback database may reside on a single server or across multiple servers. 
         [0014]    As used herein, the term “event record” means an occurrence reflected as a record in a database. Information contained in an event record may include, but is not limited to, the name, time, geographical location, type, and sponsor of an event. 
         [0015]    As used herein, the term “event record object” means a compilation of attributes and behaviors that encapsulates an event record. 
         [0016]    As used herein, the term “feedback” or “spontaneous user feedback” means a measurable, cognitive response or information a participant provides in response to an event. Feedback may include, but is not limited to, voting, manipulation of a computer component, physical responses, and providing ratings, rankings and biofeedback, and indications of change, no change, user participation and user non-participation. 
         [0017]    As used herein, the term “feedback record” means a data structure in which data derived from user feedback is stored. 
         [0018]    As used herein, the term “feedback record object” means any data structure that includes at least one attribute and/or function for user creating, changing and manipulating user feedback objects that encapsulate a feedback record. 
         [0019]    As used herein, the term “group attribute” means an attribute that defines a group or participants which can instantiate and modify user feedback record objects. 
         [0020]    As used herein, the term “instantiate” means to create an instance of a software object. 
         [0021]    As used herein, the term “invoke” means to call a function. 
         [0022]    As used herein, the term “network connection” means any software or hardware that allows two or more computers or devices to communicate with one another. 
         [0023]    As used herein, the term “record object” or “object” means a data structure which includes data attributes and functions which define the functionality of an apparatus. 
         [0024]    As used herein, the term “participant input device” or “intuitive input device” means any device capable of receiving input used to modify at least one user feedback object. A participant communication device may be any form of input hardware including, but not limited to, keyboards, iPods™, personal listening and viewing devices, telephony, devices capable of measuring biofeedback, kinetic sensing devices which measure the presence or absence of motion, facial recognition and video and audio recorders. A participant input device may include an intuitive input device if it is designed to make the user comfortable or unaware with the device so that cognitive thought related to the process of providing feedback is minimized or not needed for the collection of user feedback. 
         [0025]    As used herein, the term “participant record” means a data structure which stores data and/or attributes associated with a participant. Examples of data which may be included in a participant record include, but are not limited to, demographic data, user IDs, and information contained in a social network profile (SNP) record. 
         [0026]    As used herein, the term “participant record object” means a compilation of attributes and behaviors that encapsulate a participant record. 
         [0027]    As used herein, the term “physical storage component” means any physical data storage device, including, but not limited to, computer memory, disks, internal or external hard drives, flash drives, and other memory devices. 
         [0028]    As used herein, the term “rate plan tracking mechanism” means one or more devices configured individually or in combination to track payment and the amount received as payment for data. 
         [0029]    As used herein, the term “real time” means during a single user session, event, an instance, time segment of an event, time segment related to an external measurement, or other time period defined by a user, participant, data recipient or administrator. 
         [0030]    As used herein, the term “record” means related data treated as a unit. 
         [0031]    As used herein, the term “revenue processing component” means any software or hardware component utilized for processing payments or credits or validating user privileges associated with the exchange of data. 
         [0032]    As used herein, the term “sampled time unit” means a measurable unit of time into which the duration of an event is segmented. 
         [0033]    As used herein, the term “segment” means a unit that represents a portion of data associated with an event object or record or an event in progress. For example, a time segment means a portion of an event which occurred within a specific time frame. 
         [0034]    As used herein, the term “time segmenting function” means a function that segments an event record into time intervals. 
         [0035]    As used herein, the term “unique device identification number attribute” refers to an attribute of a participant record object that associates a specific participant with a specific input device. 
         [0036]    As used herein, the term “user feedback measurement function” means a function that measures changes in at least one attribute of a feedback record object or record. 
         [0037]    As used herein, the term “user interface” is an interface that allows a user to enter input and to interact with one or more components and/or record objects of an event feedback monitoring system. 
         [0038]    As used herein, the term “viewable feedback interface” refers to any means of communication between an event feedback database and a user that allows the user or data recipient to view feedback. 
       BACKGROUND 
       [0039]    Millions of events are broadcast, televised, hosted and staged each day. Events generally are intended for more than one participant, although an event may be experienced at different, times, locations and through different media for various participants. Participants may also view or be present during only part of an event. 
         [0040]    Events may be intended to communicate, entertain, and/or educate. However, all events evoke a unique cognitive response from each participant. 
         [0041]    Companies, television networks, training professionals, and event sponsors seek public opinion regarding the effectiveness of advertisements, scheduling of television shows, entertainment value of events, and a myriad of other qualities of the services provided. Focus groups and surveying participants or viewers may be used to receive feedback regarding advertisements, television shows, or other events. Focus groups and surveys, however, are costly and may be conducted in environments and under circumstances which by their very nature alter the spontaneity of the user response. 
         [0042]    Electronic survey devices may allow participants to respond to particular questions and prompts instantaneously, but these devices lack the capability and are not designed to continuously compile data in real time and do not offer two-way, interactive feedback to users as they are providing feedback. 
         [0043]    Electronic survey devices do not capture continuous, spontaneous and intuitive responses. Participants may be limited by responding to a prompt or cue. 
         [0044]    Additionally, methods of surveying users in real time have traditionally required the involvement of event creators and sponsors. 
         [0045]    Methods and tools in the art are not adapted to allow participants to spontaneously view or otherwise participate in an event and provide feedback in their own environment without the involvement of event creators and sponsors. 
         [0046]    Tools known in the art are not designed to provide two-way feedback to participants to alter the participants&#39; response or choice of event during the feedback gathering process. These tools are not designed to take into account a population demographic which is conditioned to use social networking tools and may desire to provide feedback as part of an overall social networking experience. 
         [0047]    It is desirable to provide a system of collecting participant feedback from both closed groups of participants and open groups of participants. 
         [0048]    It is further desirable to provide a system of collecting participant feedback where participants may respond instantaneously and intuitively. 
       SUMMARY OF THE INVENTION 
       [0049]    The present invention is an event feedback networking system configured to facilitate intuitive participant response. The event feedback networking system utilizes novel distributed hardware components and novel data structures for obtaining and processing user feedback. In various embodiments, the apparatus may be configured to process novel data structures including, but not limited to, event record objects, feedback record objects, participant record feedback objects, and one or more hardware components, such as a processor which may process data, segment events, respond to data requests by data recipients and process event record objects and participant record objects when the functions of a feedback record object are invoked. 
       DETAILED DESCRIPTION OF INVENTION 
       [0050]    For the purpose of promoting an understanding of the present invention, references are made in the text to exemplary embodiments of software and hardware components for collecting and analyzing real-time participant feedback and communicating with participants in a social networking environment, only some of which are described herein. It should be understood that no limitations on the scope of the invention are intended by describing these exemplary embodiments. One of ordinary skill in the art will readily appreciate that alternate but functionally equivalent hardware, computer components, software objects, and other data structures may be used. The inclusion of additional elements may be deemed readily apparent and obvious to one of ordinary skill in the art. Specific elements disclosed herein are not to be interpreted as limiting, but rather as a basis for the claims and as a representative basis for teaching one of ordinary skill in the art to employ the present invention. 
         [0051]    It should be understood that the drawings are not to scale; instead, emphasis has been placed upon illustrating the principles of the invention. In addition, in the embodiments depicted herein, like reference numerals in the various drawings refer to identical or near identical structural elements. 
         [0052]    Moreover, the terms “substantially” or “approximately” as used herein may be applied to modify any quantitative representation that could permissibly vary without resulting in a change in the basic function to which it is related. 
         [0053]      FIG. 1  is an exemplary embodiment of event feedback networking system  100 . The exemplary embodiment shown includes user interface  88  which is in communication with at least one server  25  which includes at least one processor  15 . In the exemplary embodiment shown, server  25  includes event record objects  50   a ,  50   b  and  50   c  which may be created by an administrator and displayed via user interface  88 , or which may be created on a spontaneous and/or continuous basis by participants  75   a ,  75   b , and  75   c.    
         [0054]    In the embodiment shown, exemplary event record object  50   a  is a software object which includes data pertaining to an event which is a live concert attended by participants  75   a ,  75   b , and  75   c . The event associated with event record object  50   b  is a televised political speech, and the event associated with event record object  50   c  is a television show. 
         [0055]    In various embodiments, server  25  may store and update any number of event record objects which may be instantiated and modified by a user, administrator, event host, participant, or any other person or entity authorized to instantiate an event record object. 
         [0056]    In the exemplary embodiment shown, participants  75   a ,  75   b , and  75   c  are associated with participant record objects  70   a ,  70   b , and  70   c . Participant record objects  70   a ,  70   b , and  70   c  are configured with functions that allow a user to create and/or modify attributes of an event record object  50   a  and to instantiate feedback record objects  60   a ,  60   b , and  60   c  through user interface  88 . 
         [0057]    Participant record objects  70   a ,  70   b , and  70   c  include attributes and data associated with a specific user. Participant record objects  70   a ,  70   b , and  70   c  may further include functions for modifying such attributes. 
         [0058]    In the embodiment shown, feedback record objects  60   a ,  60   b , and  60   c  are modified by user actions performed by participants  75   a ,  75   b , and  75   c  on user interface  88 . Values and attributes of feedback record objects  60   a ,  60   b , and  60   c  are passed to processor  15  for compilation, tracking, tabulation, scoring and display and for use by data recipients  92   a ,  92   b , and  92   c  who may purchase feedback data. In various embodiments, feedback data may or may not undergo additional processing for use by data recipients  92   a ,  92   b , and  92   c.    
         [0059]    Event record objects  50   a ,  50   b , and  50   c  contain data related to any known attributes pertaining to a particular occurrence or event, including, but not limited to, the name, time, location and sponsor of the event or any event data that can be represented symbolically, mathematically or linguistically. Cursory examples of events may include, but are not limited to, advertisements, television shows, movies, live concerts or broadcasts, dining experiences, sporting events, political debates, training exercises, assignments, travel experiences, and other relatable experiences. 
         [0060]    In various embodiments, participants  75   a ,  75   b , and  75   c  may invoke functions through a user to modify and/or update attributes of a specific participant record or object, such as age, gender, location, and any other demographic information that may be compiled about a participant. In exemplary embodiments, participant record objects  70   a ,  70   b , and  70   c  may also be linked to a social network profile (SNP) created by user or a third party administrator of such profiles (e.g., MySpace or Facebook). 
         [0061]    Feedback record objects  60   a ,  60   b , and  60   c  may be updated by any function known in the art for measuring feedback and reactions of participants  75   a ,  75   b , and  75   c  in response to an event. In various embodiments, participant feedback may include responses consciously submitted by a participant, such as a rating or indication along a sliding scale, and unconscious responses, such as recorded laughter or skin conductivity. Processor  15  is configured to modify event record objects  50   a ,  50   b , and  50   c  and participant record objects  70   a ,  70   b , and  70   c  when the functions of feedback record objects  60   a ,  60   b , and  60   c  are invoked. 
         [0062]    In the embodiment shown, participant  75   a  enters feedback using participant input device  78 , and attributes of participant record object  70   a  may be modified based on participant input. Feedback record object  60   a  may also be modified or instantiated. 
         [0063]    In still other embodiments, participant input device  78  may be equipped with attributes which are modified in response to changes in location, participant position, participant input (such as manipulating a touch pad or galvanometer), biofeedback, audio feedback, incrementation, or any other method or instrument known in the art to identify any form of user response capable of being measured and/or quantified and further used to modify attributes of feedback record objects  60   a ,  60   b , and  60   c.    
         [0064]    In various embodiments participant input device  78  may be an intuitive input device configured with any sensor, tracking component, video or audio device, ergonomic or anthropometric physical contour or configuration to make the process of providing feedback as intuitive as possible for a user. 
         [0065]    In various exemplary embodiments, participant input device  78  may include a keyboard, typewriter, cash register, touch-sensitive computer interface, voice recognition device, the certificate itself, paper document, a wireless device, laptop computer, mobile phone, personal information device, personal digital assistant, hand-held device, network appliance, pager, an analog device or a device used manually, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, a server, a mechanism capable of reading biological information, a document reader or scanner, any other recording device commonly known and used in the art, and combinations thereof. 
         [0066]    Processor  15  measures the change in participant record object  70   a  and feedback record object  60   a  to update feedback record object  60   a  and event record object  50   a . In further embodiments, processor  15  may also be adapted to display updated information on user interface  88 . 
         [0067]    In other embodiments, participant input device  78  may be an intuitive input device adapted to receive biofeedback and other nonconscious responses to an event. For example, in another embodiment, participant input device  78  may contain a galvanometer to record skin conductivity. In another embodiment, participant input device  78  may be adapted to record heart and respiration rates. In still other embodiments, participant input device  78  may contain an audio or visual recording device to record verbal or facial responses. 
         [0068]      FIG. 2  illustrates an exemplary embodiment of event feedback networking system  100  providing two-way feedback to users and which includes viewable feedback interface  89 . Participant  75  enters event feedback using participant input device  78  which may be configured for intuitive feedback. Participant input device  78  establishes network connection  79  with event feedback networking system  100  and feedback is stored in feedback record object  60 . Feedback record object  60  is located in physical storage component  10 . Feedback record object  60  is associated with event record object  50  and feedback stored in feedback record object  60 , and may be displayed with viewable feedback interface  89 . 
         [0069]    In the embodiment shown in  FIG. 2 , participant  75  is responding to a televised event. In other embodiments, participants may respond to any televised or non-live event, including, but not limited to, podcasts and web conferences. In still further embodiments, participants may be able to respond to any live event, including, but not limited to, sporting events, political debates, lobbying events, training and teaching exercises, simulated events, customer experiences, and other personal experiences to provide a semi-real time emotional response. 
         [0070]      FIGS. 3   a  and  3   b  illustrate exemplary embodiments of event feedback networking system  100  in use by both a closed group of participants  75   a ,  75   b , and  75   c  and an open group of participants  75   d ,  75   e , and  75   f.    
         [0071]    In various embodiments, each participant in either an open or closed participant group may be assigned a unique identification number or may use a participant input device  78  assigned a unique device ID number. In still other embodiments, participant record identifying information and device ID numbers may be used by a participant to log into an event record and provide feedback for that event. 
         [0072]      FIG. 3   a  illustrates an embodiment of event feedback networking system  100  in which a closed group of participants must enter a code or access a designated device and be validated by a user validation processor. In the exemplary embodiment shown, closed group of participants  75   a ,  75   b , and  75   c  are selected for survey and data gathering, and provided with authorization and access to create and/or modify feedback record objects  60 .  FIG. 3   a  further includes authentication server  23  for providing functions such as creating participant record objects  70   a ,  70   b , and  70   c , deleting participant record objects  70   a ,  70   b , and  70   c , authenticating participants attempting to access participant record objects  70   a ,  70   b , and  70   c , modifying participant record objects  70   a ,  70   b , and  70   c  and managing access to event record objects  50   a ,  50   b , and  50   c  and one or more user interfaces  88 . 
         [0073]    In the exemplary embodiment shown in  FIG. 3   a , feedback record object  60  contains a group attribute which may only be modified by a closed group of participants. Participants  75   a ,  75   b , and  75   c  use participant input devices  78   a ,  78   b , and  78   c  to enter feedback about an event. Feedback is stored in feedback record object  60 , and processor  15  measures changes in feedback record object  60  using a user feedback measurement function. Feedback record object  60  and event record object  50  are located on physical storage component  10 . In further embodiments, feedback may be visually or graphically displayed. 
         [0074]      FIG. 3   b  is an exemplary embodiment of event feedback networking system  100  with an open group of participants. Feedback record object  60  contains a group attribute which indicates that feedback will be accepted from any participant with privileges to instantiate or modify feedback record object  60 . Participants  75   d ,  75   e , and  75   f  use participant input devices  78   d ,  78   e , and  78   f  to enter feedback about an event. Feedback is stored in feedback record object  60 , and processor  15  measures changes in feedback record object  60  using a user feedback measurement function. Feedback record object  60  and event record object  50  are located on physical storage component  10 . In further embodiments, feedback may be visually or graphically displayed. 
         [0075]      FIG. 4  is an exemplary embodiment of event feedback networking system  100  which is capable of creating time segmented event data. In the embodiment shown, event record objects  50   a ,  50   b , and  50   c  may include or respond to functions invoked by other objects which cause events to be broken down into sampled time units  55   a ,  55   b , and  55   c  by modifying event record objects  50   a ,  50   b , and  50   c  or instantiating separate sampled time unit objects  56   a ,  56   b , and  56   c.    
         [0076]    In further embodiments, events may be broken down into units or event record objects, and sampled time unit objects may be modified and/or instantiated based on other defining intervals, such as presenter, topic, course or location. 
         [0077]      FIG. 5  illustrates an exemplary embodiment of event feedback networking system  100  in which data is processed and provided to data recipients  92   a ,  92   b , and  92   c  correlated with sampled time units  55   a ,  55   b , and  55   c.    
         [0078]    In further embodiments, feedback may be graphically displayed on viewable feedback interface  89 , and data recipients  92   a ,  92   b , and  92   c  may create data requests  91   a ,  91   b , and  91   c . For example, data may include, but is not limited to, data of users and data collected using user feedback objects. Data may be extracted from real time feedback, sampled feedback, time-segmented feedback, post-event feedback, comparative data, randomized data, matched data sets, statistically filtered data, demographically filtered data, and/or data filtered by an identifiable or randomized group characteristic. Data may further include data derived from comparison of user feedback from multiple events in real time, or data which is matched and compared for any number of real-time and past events, including data derived from time segments of events. 
         [0079]      FIG. 6  illustrates an exemplary revenue model with backend revenue processing  500 . Physical storage component  10  contains data recipient object  90 , which is configured with attributes and functions to enable data recipient  92  to receive user feedback. Data recipient  92  may purchase raw, compiled or analyzed data. Data recipients may include, but are not limited to, market analysts, companies, corporations, market surveyors, advertising agencies, event hosts, consumer groups, political analysts, political candidate groups, and any other group who wants data and will pay for it. User feedback processor  93  processes data requested by data recipient object  90 . 
         [0080]    Back end processor  94  with user interface  95  processes revenue and payment transactions from data recipient  92  using a defined rate plan and rate tracking mechanism. The term “rate plan” as used herein means a distribution of revenue from the sale of data or among one or more data recipients, based upon policies, percentages and statistical or other information. 
         [0081]    In further embodiments, data requests by a data recipient may be facilitated by a data recipient user interface  97  configured to accept data requests.