Event notification and organization utilizing a communication network

Abstract

A user of a telecommunications or other computing device may notify his or her contacts of an event of interest, which event may be modified by the user's contacts without requiring the permission of the originating user to do so. In this regard, an event organizing service receives an event notification request from a user of a telecommunications device (e.g., a mobile telephone), automatically identifies the user's contacts to whom the event notification is to be published, and publishes the event notification to the automatically identified contacts. A contact who receives the event notification may update the event, e.g., by modifying data describing the event, without the permission of the originating user. Accordingly, a contact who has received the event notification may modify the event (e.g., change the date/time, change the location, etc.) and the event organizing service may publish a notification for the updated event to the originating user and his or her contacts informing them of the modification. It will be appreciated that as updates to the event are made by the user's contacts (and in some cases the user herself), the event is ultimately organized by the user's social network or community without requiring the user to organize the details of or manage the event herself.

Description

BACKGROUND

Generally described, telecommunications devices and communication networks facilitate the collection and exchange of information. Utilizing a communication network and relevant communication protocols, a telecommunications device can engage in audio and/or data communications with telecommunications devices, such as voice calls, video calls, text messages (e.g., SMS), multimedia messages (e.g., MIMS), content streaming, instant messaging, Web surfing, and the like.

To facilitate communications, telecommunications devices can be associated with software and hardware components that allow the telecommunications device to maintain contact information, such as telephone numbers, email addresses, messaging addresses, etc., maintain personal information, such as task lists, calendars, etc. and send messages utilizing the contact information via available communication channels.

Given the prevalence of telecommunications devices in an increasingly mobile society, many users utilize their telecommunications devices to organize events and notify their contacts of these events and their locations. However, such events are typically organized and managed directly by a user who has been granted “organizer rights” and who thus controls the salient details of the event, e.g., location, date/time, etc. Accordingly, changes to the event can only be made with permission of the organizer (or his or her delegate(s)). This places an administrative burden on a user, who, for example, may be interested in a certain event, but not interested in fully organizing the event. Moreover, such rigid event organization does not lend itself to social network environments in which users are accustomed to communicating and interacting on a group or community basis.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of the present disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of a telecommunications environment in which a user of a telecommunications device may notify his or her contacts of an event of interest to the user, which event may be modified by the user's contacts without the user's permission;

FIG. 2 is a block diagram illustrative of components of a telecommunications device for use in requesting notification of the event of interest and/or receiving notification of the event of interest;

FIG. 3 is a block diagram of the telecommunications environment of FIG. 1 depicting an illustrative embodiment for notifying a user's contacts of an event of interest to the user;

FIG. 4 is a flow diagram of an illustrative method of generating an event notification for publication to the user's contacts;

FIG. 5 is an illustrative user interface generated on a telecommunications device for enabling a user to request an event notification;

FIG. 6 is an illustrative user interface generated on a telecommunications device for displaying data describing the event of interest and enabling a contact who has received the event notification to update the event without the permission of the originating user;

FIG. 7 is a block diagram of the telecommunications environment of FIG. 1 depicting an illustrative embodiment for notifying the originating user and other contacts of the updated event;

FIG. 8 is a flow diagram of an illustrative method for generating an updated event notification for publication to the originating user and other contacts;

FIG. 9 is an illustrative user interface generated on a telecommunications device for displaying data describing the updated event;

FIG. 10 is an illustrative user interface generated on a telecommunications device for displaying an event history for the event of interest that reflects the updates made to the event; and

FIG. 11 is an illustrative user interface generated on a telecommunications device for displaying location and arrival data for the originating user and his or her contacts with respect to the event of interest.

DETAILED DESCRIPTION

Generally described, aspects of the present disclosure relate to notifying a user's contacts of an event of interest and enabling the user's contacts to update the event without requiring the permission of the originating user to do so. In this regard, an event organizing service is described in one embodiment that receives an event notification request from a user of a telecommunications device (e.g., a mobile telephone), automatically identifies the user's contacts to whom the event notification is to be published, and publishes the event notification to the automatically identified contacts. In accordance with yet other aspects of the present disclosure, a contact who receives the event notification may update the event, e.g., by modifying data describing the event, without the permission of the originating user. In this regard, the originating user and contacts to whom the event notification is published are not granted “organizer rights,” as are granted in typical calendar or event planning applications where data describing a scheduled event (e.g., date/time, location, etc.) can only be changed by the user who scheduled the event (e.g., the organizer) or one of the organizer's delegates. Accordingly, in one embodiment, a contact who has received the event notification may modify the event (e.g., change the date/time, change the location, etc.) and the event organizing service may publish a notification for the updated event to the originating user and his or her contacts informing them of the modification. It will be appreciated that as updates to the event are made by the user's contacts (and in some cases the user herself), the event is ultimately organized by the user's social network or community without requiring the user to organize the details of or manage the event herself.

Although aspects of the present disclosure will be described with regard to an illustrative telecommunications environment and component interactions, telecommunications protocols, flow diagrams and user interfaces, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting. Specifically, although the term telecommunications device is used in this document, the term represents any type of device having a component for communicating with one or more other devices via one or more communication paths. Such communication paths can include wireless communication paths (via infra-red, RF, optical, terrestrial, or satellite communication media) and wired communication paths.

