Mobile shared group interaction

[0001] This invention relates to electronic communication, and more specifically to enabling a shared group interaction experience including a mobile group member, and at least one other mobile or non-mobile group member.

[0002] With technological advances have come many changes in the ways that people communicate with one another. For example, affordable home computing systems and the Internet have made instant messaging a popular tool for engaging in one-on-one, real-time electronic communications. Cellular telephones have also emerged as a prevalent fixture in our society, keeping even the most mobile users in touch with others.

[0003] These technological advances have led to changes in the way individuals communicate with each other in one-on-one conversations. However, many people, especially teenagers and young adults, frequently participate in group social situations involving more than just one other person. Although cellular telephones can enable conference calls with three or more individuals and instant messaging applications allow additional individuals to be invited to join a particular conversation, there are no existing applications that are designed to enable group social interactions in ways that are consistent with face-to-face group social interactions. Face-to-face group social interactions may include several simultaneous activities such as talking, listening to music, and looking at pictures. For example, if several individuals meet together at a person's house, they may simultaneously listen to a music CD, talk, and look at pictures from a trip that one of the individuals recently took. All of the individuals are able hear the music, view the pictures, and comment on the pictures to one another at the same time.

[0004] Most existing communication mechanisms allow for multiple individuals to communicate, for example through instant messaging, but require that the communication application be specifically configured for the group each time. That is, for instant messaging, each individual to be included in a conversation has to be specifically invited to join. Furthermore, existing communication mechanisms are designed to be accessed from either a desktop computer system or from a cellular telephone. There are no existing systems that enable communication between multiple members of a group where some of the group members are using a mobile device (e.g., a cellular telephone) and other group members are using a non-mobile device (e.g., a desktop computer system).

[0005] Accordingly, a need exists for a mechanism that facilitates real-time synchronous group interaction that includes mobile group members.

[0006] A technique is described for enabling a shared group interaction experience including a mobile group member as well as another mobile or non-mobile group member. A user can belong to one or more groups, where each group includes one or more other members. When a user is logged on, other members of the user's groups are able to see presence information that indicates that the user is online, and whether or not the user is connected via a mobile device (e.g., a cellular telephone).

[0007] A user interface is provided for a mobile device that enables a user to participate in real-time social group interactions with other group members who may be connected via another mobile device or via a non-mobile device (e.g., a desktop computer system).

[0008] FIG. 1 is a schematic diagram that illustrates an exemplary peer-to-peer network environment that supports mobile shared group interaction.

[0009] FIG. 2 is a block diagram that illustrates select components of an exemplary mobile device configured to support mobile shared group interaction.

[0010] FIG. 3 is a display screen representation of an exemplary non-mobile device shared group experience user interface and a corresponding exemplary mobile device shared group experience user interface.

[0011] FIG. 4 is a display screen representation of group member presence information as rendered using an exemplary non-mobile device user interface.

[0012] FIG. 5 is a display screen representation that illustrates a mobile device user interface as displayed to three different users.

[0013] FIG. 6 is a display screen representation of an exemplary group activities menu as rendered using an exemplary non-mobile device user interface and a corresponding exemplary mobile device user interface.

[0014] FIG. 7 is a display screen representation of an exemplary bubble message as rendered using an exemplary non-mobile device user interface and a corresponding exemplary mobile device user interface.

[0015] FIG. 8 is a display screen representation of an exemplary group photo sharing activity as rendered using an exemplary non-mobile device user interface and a corresponding exemplary mobile device user interface.

[0016] FIG. 9 is a display screen representation of an exemplary group photo editing activity as rendered using an exemplary non-mobile device user interface and a corresponding exemplary mobile device user interface.

[0017] FIG. 10 is a display screen representation illustrating image acquisition and association of location data with an image as rendered using an exemplary mobile device user interface.

[0018] FIG. 11 is a display screen representation of an exemplary group voting activity applied to an image as rendered using an exemplary non-mobile device user interface and a corresponding exemplary mobile device user interface.

