Anonymous mobile group communications

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under USC §119(e) of provisional application No. 61/903,927, filed Nov. 13, 2013, entitled “A Process, method, and description for cross-platform (Android, iOS, etc) mobile app to allow people to opt-in for instant and anonymous group text communications with real-time alerts (via push notifications) over a customizable and cloud-virtualized “channel” without having to know/share/disclose a user's mobile phone or email address of anyone in the group”, hereby incorporated by reference herein.

BACKGROUND OF THE INVENTION

I. Field of the Invention

The present disclosure relates generally to telecommunications. More particularly, it relates to wireless communication and devices, especially wireless devices capable of messaging (such as short messaging system (SMS) messaging, and multi-media system (MMS) messaging) and voice communication.

II. Description of the Prior Art

Wireless communications in the form of cellular phones and their supporting communications network have led to changes in the ways that people communicate with one another. For example, SMS transport is a service commonly available on mobile devices for the purpose of sending short messages between such mobile devices. This service is commonly referred to as “text messaging”. Typically, the messages comprise a few characters of text, the precise number depending on a particular encoding scheme used by the SMS implementation. Such conventional messaging technologies permit all parties (i.e. sender and recipient(s)) to a text message to specifically identify an originating party (e.g. device, web page, etc.) upon which the text message has been transmitted, and any recipient party (e.g. device, web page, etc.) upon which the text message is received. More particularly, conventional messaging technologies permit each party interacting via messaging to obtain identification credentials (e.g. IP addresses, mobile numbers, etc.) for every other party interacting therewith.

Another example of such wireless communications is the so-called Common Short Code (CSC). A CSC is a short code which is common across many wireless service providers in the United States. It is basically the inter-carrier for mobile applications. All CSCs are 5 or 6 digits in length (as compared to a 10 digit telephone number) and can be either random or select. A short code is a number to which an SMS or text message can be sent. A short code may be specific to one mobile operator or “common” and supported by all major mobile operators. In its simplest form, a CSC allows a company to effectively market and communicate with individuals; and also allows those individuals to engage and interact with a brand. For example, CSCs allow consumers to interact and communicate by sending a text message to a company's mobile application that may include voting, polling, gaming, coupons, and payments, among other applications. By way of example, a retailer that desires a personal cell phone number of a customer, might solicit that customer's text “Jack” (or something else) to 22343 (or some other number) for a coupon. While the CSC system may be advantageous under certain circumstances, one major disadvantage of the system is the costs involved.

In many group situations, individuals want to be instantly alerted/notified on their mobile device. Such situations may include, for example, emergencies, important announcements, instant coupons, events, etc. However, in many of these same group situations, many individuals would prefer to remain anonymous and maintain the privacy of their personal contact information.

Email and so-called Social networks (e.g. FaceBook, Twitter and Instagram) are not a valid solution. Such networks tend to be checked leisurely and are typically filled with non-urgent content. Additionally, millions of mobile phone users still refuse to adopt social networking as they deem it childish, unprofessional and/or distracting. Furthermore, there options still require signing in, registering, giving out personal contact information, etc. Accordingly, whether the user of a mobile device is utilizing email, a social network, SMS, CSC, or any other messaging system, anonymity is not possible.

There are, of course, numerous reasons in which users may want to keep their identity unknown during text messaging. For the one doing the transmitting, a user may desire to remain anonymous during texting of opinion, suggestion, complaint, or perhaps even reporting a crime. Additionally, a user may desire to transmit an anonymous donation or other charity. Furthermore, a business may desire to send a message containing an anonymous reminder, advertisement, discount, coupon, etc. Turning to the receiving side, it is often desirable to receive communications and other information without providing or disclosing user identification (e.g. cellular telephone number, email address, etc.). In other words, people want to receive the communication but do not want to sacrifice their personal information. The only way to currently remain somewhat anonymous during text messaging is to use a complicated system that intercepts the message (e.g. SMS, email, etc.) following message transmission, and substituting an anonymous/fake source address for the real source address originally supplied therein. This is accomplished through the use of an anonymous communication module that performs intercept and address substitution. However, this system needs initial personal identifiers to initiate communication between users.

There remains no system that can anonymously broadcast and receive such communications without the necessity of providing identifying personal information. Accordingly, there exists a need for such a system to both eliminate the necessity of obtaining such information and thereby creating a distribution list on the sending side; and to eliminate the necessity of providing identification information on the receiving side.

It is a general object of this disclosure to provide systems, methods and apparatuses for addressing the deficiencies of the current practices regarding issues associated with mobile group communications and the like.

It is a general object of this disclosure to provide systems, methods and apparatuses that are simple, easy to use and familiar for mobile group communications.

It is another general object of this disclosure to provide cost effective systems, methods and apparatuses in mobile group communications.

It is more specific object of this disclosure to provide systems, methods and apparatuses in mobile group communications while maintaining privacy and anonymity.

