WO2015175938A1

WO2015175938A1 - Asynchronous auditory messaging facilitation apparatuses, methods and systems

Info

Publication number: WO2015175938A1
Application number: PCT/US2015/031077
Authority: WO
Inventors: Jeffrey Baxter; Thomas GAYNO
Original assignee: Cord Project Inc.
Priority date: 2014-05-15
Filing date: 2015-05-15
Publication date: 2015-11-19

Abstract

The ASYNCHRONOUS AUDITORY MESSAGING FACILITATION APPARATUSES, METHODS AND SYSTEMS (CCS) transforms user cord creation and transmission inputs using CCS components into cord enabled audio messages. A user may utilize an application on a mobile device for the generation and transmission of short audio messages (e.g., Cord messages). Cord messages may be sent to a plurality of users using a streamlined interface. Recipients of a Cord message may be able to respond to the user who sent the cord with a new Cord message. If a user sends a Cord message to several recipients, each recipient may be able to automatically send a response Cord message to all of the users who received the original Cord message. The user may connect a plurality of different types of devices to her account, and the application may automatically sync settings, Cord messages, and/or similar information across all of the specified devices and platforms.

Description

ASYNCHRONOUS AUDITORY MESSAGING FACILITATION APPARATUSES, METHODS AND SYSTEMS CROSS-REFERENCE TO RELATED APPLICATIONS [oooi] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 61/994,052, filed May 15, 2014, and entitled "ASYNCHRONOUS AUDITORY MESSAGING FACILITATION APPARATUSES, METHODS AND SYSTEMS," the content of which is expressly incorporated herein by reference in its entirety. FIELD

[0002] The present innovations generally address the rapid creation, transmission and management of asynchronous auditory message events, and more particularly, include ASYNCHRONOUS AUDITORY MESSAGING FACILITATION APPARATUSES, METHODS AND SYSTEMS. [0003] However, in order to develop a reader's understanding of the innovations, disclosures have been compiled into a single description to illustrate and clarify how aspects of these innovations operate independently, interoperate as between individual innovations, and/or cooperate collectively. The application goes on to further describe the interrelations and synergies as between the various innovations; all of which is to further compliance with 35 U.S.C. §112. BACKGROUND

[0004] Users may desire to communicate with others using technology, but may be frustrated by electronic forms of communication which can be cumbersome, can lack nuance and emotion, and can in some instances limit and prohibit users from effectively communicating with one another. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The accompanying appendices and/or drawings illustrate various non- limiting, example, innovative aspects in accordance with the present descriptions: [0006] FIGURE 1 shows a block diagram illustrating aspects of an exemplary embodiment of a CCS controller, in one implementation of the CCS operation; [0007] FIGURE 2 shows an example data flow illustrating aspects of Cord device registration and account creation, in one implementation of the CCS operation; [0008] FIGURE 3 shows an example data flow illustrating aspects Cord transmission, in one implementation of the CCS operation; [0009] FIGURE 4 shows an example logic flow illustrating aspects of Cord creation, in one implementation of the CCS operation; [0010] FIGURE 5 shows a block diagram illustrating aspects of record orientation audience determination, Cord creation and broadcasting, in one implementation of the CCS operation; [0011] FIGURE 6 shows a screenshot diagram illustrating aspects of viewing a Cord inbox, in one implementation of the CCS operation; and [0012] FIGURE 7 shows a screenshot diagram illustrating aspects of reviewing and favoriting a Cord, in one implementation of the CCS operation. [0013] The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in Figure 1. Reference number 201 is introduced in Figure 2, etc. DETAILED DESCRIPTION CCS

