WO2002003723A1

WO2002003723A1 - Network-based event reporting system

Info

Publication number: WO2002003723A1
Application number: PCT/US2001/021076
Authority: WO
Inventors: Marc Vanlerberghe; Alan Toman
Original assignee: Quios, Inc.
Priority date: 2000-06-29
Filing date: 2001-06-29
Publication date: 2002-01-10
Also published as: AU2001271776A1

Abstract

A network based method and system for controlling the reception and transmission of event reports (11-17) among numerous users (2-5). A network user (wireless or wired) (2-5) registers with a server (6) to report on a selected event (18), and thus becomes a reporter (56). Multiple network users (2-5) may then subscribe with the server (6) to receive the reports submitted by the reporter (56). Subsequently, the reporter (56) submits a report to the server (6), the server (6) immediately searches to find all subscribers to reports by the reporter, and the report is immediately disseminated to each found subscriber. The subscribers preferably receive the report on cellular/digital phones (5) that allow wireless messaging (7-8). Subscribers may also receive reports at any other location (e.g. PDA (3) or e-mail (4) account) in any format desired.

Description

NETWORK-BASED EVENT REPORTING SYSTEM

BACKGROUND OF THE INVENTION

Field Of The Invention

The present invention concerns techniques by which a network user, such as a wireless network or internet user, may register to report on specific events and subsequently submit reports regarding the events to a server. The server then automatically transmits the reports via the network (wireless or wired) to subscribers that desire the particular reports.

Description Of The Related Art

Technology for transmitting and receiving wireless messages is . rapidly increasing and expanding wireless messaging possibilities. Currently, methods and systems exist for transmitting and receiving wireless messages from wireless cellular and digital phones, Personal Digital Assistant's (PDA's), such as Palm's wireless Palm Pilot VII, and notebook or desktop computers in communication with a wireless network or internet server. Hereinafter the terms 'cell phone', 'digital phone', and 'wireless phone' are synonymously used to represent a general class of wireless devices that support wireless messaging. Wireless messages are typically sent from a single sender to a single receiver, or list of receivers, using various wireless technologies. For example, a sender may send a digital text message to a cell phone user by logging on to a internet site for wireless messaging, such as the Quios.com site. The sender then enters the telephone number of the destination cell phone and a text message to be sent to the cell phone. The message is instantly transmitted to the cell phone and the cell phone user is immediately able to read the text message. In another example, a Palm Pilot VII user may enter a e-mail and send the e-mail to any e-mail account without any physical wiring. In addition, the Palm Pilot VII user may also receive e-mail messages from any other e-mail user without ever being physically wired to a network, such as the internet .

Because of the instantaneous nature of wireless communications, it has been considered for use in situations where a first user, who is attending an event, transmits real-time reports on the event to. another user or users. Heretofore, however, there has not existed an efficient architecture to ensure that users are available to report on events, and to ensure that reports are disseminated to other users who have interest in receiving them.

SUMMARY OF THE INVENTION The present invention addresses the above- noted deficiencies in the art by providing a network based method and system for controlling the reception and transmission of event reports among numerous users . Thus, the present invention permits a network user to register with a server as a reporter and to report on events selected from a list of events stored on the server.

User's may communicate with the server through any type of network, including, among others, an internet communication network, a wireless network in direct communication with the server, or a local area network. In a first embodiment, a user communicates with the server using a wireless device, such as a cell-phone, PDA, or wireless modem, via a wireless communication network in direct communication with the server. In a second embodiment, a user communicates with the server via a connection to the internet . Internet users may access the internet using any wireless internet device