It is another more specific object of this disclosure to provide systems, methods and apparatuses for mass group messaging in mobile group communications while eliminating distribution lists.

It is yet another specific object of this disclosure to provide systems, methods and apparatuses in mobile group communications for efficient mobile advertising.

A further object of this disclosure is to provide systems, methods and apparatuses in mobile group communications to effectively disseminate important or urgent information to group members.

Yet a further object of this disclosure is to provide systems, methods and apparatuses that allow customization of messages and message channels in mobile group communications.

Yet another further object of this disclosure is to provide systems, methods and apparatuses that allow users to choose to receive messages by joining message channels in mobile group communications.

A further object of this disclosure is to provide anonymity and group broadcasting capabilities that replace the archaic SMS short code technology.

These and other objects, features and advantages of this disclosure will be clearly understood through a consideration of the following detailed description.

SUMMARY OF THE INVENTION

According to an embodiment of the present disclosure, there is provided a system for establishing communication between a transmitter and one or more personal communication devices where the transmitter does not need to know the address or any other identifying indicia of any of the personal communication devices, the system includes a server to establish a designated communication channel and multiple personal communication devices for transmitting and receiving information to the channel, and application on each of the personal communication devices that permits the selection of the channel and enables reception of messages transmitted such that the personal communication devices can receive and review messages transmitted to the channel without the transmitter having to know any identifying indicia of the user of any device.

There is also provided a mobile group communications system for use with personal communication devices and a network, the system having a server capable of receiving and transmitting communications through the network and a database containing information representing each of a plurality of personal communication devices, a first user personal communication device establishing a virtual communication channel within the system for broadcasting messages and a second user personal communication device joining the channel without requiring user contact information whereby the first user broadcasts a message through the channel and the second user receives the message.

There is also provided a mobile group communications application for use with personal communication devices and a network, the application having unique code-words associated with each personal communication device and a server capable of differentiating multiple users of the application by the code-words, a database associating the code-word with a channel of communication and having a distribution list of multiple code-words for each channel whereby when a personal communication device sends a message on a channel a copy of the message is sent by the server through the network to each code-word on the list.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be more fully understood by reference to the following detailed description of one or more preferred embodiments when read in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout the views and in which:

<figref idrefs="DRAWINGS">FIG. 1</figref> is illustrative of a communication network environment in which preferred embodiments of the anonymous mobile group communications system of the present disclosure are implemented.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a simplified logistic diagram of the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 3</figref> is an application flow diagram of the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a series of personal communication device (PCD) screen shots illustrating introductory information of the anonymous mobile group communications system of the present disclosure after initial application download.

<figref idrefs="DRAWINGS">FIG. 5</figref> is a PCD screen shot illustrating a home screen of the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 6<i>a </i></figref>is a series of PCD screen shots illustrating the creation of a channel within the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 6<i>b </i></figref>is a series of PCD screen shots illustrating the creation of a channel within the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 7</figref> is a series of PCD screen shots illustrating a process of selecting a channel icon.

<figref idrefs="DRAWINGS">FIG. 8</figref> is a PCD screen shot illustrating a quick response (QR) code for a selected channel.

<figref idrefs="DRAWINGS">FIG. 9</figref> is a PCD screen shot illustrating initiation of a newly created channel.

<figref idrefs="DRAWINGS">FIG. 10</figref> is a PCD screen shot illustrating a process of sharing a channel.

<figref idrefs="DRAWINGS">FIG. 11<i>a </i></figref>is a series of PCD screen shots illustrating channel settings.

<figref idrefs="DRAWINGS">FIG. 11<i>b </i></figref>is a series of PCD screen shots illustrating channel settings.

<figref idrefs="DRAWINGS">FIG. 12</figref> is a series of PCD screen shots illustrating private communications between users of the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 13</figref> is a series of PCD screen shots illustrating the joining of a channel within the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIG. 14</figref> is a PCD screen shot illustrating the scan of the QR code for a selected channel.

<figref idrefs="DRAWINGS">FIG. 15</figref> is a PCD screen shot illustrating information regarding a selected channel.

<figref idrefs="DRAWINGS">FIG. 16</figref> is a series of PCD screen shots illustrating a process of user authorization.

<figref idrefs="DRAWINGS">FIG. 17</figref> is a PCD screen shot illustrating general information about the anonymous mobile group communications system of the present disclosure.

<figref idrefs="DRAWINGS">FIGS. 18<i>a</i>-<i>c </i></figref>illustrate the backend logic flow diagram of the coding of the anonymous mobile group communications system of the present disclosure.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the disclosure, its application or use. These exemplars are merely used to better describe the true spirit and scope of the present disclosure.

