1. Multiple MAC addresses
April 2007
doc.: IEEE /0570r0
October 2010
Multiple MAC addresses
Date: October 12, 2010
Authors:
Solomon Trainin, Intel Corporation
Eldad Perahia, Intel Corporation

2. Multiple MAC STA motivation
October 2010
Multiple MAC STA motivation
Complete separation of MAC SAP that enables MAC level Network separation
Concurrent participation in networks with different Secure authentication and different cipher (Open, RSNA, CCMP, GCMP)
Concurrent P2P operation of different usages (AV with content protection and IO with secure authentication as an example)
Solomon Trainin, Intel Corporation

3. The submission is related to the comment:
October 2010
The submission is related to the comment:
Solomon Trainin, Intel Corporation

4. October 2010
Problems to solve
Eliminate excessive multiplication of the messaging and signaling that may happen in power management, beamforming and scheduling of the Multi MAC address STAs
Solomon Trainin, Intel Corporation

5. MAC multiple addresses in general
October 2010
MAC multiple addresses in general
Convention: Multi address STA (MA-STA), that easy makes MA-mSTA
The provided analysis at some point assumes single PHY but is not limited to
Coverage:
MA-STA reference model
MA-STA data plane
MA-STA MLME
MA-STA SME
Solomon Trainin, Intel Corporation

6. October 2010
Normative impact
Add new subclause “Multi-address operation” after to define setup of the EL Cluster
Make the appropriate changes in any places that are exposed to the EL and EL clustering
Solomon Trainin, Intel Corporation

7. MA-STA reference model interpretation
October 2010
MA-STA reference model interpretation
Solomon Trainin, Intel Corporation

8. MA-STA reference model interpretation (cont1)
October 2010
MA-STA reference model interpretation (cont1)
Identification of the MAC address of the MA-STA to communicate with is not part of the spec. As an example the service information element may contain the information about pairing of the services or device types provided by the STA and the MAC addresses.
Each MAC SAP together with MLME SAP are identified with MAC Address what is different for each MAC/MLME. The MAC entity keeps its unique MAC address.
The MA-STA SME is identified by any of the MAC addresses the STA supports:
SME of the MA-STA is responsible to maintain the multiple MAC addresses of the STA. SME specifies the MAC address to be used to send the MLME frame.
The MLME frames received by any of the MLME entities of the MA-STA are indicated to the MA-STA SME.
The Multiple MAC addresses element contains multiple addresses of the MA-STA. The element may be included in any MLME frames that advertise the MA-STA capabilities like probe and information request and responses and the MLME frames that establishes the communication agreements like association, TSPEC and BA request and responses.
Solomon Trainin, Intel Corporation

9. MA-STA reference model interpretation (cont2)
October 2010
MA-STA reference model interpretation (cont2)
There are two type of MA-STA links*:
Lone - single link between the MA-STAs (Link 1 and Link 4 as an example)
Engaged – Link that is one of multiple links between several (more than one) MACs of two MA-STAs or multiple links between MACs of MA-STA and STA (Link 2 and Link 3 represents engaged link). All together EL are EL Cluster
* MA-STA Link is an abstraction of any agreement like association, TS, or BA between STAs
Solomon Trainin, Intel Corporation

10. October 2010
MA-STA data plane
Solomon Trainin, Intel Corporation

11. MA-STA data plane normative impact
October 2010
MA-STA data plane normative impact
Each MAC SAP shall be controlled by separate and independent RSNA key management entity
The internal collision resolution defined for EDCA prioritized access should be extended to work for the Multiple MAC STA (OBand and DBand CBP)
The PLCP shall be able to provide indication to the MAC of the ongoing transmission of the PHY
DBand
Engaged links should be allowed to share the same SP (link 2 and link 3 in the example)
Solomon Trainin, Intel Corporation

12. October 2010
MA-STA MLME
SME accesses each of the MLME SAPs of the MA-STA separately and independently thus are no differences between MLME functionality and MLME primitives’ semantic between STA and MA-STA
Changes in the MA-STA mode or state that has global SME (MAC and PHY) meaning like power state/mode changes and changes of the PHY band/channel should be signaled in each of the lone links
Solomon Trainin, Intel Corporation

13. October 2010
EL Cluster and AID
Single AID (actually Source and Destination AID for P2P case) to be an option for the cluster identification.
Simplifies definition of the cluster related behavior (Power management, Beamforming, BeamLink maintenance, SP scheduling)
Simplifies implementation of the cluster control
The cluster identification w/o AID is still needed when the non associated devices speak each other
Solomon Trainin, Intel Corporation

14. EL Cluster and SP scheduling
October 2010
EL Cluster and SP scheduling
When the EL Cluster is indentified with single AID the SP allocated by any EL is used by any other EL belonging to the EL cluster
Solomon Trainin, Intel Corporation

15. EL Cluster and Power mode/state maintenance
October 2010
EL Cluster and Power mode/state maintenance
Signaling of the power state/mode changes in any of the EL of the cluster is relevant for the entire cluster and shall not be repeated
Solomon Trainin, Intel Corporation

16. EL Cluster and Beam Forming
October 2010
EL Cluster and Beam Forming
Single Beam when established shall be used by the EL cluster and the beamforming shall not be repeated
Solomon Trainin, Intel Corporation