Collecting implicit information for determining context of event actions

Technique for collecting implicit information used to determine the context of an event action

<u style="single">Technical field of invention</u>

The present invention is generally related to mobile communication technologies and, more specifically, to techniques for determining implicit contextual material for shared media content associated with an event.

<u style="single">Cross-reference to related applications</u>

The present patent application claims priority to U.S. Patent Application Serial No. 11/670,400, the entire disclosure of which is incorporated herein by reference.

<u style="single">Technical background of the invention</u>

Many of the great changes that affect our daily lives have occurred in the Internet. For example, online social networking has become a new gathering place. In the United States, they are known as the new power luncheon for business events and new golf courses. Furthermore, many people use this online social network to get in touch or keep in touch with friends, neighbors, and the community.

The development of such online social networks has invisibly affected our daily lives; they provide instant contact to people with similar ideas and enable us to partner with more people in more ways.

The daily life of the online social networking technology is based on the inclusion of social gatherings in a less organized and impromptu way. For example, people can almost immediately decide online to gather at a restaurant or club. meeting. Some social gatherings that some members of the social network are aware of may be unknown to other members, and will not be notified until the social event is ongoing or ready to proceed.

Once involved in such events, one may wish to aggregate and share the various media content associated with the event. Sharing media content on mobile devices has become quite popular and has changed our daily lives. Users can send and receive media content from a variety of different mobile devices. However, managing this type of shared media content by multiple people can sometimes be difficult and quite confusing. Accordingly, the present invention has been made in view of such considerations.

<u style="single">Summary of the invention</u>

The present invention discloses a server device for managing mobile communications, comprising: a transceiver for transmitting and receiving data through a network; and a processor operable to perform the following actions, the actions comprising: generating a group associated with a spontaneous event, wherein the spontaneous event comprises a party composed of people; receiving a membership for the spontaneous event, wherein each member is associated with a mobile device; receiving at least the spontaneous event a text message or a media content message; in the spontaneous event, distributing the at least one text message or the media content message to each member's mobile device, and further publishing at least the media content message to a website associated with the spontaneous event; A start time associated with the spontaneous event and an end time are determined based on the action of receiving the at least one text message or the media content message.

<u style="single">Brief description of the schema</u>

Unrestricted and non-exhaustive embodiments of the invention are described with reference to the following drawings. In the drawings, the same component numbers indicate the same components unless otherwise indicated.

For a better understanding of the invention, reference should be made to the detailed description 1 is a system diagram showing an embodiment of an environment in which the present invention can be implemented; FIG. 2 is a diagram showing an embodiment of a mobile device included in a system in which the present invention can be implemented; FIG. 3 is shown to be implemented in a A network device embodiment in a system of the present invention; FIG. 4 is a logic flow diagram generally showing an embodiment of a program for generating an event for sharing media content; FIG. 5 is another A logic flow diagram generally showing an embodiment of a program for determining implicit information associated with an event based in part on shared media content; Figure 6 illustrates an embodiment of a usage condition for generating an event; Figure 7 illustrates an embodiment of the use of shared media content for the event in accordance with the present invention.

<u style="single">Detailed description of the preferred embodiment</u>

The invention will now be described with reference to the drawings which form a part of the invention, which The drawings show specific embodiments for carrying out the invention. However, the present invention may be embodied in a variety of different forms and should not be construed as being limited to the embodiments set forth herein. Instead, these embodiments are presented to provide a complete and complete description of the invention, and The skilled artisan fully conveys the concepts of the present invention. The invention may be embodied as a method or apparatus. Thus, the invention can be embodied as a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware facing embodiments. Therefore, the following detailed description should not be considered as limiting.

In the following description of the invention and the scope of the patent application, The meaning of the following terms is expressly stated unless it is clearly indicated otherwise in the context. As used herein, the term "in an embodiment" does not necessarily denote the same embodiment, although it may be so. Moreover, as used herein, the phrase "in another embodiment" does not necessarily mean a different embodiment, although it may be so. Therefore, various embodiments of the invention may be combined, without departing from the scope or spirit of the invention.

Moreover, as used herein, the so-called "or" is an "including" and is intended to mean the term "and / or" unless the context clearly indicates otherwise. The term "subscription" is not unique and is allowed to be based on other unexplained factors, unless the context clearly indicates otherwise. In addition, in the description of the invention, "a", "an"," The meaning of "in" includes "in" and "on".

As used herein, the terms "social network" and "community" refer to the personal network of a personal friend, family member, colleague, and can use such a network. Subsequent connectivity to identify more relevant connections for multiple different activities, including but not limited to appointments, job search links, service recommendations, content sharing, people with similar ideas, activity partners, and more. Such social networks can be generated according to a variety of different criteria, including social events such as a party, party event, and the like.

As used herein, the term "event" refers to any social gathering in which people are composed and have a start time and an end time. In an embodiment, the start and/or end times may be established sporadically, ie they may be performed informally, for example, based on informal gatherings of people. In another embodiment, the event has an established start and/or end time. Again, in an embodiment, the event can have multiple start/end times, such as with a regular scheduled meeting, and the like.