The present anonymous mobile group communications system allows users to easily send and/or receive urgent or important information or updates through group messages via PCDs. Such PCDs may include, but are not limited to, smartphones, tablets, personal computers, other computers, and the like. The group message may alert (i.e. sound, vibrate, etc.) in the same manner new messages alert users in the conventional text messaging environment. In general, those who want to broadcast (i.e. Broadcasters) their messages to a group receive a group identification or channel number from the system administrator or host. The Broadcaster then shares the channel number with the intended group of those whom may want to receive or listen (i.e. Listeners) to the messages. In its simplest form, Listeners may tune-in to any channel they want to receive messages from, much like a conventional radio. In fact, all Users are by default anonymous unless they choose not to be.

<figref idrefs="DRAWINGS">FIG. 1</figref> is a schematic overview diagram of the communication network and computing environment in which the preferred embodiments are implemented. The preferred mobile group communication system <b>10</b> includes one or more servers <b>12</b>, Broadcasters <b>14</b>, Listeners <b>16</b> and other users <b>18</b>, linked together using a network <b>20</b>, such as a cellular network. The network <b>20</b> may be comprised of any network known in the art for mobile communications. Alternatively, there may be separate and different networks between components. Further, because the preferred embodiment of the network <b>20</b> is a cellular network, there can be a huge number of participants, including Broadcasters (Broadcaster_n), Listeners (Listener_n), other users (User_n), together with the Channels (Channel_n) they may be utilizing, simultaneously.

The servers <b>12</b> include database and database interfaces known in the art. The server <b>12</b>, through its database, keeps current, accurate information about the users of the service, e.g., Broadcasters and Listeners, and their respective Channels <b>22</b>. Information is preferably stored in a non-volatile storage system, such as one or more hard disk drives, used by the server <b>12</b> for storage. The server may load data from the storage system into volatile memory when processing. It is envisioned that the management system <b>10</b> will utilize multiple servers <b>12</b> at different physical locations to help ensure safety and security. It is further envisioned that the management system <b>10</b> may utilize off-site remote server services, such as a dynamic virtual private server (e.g. cloud server). In any event, the server <b>12</b> may comprise one or more separate computer systems to run the different components of the mobile group communication system <b>10</b>. Further, in accordance with known technology, the management system <b>10</b> is enabled to create virtual channels <b>22</b> to enable unidirectional and/or bidirectional communication between, for example, Broadcasters and Listeners using standard protocols. For example, the server can create a virtual channel data path for mobile transmitting and mobile receiving devices to utilize to permit a path of communication between the transmitting and receiving devices. Accordingly, the server is capable of receiving and transmitting communications with the databases and otherwise.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a simplified logistic flow diagram <b>24</b> of the mobile group communications system of the present disclosure. In particular, once the system software and code (the application or so-called “app”) is downloaded and installed on the user PCD <b>26</b>, the new user either creates <b>28</b> a channel or joins <b>30</b> an existing channel. If the new user is creating a channel, he initializes the channel settings <b>32</b> and can then send messages <b>34</b> to his group. If the new user is joining a channel, he adds the desired group <b>36</b> and gets alerted <b>38</b> of any new messages.

Turning now to <figref idrefs="DRAWINGS">FIG. 3</figref>, the app flow diagram <b>40</b> of the anonymous mobile group communications system of the present disclosure will be more particularly described. Upon app install <b>42</b>, there are preferrably numerous onboarding or app introductory <b>44</b> PCD screens that introduce the new user to the application before negotiating the user to the home screen <b>46</b>. From the home screen <b>46</b>, the user can go to a channel <b>48</b>, create a channel <b>50</b>, join a channel <b>52</b>, scan a QR code <b>54</b> and/or review information <b>56</b> about the app. From the create channel <b>50</b> screen the user can go to the home screen <b>46</b>, incorporate a photo or icon <b>58</b>, go directly to a channel <b>48</b> and scan a QR code <b>54</b>. From the join channel <b>52</b> screen the user can go to the home screen <b>46</b> or go directly to a channel <b>48</b>. Finally, from the channel screen <b>48</b> the user can go to the home screen <b>46</b>, apply particular channel settings <b>58</b> or share <b>60</b> the channel.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a series of PCD screen shots illustrating introductory information (onboarding <b>44</b>) of the anonymous mobile group communications system of the present disclosure after initial app download. Such information may include, for example, i) broadcast text notifications to any size group without knowing recipients phone number or email address—no social network account required; ii) invite others to join your customized channel—its free and anonymous—no login or registration required <b>64</b>; iii) instantly notify your group of any urgent notifications via text message <b>66</b>; iv) send and receive messages from favorite groups and/or organizations, anonymously; and v) anyone (businesses, clubs, teams, retailers, individuals, etc.) who wants to communicate or stay in touch can take advantage of this app. Basically, the application provides a new way of group message communications. It allows users to anonymously join any number of desired group channels without logging in, registering, or sharing their contact information with anyone else on that channel. It allows users to easily start their own group channel and relieves them from manually collecting or requiring anyone's cell phone number or email address to communicate. Channels can be used for broadcasting alerts, notifications, or any type of messages. They can be made public or private, and can be used for one-way or two-way broadcast communicating. Channels can be added, deleted, silenced or de-activated at any time. Once the user scrolls through these onboarding screens, by selecting “Next” <b>72</b>, they are prompted to select “Get Started” <b>74</b>, which brings them to the app home screen <b>46</b>.