[0014] The ASYNCHRONOUS AUDITORY MESSAGING FACILITATION APPARATUSES, METHODS AND SYSTEMS (hereinafter "CCS" controller) transform audio file data into asynchronous messages, via CCS components, in response to user audio inputs. In some embodiments, this is carried out in real time. The combination of audio recordings and asynchronous messaging can allow users across multiple devices and interfaces (e.g., including iOS, Android, Google Glass, Android Wear, Apple Watch, Microsoft Phone, and/or other operating systems and/or interfaces) to communicate with each other in a meaningful and seamless manner. FIGURE 1 shows a block diagram illustrating embodiments of a CCS controller 125 and a mobile device 105, in one embodiment. For example, in some implementations, a mobile device 105 can be a device including at least one processor 110 and at least one memory 115, such that the memory 115 stores mobile application data and/or other instructions that the processor 110 can use to perform the functionality of a Cord application 120 (described in further detail below), and/or other mobile device functionality. The mobile device 105 can be a mobile phone, a tablet, an Augmented Reality (AR) device, a smartwatch, and/or a similar mobile device. The mobile device 105 can also include an orientation module 150 operatively connected to the at least one processor 110 and at least one of an accelerometer 155, a gyroscope 160, and/or a similar device orientation sensor, and implemented by the at least one processor 110, by a circuit such as an Application- Specific Integrated Circuit (ASIC), and/or by similar hardware. The orientation module 150 can be configured to obtain mobile device orientation data from the accelerometer i55and/or gyroscope 160, and determine an orientation of the mobile device 105 based on the data. The orientation can be used to facilitate broadcasting functionality, as described in FIG. 5. [0015] The mobile device 105 can communicate with the CCS controller 125, e.g., via an internet and/or similar connection to a communications interface 165 at the CCS controller 125 configured to send and/or receive information transmitted via the internet and/or similar connection. The CCS controller 125 can be a server, a cluster of servers, and/or a cloud server configured to handle processing of Cord messages and database records. The communications interface 165 in the CCS controller 125 can be connected to at least one processor 135 operatively connected to various portions of the CCS controller 125, including at least one memory 140, a Cord message creation module 145, and a CCS database 130. In some implementations, the at least one processor 135 can interact with the at least one memory 140 to access processor-readable instructions stored in the at least one memory 140, e.g., including instructions to implement the Cord message creation module 145, to allow querying of the CCS database 130, to create and/or modify database records, and/or to perform other server functions. [0016] In some implementations, the Cord message creation module 145 can be a hardware module (e.g., implemented on a circuit such as ASIC, and/or similar hardware), and/or can be a software module implemented on hardware (e.g., on an ASIC circuit and/or on the at least one processor 135). The Cord message creation module can be configured to access data from the CCS database 130, and to create Cord message records, modify Cord message accounts and/or groups based on created Cord messages, and/or to otherwise process incoming Cord messages. [0017] In some implementations, , the CCS database 130 includes several tables i3oa-d which include records relating to Cord message accounts, Cord message data structures, and/or other information. A user account table 130a includes fields such as, but not limited to: user_ID, user jpassword, user_displayname, user_email, user_location, user_profile_picture, user_type, user_phone_no, user_color, user____.linked_.___.accounts, user___contacts, user_...date, added, and/or the like. The user account table may support and/or track multiple user accounts on a CCS. Cord message table 130b includes fields such as, but not limited to: cord_ID, cord_name, cord_length, cord_audio, eord_datetime, cord_location, cord_reeipients, cord_group, cord_.__ date____.sent, and/or the like. The Cord message table may support and/or track multiple Cord messages on a CCS. A devices table 130c includes fields such as, but not limited to: device_ID, device_name, device_type, device_model, device_OS, device_.___.MAC, device___date___added, device , velocity and/or the like. With respect to device_...velocity, one or both of movement and speed of a user may inform a mode of delivery of a Cord message; for example, if from device_velocity data (e.g., the output of an accelermomenter of a mobile device) it may be deduced that the user is in a car, depending on whether the user is a driver or a passenger may dictate a voice-only Cord message or a delivery mode that could include text. The Devices table may support and/or track multiple devices on a CCS. A groups table i3od includes fields such as, but not limited to: group_ID, group_name, group_users, group_privacy, group_cords, group __date___ added, and/or the like. The groups table may support and/or track multiple user groups on a CCS. [0018 ] FIGURE 2 illustrates various apparatus and information flows for facilitating account creation for audio messaging, according to one embodiment of the present invention. The user 205 may register for a Cord message account 210 via providing account details to a Cord message user interface (e.g., a mobile application, and/or a similar program) implemented on their mobile device 105. Account details may include first and last name, email address, phone number, a display name, a password and/or PIN, a profile picture, and/or other information. [0019 ] In some implementations the user 205 may be encouraged and/ or prompted to create the account from a mobile phone and/or a similar device if the user 205 launches the application on an augmented reality (AR) and/or similar device for the first time. In some implementations the user 205 may also be able to indicate social network and/or other accounts (e.g., Facebook, Twitter, Google, Apple, Microsoft, and/or the like) to link with the created Cord message account, e.g., by providing login credentials for the accounts, and/or by providing permission to send account data to the Cord message account. In some implementations, a user 205 can have a different Cord message account associated with each type of device (e.g., a user account for mobile phones, a user account for AR devices such as Google Glass, a user account for desktop devices, and/or the like), and can link user accounts for each of the device types. [0020] The mobile device 105 may send a request to create a Cord message account 220 to CCS controller 125 configured to process such requests. The CCS controller i2smay create 230 the account for the user using all of the user-provided information, and/or may import information from the user-provided external accounts. The CCS controller 125 may then send a confirmation 235 to the user 205 indicating that the user's Cord message account has been successfully created. [0021] In some implementations, the user 205 may, in order to add contacts to her Cord message account, authorize her account to access the contacts on her mobile device 105 and/or linked accounts 240 in order to add them to her account. The mobile device 105 may generate and send a request to add contacts to the Cord message account 245 to the CCS controller 125. The CCS controller 125 may determine which contacts the user 205 has on her mobile device 105 and/or in her linked accounts have Cord message accounts 250, and may provide the user 205 with a list of contacts 255 which do have Cord message accounts and whom the user 205 may send Cord messages to. In some implementations a user 205 may be able to send Cord messages to users who do not have a Cord message account; such users may be required to register for a Cord message account in order to view the Cord message, may be required to register in order to respond to the Cord message, and/or may be otherwise incentivized to register for a Cord message account. [0022] In some implementations, all users with user accounts can view each other's profiles. Contacts may also be added to a user's contact list by viewing a user's profile and adding them as a contact. Contacts can send messages to each other, create groups together, and/or perform other functions. [0023] When the user 205 receives a Cord message, the Cord message can appear in a Cord message inbox, where each received Cord message can be displayed for the user for a predetermined duration of time (e.g., for a week, until the inbox is filled, and/or the like). Newly received Cord messages can be rendered to appear larger, brighter, and/or more elevated in the Cord message inbox than older Cord messages. Cord messages which the Cord message user has listened to can be rendered to appear faded and/or monochrome, and/or otherwise altered to indicate that they have been reviewed. In some implementations, referring to FIG. 6, a Cord message 605 can be represented by a profile picture 610 of the sender, as well as a border 615 around the profile picture. In some implementations, the thickness of the border can indicate the age of the Cord message, while the length of the border can indicate the length of the Cord message (e.g., in seconds). For example, a Cord message with a thick border encompassing half of the profile picture can indicate that the Cord message is new, and that the length of the Cord message is half the maximum duration for a Cord message. A cord with a thin border encompassing the entire profile picture can indicate that the Cord message is older, and that the Cord message is of a maximum Cord message duration. The color of the border can correspond to profile settings provided by the sender, or can be based on a group theme to which the sender belongs, and/or settings provided by the recipient. In some implementations, the color of the border can also correspond to a color of the device the sender's account is tied to (e.g., if the Cord message user interface detects, based on an identifier of the user's mobile device 105 and/or other information about the user's mobile device 105, that a user is using a red mobile phone, the border color can be red to match the phone's color). [0024] In some implementations, when a Cord message is sent to a group of users, the CCS controller 125 can create a group including each of the users which received the Cord message, as well as the sender of the Cord message. Users in the group can then respond to the Cord message such that all other users in thr group can review the response. For example, the CCS controller 125 can instantiate a group portion of a data store, and/or generate a group data structure in the CCS database 130, and can store the Cord messages generated by the users in the group in the data store, and/or can associate stored Cord messages with the group data structure. Groups can be private groups (e.g., allowing contacts to communicate with each other privately), and/or can be public groups (e.g., allowing any users to communicate with each other, e.g., about particular topics, events, and/or the like). [0025] In some implementations, when a user 205 accesses her Cord message inbox, the Cord messages in her inbox can be automatically played in reverse- chronological order (e.g., newest Cord messages first). In some implementations, the most recent Cord messages may be auto-played, and older messages may not auto-play. In other implementations, a user 205 can select particular Cord messages in her inbox to which to listen, and can have a user interface mechanism (e.g., a button) for auto- playing the entire inbox of Cord messages. The user 205 can also view, from the inbox interface and/or while the user 205 is listening to a Cord message, the usernames of each user who sent a Cord message, when the Cord message was sent, and/or other such information (e.g., see 705 of FIG. 7). In some implementations, the user 205 can perform any of these functions by verbally providing instructions to the Cord message user interface (e.g., providing a vocal command to play all Cord messages in the inbox, to record and/or send a Cord message, to navigate through the user's profile, and/or a profile of another user, and/or the like). [ 0026] FIGURE 3 illustrates various apparatus and information flows for facilitating audio messaging, according to one embodiment of the present invention. For example, in some implementations, a Cord message user can record audio message files (e.g., "Cord messages") which can be sent to other Cord message users, and/or to other contacts of the Cord message user. Each cord can be an audio file which does not exceed a maximum duration (e.g., such as 60 seconds and/or a similar duration). In some implementations the user 305 may be able to generate a Cord message 310 via recording the message with the user's mobile device 105. For example, the user 305 can press and/or hold a record button and/or other user interface element within a Cord message user interface (e.g., such as record button 620 in FIG. 6) rendered on the user's mobile device 105. Pressing the record button can cause the mobile device 105 to start recording, e.g., using a microphone in the mobile device 105. The user 305 can be shown the remaining time the user has to complete the Cord message, and/or the total length of the Cord message as the user is recording the message. The user 305 can be prompted to accept the recorded Cord message and to send the Cord message to one or more recipients, and/or reject the recorded Cord message, and to re-record the Cord message to the user's satisfaction. The user can also provide other instructions, such as delaying delivery of the Cord message to recipients until a predetermined amount of time (e.g., and allowing the user to reject the Cord message within that predetermined amount of time). [0027] The mobile device 105 may then upload the recorded audio message file (e.g., the Cord message) to CCS controller 125 configured to process the Cord message. In some implementations the CCS controller 125 may store the Cord message in CCS database 130. The user 305 may, in tandem with the Cord message being uploaded and stored at the CCS controller 125, and/or before the Cord message is sent to the CCS controller 125, indicate which contacts, if any, the user 305 would like to send the Cord message to 335, and may authorize the application to send the Cord message. In some implementations, contacts can be ranked and/or sorted based on frequency (e.g., contacts which the user sends the most Cord messages to may appear at the top of a contacts list, and/or the like). The user can also specify herself as a contact to which to send a Cord message (e.g., a user can send a Cord message to herself as a personal memo, and/or the like). [0028 ] In some implementations, the user 305 can provide information vocally (e.g., vocally indicating when to start/stop recording, vocally indicating that the user wants to send the Cord message, and/ or vocally indicating which users to send the Cord message to) to the mobile device 105. In other implementations, the user 305 can provide this information via a user interface rendered on a display component of the user's mobile device 105. In some implementations, if the user provides the information vocally, the vocal instructions can be concatenated to the Cord message audio file (e.g., appended to the end of the Cord message file, concatenated as the first portion of the Cord message file, and/or the like), and sent to the CCS controller 125 along with the recorded message as a single audio file. The CCS controller 125 can then divide the Cord message into recorded message, instructions, and recipient portions, and can process the Cord message based on these components. [ 0029 ] The CCS controller 125 may then add metadata to the Cord message record in the CCS database 130 (e.g., additional recipients, the identifier of the sender, date and time of the recording, geolocation it was recorded in, and/or the like), and may associate the Cord message record with the specified recipients. In some implementations if the user 305 did not specify any recipients, the Cord message may instead be associated with the user's account. [0030] The CCS controller 125 may then send a confirmation 350a to the user 305 indicating that the Cord message has been sent to the specified recipients, and a notification 350b to the recipients 355 indicating that they have received the Cord message. In some implementations the notifications may be sent via email, SMS, via a notice (e.g., pop-up, pre-recorded Cord message), and/or other forms of communication. In some implementations, the recipients may not receive a notification, and may see a new Cord message in their application inbox. The CCS controller 125 may also send the Cord message 360 to the recipients, e.g., when the recipients' mobile devices are connected to a network that allows the mobile devices to download the Cord message, and/or the like. [ 0031] Referring to FIG. 7, a recipient of a Cord message 705 can then listen to the Cord message, favorite the Cord message (e.g., select the Cord message for permanent storage, such that the Cord message remains in the user's inbox, and/or a Favorites inbox, as long as the Cord message is marked as a Favorite Cord message), and/or can respond to Cord messages (e.g., by pressing and holding a record button in a user interface, allowing the recipient to generate their own Cord message message and send it to the user who sent the last Cord message the recipient listened to). In some implementations, to favorite a Cord message, a user can select the Cord message, and then vocally provide the command "Favorite," and/or select a Favorite user interface button 710. The user can then see an icon 715 and/or a similar indication showing that the Cord message has been favorited. While the button 710 and the icon 715 are shown in FIG. 7 as a star shape, other shapes may be employed for a "Favorite" icon (e.g., a heart shape). In some implementations, while listening to a Cord message, the border 720 around the Cord message may turn white and/or black, and may serve as a progress bar (e.g., with the color portion of the border 725 corresponding to the amount of the Cord message listened to so far). [0032] In some implementations, rather than a Cord message user generating a Cord message, an electronic device (e.g., a home appliance, a vehicle, and advertisement server, and/or a similar electronic device) can generate Cord message messages to send to a particular user associated with the device. In one example, a dishwasher can generate a Cord message to send to a user connected to the dishwasher device, to inform the user when the dishes have been cleaned. In another example, an advertisement server can generate a Cord message file to send to a number of Cord message users who have shown interest in a particular product and/or type of product, indicating that a product has been newly put on the market, that a product is being sold at a discount, and/or other such information. In other implementations, a user can also send a Cord message to a merchant to authorize the sale of goods and/or services from the merchant. In such implementations, the user can also provide other authentication data (e.g., biometric data obtained via the mobile device 105), and/or can vocally provide authentication data (e.g., a username and/or password, and/or other information) in the Cord message, to facilitate a secure financial transaction between the user and the merchant. [0033] In some implementations, a user can delete Cord messages in her inbox, and/or can allow the Cord message to expire after a predetermined amount of time (e.g., after a number of hours, after a number of days, after the user's inbox has been filled, and/or the like). [0034] FIGURE 4 illustrates a logic flow diagram for facilitating audio messaging, according to one embodiment of the present invention. In some implementations, a user may record an audio clip 405. In some implementations the audio clip may be of a pre- determined maximum length (e.g., 60 seconds). Once the user finishes recording the Cord message 410, the user's mobile device 105 may generate and send a message to the CCS controller i25containing the recorded Cord message 415 and requesting that the CCS controller i25store the Cord message. The CCS controller I25may, after receiving the Cord message 420, store the new Cord message in CCS database 130, e.g. via generating a new Cord message record in the CCS database 130 and storing the audio with the Cord message record. [0035] The user may, after recording, select contacts to send the Cord message to 430 in the user's application. The user's mobile device 105 may then send the recipients, along with any other Cord message metadata 435 (e.g., the date and time the Cord message was recorded, where it was recorded, the Cord message length, and/or the like) to the CCS controller i2sfor processing. In some implementations the user may also be able to review her recording, and re-record the Cord message a plurality of times before selecting recipients to send the Cord message to (in such implementations, the CCS controller i25may receive the updated Cord message recordings and update the Cord message record accordingly while the user selects recipients for the Cord message). [0036] After the CCS controller 125 receives the Cord message metadata 440, the CCS controller 125 may store the Cord message metadata in the Cord message record 445, and may associate the Cord message with the user records associated with the recipients specified by the user. The CCS controller i2smay then send the Cord message to the recipients 450 (optionally sending a notification, e.g., via email or push notification to the users indicating they have received a Cord message), and may send a confirmation to the sender indicating that her Cord message has been sent to the specified contacts 455, e.g., cord confirmation 460. [0037] In other embodiments, one or more Cord messages may be recorded, sent, and played as described herein via the use primarily of audio/voice commands, for example, via devices that are primarily audio input/output devices (e.g., speaker plus microphone, as in a connected headset or other connected devices without a display screen). An audio/voice command implementation facilitiates recording, sending and playing back of Cord messages from vehicles or other environments via display-less devices. [0038] FIGURE 5 shows a block diagram illustrating aspects of record orientation audience determination, Cord message creation and broadcasting, in one implementation of the CCS operation. In one embodiment, a phone may be in an initial orientation, e.g., 501a. The orientation as shown is one which a user normally uses to conduct a phone call using the phone's build in microphone (e.g., when the phone earpiece is held to the user's ear and the user's mouth is therefore proximate to the phone's microphone). In the case of a Cord message, this orientation does not apply only to when the user is recording a Cord message with the phone held proximate to their ear, but any instance where the phone is held in a similar 'upright' manner, such as when the user is holding the phone with the screen facing their face and utilizing the microphone to record a Cord message from a greater distance than that described above. [0039] In one embodiment, a Cord message user interface (e.g., a mobile application running on the user's device) can treat Cord message recorded in this orientation 501a as having an additional indication that the user is sending a private Cord message. For example, when a Cord message recorded by a mobile device 105 in an upright position is sent to CCS controller 125, the Cord message user interface can include mobile device position information, and/or can provide a privacy indication (e.g., that the Cord message is a private Cord message) in addition to other metadata and/or other data associated with the new Cord message. The CCS controller 125 can then determine to whom the Cord message should be accessible, based on the privacy indication and/or the mobile device position information. In other embodiments, a group cord (made up of a plurality of private cords) may also be indicated by this interface. [0040] In one embodiment, the user may turn the device such that they are holding the phone in an "upside down" (e.g., inverted) manner, e.g., 501b, with the microphone pointing up instead of down as in 501a. The mobile device 105 (e.g., via the orientation module) can determine that the orientation of the mobile device 105 has changed to the inverted position. The at least one processor on the user's mobile device 105 can determine a privacy setting for a Cord message (e.g., "broadcast"), based on the orientation, and can then provide this information to the mobile application, and/or to the CCS controller 125, such that the mobile application and/or the CCS controller 125 can use the orientation information, and/or the privacy indication, to determine how to provide the Cord message to other users. In broadcast mode, an audience may initially be determined based on a user setting, user's local to the user's current location, a Twitter feed or other publicly available discussion medium, and/or the like, e.g., 502. Audio filters may be adjusted by the app to couneract the louder tone users may speak in when holding the device in such a manner. Additionally, in some embodiments, the entrance into broadcast mode may automatically initiate recording and thereafter broadcast of the cord to the indicated audience. In some embodiments, the app user interface may flip orientation as well when broadcast orientation is detected, automatically launch a broadcast specific interface, determine nearby cord users, and/or the like. [ 0041] While various inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure. [0042] The above-described embodiments can be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer system ("computer") or distributed among multiple computers. [0043] Further, it should be appreciated that a computer may be embodied in any of a number of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. Additionally, a computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital Assistant (PDA), a smart phone or any other suitable portable or fixed electronic device. [ 0044] Also, a computer may have one or more input and output devices. These devices can be used, among other things, to present a user interface. Examples of output devices that can be used to provide a user interface include printers or display screens for visual presentation of output and speakers or other sound generating devices for audible presentation of output. Examples of input devices that can be used for a user interface include keyboards, and pointing devices, such as mice, touch pads, and digitizing tablets. As another example, a computer may receive input information through speech recognition or in other audible format. [ 0045 ] Such computers may be interconnected by one or more networks in any suitable form, including a local area network or a wide area network, such as an enterprise network, and intelligent network (IN) or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks. [0046] The various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages and/or programming or scripting tools, and also may be compiled as executable machine language code or intermediate code that is executed on a framework or virtual machine. [ 0047] In this respect, various inventive concepts may be embodied as a computer readable storage medium (or multiple computer readable storage media) (e.g., a computer memory, one or more floppy discs, compact discs, optical discs, magnetic tapes, flash memories, circuit configurations in Field Programmable Gate Arrays or other semiconductor devices, or other non-transitory medium or tangible computer storage medium) encoded with one or more programs that, when executed on one or more computers or other processors, perform methods that implement the various embodiments of the invention discussed above. The computer readable medium or media can be transportable, such that the program or programs stored thereon can be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above. [ 0048] The terms "program" or "software" are used herein in a generic sense to refer to any type of computer code or set of computer-executable instructions that can be employed to program a computer or other processor to implement various aspects of embodiments as discussed above. Additionally, it should be appreciated that according to one aspect, one or more computer programs that when executed perform methods of the present invention need not reside on a single computer or processor, but may be distributed in a modular fashion amongst a number of different computers or processors to implement various aspects of the present invention. [ 0049] Computer-executable instructions may be in many forms, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments. [0050] Also, data structures may be stored in computer-readable media in any suitable form. For simplicity of illustration, data structures may be shown to have fields that are related through location in the data structure. Such relationships may likewise be achieved by assigning storage for the fields with locations in a computer-readable medium that convey relationship between the fields. However, any suitable mechanism may be used to establish a relationship between information in fields of a data structure, including through the use of pointers, tags or other mechanisms that establish relationship between data elements. [ 0051J Also, various inventive concepts may be embodied as one or more methods, of which an example has been provided. The acts performed as part of the method may be ordered in any suitable way. Accordingly, embodiments may be constructed in which acts are performed in an order different than illustrated, which may include performing some acts simultaneously, even though shown as sequential acts in illustrative embodiments. [0052] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms. [0053] The indefinite articles "a" and "an," as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean "at least one." [0054] The phrase "and/or," as used herein in the specification and in the claims, should be understood to mean "either or both" of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with "and/or" should be construed in the same fashion, i.e., "one or more" of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the "and/or" clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to "A and/or B", when used in conjunction with open-ended language such as "comprising" can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc. [0055] As used herein in the specification and in the claims, "or" should be understood to have the same meaning as "and/or" as defined above. For example, when separating items in a list, "or" or "and/or" shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as "only one of" or "exactly one of," or, when used in the claims, "consisting of," will refer to the inclusion of exactly one element of a number or list of elements. In general, the term "or" as used herein shall only be interpreted as indicating exclusive alternatives (i.e. "one or the other but not both") when preceded by terms of exclusivity, such as "either," "one of," "only one of," or "exactly one of." "Consisting essentially of," when used in the claims, shall have its ordinary meaning as used in the field of patent law. [0056] As used herein in the specification and in the claims, the phrase "at least one," in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase "at least one" refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, "at least one of A and B" (or, equivalently, "at least one of A or B," or, equivalently "at least one of A and/or B") can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc. [0057] In the claims, as well as in the specification above, all transitional phrases such as "comprising," "including," "carrying," "having," "containing," "involving," "holding," "composed of," and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases "consisting of" and "consisting essentially of" shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03.

Claims

CLAIMS What is claimed is:

1. A processor-implemented method for generating audio messages, comprising:

(A) receiving, from an electronic device, an audio message file; (B) instantiating, via an audio file creation component implemented by a processor, an audio message file record in a database based on the audio message file;

(C) receiving, from the electronic device, a selection of at least one user to which to send the audio message file;

(D) generating audio message file metadata for the audio message file record; (E) storing the audio message file metadata in the audio message file record; and (F) associating the audio message file with the at least one user; and

(G) transmitting a signal to each user in the group of users, the signal including the audio message file.

2. The method of claim l, wherein the electronic device is one of a user mobile device, an appliance, an advertisement server, or a vehicle.

3. The method of claim 1, wherein the selection of at least one user is a selection of at least one user in an address book of the electronic device.

4. The method of claim 1, wherein the audio message file metadata includes at least one of a timestamp of when the audio message file was recorded, geolocation data indicating where the audio message file was recorded, the length of the audio message file, and a privacy setting.

5. The method of claim 1, the method further comprising:

(H) appending the selection of at least one user to the audio message file record.

6. A processor-implemented method for generating audio messages, comprising:

(A) receiving a first auditory command from a user to initiate recording of an audio message file;

(B) recording the audio message file in response to the first auditory command;

(C) receiving a second auditory command from the user to terminate recording of the audio message file;

(D) terminating recording of the audio message file in response to the second auditory command;

(E) receiving a third auditory command including an audio message file command;

(F) receiving a fourth auditory command including at least one recipient; and

(G) when the audio message file command includes a first command:

(Gi) appending the third auditory command and the fourth auditory command to the audio message file, and

(G2) sending a signal to a server, the signal including the audio message file, such that the server sends the audio message file to the at least one recipient.

7. The method of claim 6, wherein the first command is a "send" command.

8. The method of claim 6, further comprising:

(H) when the audio message file command includes a second command:

(Hi) prompting the user to re-record the audio message file.

9. The method of claim 7, wherein the second command is a "reject" command.

10. The method of claim 6, further comprising: (I) receiving a notification from the server when the audio message file has been sent to the at least one recipient.

11. A processor implemented method of initiating a group cord conversation, comprising:

(A) receiving, via a processor, a cord audio message from a cord user at a user device;

(B) querying a cord user data repository at the user device for additional cord users to which to send the cord audio message;

(C) instantiating a group cord conversation interface hosted at a server, wherein the group cord conversation interface accepts selections of additional cord users to the received cord audio message;

(D) copying the received cord audio message into a group cord conversation data store as a first cord conversation in a group cord conversation; and

(E) transmitting the copied cord audio message to the additional cord users.

12. The method of claim n, wherein the user device is a user mobile device.

13. The method of claim 11, wherein the additional cord users are associated to the received cord audio message in response to the cord user selecting the additional cord users at the group cord conversation interface.

14. The method of claim 11, further comprising:

(F) instantiating a notification trigger to inform the cord user of the user device whenever a new group cord conversation cord has been received.

15. An apparatus for broadcasting an audio message file, comprising:

(A) an orientation module implemented with at least one of an accelerometer or a gyroscope, the orientation module configured to determine a device orientation for the apparatus;

(B) a memory storing at least one audio message file; and (C) a processor operatively coupled to the orientation module and the memory, the processor configured to obtain the device orientation from the orientation module, the processor configured to determine a privacy setting for the audio message file stored in the memory based on the device orientation, the processor configured to transmit a signal to a server, the signal including the audio message file and the privacy setting, such that the server transmit the audio message file based on the privacy setting. i6. The apparatus of claim 15, wherein the device orientation is one of "upright" or "inverted". 17. The apparatus of claim 16, wherein the privacy setting is "private" when the device orientation is "upright." 18. The apparatus of claim 16, wherein the privacy setting is "public" when the device orientation is "inverted." 19. The apparatus of claim 18, wherein the audio message file is transmitted to a plurality of messaging users, the plurality of messaging users determined based on at least one of geographic proximity to the apparatus, public broadcasting settings stored in the memory, and participation in a social media discussion feed. 20. The apparatus of claim 17, wherein the audio message file is transmitted to a plurality of messaging users selected based on least one selection by a user of the apparatus. 21. A portable wireless electronic communication apparatus to create, transmit, receive, store and playback a plurality of asynchronous short voice messages, the apparatus comprising:

a user interface including a display device;

a microphone;

a speaker; at least one communication interface to wirelessly transmit a plurality of outbound short voice messages and wirelessly receive a plurality of inbound short voice messages;

a memory to store processor-executable instructions and a plurality of stored inbound short voice messages; and

at least one processor, communicatively coupled to the user interface, the microphone, the speaker, the at least one communication interface, and the memory, wherein upon execution of at least some of the processor-executable instructions, the at least one processor:

A) controls the at least one communication interface to wirelessly receive the plurality of inbound short voice messages;

B) controls the memory to store at least some of the plurality of received inbound short voice messages as the plurality of stored inbound short voice messages;