With reference now to FIG. 1, a block diagram illustrative of a telecommunications environment 100 in which a user of a telecommunications device may notify his or her contacts of an event of interest to the user (which event may be modified by the user's contacts without the user's permission) will be described. A contact may correspond to an individual person, an identifier associated with a person such as a telephone number, a group of people, an identifier associated with a group of people, and the like. The telecommunications environment 100 can include an event organizing service 102. As described above, the event organizing service 102 may receive an event notification request from a user utilizing a telecommunications or other computing device, automatically identify the user's contacts to whom the event notification is to be published, and publish the event notification to the automatically identified contacts. In one embodiment, event records including data describing each event (e.g., an event descriptor, date/time, location, message, etc.) for which a notification is to be or has been published are stored in an event record data store 110 accessible by the event organizing service 102. An event record may include any data describing the event obtained from the originating user or her contacts, as well as any location or other supplemental data obtained by the event organizing service 102 from other sources, such as network data sources 120. Such network data sources may include web sites, location based services, social network services, telecommunications services, message publication services, etc. While the event record data store 110 is depicted in FIG. 1 as being local to the event organizing service 102, those skilled in the art will appreciate that the event record data store 110 may be remote to the event organizing service 102 and/or may be a network based service itself.

While the event organizing service 102 is depicted in FIG. 1 as implemented by a single computing device in the telecommunications environment 100, this is illustrative only. The event organizing service 102 may be embodied in a plurality of computing devices, each executing an instance of the event organizing service. A server or other computing device implementing the event organizing service 102 may include memory, processing unit(s), and computer readable medium drive(s), all of which may communicate with one another by way of a communication bus. The network interface may provide connectivity over the network 118 and/or other networks or computer systems. The processing unit(s) may communicate to and from memory containing program instructions that the processing unit(s) executes in order to operate the event organizing service 102. The memory generally includes RAM, ROM, and/or other persistent and auxiliary memory.

As illustrated in FIG. 1, the event organizing service 102 can include an external data source interface component 104 for obtaining external information from network data sources 120, such as location data for the event, the originating user, or the user's identified contacts and other supplemental data for the event (e.g., an image of the event location; a map to the event location; reviews for the event or event location; recommendations for related events, services, products, activities, and other locations; etc.). The event organizing service 102 can also include a device interface component 106 for obtaining device information from the telecommunications or other computing devices associated with the user or the user's identified contacts (e.g., location data for the user's telecommunications device, an IP address for a contact's home computing device, etc.). The event organizing service 102 can further include an event organizing component 108 for processing the obtained data, as well as the requests for event notification and event updates so as to facilitate organization of an event by the user and his or her contacts without granting organizer rights.

One skilled in the relevant art will appreciate that the event organizing service 102 may correspond to a number of computer devices, such as server computing devices. Additionally, the external data source interface component 104, device interface component 106, and event organizing component 108 may be implemented in a single computing device or across multiple computing devices. One skilled in the relevant art will also appreciate that the event organizing service 102 may include any one of a number of additional hardware and software components that would be utilized in the illustrative computerized network environment to carry out the illustrative functions of the service 102 and/or any of the individually identified components.

With continued reference to FIG. 1, the telecommunications environment 100 can include a number of telecommunications devices 112a, 112b or other computing devices 122, each associated with a user. As will be described in more detail below, a user may request an event notification from the event organizing service 102 or submit an event modification to the event organizing service 102 using a telecommunications device 112a, 112b or other computing device 122. In an illustrative embodiment, the computing devices 122 can include various hardware and/or software components, such as a browser software application or another software application, for requesting or receiving event notifications. The telecommunications devices 112a, 112b and other computing devices 122 can correspond to a wide variety of devices or components that are capable of initiating, receiving or facilitating communications over a communication network including, but not limited to, personal computing devices, electronic book readers (e.g., e-book readers), hand held computing devices, integrated components for inclusion in computing devices, home electronics, appliances, vehicles, machinery, landline telephones, VoIP telephones, cordless telephones, cellular telephones, smart phones, modems, personal digital assistants, laptop computers, gaming devices, media players, and the like. In an illustrative embodiment, the telecommunications devices 112a, 112b include a wide variety of software and hardware components for establishing communications over one or more communication networks, including cellular telecommunications network 114, a wired telecommunications network (not shown) and/or an IP-based telecommunications network (not shown). Illustrative components of a telecommunications device 112a, 112b will be described in greater detail with regard to FIG. 2. Although the present disclosure references a telecommunications device 112a, 112b, one skilled in the relevant art will appreciate that a telecommunications device may correspond to, or otherwise be referred to, as a mobile communication device, a wireless computing device, or a computing device. Accordingly, reference to a telecommunications device 112a, 112b or computing device 120 should not be interpreted as limiting to any particular functionality or operation.

In an illustrative embodiment, the telecommunications environment 100 can include a number of additional components, systems and/or subsystems for facilitating communications with the telecommunications devices 112a, 112b and/or the event organizing service 102. The additional components can include one or more switches or switching centers 116 (in GSM embodiments, Mobile Switching Centers or MSCs) for establishing communications with the telecommunications devices 112a, 112b via the telecommunications network 114, such as a cellular radio access network, an IP-based telecommunications network based on the family of IEEE 802.11 technical standards (“WiFi”) or IEEE 802.16 standards (“WiMax”), a converged wireless telecommunications network such as Unlicensed Mobile Access (UMA) or General Access Network (GAN), and other wired and wireless networks. The operation of telecommunications networks, such as telecommunications network 114 are well known and will not be described in greater detail. As illustrated in FIG. 1, the switching center 116 includes interfaces for establishing various communications via a communication network 118, such as the Internet, intranets, private networks and point to point networks, generally referred to as the “network.” Although the telecommunications network 114 is illustrated as a single communication network, one skilled in the relevant art will appreciate that the communication network can be made up of any number of public or private communication networks and/or network connections.

As noted above, the telecommunications environment 100 can further include one or more network data sources 120 for providing external information to the event organizing service 102. The network data sources 120 may include a number of computing devices for obtaining and processing requests for information from either the event organizing service 102 and/or the telecommunications devices 112a, 112b.