The application home screen <b>46</b>, as illustrated in <figref idrefs="DRAWINGS">FIG. 5</figref>, is typically the main screen used, and allows the user to navigate through many of the features/functions of the app. More particularly, if the user desires to create <b>50</b> a new channel, he selects the create icon <b>76</b>. If the user desires to join <b>52</b> an existing channel, he selects the join channel icon <b>78</b>. The channels that the user is already associated with are also listed <b>80</b> the home screen <b>46</b>. Any channel (<b>80</b><i>a</i>-<b>80</b><i>e</i>) listed here may be selected, and the user will navigate directly to the desired channel. The home screen <b>46</b> further includes icons <b>82</b>,<b>84</b> to navigate to Scan QR <b>54</b> and About <b>56</b>, respectively.

The process by which a channel is created <b>50</b> will now be more particularly described as illustrated in <figref idrefs="DRAWINGS">FIGS. 6<i>a </i>and 6<i>b</i></figref>. At the initial screen <b>86</b>, the user (Broadcaster) selects whether he wants to create a private <b>88</b> or a public <b>90</b> channel. A private channel <b>88</b> is a channel that requires a password and only users who know the password can add the channel to their respective channel list and join. If the Broadcaster desires to create his channel as a private channel, he will be prompted to create a password <b>92</b> for his Listeners to be able to join. If the Broadcaster creates a public channel, the password <b>92</b> select option is inoperable. Additionally, the password can be changed (or even eliminated, thereby making it a “public” channel) by the Broadcaster at any time via the settings menu.

In any event, once the channel type has been selected, the Broadcaster selects “Continue” <b>94</b> and proceeds to the type of messaging screen <b>96</b>. From here, the Broadcaster selects one way <b>98</b> or two way <b>100</b> messaging. One way <b>98</b> channels allow only the Broadcaster to send messages and the Listeners are only able to receive and not respond. Two way <b>100</b> channels allow the Listeners to respond and send messages. Should the Broadcaster choose a one way <b>98</b> channel he will proceed to the privacy screen <b>102</b> upon selecting Continue <b>94</b>. Should the Broadcaster choose to create a two way <b>100</b> channel he will further be prompted to choose whether Listeners can respond only to the Broadcaster <b>104</b> or to everyone <b>106</b> Listening to the channel at the two way selection screen <b>108</b> before Continuing <b>94</b> to the privacy screen <b>102</b>.

At the privacy screen <b>102</b>, the Broadcaster next selects how he wants to appear to members of his group chat or channel. In particular, if he wants to remain anonymous, and simply be known as BROADCASTER, he selects the anonymous icon <b>110</b> and then Continue <b>94</b> will navigate him to the channel description screen <b>112</b>. However, if he selects Usemame <b>114</b>, he will need to create a Usemame <b>116</b> so that his followers will know him by his name. After which Continue <b>94</b> will navigate to the description screen <b>112</b>. Once at the description screen, the Broadcaster can choose how he wants to display his channel to help users locate it. For example, channel name <b>118</b>, and channel description <b>120</b> may be entered and a category <b>122</b> may be chosen. If the Broadcaster desires to choose a category, category screen <b>124</b> may provide any number of choices <b>126</b> (i.e. Retail, School, Sports, etc.) or simply “Other” <b>128</b>. Once a category is selected, the Broadcaster is navigated back to the description screen <b>112</b>, selects Continue <b>94</b> and moves on to the Add A Photo screen <b>130</b>.

In the event the Broadcaster does not want to include a photo or other icon to display along with the channel information, he simply selects Continue <b>94</b> and moves on to the Registration screen <b>132</b>. However, if the Broadcaster desires to include a photo/icon, the Add Photo icon <b>134</b> will navigate him to the process of selecting as illustrated by <figref idrefs="DRAWINGS">FIG. 7</figref>. The initial choice screen <b>136</b> provides the choices of either taking a new photo <b>138</b>, choosing a photo <b>140</b> or canceling <b>142</b> back to the Add a photo screen <b>130</b>. If he chooses to take a photo, he will be navigated to the take photo screen <b>144</b> wherein his PCD can take a photo <b>146</b> or cancel <b>148</b> back to the initial choice screen <b>136</b>. After the photo has been taken, it can be cropped <b>150</b> in any manner used by the PCD and the Broadcaster can either use it <b>152</b> as the channel icon or retake <b>154</b> it. If he chooses to use it, flow goes back to the Add a photo screen <b>130</b> and Continues <b>94</b> to Registration <b>132</b>. If he wants to Retake <b>154</b>, then he is navigated back to the take photo screen <b>144</b>.

