Phone-less member of group communication constellations

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser. No. 62/466,754 filed Mar. 3, 2017, which is incorporated herein by reference in its entirety for all purposes.

BACKGROUND

Modern communications devices have become an essential part of the lives of individuals around the world. These devices allow people to communicate in a variety of ways for both business and personal reasons. Examples of modern communication devices include cellular telephones, smartphones, discrete devices, computers, tablets, and others. Many of these devices often require multi-step processes to send and/or receive the communications. For example, some communication devices require a user to perform multiple steps with a graphical user interface that may not be practical or even possible for a user to perform in some settings. As such, in some cases, users may prefer communication devices for communicating with one another with less complicated interfaces for sending and receiving communications.

SUMMARY

Systems and methods are described for intelligent grouping between group communication devices. More specifically, some embodiments relate to grouping phone-less members of group communication constellations. In some embodiments, a method includes receiving, at a remote management platform, a recorded audio message from a first communication device that device includes a cellular networking component capable of connecting the first communication device to a cellular network. The first communication device may have a default grouping with a set of additional communication devices. In some embodiments, the default grouping can be created at a factory when the communication devices are manufactured. In other embodiments, the first communication device and the set of additional communications devices can be automatically paired upon initialization via a local communication network. A linking request can be automatically sent to the remote management platform to create the default grouping (e.g., by creating an entry in a routing table at the remote management platform).

Once a recorded message is received, the remote management platform can identify the set of additional communication devices associated with the default grouping and transmit the recorded message to that specific set of additional communication devices.

In some embodiments, the default group can be modified upon request (e.g., via a graphical user interface or voice command) by creating or editing entries within a routing table within the remote management platform. As a result, any recorded audio message received after the entry is added or modified will be routed to the default grouping and the additional communication device. In some embodiments, the additional communication devices can be a bot capable of processing natural language commands and generating a response (e.g., placing an order, collecting information, searching the web, etc.).

Some embodiments include a method for generating a registration request upon initial activation of the communication device. The communication device can be authorized to be used on a cellular network which can be used to transmit an activation signal from the communication device to a cloud-based management platform running on one or more servers. The cloud-based management platform automatically associates, upon activation and based on a factory setting, the communication device with a group of additional communication devices identified by a factory setting. An audio message can be recorded at the group communication device that is then transmitted via the cellular network to the cloud-based management platform. The cloud-based management platform can then identify the group of additional communication devices and automatically transmit the recorded audio message to each of the additional communications devices (e.g., one or more bots, voice assistants, or IoT devices).

Embodiments of the present invention also include computer-readable storage media containing sets of instructions to cause one or more processors to perform the methods, variations of the methods, and other operations described herein.

Some embodiments provide for a remote management platform that includes a processor, a database, a pairing module, a group management module, a natural language processor, a message conversion module, and/or an identification module. The database can store multiple group profiles that include communication profiles identifying communication devices within a group of communication devices associated with that profile. The pairing module configured to receive a grouping request generated upon an initial activation of a communication device and create an entry within a routing table. The entry can be based, at least in part, on information within the grouping request associating multiple communication devices together so that recorded audio messages received from any one of the multiple communication devices are automatically routed to the remaining communication devices according to the entry within the routing table. The group management module configured to receive a modification request from one of the multiple communication devices and update the entry in the routing table to include an additional communication device or to remove at least one of the communication devices from the group.

The natural language processor can be used to analyze the recorded audio message. For example, the natural language process can search and identify various types of directives (e.g., implicit directives, explicit directives, etc.) within recorded messages. The message conversion module can, generate a modified message based, at least in part, on the directive identified by the natural language processor. The routing module can route the message to a destination (e.g., endpoints such as the other group communication devices). The identification module can receive responses from the bot and identify the group for routing. The routing module can then route the responses from the bot to the group identified by the identification module.

While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the invention. As will be realized, the invention is capable of modifications in various aspects, all without departing from the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present technology will be described and explained through the use of the accompanying drawings in which:

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an example of a communications environment in which various embodiments of the present technology may be used;

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an embodiment of a communication device that may be used in some embodiments of the present technology;

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example of a set of components of a communication device in accordance with various embodiments of the present technology;

