Discussion on Device ID Renaming in IEEE 802.11-22/1665r0

The document explores the ongoing discussion on renaming the Device ID in IEEE 802.11-22/1665r0 standards. Various proposals, including Persistent Opaque Identifier and Persistent Identifier, are considered. The Device ID's role in the current specifications is analyzed, along with the opacity of the ID in different scenarios. Different stages of the interaction involving the Device ID are outlined, emphasizing its importance and potential ambiguities.

• IEEE standards
• Device ID
• Renaming
• Ongoing discussion
• Network protocols

breelan Follow

Uploaded on Sep 13, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. doc.: IEEE 802.11-22/1665r0 Discussion on Device ID renaming Authors: Name Antonio de la Oliva InterDigital, Affiliation Address Phone email aoliva@it.uc3m.es UC3M Submission Antonio de la Oliva, InterDigital

2. doc.: IEEE 802.11-22/1665r0 Status of discussion Device ID has been used to denote the identifier of the STA which may be transmitted/provided to/by the AP. Several proposals for changing its naming have been discussed Persistent Opaque Identifier Persistent Identifier A mix of both, POI when talking about MAC layer and over the air, PI when talking outside There is unfinished discussion on what and where the ID is opaque Submission Antonio de la Oliva, InterDigital

3. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) MLME-ASSOCIATE.response (DeviceID) Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

4. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME If Device ID present, always opaque MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

5. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME If Device ID present, always opaque MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) Device ID1 Some thing Some thing If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Device ID2 Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

6. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME If Device ID present, always opaque MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) Device ID1 Some thing Some thing Device ID1==Device ID? Device ID2==Device ID? If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Device ID2 Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

7. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME If Device ID present, always opaque MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) Device ID1 Some thing Some thing Device ID1==Device ID? Device ID2==Device ID? If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Device ID2 Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

8. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Are these Device IDs the same? Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME MLME-ASSOCIATE.request (DeviceID) Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) Device ID1 Some thing Some thing Device ID1==Device ID? Device ID2==Device ID? If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Device ID2 Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

9. doc.: IEEE 802.11-22/1665r0 The Device ID in current spec (my view, may be wrong) Non-AP STA SME Non-AP STA MAC AP STA MAC AP STA SME If Device ID present, always opaque Out of scope, Device ID1 for SME is opaque? MLME-ASSOCIATE.request (DeviceID) Out of scope, for SME is opaque? Association Request (Device ID) MLME-ASSOCIATE.indication (DeviceID) Device ID1 Some thing Some thing If Device ID present, always opaque MLME-ASSOCIATE.response (DeviceID) Association Response (Device ID) MLME-ASSOCIATE.confirm (DeviceID) Submission Antonio de la Oliva, InterDigital

10. doc.: IEEE 802.11-22/1665r0 Ideas for decisions Based on our discussion Shall we have different naming for Device ID coming from external entity, SME and over the air? Is the Device ID always opaque within 11bh scope? Submission Antonio de la Oliva, InterDigital