As used herein, the term "spontaneous event" means an event resulting from an instantaneous impulse, or a similar impromptu action, rather than an already planned event. Thus, a spontaneous event may have an informally announced start time, or a start time within a short period of time from the announcement of the event. This is not like a planned event with a defined start time that occurs hours or even days after the invitation of the potential participant of the event to send the event. Furthermore, many planned events may include a predetermined end time. Typically, planned events are published with a notice including a scheduled start and/or end time. However, because a spontaneous event may have a ambiguity or undefined start and/or end time, at least one of the times may not even be provided. For example, a spontaneous event may allow a number of people to agree to meet at about 5 pm to have a small drink, but there is no formal planning. The meeting is held until one of the potential participants makes a suggestion on that day. Thus, although this example exhibits a fuzzy (about) start time, it may not have a predetermined end time. Another example of a spontaneous event may be when a person sends a message to another person, suggesting that they meet at a party or other event that is happening or about to happen. In this example, the start time is again blurred, such as "Let's get together at that party tonight." As such, this example also demonstrates that the end time is typically not announced for the spontaneous event. However, a spontaneous event can also occur in a planned event. For example, a person can 'gather' in a planned event and 'start' a spontaneous event in the planned event.

As used herein, the term "media content" means any digital material relating to the user of the computing device, including but not limited to: audio data, multimedia material, photos, video data, still images, text, graphics, animation files, voice. Messages, text messages, and more.

The invention, which is briefly described, is directed to a spontaneous event determination start and/or an end time. The present invention enables one to generate an online membership for the spontaneous event and to share media content messages and/or other types of messages among the members in the spontaneous event. In an embodiment, the media content and/or other messages may be automatically posted to a website where the members may subsequently annotate the spontaneous event.

The present invention enables a mobile device user to generate a group that includes one or more members of the spontaneous event. The user can then send an invitation or other message to the member. In this spontaneous event, members can share media content messages and/or text messages with other members. In an embodiment, it may be partially rooted The start time and/or end time of the spontaneous event is automatically determined based on the media content and/or text message traffic between the members. In an embodiment, the start time may be based on when the group was generated, and then modified when the traffic rate of the media content and/or message exceeds a threshold. However, other criteria can also be used to determine the start time, including, for example, when the media content message was first shared. In another embodiment, the start time can also be determined by searching for the content of the text message for the time information. In an embodiment, the end time is based on a flow rate of shared messages between the members being lower than another threshold. For example, in one embodiment, if the message rate being shared indicates that the message has not been shared between members for a predetermined period of time, the end time may be indicated using the last time the message was shared. In another embodiment, the end time may be determined based on the traffic rate of the message being shared being less than the number of messages per time unit, and the like. The location of the spontaneous event may also be determined based on the physical location of the member's mobile device in the event. Moreover, in an embodiment, other information indicating whether the member of the group participates in the event may also be determined by sending media content or other messages to other members of the group in the spontaneous event.

<u style="single">Display work environment</u>

Figure 1 shows, in a system diagram, an environmental embodiment in which the present invention can be implemented. Not all of the components are required to implement the invention, and variations in the configuration and type of such components may be made without departing from the spirit or scope of the invention. As shown, the system 100 of Figure 1 includes an area Network ("LAN") / wide area network ("WAN") (network) 105, wireless network 110, event sharing server (ESS) 106, mobile devices (client devices) 102 to 104, and client devices 101.

An embodiment of the mobile devices 102 to 104 will be described in more detail below in conjunction with FIG. In general, however, mobile devices 102-104 can virtually include any portable computing device capable of receiving and transmitting messages over the network, such as network 105, wireless network 110, and the like. The mobile devices 102-104 can also be generally illustrated as being grouped into a portable client device. Thus, mobile devices 102-104 can virtually include any portable computing device that can be coupled to another computing device and that receives information. Such devices include portable devices such as cellular phones, smart phones, display pagers, radio frequency (RF) devices, infrared (IR) devices, personal digital assistants (PDAs), handheld computers, laptops, wearable devices. Computer, tablet computer, integrated device incorporating one or more of the aforementioned devices, and the like. Thus, mobile devices 102-104 are typically quite extensive in terms of performance and features. For example, a cellular phone can have a numeric keypad set and a monochrome LCD display on which only text can be displayed. In another example, a network enabled mobile device can have a touchpad, stylus, and a color LCD display in which text and graphics can be displayed.

The network enabled mobile device may include a browser application that is configured to receive and send web pages, website-like messages, and the like. The browser application can be configured to virtually receive and display graphics, text, multimedia, etc. using any web-based language, including a wireless application protocol message (WAP). In one embodiment, the browser application is enabled and enabled Use Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WML Script, Java Script, Standard Generalized Markup Language (SMGL), Hypertext Markup Language (HTML), Extensible Markup Language (XML), etc. Display and send messages.

Mobile devices 102-104 may also include at least one other client application that is configured to receive content from another computing device. The client application can include the ability to provide and receive text content, media content, and the like. The client application can provide additional information identifying itself, including type, performance, name, and so on. In an embodiment, the mobile devices 102-104 can uniquely identify themselves through a variety of different mechanisms, including a telephone number, a mobile identification number (MIN), an electronic serial number (ESN), or other mobile device identifier. The information may also indicate a content format in which the mobile device is enabled. This information can be placed in a message and transmitted to the ESS 106, the client device 101, or other computing device.

The mobile devices 102 to 104 can also be configured to communicate a message with another computing device (eg, ESS 106, client device 101, etc.), such as through a short message service (SMS), multimedia messaging service (MMS), instant messaging. Communication program (IM), Internet chat room (IRC), Mardam-Bey's IRC (mIRC), Jabber, etc. However, the invention is not limited to such message agreements, and any other message protocol may be used virtually. For example, the client application allows users to interact with browser applications, email applications, VOIP applications, and the like.

The mobile devices 102 to 104 can be further configured to include a client application that causes the terminal user to log in to one managed by another computing device. End user account, such as ESS 106. For example, such end user accounts can be configured to enable end users to receive emails, send/receive IM messages, SMS messages, access selected web pages, participate in social networking event events, and the like. However, there is no need to log in to the terminal user account and participate in various social network connection events.