With reference now to FIG. 2, illustrative components of a telecommunications device, such as telecommunications device 112a, for use in requesting a notification for an event of interest or submitting a modification to the event of interest will be described. The telecommunications device 112a may include one or more processing units 202, such as one or more CPUs. The telecommunications device 112a may also include system memory 204, which may correspond to any combination of volatile and/or non-volatile storage mechanisms. The system memory 204 may store information which provides an operating system component 206, various program components 208, program data 210, an event organizing component 222 and/or other components. As will be explained in greater detail below, the event organizing component 222 stored in system memory of the telecommunications device 112a may perform all or some of the functions described above in connection with the event organizing component 108 of the event organizing service 102. The above-enumerated list of components is representative and is not exhaustive of the types of functions performed, or components implemented, by the telecommunications device 112a. One skilled in the relevant art will appreciate that additional or alternative components may also be included in the telecommunications device 112a to carry out other intended functions such as a mobile telephone functions.

The telecommunications device 112a performs functions by using the processing unit(s) 202 to execute instructions provided by the system memory 204. The telecommunications device 112a may also include one or more input devices 212 (keyboard, mouse device, specialized selection keys, etc.) and one or more output devices 214 (displays, printers, audio output mechanisms, etc.). Illustrative user interfaces for a telecommunications device 112a will be described with regard to FIGS. 5, 6 and 9-11, described below.

With continued reference to FIG. 2, the telecommunications device 112a may also include one or more types of removable storage 216 and one or more types of non-removable storage 218. Still further, the telecommunications device 112a can include communication components 220 for facilitating communication via wired and wireless communication networks, such as the telecommunications network 114 and network 118 (FIG. 1). Examples of various communication protocols include, but are not limited to, Bluetooth, the family of IEEE 802.11 technical standards (“WiFi”), the IEEE 802.16 standards (“WiMax), short message service (“SMS”), voice over IP (“VoIP”) as well as various generation cellular air interface protocols (including, but not limited to, air interface protocols based on CDMA, TDMA, GSM, WCDMA, CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA and similar technologies).

FIG. 3 is a block diagram of the interaction between various components of the telecommunications environment 100 when user A of telecommunications device 112a requests to publish a notification to his or her contacts of an event of interest to user A. For purposes of the example, however, the illustration has been simplified such that many of the components utilized to facilitate communications are not shown (e.g., telecommunications network 114, switching centers 116, etc.). One skilled in the relevant art will appreciate that such components can be utilized and that additional interactions would accordingly occur without departing from the spirit and scope of the present disclosure.

As depicted in FIG. 3, user A creates an event notification request using her telecommunications device 112a for an event of interest to user A. For example, user A may be interested in having lunch with her friends at a local restaurant, and thus, creates an event notification request in order to notify her friends of the lunch event. As will be described in more detail below, the event notification request created by user A may include data that describes the event, e.g., an event descriptor, date/time, location, message, etc. Such data may be entered directly by user A utilizing the telecommunications device 112a and/or obtained by the event organizing component 222 of the telecommunications device 112a. In some embodiments, user A will also directly enter his or her contacts to whom the requested event notification is to be published. However, in other embodiments the event organizing component 222 of the telecommunications device 112a and/or the event organizing component 108 of the event organizing service 102 automatically identifies the contacts to whom the requested event notification is to be published, as will be described in more detail below. Accordingly, user A need not spend additional time or effort directly entering his or her contacts or adding contacts from an address book or other contact manager component.

The telecommunications device 112a transmits the event notification request to the event organizing service 102 via the network 118. The event organizing service 102 then generates an event record including the data describing the event and stores the event record in the event record data store 110. As noted above, the event organizing service 102 may automatically identify the contacts to whom the requested notification is to be published. In such cases, the event organizing service 102 includes the contact information (e.g., name, electronic mail address, mobile telephone number, etc.) for the automatically identified contacts (or perhaps pointers to such contact information) in the stored event record. In some embodiments, the event organizing service 102 obtains location and other supplemental data and includes such data in the event record as well. For example, the event organizing service 102 may obtain location data for the event (e.g., a street address and map for the event), location data for user A (e.g., GPS data for the telecommunications device 112a associated with user A), or location data for one or more of user A's identified contacts (e.g., GPS data for the telecommunications device 112b associated with user B, an IP address for a computing device 122 associated with user C, etc.). Other supplemental data may include, but not be limited to, an image of the event location; a map of the event location; reviews for the event or event location; recommendations for related events, services, products, activities, and other locations; etc.

Once the event record is generated, the event organizing service 102 may publish a notification for the event of interest to user A's contacts. In one embodiment, user A's contacts are automatically identified as noted above. Accordingly, in the illustrated example, the event notification is published by the event organizing service 102 to telecommunications device 112b associated with user B and computing device 122 associated with user C. Although reference is made herein to a telecommunications or other computing device associated with a user, those skilled in the art will recognize the device is any device utilized by the user to send and receive communication using an electronic mail account, mobile telephone account by virtue of a mobile telephone number, email address, etc. Accordingly, the device need not be a dedicated device or the same device.

The event notification may be sent via the network 118 as an electronic mail message, a SMS or MMS message, an electronic message that is published or posted for viewing by others (sometimes known as a “micro-blog” post, “twitter” message or “tweet”), a user interface generated on the display of the computing device 122/telecommunications device 112 (e.g., via a pop-up window, web page, tool bar message, etc.), a voice message, etc. In some embodiments, the type of notification published depends on the contact information stored in the event record for the automatically identified contacts. In other embodiments, the originating user (e.g., user A in the illustrated example) indicates the type of notification to be published to certain contacts and/or mode of communication in the event notification request. For example, in the case of user B's telecommunications device 112b, a notification is published to the telecommunications device 112b in the form of a SMS message since the contact information for user B included a mobile telephone number. In another example, the contact information for user B may also include an email address for user B. Accordingly, the notification may be published to an email account associated user B's email address and accessed by user B via the telecommunications device 112b or another telecommunications or computing device associated with user B. In some embodiments, the notification itself includes the data describing the event. However, in other embodiments the notification (e.g., the SMS message or electronic mail message), includes a Uniform Resource Identifier (URI) (or a shortened alias for redirection of a long URI) that identifies a network resource (e.g., a web page) that can be accessed to obtain the data describing the event. Accordingly, the contact to whom the notification has been published may utilize the URI to retrieve and view the event data using his or her telecommunications or other computing device and initiate generation of the event user interface on his or her telecommunication or other computing device for displaying such information. Those skilled in the art will recognize that the event user interface may be generated for display (directly or indirectly) by the event coordination service 102 and/or the event coordination component 222 of the telecommunications or other computing device.

