US20210144109A1 - Bot group messaging using general voice libraries - Google Patents
Bot group messaging using general voice libraries Download PDFInfo
- Publication number
- US20210144109A1 US20210144109A1 US17/152,393 US202117152393A US2021144109A1 US 20210144109 A1 US20210144109 A1 US 20210144109A1 US 202117152393 A US202117152393 A US 202117152393A US 2021144109 A1 US2021144109 A1 US 2021144109A1
- Authority
- US
- United States
- Prior art keywords
- bot
- group
- user
- message
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 claims abstract description 61
- 230000008569 process Effects 0.000 claims abstract description 31
- 238000012545 processing Methods 0.000 claims abstract description 14
- 230000002708 enhancing effect Effects 0.000 claims 2
- 238000012795 verification Methods 0.000 description 18
- 230000004044 response Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012552 review Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000006854 communication Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000009977 dual effect Effects 0.000 description 3
- 238000012358 sourcing Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 241000238558 Eucarida Species 0.000 description 1
- 230000002730 additional effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 239000003990 capacitor Substances 0.000 description 1
- 230000009193 crawling Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000035755 proliferation Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/02—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/61—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G10—MUSICAL INSTRUMENTS; ACOUSTICS
- G10L—SPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
- G10L15/00—Speech recognition
- G10L15/26—Speech to text systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/403—Arrangements for multi-party communication, e.g. for conferences
Definitions
- An internet Bot also known as web robot, WWW robot or simply bot, is a software application that runs automated tasks (scripts) over the internet.
- bots perform tasks that are both simple and structurally repetitive, at a much higher rate than would be possible for a human alone.
- the largest current use of bots is in web spidering or web crawling, in which an automated script fetches, analyzes and files information from web servers at many times the speed of a human. More than half of all web traffic is made up of bots.
- Some bots communicate with other users of internet-based services, via Instant Messaging (IM), Internet Relay Chat (IRC), or another web interface such as Facebook Bots and Twitterbots. These chatterbots may allow people to ask questions in plain English and then formulate a proper response. These bots can often handle many tasks, including reporting weather, zip-code information, sports scores, converting currency or other units, etc. Others are used for entertainment, such as SmarterChild on AOL Instant Messenger and MSN Messenger. An additional role of IRC bots may be to lurk in the background of a conversation channel, commenting on certain phrases uttered by the participants (based on pattern matching). This is sometimes used as a help service for new users, or for censorship of profanity.
- IM Instant Messaging
- IRC Internet Relay Chat
- General-purpose bots such as Amazon's Alexa, Microsoft's Cortana, Google's Assistant, and Apple's Siri, are digital personal assistants able to provide a wide range of consumer-oriented voice-activated services, including turning lights on/off, controlling appliances, playing requested music from services such as Pandora or Spotify, providing requested information, or ordering products or services.
- bot messaging With increasing interest in bot-based platforms and internet ease of use, it is desirable to create a new generation of messaging services that allow groups of users to interact with both user-oriented bots as well as group-oriented bots.
- the present disclosure provides advantages for bot environments. Methods, apparatuses, and computing systems are provided for bot messaging.
- a method may include one or more of receiving, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including recorded audio, a message address and a first group identifier, and determining that the group includes a bot, the bot including a software application for performing one or more tasks over the internet.
- the method may also include selecting a voice library to process the recorded audio, processing, by the selected voice library, the recorded audio to produce enhanced text, determining whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and sending, by the group messaging service, the enhanced text to the determined user bot or group bot.
- a non-transitory computer readable storage medium configured to store computer instructions that when executed cause a processor to perform one or more of receiving, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including encoded recorded audio, a message address, and a first group identifier, and determining that the group includes a bot, the bot including a software application for performing one or more tasks over the internet.
- the processor also performs selecting a voice library to process the encoded recorded audio, processing, by the selected voice library, the encoded recorded audio to produce enhanced text, determining whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and sending, by the group messaging service, the enhanced text to the determined user bot or group bot.
- a computing system includes one or more of a storage system including program instructions and a processing system, operably coupled to the storage system.
- Program instructions when executed by the processing system are directed to receive, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including encoded recorded audio, a message address and a first group identifier, and determine that the group includes a bot, the bot including a software application for performing one or more tasks over the internet.
- the program instructions are further directed to select a voice library to process the encoded recorded audio, process, by the selected voice library, the encoded recorded audio to produce enhanced text, determine whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and send, by the group messaging service, the enhanced text to the determined user bot or group bot.
- FIG. 1 illustrates a group messaging system in accordance with embodiments of the present disclosure.
- FIG. 2 illustrates a messaging flow for configuring a bot into a group in accordance with embodiments of the present disclosure.
- FIG. 3 illustrates a flowchart of a bot messaging process in accordance with embodiments of the present disclosure.
- FIG. 4 illustrates a messaging flow for a user node in accordance with embodiments of the present disclosure.
- FIG. 5A illustrates a shared bot entry within a data structure in accordance with embodiments of the present disclosure.
- FIG. 5B illustrates a per-user bot entry within a data structure in accordance with embodiments of the present disclosure.
- FIG. 6 illustrates messaging using a shared bot with a commercial service in accordance with embodiments of the present disclosure.
- FIG. 7 illustrates messaging using a per-user bot with a commercial service in accordance with embodiments of the present disclosure.
- FIG. 8 illustrates a flowchart of a messaging process using shared or per-user bots in accordance with embodiments of the present disclosure.
- FIG. 9 illustrates a bot system architecture in accordance with a first embodiment of the present disclosure.
- FIG. 10 illustrates a bot system architecture in accordance with a second embodiment of the present disclosure.
- FIG. 11 illustrates a flowchart of a bot architecture message flow process using voice libraries in accordance with embodiments of the present disclosure.
- FIG. 12 illustrates a representative computing device in accordance with embodiments of the present disclosure.
- FIG. 1 illustrates a group messaging system 100 in accordance with embodiments of the present disclosure.
- Group messaging system 100 includes at least user nodes 108 and a group messaging service 104 .
- the group messaging service 104 includes one or more computers or servers that facilitate communication between user nodes 108 .
- Each user node 108 includes at least a mobile device 112 , including smart phones, PDAs, or certain wearable computers.
- user nodes 108 include a wearable pendant 116 for wireless bidirectional audio communication with the mobile device 112 .
- user nodes 108 do not include a wearable pendant 116 .
- the wireless bidirectional communication protocol uses Bluetooth LE.
- Mobile device 112 may also include one or more embedded or downloadable software applications that facilitate audio communication between the wearable pendant 116 and other user nodes 108 or the group messaging service 104 .
- User nodes 108 may be organized into one or more groups 120 , where each group 120 includes at least one user node 108 .
- groups 120 are present in the group messaging system 100 , identified as group 1 120 A and group 2 120 B.
- Group 1 120 A includes three user nodes 108 , identified as user node A 108 A, user node B 108 B, and user node C 108 C.
- Each of the three user nodes 108 in group 1 120 A includes a wearable pendant 116 .
- Group 2 120 B also includes three user nodes 108 , identified as user node A 108 A, user node D 108 D, and user node E 108 E.
- User node A 108 A and user node D 108 D each include a wearable pendant 116 , while user node E 108 E does not include a wearable pendant 116 . In the absence of a wearable pendant 116 , the user for user node E 108 E communicates with the mobile device 112 E as they would with any smart phone or similar mobile device 112 .
- both group 1 120 A and group 2 120 B include user node A 108 A.
- a given user node 108 may be in none, one, or any number of groups 120 .
- Multiple groups 120 may include different user nodes 108 , or exactly the same user nodes 108 . There is no limit to the association between user nodes 108 and groups 120 .
- messages 124 are sent wirelessly and through the internet between the communicating user nodes 108 and the group messaging service 104 .
- Messages 124 include recorded audio (a recorded message) as well as an ID of the sending user node 108 and a group ID for the destination group the message is being delivered to.
- the group messaging service 104 receives the message 124 , identifies the group ID associated with the message 124 , looks up the user nodes 108 contained within the destination group 120 , and transmits the message 124 including the ID of the sending user node 108 to each of the user nodes 108 in the destination group 120 .
- the user of user node B 108 B wanted to send a message 124 to group 2 120 B
- the user of user node B 108 B would speak into the wearable pendant 116 and identify group 2 120 B as the destination for the message 124 while speaking the audio for the message into the wearable pendant 116 .
- An application on mobile device 112 B would then create a message 124 including recorded audio as described above and send the message 124 to the group messaging service 104 .
- the software application on the mobile device 112 B would have been previously configured with the group messaging service 104 .
- the group messaging service 104 would then receive, analyze, and transmit the message 124 to each of the user nodes in group 2 120 B as described earlier.
- each of the users of user node A 108 A, user node D 108 D, and user node E 108 E would receive and hear the audio for the message 124 sent by the user of user node B 108 B.
- Use of groups 120 as described herein does not preclude sending messages 124 directly from one user node 108 to a different user node 108 .
- FIG. 2 illustrates a messaging flow for configuring a bot 208 into a group 120 in accordance with embodiments of the present disclosure.
- System 200 includes one or more groups 120 as described with reference to FIG. 1 , a group messaging service 104 , and one or more existing bots 204 .
- Bots 208 are software applications for performing one or more tasks over the internet. Therefore, bots 208 are internet-connected and in most embodiments are separate from the group messaging service 104 .
- Bots 208 may be incorporated into groups 120 by configuring each bot 208 in the group messaging service 104 in a similar fashion to user nodes 108 .
- Group messaging service 104 includes data structures 212 for specifying which user nodes 108 and bots 208 are in each group 120 .
- Each such data structure 212 includes identifiers and addresses for each user node 108 and bot 208 entity in the data structure 212 .
- Group messaging service 104 in group messaging system 200 includes two group data structures 212 , identified as group 1 data structure 212 A and group 2 data structure 212 B.
- Data structure 212 A includes identifiers and addresses for each of the user nodes 108 in group 1 120 .
- data structure 212 A includes a user node A 108 A address and identifier, a user node B 108 B address and identifier, and a user node C 108 C address and identifier.
- Data structure 212 B includes a user node A 108 A address and identifier, a user node D 108 D address and identifier, and a user node E 108 E address and identifier.
- Group messaging service 104 may include any number of data structures 212 , and a given bot 208 may be included in any number of data structures 212 .
- Data structures 212 may include service IDs or identifiers for any user nodes 108 , as well. Service IDs may be anything, including a user name, and email address, or anything else that uniquely identifies a user or user node 108 .
- a user of a user node 108 initiates adding a bot 208 to a group 120 .
- a user in group 1 120 A sends a configuration message 220 to the group messaging service 104 through the application on a corresponding mobile device 112 requesting a specific bot 208 C the user has identified be added to group 1 120 A.
- the user may not have the address of the requested bot 208 C, but is at least able to uniquely identify the requested bot 208 C. It is assumed that multiple existing bots 204 may be available to be messaged, and in the example of FIG. 2 , bots 208 A, 208 B, and 208 C are available.
- a system administrator associated with the group messaging service configures 224 data structure 212 A to route messages to or from bot 208 C.
- a bot 208 C address and identifier is added to data structure 212 A for group 1 .
- the system administrator may need to obtain information associated with bot 208 C in order to configure data structure 212 A.
- the system administrator sends a configuration message (not shown) to the group 1 120 A user that sent the request 220 to add bot 208 C to group 1 120 .
- bot 208 C is configured into group 1 120 A along with user nodes 108 A, 108 B, and 108 C and ready to receive messages from any user node 108 in group 1 120 A.
- Group messaging service 104 also includes a process 216 for sending messages to a bot 208 configured in a group 120 .
- FIG. 3 illustrates a flowchart of a bot messaging process 216 in accordance with embodiments of the present disclosure.
- the bot messaging process 216 allows a user node 108 to send a message 124 to a bot 208 in a group 120 .
- a user node 108 may send and receive messages to and from the bot 208 through the group messaging service 104 .
- Flow begins at block 304 .
- the group messaging service 104 receives a message 124 from a user node 108 in a group 120 .
- the message 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if the message 124 is intended to be sent to a bot 208 ), and an identifier of the user node 108 sending the message 124 .
- Flow proceeds to decision block 308 .
- the group messaging service 104 determines if there is a bot 208 configured in the group 120 corresponding to the destination group identifier. If there is a bot 208 configured in the group 120 corresponding to the destination group identifier, then flow proceeds to decision block 316 . If there is not a bot 208 configured in the group 120 corresponding to the destination group identifier, then flow instead proceeds to block 312 .
- the group messaging service 104 has determined that a bot 208 is not configured in the group 120 corresponding to the destination group identifier, and therefore sends the received message 124 to the user nodes 108 within the destination group 120 .
- Addresses for the user nodes 108 within the destination group 120 are determined by reviewing the data structure 212 within the group messaging service 104 corresponding to the destination group 120 .
- Flow ends at block 312 or the group messaging service 104 returns to block 304 to wait for a next received message 124 .
- the group messaging service 104 determines if the received message 124 should be sent to a specific bot 208 .
- the group messaging service 104 reviews the data structure 212 corresponding to the destination group 120 , and identifies a bot entry 504 corresponding to the bot identifier in the received message 124 .
- a data structure 212 may include any number of bot entries 504 . If there is a match, and a bot entry 504 in the data structure 212 matches the bot identifier, then flow proceeds to block 320 . If there is not a match, and no bot entries 504 in the data structure 212 matches the bot identifier, then flow instead proceeds to block 312 .
- the group messaging service 104 has identified a match between the received message 124 and the data structure 212 corresponding to the destination group 120 , and sends the message 124 to the selected bot 208 .
- the message 124 has been delivered to the addressed bot 208 , and the addressed bot 208 carries out one or more functions corresponding to recorded audio within the message 124 .
- the bot 208 provides a data or audio acknowledgment back to the group messaging service 104 , and in turn the group messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent the original message 124 or the group 120 that includes the user node 108 that sent the original message 124 .
- flow proceeds to block 312 and the group messaging service 104 sends the message 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent the original message 124 .
- FIG. 4 illustrates a messaging flow 400 for a user node 108 in accordance with embodiments of the present disclosure.
- the present invention allows users and user nodes 108 to send messages 124 through a group messaging service 104 to one or more bots 208 , and have the one or more bots 208 perform various tasks related to the functionality of the one or more bots 208 .
- bots 208 may provide enhanced functionality beyond providing information back to a requesting user node 108 .
- a bot 208 may be associated with one or more commercial services 404 that may allow purchase, sale, or other financial or more complex transactions.
- Bot 208 may parse message inputs to determine service handles corresponding to specific commercial services 404 .
- commercial services 404 may be associated with different user accounts, for example an account associated with a specific user or user node 108 and another account associated with a group 120 . In order to utilize such commercial services 404 , it is generally necessary to configure the commercial service 404 with various information 408 related to the user and user node 108 sourcing the transaction.
- the commercial service 404 is configured at least with a user ID and a user address or IP address corresponding to a user and user node 108 who intends to use the commercial service 404 .
- the commercial service 404 is further configured with other information 408 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information.
- user node C 108 C sends a message 124 specifying bot 208 C to the group messaging service 104 .
- the group messaging service 104 identifies bot 208 C is a valid recipient of the message 124 , and forwards the message 124 to bot 208 C.
- Bot 208 C is associated with commercial service 404 , and passes along information within the message 124 to the commercial service 404 .
- the commercial service 404 verifies the information within the message 124 by comparing it to information 408 within the commercial service 404 that has previously been configured.
- commercial service 404 sends a message 412 to user node C 108 C requesting service verification.
- an application on mobile device 112 C receives and displays the service verification 412 to the user, and the user verifies the transaction through the application.
- the application replies to the service verification 412 and sends a reply back to the commercial service 404 , where the requested transaction is then executed and acknowledged.
- the service verification 412 and reply are sent through a different messaging channel than messages 124 that go through the group messaging service 104 .
- the service verification 412 and reply are sent through the same messaging channel than messages 124 that go through the group messaging service 104 .
- FIG. 5A illustrates a shared bot entry 504 A within a data structure 212 A in accordance with embodiments of the present disclosure.
- Data structures 212 may be configured one of two ways, depending on desired bot 208 performance within a group 120 .
- data structure 212 A includes a bot entry 504 A that designates bot 208 C as a shared bot 208 .
- Shared bot entry 504 A includes a bot address 508 A and a bot identifier or ID 512 A.
- a shared bot 208 is identified by a group 120 designation within the bot entry 504 A.
- the group messaging service 104 treats the corresponding bot 208 (bot 208 C) as a shared bot within the corresponding group 120 (group 1 , as shown).
- FIG. 5B illustrates a per-user bot 208 within a data structure 212 A in accordance with embodiments of the present disclosure.
- Data structures 212 may be configured one of two ways, depending on desired bot 208 performance within a group 120 .
- data structure 212 A includes a per-user bot entry 504 B that designates bot 208 C as a per-user bot 208 .
- Per-user bot entry 504 B includes a bot address 508 B and a bot identifier or ID 512 B.
- a per-user bot 208 is identified by a user or user node 108 designation within the bot entry 504 B.
- the group messaging service 104 treats the corresponding bot 208 (bot 208 C) as a dedicated bot 208 to a corresponding user or user node 108 (user C, as shown).
- FIG. 6 illustrates messaging using a shared bot 208 with a commercial service 404 in accordance with embodiments of the present disclosure.
- the present invention allows users and user nodes 108 to send messages 124 through the group messaging service 104 to one or more shared bots 208 , and have the one or more shared bots 208 perform various tasks related to the functionality of the one or more shared bots 208 .
- shared bots 208 are bots 208 assigned to a specific group 120 instead of a specific user or user node 108 . Any user node 108 within a group 120 may send a message to a shared bot 208 configured within the same corresponding group's data structure 212 A, and the group messaging service 104 will respond accordingly. Otherwise, the group messaging service 104 will send a notification to the requesting user or user node 108 that the shared bot 208 is currently not assigned to the group 120 of the requesting user or user node 108 .
- Data structure 212 A includes one or more shared bot entries 504 A. Data structure 212 A may also contain both shared bot entries 504 A and per-user bot entries 504 B. Each shared bot entry 504 A includes a bot address 508 A and a bot identifier or ID 512 A.
- Group messaging service 104 includes a process 604 , shown in more detail in FIG. 8 , that selects a specific shared bot entry 504 A corresponding to the message 124 , and sends a message specifying the group ID 612 to the selected shared bot 208 . It should be understood that the shared bot 208 , and the commercial service 404 if applicable, provides a response to the group messaging service 104 at least related to completion of the requested task in the message 612 . The group messaging service 104 would then provide a notification to each of the user nodes 108 in the requesting group 120 A.
- shared bots 208 may provide enhanced functionality beyond providing information back to a requesting user node 108 .
- a shared bot 208 may be associated with one or more commercial services 404 that may allow purchase, sale, or other financial or more complex transactions.
- the commercial service 404 it is generally necessary to configure the commercial service 404 with various information 608 related to the group 120 and user node 108 sourcing the transaction.
- the commercial service 404 is configured at least with an account ID, an ID corresponding to the group 120 , and an IP address corresponding to the group 120 for the user nodes 108 whose users intend to use the commercial service 404 .
- the commercial service 404 is further configured with other information 608 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information.
- a user node 108 in group 1 120 A sends a message 124 specifying shared bot 208 to the group messaging service 104 .
- the group messaging service 104 identifies shared bot 208 is a valid recipient of the message 124 , and forwards the message 124 to shared bot 208 .
- Shared bot 208 is associated with commercial service 404 , and passes along information within the message 124 to the commercial service 404 .
- the commercial service 404 verifies the information within the message 124 by comparing it to information 608 within the commercial service 404 that has previously been configured for the group 120 .
- the group messaging service 104 and data structure 212 A may be configured to forward all messages 124 from group 1 120 A to a specific bot 208 , without the specific bot 208 being explicitly addressed. In this way, a specific bot 208 may be effectively monitoring all conversations within group 1 120 A between user nodes 108 of group 1 120 A, and acting upon predetermined identified audio within each recorded message 124 .
- commercial service 404 sends a message to one or more user nodes 108 of the corresponding group 120 requesting service verification. For example, for improved security it may be beneficial to provide user verification for a financial transaction that may have impacts to financial accounts associated with the group 120 .
- an application on mobile devices 112 in the group 120 receives and displays the service verification to the user(s), and the user(s) verify the transaction through a mobile device 112 application. The application then replies to the service verification and sends a reply back to the commercial service 404 , where the requested transaction is then executed and acknowledged.
- the service verification and reply are sent through a different messaging channel than messages 124 that go through the group messaging service 104 .
- the service verification and reply are sent through the same messaging channel than messages 124 that go through the group messaging service 104 .
- FIG. 7 illustrates messaging using a per-user bot 208 with a commercial service 404 in accordance with embodiments of the present disclosure.
- the present invention allows users and user nodes 108 to send messages 124 through the group messaging service 104 to one or more per-user bots 208 , and have the one or more per-user bots 208 perform various tasks related to the functionality of the one or more per-user bots 208 .
- per-user bots 208 are bots 208 assigned to a specific user or user node 108 instead of a group 120 .
- Any user node 108 within a group 120 may send a message 124 to a per-user bot 208 configured within the corresponding group's data structure 212 A, and the group messaging service 104 will process the message to the per-user bot 208 if the per-user bot 208 is configured to the sending user or user node 108 C. Otherwise, the group messaging service 104 will send a notification to the requesting user or user node 108 that the per user bot 208 is currently not assigned to the requesting user or user node 108 .
- Data structure 212 A includes one or more per-user bot entries 504 .
- Data structure 212 A may also contain both shared bot entries 504 A and per-user bot entries 504 B.
- Each per-user bot entry 504 B includes a bot address 508 B and a bot identifier or ID 512 B.
- Group messaging service 104 includes a process 604 , shown in more detail in FIG. 8 , that selects a specific per-user bot entry 504 A corresponding to the message 124 , and sends a message specifying the user ID 708 to the selected per-user bot 208 .
- the per-user bot 208 provides a response to the group messaging service 104 at least related to completion of the requested task in the message 708 .
- the group messaging service 104 would then provide a notification to the user node 108 C that sent the original message 124 .
- per-user bots 208 may provide enhanced functionality beyond providing information back to a requesting user node 108 C.
- a per-user bot 208 may be associated with one or more commercial services 404 that may allow purchase, sale, or other financial or more complex transactions.
- the commercial service 404 it is generally necessary to configure the commercial service 404 with various information 704 related to the user and user node 108 C sourcing the transaction.
- the commercial service 404 is configured at least with an account ID, an ID corresponding to the user or user node 108 C, and an IP address corresponding to the user node 108 C whose user intends to use the commercial service 404 .
- the commercial service 404 is further configured with other information 704 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information.
- user node 108 C sends a message 124 specifying per-user bot 208 to the group messaging service 104 .
- the group messaging service 104 identifies per-user bot 208 is a valid recipient of the message 124 , and forwards the message 124 to per-user bot 208 .
- Per-user bot 208 is associated with commercial service 404 , and passes along information within the message 124 to the commercial service 404 .
- the commercial service 404 verifies the information within the message 124 by comparing it to information 704 within the commercial service 404 that has previously been configured for the user and user node 108 C.
- the group messaging service 104 and data structure 212 A may be configured to forward all messages 124 from a specific user node C 108 C to a specific bot 208 , without the specific bot 208 being explicitly addressed.
- a specific bot 208 may be effectively monitoring all conversations from user node C 108 C between user nodes 108 of group 1 120 A, and acting upon identified audio within each recorded message 124 from user node C 108 C.
- commercial service 404 sends a message to user node 108 C requesting service verification.
- an application on mobile device 112 of user node 108 C receives and displays the service verification to the user, and the user verifies the transaction through the mobile device 112 application.
- the application replies to the service verification and sends a reply back to the commercial service 404 , where the requested transaction is then executed and acknowledged.
- the service verification and reply are sent through a different messaging channel than messages 124 that go through the group messaging service 104 .
- the service verification and reply are sent through the same messaging channel than messages 124 that go through the group messaging service 104 .
- FIG. 8 illustrates a flowchart of a messaging process 604 using shared or per-user bots 208 in accordance with embodiments of the present disclosure.
- the bot messaging process 604 allows a user node 108 to send a message 124 to either a shared bot 208 or a per-user bot 208 in a group 120 .
- a user node 108 may send and receive messages 124 to and from the bot 208 through the group messaging service 104 .
- Flow begins at block 804 .
- the group messaging service 104 receives a message 124 from a user node 108 in a group 120 .
- the message 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if the message 124 is intended to be sent to a bot 208 ), and an identifier of the user node 108 sending the message 124 .
- Flow proceeds to decision block 808 .
- the group messaging service 104 determines if there is a bot 208 configured in the group corresponding to the destination group 120 identifier. If there is a bot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow proceeds to decision block 812 . If there is not a bot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow instead proceeds to block 832 .
- the group messaging service 104 determines if the received message 124 should be sent to a specific shared bot 208 .
- the group messaging service 104 reviews the data structure 212 corresponding to the destination group 120 , and identifies a shared bot entry 504 A corresponding to the bot identifier in the received message 124 .
- a data structure 212 may include any number of shared or per-user bot entries 504 A/ 504 B. If there is a match, and a shared bot entry 504 A in the data structure 212 matches the bot identifier, then flow proceeds to decision block 816 . If there is not a match, and no shared bot entries 504 A in the data structure 212 match the bot identifier, then the received message should be sent to a per-user bot 208 and flow instead proceeds to decision block 824 .
- the group messaging service 104 determines if the message 124 qualifies.
- a qualified message 124 is a message with content that conforms with a bot entry 504 A/ 504 B in the data structure 212 .
- the message 124 since there is a bot 208 involved (decision block 808 ) and the bot 208 is a shared bot 208 (decision block 812 ), the message 124 must be sent by a user node 108 in the same data structure 212 as the shared bot 208 . Therefore, a qualified user node 108 has transmitted the message 124 and is able to have the message 124 sent to the shared bot 208 . If the message qualifies, then flow proceeds to block 820 . If the message does not qualify, then flow instead proceeds to block 832 .
- the group messaging service 104 has identified a match between the received message 124 and the data structure 212 corresponding to the destination group 120 , and sends the message 124 to the selected shared bot 208 .
- the message 124 has been delivered to the addressed shared bot 208 , and the addressed shared bot 208 carries out one or more functions corresponding to recorded audio within the message 124 .
- the shared bot 208 provides a data or audio acknowledgment back to the group messaging service 104 , and in turn the group messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent the original message 124 or the group 120 that includes the user node 108 that sent the original message 124 .
- flow proceeds to block 832 and the group messaging service 104 sends the message 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent the original message 124 .
- the group messaging service 104 determines if the message 124 qualifies.
- a qualified message 124 is a message with content that conforms with a bot entry 504 A/ 504 B in the data structure 212 .
- the message 124 since there is a bot 208 involved (decision block 808 ) and the bot 208 is a per-user bot 208 (decision block 812 ), the message 124 must be sent by a user node 108 in the same data structure 212 as the per-user bot 208 . Therefore, a qualified user node 108 has transmitted the message 124 and is able to have the message 124 sent to the per-user bot 208 . If the message qualifies, then flow proceeds to block 828 . If the message does not qualify, then flow instead proceeds to block 832 .
- the group messaging service 104 has identified a match between the received message 124 and the data structure 212 corresponding to the destination group 120 , and sends the message 124 to the selected per-user bot 208 .
- the message 124 has been delivered to the addressed per-user bot 208 , and the addressed per-user bot 208 carries out one or more functions corresponding to recorded audio within the message 124 .
- the per-user bot 208 provides a data or audio acknowledgment back to the group messaging service 104 , and in turn the group messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent the original message 124 .
- flow proceeds to block 832 and the group messaging service 104 sends the message 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent the original message 124 .
- the group messaging service 104 has determined that a bot 208 is not configured in the group corresponding to the destination group 120 identifier (decision block 808 ) or the message 124 is not qualified (decision block's 816 and 824 ), and therefore sends the received message 124 to the user nodes 108 within the destination group 120 .
- Addresses for the user nodes 108 within the destination group 120 are determined by reviewing the data structure 212 within the group messaging service 104 corresponding to the destination group 120 .
- Flow ends at block 832 or the group messaging service 104 returns to block 804 to wait for a next received message 124 .
- FIG. 9 illustrates a bot system 900 architecture in accordance with a first embodiment of the present disclosure.
- a group such as group 1 120 A includes one or more user nodes 108 , including user node B 108 B including mobile device 112 B and wearable pendant 116 .
- User node 108 B sends a recorded message with encoded audio 904 to the group messaging service 104 , where the recorded message 904 is directed to a bot 208 in group 1 120 A.
- Group messaging service 104 decodes the encoded audio in the recorded message 904 to create decoded audio 908 .
- Group messaging service 104 executes process 940 to identify a bot 208 and voice library, and direct the recorded message to users and bots 208 appropriately. Process 940 is shown and described in more detail with respect to FIG. 11 .
- Group messaging service 104 either includes a voice library as part of group messaging service 104 , or has access to one or more remote voice libraries.
- Voice libraries include at least a speech-to-text engine 902 and a natural language unit 903 .
- the speech-to-text engine 902 is part of group messaging service 104 while the natural language unit 903 is remote.
- the speech-to-text engine 902 is remote while the natural language unit 903 is part of group messaging service 104 .
- Remote portions of the voice library are accessed through Gateway processing 901 .
- Data structures 212 of the group messaging service 104 need to be configured as to whether voice libraries are required to be used for group messages, or not. For example, some bots 208 may require a voice library to be used while other bots 208 may not.
- the group messaging service 104 sends the decoded audio to the speech-to-text engine 902 , and the speech-to-text engine 902 converts the decoded audio into text 912 and sends the text 912 to the group messaging service 104 .
- the speech-to-text engine 902 sends the text 912 directly to the natural language unit 903 .
- the group messaging service 104 sends the text 912 to the natural language unit 903 , which reviews the text 912 and converts the text 912 into enhanced text 916 .
- Enhanced text 916 is clarified and simplified from text 912 into a form more suitable for presentation to a bot 208 to execute.
- the natural language unit 903 sends the enhanced text 916 to the group messaging service 104 .
- the group messaging service 104 After receiving the enhanced text 916 from the natural language unit 903 , the group messaging service 104 sends the enhanced text 916 to the selected bot 208 corresponding to the recorded message 904 .
- Bot 208 receives the enhanced text 916 and in response, performs one or more designated actions 920 corresponding to the decoded audio 908 and enhanced text 916 .
- bot 208 is associated with one or more commercial services 404 , such as order management systems or systems involving various financial transactions. Bot 208 forwards an order 936 or other commercial service request to commercial service 404 for execution.
- commercial service 404 would need to be previously configured by the user of user node B 108 B with payment, account number, IP address, or any other required information.
- Bot 208 would then send a reply 924 to the group messaging service 104 with various information including at least completion of the request corresponding to the enhanced text 916 .
- the group messaging service 104 forwards a reply 928 to group 1 120 A including user node B 108 B.
- group messaging service 104 provides the original recorded message to the group 932 in order to inform other user nodes 108 of group 1 120 A of the request made by user node B 108 B.
- all actions with recorded message 904 have been carried out and the requested transaction has been completed.
- FIG. 10 illustrates a bot system 1000 architecture in accordance with a second embodiment of the present disclosure.
- FIG. 10 illustrates a more complex embodiment to that illustrated bot system 900 of FIG. 9 .
- Bot system 1000 includes alternative voice libraries directly accessible by bot 208 .
- a group such as group 1 120 A includes one or more user nodes 108 , including user node B 108 B including mobile device 112 B and wearable pendant 116 .
- User node 108 B sends a recorded message with encoded audio in a PCU format 1016 to the group messaging service 104 , where the recorded message 904 is directed to a bot 208 in group 1 120 A.
- Group messaging service 104 decodes the encoded audio in the recorded message 904 to create decoded audio 908 .
- Group messaging service 104 executes process 940 to identify a bot 208 and voice library, and direct the recorded message to users and bots 208 appropriately. Process 940 is shown and described in more detail with respect to FIG. 11 .
- group messaging service 104 either includes a voice library as part of group messaging service 104 , or has access to one or more remote voice libraries 1004 .
- Voice libraries 1004 include at least Gateway processing 901 , a speech-to-text engine 902 A and a natural language unit 903 A. Voice libraries 1004 may be accessible through one or more application programming interfaces (APIs).
- APIs application programming interfaces
- the speech-to-text engine 902 A is part of group messaging service 104 while the natural language unit 903 A is remote.
- the speech-to-text engine 902 A is remote while the natural language unit 903 A is part of group messaging service 104 .
- a generic speech-to-text engine 902 A may be used in conjunction with multiple natural language units 903 .
- one natural language unit 903 may be used for restaurant or food-related messages
- another natural language unit 903 may be used for document or publication-related messages
- another natural language unit 903 may be used for scheduling related messages.
- Data structures 212 of the group messaging service 104 need to be configured as to whether voice libraries are required to be used for group messages, or not. Also, if multiple voice libraries 1004 , 1008 , 1012 are available, data structures 212 may indicate which voice library is used for each bot 208 . For example, some bots 208 may require a voice library to be used while other bots 208 may not.
- the group messaging service 104 sends the decoded audio 1020 to the speech-to-text engine 902 A, and the speech-to-text engine 902 A converts the decoded audio into text and sends the text directly to the natural language unit 903 A.
- the natural language unit 903 A reviews the text and converts the text into enhanced text 1024 , and sends the enhanced text 1024 to the group messaging service 104
- Enhanced text 1024 is clarified and simplified text in a form more suitable for presentation to a bot 208 to execute.
- the group messaging service 104 After receiving the enhanced text 1024 from the natural language unit 903 A, the group messaging service 104 sends the enhanced text 1028 to the selected bot 208 corresponding to the recorded message 1016 .
- Bot 208 receives the enhanced text 1028 and in response, performs one or more designated actions 1040 corresponding to the decoded audio 1020 and enhanced text 1028 .
- bot 208 is associated with one or more commercial services 404 , such as order management systems or systems involving various financial transactions. Bot 208 forwards one or more orders 1044 or other commercial service request to one or more commercial services 404 for execution.
- commercial services 404 would need to be previously configured by the user of user node B 108 B with payment, account number, IP address, or any other required information.
- Bot 208 would then send a text reply 1028 to the group messaging service 104 with various information including at least completion of the request corresponding to the enhanced text 1028 .
- the group messaging service 104 forwards a reply 1052 to group 1 120 A including user node B 108 B.
- group messaging service 104 provides the original recorded message to the group 1056 in order to inform other user nodes 108 of group 1 120 A of the request made by user node B 108 B.
- all actions with recorded message 1016 have been carried out and the requested transaction has been completed.
- a second embodiment where the bot 208 directly interfaces with voice libraries 1012 is now described.
- the group messaging service 104 forwards the .PCU audio 1032 to a .PCU to .WAV voice library 1008 .
- the .PCU to .WAV voice library 1008 converts the audio in .PCU format 1032 to .WAV format 1036 .
- the .PCU to .WAV voice library 1008 is also able to convert audio in .WAV format 1036 to .PCU format 1032 .
- the .PCU to .WAV voice library 1008 may either be part of group messaging service 104 or remote from group messaging service 104 .
- the .PCU to .WAV voice library 1008 sends the .WAV audio 1036 to the bot 208 .
- Bot 208 has an associated bot voice library 1012 , including a speech-to-text engine 902 B and a natural language unit 903 B.
- Bot voice library 1012 converts .WAV audio 1036 into enhanced text.
- the enhanced text may be required by the bot 208 in order to perform designated actions 1040 , or may be required by one or more commercial services 404 to perform additional actions including processing orders or financial transactions.
- bot 208 performs designated actions 1040 after receiving the .WAV audio 1036 but before converting the .WAV audio 1036 into enhanced text with bot voice library 1012 .
- bot 208 performs designated actions 1040 after receiving the .WAV audio 1036 and after converting the .WAV audio 1036 into enhanced text with bot voice library 1012 .
- bot 208 sends an audio reply 1048 , usually in compressed .MP 3 format, to the .PCU to .WAV voice library 1008 .
- the .PCU to .WAV voice library 1008 converts audio in .MP 3 format 1048 into .PCU audio 1032 , and sends the .PCU audio 1032 to the group messaging service 104 .
- the group messaging service 104 receives the .PCU audio 1032 and a reply, and sends a reply 1052 to group 1 120 A, including user node B 108 B.
- the group messaging service 104 sends the original message to the group 1056 . At this point, all actions with recorded message 1016 have been carried out and the requested transaction has been completed.
- FIG. 11 illustrates a flowchart of a bot architecture message flow process 940 using voice libraries in accordance with embodiments of the present disclosure.
- the bot messaging process 940 allows a user node 108 of a group 120 to send a message 124 to various configurations of bots 208 and voice libraries. Once a bot 208 is configured into a group 120 , a user node 108 may send and receive messages to and from the bot 208 through the group messaging service 104 .
- Flow begins at block 1104 .
- the group messaging service 104 receives a message 124 from a user node 108 in a group 120 .
- the message 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if the message 124 is intended to be sent to a bot 208 ), and an identifier of the user node 108 sending the message 124 .
- Flow proceeds to decision block 1108 .
- the group messaging service 104 determines if there is a bot 208 configured in the group 120 corresponding to the destination group 120 identifier. If there is a bot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow proceeds to block 1116 . If there is not a bot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow instead proceeds to block 1112 .
- the group messaging service 104 has determined that a bot 208 is not addressed in the message 124 (decision block 1108 ) or the message 124 is not qualified (decision blocks 1124 and 1132 ), and therefore sends the received message 124 to the user nodes 108 within the destination group 120 .
- Addresses for the user nodes 108 within the destination group 120 are determined by reviewing the data structure 212 within the group messaging service 104 corresponding to the destination group 120 . Flow ends at block 1112 , or the group messaging service 104 returns to block 1104 to wait for a next received message 124 .
- the group messaging service 104 selects a voice library 1004 , 1008 , 1012 to apply to the message 124 . If only a single voice library is available, the group messaging service 104 selects that voice library.
- voice libraries 1012 may be specific to a bot 208 .
- voice libraries 1004 may be general-purpose and able to be used with many such bots 208 .
- voice libraries 1008 may be used to convert recorded audio from one format to another format. Flow proceeds to decision block 1120 .
- the group messaging service 104 determines if the received message 124 should be sent to a specific shared bot 208 .
- the group messaging service 104 reviews the data structure 212 corresponding to the destination group 120 , and attempts to identify a shared bot entry 504 A corresponding to the bot identifier in the received message 124 .
- a data structure 212 may include any number of shared or per-user bot entries 504 A/ 504 B. If there is a match, and a shared bot entry 504 A in the data structure 212 matches the bot identifier, then flow proceeds to decision block 1124 . If there is not a match, and no shared bot entries 504 A in the data structure 212 match the bot identifier, then the received message should be sent to a per-user bot 208 and flow instead proceeds to decision block 1132 .
- the group messaging service 104 determines if the message 124 qualifies.
- a qualified message 124 is a message with content that conforms with a bot entry 504 A/ 504 B in the data structure 212 .
- the message 124 since there is a bot 208 involved (decision block 1108 ) and the bot 208 is a shared bot 208 (decision block 1120 ), the message 124 must be sent by a user node 108 in the same data structure 212 as the shared bot 208 . Therefore, a qualified user node 108 has transmitted the message 124 and is able to have the message 124 sent to the shared bot 208 . If the message qualifies, then flow proceeds to block 1128 . If the message does not qualify, then flow instead proceeds to block 1112 .
- the group messaging service 104 has identified a match between the received message 124 and the data structure 212 corresponding to the destination group 120 , and sends the message 124 to the selected shared bot 208 .
- the message 124 has been delivered to the addressed shared bot 208 , and the addressed shared bot 208 carries out one or more functions corresponding to recorded audio within the message 124 .
- the shared bot 208 provides a data or audio acknowledgment back to the group messaging service 104 , and in turn the group messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent the original message 124 or the group 120 that includes the user node 108 that sent the original message 124 .
- flow proceeds to block 1112 and the group messaging service 104 sends the message 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent the original message 124 .
- the group messaging service 104 determines if the message 124 qualifies.
- a qualified message 124 is a message with content that conforms with a bot entry 504 A/ 504 B in the data structure 212 .
- the message 124 since there is a bot 208 involved (decision block 1108 ) and the bot 208 is a per-user bot 208 (decision block 1120 ), the message 124 must be sent by a user node 108 in the same data structure 212 as the per-user bot 208 . Therefore, a qualified user node 108 has transmitted the message 124 and is able to have the message 124 sent to the per-user bot 208 . If the message qualifies, then flow proceeds to block 1136 . If the message does not qualify, then flow instead proceeds to block 1112 .
- the group messaging service 104 has identified a match between the received message 124 and the data structure 212 corresponding to the destination group 120 , and sends the message 124 to the selected per-user bot 208 .
- the message 124 has been delivered to the addressed per-user bot 208 , and the addressed per-user bot 208 carries out one or more functions corresponding to recorded audio within the message 124 .
- the per-user bot 208 provides a data or audio acknowledgment back to the group messaging service 104 , and in turn the group messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent the original message 124 .
- flow proceeds to block 1112 and the group messaging service 104 sends the message 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent the original message 124 .
- FIG. 12 illustrates a representative computing device 1200 in accordance with embodiments of the present disclosure.
- Computing device 1200 performs the processes of the present application, including process 216 of FIG. 3 , process 604 of FIG. 8 , and process 940 of FIG. 11 .
- Computing device 1200 may be any sort of known computing device including servers, desktop computers, notebook computers, tablets, embedded computers, personal digital assistants (PDAs), smart phones, wearable computers, or any other sort of computing device 1200 .
- PDAs personal digital assistants
- Computing device 1200 includes memory 1208 , which may include one or both of volatile and nonvolatile memory types.
- the memory 1208 includes firmware which includes program instructions that are fetched and executed, including program instructions for the processes of the present invention.
- Memory 1208 also includes data 1216 which includes data structures 212 of the present application. Examples of non-volatile memory 1208 include, but are not limited to, flash memory, SD, Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), hard disks, and Non-Volatile Read-Only Memory (NOVRAM). Volatile memory 1208 stores various data structures and user data.
- volatile memory 1208 examples include, but are not limited to, Static Random Access Memory (SRAM), Dual Data Rate Random Access Memory (DDR RAM), Dual Data Rate 2 Random Access Memory (DDR2 RAM), Dual Data Rate 3 Random Access Memory (DDR3 RAM), Zero Capacitor Random Access Memory (Z-RAM), Twin-Transistor Random Access Memory (TTRAM), Asynchronous Random Access Memory (A-RAM), ETA Random Access Memory (ETA RAM), and other forms of temporary memory.
- SRAM Static Random Access Memory
- DDR RAM Dual Data Rate Random Access Memory
- DDR2 RAM Dual Data Rate 2 Random Access Memory
- DDR3 RAM Dual Data Rate 3 Random Access Memory
- Z-RAM Zero Capacitor Random Access Memory
- TTRAM Twin-Transistor Random Access Memory
- A-RAM Asynchronous Random Access Memory
- ETA RAM ETA Random Access Memory
- computing device 1200 may also include a database 1220 , which may be local to computing device 1200 or externally accessible to computing device 1200 such as in a cloud environment providing cloud storage.
- Database 1220 may provide storage for a large number of parameters including data structures 212 , recorded or decoded audio from messages 124 , voice libraries, or any other applications or data associated with embodiments of the present application.
- Computing device 1200 includes a processor 1204 .
- Processor 1204 includes one or more processing devices suitable for executing device applications 1212 and data 1216 such as Intel x86-compatible processors, embedded processors, mobile processors, and/or RISC processors.
- Processor 1204 may include several devices including field-programmable gate arrays (FPGAs), memory controllers, North Bridge devices, and/or South Bridge devices.
- FPGAs field-programmable gate arrays
- processor 1204 fetches application 1212 program instructions and data 1216 from memory 1208 , it should be understood that processor 1204 and applications 1212 may be configured in any allowable hardware/software configuration, including pure hardware configurations implemented in ASIC or FPGA forms.
- Computing device 1200 also includes a display 1232 .
- the display 1232 may include control and non-control areas.
- controls are “soft controls” displayed on a screen and not necessarily hardware controls or buttons.
- one or more controls may be “soft controls” and one or more controls may be hardware controls or buttons.
- controls may be all hardware controls or buttons.
- Display 1232 may be a touch screen whereby controls may be activated by a finger touch or touching with a stylus or pen.
- Non-control areas are areas of the screen not including a control.
- Computing device 1200 includes a network transceiver 1236 .
- Network transceiver 1236 is any wired or wireless interface able to connect to one or more networks, including the internet or cloud in order to transmit and receive messages 124 , 612 , 708 , 904 , 932 , 1016 , 1056 and replies 924 , 928 , 1052 .
- Network transceiver 1236 may also be configured to transmit and receive decoded audio 908 and 1020 , PCU audio 1032 , text 912 , and enhanced text 916 , 1024 , and 1028 .
- Computing device 1200 may also include a keyboard 1224 and pointing device 1228 to interact with applications 1212 and the display 1232 .
Abstract
Description
- The present application is a continuation of and claims priority to pending U.S. patent application application Ser. No. 15/936,941, filed Mar. 27, 2018; and to U.S. provisional patent applications Ser. No. 62/477,070, filed on Mar. 27, 2017, both of which share a title with the current application, and the contents of which are hereby incorporated by reference in their entirety.
- With the worldwide proliferation of the internet, providing goods and services to users and consumers has become more commonplace and automated. One way that automatically providing increased numbers of goods and services is through bots. An internet Bot, also known as web robot, WWW robot or simply bot, is a software application that runs automated tasks (scripts) over the internet. Typically, bots perform tasks that are both simple and structurally repetitive, at a much higher rate than would be possible for a human alone. The largest current use of bots is in web spidering or web crawling, in which an automated script fetches, analyzes and files information from web servers at many times the speed of a human. More than half of all web traffic is made up of bots.
- Some bots communicate with other users of internet-based services, via Instant Messaging (IM), Internet Relay Chat (IRC), or another web interface such as Facebook Bots and Twitterbots. These chatterbots may allow people to ask questions in plain English and then formulate a proper response. These bots can often handle many tasks, including reporting weather, zip-code information, sports scores, converting currency or other units, etc. Others are used for entertainment, such as SmarterChild on AOL Instant Messenger and MSN Messenger. An additional role of IRC bots may be to lurk in the background of a conversation channel, commenting on certain phrases uttered by the participants (based on pattern matching). This is sometimes used as a help service for new users, or for censorship of profanity.
- General-purpose bots, such as Amazon's Alexa, Microsoft's Cortana, Google's Assistant, and Apple's Siri, are digital personal assistants able to provide a wide range of consumer-oriented voice-activated services, including turning lights on/off, controlling appliances, playing requested music from services such as Pandora or Spotify, providing requested information, or ordering products or services.
- With increasing interest in bot-based platforms and internet ease of use, it is desirable to create a new generation of messaging services that allow groups of users to interact with both user-oriented bots as well as group-oriented bots. The present disclosure provides advantages for bot environments. Methods, apparatuses, and computing systems are provided for bot messaging.
- In an implementation, a method may include one or more of receiving, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including recorded audio, a message address and a first group identifier, and determining that the group includes a bot, the bot including a software application for performing one or more tasks over the internet. The method may also include selecting a voice library to process the recorded audio, processing, by the selected voice library, the recorded audio to produce enhanced text, determining whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and sending, by the group messaging service, the enhanced text to the determined user bot or group bot.
- In another implementation, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium is configured to store computer instructions that when executed cause a processor to perform one or more of receiving, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including encoded recorded audio, a message address, and a first group identifier, and determining that the group includes a bot, the bot including a software application for performing one or more tasks over the internet. The processor also performs selecting a voice library to process the encoded recorded audio, processing, by the selected voice library, the encoded recorded audio to produce enhanced text, determining whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and sending, by the group messaging service, the enhanced text to the determined user bot or group bot.
- In yet another implementation, a computing system is provided. The computing system includes one or more of a storage system including program instructions and a processing system, operably coupled to the storage system. Program instructions when executed by the processing system are directed to receive, by a group messaging service coupled to the internet and a group including one or more user nodes, a message including encoded recorded audio, a message address and a first group identifier, and determine that the group includes a bot, the bot including a software application for performing one or more tasks over the internet. The program instructions are further directed to select a voice library to process the encoded recorded audio, process, by the selected voice library, the encoded recorded audio to produce enhanced text, determine whether the bot is a user bot responsive to a user node in the group or a group bot responsive to each of the one or more user nodes, and send, by the group messaging service, the enhanced text to the determined user bot or group bot.
- This overview is provided to introduce a selection of concepts in a simplified form that are further described below in the Technical Disclosure. It may be understood that this overview is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
- Many aspects of the disclosure can be better understood with reference to the following drawings. While several implementations are described in connection with these drawings, the disclosure is not limited to the implementations disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.
-
FIG. 1 illustrates a group messaging system in accordance with embodiments of the present disclosure. -
FIG. 2 illustrates a messaging flow for configuring a bot into a group in accordance with embodiments of the present disclosure. -
FIG. 3 illustrates a flowchart of a bot messaging process in accordance with embodiments of the present disclosure. -
FIG. 4 illustrates a messaging flow for a user node in accordance with embodiments of the present disclosure. -
FIG. 5A illustrates a shared bot entry within a data structure in accordance with embodiments of the present disclosure. -
FIG. 5B illustrates a per-user bot entry within a data structure in accordance with embodiments of the present disclosure. -
FIG. 6 illustrates messaging using a shared bot with a commercial service in accordance with embodiments of the present disclosure. -
FIG. 7 illustrates messaging using a per-user bot with a commercial service in accordance with embodiments of the present disclosure. -
FIG. 8 illustrates a flowchart of a messaging process using shared or per-user bots in accordance with embodiments of the present disclosure. -
FIG. 9 illustrates a bot system architecture in accordance with a first embodiment of the present disclosure. -
FIG. 10 illustrates a bot system architecture in accordance with a second embodiment of the present disclosure. -
FIG. 11 illustrates a flowchart of a bot architecture message flow process using voice libraries in accordance with embodiments of the present disclosure. -
FIG. 12 illustrates a representative computing device in accordance with embodiments of the present disclosure. - The following figures and description describe various embodiments that may be used to provide bot messaging in group user node environments. Many arrangements of
messaging systems -
FIG. 1 illustrates agroup messaging system 100 in accordance with embodiments of the present disclosure.Group messaging system 100 includes at least user nodes 108 and agroup messaging service 104. Thegroup messaging service 104 includes one or more computers or servers that facilitate communication between user nodes 108. Each user node 108 includes at least a mobile device 112, including smart phones, PDAs, or certain wearable computers. In some embodiments, user nodes 108 include awearable pendant 116 for wireless bidirectional audio communication with the mobile device 112. In other embodiments, user nodes 108 do not include awearable pendant 116. In one embodiment, the wireless bidirectional communication protocol uses Bluetooth LE. Mobile device 112 may also include one or more embedded or downloadable software applications that facilitate audio communication between thewearable pendant 116 and other user nodes 108 or thegroup messaging service 104. - User nodes 108 may be organized into one or more groups 120, where each group 120 includes at least one user node 108. In the exemplary embodiment illustrated in
FIG. 1 , two groups 120 are present in thegroup messaging system 100, identified asgroup 1 120A andgroup 2 120B.Group 1 120A includes three user nodes 108, identified asuser node A 108A,user node B 108B, anduser node C 108C. Each of the three user nodes 108 ingroup 1 120A includes awearable pendant 116.Group 2 120B also includes three user nodes 108, identified asuser node A 108A,user node D 108D, anduser node E 108E.User node A 108A anduser node D 108D each include awearable pendant 116, whileuser node E 108E does not include awearable pendant 116. In the absence of awearable pendant 116, the user foruser node E 108E communicates with themobile device 112E as they would with any smart phone or similar mobile device 112. - Notably, both
group 1 120A andgroup 2 120B includeuser node A 108A. A given user node 108 may be in none, one, or any number of groups 120. Multiple groups 120 may include different user nodes 108, or exactly the same user nodes 108. There is no limit to the association between user nodes 108 and groups 120. - When a user node 108 of a group 120 communicates with another group 120 through the
group messaging service 104,messages 124 are sent wirelessly and through the internet between the communicating user nodes 108 and thegroup messaging service 104.Messages 124 include recorded audio (a recorded message) as well as an ID of the sending user node 108 and a group ID for the destination group the message is being delivered to. Thegroup messaging service 104 receives themessage 124, identifies the group ID associated with themessage 124, looks up the user nodes 108 contained within the destination group 120, and transmits themessage 124 including the ID of the sending user node 108 to each of the user nodes 108 in the destination group 120. For example, if the user ofuser node B 108B wanted to send amessage 124 togroup 2 120B, the user ofuser node B 108B would speak into thewearable pendant 116 and identifygroup 2 120B as the destination for themessage 124 while speaking the audio for the message into thewearable pendant 116. An application onmobile device 112B would then create amessage 124 including recorded audio as described above and send themessage 124 to thegroup messaging service 104. The software application on themobile device 112B would have been previously configured with thegroup messaging service 104. Thegroup messaging service 104 would then receive, analyze, and transmit themessage 124 to each of the user nodes ingroup 2 120B as described earlier. Finally, each of the users ofuser node A 108A,user node D 108D, anduser node E 108E would receive and hear the audio for themessage 124 sent by the user ofuser node B 108B. Use of groups 120 as described herein does not preclude sendingmessages 124 directly from one user node 108 to a different user node 108. -
FIG. 2 illustrates a messaging flow for configuring abot 208 into a group 120 in accordance with embodiments of the present disclosure.System 200 includes one or more groups 120 as described with reference toFIG. 1 , agroup messaging service 104, and one or more existingbots 204.Bots 208 are software applications for performing one or more tasks over the internet. Therefore,bots 208 are internet-connected and in most embodiments are separate from thegroup messaging service 104. -
Bots 208 may be incorporated into groups 120 by configuring eachbot 208 in thegroup messaging service 104 in a similar fashion to user nodes 108.Group messaging service 104 includesdata structures 212 for specifying which user nodes 108 andbots 208 are in each group 120. Eachsuch data structure 212 includes identifiers and addresses for each user node 108 andbot 208 entity in thedata structure 212.Group messaging service 104 ingroup messaging system 200 includes twogroup data structures 212, identified asgroup 1data structure 212A andgroup 2data structure 212B.Data structure 212A includes identifiers and addresses for each of the user nodes 108 ingroup 1 120. Using the example shown inFIG. 1 ,data structure 212A includes auser node A 108A address and identifier, auser node B 108B address and identifier, and auser node C 108C address and identifier.Data structure 212B includes auser node A 108A address and identifier, auser node D 108D address and identifier, and auser node E 108E address and identifier.Group messaging service 104 may include any number ofdata structures 212, and a givenbot 208 may be included in any number ofdata structures 212.Data structures 212 may include service IDs or identifiers for any user nodes 108, as well. Service IDs may be anything, including a user name, and email address, or anything else that uniquely identifies a user or user node 108. - A user of a user node 108 initiates adding a
bot 208 to a group 120. In the example illustrated inFIG. 2 , a user ingroup 1 120A sends aconfiguration message 220 to thegroup messaging service 104 through the application on a corresponding mobile device 112 requesting aspecific bot 208C the user has identified be added togroup 1 120A. The user may not have the address of the requestedbot 208C, but is at least able to uniquely identify the requestedbot 208C. It is assumed that multiple existingbots 204 may be available to be messaged, and in the example ofFIG. 2 ,bots - In response to the
group messaging service 104 receiving themessage 220 forbot 208C ingroup 1 120A, a system administrator associated with the group messaging service configures 224data structure 212A to route messages to or frombot 208C. Abot 208C address and identifier is added todata structure 212A forgroup 1. In some embodiments, the system administrator may need to obtain information associated withbot 208C in order to configuredata structure 212A. Typically, once the system administrator has completed configuringbot 208C into thegroup 1data structure 212A, the system administrator sends a configuration message (not shown) to thegroup 1 120A user that sent therequest 220 to addbot 208C togroup 1 120. At this point,bot 208C is configured intogroup 1 120A along withuser nodes group 1 120A.Group messaging service 104 also includes aprocess 216 for sending messages to abot 208 configured in a group 120. -
FIG. 3 illustrates a flowchart of abot messaging process 216 in accordance with embodiments of the present disclosure. Thebot messaging process 216 allows a user node 108 to send amessage 124 to abot 208 in a group 120. Once abot 208 is configured into a group 120, a user node 108 may send and receive messages to and from thebot 208 through thegroup messaging service 104. Flow begins atblock 304. - At
block 304, thegroup messaging service 104 receives amessage 124 from a user node 108 in a group 120. Themessage 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if themessage 124 is intended to be sent to a bot 208), and an identifier of the user node 108 sending themessage 124. Flow proceeds todecision block 308. - At
block 308, thegroup messaging service 104 determines if there is abot 208 configured in the group 120 corresponding to the destination group identifier. If there is abot 208 configured in the group 120 corresponding to the destination group identifier, then flow proceeds todecision block 316. If there is not abot 208 configured in the group 120 corresponding to the destination group identifier, then flow instead proceeds to block 312. - At
block 312, thegroup messaging service 104 has determined that abot 208 is not configured in the group 120 corresponding to the destination group identifier, and therefore sends the receivedmessage 124 to the user nodes 108 within the destination group 120. Addresses for the user nodes 108 within the destination group 120 are determined by reviewing thedata structure 212 within thegroup messaging service 104 corresponding to the destination group 120. Flow ends atblock 312, or thegroup messaging service 104 returns to block 304 to wait for a nextreceived message 124. - At
decision block 316, thegroup messaging service 104 determines if the receivedmessage 124 should be sent to aspecific bot 208. Thegroup messaging service 104 reviews thedata structure 212 corresponding to the destination group 120, and identifies a bot entry 504 corresponding to the bot identifier in the receivedmessage 124. Adata structure 212 may include any number of bot entries 504. If there is a match, and a bot entry 504 in thedata structure 212 matches the bot identifier, then flow proceeds to block 320. If there is not a match, and no bot entries 504 in thedata structure 212 matches the bot identifier, then flow instead proceeds to block 312. - At
block 320, thegroup messaging service 104 has identified a match between the receivedmessage 124 and thedata structure 212 corresponding to the destination group 120, and sends themessage 124 to the selectedbot 208. At this point, themessage 124 has been delivered to the addressedbot 208, and the addressedbot 208 carries out one or more functions corresponding to recorded audio within themessage 124. In some embodiments, thebot 208 provides a data or audio acknowledgment back to thegroup messaging service 104, and in turn thegroup messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent theoriginal message 124 or the group 120 that includes the user node 108 that sent theoriginal message 124. In some embodiments, after thegroup messaging service 104 sends themessage 124 to the selectedbot 208, flow proceeds to block 312 and thegroup messaging service 104 sends themessage 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent theoriginal message 124. -
FIG. 4 illustrates amessaging flow 400 for a user node 108 in accordance with embodiments of the present disclosure. The present invention allows users and user nodes 108 to sendmessages 124 through agroup messaging service 104 to one ormore bots 208, and have the one ormore bots 208 perform various tasks related to the functionality of the one ormore bots 208. - In some cases,
bots 208 may provide enhanced functionality beyond providing information back to a requesting user node 108. For example, abot 208 may be associated with one or morecommercial services 404 that may allow purchase, sale, or other financial or more complex transactions.Bot 208 may parse message inputs to determine service handles corresponding to specificcommercial services 404. In some embodiments,commercial services 404 may be associated with different user accounts, for example an account associated with a specific user or user node 108 and another account associated with a group 120. In order to utilize suchcommercial services 404, it is generally necessary to configure thecommercial service 404 with various information 408 related to the user and user node 108 sourcing the transaction. In some embodiments, thecommercial service 404 is configured at least with a user ID and a user address or IP address corresponding to a user and user node 108 who intends to use thecommercial service 404. In other embodiments, thecommercial service 404 is further configured with other information 408 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information. - In the exemplary embodiment illustrated in
group messaging system 400,user node C 108C sends amessage 124 specifyingbot 208C to thegroup messaging service 104. As described with reference toFIG. 3 , thegroup messaging service 104 identifiesbot 208C is a valid recipient of themessage 124, and forwards themessage 124 tobot 208C.Bot 208C is associated withcommercial service 404, and passes along information within themessage 124 to thecommercial service 404. Thecommercial service 404 verifies the information within themessage 124 by comparing it to information 408 within thecommercial service 404 that has previously been configured. - In some embodiments,
commercial service 404 sends amessage 412 touser node C 108C requesting service verification. For example, for improved security it may be beneficial to provide user verification for a financial transaction that may have impacts to financial accounts associated with the user ofuser node C 108C. In most embodiments, an application onmobile device 112C receives and displays theservice verification 412 to the user, and the user verifies the transaction through the application. The application then replies to theservice verification 412 and sends a reply back to thecommercial service 404, where the requested transaction is then executed and acknowledged. In one embodiment, theservice verification 412 and reply are sent through a different messaging channel thanmessages 124 that go through thegroup messaging service 104. In other embodiments, theservice verification 412 and reply are sent through the same messaging channel thanmessages 124 that go through thegroup messaging service 104. -
FIG. 5A illustrates a sharedbot entry 504A within adata structure 212A in accordance with embodiments of the present disclosure.Data structures 212 may be configured one of two ways, depending on desiredbot 208 performance within a group 120. In a first embodiment,data structure 212A includes abot entry 504A that designatesbot 208C as a sharedbot 208. Sharedbot entry 504A includes abot address 508A and a bot identifier orID 512A. A sharedbot 208 is identified by a group 120 designation within thebot entry 504A. When a group 120 designation appears within abot entry 504A, thegroup messaging service 104 treats the corresponding bot 208 (bot 208C) as a shared bot within the corresponding group 120 (group 1, as shown). -
FIG. 5B illustrates a per-user bot 208 within adata structure 212A in accordance with embodiments of the present disclosure.Data structures 212 may be configured one of two ways, depending on desiredbot 208 performance within a group 120. In a second embodiment,data structure 212A includes a per-user bot entry 504B that designatesbot 208C as a per-user bot 208. Per-user bot entry 504B includes abot address 508B and a bot identifier orID 512B. A per-user bot 208 is identified by a user or user node 108 designation within the bot entry 504B. When a user or user node 108 designation appears within a bot entry 504B, thegroup messaging service 104 treats the corresponding bot 208 (bot 208C) as adedicated bot 208 to a corresponding user or user node 108 (user C, as shown). -
FIG. 6 illustrates messaging using a sharedbot 208 with acommercial service 404 in accordance with embodiments of the present disclosure. The present invention allows users and user nodes 108 to sendmessages 124 through thegroup messaging service 104 to one or more sharedbots 208, and have the one or more sharedbots 208 perform various tasks related to the functionality of the one or more sharedbots 208. As described with reference toFIG. 5A , sharedbots 208 arebots 208 assigned to a specific group 120 instead of a specific user or user node 108. Any user node 108 within a group 120 may send a message to a sharedbot 208 configured within the same corresponding group'sdata structure 212A, and thegroup messaging service 104 will respond accordingly. Otherwise, thegroup messaging service 104 will send a notification to the requesting user or user node 108 that the sharedbot 208 is currently not assigned to the group 120 of the requesting user or user node 108. -
Data structure 212A includes one or more sharedbot entries 504A.Data structure 212A may also contain both sharedbot entries 504A and per-user bot entries 504B. Each sharedbot entry 504A includes abot address 508A and a bot identifier orID 512A.Group messaging service 104 includes aprocess 604, shown in more detail inFIG. 8 , that selects a specific sharedbot entry 504A corresponding to themessage 124, and sends a message specifying the group ID 612 to the selected sharedbot 208. It should be understood that the sharedbot 208, and thecommercial service 404 if applicable, provides a response to thegroup messaging service 104 at least related to completion of the requested task in the message 612. Thegroup messaging service 104 would then provide a notification to each of the user nodes 108 in the requestinggroup 120A. - In some cases, shared
bots 208 may provide enhanced functionality beyond providing information back to a requesting user node 108. For example, a sharedbot 208 may be associated with one or morecommercial services 404 that may allow purchase, sale, or other financial or more complex transactions. In order to utilize suchcommercial services 404, it is generally necessary to configure thecommercial service 404 withvarious information 608 related to the group 120 and user node 108 sourcing the transaction. In the case of a sharedbot 208, thecommercial service 404 is configured at least with an account ID, an ID corresponding to the group 120, and an IP address corresponding to the group 120 for the user nodes 108 whose users intend to use thecommercial service 404. In other embodiments, thecommercial service 404 is further configured withother information 608 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information. - In the exemplary embodiment illustrated in
group messaging system 600, a user node 108 ingroup 1 120A sends amessage 124 specifying sharedbot 208 to thegroup messaging service 104. As described with reference toFIG. 6 , thegroup messaging service 104 identifies sharedbot 208 is a valid recipient of themessage 124, and forwards themessage 124 to sharedbot 208.Shared bot 208 is associated withcommercial service 404, and passes along information within themessage 124 to thecommercial service 404. Thecommercial service 404 verifies the information within themessage 124 by comparing it toinformation 608 within thecommercial service 404 that has previously been configured for the group 120. - In one embodiment, the
group messaging service 104 anddata structure 212A may be configured to forward allmessages 124 fromgroup 1 120A to aspecific bot 208, without thespecific bot 208 being explicitly addressed. In this way, aspecific bot 208 may be effectively monitoring all conversations withingroup 1 120A between user nodes 108 ofgroup 1 120A, and acting upon predetermined identified audio within each recordedmessage 124. - In some embodiments (not shown),
commercial service 404 sends a message to one or more user nodes 108 of the corresponding group 120 requesting service verification. For example, for improved security it may be beneficial to provide user verification for a financial transaction that may have impacts to financial accounts associated with the group 120. In most embodiments, an application on mobile devices 112 in the group 120 receives and displays the service verification to the user(s), and the user(s) verify the transaction through a mobile device 112 application. The application then replies to the service verification and sends a reply back to thecommercial service 404, where the requested transaction is then executed and acknowledged. In one embodiment, the service verification and reply are sent through a different messaging channel thanmessages 124 that go through thegroup messaging service 104. In other embodiments, the service verification and reply are sent through the same messaging channel thanmessages 124 that go through thegroup messaging service 104. -
FIG. 7 illustrates messaging using a per-user bot 208 with acommercial service 404 in accordance with embodiments of the present disclosure. The present invention allows users and user nodes 108 to sendmessages 124 through thegroup messaging service 104 to one or more per-user bots 208, and have the one or more per-user bots 208 perform various tasks related to the functionality of the one or more per-user bots 208. As described with reference toFIG. 5B , per-user bots 208 arebots 208 assigned to a specific user or user node 108 instead of a group 120. Any user node 108 within a group 120 may send amessage 124 to a per-user bot 208 configured within the corresponding group'sdata structure 212A, and thegroup messaging service 104 will process the message to the per-user bot 208 if the per-user bot 208 is configured to the sending user oruser node 108C. Otherwise, thegroup messaging service 104 will send a notification to the requesting user or user node 108 that the peruser bot 208 is currently not assigned to the requesting user or user node 108. -
Data structure 212A includes one or more per-user bot entries 504.Data structure 212A may also contain both sharedbot entries 504A and per-user bot entries 504B. Each per-user bot entry 504B includes abot address 508B and a bot identifier orID 512B.Group messaging service 104 includes aprocess 604, shown in more detail inFIG. 8 , that selects a specific per-user bot entry 504A corresponding to themessage 124, and sends a message specifying the user ID 708 to the selected per-user bot 208. It should be understood that the per-user bot 208, and thecommercial service 404 if applicable, provides a response to thegroup messaging service 104 at least related to completion of the requested task in the message 708. Thegroup messaging service 104 would then provide a notification to theuser node 108C that sent theoriginal message 124. - In some cases, per-
user bots 208 may provide enhanced functionality beyond providing information back to a requestinguser node 108C. For example, a per-user bot 208 may be associated with one or morecommercial services 404 that may allow purchase, sale, or other financial or more complex transactions. In order to utilize suchcommercial services 404, it is generally necessary to configure thecommercial service 404 with various information 704 related to the user anduser node 108C sourcing the transaction. In the case of a per-user bot 208, thecommercial service 404 is configured at least with an account ID, an ID corresponding to the user oruser node 108C, and an IP address corresponding to theuser node 108C whose user intends to use thecommercial service 404. In other embodiments, thecommercial service 404 is further configured with other information 704 such as, but not limited to, credit card numbers, credit card expiration dates, passwords, authentication keys, or any other information. - In the exemplary embodiment illustrated in
group messaging system 700,user node 108C sends amessage 124 specifying per-user bot 208 to thegroup messaging service 104. As described with reference toFIG. 8 , thegroup messaging service 104 identifies per-user bot 208 is a valid recipient of themessage 124, and forwards themessage 124 to per-user bot 208. Per-user bot 208 is associated withcommercial service 404, and passes along information within themessage 124 to thecommercial service 404. Thecommercial service 404 verifies the information within themessage 124 by comparing it to information 704 within thecommercial service 404 that has previously been configured for the user anduser node 108C. - In one embodiment, the
group messaging service 104 anddata structure 212A may be configured to forward allmessages 124 from a specificuser node C 108C to aspecific bot 208, without thespecific bot 208 being explicitly addressed. In this way, aspecific bot 208 may be effectively monitoring all conversations fromuser node C 108C between user nodes 108 ofgroup 1 120A, and acting upon identified audio within each recordedmessage 124 fromuser node C 108C. - In some embodiments (not shown),
commercial service 404 sends a message touser node 108C requesting service verification. For example, for improved security it may be beneficial to provide user verification for a financial transaction that may have impacts to financial accounts associated with the user ofuser node 108C. In most embodiments, an application on mobile device 112 ofuser node 108C receives and displays the service verification to the user, and the user verifies the transaction through the mobile device 112 application. The application then replies to the service verification and sends a reply back to thecommercial service 404, where the requested transaction is then executed and acknowledged. In one embodiment, the service verification and reply are sent through a different messaging channel thanmessages 124 that go through thegroup messaging service 104. In other embodiments, the service verification and reply are sent through the same messaging channel thanmessages 124 that go through thegroup messaging service 104. -
FIG. 8 illustrates a flowchart of amessaging process 604 using shared or per-user bots 208 in accordance with embodiments of the present disclosure. Thebot messaging process 604 allows a user node 108 to send amessage 124 to either a sharedbot 208 or a per-user bot 208 in a group 120. Once abot 208 is configured into a group 120, a user node 108 may send and receivemessages 124 to and from thebot 208 through thegroup messaging service 104. Flow begins atblock 804. - At
block 804, thegroup messaging service 104 receives amessage 124 from a user node 108 in a group 120. Themessage 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if themessage 124 is intended to be sent to a bot 208), and an identifier of the user node 108 sending themessage 124. Flow proceeds todecision block 808. - At
block 808, thegroup messaging service 104 determines if there is abot 208 configured in the group corresponding to the destination group 120 identifier. If there is abot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow proceeds todecision block 812. If there is not abot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow instead proceeds to block 832. - At
decision block 812, thegroup messaging service 104 determines if the receivedmessage 124 should be sent to a specific sharedbot 208. Thegroup messaging service 104 reviews thedata structure 212 corresponding to the destination group 120, and identifies a sharedbot entry 504A corresponding to the bot identifier in the receivedmessage 124. Adata structure 212 may include any number of shared or per-user bot entries 504A/504B. If there is a match, and a sharedbot entry 504A in thedata structure 212 matches the bot identifier, then flow proceeds todecision block 816. If there is not a match, and no sharedbot entries 504A in thedata structure 212 match the bot identifier, then the received message should be sent to a per-user bot 208 and flow instead proceeds todecision block 824. - At
decision block 816, thegroup messaging service 104 determines if themessage 124 qualifies. Aqualified message 124 is a message with content that conforms with abot entry 504A/504B in thedata structure 212. With respect to decision block 816, since there is abot 208 involved (decision block 808) and thebot 208 is a shared bot 208 (decision block 812), themessage 124 must be sent by a user node 108 in thesame data structure 212 as the sharedbot 208. Therefore, a qualified user node 108 has transmitted themessage 124 and is able to have themessage 124 sent to the sharedbot 208. If the message qualifies, then flow proceeds to block 820. If the message does not qualify, then flow instead proceeds to block 832. - At
block 820, thegroup messaging service 104 has identified a match between the receivedmessage 124 and thedata structure 212 corresponding to the destination group 120, and sends themessage 124 to the selected sharedbot 208. At this point, themessage 124 has been delivered to the addressed sharedbot 208, and the addressed sharedbot 208 carries out one or more functions corresponding to recorded audio within themessage 124. In some embodiments, the sharedbot 208 provides a data or audio acknowledgment back to thegroup messaging service 104, and in turn thegroup messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent theoriginal message 124 or the group 120 that includes the user node 108 that sent theoriginal message 124. In some embodiments, after thegroup messaging service 104 sends themessage 124 to the selected sharedbot 208, flow proceeds to block 832 and thegroup messaging service 104 sends themessage 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent theoriginal message 124. - At
decision block 824, thegroup messaging service 104 determines if themessage 124 qualifies. Aqualified message 124 is a message with content that conforms with abot entry 504A/504B in thedata structure 212. With respect to decision block 824, since there is abot 208 involved (decision block 808) and thebot 208 is a per-user bot 208 (decision block 812), themessage 124 must be sent by a user node 108 in thesame data structure 212 as the per-user bot 208. Therefore, a qualified user node 108 has transmitted themessage 124 and is able to have themessage 124 sent to the per-user bot 208. If the message qualifies, then flow proceeds to block 828. If the message does not qualify, then flow instead proceeds to block 832. - At
block 820, thegroup messaging service 104 has identified a match between the receivedmessage 124 and thedata structure 212 corresponding to the destination group 120, and sends themessage 124 to the selected per-user bot 208. At this point, themessage 124 has been delivered to the addressed per-user bot 208, and the addressed per-user bot 208 carries out one or more functions corresponding to recorded audio within themessage 124. The per-user bot 208 provides a data or audio acknowledgment back to thegroup messaging service 104, and in turn thegroup messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent theoriginal message 124. In some embodiments, after thegroup messaging service 104 sends themessage 124 to the selected per-user bot 208, flow proceeds to block 832 and thegroup messaging service 104 sends themessage 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent theoriginal message 124. - At
block 832, thegroup messaging service 104 has determined that abot 208 is not configured in the group corresponding to the destination group 120 identifier (decision block 808) or themessage 124 is not qualified (decision block's 816 and 824), and therefore sends the receivedmessage 124 to the user nodes 108 within the destination group 120. Addresses for the user nodes 108 within the destination group 120 are determined by reviewing thedata structure 212 within thegroup messaging service 104 corresponding to the destination group 120. Flow ends atblock 832, or thegroup messaging service 104 returns to block 804 to wait for a nextreceived message 124. -
FIG. 9 illustrates abot system 900 architecture in accordance with a first embodiment of the present disclosure. Once agroup messaging service 104 has been configured to use one ormore bots 208, user nodes 108 within groups 120 may send and receive messages from thebots 208. In some embodiments,bots 208 may be configured to respond to enhancedtext 916, rather than recordedmessages 124 as described previously. In such cases,group messaging service 104 must be able to convert audio from the recordedmessages 124 into enhancedtext 916 which may be sent to abot 208 to execute one or more actions. - A group, such as
group 1 120A includes one or more user nodes 108, includinguser node B 108B includingmobile device 112B andwearable pendant 116.User node 108B sends a recorded message with encoded audio 904 to thegroup messaging service 104, where the recordedmessage 904 is directed to abot 208 ingroup 1 120A.Group messaging service 104 decodes the encoded audio in the recordedmessage 904 to create decodedaudio 908.Group messaging service 104 executesprocess 940 to identify abot 208 and voice library, and direct the recorded message to users andbots 208 appropriately.Process 940 is shown and described in more detail with respect toFIG. 11 . -
Group messaging service 104 either includes a voice library as part ofgroup messaging service 104, or has access to one or more remote voice libraries. Voice libraries include at least a speech-to-text engine 902 and anatural language unit 903. In some embodiments, the speech-to-text engine 902 is part ofgroup messaging service 104 while thenatural language unit 903 is remote. In other embodiments, the speech-to-text engine 902 is remote while thenatural language unit 903 is part ofgroup messaging service 104. Remote portions of the voice library are accessed throughGateway processing 901.Data structures 212 of thegroup messaging service 104 need to be configured as to whether voice libraries are required to be used for group messages, or not. For example, somebots 208 may require a voice library to be used whileother bots 208 may not. - The
group messaging service 104 sends the decoded audio to the speech-to-text engine 902, and the speech-to-text engine 902 converts the decoded audio intotext 912 and sends thetext 912 to thegroup messaging service 104. In some embodiments, the speech-to-text engine 902 sends thetext 912 directly to thenatural language unit 903. After receiving thetext 912, thegroup messaging service 104 sends thetext 912 to thenatural language unit 903, which reviews thetext 912 and converts thetext 912 into enhancedtext 916.Enhanced text 916 is clarified and simplified fromtext 912 into a form more suitable for presentation to abot 208 to execute. Thenatural language unit 903 sends the enhancedtext 916 to thegroup messaging service 104. - After receiving the enhanced
text 916 from thenatural language unit 903, thegroup messaging service 104 sends the enhancedtext 916 to the selectedbot 208 corresponding to the recordedmessage 904.Bot 208 receives the enhancedtext 916 and in response, performs one or more designatedactions 920 corresponding to the decodedaudio 908 andenhanced text 916. In some embodiments,bot 208 is associated with one or morecommercial services 404, such as order management systems or systems involving various financial transactions.Bot 208 forwards an order 936 or other commercial service request tocommercial service 404 for execution. As previously described,commercial service 404 would need to be previously configured by the user ofuser node B 108B with payment, account number, IP address, or any other required information.Commercial service 404, after verifying the transaction withmobile device 112B, then carries out the requested order 936.Bot 208 would then send areply 924 to thegroup messaging service 104 with various information including at least completion of the request corresponding to the enhancedtext 916. - In response to receiving the
reply 924 from thebot 208, thegroup messaging service 104 forwards areply 928 togroup 1 120A includinguser node B 108B. Optionally,group messaging service 104 provides the original recorded message to the group 932 in order to inform other user nodes 108 ofgroup 1 120A of the request made byuser node B 108B. At this point, all actions with recordedmessage 904 have been carried out and the requested transaction has been completed. -
FIG. 10 illustrates abot system 1000 architecture in accordance with a second embodiment of the present disclosure.FIG. 10 illustrates a more complex embodiment to that illustratedbot system 900 ofFIG. 9 .Bot system 1000 includes alternative voice libraries directly accessible bybot 208. - A group, such as
group 1 120A includes one or more user nodes 108, includinguser node B 108B includingmobile device 112B andwearable pendant 116.User node 108B sends a recorded message with encoded audio in a PCU format 1016 to thegroup messaging service 104, where the recordedmessage 904 is directed to abot 208 ingroup 1 120A.Group messaging service 104 decodes the encoded audio in the recordedmessage 904 to create decodedaudio 908.Group messaging service 104 executesprocess 940 to identify abot 208 and voice library, and direct the recorded message to users andbots 208 appropriately.Process 940 is shown and described in more detail with respect toFIG. 11 . - For embodiments where the
group messaging service 104 interfaces with and controls voice libraries,group messaging service 104 either includes a voice library as part ofgroup messaging service 104, or has access to one or moreremote voice libraries 1004.Voice libraries 1004 include at least Gateway processing 901, a speech-to-text engine 902A and anatural language unit 903A.Voice libraries 1004 may be accessible through one or more application programming interfaces (APIs). In some embodiments, the speech-to-text engine 902A is part ofgroup messaging service 104 while thenatural language unit 903A is remote. In other embodiments, the speech-to-text engine 902A is remote while thenatural language unit 903A is part ofgroup messaging service 104. In some embodiments, a generic speech-to-text engine 902A may be used in conjunction with multiplenatural language units 903. For example, onenatural language unit 903 may be used for restaurant or food-related messages, anothernatural language unit 903 may be used for document or publication-related messages, and anothernatural language unit 903 may be used for scheduling related messages. -
Data structures 212 of thegroup messaging service 104 need to be configured as to whether voice libraries are required to be used for group messages, or not. Also, ifmultiple voice libraries data structures 212 may indicate which voice library is used for eachbot 208. For example, somebots 208 may require a voice library to be used whileother bots 208 may not. - The
group messaging service 104 sends the decoded audio 1020 to the speech-to-text engine 902A, and the speech-to-text engine 902A converts the decoded audio into text and sends the text directly to thenatural language unit 903A. Thenatural language unit 903A reviews the text and converts the text into enhancedtext 1024, and sends the enhancedtext 1024 to thegroup messaging service 104Enhanced text 1024 is clarified and simplified text in a form more suitable for presentation to abot 208 to execute. - After receiving the enhanced
text 1024 from thenatural language unit 903A, thegroup messaging service 104 sends the enhancedtext 1028 to the selectedbot 208 corresponding to the recorded message 1016.Bot 208 receives the enhancedtext 1028 and in response, performs one or more designated actions 1040 corresponding to the decodedaudio 1020 and enhancedtext 1028. In some embodiments,bot 208 is associated with one or morecommercial services 404, such as order management systems or systems involving various financial transactions.Bot 208 forwards one ormore orders 1044 or other commercial service request to one or morecommercial services 404 for execution. As previously described,commercial services 404 would need to be previously configured by the user ofuser node B 108B with payment, account number, IP address, or any other required information.Commercial services 404, after verifying the transaction withmobile device 112B, then carries out the requestedorder 1044.Bot 208 would then send atext reply 1028 to thegroup messaging service 104 with various information including at least completion of the request corresponding to the enhancedtext 1028. - In response to receiving the
text reply 1028 from thebot 208, thegroup messaging service 104 forwards areply 1052 togroup 1 120A includinguser node B 108B. Optionally,group messaging service 104 provides the original recorded message to thegroup 1056 in order to inform other user nodes 108 ofgroup 1 120A of the request made byuser node B 108B. At this point, all actions with recorded message 1016 have been carried out and the requested transaction has been completed. - A second embodiment where the
bot 208 directly interfaces withvoice libraries 1012 is now described. After thegroup messaging service 104 receives the recorded message with encoded audio (.PCU format) 1016, thegroup messaging service 104 forwards the .PCU audio 1032 to a .PCU to .WAV voice library 1008. The .PCU to .WAV voice library 1008 converts the audio in .PCU format 1032 to .WAV format 1036. The .PCU to .WAV voice library 1008 is also able to convert audio in .WAV format 1036 to .PCU format 1032. The .PCU to .WAV voice library 1008 may either be part ofgroup messaging service 104 or remote fromgroup messaging service 104. The .PCU to .WAV voice library 1008 sends the .WAV audio 1036 to thebot 208. -
Bot 208 has an associatedbot voice library 1012, including a speech-to-text engine 902B and a natural language unit 903B.Bot voice library 1012 converts .WAV audio 1036 into enhanced text. The enhanced text may be required by thebot 208 in order to perform designated actions 1040, or may be required by one or morecommercial services 404 to perform additional actions including processing orders or financial transactions. In one embodiment,bot 208 performs designated actions 1040 after receiving the .WAV audio 1036 but before converting the .WAV audio 1036 into enhanced text withbot voice library 1012. In another embodiment,bot 208 performs designated actions 1040 after receiving the .WAV audio 1036 and after converting the .WAV audio 1036 into enhanced text withbot voice library 1012. - After
bot 208 has completed all designated actions 1040,bot 208 sends anaudio reply 1048, usually in compressed .MP3 format, to the .PCU to .WAV voice library 1008. The .PCU to .WAV voice library 1008 converts audio in .MP3 format 1048 into .PCU audio 1032, and sends the .PCU audio 1032 to thegroup messaging service 104. Thegroup messaging service 104 receives the .PCU audio 1032 and a reply, and sends areply 1052 togroup 1 120A, includinguser node B 108B. Optionally, thegroup messaging service 104 sends the original message to thegroup 1056. At this point, all actions with recorded message 1016 have been carried out and the requested transaction has been completed. -
FIG. 11 illustrates a flowchart of a bot architecturemessage flow process 940 using voice libraries in accordance with embodiments of the present disclosure. Thebot messaging process 940 allows a user node 108 of a group 120 to send amessage 124 to various configurations ofbots 208 and voice libraries. Once abot 208 is configured into a group 120, a user node 108 may send and receive messages to and from thebot 208 through thegroup messaging service 104. Flow begins atblock 1104. - At
block 1104, thegroup messaging service 104 receives amessage 124 from a user node 108 in a group 120. Themessage 124 includes recorded audio, a destination group 120 identifier, a bot identifier (if themessage 124 is intended to be sent to a bot 208), and an identifier of the user node 108 sending themessage 124. Flow proceeds todecision block 1108. - At
block 1108, thegroup messaging service 104 determines if there is abot 208 configured in the group 120 corresponding to the destination group 120 identifier. If there is abot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow proceeds to block 1116. If there is not abot 208 configured in the group 120 corresponding to the destination group 120 identifier, then flow instead proceeds to block 1112. - At block 1112, the
group messaging service 104 has determined that abot 208 is not addressed in the message 124 (decision block 1108) or themessage 124 is not qualified (decision blocks 1124 and 1132), and therefore sends the receivedmessage 124 to the user nodes 108 within the destination group 120. Addresses for the user nodes 108 within the destination group 120 are determined by reviewing thedata structure 212 within thegroup messaging service 104 corresponding to the destination group 120. Flow ends at block 1112, or thegroup messaging service 104 returns to block 1104 to wait for a nextreceived message 124. - At
block 1116, thegroup messaging service 104 selects avoice library message 124. If only a single voice library is available, thegroup messaging service 104 selects that voice library. In some embodiments,voice libraries 1012 may be specific to abot 208. In other embodiments,voice libraries 1004 may be general-purpose and able to be used with manysuch bots 208. In yet other embodiments,voice libraries 1008 may be used to convert recorded audio from one format to another format. Flow proceeds todecision block 1120. - At
decision block 1120, thegroup messaging service 104 determines if the receivedmessage 124 should be sent to a specific sharedbot 208. Thegroup messaging service 104 reviews thedata structure 212 corresponding to the destination group 120, and attempts to identify a sharedbot entry 504A corresponding to the bot identifier in the receivedmessage 124. Adata structure 212 may include any number of shared or per-user bot entries 504A/504B. If there is a match, and a sharedbot entry 504A in thedata structure 212 matches the bot identifier, then flow proceeds todecision block 1124. If there is not a match, and no sharedbot entries 504A in thedata structure 212 match the bot identifier, then the received message should be sent to a per-user bot 208 and flow instead proceeds todecision block 1132. - At
decision block 1124, thegroup messaging service 104 determines if themessage 124 qualifies. Aqualified message 124 is a message with content that conforms with abot entry 504A/504B in thedata structure 212. With respect todecision block 1124, since there is abot 208 involved (decision block 1108) and thebot 208 is a shared bot 208 (decision block 1120), themessage 124 must be sent by a user node 108 in thesame data structure 212 as the sharedbot 208. Therefore, a qualified user node 108 has transmitted themessage 124 and is able to have themessage 124 sent to the sharedbot 208. If the message qualifies, then flow proceeds to block 1128. If the message does not qualify, then flow instead proceeds to block 1112. - At
block 1128, thegroup messaging service 104 has identified a match between the receivedmessage 124 and thedata structure 212 corresponding to the destination group 120, and sends themessage 124 to the selected sharedbot 208. At this point, themessage 124 has been delivered to the addressed sharedbot 208, and the addressed sharedbot 208 carries out one or more functions corresponding to recorded audio within themessage 124. In some embodiments, the sharedbot 208 provides a data or audio acknowledgment back to thegroup messaging service 104, and in turn thegroup messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent theoriginal message 124 or the group 120 that includes the user node 108 that sent theoriginal message 124. In some embodiments, after thegroup messaging service 104 sends themessage 124 to the selected sharedbot 208, flow proceeds to block 1112 and thegroup messaging service 104 sends themessage 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent theoriginal message 124. - At
decision block 1132, thegroup messaging service 104 determines if themessage 124 qualifies. Aqualified message 124 is a message with content that conforms with abot entry 504A/504B in thedata structure 212. With respect todecision block 1132, since there is abot 208 involved (decision block 1108) and thebot 208 is a per-user bot 208 (decision block 1120), themessage 124 must be sent by a user node 108 in thesame data structure 212 as the per-user bot 208. Therefore, a qualified user node 108 has transmitted themessage 124 and is able to have themessage 124 sent to the per-user bot 208. If the message qualifies, then flow proceeds to block 1136. If the message does not qualify, then flow instead proceeds to block 1112. - At
block 1136, thegroup messaging service 104 has identified a match between the receivedmessage 124 and thedata structure 212 corresponding to the destination group 120, and sends themessage 124 to the selected per-user bot 208. At this point, themessage 124 has been delivered to the addressed per-user bot 208, and the addressed per-user bot 208 carries out one or more functions corresponding to recorded audio within themessage 124. The per-user bot 208 provides a data or audio acknowledgment back to thegroup messaging service 104, and in turn thegroup messaging service 104 provides the data or audio acknowledgment back to the user node 108 that sent theoriginal message 124. In some embodiments, after thegroup messaging service 104 sends themessage 124 to the selected per-user bot 208, flow proceeds to block 1112 and thegroup messaging service 104 sends themessage 124 to other users and user nodes 108 within the same group 120 as the user node 108 that sent theoriginal message 124. -
FIG. 12 illustrates arepresentative computing device 1200 in accordance with embodiments of the present disclosure.Computing device 1200 performs the processes of the present application, includingprocess 216 ofFIG. 3 ,process 604 ofFIG. 8 , andprocess 940 ofFIG. 11 .Computing device 1200 may be any sort of known computing device including servers, desktop computers, notebook computers, tablets, embedded computers, personal digital assistants (PDAs), smart phones, wearable computers, or any other sort ofcomputing device 1200. -
Computing device 1200 includesmemory 1208, which may include one or both of volatile and nonvolatile memory types. In some embodiments, thememory 1208 includes firmware which includes program instructions that are fetched and executed, including program instructions for the processes of the present invention.Memory 1208 also includesdata 1216 which includesdata structures 212 of the present application. Examples ofnon-volatile memory 1208 include, but are not limited to, flash memory, SD, Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), hard disks, and Non-Volatile Read-Only Memory (NOVRAM).Volatile memory 1208 stores various data structures and user data. Examples ofvolatile memory 1208 include, but are not limited to, Static Random Access Memory (SRAM), Dual Data Rate Random Access Memory (DDR RAM),Dual Data Rate 2 Random Access Memory (DDR2 RAM), Dual Data Rate 3 Random Access Memory (DDR3 RAM), Zero Capacitor Random Access Memory (Z-RAM), Twin-Transistor Random Access Memory (TTRAM), Asynchronous Random Access Memory (A-RAM), ETA Random Access Memory (ETA RAM), and other forms of temporary memory. - In addition to
memory 1208,computing device 1200 may also include adatabase 1220, which may be local tocomputing device 1200 or externally accessible tocomputing device 1200 such as in a cloud environment providing cloud storage.Database 1220 may provide storage for a large number of parameters includingdata structures 212, recorded or decoded audio frommessages 124, voice libraries, or any other applications or data associated with embodiments of the present application. -
Computing device 1200 includes aprocessor 1204.Processor 1204 includes one or more processing devices suitable for executingdevice applications 1212 anddata 1216 such as Intel x86-compatible processors, embedded processors, mobile processors, and/or RISC processors.Processor 1204 may include several devices including field-programmable gate arrays (FPGAs), memory controllers, North Bridge devices, and/or South Bridge devices. Although in most embodiments,processor 1204 fetchesapplication 1212 program instructions anddata 1216 frommemory 1208, it should be understood thatprocessor 1204 andapplications 1212 may be configured in any allowable hardware/software configuration, including pure hardware configurations implemented in ASIC or FPGA forms. -
Computing device 1200 also includes adisplay 1232. Thedisplay 1232 may include control and non-control areas. In most embodiments, controls are “soft controls” displayed on a screen and not necessarily hardware controls or buttons. In some embodiments one or more controls may be “soft controls” and one or more controls may be hardware controls or buttons. In yet other embodiments, controls may be all hardware controls or buttons.Display 1232 may be a touch screen whereby controls may be activated by a finger touch or touching with a stylus or pen. Non-control areas are areas of the screen not including a control. -
Computing device 1200 includes anetwork transceiver 1236.Network transceiver 1236 is any wired or wireless interface able to connect to one or more networks, including the internet or cloud in order to transmit and receivemessages Network transceiver 1236 may also be configured to transmit and receive decodedaudio PCU audio 1032,text 912, andenhanced text -
Computing device 1200 may also include akeyboard 1224 andpointing device 1228 to interact withapplications 1212 and thedisplay 1232. - The functional block diagrams, operational scenarios and sequences, and flow diagrams provided in the Figures are representative of exemplary systems, environments, and methodologies for performing novel aspects of the disclosure. While, for purposes of simplicity of explanation, methods included herein may be in the form of a functional diagram, operational scenario or sequence, or flow diagram, and may be described as a series of acts, it is to be understood and appreciated that the methods are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.
- The descriptions and figures included herein depict specific implementations to teach those skilled in the art how to make and use the best option. For the purpose of teaching inventive principles, some conventional aspects have been simplified or omitted. Those skilled in the art will appreciate variations from these implementations that fall within the scope of the disclosure. Those skilled in the art will also appreciate that the features described above can be combined in various ways to form multiple implementations. As a result, the invention is not limited to the specific implementations described above, but only by the claims and their equivalents.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/152,393 US20210144109A1 (en) | 2017-03-27 | 2021-01-19 | Bot group messaging using general voice libraries |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762477070P | 2017-03-27 | 2017-03-27 | |
US15/936,941 US10897433B2 (en) | 2017-03-27 | 2018-03-27 | Bot group messaging using general voice libraries |
US17/152,393 US20210144109A1 (en) | 2017-03-27 | 2021-01-19 | Bot group messaging using general voice libraries |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/936,941 Continuation US10897433B2 (en) | 2017-03-27 | 2018-03-27 | Bot group messaging using general voice libraries |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210144109A1 true US20210144109A1 (en) | 2021-05-13 |
Family
ID=63583692
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/936,941 Active 2038-10-03 US10897433B2 (en) | 2017-03-27 | 2018-03-27 | Bot group messaging using general voice libraries |
US17/152,393 Abandoned US20210144109A1 (en) | 2017-03-27 | 2021-01-19 | Bot group messaging using general voice libraries |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/936,941 Active 2038-10-03 US10897433B2 (en) | 2017-03-27 | 2018-03-27 | Bot group messaging using general voice libraries |
Country Status (2)
Country | Link |
---|---|
US (2) | US10897433B2 (en) |
WO (1) | WO2018183290A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10855626B2 (en) * | 2017-10-03 | 2020-12-01 | Orion Labs, Inc. | Transcription bot for group communications |
US11258731B2 (en) * | 2019-08-22 | 2022-02-22 | Orion Labs, Inc. | Bot proxy for group communication service |
US10951554B1 (en) * | 2019-09-12 | 2021-03-16 | Genesys Telecommunications Laboratories, Inc. | Systems and methods facilitating bot communications |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1365553A1 (en) * | 2002-05-23 | 2003-11-26 | Accenture Global Services GmbH | Method and device for instant messaging |
US7603413B1 (en) * | 2005-04-07 | 2009-10-13 | Aol Llc | Using automated agents to facilitate chat communications |
EP1914639A1 (en) * | 2006-10-16 | 2008-04-23 | Tietoenator Oyj | System and method allowing a user of a messaging client to interact with an information system |
US8818926B2 (en) * | 2009-09-29 | 2014-08-26 | Richard Scot Wallace | Method for personalizing chat bots |
US20140046891A1 (en) * | 2012-01-25 | 2014-02-13 | Sarah Banas | Sapient or Sentient Artificial Intelligence |
US10319363B2 (en) * | 2012-02-17 | 2019-06-11 | Microsoft Technology Licensing, Llc | Audio human interactive proof based on text-to-speech and semantics |
US9830044B2 (en) * | 2013-12-31 | 2017-11-28 | Next It Corporation | Virtual assistant team customization |
US10078872B2 (en) * | 2015-03-26 | 2018-09-18 | Chatnels Software Inc. | System and method for managing and processing channel lines in a communication network |
US20160379638A1 (en) * | 2015-06-26 | 2016-12-29 | Amazon Technologies, Inc. | Input speech quality matching |
US10147415B2 (en) * | 2017-02-02 | 2018-12-04 | Microsoft Technology Licensing, Llc | Artificially generated speech for a communication session |
-
2018
- 2018-03-27 WO PCT/US2018/024513 patent/WO2018183290A1/en active Application Filing
- 2018-03-27 US US15/936,941 patent/US10897433B2/en active Active
-
2021
- 2021-01-19 US US17/152,393 patent/US20210144109A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US10897433B2 (en) | 2021-01-19 |
WO2018183290A1 (en) | 2018-10-04 |
US20180278556A1 (en) | 2018-09-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11711326B2 (en) | Bot group messaging method | |
US11431659B2 (en) | Shared and per-user bot group messaging method | |
US20220157663A1 (en) | Bot group messaging using bot-specific voice libraries | |
US20210144109A1 (en) | Bot group messaging using general voice libraries | |
US10581835B2 (en) | On demand passwords | |
AU2016265837B2 (en) | Virtual assistant in a communication session | |
US11777918B2 (en) | Dynamic and cryptographically secure augmentation of participants in programmatically established chatbot sessions | |
US10733572B2 (en) | Data protection using alerts to delay transmission | |
US20160352816A1 (en) | Method and system for sharing data between social networking platforms | |
US9710459B2 (en) | Communication monitoring based on sentiment | |
US20150264095A1 (en) | Web service push method and web service push server and web service providing server performing same | |
US10447692B2 (en) | Auto-creation of application passwords | |
US10783886B2 (en) | Cognitive agent disambiguation | |
KR20220037898A (en) | Character information processing system using Microsoft Excel | |
CN112306596A (en) | Information interaction method and device and electronic equipment | |
US20240073161A1 (en) | Message processing method, information processing apparatus, and program | |
KR20160109378A (en) | Apparatus and method for providing information of cafe | |
KR20230024525A (en) | Method and apparatus for providing counseling service | |
KR20230052691A (en) | Short url processing server and control method therof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ORION LABS, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROBBINS, JESSE;ALBRECHT, GREG;JUHLIN, ELLEN;SIGNING DATES FROM 20180518 TO 20180606;REEL/FRAME:054956/0612 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |