The above mention challenges make any MRMC single radio system a complex one to implement, and as such there are some requirements which it is expected to meet in order to ensure a reliable and a stable solution. This section elaborates the key requirements expected from any solution to consider when coming to implement a MRMC single radio system.

First is the role’s availability. Each one of the active roles’ availability must be handled carefully and its absence from the operating channel must be taken in account. As will be further elaborate in Section 3, there are some actions that can be taken by the system (some are defined by the 802.11 specification) which allows the active role to indicate its peers he is about to leave the operating channel and avoid any of the implication described earlier.

Second is the role’s activities timing. Each one of the active roles has its own unique timing and priority requirements for each of its activities (for example, activity starting point, its duration, minimum time required, expiry time). The solution is required to handle multiple of those hard-timing activities and requests coming from each one of the roles simultaneously and asynchronously. To do that the solution might include some kind of scheduling mechanism that is able to suspend and resume each role activities on time and thus minimize user experience impact and keep system efficiency high.

Failing to handle the above requirements properly can cause unstable system behavior, periodic disconnections and very low unbalanced throughput.