(including, among others, cell phones and PDA's) or any device hard wired to the internet (e.g. through a dial- up or network connection) .

Users may also add events to the event list stored on the server, such as: local events, spontaneous events (e.g. disasters or riots) or any other event not already listed on the event list. After the reporter is registered to report on an event, other users may subscribe with the server to receive the reports submitted by the reporter. Multiple users may subscribe to receive a specific reporter's reports. Subsequently, when the reporter submits a report to the server, the server immediately searches to find all subscribers to reports by the particular reporter regarding the particular event, and the report is immediately disseminated to each found subscriber. In effect, one reporter may instantly send event reports- to thousands of subscribers around the world. In the preferred embodiment, the subscribers receive the report on cellular/digital phones that allow wireless messaging. Subscribers may also receive reports at any other location (e.g. PDA or e-mail account) in any format desired.

Thus, in one aspect, the present invention registers reporters to submit reports to a server corresponding to an event. Specifically, an event is selected from a computer-generated display of event identifiers and event characteristics are submitted for the selected event, wherein the characteristics are submitted over the network. From the server's perspective, a selection and event characteristics are received from the reporter corresponding to an event selected from a computer generated list of event identifiers, wherein the characteristics are submitted over the network. In one embodiment, the network is an internet communication network. In another embodiment the network is a wireless communication network. In another embodiment the network is a local area network. In another embodiment, the computer-generated display of events includes events entered by the reporter, including spontaneous events. In another embodiment, the event characteristics include at least one of : coverage description, reporting language, time zone, start date and time, end date and time, and maximum reports per day. In yet another embodiment, the reporter receives a registration confirmation through the network. In still another embodiment, the reporter receives a reminder message some time after registration for the event and before the event occurs. In another aspect, according to the present invention, reporters submit reports corresponding to a specific event to a server. Specifically, an event is selected from a computer generated list of event identifiers to which a reporter is registered, report information is entered in a computer generated interface, and the report is submitted to the server, wherein the report is transmitted to the server through the network. From a server's perspective, a server receives a report from a reporter. Specifically, an event selection is received from a registered reporter, a computer-generated interface for the reporter to enter the report is provided, and the report is received through the network. In one embodiment, the network is an internet communication network. In another embodiment the network is a wireless communication network. In another embodiment the network is a local area network. In another embodiment, the report information may include one or more of the following media formats: text, still graphics, video, and audio. In another embodiment, a confirmation report is received by the reporter to confirm the report has been received by the server.

In another aspect, according to the present invention, reports regarding a selected event are received. Specifically, an event is selected from a computer generated list of events, a reporter is selected from a computer generated list of reporters, and a report is received from the server, wherein the report corresponds to the selected event and the selected reporter. From the server's perspective, according to the present invention, reports regarding a selected event are transmitted. Specifically, an event selection and a reporter selection are received, and a report is transmitted to the server, wherein the report corresponds to the selected event and the selected reporter. In one embodiment, the network is an internet communication network. In another embodiment the network is a wireless communication network. In another embodiment the network is a local area network. In another embodiment, a desired format for the report is selected and a desired location for the report to be transmitted is selected. In another embodiment, the desired format may include one or more of the following: ascii, ansi, rtf, html, Java, mpeg, asf, wav, mp3, jpeg, gif, bmp, tif . In yet another embodiment, the desired transmission location may be one or more of the following: telephone number, e-mail address, IP address, or network address.

In another aspect, according to the present invention, a report submitted by a registered reporter is disseminated to subscribers. Specifically, a server receives a report submitted by a registered reporter corresponding to a specific event, the server searches a database to determine which subscribers have subscribed to receive reports from the registered reporter corresponding to the specific event, and the report is transmitted to all subscribers found in the searching, wherein the report is disseminated immediately to the subscribers found in the searching. In one embodiment, the network is an internet communication network. In another embodiment the network is a wireless communication network. In another embodiment the network is a local area network. In another embodiment, the transmission of each respective report is done according to a transmission location and transmission format selected by each respective subscriber. In another embodiment, a rating criteria is submitted in response to a received report, wherein the rating is selected by a subscriber in reference to the subscribers perceived quality level of a received report, wherein the submission is transmitted to the server over the network.

The brief summary of the invention is provided so that the nature of the invention may be understood quickly. A fuller understanding may be obtained by reference to the following detailed description of the invention in connection with the appended drawings .

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram describing one embodiment of the present invention;

FIG. 2 is a flow diagram describing the method of registering a user as a reporter for a specific event;

FIG. 3 is a flow diagram describing the method of submitting a report by a registered reporter;

FIG. 4 is a flow diagram describing the method of subscribing to receive a report from a registered reporter;

FIG. 5 is a flow diagram describing the method of disseminating a report to subscribers;

FIG. 6 is a graphical user interface depicting a server home page; FIG. 7 is a graphical user interface depicting a top level topic selection interface;

FIG. 8 is a graphical user interface depicting a second level topic selection interface; FIG. 9 is a graphical user interface depicting an event level selection interface;

FIG. 10 is a graphical user interface depicting a reporter descriptions interface;

FIG. 11 is a graphical user interface depicting a reporter assignment interface; FIG. 12 is a graphical user interface depicting a user summary interface;

FIG. 13 is a graphical user interface depicting a submit report interface;

FIG. 14 is a graphical user interface depicting a reporter rating interface; and FIG. 15 is a graphical user interface depicting an add event interface.

DETAILED DESCRIPTION OF THE DRAWINGS FIG. 1 is a flow diagram describing one embodiment of the present invention. Briefly, according to FIG. 1, a reporter registers to report on a specific event and a subscriber who wishes to receive reports subscribes to specific events from specific reporters. Thereafter, when the reporter submits a report the report is disseminated automatically by a server to all subscribers for that report. Preferably, the report is transmitted instantaneously by wireless communication to the subscriber, so that all subscribers receive it in near real-time to its submission by the reporter. In more detail, In step S10 various reporters register to report on specific events. The reporters select the events on which they wish to report from a list of events provided by the server. The selection process may consist of each reporter selecting event categories in a hierarchical manner in order to finally select a specific event. For example, a prospective reporter may be planning to attend a professional basketball game, involving the Los Angeles Lakers on the evening of June 9th. In order to select the specific game on June 9th the reporter may initially be presented with a choice regarding the type of event he would like to report on, for example: sporting, political, local, religious, or professional event. In the current example, the reporter would choose to report on a sporting event . Subsequently, the reporter is presented with the choice of type of sporting event. After the reporter chooses basketball another choice may be required to determine a specific team or location from which the reporter desires to report on. Continuing with the example, the reporter would choose the Los Angeles Lakers. Finally, the reporter will be presented with a list of specific games that the Los Angeles Lakers will be playing. The reporter selects the specific game on June 9th to report on. In addition to events listed in the event hierarchy on the server, it is also contemplated that reporters may add their own events that are not already on the event list. In other words, it is contemplated that a reporter may add an event to the event list stored on the server, and subsequently register to report on the event. For example, a prospective reporter may wish to provide real-time reports on a High School football game, which the school's former football players may be interested in receiving. The server will likely not have the game listed in the event list. According to the present invention, it is contemplated that the reporter may create a new event on the server for the high school football game and subsequently register to report on the event. In addition, spontaneous events, such as riots, disasters, or breaking news may be added to the event list by a reporter to enable immediate reporting of the spontaneous event.

After selecting a specific event, the reporter may then enter more specific event characteristics such as a coverage description, reporting language, time zone of event, start date and time, end date and time, and approximate number of reports expected to be submitted during the event. After the reporter enters the event characteristics, the reporter clicks on a submit button to complete the event registration. If the registration process was successful, the reporter will receive a confirmation message and the reporter is now able to submit reports regarding the registered event . In step S20, network users subscribe to receive reports submitted by specific reporters regarding specific events. User's may communicate with the server through any type of network, including, among others, an internet communication network, a wireless network in direct communication with the server, or a local area network. A wireless network may communicate directly with its' subscriber's (e.g. cell phone, PDA, or wireless modem users) and with the server, such that communications are not transmitted over the internet. A user becomes a subscriber by registering with the server (i.e. becoming a registered user) and selecting an event to subscribe to. Once a user is a registered user, he then goes through the same event hierarchy described above with reference to step S10 in order to select a specific event on which to receive reports. With regard to the above example, an interested user would select the June 9th Lakers game. Once the specific event has been selected, the subscriber will be presented with a list of reporters that are registered to report on the event . A specific event may have numerous reporters who each plan to report on the event. For example, there may be 200 people that are registered to report on the June 9th Lakers game. The list of registered reporters includes individual reporter identities, coverage description, reporting language, time zone of event, start date and time, end date and time, and approximate number of reports expected to be submitted during the event, all as entered by the reporter. The registered user then selects at least one reporter from which to receive reports. After submitting the choice of reporter, the registered user becomes a subscriber to the event . In step S30 the registered reporters submit reports to the server regarding the scheduled event. In the example above, each of the 200 reporters registered to report on the June 9^th Lakers game will submit reports throughout the event. Each report is transmitted to the server and in step S40 the server receives the reports from the registered reporters. The transmission method and medium may vary according to the particular reporter. For example, FIG. 1A illustrates a reporter transmitting from a computer 1 hardwired 4 to a communication network ("network") 7. The network 7 may be any type of network know in the art, including, among other, an internet network, a wireless network, and a local area network. FIG. IB illustrates another reporter transmitting from a personal digital assistant ("PDA") 3 connected to an internet communication network ("internet") 9 and FIG. 1C illustrates yet another reporter transmitting a report from a cell phone via a wireless connection to a wireless communication network 8.

In step S40, the server receives a specific report via a network 7 connection. In step S50, the server 6 immediately searches for subscribers to the specific event and reporter from which the report was received. The search may be accomplished by any method of database searching known in the art. After a list of subscribers is found, in step S60 the server immediately transmits the report to each subscriber found in the search. Each report is sent to the respective subscribers in the method and format specified by the respective subscribers in the registration process. Messages are disseminated through any type of network 7 known in the art . For example, one subscriber may desire to have reports sent to his cell phone as text messages not longer than 100 characters. Another subscriber may desire to have the same report sent in short messaging service ("SMS") format, which includes digital text in a packet limited size. Yet Another subscriber may desire to have the same report sent to his e-mail account, which he will receive on an electronic device configured to receive e-mail.

In a first embodiment, a report submitted by a desktop computer connected to the server via a network is instantaneously transmitted to multiple wireless communication devices in contact with the network. FIG 1A illustrates multiple subscribers receiving a report sent to their respective cell phones 2 and PDA's 3. The report in FIG 1A is submitted by a reporter using a computer 1 connected to server 6 via a wired 4 connection to network 7. The wireless connection 5 between each subscriber's respective wireless device and the server 6, via network 7, allows the subscriber's to receive the report at any location within the subscriber's respective cell phone 2 or PDA 3 coverage area. In a second embodiment, a report submitted by a wireless communication device to server 6, via a wireless connection with internet communication network ("internet") 9, is instantaneously transmitted to multiple wireless communication devices. FIG. IB illustrates multiple cell-phone 2 and PDA 3 subscribers receiving a report sent to server 6 from a PDA 3 via a wireless connection 5 to internet 9. In other words, the reporter of FIG. IB has submitted the report to server 6 via a wireless connection to internet 9 using a Personal Digital Assistant (PDA) 3, such as a Palm Pilot VII, and the subscribers receive the report from server 6 via a wireless connection to internet 9.

In a third embodiment, a report submitted by a cell phone 2 to server 6, via a wireless connection 5 to wireless communication network 8, is instantaneously transmitted from server 6 to multiple cell phone 2 subscriber's, via a wireless connection 5. FIG. 1C illustrates a cell phone user submitting a report to server 6 through a wireless connection 5 to wireless communication network 8. Server 6, after determining which cell phone 2 users have subscribed to the reporter, immediately transmits the report to subscriber cell phones 2 via wireless communication network 8. In other words, the network 7 of FIG. 3 does not include an internet 9 network, but instead, communications with server 6 occur via direct communications with wireless communication network 8. While three embodiments of the present invention have been discussed in detail, with respect to Figures 1A - 1C, it is contemplated that any combination of devices, wireless or wired to the network, may be used to implement the present invention. In other words, it is contemplated that any network compatible communication device may be used to submit reports, and any network compatible communication device may be used to receive reports. In addition, it is contemplated that any type of network is usable for communications between the server and communication devices. A network, according to the present invention, may include any combination of the following types of networks: wireless communication networks, the internet, wireless internet, local area networks (LANs) , wireless LANs, metropolitan area networks (MANs) , wireless MANs, wide area networks (WANs) , wireless WANs, and any other network know in the art.

If a reporter desires to submit another report regarding the same event, the procedure returns to step S30 and continues to step S60 where the new report is transmitted to the subscribers. FIG. 2 is a flow diagram describing the method of registering a user as a reporter for a specific event. In step S110 a list of events is presented to the user in a graphical user interface (GUI) created by the server. FIG. 6 illustrates such a GUI in the form of a HOME PAGE 10 that allows the user to select a general event category. As shown in HOME PAGE 10, a user has the following choices of general event categories: disasters and conflicts, sports 11, politics and law 12, business 13, entertainment 14, paranormal 15, science and technology 16, or top news 17. It is also contemplated that additional general event categories may be listed on a HOME PAGE 10. When a general event category is selected the user is presented with a TOP LEVEL TOPIC 20 listing which corresponds with the selected general event category. For example, if a user selects sports 11, an updated GUI will be produced that lists categories of sporting events. FIG. 7 illustrates a TOP LEVEL TOPIC 20 listing relating to a sports 11 general event category. In the example of

FIG. 7 the user is presented with choices in the sports 11 category including: auto racing, basketball, boxing, cycling, cricket, soccer 21, football, or golf. When a user selects a top level topic from the choices presented, the user is presented with a narrower SECOND LEVEL TOPIC 30 listing of event categories within the TOP LEVEL TOPIC 20 category. For example, if a user selects soccer 21 from the TOP LEVEL TOPIC 20 the server will respond by presenting a SECOND LEVEL TOPIC 30 GUI similar to the one illustrated in FIG. 8, which allows selection of specific soccer 21 events, such as Euro 2000 18, AFC, FIFA, CAF, UEFA, BLS, CONCACAF, or OFC. When a SECOND LEVEL TOPIC 30 is selected, the user is presented with an EVENT LEVEL 40 GUI, such as FIG. 9. The EVENT LEVEL 40 screen lists specific events on which the user may choose to report on. Continuing with the example above, if a user selects Euro 2000 18 from the SECOND LEVEL TOPIC 30 screen the user will be presented with an EVENT LEVEL 40 screen including specific event choices such as: Belgium v

Sweden, France v Denmark, Netherlands v Czech Republic, Germany v Romania, Portugal v England, and Spain v Norway.

Alternatively, a user may go directly from the HOME PAGE 10 to the EVENT LEVEL 40 by selecting a second level topic listed below one of the general event categories listed on the HOME PAGE 10. For example, under sports 11 there are two second level topics listed, namely Euro 2000 18 and Olympics 19. By clicking on one of these links a user will go directly to the EVENT LEVEL 40 GUI. For example, if the user selects Euro 2000 18 from FIG. 6 the user will be presented with specific Euro 2000 events, such as those listed in FIG. 9. In step S112, the user may suggest a new event to add to the EVENT LEVEL 40 event listing. If the user chooses to add an event, step S114 allows the user to add events to the EVENT LEVEL 40 list which are not already listed. FIG. 15 illustrates an ADD EVENT 100 interface for adding events to the list of events stored on the server. In one embodiment, the ADD EVENT 100 screen is only accessible by certain users, e.g. those users that have been registered for a long period of time. In another embodiment, all users are allowed to add events through the ADD EVENT 100 interface. The ADD EVENT 100 interface may query the user for information including: name of event, description, keywords, city, time zone, start date & time, and end date & time. This format is preferred because it allows entry of both scheduled events and non-scheduled spontaneous events. After the user completes the ADD EVENT 100 form, the information is submitted to the server. If the server accepts the newly added event, a confirmation message will be sent to the reporter and the event will be added to the servers event list in the appropriate category such that registered users may register as reporters or subscribers to the new event . Once a new event listing has been created, the user is return to step S110 which displays the EVENT LEVEL 40 list of events, which now includes the user added event .

In step S120, the user selects the specific event, which he desires to report on. The selection is made from the choices listed on the EVENT LEVEL 40 screen by clicking on the EVENT NAME 45, the REPORT ON THIS 44 icon, or any other hyperlink associated with the desired event.

Immediately after a user selects a specific event from FIG. 9, the server determines if the user is registered with the server in step S130. This determination may be accomplished by the user entering a username and password or by the server automatically recognizing the registration status of the user. If the server determines that the user is already registered with the server the flow continues to step S150. If the user is not registered with the server, step S140 allows the user to complete the user registration process. The user is presented with a NEW USER REGISTRATION screen, which may simply include selection of a username and password or may require more extensive biographical information about the user. For example, a server may query the user for biographical information including name, address, phone number, email address, and hobbies. This information may later be used to select advertising links that a user is likely to be interested in.

In step S150 the registered user enters event characteristics corresponding to the event selected in S120. FIG. 11 illustrates a REPORTER ASSIGNMENT 60 screen, in which the registered user enters information in order to complete registration to report on the selected event. The user first enters an ASSIGNMENT ID 61 which is a brief description of the reporting the user intends to provide. The ASSIGNMENT ID 61 will not be seen by other registered users, but is only used to identify the specific reporting assignment to the reporter at the time when a report is being submitted. Continuing with the above example, a reporter may enter an ASSIGNMENT ID 61 of "score updates", another reporter may enter an ASSIGNMENT ID 61 of "play-by-play reports" , and yet another reporter may enter an ASSIGNMENT ID 61 of "crowd reaction to the game." The ASSIGNMENT ID 61 will later appear on a list of events registered to the respective reporter to enable the reporter to easily identify the event for which he wishes to submit a report .

The reporter then enters a COVERAGE DESCRIPTION 62, which includes a short description that is viewable by potential subscribers to allow them to determine whether to subscribe for reports by specific reporters. For example, one reporter may enter a COVERAGE DESCRIPTION 62 such as "updates after every score by Belgium and a short summary of game immediately after its' conclusion" while another reporter may enter a

COVERAGE DESCRIPTION 62 such as "description of half- time show costumes." The COVERAGE DESCRIPTION 62 is helpful because it will inform potential subscribers of the type of reports each respective reporter will submit. The reporter then selects the REPORTING LANGUAGE

63 from a drop down menu. This option is available because events may occur at any location around the world. The drop down menu allows the user to select from a list of languages, and may also allow a reporter to enter his own REPORTING LANGUAGE 63.

Next, the reporter may specify a START DATE & TIME

64 and a STOP DATE & TIME 65. The start and stop times are selected with a series of pull-down menus. The START DATE & TIME 64 may be set to a default value equal to the date and time the selected event is scheduled to start. For example, If the Belgium v Sweden soccer game in the Euro 2000 is scheduled to occur on June 10^th at 20:46, the default START DATE & TIME 64 will be set to June 10^th at 20:46. In other words, the reporter does not ordinarily need to adjust the START DATE & TIME 64 unless the scheduled date and time is not the desired START DATE & TIME 64. The STOP DATE & TIME 65 may be set to a default scheduled stop date and time in a similar way as described above with respect to the START DATE & TIME 64.

Finally, the reporter may select an approximate MAXIMUM REPORTS PER DAY 66, which gives subscribes an idea of the number of reports to expect from the respective reporter. For example, a reporter that plans to give play-by-play reports of a soccer game may select a high number of MAXIMUM REPORTS PER DAY 66. If the reporter estimates sending a report every minute in a game that is expected to last 90 minutes, the reporter would select 90 as the MAXIMUM REPORTS PER DAY

66. Another reporter that will only be providing a post game summary would select 1 for the MAXIMUM REPORTS PER DAY 66. The MAXIMUM REPORTS PER DAY 66 allows potential subscribers to match their interest level in the event and capabilities in receiving reports with the number of expected reports each respective reporters plans to submit regarding the selected event.

After the information on the REPORTER ASSIGNMENT 60 screen of FIG. 11 has been completed the reporter presses the SUBMIT 67 button. If the REPORTER ASSIGNMENT 60 form has been completed properly the report is sent to the server, and in step S160 the server enters the reporter information in a reporter database. The server may also send the reporter a confirmation screen. If the form has not been completed correctly, an error screen is received and the reporter is returned to the REPORTER ASSIGNMENT 60 screen. After the reporter has successfully registered for an event the reporter is able to submit reports relating to the event. In the preferred embodiment, a reporter registers for a specific event at a time sufficiently before an event (perhaps several days) to allow other users to view the reporter's event characteristics (as discussed above) and decide whether or not to subscribe to the reporter's reports. When the reporter is ready to submit reports (typically during or near the time of the event) the report is submitted as outlined in FIG. 3.

FIG 3. is a flow diagram describing the method of submitting a report by a registered reporter. The method begins in step S200 when the HOME PAGE 10 is displayed to the reporter. HOME PAGE 10, in addition to listing broad event type .as discussed above, also provides links to SUBMIT REPORTS 80, MY SUMMARY 70, and Tutorial. In order to submit a report, the reporter clicks the SUBMIT REPORTS 80 button. Thus, in step S210 the server waits for the reporter to press the button. When the SUBMIT REPORTS 80 button is selected, step S220 displays to the reporter the SUBMIT REPORTS 80 screen of FIG. 13. The SUBMIT REPORTS 80 screen of FIG. 13 includes a DROP DOWN MENU 81, which includes events the reporter has previously registered to report on, a TEXT ENTRY FIELD 82, which allows the reporter to enter the text of the report, and a CHARACTER COUNT 83, which displays a running total of characters typed in the TEXT ENTRY FIELD 82. The DROP DOWN MENU 81 includes only the ASSIGNMENT ID'S 61 entered by the reporter when registering for the events. In other words, only those events that the reporter has registered for, as outlined in FIG. 2 above, are listed in the DROP DOWN MENU 81.

In step S230 the reporter selects the specific event in DROP DOWN MENU 81 which he currently wishes to submit a report for. In step S240, the report may then be entered in the TEXT ENTRY FIELD 82. The text entered in the TEXT ENTRY FIELD 82 is the report that will be sent to the subscribers of the specific event and reporter. In addition to the text reports, it is contemplated to allow reports in other or mixed media, such as image, sounds, video, and the like. For example, it is contemplated that a registered reporter may submit a sound clip from a concert or a video clip from a football game in place of, or in addition to, a text report. The CHARACTER COUNT 83 allows the reporter to monitor the length of the current report . Different report lengths are desirable for different reporting situations. For example, if a majority of subscribers to a particular report, will receive the report on cell phones which only accept text messages of less than 100 characters, the reporter may want to limit the number of characters to under 100. It is also contemplated that different report lengths, each corresponding to the same event, may be submitted in order to provide a maximum efficient report length to each subscriber, regardless of the subscriber's platform. For example, a reporter may enter a report of less than 100 characters that is to be sent to all cell phone subscribers, and, in addition, submit a report of several text pages to be sent to all e-mail subscribers. If the reporter wants to abandon the current report the reporter may click on the DONE 85 button, which will return the reporter to HOME PAGE 10. In step S250, the reporter submits the completed report to the server by clicking the SUBMIT 84 button. The report is sent to the server and is temporarily stored on the server pending a confirmation from the reporter. In step S270, the reporter is presented with a confirmation screen which displays the submitted report, as it will appear to subscribers, and a choice to confirm submission or return to report entry step S240. If the reporter desires to submit the displayed report to the server, and consequently to all subscribers to the report, the reporter clicks on the confirm submission button. Alternatively, the reporter clicks on the return to report entry button and is returned to the SUBMIT REPORTS 80 screen of FIG. 13. After a report submission has been confirmed, in step S280 the report is stored on the server and the reporter is returned to step S220 which displays the SUBMIT REPORTS 80 screen of FIG. 13. The reporter may immediately choose another registered event to report on, or alternatively, the reporter may choose to enter another report regarding the same event. .

Once the report is stored on the server in step S280, the report will be disseminated to the subscribers of the particular report . This process is discussed in detail with regards to FIG. 5 below. FIG. 4 is a flow diagram describing a method of subscribing to receive a report from a registered reporter. In step S300 the user (or potential subscriber) is shown a list of events, such as those shown in the EVENT LEVEL 40 GUI of FIG. 9 regarding specific Euro 2000 soccer games. The user arrived at the list of specific events by a hierarchical selection process as described above with respect to FIG. 2. In other words, the user begins at the HOME PAGE 10, which list general event categories. After a general event category is selected, a TOP LEVEL TOPIC 20 list is displayed, such as FIG. 7. Once a top level topic is selected, a SECOND LEVEL TOPIC 30, such as FIG. 8, is displayed. After a second level topic is selected, the EVENT LEVEL 40 GUI, such as FIG. 9, is displayed from which a user may select a specific event. The EVENT LEVEL 40 GUI also displays the EVENT TITLE 45, DATE & TIME 41, and CITY 42 corresponding to each event. To the left of each listed event is a REPORT ON THIS 44 icon and a SELECT/VIEW THIS 43 icon. If the user selects the REPORT ON THIS 44 icon the REPORTER ASSIGNMENT 60 screen will be displayed and the user will be able to register to report on the selected event as discussed above with reference to FIG. 2. If the user selects the SELECT/VIEW THIS 43 icon, the user will be able to subscribe to receive reports corresponding to the selected event. In step S320 a list of reporters registered to report on the selected event is displayed. FIG. 10 illustrates a REPORTER DESCRIPTION 50 screen showing an example list of • reporters registered to report on the Belgium v Sweden soccer game. Each respective reporter registered to report on the selected event is listed in REPORTER 56 column. Corresponding to each reporter there is a SELECTION CHECKBOX 57, a reporting language, a REPORTER RATINGS 55, a VOTE 58 link, a START DATE/TIME, and a number of SUBSCRIBERS 59 already subscribed to the respective reporter.

In step S322, the server monitors whether a VOTE 58 link has been selected. Selection of this link permits a user to record his opinion of a particular reporter. If the user has not selected VOTE 58 link the user will be allowed to select a report to subscribe to as described below in step S330. If the user selects VOTE 58 link, step S323 determines if the user is a registered system user and a registered subscriber to the corresponding reporter. If the user is not registered with the server, the user will be sent to a user registration screen that must be completed before returning to the REPORTER DESCRIPTION 50 screen of FIG. 10. If the user is a registered user, but has not subscribed to the respective reporter, the user is not allowed to vote on the respective reporter. In this case, step S323 sends the user to step S330 where the user may select a reporter to subscribe to.

If the user is both a registered user with the server and a subscriber to the respective reporter, the user (subscriber) may rate the respective reporter.

In step S324, the subscriber is allowed to rate the subjective quality of the respective reporter's reports. FIG. 14 illustrates an example of a REPORTER RATING 90 screen. At the top of REPORTER RATING 90 is listed the REPORTER NAME 56 which the subscriber is rating. In one embodiment, the rating of a reporter includes a one-star to five-star rating plus a textual • description of the reporter quality. The one-star to five-star rating is selected- by clicking on the RADIO BUTTON 91 next to the desired number of stars. For example, if the subscriber wants to give the best rating possible to a particular reporter, the subscriber would click on the RADIO BUTTON 91 next to the five-stars. If the subscriber wishes to include a textual rating, the subscriber may enter the textual rating in the DESCRIPTION ENTRY BOX 92. When the subscriber is completed with his rating of a reporter (i.e. has selected a RADIO BUTTON 91 and entered desired text) , the subscriber may submit the rating by clicking on the SUBMIT 93 button. After the SUBMIT 93 button has been pressed, the information from the REPORTER RATING 90 screen is sent to the server for processing. The server will add the one-star to five-star rating and the textual description to a database which includes other ratings for the respective reporter. The server may then average all one-star to five-star ratings and display an average RATINGS 55 on the REPORTER DESCRIPTION 50 screen. For example, if a respective reporter has receive 3 ratings of 5, 4, and 3, the RATINGS 55 on the REPORTER DESCRIPTION 50 screen would display a rating of 4 (i.e. the average rating = (5+4+3) /3). In other embodiments the reporter rating may be accomplished using a different rating scale, such as an A - F scale, a 0 -100 scale, or a 0-10 scale. In addition, RATINGS 55 may display a value, text, or icon representative of collected ratings instead of the average of all ratings. It is also contemplated that any other rating scale and method known in the art may be used to produce RATINGS 55.

From the subscribers perspective, The SUBSCRIBERS 59 column is another helpful indicator of the quality of reporting done by respective reporters. The value shown in the SUBSCRIBERS 59 column indicates the number of subscribers that have already subscribed to receive reports from the respective reporter for the selected event. For example, the first listed reporter in FIG. 10 has 16 subscribers already subscribed to receive reports regarding the Belgium v Sweden soccer game.

In addition, each reporter's COVERAGE DESCRIPTION 62 is displayed immediately below the listed reporter. As discussed above, the COVERAGE DESCRIPTION 62 may give the user more information on the type of reports the reporter plans to submit .

In step S330, a specific reporter is selected. By clicking the SELECTION CHECKBOX 57 corresponding to a specific reporter (i.e. to the left of the reporter name) , the specific reporter is preliminarily selected and a check mark is placed in the respective SELECTION CHECKBOX 57. A user may choose to subscribe to multiple reporters covering the same event by clicking on the SELECTION CHECKBOX 57 corresponding to multiple reporters. Alternatively, if the user wishes to subscribe to all reporters listed on the REPORTER DESCRIPTION 50 screen, the user may simply click on the SELECT ALL 51 button to select all reporters. When the SELECT ALL 51 button is selected a check mark is placed in the SELECTION CHECKBOX 57 next to all reporters. The user may also de-select all selected reporters by clicking on the CLEAR 52 button. In other words, clicking on the CLEAR 52 button removes check marks from every SELECTION CHECKBOX 57. When the user has placed check marks in the SELECTION CHECKBOX 57 corresponding to the reporters the user wishes to subscribe to, the user clicks on the SUBMIT 53 button to transmit the information to the server. In step S340 the server determines if the user is a registered user. If the user has not registered with the server, the user is taken to the NEW USER REGISTRATION screen and the user may register with the server as discussed above in step S140. Once the user has completed the user registration, the registered user is returned to step S340. After step S340 verifies that the user has registered with the server, the registered user's subscription information is transmitted to the server. In step S360 the user may select a delivery location or format or may want to have the reports sent to a default location in a default format. The default format and default location are selected in step S140 when the user registers with the server. For example, a user may enter a phone number for the default location and a wireless messaging format as the default format. The default location and format will be used unless alternatives are selected in step S360. Continuing with the prior example, the user may want the reports, from the reporter he is currently subscribing, to be delivered to his office e-mail account. In this case, the user would select 'e-mail' as the format and enter his e-mail address as the delivery location. This allows subscribers to receive reports at more than one location and in more than one format . It is also contemplated that the user may select different delivery locations and formats corresponding to different times during the day. For example, between 9AM and 5PM a user may want reports sent to his office e-mail account, but from 5PM to 9AM the user may want the reports sent to his cell phone. In step S360, the user may select any combination of special delivery options from those discussed above. In step S370 the server enters the subscription information into a subscriber database and in step S380 the subscription process is complete. The server may also send a confirmation note to the subscriber indicating the event and reporter subscribed to. The subscriber will now automatically receive all reports submitted by the selected reporter regarding the selected event.

FIG. 5 is a flow diagram describing the method of disseminating reports to subscribers. In step S400, at the time of the event, the reporter submits a report as discussed in FIG. 3 above. The report is temporarily stored on the server.

In step S405 the server searches the subscriber database to find all subscribers that have registered to receive reports from the specific reporter on the specific event. This searching may be done in any database searching method known in the art . For example, one database may create a subscriber list for each reporter registered event and attach each subscriber's delivery format and location information to the list. In this way, the server might simply access the attached list to find the subscribers. In another database, the database may query a subscriptions field within each users registration information, in search of the specific reporter and event from which a report was recently received. Regardless of the search method used, the server is provided with a list of subscribers, including each subscriber's respective delivery location and delivery format.

In step S410, the server transmits the submitted report to all subscribers in the list provided by the database search. The report is sent to each subscriber, via network 7, in the respective format and to the respective delivery location. For example, reporter John Smith has 1000 subscribers for his reports on the Belgium v Sweden soccer game on June 10 at 20:46. Immediately after the game begins, John submits his first report to the server according to the method described in FIG. 3. The database immediately searches the subscriber database and returns a list of 1000 subscribers to the server. 700 of the subscribers wish to receive the reports on their cell phones. The wireless messages are sent to each of the 700 phone numbers in the desired format (probably text of less than 100 characters) . Another 150 of the subscribers want to receive their messages on their PDA's. 100 (of the 150) want the full report, regardless of length, while the remaining 50 only want reports of less than 100 words. The report is sent to each PDA subscriber in the selected format. The remaining 150 subscribers want to have the report, including any graphics, sounds, or other attachments, delivered to an e-mail address. If the report contains any media or attachments, these 150 subscribers will receive the attachments in their report e-mail. According to this method, the server and database effectively disseminate the report to those that want the report and in the format they respectively want the report . In step S420, all subscribers receive the report.

With regard to the above example, it is contemplated that all 1000 subscribers will receive the report at substantially the same time. Because the processes of searching the database and transmitting the report are automated (i.e. are performed by high-speed computers), the report is disseminated to all subscribers immediately after the report is received.

In step S425 the server determines if the report is to be stored on the server for future access. In one embodiment the server may store all reports from the most popular reporters, e.g. those that have a rating above 4.5 and more than 100 subscribers, for access by future subscribers. For example, a user may want to subscribe to an event that happened early that day in order to read the stored analysis (reports) made by the most followed reporters. In another embodiment, the reporter may select whether or not to store the reports on the server. If the server is not to store the report, step S430 removes the report from the server. If the report is to be stored on the server, step S440 moves the report from temporary storage memory to permanent storage memory. Permanently stored reports may be accessed through interactive web browsing. FIG. 12 is a graphical user interface depicting a MY SUMMARY 70 user interface. The MY SUMMARY 70 screen lists the events a respective registered user has subscribed to and those events the user has registered to report on. Thus, the MY SUMMARY 70 screen is divided in two sections, as shown in the example of

FIG. 12. The SUBSCRIPTION SUMMARY 71 lists each EVENT NAME 45, REPORTER 56, reporting language, event date and COVERAGE DESCRIPTION 62. The SUBSCRIPTION SUMMARY 71 serves as a reminder of the events the user has subscribed to. Each listed subscription has a corresponding SELECTION CHECKBOX 57 that is used to unsubscribe to selected subscriptions. For example, in FIG. 12, the user is subscribed to receive reports from REPORTER 56 'Digitalplay' regarding the Italy v Sweden game on June 10, submitted in English, having a

COVERAGE DESCRIPTION 62 of 'Scores'. If the respective user wants to un-subscribe to the reports by Digitalplay, the user clicks the SELECTION CHECKBOX 57 next to the Digitalplay listing. When the SELECTION CHECKBOX 57 is clicked, a checkmark will be placed in the checkbox indicating that the particular subscription has been selected for removal. The user completes the subscription removal process by clicking on the REMOVE 73 button. When the REMOVE 73 button is selected the server will un-subscribe the user from all subscriptions in which their respective SELECTION CHECKBOX 57 has been checked. For example, if the user of the MY SUMMARY- 70 screen shown in FIG. 12 clicks on the REMOVE 73 button, the Italy v Sweden and France v Denmark events would be removed from the user's subscription list. If the user wishes to remove all subscriptions, the user may click the SELECT ALL 51 button, which places check marks in every SELECTION CHECKBOX 57, and subsequently click the REMOVE 73 button.

The REPORTER SUMMARY 72 lists all events the user is currently registered to report on. More specifically, the REPORTER SUMMARY 72 lists the EVENT NAME 45, reporting language, start date, number of SUBSCRIBERS 59, and COVERAGE DESCRIPTION 62 for each registered event. The REPORTER SUMMARY 72 serves as a reminder of the events the user has registered to report on. In addition, each event has a corresponding SELECTION CHECKBOX 57, which is used to remove registration from reporting assignments. The process is identical to that described above with reference to un-subscribing to subscriptions. In the example of FIG. 12, the user has selected the Italy v Sweden and France v Denmark events for registration removal. The process is completed by clicking on the REMOVE 73 button, wherein the reporter is no longer registered to report on the selected event (s). When a reporter removes a registration for an event, subscriptions to that particular event are automatically removed. For example, in FIG. 12 there are 10 users subscribed to receive this particular reporters reports regarding the Italy v Sweden event. When the reporter removes the registration from this event, the 10 subscribed users will be un-subscribed to the reports. When the user is done viewing the MY SUMMARY 70 screen the user may return to the HOME PAGE 10 by clicking on the DONE 74 button.

The invention has been described with respect to particular illustrative embodiments. It is to be understood that the invention is not limited to the above-described embodiments and that various changes and modifications may be made by those of ordinary skill in the art without departing from the spirit and scope of the invention.

Claims

WHAT IS CLAIMED IS:

1. Network implemented method for registering reporters to submit reports to a server on the network, the reports corresponding to an event, said method comprising the steps of: selecting an event to report, wherein said selection is made from a computer generated display of event identifiers received over the network from the server; submitting event characteristics for the selected event wherein the characteristics are submitted over the network.

2. A method according to Claim 1, wherein, the network is an internet communication network.

3. A method according to Claim 1, wherein, the network is a wireless communication network.

4. A method according to Claim 1, wherein, the network is a local area network.

5. A method according to Claim 1, wherein, the computer generated display of events includes events created by the reporter, wherein the created events are listed in the computer generated display of event identifiers.

6. A method according to Claim 5, wherein, events created by the reporter are spontaneous events.

7. A method according to Claim 1, wherein the event characteristics include at least one of: coverage description, reporting language, time zone, start date and time, end date and time, and maximum reports per day.

8. A method according to Claim 1, wherein the reporter receives confirmation of registration, wherein said confirmation is received through the network.

9. A method according to Claim 1, wherein the reporter receives a reminder message some time after registration for the event and before the event occurs .

10. Network implemented method for registering reporters to submit reports to a server on the network, the reports corresponding to an event, said method comprising the steps of: receiving a selection from reporter corresponding to an event selected from a computer generated list of event identifiers; wherein said list is placed on the server and said selection is received through a network connection; and receiving reporter characteristics for the reporter selected event wherein the characteristics are submitted over the network.

11. A method according to Claim 10, wherein, the network is an internet communication network.

12. A method according to Claim 10, wherein, the network is a wireless communication network.

13. A method according to Claim 10, wherein, the network is a local area network.

14. A method according to Claim 10, wherein the computer generated display of events includes reporter created events, wherein the created events are listed in the computer generated display of event

5 identifiers.

15. A method according to Claim 14, wherein, events created by the reporter are spontaneous events.

10 16. A method according to Claim 10, wherein the reporter characteristics relate to at least one of: coverage description, reporting language, time zone, start date and time, end date and time, and maximum reports per day.

15

17. A method according to Claim 10, wherein the server transmits confirmation of registration to the reporter, wherein said confirmation is transmitted through the network.

20

18. An network implemented method for submitting a report to a server on the network, comprising the steps of: selecting an event from a computer generated 25 list of event identifiers to which a reporter is registered; entering report information in a computer generated interface; and submitting the report to the server, wherein •30 the report is transmitted to the server through the network.

19. A method according to Claim 18, wherein, the network is an internet communication network.

35

20. A method according to Claim 18, wherein, the network is a wireless communication network.

21. A method according to Claim 18, wherein, the network is a local area network.

22. A method according to claim 18, wherein the report information may include one or more of the following media formats: text, still graphics, video, and audio.

23. A method according to Claim 18, wherein a confirmation report is received by the reporter to confirm the report has been received by the server.

24. A method according to Claim 18, further comprising the step of: transmitting the report information from the server to a plurality of network users, wherein the report transmissions occur immediately after receiving the report information from the registered reporter.

25. An network implemented method for a server on the network receiving a report from a reporter comprising the steps of: receiving an event selection from a registered reporter; providing a computer generated interface for the reporter to enter the report; and receiving the submission of the report through the network from the registered reporter, wherein the report is stored on the server.

26. A method according to Claim 25, wherein, the network is an internet communication network.

27. A method according to Claim 25, wherein, the network is a wireless communication network.

28. A method according to Claim 25, wherein, the network is a local area network.

29. A method according to Claim 25, wherein the report information may include one or more of the following media formats: text, still graphics, video, and audio.

30. A method according to Claim 25, wherein, a confirmation report is transmitted from the server to the reporter to confirm the report has been received by the server.

31. A method according to Claim 25, further comprising the step of: transmitting the report information from the server to a plurality of network users, wherein the report transmissions occur immediately after receiving the report information from the registered reporter.

32. An network implemented method for receiving reports regarding a selected event comprising the steps of : selecting an event from a computer generated list of events; selecting a reporter from a computer generated list of reporters; wherein the selections are transmitted to a server over a network connection; receiving a report from the server, wherein the report corresponds to the selected event and the selected reporter, wherein the report is received by the server after selection of the event and selection of the reporter, and wherein the report is received from the server substantially immediately after receipt by the server.

33. A method according to Claim 32, wherein, the network is an internet communication network.

34. A method according to Claim 32, wherein, the network is a wireless communication network.

35. A method according to Claim 32, wherein, the network is a local area network.

36. A method according to Claim 32, further comprising the steps of: selecting a desired format for the report; and selecting a desired location for the report to be transmitted.

37. A method according to Claim 36, wherein the desired format may be one or more of the following: ascii, ansi, rtf, html, Java, mpeg, asf, wav, mp3 , jpeg, gif, bmp, tif.

38. A method according to Claim 36, wherein the desired transmission location may be one or more of the following: telephone number, e-mail address, IP address, or network address.

39. An network implemented method for transmitting reports regarding a selected event comprising the steps of: receiving an event selection from a computer generated list of events; receiving a reporter selection from a computer generated list of reporters; wherein the selections are received by a server over a network connection; transmitting a report from the server, wherein the report corresponds to the selected event and the selected reporter, wherein the report is received by the server after receipt of the event selection and reporter selection, and wherein the report is transmitted from the server substantially immediately after receipt by the server.

40. A method according to -Claim 39, wherein, the network is an internet communication network.

41. A method according to Claim 39, wherein, the network is a wireless communication network.

42. A method according to Claim 39, wherein, the network is a local area network.

43. A method according to Claim 39, further comprising the step of: receiving a desired report format selection; receiving a desired transmission location selection.

44. A method according to Claim 43, wherein the desired format may be one or more of the following: ascii, ansi, rtf, html, Java, mpeg, asf, wav, mp3 , jpeg, gif, bmp, tif.

45. A method according to Claim 43, wherein the desired transmission location may be one or more of the following: telephone number, e-mail address, IP address, or network address.

46. An network implemented method for disseminating a report submitted to a server on the network by a registered reporter comprising the steps of: receiving at a server a report submitted by a registered reporter corresponding to a specific event; searching server database to determine which subscribers have subscribed to receive reports from said registered reporter corresponding to said specific event; transmitting the report to all subscribers found in the searching, wherein the report is immediately disseminated to the subscribers found in the searching via a network.

47. A method according to Claim 46, wherein, the network is an internet communication network.

48. A method according to Claim 46, wherein, the network is a wireless communication network.

49. A method according to Claim 46, wherein, the network is a local area network.

50. A method according to Claim 46, wherein transmission of each respective report, is done according to a transmission location and transmission format selected by each respective subscriber.

51. A method according to Claim 46, further comprising the step of: submitting a rating criteria in response to a received report, wherein the rating is selected by a subscriber in reference to the subscribers perceived quality level of a received report, wherein the submission is transmitted to the server over the network.

52. An apparatus for registering reporters to submit reports to a server on corresponding to an event, submitting a report to a server, disseminating a submitted report to subscribers, and receiving reports, comprising: a program memory for storing process steps executable to perform a method according to any of Claims 1 to 51; and a processor for executing the process steps stored in said program memory.

53. Computer-executable process steps stored on a computer readable medium, said computer-executable process steps for registering reporters to submit reports to a server corresponding to an event, submitting a report to a server, disseminating a submitted report to subscribers, and receiving reports, wherein said computer-executable process steps executable to perform a method according to any of Claims 1 to 51.

54. A computer-readable medium which stores computer-executable process steps, the computer- executable process steps for registering reporters to submit reports to a server corresponding to an event, submitting a report to a server, disseminating a submitted report to subscribers, and receiving reports, wherein said computer executable process steps comprising process steps executable to perform a method according to any of Claims 1 to 51.