[0019] FIG. 12 is a display screen representation of an exemplary calling card introduction as rendered using an exemplary mobile device user interface.

[0020] FIG. 13 is a display screen representation of an exemplary invitation for a third user to join a group musicmix activity being shared by two members of a group.

Overview

[0021] The embodiments described below provide techniques for enabling mobile shared group interaction. An application running on a mobile device (e.g., a cell phone) provides an interface through which a user can participate in synchronous, shared group activities (e.g., group instant messaging, image sharing, audio sharing, etc.). Other group members may participate in the shared group activities via another mobile device or via a non-mobile device (e.g., a personal computer) running an application that provides a similar user interface.

[0022] In an exemplary implementation, some group activities may be accessible by all group members; other group activities may be available only to those group members who are connected via a non-mobile device; and other group activities may be available only to those group members who are connected via a mobile device. For example, due to bandwidth constraints or mobile device memory limitations, a group file sharing activity may not be available to mobile group members. Similarly, an activity that enables group members to participate in a treasure hunt game may only be applicable to members who are connected via a mobile device.

[0023] Furthermore, support for some group activities may be implemented and/or presented differently on a mobile device as compared to on a non-mobile device. For example, to reduce bandwidth and memory requirements, a group photo sharing activity may automatically reduce the size of an image that is being transmitted to mobile group members.

[0024] In an exemplary implementation, a mobile group interaction user interface has limited structure and limited rules, thereby enabling a social group interaction that is equally controlled by each group member. For example, all members of any given group have equal authority regarding activities that the group can participate in, who can be invited to join the group, what icon and name are used to represent the group, and so on. In this way, a group is designed to mimic a face-to-face social group interaction in that all group members have the ability to participate in the group to the level they desire. Furthermore, no group member has the ability to remove another member from the group. Members can invite others to join the group and each member has the ability to leave a group.

[0025] Enabling online group social interactions is described in U.S. patent application Ser. No. 10/174,422, filed Jun. 18, 2002, entitled “Visual Group Interface for Group Connectivity”, and assigned to Microsoft Corporation, and U.S. patent application Ser. No. 10/230,247, filed Aug. 28, 2002, entitled “System and Method for Shared Integrated Online Social Interaction”, also assigned to Microsoft Corporation, both of which are hereby incorporated by reference in their entirety.

Network Environment

[0026] FIG. 1 illustrates an exemplary network environment 100 via which mobile shared group interaction may be enabled. Environment 100 includes mobile device 102, mobile device 104, non-mobile device 106, and non-mobile device 108. In the illustrated example, users of mobile device 102, mobile device 104, and non-mobile device 106 all belong to a particular group, as indicated by connections 110, 112, and 114. Similarly, users of mobile device 104, non-mobile device 106, and non-mobile device 108 all belong to another group, as indicated by connections 114, 116, and 118. In an exemplary implementation, connections 110, 112, 114, 116, and 118 are peer-to-peer connections that directly link the respective devices. In alternate implementations, other types of network connections may be used, such as server-based connections.

[0027] Although FIG. 1 illustrates mobile devices 102 and 104 as cellular telephones and non-mobile devices 106 and 108 as desktop computer systems, any device that can be configured to support real-time peer-to-peer connections and run an application that provides a group interaction user interface can be implemented as a component of network environment 100. For example, other types of mobile devices that may be configured as part of environment 100 include, but are not limited to, a personal digital assistant (PDA), a car stereo, a portable television, a portable DVD player, a portable stereo (e.g., a boombox), a digital picture frame, a watch, digital jewelry (e.g., a bracelet or pendant), and so on. Other types of non-mobile devices that may be configured as part of environment 100 include, but are not limited to, a laptop computer, a television set, a DVD player, a cable television system set-top box, and a digital video recorder.

Exemplary Mobile Device