C) controls the display device to display an inbox graphical user interface (GUI) representing an inbox for at least some of the plurality of stored inbound short voice messages, the inbox GUI comprising a plurality of inbound short voice message indicators and at least one record message indicator;

D) controls the user interface to receive a user message selection of a first inbound short voice message indicator of the plurality of inbound short voice message indicators in the inbox GUI;

E) in response to the user message selection in D), controls the memory and the speaker so as to retrieve and playback a first stored inbound short voice message of the plurality of stored inbound short voice messages corresponding to the selected first inbound short voice message indicator;

F) controls the user interface to receive a user record selection of the at least one record message indicator in the inbox GUI;

G) in response to the user record selection in F), controls the memory and the microphone to record a first outbound short voice message having a duration corresponding to a length of time of the user record selection of the at least one record message indicator; H) upon release of the user record selection of the at least one record message indicator, controls the at least one communication interface to wirelessly transmit the first outbound short voice message to a server;

I) controls the display device to display a contacts GUI representing a plurality of user contacts;

J) controls the user interface to receive at least one user contact selection of at least a first contact of the plurality of user contacts in the contacts GUI to be a first recipient of the first outbound short voice message;

K) in response to the at least one user contact selection in J), controls the at least one communication interface to wirelessly transmit the selection of the first recipient of the first outbound short voice message to the server; and