In addition, the mobile devices 102-104 can include another application that is configured to enable the mobile user to share and/or receive media content and display the media content. In an embodiment, each of the mobile devices 102-104 can share and/or receive media content from the ESS 106 and/or from another of the mobile devices 102-104. For example, media content can be shared between mobile devices using MMS, WAP, and the like. In one embodiment, a mobile device can receive a message indicating that the media content is available for viewing and/or annotating a website or the like.

With respect to shared media content, mobile devices 102-104 can enable interaction with each other by sharing various different messages, as well as substantially participating in a variety of different integrated social experiences in addition to voice communication. In an embodiment, the mobile devices 102-104 can enable a user to interact with a spontaneous event. For example, a user of one of the mobile devices 102-104 can generate a group including the identified members and send a message to the member regarding the event. In an embodiment, members of the group may then choose to share media content, such as photos, video clips, audio clips, text messages, emails, etc., with other members of the group. Moreover, the mobile devices 102-104 can cause any member of the group to also join other members to the group. Figures 6 through 7 below include group generation and shared media An embodiment of the volume.

Mobile devices 102-104 can also communicate with non-mobile client devices, such as client device 101 and the like. In one embodiment, the communication includes providing information about the shared media to the user of the client device 101, and the like.

The client device 101 can virtually include any computing device capable of communicating over the network to send and receive information (including social network connection information, etc.). The set of devices includes devices that are typically connected using wired or wireless communication media, such as personal computers, multi-processor systems, microprocessor-based consumer electronic devices or programmable consumer electronic devices, network PCs, and the like. In an embodiment, client device 101 may be grouped into a website, or other location, that can access shared media content, and annotate the media content, add additional media content, and the like.

The wireless network 110 can be configured to couple the mobile devices 102-104 and its components to the network 105. Wireless network 110 may include any of a variety of different wireless subnetworks that additionally cover a separate special network to provide infrastructure-oriented connectivity to mobile devices 102-104. The seed network may include a mesh network, a wireless LAN (WLAN) network, a cellular network, and the like.

Wireless network 110 may additionally include a stand-alone system of terminals, gateways, routers, etc., connected by a wireless radio link or the like. The connectors can be configured to move freely and randomly, and can be arbitrarily self-organized so that the topology of the wireless network 110 can be changed quickly.

The wireless network 110 can additionally employ a variety of access technologies, including a second generation (2G) radio access cellular system, a third generation (3G) radio access cellular system, WLAN, wireless router (WR) mesh, and more. Access technologies such as 2G, 3G, and future access networks may enable wide-area coverage of mobile devices, such as mobile devices 102-104 having a variety of different mobilities. For example, the wireless network 110 can enable a radio connection through a radio network access technology, such as Global System for Mobile Communications (GSM), Integrated Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Broadband Code Multiple Access (WCDMA) and so on. Essentially, wireless network 110 can virtually include any wireless communication mechanism whereby information can be moved between mobile devices 102-104 and another computing device, network, and the like.

Network 105 may be configured to couple ESS 106 and its components to other computing devices, including mobile devices 102-104, client device 101, and to mobile devices 102-104 via wireless network 110. The network 105 is enabled to use any form of computer readable media for communicating information from one electronic device to another. Similarly, in addition to local area networks (LANs), wide area networks (WANs), and direct connections, the network 105 can include the Internet, such as through a universal serial bus (USB) port, which can be read by other forms of computers. Media, or any combination of these. On a set of interconnected LANs, including LANs based on different architectures and protocols, a router acts as a link between the LANs, thereby passing messages from one LAN to another. Similarly, the communication links between LANs typically include twisted pairs or coaxial cables, and the communication links between the networks can use analog telephone lines, complete or partial dedicated digital lines, including T1, T2, T3 and T4, Integrated Services Digital Network (ISDN), Digital Subscriber Line (DSL), wireless links (including satellite links), or other communication links known to those skilled in the art. Furthermore, the far end The computer and other related electronic devices can be remotely connected to the LAN or WAN via a modem or temporary telephone link. Essentially, the network 105 includes any communication method whereby information can be used in the ESS 106. Moving between the client device 101 and other computing devices.

In addition, the communication medium may typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, data signal, or other transmission mechanism, and including any information delivery media. The terms "modulated data signal" and "carrier signal" include a signal that has one or more of its own set of features or that is altered to encode information, instructions, data, etc. in the signal. For example, communication media includes wired media such as twisted pairs, coaxial cables, fiber optic cables, waveguides, and other wired and wireless media such as acoustic, RF, infrared, and other wireless media.

An embodiment of the ESS 106 will be explained in greater detail below in conjunction with FIG. However, in brief, the ESS 106 can include any computing device that is coupled to the network 105 to enable generation of a spontaneous event group and for sharing media content with members of the group. The ESS 106 can receive media content from various different participants of the event as well as other social network connection information, including information associated with events, messages, and the like. The ESS 106 can then use any of a variety of different communication services to enable the message to be shared among members of the group. Further, the ESS 106 can enable a website or other location for storing and accessing at least some of the shared messages. The ESS 106 may additionally enable members of the group to join more members to the group, even if the member who joins the action is not the original founder of the group.

The ESS 106 may also enable members of the group to provide annotations to the event, and/or media content associated with the event. In one embodiment, the ESS 106 can provide a user interface, such as a drop down menu, a form, a description language, etc., to enable a member to access event information and provide annotations to various different components associated with the event. For example, the ESS 106 may enable a member to select a photo, audio clip, or other media content using the user interface and associate text or other content with the selected item. Further, the user may also be enabled by the ESS 106 to provide various other interpretations of the event, such as the title of the event, the location of the event, information about other participants of the event, an avatar, and the like.