[0028] FIG. 2 illustrates select components of an exemplary mobile device 200. As described above, mobile device 200 can be implemented in any number of embodiments, for example, as a cellular telephone, a portable television, a portable DVD player, and so on. Exemplary mobile device 200 includes one or more processors 202, a memory 204, a communication interface 206, and audio and/or video output 208.

[0029] Processor 202 is configured to perform any operations as required by mobile device 200. For example, if configured as a cellular telephone, processor 202 includes telephone processors that enable communications to be transferred over a cellular telephone network. Operating system 210 and application programs 212 are stored in memory 204 and executed on processor 202. Application programs 212 may include any type of firmware or software that can be executed using processor 202 to enable a particular functionality on mobile device 200. Example application programs may include an address book application and one or more games.

[0030] Social group application 214 is a particular application program that may be stored in memory 204 and executed on processor 202. Social group application 214 provides a user interface that enables a user of mobile device 200 to participate in real-time social interactions with other members of a group who are geographically distributed. An example user interface and social activities that may be supported by social group application 214 are described below.

Mobile Device User Interface

[0031] FIG. 3 illustrates an example user interface that may be rendered on a mobile device to enable a user to participate in shared group interactions, and a corresponding user interface that may be rendered on a non-mobile device. Non-mobile device user interface 302 includes group icons 304(1), 304(2), and 304(3), each of which represent a group to which the user currently logged onto the non-mobile device is a member. Associated with each group icon is a group name, presence information associated with members of the group, and activity notification icons associated with the group. For example, group icon 304(1) represents a group named “shredder”, as indicated by group name 306. Shredder group presence information 308 indicates that the shredder group includes seven members, four of whom are currently online.

[0032] Shredder group activity notifications 310 represent activities that one or more members of the group are currently participating in. Activity notifications 310 are shared, and appear to each member that is currently online.

[0033] Furthermore, in an exemplary implementation, although not illustrated, a history of group activity may be maintained and accessible by any member of the group. For example, the history function enables a user to “catch up” by reviewing group social interactions that have taken place while the user was logged off or otherwise unavailable. In the described exemplary implementation, group history notifications are available to users who are logged on via a mobile device or a non-mobile device. However, the amount or detail of the history notifications may be limited for users of a mobile device due to storage or bandwidth limitations. For example, a user on a mobile device may only be able to view the 15 most recent historical group interactions, but when logged on using a non-mobile device, the user has access to all of the available historical data.

[0034] A similar mobile device user interface 350 is also illustrated in FIG. 3. Mobile device user interface 350 includes one or more group icons 352(1), 352(2), 352(3). Mobile device user interface 350 may also include one or more individual icons, such as individual icon 354. Individual icons may represent, for example, individuals who are on the current user's instant messaging buddy list and who are currently online. A user can scroll through icons that are displayed, for example, by selecting scroll arrows 356 and 358. Other methods may also be used to scroll data on the screen, for example, specific buttons on the mobile device may be pressed to cause data on the screen to be scrolled. A user's social network is visually represented with group icons and individual avatars. The visual representation of the social network may be customized based on, for example, filtering preferences.

[0035] For example, in an exemplary implementation, group and individual icons may be filtered and/or arranged, at least in part, based on geographic data that describes the physical locations of one or more group members. For example, icons can be filtered so that only individuals who are mobile or groups with members who are mobile are displayed, and the icons at the bottom of the screen may be rendered larger than icons nearer the top of the screen to present a graphical perception of nearness. For group members using a mobile device with an embedded global positioning system (GPS), location information can be used to organize the group icons. This may be useful, for example, if one group member is shopping and finds a dress that she wants someone else to come look at. If the icons are displayed in an arrangement that indicates which other group members are closest (e.g., around the corner at a coffee shop as opposed to across town), she can contact those individuals and ask them to meet her at the store.