<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example of a set of components of a remote management system according to one or more embodiments of the present technology;

<figref idref="DRAWINGS">FIG. 5</figref> illustrates an example of a set of operations for routing messages within a communications environment according to some embodiments of the present technology;

<figref idref="DRAWINGS">FIG. 6</figref> illustrates an example of a set of operations for modifying a group of communication devices, bots, IoT devices, or other endpoints in accordance with various embodiments of the present technology;

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an example of a graphical user interface that may be used for modifying a group of communication devices, bots, IoT devices, or other endpoints in accordance with one or more embodiments of the present technology; and

<figref idref="DRAWINGS">FIG. 8</figref> is a sequence diagram illustrating an example of a set of communications between components of a communication system in accordance with some embodiments of the present technology.

The drawings have not necessarily been drawn to scale. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present technology. Moreover, while the technology is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the technology to the particular embodiments described. On the contrary, the technology is intended to cover all modifications, equivalents, and alternatives falling within the scope of the technology as defined by the appended claims.

DETAILED DESCRIPTION

Various embodiments of the present technology generally relate to systems and methods for intelligent grouping between group communication devices. More specifically, some embodiments relate to phone-less members of group communication constellations. In accordance with various embodiments, group communication devices may need to be grouped together so that multiple users can easily communicate with each other. Forming these groups may be difficult and time-consuming for large numbers of devices. Also, as situations change groups may need to also change to accommodate different group configurations, add various bots, Internet of Things (IoT) devices, voice assistants, or other group members.

Some embodiments provide for communication devices that are set at the factory with an initial group setting. This grouping creates a link (e.g., within a table stored on a remote management platform) between the devices that allows any of the communication devices to communicate with the other devices in the group. For example, multiple devices (e.g., two, three, four, or more) may be added to a group and then sold to a consumer as a set. As such, the users of this set of communication devices do not have to take the time to add these devices to a group and can begin communications immediately upon purchase. In some embodiments, these communication devices include personal communication nodes that include discrete devices specialized for group communications that include one or more wireless transceivers and user interface elements tailored to streamlined group communications.

The group communications can be initiated and/or altered either by user intervention or automatically by a shared remote management system. In some embodiments, the features of the discrete devices can be incorporated into other devices, such as personal communication devices which comprise cellular smartphones, gaming devices, wearable devices, personal computers, tablet computers, and the like. Voice command features can be included that allow user to modify the group, perform keyword-based searching, access productivity assistance, or access navigation assistance, among other features. Further features can include conversational interaction for information transmittal or retrieval, such as activity reminders, weather, stocks, messaging, email, calendar, contacts, notes, music, clocks, web browsers, maps and other applications.

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present technology. It will be apparent, however, to one skilled in the art that embodiments of the present technology may be practiced without some of these specific details. While, for convenience, embodiments of the present technology are described with reference to personal communication devices by creating default communication settings for groups of devices, embodiments of the present technology are equally applicable to various other cloud-based electronic devices.

The techniques introduced here can be embodied as special-purpose hardware (e.g., circuitry), as programmable circuitry appropriately programmed with software and/or firmware, or as a combination of special-purpose and programmable circuitry. Hence, embodiments may include a machine-readable medium having stored thereon instructions which may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), magneto-optical disks, ROMs, random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.