Turning back to the initial choice screen <b>136</b> of <figref idrefs="DRAWINGS">FIG. 7</figref>, if the Broadcaster desires to Choose a Photo <b>140</b> from his PCD, he will be navigated to the particular photo collections <b>156</b> library of his PCD. The Broadcaster can then make a selection, camera roll <b>158</b>, for example, wherein that particular selection screen <b>160</b> provides photos to be chosen. Once a photo is selected <b>162</b> it can be cropped <b>164</b> in any manner used by the PCD and the Broadcaster can either Choose it <b>166</b> and navigate back to the Add a photo screen <b>130</b> to Continue <b>94</b> to Registration, or he can cancel <b>168</b> back to the selection screen <b>160</b>.

Once at the Registration screen <b>132</b>, the Broadcaster simply needs to provide an email address <b>170</b> to the system administrator. This address will not be provided to the Listeners, but will be used only to maintain administrative privileges in the event that the Broadcaster switches PCDs. N other words, the Broadcaster would not be able to recover administrative privileges by simply rejoining the particular channel because his privileges would be limited to an ordinary user (Listener). The email address simply provides the system with the ability to promote the user's new PCD back to Broadcaster status for those channels in which he was the administrator. In any event, once registration is completed, Continue <b>94</b> navigates to the confirmation screen <b>172</b>. At the confirmation screen the channel number <b>174</b>, channel name <b>176</b> and channel password <b>178</b> (if applicable) are displayed. The Broadcaster can either select the Show QR Code icon <b>180</b> or the Start Broadcasting <b>182</b> icon. If he selects Show QR <b>180</b>, then the QR Code screen <b>184</b> for the particular channel is presented, see <figref idrefs="DRAWINGS">FIG. 8</figref>. Anyone that has downloaded the app and wants information on the particular channel can then simply scan the code <b>186</b>. If the Broadcaster selects the Start broadcasting icon <b>182</b> from the confirmation screen <b>172</b> he navigates to the newly created channel screen <b>188</b>.

From the channel screen <b>188</b>, <figref idrefs="DRAWINGS">FIG. 9</figref>, the Broadcaster can begin to send messages via the dialog box <b>190</b> to his Listeners. He is further capable of deleting <b>192</b> Listener responses (if any), deleting <b>194</b> a Listener from his channel and flagging <b>196</b> a response (if any). Further icons on the channel screen <b>188</b> may include sharing <b>198</b> the channel, channel settings <b>200</b> and private messaging <b>202</b> capabilities.

The process of sharing a channel is illustrated by the PCD screen <b>204</b> of <figref idrefs="DRAWINGS">FIG. 10</figref>. While it is up to the Broadcaster to spread the existence of his channel to his desired group of listeners via word of mouth, flyers, social networking, school announcements, etc., the app also provides ways to share. The Broadcaster can share his channel in numerous ways, including for example, email <b>206</b>, SMS text <b>208</b>, social media <b>210</b> or by showing the channel QR Code <b>212</b> (as previously discussed with respect to <figref idrefs="DRAWINGS">FIG. 8</figref>).

Referring back to <figref idrefs="DRAWINGS">FIG. 9</figref>, if the User, whether a Broadcaster or a Listener selects the setting icon <b>200</b> he is navigated to the channel settings process of <figref idrefs="DRAWINGS">FIGS. 11<i>a </i>and 11<i>b</i></figref>. If the User is a Listener, the Listener settings screen <b>214</b> allows him to toggle the channel to Mute <b>216</b> the channel turn Off <b>218</b> the channel and even delete <b>220</b> the channel from his listing. Muting disables notifications and alerts, and Off stops all messages and updates. The Listener can also select to show the channel QR Code <b>222</b> (previously discussed <figref idrefs="DRAWINGS">FIG. 8</figref>) and/or select to change/create a Usemame <b>224</b>. The Usemame screen <b>226</b> allows either a Broadcast or a Listener to enter text <b>228</b> to create.

When a Broadcaster selects the settings icon <b>200</b> from <figref idrefs="DRAWINGS">FIG. 9</figref>, he is directed to the Broadcaster settings screen <b>230</b>. The Broadcaster settings screen <b>230</b> includes selections already described in the Listener settings screen <b>214</b>; namely Mute <b>216</b>, Off <b>218</b>, Delete <b>220</b>, QR Code <b>222</b> and Username <b>224</b>; together with additional Broadcaster selections. The Broadcaster may desire to change some settings that he already provided, namely the channel name <b>232</b> where he would be directed to the channel name screen <b>234</b> for edits, the channel photo/icon <b>236</b> where he would be directed to the channel icon screen <b>236</b>, the channel description <b>238</b> where he would be directed to the channel description screen <b>240</b>, and the channel messaging direction <b>242</b> where he would be directed to the communication direction screen <b>244</b>. The promote channel selection <b>246</b> brings the Broadcaster to the promotions screen <b>248</b> wherein he is presented with numerous options <b>250</b> by which to promote his channel. Such promotions will be administered through the backend of the system via the system administrator. These promotions may include, for example, becoming a featured channel, advertising the channel to random Users, adding the channel to the next number of application installations, and/or access to backend administrative data including analytics, etc.