[0036] In an alternate implementation, individual and/or group icons may be filtered and/or arranged based on recent or frequent interaction. For example, a user may be a member of six groups and also have a relationship with three individuals. If only six icons can be displayed at a time, the icons may be filtered or arranged so that the six icons associated with the groups or individuals that the user interacts with most frequently (or has interacted with most recently) are displayed first.

[0037] In the illustrated example, the icon that is located closest to the bottom of the screen is currently selected. Data associated with a currently selected group icon 352(1) is displayed in the upper left portion of mobile device user interface 350. Similar to non-mobile device user interface 302, mobile device user interface 350 displays a group name 360, presence information 362, and activity notification icons 364 associated with the selected group. Additional presence information 366 may also be displayed that indicates which group members are online and of those, which are connected using a mobile device. Furthermore, mobile device user interface 350 also displays an avatar and presence information associated with the user of the mobile device. Avatar 368 is a visual representation of the user, which is displayed to other users with whom the current user is communicating. User presence information 370 displays the presence information that is displayed to other users in association with the current user.

[0038] FIG. 4 illustrates an exemplary display of detailed group presence information according to non-mobile device user interface 302. As described above, mobile device user interface 350 displays detailed group presence information 366 when a group icon is selected by scrolling it to the bottom most position of the screen. In the described exemplary implementation, more detailed presence information for each online group member may be accessed using non-mobile device user interface 302 by mousing over the group icon 304(1). When a user mouses over a group icon 304(1), a presence display box 402 appears that lists the name of each online group member, and for those members who are currently mobile, a mobile phone icon 404, or other type of mobile indicator.

[0039] FIG. 5 illustrates a mobile device user interface as displayed to three different users. The illustrated screen displays show that users can belong to more than one group, and that when a user is logged on, they automatically appear online to other members of each group that they belong to. That is, a user is not limited to participation in only one group at a time.

[0040] The user of mobile device 502 has username “buffybot” as indicated by the username 504. Similarly, the user of mobile device 506 has username “Geo”, and the user of mobile device 508 has username “Rocda House”. Rocda House uses an image of headphones 510 to represent himself. Geo and Rocda House are members of a two-member group, as indicated by the headphone icon 512 on Geo's display. Geo and Rocda House are also members of the Efx group 512 that is currently selected on Rocda House's display. Similarly, buffybot and Geo are both members of the shredder group 514 that is selected on both buffybot's user interface and Geo's user interface.

[0041] FIG. 6 illustrates a non-mobile device user interface group activity menu and a corresponding mobile device user interface group activity menu. In the described implementation, when a user of non-mobile device user interface 302 right clicks on a group icon 304(1), a group activity menu 602 is displayed. Group activity menu 602 includes a list of actions that can be performed in association with the group, such as activities, instant messaging (IM), sending a wink, sending a bubble, sending an email, and sharing a file.

[0042] Selection of the instant messaging menu item launches an instant messaging window that is visible to all of the group members who are online.

[0043] Selection of the “send wink” menu item launches a wink selection window through which a user can select or create a wink, which is a visual expression that, when selected, is sent to all members of the group. Winks may be static visual images, short video clips, or short animations. Furthermore, winks may also have an associated audio component that plays while the visual portion of the wink is rendered. Winks may be used to simultaneously express a user's mood or opinion to all members of the group. For example, a particular user may always send a wink that includes a yellow smiley face image and an audio portion that states, “Have a nice day!” every time they log off, as a way of sending a pleasant “goodbye” message to all of their friends who are still online.

[0044] In an exemplary implementation, to support mobile group members, large winks (e.g., winks that include a large graphics and/or audio component) may have an associated smaller version that can be sent to mobile group members. For example, a smaller version of a wink that includes a video component may have a static image instead of the video component. In this way, mobile users can participate in group activities while restricted by bandwidth and/or storage limitations.

[0045] Selection of the “send bubble” menu item launches a bubble creation window through which a user can enter a text message to be simultaneously sent to all members of the group. Bubbles are described in further detail below with reference to FIG. 7.

[0046] Selection of the “send email” menu item launches an email composition window through which a user can compose an email message to be simultaneously sent to all members of the group.

[0047] Selection of the “share file” menu item enables a user connected via a broadband connection to make a file available for other group members to download.

[0048] In the illustrated example, group activities are further listed in activity menu 604, which includes musicmix, photomix, voicechat, flix, and games lobby. Selection of the musicmix menu item launches a shared music listening activity through which all group members can simultaneously listen to the same music selections. An example musicmix implementation is described in further detail below with reference to FIG. 13.

[0049] Selection of the photomix menu item launches a photo sharing activity through which all group members can simultaneously view and edit one or more photos. An example photomix implementation is described in further detail below with reference to FIGS. 8-11.

[0050] Selection of the voicechat menu item launches a chat activity, similar to a telephone conference call, through which all group members can talk to one another. In an exemplary implementation, a voicechat activity may include mobile and/or non-mobile users.

[0051] Selection of the flix menu item launches a video clip sharing activity via which group members can simultaneously view, comment on, and/or edit short video clips. For example, a mobile user may capture a short video clip using a video-enabled cellular telephone, and then launch flix to share the video clip with other members of a group. Similarly, a user who is connected via a non-mobile device may launch flix to share with a group, a video clip stored on the user's PC hard drive. In an exemplary implementation, video clips shared from a non-mobile device may be compressed or otherwise altered to improve the transfer speed or viewing ability for mobile members of the group.

[0052] Selection of the “games lobby” menu item enables a group member to launch a game in which other members of the group can participate. In an exemplary implementation, a listing of available games, members' scores and trophies may be accessed through the games lobby. In an exemplary implementation, a mobile group member may see a different list of available games than a non-mobile group member. For example, a location-based treasure hunt game may be available to mobile group members, but not available to non-mobile group members.

[0053] Selection of the “group” menu item enables a group member to modify group settings, such as the group name, the group icon, and the group skin. Menu items may also be available that allow a member to invite another individual to join the group, or to enable a group member to remove themselves from the group.

[0054] A group member who is connected to the group via a mobile device can access mobile device user interface group activity menu 606 that corresponds to non-mobile device user interface group activity menu 602. The user may access mobile device user interface group activity menu 606, for example, by pressing a particular button on the mobile device while a particular group icon is selected.

[0055] The menu items displayed in mobile device user interface group activity menu 606 may be the same as, or may differ from, those displayed in non-mobile device user interface group activity menu 602. For example, due to mobile device memory constraints, bandwidth constraints, and/or limited screen size, group activities that are available to a group member that is logged on using a non-mobile device may not be feasible for a group member that is logged on using a mobile device. Accordingly, menu items for those activities may be displayed on non-mobile device user interface group activity menu 502, but not on mobile device user interface group activity menu 506. Similarly, there may be menu items that are available to group members that are logged on using a mobile device that are not available to group members that are logged on using a non-mobile device.

[0056] For example, mobile device user interface group activity menu 606 does not include a “share file” entry because making a file available for others to download from a mobile device may not be practical. However, mobile device user interface group activity menu 606 does include a “send file” entry, selection of which enables the mobile user to send a particular file directly to one or more group members.

[0057] In an alternate implementation, a share file activity may be available from both a mobile device and a non-mobile device, depending, for example, on available bandwidth and memory resources.

[0058] Although not shown, another group activity that may be available is a “push-to-talk” activity that enables a group member to talk with other mobile group members as if using a walkie-talkie. In an exemplary implementation, a “push-to-talk” activity may be available to mobile and non-mobile group members. Alternatively, a “push-to-talk” activity may be available only to mobile group members.

[0059] FIG. 7 illustrates an exemplary implementation of a shared group bubble activity. As describe above with reference to FIG. 6, members of a group, when logged on, may simultaneously send a bubble text message to each member of the group. The right hand side of FIG. 7 illustrates how, according to the illustrated implementation, such a bubble text message 702 may be displayed according to non-mobile device user interface 302.