The phrases “in some embodiments,” “according to some embodiments,” “in the embodiments shown,” “in other embodiments,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one implementation of the present technology, and may be included in more than one implementation. In addition, such phrases do not necessarily refer to the same embodiments or different embodiments.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an example of a communications environment <b>100</b> in which various embodiments of the present technology may be used. As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, communications environment <b>100</b> may include one or more intermediary devices <b>110</b>A-<b>110</b>B (e.g., a mobile device, mobile phone, tablet computer, mobile media device, mobile gaming device, vehicle-based computer, wearable computing device, etc.) which can connect to one or more group communication devices <b>120</b>A-<b>120</b>N, communications network <b>130</b>, bots <b>140</b>A-<b>140</b>N, IoT devices <b>150</b>A-<b>150</b>N, voice assistants <b>160</b>A-<b>160</b>N, remote management platform <b>170</b>, and databases <b>180</b>A-<b>180</b>N. In addition, intermediary devices <b>110</b>A-<b>110</b>N and/or group communication devices <b>120</b>A-<b>120</b>N can include various network communication components that enable intermediary devices <b>110</b>A-<b>110</b>N and/or group communication devices <b>120</b>A-<b>120</b>N to communicate with other devices, bots <b>140</b>A-<b>140</b>N, IoT devices <b>150</b>A-<b>150</b>N, voice assistants <b>160</b>A-<b>160</b>N, remote management platform <b>170</b> or other devices or systems by transmitting and receiving wireless signals using licensed, semi-licensed or unlicensed spectrum over communications network <b>130</b>.

In some cases, communication network <b>130</b> may be comprised of multiple networks, even multiple heterogeneous networks, such as one or more border networks, voice networks, broadband networks, service provider networks, Internet Service Provider (ISP) networks, and/or Public Switched Telephone Networks (PSTNs), interconnected via gateways operable to facilitate communications between and among the various networks. Examples of communications network <b>130</b> include, but are not limited to, Long Term Evolution (LTE), Global System For Mobile Communications (GSM), Code Division Multiple Access (CDMA), IEEE 802.11 WiFi, Bluetooth, Personal Area Networks (PANs), Wide Area Networks, (WANs), Local Area Networks (LANs), or Wireless Local Area Networks (WLANs), and the like.

In accordance with some embodiments, group communication devices <b>120</b>A-<b>120</b>C may be sold in groups (e.g., two, three, four, or more devices). These devices can establish a default grouping for communicating with recorded messages (e.g., audio messages, video messages, etc.) thereby preventing the user from having to create the group manually. This grouping may be done at the factory or upon activation. For example, when one of group communication devices <b>120</b>A-<b>120</b>N is first activated by a user (e.g., over-the-air, in a retail store, via an application running on intermediary device <b>110</b>A-<b>110</b>B, scanning a code, etc.), one or more registration messages can be generated which can be transmitted through communications network <b>130</b> to remote management platform <b>170</b>. The registration messages may include device identifier, user identifier, and/or other information which can be used to register the device, identify a group, create a group, or for other purposes.

In some embodiments, each of the group devices sold together may share a common portion of a device identifier which can be used by remote management platform <b>170</b> to add the device to the common group for communications. The following table illustrates an example of the group communication device ID being used to create an entry in a routing table within databases <b>180</b>A-<b>180</b>N that can be accessed by remote management platform <b>170</b>. The entry may also include various device profile information such as device configurations or capabilities, model numbers, attributes, and the like.

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="28pt" align="left" /><colspec colname="3" colwidth="49pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><thead><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Group</entry><entry /><entry /></row><row><entry>GCD ID</entry><entry>#</entry><entry>Attributes</entry><entry>Device Configuration</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>ABCD12-A1234</entry><entry>1</entry><entry>Location A</entry><entry>LTE-Enabled</entry></row><row><entry>ABCD12-A3456</entry><entry>1</entry><entry>Location B</entry><entry>LTE-Enabled</entry></row><row><entry>ABCD12-B345</entry><entry>1</entry><entry>Location C</entry><entry>Bluetooth Only</entry></row><row><entry>IURD14-BCD12</entry><entry>2</entry><entry>Noise Level 1</entry><entry>Bluetooth Only</entry></row><row><entry>IURD14-ACD12</entry><entry>2</entry><entry>Noise Level 2</entry><entry>LTE-Enabled</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

