Examples of data structures 400 that may be received, stored, retrieved, sent, managed, etc. in the processes as described herein may be as shown in FIG. 4A through FIG. 4C. The various different data structures 400 can be sent in signals as described in conjunction with FIG. 3. A first data structure 404 that may be exchanged, saved, etc. during determination of the master/slave relationship, in signals 316, may be as shown in FIG. 4A. The data structure 404 can include one or more of, but is not limited, a master identifier (ID) 408, a slave ID 412, etc. There may be more or fewer fields than those shown in FIG. 4A, as represented by ellipses 416. There also may be one or more data structures 404 involved in various different OFDMA schedules as represented by ellipses 420.

The master AP ID 408 can be any type of identifier that identifies AP 104a, as the master AP, for the joint OFDMA scheduling. This master AP ID 408 can include a numeric ID, an alphanumeric ID, a globally unique ID (GUID), a MAC address, a URL, or other types of identifiers. The ID need only identify the master AP 104a amongst the various APs 104 in both the BSSs 100a, 100b.