[0060] Similarly, the same bubble text message, when received by a group member using a mobile device, may also be displayed according to mobile device user interface 350. Bubbles can be thought of as gifts that are sent, and need to be opened. Accordingly, bubble text message notification 704 includes an icon that identifies the group member who sent the bubble text message. When a user selects the bubble text message notification 704 (e.g., by pressing a designated button on the mobile device), bubble text message 706 is displayed. In an exemplary implementation, some bubble templates may be optimized for either mobile or non-mobile devices, while others may be optimized for non-mobile devices. Bubble templates optimized for non-mobile devices may have an associated smaller version that is transmitted to mobile group members when the bubble template is used to send a message.

[0061] FIG. 8 illustrates an exemplary implementation of a shared group photomix activity. As described above with reference to FIG. 6, members of a group, when logged on, may simultaneously view, edit, and comment on one or more photos. The right hand side of FIG. 8 illustrates how, according to the illustrated implementation, such a photomix activity 802 may be displayed according to non-mobile device user interface 302. The particular photo that is being viewed 804 is displayed within the photomix activity window 802.

[0062] Similarly, the same photo that is being viewed by group members through non-mobile device user interface 302 can also be viewed by mobile group members through mobile device user interface 350. In an exemplary implementation, to conserve bandwidth and memory, a photo (or any other image) may be resampled and/or resized (or otherwise altered to make the image smaller) before it is sent to the mobile device. The left side of FIG. 8 illustrates an exemplary display of a group photomix activity 806 through mobile device user interface 350. The image 804 that is being viewed by the group is indicated in the mobile device user interface display of group photomix activity 806 as a highlighted thumbnail 808 of the image. In an exemplary implementation, a mobile group member can switch to a larger view of the image by selecting the highlighted image thumbnail 808.

[0063] FIG. 9 illustrates shared photo editing as can be performed according to a group photomix activity. The right side of FIG. 9 illustrates an exemplary screen display according to a non-mobile device user interface 302. A user can edit the photo 804 currently being viewed by the group, for example, by adding a sticker 902 (i.e., a small graphical element that can be “pasted’ onto an image) or by using a pen tool to draw on the drawing. Any edits made to the image by one group member are automatically visible to the other group members. This is illustrated on the left-hand side of FIG. 9, which represents a mobile device user interface 350 for enabling a group member to participate in a group photomix activity. The sticker 902 that was added by the user of non-mobile device user interface 302 is also visible as sticker 904 to the user of mobile device user interface 350. The group member who is using mobile device user interface 350 may also add stickers, or otherwise edit the photo. For example, sticker 906 may be added to the photo using mobile device user interface 350. After sticker 906 is added, it will automatically be visible to other online group members.

[0064] FIG. 10 illustrates example actions that can be performed in association with a shared image through mobile device user interface 350. The left side of FIG. 10 illustrates a photomix menu 1002 that may be displayed using mobile device user interface 350. Photomix menu 1002 includes selectable menu items that enable a user to update an image, add an image, add a comment to an image, add location information associated with an image, add a border to an image, add stickers to an image, add a vote to an image, save an image, or delete an image. As illustrated in FIG. 10, an image may be acquired from a digital camera, which may be an integrated component of the mobile device, or from an image library, which may be stored on the mobile device or in a separate repository that can be accessed via the mobile device.

[0065] The right side of FIG. 10 illustrates the association of location information with an image. For example, when a user, using a camera phone, takes a photo to share with the group, the user can associate location information with the image to indicate to the other group members where the picture was taken. In an exemplary implementation, location information may be added automatically using a geographic positioning system (GPS) component that is an integrated part of the mobile device. Alternatively, the user may access an online map for which a link can be associated with the image. Additionally, if multiple images are available, each with associated location information, a map may be displayed with the location associated with each image highlighted or otherwise indicated.