Once the group has been formed, a user can record a message via one of the group communication devices <b>120</b>A-<b>120</b>N. The recording may be limited (e.g., less than two minutes) or continue until the user signals (e.g., by a pause in speaking, physical interaction with the group communication device, or other signaling) that the recording should end. The group communication devices or intermediary devices <b>110</b>A-<b>110</b>B can then transmit a signal that includes the recorded message to remote management platform <b>170</b> where decisions can be made about how to route the recorded message. For example, remote management platform <b>170</b> can identify additional members in a group (e.g., by looking up a routing entry in databases <b>180</b>A-<b>180</b>N). Some embodiments use a dynamic routing table which can include additional information (e.g., IP addresses) that can be updated as the device moves around. Once the additional members of the group have been identified, the recorded message can be sent to the other members in the group.

As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, a device may belong to multiple groups. For example, group communication devices <b>120</b>A and <b>120</b>B may be part of group A, while group communication devices <b>120</b>B and <b>120</b>C may be part of Group B. As a result, a user may have to select (e.g., via voice commands, hardware manipulation, etc.) which group the user intends the recorded message to be used for communication. In addition, any of the groups may include additional endpoints other than group communication devices <b>120</b>A-<b>120</b>N. For example, a group may also include bots <b>140</b>A-<b>140</b>N, IoT devices <b>150</b>A-<b>150</b>N, voice assistants <b>160</b>A-<b>160</b>N, and the like. Remote management platform can process the recorded messages originating from group communication devices <b>120</b>A-<b>120</b>N to identify various directives. The directives can include implicit directives, explicit directives, or bot directives.

For example, a personal message can include an implicit bot directive. When remote management platform <b>170</b> detects a directive, the message can be routed accordingly to an endpoint other than group communication devices <b>120</b>A-<b>120</b>N that are within the group. For example, a message recorded at group communication device may state the following: “Barabara, would you like to go see Star Wars tonight at the movie theater?” Remote management platform <b>170</b> can identify that this message includes an implicit bot directive to retrieve the start times for Star Wars. The original message can be delivered to Barabara's communication device followed by a response from a bot identifying movie times.

Bots <b>140</b>A-<b>140</b>N may facilitate keyword-based searching, productivity assistance, or navigation assistance, among other features. In some embodiments, bots <b>140</b>A-<b>140</b>N may facilitate conversational interaction for information transmittal or retrieval, such as activity reminders, weather, stocks, messaging, email, calendar, contacts, notes, music, clocks, web browsers, maps and other applications. Similarly, IoT devices can be any smart device (e.g., smart home appliance, security system, etc.) that can be commanded or accessed remotely.

Various components illustrate in <figref idref="DRAWINGS">FIG. 1</figref> may use secure communication methods for communicating with other components of the system. Secure communication methods include where users and nodes can securely share communications and other information among each other without non-group member or third-party interception or monitoring of the information or associated communications. Secure communication methods may comprise symmetric key encryption, asymmetric key encryption, public-key encryption, or some other type of encryption, including combinations thereof. The actual communications between personal communication devices can employ secure communication methods, and the associated links can employ secure communication methods independently.

End to end encryption of communications, such as audio communications, can be established among members of the group. These end-to-end encrypted communications can include transport layer security (TLS) or secure sockets layer (SSL) communications, among other secure link types.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an embodiment of a group communication device <b>200</b> that may be used in some embodiments of the present technology. In the embodiments illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, group communication device <b>200</b> has a face <b>205</b> that can be generally circular in shape, as shown in <figref idref="DRAWINGS">FIG. 2A</figref>, or can be any other shape. Group communication device <b>200</b> can use the generally circular shape to facilitate certain operations and to permit the positioning of certain functions and components, which also can be performed and implemented in alternative ways in other configurations. Group communication device <b>200</b> a generally cylindrical body <b>210</b> and face <b>205</b> can be slightly convex (e.g., having a quasi-conical shape or a cup-like shape). Because of the simplified controls disclosed herein, group communication device <b>200</b> can be smaller and more compact that earlier personal communication devices. For example, some embodiments of group communication device <b>200</b> can have a diameter of between one and three inches and be between one-half to one inch thick, making wearing or otherwise attaching device <b>200</b> to a user easier, in addition to simplifying the device's operation.