Turning back to the channel screen <b>188</b> of <figref idrefs="DRAWINGS">FIG. 9</figref>, if the Broadcaster selects the private messaging icon <b>202</b> he is directed to the private chat list screen <b>252</b>, see <figref idrefs="DRAWINGS">FIG. 12</figref>. The chat list screen <b>252</b> displays a listing <b>254</b> of all the active users on the channel. The Broadcaster can then either scroll through the listing <b>254</b> and select the appropriate User to private message or select the search icon <b>256</b>. The search icon will navigate the Broadcaster to the search screen <b>258</b> wherein he can enter the name in the text box <b>260</b>. In any event, once the User is selected the private chat screen <b>262</b> opens and dialog begins. Just as with the typical text message, text is entered in the dialog box <b>264</b> and the send icon <b>266</b> is selected to send the message. The Broadcaster also has the option of changing settings via settings icon <b>268</b>, which will bring him to the chat settings screen <b>270</b> where he can allow the User to send messages back to the Broadcaster or to the entire channel via respective toggle icons <b>272</b>, <b>274</b>. The user can also be deleted from the channel through the delete user selection <b>276</b>.

Referring back to <figref idrefs="DRAWINGS">FIG. 9</figref> once more, if the User is a Listener and he wants to private chat with the Broadcaster, the private chat icon <b>202</b> is selected and he is navigated to the Listener private chat screen <b>278</b> of <figref idrefs="DRAWINGS">FIG. 12</figref>. Again, just as with the typical text message, text is entered in the dialog box <b>280</b> and the send icon <b>282</b> is selected to send the message. When the Listener is done and wants to return to the channel, channel icon <b>284</b> is selected.

The application features of the present disclosure have thus far mostly been described as they relate to the User being a Broadcaster. The features relating to the User being a Listener are just as advantageous and will now be further described. Referring back to the home screen <b>46</b> of <figref idrefs="DRAWINGS">FIG. 5</figref>, when the User desires to join a channel via the join channel icon <b>78</b>, he is navigated to the join channel screen <b>286</b> of <figref idrefs="DRAWINGS">FIG. 13</figref>. Channels may be listed <b>288</b> on the join channel screen <b>286</b> by any number of ways, be it Featured, Popular, New, etc.; a toggled selector <b>290</b> may further scroll through these or other categories. A channel may also be scanned via scan icon <b>292</b>. This scanning can be accomplished both in the real world (e.g. display or decal near a point of sale) as well as being shown on another user's phone. If the user desired to scan a channel, the scan icon <b>292</b> will navigate him to the scan QR screen <b>294</b> of <figref idrefs="DRAWINGS">FIG. 14</figref>. Once a proper channel QR Code has been scanned, the channel information relating to that channel will be displayed via a channel information screen <b>296</b>, see <figref idrefs="DRAWINGS">FIG. 15</figref>. Furthermore, the Listener can always simply join a channel upon the opening of a link that may have been shared via email, text and/or social media, etc.

Referring back to the join channel screen <b>286</b>, the User may also search for a channel through the search selector <b>298</b>. The search screen <b>300</b> then allows the User to enter text <b>302</b> and search for channels. Users can search by keyword, channel name, channel number, etc. A search results screen <b>304</b> lists the results <b>306</b> of the search.

Channel information, <figref idrefs="DRAWINGS">FIG. 15</figref>, may be accessed at numerous points throughout the flow of the joining a channel process. For example, particular channel information <b>48</b> may be selected from the home screen <b>46</b>, from the join channel screen <b>286</b> and from the search results screen <b>304</b>. Similarly, join channel icons <b>308</b> allow the user to join the channel from numerous locations throughout the process. For example, from the join channel screen <b>286</b>, the search results screen <b>304</b> and the channel information screen <b>296</b>. If the Broadcaster of the particular channel requires a password, the User will be directed to the password screen <b>310</b> of <figref idrefs="DRAWINGS">FIG. 16</figref> wherein a password will need to be entered in the password box <b>312</b> and the join icon <b>314</b> selected. The user will then be directed to the Usemame screen <b>316</b> wherein he will have the opportunity to provide a Usemame <b>318</b> before continuing <b>320</b> back to the channel. In any event, once a user joins a particular channel, he becomes a Listener of that channel and will receive messages from that channel's Broadcaster.

The user of the application is able to access information relative to the application by selecting the About icon <b>84</b> from the home screen <b>46</b>. The about screen <b>322</b>, <figref idrefs="DRAWINGS">FIG. 17</figref>, provides the user the opportunity to go back to the onboarding process <b>324</b>, optional registration <b>326</b>, and/or various system and administrative options <b>328</b>.