The ESS 106 group can be configured to further determine the start time and/or an end time of the event. In one embodiment, the start time and/or end time of the event may be automatically determined based in part on the media content and/or text message flow between the members. In an embodiment, the start time may be based on the time generated by the group, and then corrected when the flow rate of the media content and/or message exceeds a threshold. In another embodiment, the start time can be determined by searching for content of a text message or the like for time information. In one embodiment, the end time is based on a flow rate of shared messages between members that is less than another threshold. In another embodiment, the end time may be determined according to the time when the traffic rate of the shared message is less than a certain number per hour or the like. The ESS 106 can perform at least some of its actions using a procedure similar to that described in connection with FIG.

Devices that can operate as ESS 106 include: personal computers, desktop computers, multi-processor systems, microprocessor-based consumer electronics, or programmable Consumer electronics, network PCs, servers, and more.

Although the ESS 106 is shown as a single computing device in Figure 1, the present invention is not so limited. For example, one or more functions of the ESS 106 can be assigned to one or more separate computing devices. For example, the actions of various social network connection events may be managed by multiple computing devices, including sharing media content, managing instant messaging (IM) talks, SMS messages, email messages, without departing from the scope or spirit of the present invention. Publish media content and determine implicit information such as start/end time, location of an event, and more.

<u style="single">Demonstrative mobile client environment</u>

Figure 2 illustrates an embodiment of a mobile device 200 included in a system in which the present invention can be implemented. The mobile device 200 can include more or less than the components shown in FIG. However, the components shown are sufficient to disclose a display embodiment for practicing the invention. For example, mobile device 200 can represent mobile devices 102-104 of Figure 1.

As shown in the figure, the mobile device 200 includes a processing unit (CPU) 222 that communicates with a plurality of memories 230 via bus bars 224. The mobile device 200 also includes a power supply 226, one or more network interfaces 250, an audio interface 252, a video interface 259, a display 254, a keyboard group 256, a luminaire 258, an input/output interface 260, and a graphical touch interface 262. And a selective global positioning system (GPS) receiver 264. The power supply 226 provides power to the mobile device 200. A rechargeable or non-rechargeable battery can be used to provide power. The power can also be supplied by an external power source, such as an AC rectifier or pair A battery extension that replenishes power and/or charges the battery.

The mobile device 200 can selectively communicate with a base station (not shown) or directly with another computing device. The network interface 250 includes circuitry for coupling the mobile device 200 to one or more networks, and is constructed to be used in conjunction with one or more communication protocols and technologies, including but not limited to: Global System for Mobile Communications (GSM), Code Multiple Access (CDMA), Time Division Multiple Access (TDMA), User Datagram Protocol (UDP), Transmission Control Protocol/Internet Protocol (TCP/IP), SMS, Integrated Packet Radio Service (GPRS), WAP, Ultra Wideband (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols. The network interface 250 is sometimes referred to as a transceiver, transceiver, or network interface card (NIC).

The audio interface 252 can be configured to generate and receive audio signals, such as human voice. For example, the audio interface 252 can be coupled to a speaker and microphone (not shown) to enable communication with other devices and/or to generate an audio confirmation message for an action. Display 254 can be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), or any other type of display used in conjunction with an arithmetic device. Display 254 can also include a touch screen configured to receive input from an object, such as a stylus or a human finger.

The video interface 259 can be configured to capture video images, such as still photos, video clips, infrared video, and the like. For example, video interface 259 can be coupled to a digital video camera, a webcam, or the like. The video interface 259 can include lenses, image sensors, and other electronic devices. Image sensor A complementary metal oxide semiconductor (CMOS) integrated circuit, a charge coupled device (CCD), or any other integrated circuit for sensing light may be included.

Keyboard set 256 can include any input device configured to receive input from a user. For example, keyboard set 256 can include a button numeric dial or a keyboard. Keyboard set 256 can also include command buttons associated with selecting and transmitting images. Illuminator 258 can provide status indication and/or provide light. The illuminator 258 can remain active for a specific period of time, or remain active in response to an event. For example, when illuminator 258 is active, it can provide backlighting for buttons on keyboard set 256 and remain on, while the client device is powered. Likewise, illuminator 258 can provide backlighting for various different types of buttons when performing certain actions, such as dialing another client device. Illuminator 258 can also place the light source in a transparent or translucent housing of the client device to illuminate in response to an action.

Mobile device 200 also includes an input/output interface 260 for communicating with external devices, such as earphones, or other input or output devices not shown in FIG. The input/output interface 260 can use one or more communication technologies such as USB, infrared, Bluetooth (Bluetooth)^TM)Wait. The graphical tactile interface 262 can be configured to provide tactile feedback to a user of the client device. For example, when another user of an computing device is making a call, a graphical tactile interface can be used to cause the mobile device 200 to vibrate in a particular manner.

The selective GPS transceiver 264 can determine the physical coordinates of the mobile device 200 at the surface of the earth, which typically outputs a position as a latitude and longitude value. The GPS transceiver 264 can also be applied to other geolocation mechanisms including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or the like to additionally determine the physical location of the mobile device 200 on the surface of the earth. It is to be understood that in different situations, the GPS transceiver 264 can determine that the mobile device 200 is in a physical location within a few centimeters; in other conditions, the determined physical location may be less precise, such as one meter. Or greater distance. However, in an embodiment, the mobile device may provide other information for determining the physical location of one of the devices through other components, including, for example, a MAC address, an IP address, and the like.