Body <b>210</b> may have an attachment mechanism <b>215</b> (e.g., a clip or clasp) mounted thereon to permit attachment of device <b>200</b> to clothing, a backpack, a bag strap or another personal item that facilitates a user's conversation with other users while wearing device <b>200</b>. Various functional components of device <b>200</b> can be situated around the periphery of body <b>210</b>, as seen in <figref idref="DRAWINGS">FIG. 2</figref>. A master power switch <b>220</b> can turn device <b>200</b> master power on and off (as distinguished from silencing device <b>200</b> and/or enabling sound transmission by device <b>200</b>). Speaker <b>225</b> and microphone <b>230</b> can be built into body <b>210</b>. Speaker <b>225</b> and microphone <b>230</b> can be of a type and size that facilitates and enables conversation by a user wearing device <b>200</b>. A volume control <b>235</b> can permit adjustment of the sound level generated by speaker <b>225</b> (e.g., lowering sound level by depressing one end—such as the “−” end—of volume control <b>235</b> and increasing sound level by depressing another end—such as the “+” end). Other components and/or features (e.g., a micro and/or other Universal Serial Bus (USB) port, charging port and/or headphone jack) can also be positioned around the periphery of device <b>200</b>.

Face <b>205</b> can be made of plastic or any other suitable material and includes an optical display <b>240</b> which in <figref idref="DRAWINGS">FIG. 2</figref> is an LED array. In other implementations, the optical display on face <b>205</b> can be a sticker, label or decal applied to face <b>205</b>. LED array <b>240</b> can operate in various implementations such as, but not limited to, one-touch silencing and one-touch transmission. Face <b>205</b> can be attached to body <b>210</b> in a manner that permits limited rotation of face <b>205</b> relative to body <b>210</b>, as referenced by arrow <b>245</b>. Likewise, face <b>205</b> can be mounted to body <b>210</b> in a depressible configuration that permits limited displacement and depression of face <b>205</b> relative to body <b>210</b>, as referenced by arrow <b>250</b>.

When a user wishes to use device <b>200</b> for communicating (e.g., via an intermediate communication device <b>110</b>A-<b>110</b>B or using cellular capabilities of device <b>200</b>), face <b>205</b> can be rotated as indicated by arrow <b>245</b> relative to body <b>210</b> which puts device <b>200</b> in an active mode. Optical display <b>240</b> can be used to confirm successful switching to the active mode (e.g., by providing a single-color LED animation). Once the user knows that device <b>200</b> is in active mode, messages can be recorded and transmitted to associated group members, bots, IoT devices or other endpoints. To create a recording, a user may depress face <b>205</b> downward relative to body <b>210</b> as indicated by arrows <b>250</b>. Sounds picked up by microphone <b>230</b> can be recorded locally on the device or streamed to an intermediary device (e.g., <b>110</b>A-<b>110</b>B as shown in <figref idref="DRAWINGS">FIG. 1</figref>) while face <b>205</b> is depressed. Once face <b>205</b> is released, the recording stops. If the message is being stored locally on the group communication device <b>200</b>, then the recorded message can then be transmitted to intermediary device for transmission or directly to remote management platform <b>170</b>. The recorded message can then be transmitted to other endpoints (e.g., via remote management platform <b>170</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>).

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a set of components within group communication device <b>120</b>A-<b>120</b>N according to one or more embodiments of the present technology. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, group communication device <b>120</b>A-<b>120</b>N may include memory <b>305</b> (e.g., volatile memory and/or nonvolatile memory), application processor(s) <b>310</b>, baseband processor(s) <b>315</b>, power supply <b>320</b> (e.g., battery), operating system <b>325</b>, network communications <b>330</b>, natural language processors, <b>335</b>, Bluetooth® interface <b>340</b>, LEDs <b>345</b>, microphone <b>350</b>, speaker <b>355</b>, camera <b>360</b>, encryption/decryption module <b>365</b>, USB interface <b>370</b>, and or additional user interface. Other embodiments may include different component configurations that do not include some of the components, combine the functionality of various components into a single component, and/or do not include some of the components shown in <figref idref="DRAWINGS">FIG. 3</figref>. For example, various embodiments may include additional; transceivers, audio transducers, processing systems, environmental sensors, accelerometers, gyroscopes, Global Positioning System (GPS) receivers, and other hardware or software components.