L) controls the display device and/or the speaker to provide a message sent indicator to indicate the wireless transmission of the first outbound short voice message to the first recipient in response to receiving a send confirmation from the server. 22. The apparatus of claim 21, wherein:

in J) the at least one processor controls the user interface to receive at least two user contact selections of the first contact and a second contact of the plurality of user contacts in the contacts GUI to be the first recipient and a second recipient of the first outbound short voice message; and

in K) the at least one processor controls the at least one communication interface to wirelessly transmit the selection of the first recipient and the second recipient of the first outbound short voice message to the server. 23. The apparatus of claim 22, wherein in C), each inbound short voice message indicator of the plurality of inbound short voice message indicators displayed in the inbox GUI includes a plurality of visual attributes comprising:

a first visual attribute to indicate a sender of a stored inbound short voice message corresponding to the inbound short voice message indicator;

a second visual attribute to indicate a length of the corresponding stored inbound short voice message; and a third visual attribute to indicate that the corresponding inbound short voice message has been previously played back; 24. The apparatus of claim 23, wherein the plurality of visual attributes further comprises:

a fourth visual attribute to indicate that the corresponding inbound short voice message has not been previously played back;

a fifth visual attribute indicating a progress of playback of the corresponding inbound short voice message;

a sixth visual attribute indicating a sent time at which the corresponding inbound short voice message was sent by the sender. 25. The apparatus of claim 21, wherein in K) the at least one processor controls the at least one communication interface to wirelessly transmit the selection of the first recipient of the first outbound short voice message to the server together with first metadata for the first outbound short voice message, the first metadata comprising:

a first identifier for a sender of the first outbound short voice message; a length of the first outbound short voice message;

a send time of the first outbound short voice message; and

a geographic location for the apparatus when the first outbound short voice message was recorded in G). 26. The apparatus of claim 21, wherein in A), an inbound short voice message from the plurality of inbound short voice messages includes metadata, the metadata including:

an identifier for a sender of the inbound short voice message; a length of the inbound short voice message; and

a send time of the inbound short voice message.