It will be appreciated that unlike most applications, the application of the present disclosure does not employ a mandatory login or registration feature upon installation in order for a user to join a channel. Instead, the application ties a unique token to a particular PCD. In the event the user gets a new PCD, they simply need to rejoin all of their channels of interest again. Optionally, they can use the system's “optional login” mechanism <b>326</b> through the About 84 menu of <figref idrefs="DRAWINGS">FIG. 17</figref>. This allows the user the option to create an account, and therefor the ability to recover all of their channels should they obtain a new PCD.

Once downloaded and set up on the User's phone, the app is instantly opened and the Broadcaster can type and send small, simple ASCII notifications to their groups. The Broadcaster can send active links that open a browser, attach pre-recorded pictures or video clips as well. Listeners will be alerted/notified via push notifications if any of their subscribed (joined) channels have unread information.

The possible uses of the app has no end. It can be used by small organizations (e.g. principals, teachers, club members, coaches, etc.) or larger companies (e.g. private corporations, sports stations, news stations, etc.) to disseminate and communicate information efficiently, without having to obtain or maintain the end user's (Listener's) contact information. Users can simply add and “tune-in” to any of the “channels” they want to get their announcements from.

By way of example, a second grade teacher can send out a broadcast on her channel informing parents that tomorrow is a minimum day and that the money for next week's field trip is due on Friday. For convenience, she can attach a permission slip to remind parents to sign and return. Similarly, a soccer coach can send out a broadcast on his channel and advise parents where/when the next soccer game is being played and ask for a response from the mom who signed up for snack duty. For fun, he can attach a video clip of the winning shot from last week's soccer match.

The app can be used for social and sporting events by notifications regarding game times, locations, cancellations, reminders, reunions, event coordination, etc. It can be used for education and religious information by notifications regarding classroom news, field trips, reminders, homework, study groups, club announcements, campus emergencies, bible study, church announcements, etc. It can be used for community and government purposes by notifications regarding blackouts, neighborhood watch, buss/trolley times, bulletin board, local police/fire/Amber/news alerts, etc. It can be used for retail and business by notifications regarding coupons/ads, real estate, marketing, corporate announcements, business meetings, restaurants, etc. It is envisioned that further localized or specialized uses will occur. For example, a group chaperone that is taking a group of students on a field trip can use the app to quickly communicate with all of the students at the same time (i.e. “bus will be here at 7 pm”). There are virtually unlimited numbers of markets and social ecosystems in which anonymous mobile group communications system of the present disclosure can be implemented.

It will be appreciated that the flow of the app in use, as previously described, may be altered without deterring from the scope of this disclosure. Such use of the app has been shown and described from both a Broadcaster and a Listener perspective. It has been shown that the iOS and Android app utilizes virtual channels (running on a cloud based service) with databased-driven queries and remote push notifications to allow broadcast text communications that alert user PCD akin to SMS text messaging.

Turning now to <figref idrefs="DRAWINGS">FIGS. 18<i>a</i>-<i>c</i></figref>, the backend logic of the system, and the coding (software) by which the app works, will now be briefly described. <figref idrefs="DRAWINGS">FIG. 18</figref> shows the software coding flow <b>330</b> of the application capable of running on any PCD system platform. The code flow has been written for current major system platforms, specifically the so-called iOS system and the so-called Android system. Furthermore, the backend system uses a service to interface to the Apple Push Notification Service (APNS) and Google Cloud Messaging Service (GCM) to distribute the push notification text messages to the appropriate users in teal-time.

When a user first downloads the application, the backend server creates a unique token or code-word that is used to identify the user and the device they are using. This token is bound by the user's operating system (i.e. Apple iOS, Google Android, etc.) profile so if the application is re-downloaded the token remains the same. The token is preferably derived by an algorithm that uses a physical hardware component (e.g. phone UDID) and a software component as well. This token is used by the backend to retrieve channels, preferences and private/public messages. If the user provides an email address or any other identifying information, it may be encrypted before it is stored in the database.

After initial application download and installation to the user's PCD, <figref idrefs="DRAWINGS">FIG. 18</figref> illustrates the backend logic of the system. In particular, when the user accesses application <b>332</b>, the system performs an initial request <b>334</b> for all user channels and provides a listing <b>336</b> thereof and waits for user list action <b>338</b>. Should the user desire to create <b>340</b> a channel, the channel parameters are set <b>342</b> (including whether the channel will be private, and require a password, or public), validated <b>344</b>, a new channel created <b>346</b>, and channel messages <b>348</b> are displayed to the user. When a new channel is created a unique code is generated by the system to identify the channel for quick searching. This code is never duplicated and preferably uses a hashing protocol to reduce sequential channel numbers.