Application processor <b>310</b> can provide the processing power to support software applications, memory management, graphics processing, and multimedia. Application processor <b>310</b> may be communicably coupled with memory <b>305</b> and configured to run the operating system, user interface <b>375</b>, and the applications stored on memory <b>305</b>. Baseband processor <b>315</b> may be configured to perform signal processing and implement/manage real-time radio transmission operations of group communication device <b>120</b>A-<b>120</b>N. These processors along with the other components may be powered by power supply <b>320</b>. The volatile and nonvolatile memories found in various embodiments may include storage media for storing information such as processor-readable instructions, data structures, program modules, or other data. Some examples of information that may be stored include basic input/output systems (BIOS), operating systems, and applications.

Group communication device <b>120</b>A-<b>120</b>N may also include one or more network interfaces (e.g., Bluetooth Interface <b>340</b>; and Network Communication Interface <b>330</b>, which enables the group communication device to communicate with a remote management server or intermediary device by transmitting and receiving wireless signals using licensed, semi-licensed or unlicensed spectrum over a telecommunications network), natural language processors <b>335</b> for processing human speech, audio interface (not shown), microphone <b>350</b> for recording sounds, speaker <b>355</b> for playing messages, encryption/decryption module <b>365</b> for encrypting/decrypting messages, USB interface for powering the battery or transferring data, and/or other user interfaces <b>375</b> (e.g., displays, buttons, switches, keypad, and the like). The various components of a mobile device may be interconnected via a bus.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a set of components within remote management platform <b>170</b> according to one or more embodiments of the present technology. According to the embodiments shown in <figref idref="DRAWINGS">FIG. 4</figref>, remote management platform <b>170</b> can include memory <b>405</b>, one or more processors <b>410</b>, operating system <b>415</b>, voice library <b>420</b>, natural language processor <b>425</b>, group management module <b>430</b>, identification module <b>435</b>, status module <b>440</b>, prioritization module <b>445</b>, routing module <b>450</b>, message conversion module <b>455</b>, encryption/decryption module <b>460</b>, bot and IoT device management module <b>465</b>, and graphical user interface (GUI) generation module <b>470</b>. Each of these modules can be embodied as special-purpose hardware (e.g., one or more ASICS, PLDs, FPGAs, or the like), or as programmable circuitry (e.g., one or more microprocessors, microcontrollers, or the like) appropriately programmed with software and/or firmware, or as a combination of special purpose hardware and programmable circuitry.

Other embodiments of the present technology may include some, all, or none of these modules and components along with other modules, applications, and/or components. Still yet, some embodiments may incorporate two or more of these modules and components into a single module and/or associate a portion of the functionality of one or more of these modules with a different module. For example, in one embodiment, identification module <b>435</b> and status module <b>440</b> can be combined into a single module for monitoring a group communication device.

Memory <b>405</b> can be any device, mechanism, or populated data structure used for storing information. In accordance with some embodiments of the present technology, memory <b>405</b> can encompass any type of, but is not limited to, volatile memory, nonvolatile memory and dynamic memory. For example, memory <b>405</b> can be random access memory, memory storage devices, optical memory devices, media magnetic media, magnetic tapes, hard drives, SDRAM, RDRAM, DDR RAM, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), compact disks, DVDs, and/or the like. In accordance with some embodiments, memory <b>405</b> may include one or more disk drives, flash drives, one or more databases, one or more tables, one or more files, local cache memories, processor cache memories, relational databases, flat databases, and/or the like. In addition, those of ordinary skill in the art will appreciate many additional devices and techniques for storing information which can be used as memory <b>405</b>.