FIG. 4 is a flow diagram of an illustrative method 400 implemented by the event organizing service 102 to generate an event notification upon receipt of a request from a user. The routine begins in block 402 and proceeds to block 404 where the event organizing service 102 receives an event notification request from a user. As described in more detail below the request may include, but not be limited to, an event descriptor, date/time, location, message, etc. as supplied by the user via a user interface (such as user interface 500 shown in FIG. 5) that is generated on the display of the user's telecommunications or other computing device. Next, in block 406, the event organizing service 102 identifies contacts of the user to whom the requested event notification is to be published. In one embodiment, all or some of the contacts are included by the user in the request itself. In other embodiments, the contacts are automatically identified by the event organizing service 102 without requiring entry by, or direction from, the user. For example, the event organizing service 102 may identify and obtain contact information for a user's contacts from an address book or other contact manager component maintained on the user's telecommunications or other computing device, maintained by the event organizing service 102 or maintained by or at another network data source 120, such as a telecommunications service, a social network service or a message publication service. In addition, the contacts automatically identified by the event organizing service 102 may include only a subset of the user's contacts. A subset of contacts may correspond to a portion of the user's contacts which are accessible via the user's telecommunications or other computing device. In one illustrative embodiment, the subset of contacts is selected by the user and an indication of such can be subsequently maintained, for example, in data store 224 of the user's telecommunications device or by the event organizing service 102, for future automatic identification of the contacts to whom an event notification is to be published on behalf of the user.

In another embodiment, a portion of the subset of contacts can be selected by the user of a telecommunications or other computing device, while a remaining portion of the subset of contacts are selected automatically based on one or more other factors. In one example, the factor can be a frequency of communication between user A and one or more user contacts accessible by the telecommunications device 112a. In this example, the event organizing component 222 (or another component of the telecommunications device 112a, such a contact management component (not shown)) monitors communications between the user and each of user A's contacts accessible by the telecommunications device 112a and maintains data associated with the monitored communications. Based on the monitored communications and corresponding maintained data, a frequency of communication may be determined between user A and each of user A's contacts. This information can then be used to determine the remaining portion of the subset of contacts. In one illustrative embodiment, the remaining portion of the subset of contacts can be selected based on the contacts that have been in communication with user A the most number of times. In other embodiments, the types of communications may be monitored between the user and the user's contacts, such as SMS messages, MIMS messages, emails, instant messages, voice calls, and the like, and then the remaining portion of the subset of contacts may be selected based on the frequency of one type of communication or an aggregation of some or all types of communications. In addition, if aggregated, one type of communication can be weighted over other types. Even further, in other embodiments, only those communications initiated by the user may be monitored to select the remaining portion of the subset of contacts based on the user's frequency of initiating communication with each of the user's contacts.

Additionally or alternatively, in a further embodiment, a subset of user contacts can be associated with a special rate plan offered by a telecommunications carrier providing communication services to the telecommunications device 112a. Specifically, user A may be provided a special rate associated with any communications made between user A and any of the contacts identified in the subset. In addition to a special rate, the rate plan may have a variety of other parameters that may affect selection of the contacts to be included in the subset. For example, in one embodiment, the subset of contacts may be limited in number to correspond to a number of contacts with whom communications will be provided at a special rate. As another example, the subset of contacts may be editable only after a specified period of time has elapsed from initial selection (whether by the user or partially by automated selection based on other factors such as frequency of communication information).

Accordingly, when the user submits an event notification request to the event organizing service 102, the event organizing service may automatically identify a subset of contacts to whom the event notification is to be published without requiring the user herself to identify the subset to whom the event notification is to be published. In some embodiments, the automatically identified subset of contacts will be presented to the user for confirmation and/or editing. However, in other embodiments, it will be assumed that no such confirmation is necessary since the automatically identified subset of contacts may be relied upon as the most likely contacts with whom the user would wish to organize an event or as the most likely contacts to be interested in the event.

Referring again to FIG. 4, once the contacts are identified in block 406, the event organizing service 102 may obtain location data for inclusion in the event record in block 408. The location data may be for the event itself (e.g., street address, map, etc.), the originating user (e.g., GPS coordinates for the user obtained from a GPS component included in the user's telecommunications device or obtained using a location based service), or one or more of the user's identified contacts (e.g., GPS coordinates, IP address, etc. of the telecommunications or other computing devices associated with the contacts). As will be described in more detail below, such location data may be used to augment the event notifications published by the event organizing service 102. Accordingly, the user is not required to include all or portion of such data in the request for event notification nor in an event modification.

In other embodiments, location data may be applied as a filter to the automatically identified contacts so as to select only those contacts to whom the event may be of possible interest. For example, by applying the location data as a filter, the event organizing service 102 may publish an event notification to only those identified contacts currently within or predicted to be within a certain distance or estimated arrival time of the event. In other embodiments, rather than filter the identified contacts by location to obtain a further subset to whom to publish the notification, the event organizing service 102 may include the location data for the user's contacts in the event record for further access by the user. Accordingly, the user may access and view the data (e.g., via a user interface displayed on the user's telecommunications or other computing device) to determine where her contacts are located and thus, gauge whether and/or when her contacts will attend the event.