[0066] FIG. 11 illustrates an exemplary group voting activity that may be associated with an image. For example, if a mobile group member sees a cute guy and wants her friends to rate him based on how cute they think he is, the mobile group member can take a picture of him, add the photo 1102 to a photomix activity, and then associate a group voting activity with the image. The right side of FIG. 11 illustrates an exemplary non-mobile device user interface display of a photomix image 1102 that has an associated voting activity. In the illustrated example, the photo has an average rating of three out of five stars, and has been voted on by two group members, as indicated by the group member avatars 1104 displayed below the star rating 1106. In an exemplary implementation, a user can see how a particular group member rated the photo by selecting one of the group member avatars 1104. The rating submitted by the user associated with the selected avatar would then be displayed. The left side of FIG. 11 illustrates a corresponding exemplary mobile device user interface display of the same photo and the associated group voting activity.

[0067] FIG. 12 illustrates an exemplary user interface that enables one group member to introduce a third party to another group member. For example, as described above and illustrated with reference to FIG. 11, a group member may take a picture of someone and share that photo with the group. FIG. 12 illustrates an interaction that may take place in a scenario in which one of the group members happens to be friends with the individual in the photo. In the illustrated example, the user of mobile device 1202 (username “Geo”) belongs to another group that includes the individual whose photo was taken and shared. Based on that group connection, Geo may forward a calling card 1204 associated with “RocDa House” (the username of the individual in the photo) that includes personal information that user RocDa House has decided to make public (e.g., a first name and a phone number). In an exemplary implementation a calling card may be sent to a particular individual or to a group, in which case the calling card is sent to each member of the group. A user who receives a calling card may then use that information to invite the individual identified by the calling card to join one or more groups that the user is a member of.

[0068] FIG. 13 illustrates an exemplary mobile device user interface component that enables a shared music experience. In the illustrated example, users of mobile devices 1302 and 1304 are members of the same group and are engaged in a musicmix activity. In an exemplary implementation, the playlist, song state, and background skin are shared, meaning that each group member participating in the musicmix activity hears the same song at the same time, sees the same background, and can select a different song from the same playlist. FIG. 13 also illustrates how a group member (e.g., user of mobile device 1302) can invite another individual (e.g., user of mobile device 1306) to join in the music mix. By inviting an individual from outside the group, if the individual accepts the invitation, they become a member of the group.

Mobile Online Group Interaction Method

[0069] FIG. 14 is a flow diagram that illustrates an exemplary method 1400 for enabling mobile online group interaction. The illustrated process can be implemented in any suitable hardware, software, firmware or combination thereof.

[0070] At block 1402, an application identifies groups in which the user is a member. For example, social group application 214 identifies the groups in which the user is a member.

[0071] At block 1404, the application may filter and/or order group icons associated with the groups in which the user is a member. For example, if screen real estate is limited such that only six group icons can be displayed, but the user belongs to more than six groups, then the icons that are displayed may be associated with those groups the user communicates with most frequently.

[0072] Alternatively, the group icons that are displayed may be associated with those groups for which online members of the group are located geographically closest to the user. In an exemplary implementation, geographic information may be gathered from users who are logged on using a device (mobile or non-mobile) that includes a global positioning system.

[0073] At block 1406, a user interface including one or more group icons is displayed. For example, mobile device 200 displays a user interface 350 associated with social group application 214.

[0074] At block 1408, a connection is automatically established between the mobile device and devices being used by other members of the groups represented by the displayed group icons. For example, a peer-to-peer connection is established between the mobile device and another mobile device being used by another member of a group associated with a displayed group icon, and/or a peer-to-peer connection is established between the mobile device and a non-mobile device being used by another member of a group represented by a displayed group icon. Connections are automatically established between the mobile device and any device (mobile or non-mobile) being used by any other member of any group to which the user of the mobile device is a member.

[0075] A user may then participate in social group interactions over the established connections as enabled by social group application 214.

Conclusion

[0076] The systems and methods described above enable mobile group social interaction. Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.