When a Broadcaster creates a channel, there is a database that associates the Broadcaster's token with that new “virtual” channel. A virtual channel is basically a new database entry. Initially the database is 1-to-1 since nobody else has yet joined the channel. When users start joining as Listeners to that channel, their token gets added to the distribution list of the new database entry, so that the database becomes a one-to-many type relationship. When the Broadcaster sends a message, the backend system sends a copy of the message to each user (Listener) that is on the distribution list (i.e. each user that has a token associated with that channel). It will be appreciated that should the messages be private (not public), they are only distributed to one particular user.

Turning back to the user list action <b>338</b>, should the user desire to search <b>350</b> for a channel and channels are found <b>352</b>, then the user selects <b>354</b> the desired channel and the system determines whether the selected channel requires a password <b>356</b>. If it does, there is a password prompt <b>358</b> and a subsequent password validation <b>360</b> before the channel is added <b>362</b> to the user's account and channel messages <b>348</b> are displayed. If there is no password requirement, the channel is simply added <b>362</b> to the user's account and channel messages <b>348</b> are displayed. When a user joins a channel, their token is added to the channel list. If the user removes the channel, the token is kept but flagged as removed. This allows the user to re-join the channel and keep their count. Users with channel tokens flagged as removed will not see the channel in their list or receive any notifications.

Turning once more back to the user list action <b>338</b>, should the user desire to simply open <b>364</b> a channel, that channel's messages <b>348</b> are displayed. The system then provides a number of channel actions <b>366</b> for the user. For example, a user may send a public message <b>368</b> including any number of details <b>370</b>. Once validated <b>372</b>, the message is sent and displayed at the channel messages <b>348</b>. The user may also desire to send a private message <b>374</b>, in which case a private message list <b>376</b> will be displayed and the system will determine the private option action <b>378</b> dependent upon whether the private message is to be generated from an existing user <b>380</b> or a new user <b>382</b>. If from an existing user, the system displays the user's private messages <b>384</b> and provides the option <b>386</b> of either selecting <b>388</b> and displaying <b>390</b> messages or searching <b>392</b> for a user. If the user desires to search, then the system displays <b>394</b> and validates <b>396</b> the search before displaying <b>390</b> any messages.

Referring back to the private option action <b>378</b>, if from a new user <b>382</b>, the system displays the channel user list <b>398</b> and provides the channel user options <b>400</b> of either views <b>402</b> the new user list and onto the private message list <b>376</b> or send a message <b>404</b>. If the user is going to send a message, the message details <b>406</b> are validated <b>408</b> and displayed <b>390</b>. Once messages are displayed <b>390</b> the system provides the messages options <b>410</b> for the continued sending <b>412</b> of private messages.

Each message sent is sanitized and validated by the system to prevent any cross-site scripting attacks or injection attacks. If a message fails validation the user is prompted about the failure. All messages are stored in a one-too-many relationship database schema. If the channel allows for private messaging the user can create a sub-channel for one on one communication with another channel user. The process creates a new channel record that can be accessed through the parent channel. Private channels cannot be seen by other users in the parent channel. Users are able to search for other user nicknames within the private channel. Finally, users are able to share a channel with their friends/family/contacts via social media or native SMS callbacks. These functions register with the server when called to log channel activity.

Turning back again to where the system provides channel actions <b>366</b> for the user. Rather than send messages, the system also allows the user to select channel <b>414</b> or message <b>416</b> options to either change channel options <b>418</b> or change message options <b>420</b> respectively. Whichever change is called for, the system will check the user's privileges <b>422</b> before proceeding to the option group action <b>424</b> where either the Listener (User) options are updated <b>426</b> and validated <b>428</b> or the Broadcaster options are updated <b>428</b> and validated <b>430</b> before proceeding to channel messages <b>348</b>.

It will be appreciated that an application coordinator and/or system host can be a third party and that the account coordinator or system host can receive compensation for acting as the account coordinator or system host. For example, a third party account coordinator or system host can charge Broadcasters a fee per message sent. Alternatively, for example, the app is initially free of charge until after a fixed amount of time, group size, or frequency of messages is achieved. In another alternative example, Listeners are always free to use the app, but the system host will allow Listener purchases within the app.

Broadcasters may want their own channel name, and not a random channel number provided by the system administrator. In such a situation, Broadcasters can be charged a premium for their company name, similar to purchasing a domain name.

Additionally, the app can be used as a supplement/substitute for online purchases between individual buyers and sellers (e.g. Craigslist, etc.). The buyer and seller each open a broadcast channel that they share with one another and then can communicate without ever disclosing their phone numbers. The system host will then manage the transaction and receive a percentage of the transaction as compensation therefore.

The foregoing detailed description has been given for clearness of understanding only and no unnecessary limitations should be understood therefrom. Accordingly, while one or more particular embodiments of the disclosure have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made therein without departing from the invention if its broader aspects, and, therefore, the aim in the appended claims is to cover all such changes and modifications as fall within the true spirit and scope of the present disclosure.