The bulk memory 230 includes a RAM 232, a ROM 234, and other storage components. A large number of memories 230 display another example of a computer storage medium for storing information, such as computer readable instructions, data structures, program modules, or other materials. The bulk memory 230 stores a basic input/output system ("BIOS") 240 for controlling the low-level operation of the mobile device 200. The mass memory also stores an operating system 241 for controlling the operation of the mobile device 200. It will be appreciated that this component can include general purpose operating systems such as UNIX or LINUX.^TMOr a professional client communication operating system, such as Windows Mobile^TMOr Symbian^®working system. The operating system can include or be coupled to a Java virtual machine module that enables control of hardware component and/or operating system operations via a Java application.

The memory 230 further includes one or more data stores 244 for the mobile device 200 to store the application 242 and/or other materials. For example, the data store 244 can also be used to store information describing various different capabilities of the mobile device 200. This information can then be provided to another device, including being transmitted as a header in a communication action, being requested to transmit, and the like. Furthermore, the data store 244 can also be used to store media content and/or social media. Hand over network links, including text messages, contacts, and community membership lists. At least a portion of the media content and/or event information may also be stored on the storage medium 266, such as a disk drive in the mobile device 200, a removable storage, or the like.

The application 242 can include computer executable instructions that, when executed by the mobile device 200, can provide, for example, a calendar, a contact manager, a work manager, a transcoder, a database program, a word processor, a screen saver, a security application. Programs, spreadsheet programs, games, search programs, and more. Application 242 can additionally include a message manager (MM) 245.

The MM 245 represents any of a variety of different applications that are configured to send, receive, and/or process messages and other network content, including but not limited to SMS, MMS, IM, email, VOIP, browsers. And, and enable communication with another user of another network connection device. For example, the MM 245 can include any of a variety of different browser applications that are controlled by the operating system 241 to enable and manage the actions of requesting, receiving, and presenting a page, such as a WAP page (sometimes referred to as a WAP card). , SMGL, HTML, HDML, WML, WMLScript, JavaScript, etc.

MM 245 may include other subject or group with management to initiate a meeting of IM instant messaging applications, including but not limited to AOL instant messenger, Yahoo! Messenger, .NET Messenger server, ICQ, etc. In one embodiment, the IM applications in the MM 245 can be combined to use SIP/RTP to integrate IM/VOIP features. For example, IM applications can use SIMPLE (SIP for instant messaging and presence), APEX (application) Exchange), Prim (attendance and instant messaging protocol), Open XML style XMPP (extension of the sender and presence protocol), created specifically for mobile devices and is generally known as Jabber and OMA (Open Mobile Alliance) of IMPS (Instant Messaging and Presence Service) and so on.

The MM 245 can also include a text messaging application that enables the mobile device 200 to receive and/or send text messages to another device. In one embodiment, the text messaging application can also provide an alerting mechanism to the user of the mobile device 200 indicating when the text message was received. The text messaging application also allows the user to write a text response message and send the text response message over the network. The text messaging application can operate to manage SMS text messages, MMS messages, enhanced messaging service (EMS) messages, etc., wherein graphics, video clips, voice files, and files can be transferred between the mobile device 200 and another network connection device. Or other media content.

Regardless, any one of the MM 245 or one of the plurality of messaging applications can be used to cause the user of the mobile device 200 to generate a group of members for the event, to share media content with members of the group, and others. Messages, joins from another network connection device to access media content, etc., such as websites, servers, and the like. In one embodiment, the MM 245 may enable the user to send SMS messages and/or send/receive MMS messages, where the messages may include media content, links to remote servers storing media content, and the like. The MM 245 can use an interface, such as in conjunction with the interfaces described in Figures 6 through 7 below, to perform at least some of its actions. Moreover, the mobile device 200 can use a program, such as the one described in connection with FIG. 4, to perform at least some of its actions.

<u style="single">Display server environment</u>

Figure 3 illustrates an embodiment of a network device included in a system in which the present invention can be implemented. Network device 300 may include more components than shown. However, the components shown are sufficient to expose a display embodiment for implementing the present invention. For example, network device 300 can represent ESS 106 of FIG.

The network device 300 includes a processing unit 312, a video display adapter 314, and a plurality of memories, each of which communicates with each other via a bus bar 322. The bulk memory generally includes a RAM 316, a ROM 332, and one or more permanent mass storage devices, such as a hard disk drive 328, a tape drive, a CD player, and/or a floppy disk drive. The mass memory stores an operating system 320 for controlling the operation of the network device 300. Any general purpose operating system can be used. A basic input/output system ("BIOS") 318 can also be provided to control the low-level operation of the network device 300. As shown in FIG. 3, the network device 300 can also communicate with the Internet or some other communication network via the network interface unit 310. The network interface unit is constructed to be used in combination with various communication protocols, including TCP/ IP Agreement. The network interface unit 310 can sometimes be referred to as a transceiver, transceiver, or network interface card (NIC).

The above-mentioned large amount of memory exhibits another type of computer readable medium, namely a computer storage medium. Computer storage media may include power, non-electricity, removable, non-removable, implemented by any method or technology for storing information (eg, computer readable instructions, data structures, program modules, or other materials). Divisor media. Examples of computer storage media include storage RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disc (DVD), or other optical storage, magnetic cassette, which is accessed by the computing device. A tape, disk storage, or other magnetic storage device, or any other medium.

The large amount of memory also stores code and data. One or more applications 350 can be loaded into a large amount of memory and executed on the operating system 320. Examples of applications include: transcoders, schedulers, perpetual calendars, database programs, word processing programs, HTTP programs, customized user interface programs, IPSec applications, encryption programs, security programs, account management, and more. An event manager (EM) 355 and/or a message server 354 can also be included as an application in the application 350.

An event data store (EDS) 352 stores a plurality of received media content. In an embodiment, EDS 352 can be a database, a file structure, and the like. The EDS 352 can store the media content in a category structure, such as a file, a photo album, a picture, a tree diagram, etc., based in part on the event, the time associated with the event, and the like. In an embodiment, because certain events may occur according to a schedule, such as periodically, etc., media content may also be classified according to event schedules. Furthermore, any of a variety of different data formats can be utilized to store media content. In one embodiment, the media content in the EDS 352 can be accessed for display over a network. For example, media content can be accessed via a hyperlink, from a web server, using a mobile device, and the like.

The EDS 352 group can also be configured to store information associated with group membership. Thus, in an embodiment, EDS 352 can receive and store identification information for one of a group of members. The identification information may include a name, Phone number, network address, etc.

The message server 354 virtually includes any communication server that is blocked to enable communication between the network connection devices, including an email server, an SMS server, various text messaging servers, VOIP servers, and IM servers. , MMS server, RSS server, audio server, network server, etc. Message server 354 can use EDS 352 to store or manage media content delivered over the network. In one embodiment, various message servers 354 can receive messages from the network device and use the event manager (EM) 355 to store media content and/or through the network using other information about group membership. Members share media content. In an embodiment, the message server 354 can store the received media content in the EDS 352 for a group in conjunction with the EM 355.

The EM 355 group can be configured to manage events, including spontaneous events. Thus, the EM 355 can receive a request from the message server 354 to generate, delete, or modify a group for an event. The EM 355 can use the EDS 352 to generate or manage membership in the group. The EM 355 can additionally use a variety of different messaging servers 354 to send messages to members of the group indicating that they are members of the group.

Although the message server 354 can be configured to manage and enable sharing of messages, including messages with media content, the EM 355 can use the message and related information to determine implicit information about an event. Therefore, the EM 355 can determine the start time, end time, location, and the like of an event. In an embodiment, the EM 355 can utilize at least one message server 354 to access the implicit information. Furthermore, the EM 355 provides a user interface for An event, and/or media content in an event is annotated on a website or other location in conjunction with a variety of different messaging servers 354. The EM 355 can use a program, such as the one described below in conjunction with Figure 5, to perform at least some of its actions.

<u style="single">Generalized operation</u>

Some aspects of the operation of the present invention will be described below with reference to Figs. 4 to 5. Figures 4 through 5 provide some aspect-oriented logic flow diagrams, while Figures 6 through 7 provide examples of further use cases of the present invention.

Figure 4 is a logic flow diagram that generally illustrates an embodiment of a program for generating an event for sharing media content. As shown, the program 400 of FIG. 4 can be performed using any of the mobile devices 102-104 of FIG. Moreover, in an embodiment, at least some of the blocks of the program 400 can occur in an event.

After the start block, the process 400 begins at block 402 where a user of the mobile device generates a group. Referring to the example 600 of FIG. 6, in an embodiment, the interface 601 exhibits a message that can be sent to an event manager service, such as the EM 355 of FIG. In an embodiment, the message may use SMS, although the invention is not limited thereto, and any of a variety of different communication message services may be used. As shown in Figure 6, the message can request that a "new" group be created, named after the name "party group." In an embodiment, the first user of the event manager service may also be required to register. For example, such registration methods include a click action regarding consent to the terms of service, privacy, and the like. In an embodiment, Accessing such a consent click action and the like on a remote server using a hyperlink.

Referring to the process 400, the process then proceeds to block 404 where the user of the mobile device and/or the identification of the member of the group is requested to be queried. Referring briefly to FIG. 6, interfaces 602 and 603 show communication embodiments that may occur in block 404.

The process then proceeds to block 406 where the user can then choose to send one or more messages to the members of the group. Examples of this action are shown in interfaces 605 and 605 of Figure 6. The process 400 can then proceed to blocks 408, 410, and/or block 412.

In block 408, the user who generated the group or any member of the group may modify the group membership. In other words, at any time during an event, a member of the group can enter another person's identification material to cause other individuals to join the group and share information about the event. The process then loops to decision block 414.

In block 410, in the event, any member of the group can share media content with other members of the group. For example, in this event, members can take photos, record video clips, audio clips, or access a variety of other media content. The member can then use the MMS or another messaging service to send the media content to the event manager service for sharing. An example of such a sharing method is shown in Figure 7 by interfaces 701 through 703. As shown, in an embodiment in which the user can be a member of a plurality of groups, the user can be asked which group to share the media content with. However, in an embodiment, once selected, it will be based on the end of the event. A decision made by time or according to a variety of other actions, directing additional media content to the same group until the user selects another group, or the event ends. Also shown in Figure 7 is an example showing the delivery of media content to other members of the group using a variety of different mechanisms, including, for example, MMS. In one embodiment, a message can be transmitted to another member of the group as an SMS message that includes a hyperlink to a server in which media content is accessible. Moreover, in one embodiment, the media content can be communicated to the member using the messaging service based in part on the capabilities of its mobile device. Thus, for example, information about the member's mobile device can be utilized to determine that the mobile device is capable of receiving media content using MMS, WAP, email, etc., while another mobile device uses only SMS. Regardless, in block 410 of Figure 4, the media content may be shared during the event. The process 400 can then proceed to decision block 414.

In block 412, other types of messages can also be delivered to members of the group using a variety of other text messaging services, email services, and the like. In this event, the message can be received and the message is distributed to members of the group. The process then proceeds to decision block 414.