Next, in block 410, the event organizing service 102 may obtain other supplemental data for the event from other sources, such as network data sources 120 for inclusion in the event record. Such supplemental data may include, but not be limited to, an image of the event location; a map to the event location; reviews for the event or event location; recommendations for related events, services, products, activities, and other locations; weather data related to the event; etc. In some embodiments, the user may indicate in the event notification request that she is interested in such supplemental data (e.g., by checking a box for including a map or recommendations, by indicating such in a set of user preferences maintained in the data store 224 of the user's telecommunications device or by the event organizing service 102, etc.).

In block 412, the event organizing service 102 generates an event record corresponding to the request for event notification that includes, for example, an event descriptor, date/time, location, message, etc. as supplied by the user, as well as the contact information, location data and other supplemental data obtained in blocks 406, 408 and 410. The event organizing service 102 stores then stores the event record in the event record data store 110.

Once the event record is generated, the event organizing service 102 publishes a notification of the event described in the event record to the user's identified contacts in block 414. As noted above, such a notification may be published as an electronic mail message, a SMS or MMS message, an electronic message that is published or posted for viewing by others, a user interface display, etc. In some embodiments, the type of notification published depends on the contact information stored in the event record for the automatically identified contacts or on a mode of communication preference. As also noted above, the notification (e.g., the SMS message or electronic mail message) may include a URI that identifies a network resource (e.g., a web page) that can be accessed to obtain the data from the event record that describes the event. Accordingly, the contact to whom the notification has been published may utilize the URI to retrieve and view the event data via a user interface generated on his or her telecommunications or other computing device such as the user interfaces depicted in FIGS. 6 and 9-11. Upon publication of the event notification, the method 400 ends in block 416.

FIG. 5 is an illustrative user interface 500 generated on a telecommunications device, such as user A's telecommunications device 112a, for enabling a user to request an event notification. For example, user A may be interested in having lunch with her friends at a local restaurant. Thus, user A creates an event notification request 501 in order to notify her friends of the lunch event via user interface 500 generated by the event organizing service 102 and displayed on user A's telecommunications device (e.g., a mobile telephone). Accordingly, user A enters a descriptor 502 for the event (e.g., “Lunch at Jack's Café”) and a date 512 and time 504 for the event. In other embodiments the date/time fields may be automatically completed with the current date/time, which may indicate that the event is occurring immediately.

In addition, user A may enter location data for the event, such as a location name 514, street 516, city 518, state 520 and zip code 508. The user may also include a map for the location by selecting a map checkbox 506. Alternatively, the user may indicate that her current location is the location for the event by selecting a location checkbox 522. As noted above, the event organizing service 102 may obtain current location data for the user A utilizing GPS, a location based service, etc. In addition, if the user has included a location name 514 for the event, but not a street address, the event organizing service 102 may obtain location data for the event, e.g., from a network yellow/white pages data source 120, from a combination of the same with the user's identified location, from prior event records associated with the user, etc.

User A may further enter a message 524 (e.g., “Let's meet for lunch at Jack's Café in a ½ hour”) for the event notification request, which message may be included in the event notification published to user A's identified contacts. User A's contacts may be added directly by the user upon selection of an add contacts checkbox 528 (which in turn, may cause further user interfaces to be generated and displayed on the telecommunications device 112a for entry of the contacts or transfer of the contacts from an address book or other contact manager component). Alternatively, user A may select a “my contacts” checkbox 526 to indicate that the event organizing service 102 automatically identify the user's contacts and publish the event notification the user's contacts. When user A has completed the event notification request 501, user A may submit the request to the event organizing service 102 upon selection of a submit control 510.

As described above, upon receipt of the event notification request, the event organizing service 102 identifies user A's contacts and generates an event record including data describing the event. The data may include the descriptor, date/time, location, message and contact information entered by user A, as well as any contact information, location data or other supplemental data the event organizing service 102 obtains. The event organizing service 102 then publishes an event notification to user A's identified contacts. As mentioned above, the event notification may include a URI that may be utilized to retrieve and view the event record data via a user interface such as user interface 600 depicted in FIG. 6.

As shown in FIG. 6, user B has received a published event notification for “Lunch at Jack's Café.” Accordingly, user interface 600 includes the data found in the corresponding event record, such as a descriptor 610 for the event (i.e., “Lunch at Jack's Café”), location data 602, a map 612, a date 614, a time 606 and a message 616. User B may forward the event notification “as is” to his own contacts (see reference number 620) and/or add it to his calendar by selecting an add to calendar control 622. However, user B may instead choose to modify the event data. Since user A does not keep organizer rights to the event, user B (as well as user A's other identified contacts) may modify the event data stored in the corresponding event record without user A's permission or authorization. Accordingly, in one embodiment, user B may modify the event (e.g., change the date/time, change the location, etc.) and the event organizing service may publish a notification for the updated event to user A and user A's other identified contacts informing them of the modification. It will be appreciated that as updates to the event are made by user A's contacts (and in some cases user A herself), the event is ultimately organized by user A's social network or community without requiring user A to organize the details of or manage the event herself.

In the illustrated example, user B may select an edit control 604 to modify the descriptor 610 or location data 602 for the event, and an edit control 618 to modify the message 616. In addition, user B may modify the date 614 and time 606 of the event. Upon completion of the modification, user B may submit the event modifications to the event organizing service 102 upon selection of a submit control 608. Those skilled in the art will appreciate that user interface 600 may include, and the user may modify, other or different data than that depicted in FIG. 6 without departing from the spirit and scope of the present disclosure. However, those skilled in the art will appreciate from the foregoing description that user B need not obtain permission from user A to directly modify any data, particularly the descriptor, date/time and location data; nor must user B propose such a modification to user A for user A's acceptance before such modifications are made. Rather, upon receipt of the event modification from user B, the event organizing service 102 updates the corresponding event record with the modification and publishes an updated event notification to user A and the other identified contacts as will be described in more detail below.

FIG. 7 is a block diagram of the interaction between various components of the telecommunications environment 100 when user B of telecommunications device 112b submits an event modification to the event organizing service 102. As depicted in FIG. 7, when user B submits an event modification, it is transmitted to the event organizing service 102 via the network 118. The event organizing service 102 then updates the corresponding event record to include the data modified by user B and stores the updated event record in the event record data store 110. Because the event record has been updated, the event organizing service 102 publishes an updated event notification. Accordingly, the event organizing service 102 may identify the contacts to whom the updated event notification is to be published. In some embodiments, the event organizing service 102 simply identifies the same contacts as those to whom the prior event notification was published (i.e., user A's contacts in the illustrated example), which contacts are already identified in the event record. However, in other embodiments, user B's contacts (which may be different than user A's) are also identified by the event organizing service 102 and published the updated event notification. In such cases, the event organizing service 102 adds the contact information (e.g., name, electronic mail address, mobile telephone number, etc.) for user B's identified contacts (or perhaps pointers to such contact information) in the updated event record. In some embodiments, the event organizing service 102 obtains further location and supplemental data and includes such data in the updated event record as well. For example, the event organizing service 102 may obtain new location data for the event if user B modifies the location, or updated location data for the contacts to whom the updated event notification is to be published.

Once the event record is updated, the event organizing service 102 may publish an updated notification for the event to contacts identified in the updated even record (which contacts may include the originating user (user A), user A's contacts and any additional contacts of user B. Accordingly, in the illustrated example, the updated event notification is published by the event organizing service 102 to telecommunications device 112a associated with user A and computing device 122 associated with user C. Such a notification may be sent via the network 118 as an electronic mail message, a SMS or MMS message, etc.

FIG. 8 is a flow diagram of an illustrative method 800 implemented by the event organizing service 102 to update an event upon receipt of an event modification. The routine begins in block 802 and proceeds to block 804 where the event organizing service 102 receives an event modification from a contact. As described in more detail below the request may include, but not be limited to, modifications to an event descriptor, date/time, location, message, etc. of an event regarding which the contact was previously notified (see FIG. 6). Next, in block 806, the event organizing service 102 identifies contacts to whom the updated event notification is to be published. In one embodiment, the contacts are automatically identified by the event organizing service 102 without requiring entry by, or direction from, the contact submitting the modification. For example, at least a portion of the contacts may be identified from the corresponding event record.

Once the contacts are identified in block 806, the event organizing service 102 may update the event record with the event modification submitted by the contact, as well as any additional contact, location or other supplemental data it may obtain. As noted above, location data may be applied as a filter to the identified contacts so as to select only those contacts to whom the event may still be of possible interest. For example, by applying the location data as a filter, the event organizing service 102 may publish an updated event notification to only those identified contacts currently within or predicted to be within a certain physical distance or estimated arrival time of the event. Accordingly, if a contact has moved beyond such a distance or arrival time, the event organizing service 102 may not publish the updated event notification to the contact.

Next, in block 810, the event organizing service 102 publishes an updated notification of the event as described in the updated event record to the identified contacts. As noted above, such a notification may be published as an electronic mail message, a SMS or MMS message, an electronic message that is published or posted for viewing by others, a user interface display, etc. As noted above, the updated event notification (e.g., the SMS message or electronic mail message) may include a URI that identifies a network resource (e.g., a web page) that can be accessed to obtain the data from the updated event record that describes the event. Accordingly, the URI may be utilized to retrieve and view the event data using his or her telecommunications or other computing device via a user interface such as user interface 900 depicted in FIG. 9.

As shown in FIG. 9, user A has received an updated event notification for “Lunch at Jack's Café” indicating that the event has been changed. Accordingly, user interface 900 includes the data found in the corresponding updated event record, such as a descriptor 912 for the event (i.e., “Lunch at Jack's Café”), location data 902, a map 914, a date 916, a time 906 and a message 918. As can be seen from FIG. 9, the location data 902 and message 918 have been modified since the prior event notification. More specifically, the event location has been modified from Jack's Café at 123 Main Street, Anywhere, Calif. 12345 to Mo's Diner at 987 First Ave, Anywhere, CA 12345, and the corresponding message has been modified to read “Jack's Café isn't vegan, so let's go to Mo's Diner around the corner.” However, the date/time of the event remain the same. In the illustrated example, user A may add the event notification to her calendar by selecting an add to calendar control 922, get a history for the event by selecting a get event history control 908 (as will be described in more detail below), get an estimated time of arrival to the event for user A and/or user A's contacts by selecting a get ETA control 924 (as will be also described in more detail below) or modify the updated event data. Since no user has organizer rights to the event, user A (as well as any other contacts who received the updated event notification) may further modify the event data stored in the corresponding event record without permission or authorization. In this manner, contacts may continue to modify the event (e.g., change the date/time, change the location, etc.) and the event organizing service 102 may continue to publish notifications to the contacts' telecommunications or other computing devices as the event is updated. In one embodiment, the modifications are made to the event record in the chronological order in which they are received by the event organizing service. However, in other embodiments, certain modifications may be given priority over others depending on the identity of the contact submitting the modification, date/time of the event, importance of the event, etc. It will be appreciated that as modifications to the event are made, the event is ultimately organized by a social network or community of contacts without requiring any particular contact to organize the details of or manage the event herself.

As noted above, user A may select a get event history control 908 to obtain a history of modifications to an event made by his or her contacts. If selected, a user interface such as user interface 1000 depicted in FIG. 10 may be generated by the event organizing service 102 and displayed on user A's telecommunications device 112a. As illustrated, user interface 1000 includes an event history 1002 for the event “Lunch at Jack's Café.” Accordingly, the event history 1002 includes an entry 1012 for the original event notification, which was created at 11:45 AM on Mar. 9, 2009 by user A. The next entry 1010 in the event history (in chronological order) is for the event modification made by user B (described above) at 11:50 AM on the same date changing the location of the event “Lunch at Jack's Café” to Mo's Diner and modifying the message to read “Jack's Café isn't vegan, so let's go to Mo's Diner around the corner.”

However, as can be seen from the next entry 1008 in the event history 1002, user C further modified the event at 11:54 AM to change the date of the event to Mar. 10, 2009 and indicate via the message that “I can't make it today. Let's do it tomorrow.” But as evidenced by the next entry 1107, user A (who requested the original event notification), changed the date back to Mar. 9, 2009 and changed the message to read “Sorry, I can only do lunch today.” As shown in the next entry 1006 to the event history 1002, user C again submits a modification to the event organizing service 102, but this time merely modifies the message to state that “Mo's doesn't serve pizza.” However, user C does not change the date/time or location of the event. Rather, user B submits a modification of the event to the event organizing service 102 changing the location to Melanie's Vegan Pizza Palace and the message to “So let's go to Melanie's Vegan Pizza Palace” as is reflected in entry 1004 to the event history 1002. In the illustrated example, the modifications were made to the event record for this event in the chronological order in which they were received by the event organizing service 102. Accordingly, user A was able to change the date of the event back to Mar. 9, 2009 after user C submitted his modification changing the date to Mar. 10, 2009. However, in other embodiments, certain modifications may be given priority over others depending on the identity of the contact submitting the modification, date/time of the event, importance of the event, etc. Accordingly, in such an embodiment, if user C is identified as, for example, a key or primary contact, user C's modification is given priority and thus, user C's proposed date prevails. In yet another embodiment, a voting scheme may be implemented to resolve conflicting modifications and assign priority to the prevailing modification. Consequently, in such an embodiment, user C's modification to the date may trigger a voting option to be displayed to all of the identified contacts. Each contact is then enabled to vote for the date he or she prefers and the date with the most votes prevails. Those skilled in the art will appreciate from FIG. 10 how the event service 102 enables a group of users to publicize and organize an event dynamically, without requiring any particular contact to have organizer rights for the event or manage the event directly.

In yet another embodiment, user A (or any other contact to whom an event notification has been sent) may select a get ETA control 924 (FIG. 9) to obtain estimated arrival times for herself and/or the contacts to whom the event notification(s) were published. If selected, a user interface such as user interface 1100 depicted in FIG. 11 may be generated by the event organizing service 102 and displayed on user A's telecommunications device 112a. As illustrated, user interface 1100 includes estimated arrival times (ETAs) for the identified contacts for the event “Lunch at Jack's Café.” Such ETAs may be obtained by the event organizing service 102 from a network data source 120 such as a location based service, or may be determined by the organizing service 102 from location data obtained from a network data source 120 or from the telecommunications or other computing devices associated with each of the contacts. Accordingly, the ETA 1110 for user A in the user interface 1100 is one minute, the ETA 1112 for user B is nine minutes and the ETA for user C indicates that user C is “out of range” and thus, his or her ETA cannot be determined. (This would be consistent with the event history 1002 in which user C indicated he could not make the event.) In addition to the ETAs for the contacts who have been published the event notification(s), user interface 1100 may further include a map 1106 in which a geographic position of each such contact with respect to the even is represented by an icon for the contact. Accordingly, user A (who is estimated to arrive at the event location indicated by a star shape in one minute) is represented on the map with an icon 1116, while user B is represented on the map with an icon 1104. User C who is “out of range” is represented on the map 1106 with an icon 1108 which is displayed outside of the boundaries of the map. In some embodiments, user interface 1100 is dynamically updated so that the ETA data and positions of the icons representing the contacts change in real time as the contacts near (or perhaps travel away from) the event location. Those skilled in the art will recognize that the map 1106 may be any type of map to which the event organizing service 102 may have access and that is suitable for depicting the event location. Accordingly, the map 1106 may be a street map, satellite map, a contour map, etc., displayed at any scale or level of detail appropriate for depicting the positions of the contacts relative to the event location. In addition, the scale or level of detail may change as the relative positions of the contacts change.

Those skilled in the art will also recognize that the user interface 1100 depicted in FIG. 11, as well as the user interfaces depicted in FIGS. 5, 6 and 9-10, are illustrative and thus, may contain more, less or different data, controls, etc. than that depicted without departing from the spirit and scope of the present disclosure. In addition, the user interfaces displayed on a telecommunications device 112a, 112b may be the same as or different from those displayed on a computing device 122. For example, due to mobile phone memory constraints, bandwidth constraints, limited screen size, and/or input interfaces (e.g., touch screen, keyboard, etc.), the user interface generated on the device may vary.

All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.

Conditional language such as, among others, “can,” “could,” “might” or “may,” unless specifically stated otherwise, are otherwise understood within the context as used in general to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Any process descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or elements in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown, or discussed, including substantially concurrently or in reverse order, depending on the functionality involved as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims

1. A system for notifying contacts of events, the system comprising: a data store that stores event records, each event record describing an event; anda computing device in communication with the data store, the computing device operative to: obtain an event request from a mobile computing device, the event request including data describing an event of interest to a user of the mobile device and of possible interest to contacts of the user;without requiring action by the user, automatically identify contacts of the user to whom a notification of the event is to be published, wherein at least one of the contacts is automatically identified based at least in part on a frequency of communication with the user;generate an event record based on the event request obtained from the mobile computing device, the event record including the data describing the event of interest;receive a modification to the data describing the event of interest from at least one of the automatically identified contacts, wherein the at least one of the automatically identified contacts has not been granted organizer rights for the event;modify the data describing the event of interest in response to the modification without permission from anyone who has been granted organizer rights;store the event record in the data store; andpublish a notification of the event described in the event record to a plurality of computing devices, each computing device associated with each of the automatically identified contacts of the user.

2. The system of claim 1, wherein the computing device is further operative to obtain location data for the event.

3. The system of claim 2, wherein the location data for the event is based upon a location of at least one of the event, the user and a contact of the user.

4. The system of claim 1, wherein the computing device is further operative to obtain and store supplemental data in the event record.

5. The system of claim 1, wherein the notification of the event is published as at least one of an electronic message, a voice message or a user interface display.

6. The system of claim 1, wherein the computing device automatically identifies the contacts of the user to whom a notification of the event is to be published from a set of contacts.

7. The system of claim 1, wherein the contacts of the user are automatically identified further based at least in part on at least one of a type of the event, a location of the event, time of the event, input of the user, location of the user, and location of at least one contact.

8. The system of claim 1, wherein the contacts are obtained from at least one of the mobile device of the user, the computing device in communication with the data store, and another computing device.

9. A method for notifying a user's contacts of an event of interest to the user, the method comprising: as implemented by one or more computing devices configured with specific executable instructions, without requiring action by the user, automatically identifying the user's contacts to be notified of the event, wherein at least one of the contacts is automatically identified based at least in part on a frequency of communication with the user;generating an event record including data describing the event of interest, which data is freely modified without an organizer's authorization and by request from at least one automatically identified contact to whom organizer rights for the event of interest have not been granted; andpublishing an event notification for the event described in the event record to a plurality of computing devices, each of the computing devices associated with an automatically identified contact.

10. The method of claim 9 further comprising obtaining location data for the event.

11. The method of claim 10, wherein the location data is based on at least one of a location of the event, a location of the user and a location of the contact of the user.

12. The method of claim 10 further comprising estimating a time of arrival to the event for the user based on the location data.

13. The method of claim 10 further comprising estimating a time of arrival to the event for at least one of the automatically identified contacts to whom the event notification was published based on the location data.

14. The method of claim 10, wherein the location data is used to automatically identify the user's contacts to be notified of the event.

15. The method of claim 9, wherein the event notification comprises at least one of a descriptor of the event, location of the event, time of the event, message regarding the event and contact information for the event.

16. The method of claim 9, wherein the user's contacts are automatically identified from a set of contacts maintained by at least one of a telecommunication service, a social network service and a message publication service.

17. The method of claim 9, wherein the user's contacts are automatically identified further based at least in part on at least one of a type of the event, location of the event, time of the event, input of the user, location of the user, and location of at least one contact.

18. A system for notifying contacts of an event of possible interest, the system comprising: a data store that stores event records, each event record describing an event; anda computing device in communication with the data store, the computing device operative to: automatically identify contacts to whom a notification of an event of possible interest to the contacts is to be provided, wherein at least one of the contacts is automatically identified based at least in part on a frequency of communication with a user of the computing device;generate an event record including data describing the event of possible interest;receive a modification to the data describing the event of interest from at least one automatically identified contact who has received the notification but who has not been provided organizer rights for the event;modify the data describing the event of interest in response to the modification without action by anyone who has been provided organizer rights for the event; andpublish a notification of the event described in the event record to at least one computing device, the at least one computing device associated with an automatically identified contact.

19. The system of claim 18, wherein the computing device is further operative to obtain data describing the event of possible interest from at least one originating computing device.

20. The system of claim 19, wherein the originating computing device is a mobile computing device.

21. The system of claim 18, wherein the computing device is further operative to automatically obtain location data for the event.

22. The system of claim 21, wherein the location data for the event is based upon a location of at least one of the event, a location of the originating computing device and a location of the at least one computing device to which the notification is published.

23. The system of claim 22, wherein the computing device is further operative to generate an estimate of a time of arrival to the event based on the location data.

24. The system of claim 18, wherein the computing device is further operative to store supplemental data in the event record.

25. The system of claim 18, wherein the notification of the event is published as at least one of an electronic message, a voice message or a user interface display.

26. The system of claim 18, wherein the contacts of the user are automatically identified further based at least in part on at least one of a type of the event, location of the event, time of the event, location of the originating device, and location of the at least one computing device to which the notification is published.

27. A non-transitory computer-readable medium having a computer-executable component for publishing to contacts of a user, a notification of an event of interest the user, the computer-executable component comprising: an event organizing component operative to: without requiring input from the user, automatically identify contacts to whom the notification of the event of interest to the user is to be published, wherein at least one of the contacts is automatically identified based at least in part on a frequency of communication with the user;generate an event record including data describing the event of interest, which data is modifiable by the automatically identified contacts who have received the notification of the event of interest, wherein the data is modifiable without granting organizer rights for the event to the user or the automatically identified contacts; andpublish a notification of the event described in the event record to a plurality of computing devices, each computing device associated with an automatically identified contact.

28. The non-transitory computer-readable medium of claim 27, wherein the event organizing component is further operative to obtain data describing the event of possible interest from a computing device associated with the user.

29. The non-transitory computer-readable medium of claim 28, wherein the computing device associated with the user is a mobile computing device.

30. The non-transitory computer-readable medium of claim 27, wherein the event organizing component is further operative to obtain location data for at least one of the event, the user and at least one automatically identified contact.

31. The non-transitory computer-readable medium of claim 30, wherein the event organizing component is further operative to automatically identify contacts to whom the notification of the event of interest to the user is to be published further based at least in part on the location data.

32. The non-transitory computer-readable medium of claim 27, wherein the event organizing component is further operative to generate an estimate of a time of arrival to the event based on the location data.

33. The non-transitory computer-readable medium of claim 27, wherein the notification of the event is published as at least one of an electronic message, a voice message or a user interface display.

34. The non-transitory computer-readable medium of claim 27, wherein the event record includes at least one of a descriptor of the event, location of the event, time of the event, and message regarding the event.

35. The non-transitory computer-readable medium of claim 27, wherein the notification of the event includes a locator to a resource from which a computing device associated with an automatically identified contact may retrieve data describing the event of interest.