Memory <b>405</b> may be used to store instructions for running one or more applications or modules on processor(s) <b>410</b>. For example, memory <b>405</b> could be used in one or more embodiments to house all or some of the instructions needed to execute the functionality of operating system <b>415</b>, voice library <b>420</b>, natural language processor <b>425</b>, group management module <b>430</b>, identification module <b>435</b>, status module <b>440</b>, prioritization module <b>445</b>, routing module <b>450</b>, message conversion module <b>455</b>, encryption/decryption module <b>460</b>, bot and IoT device management module <b>465</b>, and/or GUI generation module <b>470</b>. Operating system <b>415</b> provides a software package that is capable of managing the hardware resources of management platform <b>140</b>. Operating system <b>415</b> can also provide common services for software applications running on processor(s) <b>410</b>.

Voice library <b>420</b> can include a set of voice commands that can be used to by remote management platform <b>170</b> for processing recorded messages received from group communication devices. For example, a recorded message may include explicit directives such as “order a pizza” or “delete Sam from the group.” This library can be used to help identify and process those explicit directives or commands within the directive. Voice library <b>420</b> may also include customized training data received from users so that their voice commands may be processed more accurately.

Natural language processor <b>425</b> can use voice library <b>420</b> to analyze and parse the recorded messages that are received from the group communication devices. Natural language process or <b>425</b> can process the natural language used by the users of the communication device to determine if there are any directives that may be included within the message or if the message is a personal message for just the other group members. Message conversion module <b>455</b> can receive the directives identified by natural language processor <b>425</b> and generates a modified message based, at least in part, on the directive identified by the natural language processor and the protocols and formatting requirements of the destination endpoint (e.g., IoT device or bot). The modified message can then be routed based on commands from routing module <b>450</b>. In addition, routing module <b>450</b> may route (e.g., based on a group ID and routing table entry) responses or messages from any endpoint to the group.

Group management module <b>430</b> can be configured to receive a request to create or modify a group. This request may originate from a device at the factory when the communication devices are built, upon activation, from a store, from a user, or the like. The request may identify whether a default group is being created, a new group is being created, and/or with an existing group is being modified. Group management module <b>430</b> can update or create entries in a routing table to create new groups or modify existing groups to include an additional communication device or to remove at least one of the communication devices from the group.

Identification module <b>435</b> can identify the group or destination endpoint for any message received. For example, a response from a bot can be processed by identification module <b>435</b> to determine the group and/or other endpoints. Identification module <b>435</b> can use information in the message itself (e.g., by using a field in the message) to identify a message chain, originating device, group, etc. Using this information, identification module <b>435</b> can looking up destination IP addresses or other routing information for routing the message.

Status module <b>440</b> can monitor for update messages from the various endpoints and can update contact information, device information, communication signal strength and other data within routing table entries. This information can be used to decide how to process the recorded messages. In some embodiments, prioritization module <b>445</b> can assign priorities to messages that are sent using routing module <b>450</b>. In one or more embodiments, these messages may be encrypted. Encryption/decryption module <b>460</b> can be used to encrypt and decrypt any of the messages sent or received at the remote management platform.

Bot and IoT device management module <b>465</b> can be used to manage the bots and IoT devices. For example, various bots and IoT devices may have particular communication protocols and/or other interfacing requirements. Bot and IoT device management module <b>465</b> can identify these requirements and ensure that message conversion module <b>455</b> converts messages into the correct format.

GUI generation module <b>470</b> can generate one or more GUI screens that allow for interaction with a user. In at least one embodiment, GUI generation module <b>470</b> can generate a graphical user interface allowing a user to set group preferences, review reports, add/remote IoT devices and/or bots, and/or otherwise receive or convey information about groups and the group communication devices to the user.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates an example of a set of operations <b>500</b> for routing messages within a communications environment according to some embodiments of the present technology. The operations illustrated in <figref idref="DRAWINGS">FIG. 5</figref> can be performed by remote management platform <b>170</b> and/or one or more components (e.g., processor(s) <b>410</b>), engines, and/or modules (e.g., identification module <b>435</b>) associated with remote management platform <b>170</b>. As illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, a communication is received from a group communication device during receiving operation <b>510</b>. The communication received during receiving operation <b>510</b> may include multiple fields. For example, in some embodiments, the communication may include one or more of a originating device identifier, a user identifier, a group selection identifier, a time/date stamp, IP address, payload, and/or other field.