In decision block 414, it will be determined if there are more messages, media content, and/or membership changes for this event. If so, the process can loop back to block 406 to continue until there are no messages, media content, or membership changes. This type of loop can be done in this event, but can be done for a certain period of time after the event has actually ended. For example, in some situations, a member may have taken several photos, video Movies, etc., and after the event has actually ended, choose to share them. The action of determining the end of the event can then be made in accordance with a number of different criteria, including the criteria described in connection with FIG. However, in brief, if it is determined that no more messages or changes have been received, the process proceeds to decision block 416.

In decision block 416, it will be determined if the shared event is to be annotated. If the shared event is to be annotated, the process proceeds to block 418; otherwise, the handler returns to a call procedure for other actions.

In block 418, in an embodiment, the user may select the event using his own mobile device or other computing device having a browser interface. In an embodiment, the media content may be displayed in a format suitable for the mobile device or other computing device, whereby the user may subsequently select and/or annotate the media content, and/or the event itself. Referring briefly to Figure 7, interface 705 shows a website interface embodiment for presenting event information including media content. The user can then select and provide annotations using a variety of different institutions, including menus, indicators, forms, text boxes, and the like.

Figure 5 is another logic flow diagram that generally illustrates an embodiment of a program for determining implicit information associated with an event based in part on shared media content. For example, the program 500 of Fig. 5 can be implemented in the ESS 106 of Fig. 1.

After the start block, the routine 500 will begin at decision block 502 where a determination will be made as to whether a new group is to be established or operated with an existing group. If you want to create a new group, before processing the program Proceed to block 504; otherwise, the process proceeds to decision block 510.

In block 504, a request to generate a new group will be received. In an embodiment, the candidate name of the group may be provided by the mobile device user. In an embodiment, if the candidate name already exists, the user is asked to select another name. However, in an embodiment, the group name copying action can be managed according to membership. Thus, in an embodiment, if the user is not a member of the group with the provided name, the name can be utilized to generate the group even if the group name is already independent of the producer. Thus, in an embodiment, in the routine 500, the group can be uniquely identified based on the identification information of the producer and the provided group name. Regardless, the process then proceeds to block 506 where the identifier of the member of the group will be received. The identifiers include any of an email address, an SMS address, an IM address, a phone number, or a plurality of different other identifiers. The process then proceeds to block 508 where the time generated by the group will be recorded. In an embodiment, the time generated by the group may be used as the initial start time of an event associated with the group. The process then proceeds to decision block 510.

In decision block 510, a determination is made as to whether a text message has been received from one or more members of the group. The text message can be received via SMS, IM, email, MMS, etc. If a text message is received, the process will proceed to block 512; otherwise, the process proceeds to decision block 516.

In block 512, the received text message can be shared (e.g., scattered) with other members of the group using any of a variety of different messaging services, including the same messaging service used in conjunction with the received text message. program 500 proceeds to block 514, in an embodiment, the initial start time and/or end time of the event associated with the group will be determined in block 514. For example, in an embodiment, a time at which the first text message is received to be shared with the group can be used to determine the start time of the event associated with the group. In an embodiment, the content of the text message may be searched for keywords, such as time, date, and the like. If the keywords are identified in the message, they can be used in part to determine the start and/or end time of the event. In another embodiment, relevant information about the physical location of the mobile device for transmitting the text message can be obtained and used to determine the location of the event. The process will then proceed to decision block 516.

In decision block 516, a determination is made whether a message including media content is received. If so, the process will proceed to block 518; otherwise, the process proceeds to decision block 524. In block 518, the received media content may be shared (eg, distributed) by other members of the group. In an embodiment, the media content may be shared using a messaging service that is different than the media content received. The handler then moves to block 520 where the media content, such as a website, etc., can be automatically posted to a server (associated with the event). In an embodiment, the shared media content action in block 518 can include providing a hyperlink to the location of the media content, or other access mechanism. The process then proceeds to block 522 where the start and/or end time of the event can be modified. What is expected is that when an event occurs, more messages are shared, often increasing with the traffic rate of the event's message (eg, sharing rate). Therefore, in one embodiment, several text messages and/or messages with media content may be close to one thing. The beginning of the piece is shared. However, as the event continues, it is expected that the rate of message sharing among members will increase. It can be further understood that when the event is nearing the end, the sharing rate of the message will decrease. At some point, the message can be stopped or reduced to a very low traffic rate. Therefore, various criteria can be used when determining the modification start time of an event. For example, in one embodiment, when the message traffic rate exceeds a certain threshold, such as two minutes, five minutes, etc., then it may be determined that the event has begun. However, it should be understood that other values may be selected without departing from the scope of the invention. Furthermore, in an embodiment, the start time may also be determined, for example, based on receipt of a first message having media content.

Similarly, the end time can also be inferred from the traffic rate of the message. Therefore, in an embodiment, when the traffic rate or the like of the message or media content message falls below another threshold, it may be determined that the time is the end time of the event. For example, if a media content message or a text message is not received during a 2-hour period, a 12-hour period, or the like, the end time can be determined as the time at which the last message was received, or based on a gap time from that time.

Moreover, in the process of sharing the media content message, the physical location of the mobile device associated with sending the pre-shared message may also be obtained. In one embodiment, if it is determined that a plurality of mobile device sharing messages are outside a certain determination distance, then the locations may be used to determine a location of the event. Thus, in an embodiment, the location of the event can be determined using a location at the center of the location of the mobile device. In another embodiment, the location of the mobile device can be used to search for data stores, such as business listings, white papers, maps, etc., to identify institutions, businesses, parks, theaters, homes, and the like. Can accompany The location of the mechanism is then used to indicate the location of the event. However, the invention is not limited to such techniques used to determine the location of the event, and any other mechanism may be used virtually. For example, in an embodiment, a shared message may be searched for a keyword that may indicate a location. Regardless, the process then proceeds to decision block 524.

In decision block 524, a determination is made whether a request to modify the membership of the group is received. The request may be received from the producer of the group, or even from one or more members of the group. Regardless, if a request is received, the process proceeds to block 526 where the membership will be modified. The process then proceeds to decision block 528. If the request is not received, the handler also proceeds to decision block 528.

In decision block 528, it is determined whether more messages are received for the events of this group. In one embodiment, such a determination is made based on the flow rate of the shared message below a certain threshold. Therefore, if a message has not been received for a certain period of time, it may be determined that the event has ended and the process proceeds to block 530. Although subsequent messages may be received, such as days or even weeks after the end of an event, decision block 528 determines the end of an event based on some implicit information obtained from the message sharing action, as described above. Thus, if more messages are received according to the selected criteria, the handler then loops back to decision block 510 where it is expected that the event is occurring and more messages will be shared or being shared.

In block 530, the start and/or end time of the event can be modified using any of a variety of different mechanisms, including the mechanisms described above. In an embodiment, the determined start and/or end time can be sent to a website This event is annotated for example, as shown in Figure 7 at start time 706 and end time 707.

The process then proceeds to block 532 where the location of the event can be modified according to any of a variety of different mechanisms, including the mechanisms described above. In one embodiment, the determined location may be provided to a website for annotating the event, such as indicated by location 708 in FIG.

Moreover, in an embodiment, a plurality of different other implicit information may also be determined according to the message sharing action in the event. For example, in an embodiment, it may be determined that the member is not participating in the event based on certain low-level messages sent from a member and/or a physical location of the member's mobile device. In another embodiment, such information may also be used to indicate that the member attended the event but chose not to send the message. The information may also be recorded and/or used to annotate the event, determine future event members, or be used for any of a variety of other purposes. Regardless, the handler can then return to a calling program for other actions.

It will be appreciated that various blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by computer program instructions. The program instructions can be provided to a processor to produce a machine whereby upon execution of the instructions on the processor, means for performing the actions indicated by the flowchart block are generated. The computer program instructions can be executed by a processor such that a series of operational steps can be performed by the processor to generate a computer-implemented program, whereby when the instructions are executed on the processor, a The component of the action. The computer program instructions may also cause at least some of the operational steps shown in the flowchart block to be performed in parallel. Furthermore, there can be more than one processing Some of these steps are performed on the device, such as may occur in a multi-processor computer system. In addition, one or more of the blocks or combinations of blocks in the flowcharts can be carried out simultaneously with other blocks or combinations of blocks, or even in a different order than the ones presented, without departing from the scope or spirit of the invention. .

Accordingly, blocks of the flowchart support component combinations for performing the specified actions, combinations of steps for performing the specified actions, and program command means for performing the specified actions. It will also be appreciated that various blocks of the flowcharts and combinations of blocks of the flowcharts can be practiced in the combination of a special purpose hardware system or a special purpose hardware and computer instructions for performing the specified actions or steps.

The above description, examples and materials provide a complete description of the manufacture and use of the present invention. Since many embodiments of the invention can be made without departing from the scope and spirit of the invention, the spirit of the invention is disclosed in the following claims.

<p>100 system</p><p>101Client device</p><p>102Mobile devices (client devices)</p><p>103Mobile devices (client devices)</p><p>104Mobile devices (client devices)</p><p>105Local Area Network (LAN) / Wide Area Network (WAN) (Network)</p><p>106Event Sharing Server (ESS)</p><p>110Wireless network</p><p>200 mobile device</p><p>222Processing Unit (CPU)</p><p>224 busbar</p><p>226Power supply</p><p>230A large amount of memory</p><p>232RAM</p><p>234ROM</p><p>240Basic input/output system ("BIOS")</p><p>241 operating system</p><p>242Application</p><p>244 data storage</p><p>245Message Manager (MM)</p><p>250Internet interface</p><p>252 audio interface</p><p>254 display</p><p>256 keyboard group</p><p>258 illuminator</p><p>259Video interface</p><p>260Input/output interface</p><p>262 Graphical touch interface</p><p>264Global Positioning System (GPS) Receiver</p><p>266 Storage media</p><p>300Network devices</p><p>310Network Interface Unit</p><p>312Processing unit</p><p>314 video display adapter</p><p>318Basic Input/Output System ("BIOS")</p><p>316RAM</p><p>320Operating system</p><p>322 busbar</p><p>324Input/Output Interface</p><p>326CD-ROM/DVD-ROM drive</p><p>328hard disk drive</p><p>332ROM</p><p>350Application</p><p>352 Event Data Storage (EDS)</p><p>354Message Server</p><p>355Event Manager (EM)</p><p>400Program</p><p>402~418Steps</p><p>500 procedures</p><p>502~532Steps</p><p>600Instance</p><p>601 interface</p><p>602" interface</p><p>603 interface</p><p>604" interface</p><p>605 interface</p><p>700Instances</p><p>701 interface</p><p>702 interface</p><p>703 interface</p><p>705" interface</p><p>706Starting time</p><p>707 End time</p><p>708 position</p>

1 is a system diagram showing an embodiment of an environment in which the present invention can be implemented; FIG. 2 is a diagram showing an embodiment of a mobile device included in a system in which the present invention can be implemented; FIG. 3 is shown to be implemented in a A network device embodiment in a system of the present invention; FIG. 4 is a logic flow diagram generally showing an embodiment of a program for generating an event for sharing media content; Figure 5 is another logic flow diagram that generally illustrates an embodiment of a program for determining implicit information associated with an event based in part on shared media content; Figure 6 illustrates a usage condition for generating an event. An embodiment; and Figure 7 illustrates an embodiment of the use of shared media content for the event in accordance with the present invention.