The four main components to complete this concept are:
1. The Publishers with the Source Content (Streaming Plans)
2. The Cellular Network Provider for the Music Cloud Delivery
3. The Software Development to Standardized a Base Framework to Run the Profile System Features
4. The Hardware Device Developers
I just realized that for the "dongle" concept one could also just have a simple audio jack that could connect to all devices. The dongle would contain the antennas as well as the software to run the profiles to distribute the music to the device.
The devices and the potential "dongle" or "MusePod" would feature an "on network" fingerprint to curtail misuse of the technology. One would by the service and then connect the appropriate number of software or hardware dongles. So each customer of the service is identifiable within the system. Perhaps the number of devices and dongles needed would be supplied as necessary by default, if the user needed more than that, they would by another package because those amount of devices would pass the bandwidth threshold for the base price of the service. The antennna is critical to the system as well as device identifiers because one is referencing a mobile network and not just a home wifi system, having the identification hardware makes it easier for them to automically connect to the system once everything is setup.
The Modular side means the ability to take everywhere potentially swap parts and mix and match. But a key thing missing with portable sound technology is a way to affix them as needed. Like the ability to use "suction" cups to stick it on a wall, or velcro style attachment for more solid connection. This could include "docking" stations as another means to attach the device and detach where a more secure connection is desired.
The 2 software sides to this are, one piece of software is the GUI for the hardware, the other software is the "profile" engine. The profile engine is where you would program your personalized catalog and how it should function. If you were going to use the service on just the dongle, you would need to interface a GUI such as a phone, tablet or desktop to program how the dongle should function if there are no controls on the device it's being plugged into. If you have only an audio input for instance, you would need to control the functionality of the dongle through a device that has a screen (select "radio" stations, channels, playlists, program playlist behavior, use search features, show track information, catalog information, signal information, additional devices associated with the profile, additional profiles available etc...)
The "profile" is the base template of how the user interacts between the music streaming services "music cloud" and the hardware. It's more of a generalized and standardized specification that continually develops in an open-ended way. The critical features being access to music on servers provided by the streaming companies and ways to organize that content as well as information about the "system" of the profile user, such as which streaming services they use, which devices they use, a means of navigation and selection, custom features of the profile,
5G Music Radio