Using the contents of the communication message, determination operation <b>520</b> can determine members of a group to which a message contained within the communication should be transmitted. Identification operation <b>530</b> can identify the recorded message. The recorded message can be processed, if needed, and then relayed to the group members using routing operation <b>540</b>.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates an example of a set of operations <b>600</b> for modifying a group of communication devices, bots, IoT devices, or other endpoints in accordance with various embodiments of the present technology. As illustrated in <figref idref="DRAWINGS">FIG. 6</figref>, creation operation <b>610</b> creates a default group for communications between one or more endpoints. The default group may be set at a factory or upon activation. For example, the default group may be created between a multiple group communication devices <b>120</b>A-<b>120</b>N at the factory and those devices can be packaged and sold together to the consumer. An entry in a routing table may be created at that time. In other embodiments, the entry may be created upon activation. For example, the devices may share a common code or identifier that is automatically identified and sent to the remote management platform <b>170</b> to allow for creation of the entry. As another example, the devices may automatically pair with nearby devices upon activation. The devices can then send, for example, a single registration request to create the entry in the routing table. The devices may include various branding (e.g., sports, food, entertainment, or other type branding) which is based on the automatic inclusion of various bots or voice assistants in the default group that specialize in that knowledge.

Over time, a user may desire to modify the group. In response to a request to modify the group that is received during receiving operation <b>620</b>, a selection of potential new group members can be presented during presentation operation <b>630</b>. A selection can be entered during selection operation <b>640</b> and the modified group can be created during creation operation <b>650</b>.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an example of a graphical user interface <b>700</b> that may be used for modifying a group of communication devices, bots, IoT devices, or other endpoints in accordance with one or more embodiments of the present technology. As illustrated in <figref idref="DRAWINGS">FIG. 7</figref>, a user can select a group <b>710</b>A-<b>710</b>C for management. Once a group is selected, the user can use device selection area <b>720</b> or advance search area <b>730</b> for identifying addition endpoints such as bots, IoT devices, live assistants, group communication devices and the like.

<figref idref="DRAWINGS">FIG. 8</figref> is a sequence diagram <b>800</b> illustrating an example of a set of communications between components of a communication system in accordance with some embodiments of the present technology. As illustrated in the embodiments shown in <figref idref="DRAWINGS">FIG. 8</figref>, a first group communication device <b>810</b> can record a message (e.g., audio message or a video message) which can be transmitted to remote management server <b>820</b>. The remote management server can identify the message, the originating device, and destination endpoints. In some cases, the message may need to be processed. For example, the message may include various directives (e.g., implicit, explicit, group, etc.). Remote management platform <b>820</b> can prepare sub-messages per end-point protocols before transmission to bots <b>830</b>, IoT devices <b>840</b>, and/or additional group communication devices. Any responses from these endpoints are routed back through remote management server <b>820</b> and can be processed before being delivered to the group communication devices.

CONCLUSION

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above Detailed Description of examples of the technology is not intended to be exhaustive or to limit the technology to the precise form disclosed above. While specific examples for the technology are described above for illustrative purposes, various equivalent modifications are possible within the scope of the technology, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.

The teachings of the technology provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the technology. Some alternative implementations of the technology may include not only additional elements to those implementations noted above, but also may include fewer elements.

These and other changes can be made to the technology in light of the above Detailed Description. While the above description describes certain examples of the technology, and describes the best mode contemplated, no matter how detailed the above appears in text, the technology can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the technology to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the technology encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the technology under the claims.

To reduce the number of claims, certain aspects of the technology are presented below in certain claim forms, but the applicant contemplates the various aspects of the technology in any number of claim forms. For example, while only one aspect of the technology is recited as a computer-readable medium claim, other aspects may likewise be embodied as a computer-readable medium claim, or in other forms, such as being embodied in a means-plus-function claim. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for”, but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application to pursue such additional claim forms, in either this application or in a continuing application.