1 / 21

Continued Discussion on WUR (802.11ba) Nomenclature

This document by Joseph Levy from InterDigital continues the discussion on the nomenclature currently used in the TGba draft amendment (IEEE P802.11ba/D1.0). It addresses the concepts of capability, architecture views, STA functionality, PHY functions, concerns, and intent.

pcurrier
Télécharger la présentation

Continued Discussion on WUR (802.11ba) Nomenclature

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joseph LEVY (InterDigital) Authors: Continued Discussion on WUR (802.11ba) Nomenclature Date: 2019-01-14

  2. Abstract • This contribution continues the discussion on the nomenclature currently used in the TGba draft amendment (IEEE P802.11ba/D1.0). The intent of this document is to continue the discussion held in the ARC SC session held on AM1, Wednesday 14 November. Addressing the action item: • “ARC folks, look at the latest 11ba draft, and see if the concepts are consistent, when read from this point of view, of a “capability” (from 11/18/2018r0) With the intent to progress understanding so that so that agreement can be reached on the TGba nomenclature. Joseph LEVY (InterDigital)

  3. Possible Architectures Views “New” WUR AP WUR non-AP STA PCR WUR AP Device WUR AP Device WUR AP WUR non-AP STA D 1.0? WUR Tx WURx Companion Radio Joseph LEVY (InterDigital)

  4. Joseph LEVY (InterDigital) Some Questions

  5. Is WUR Functionality a Capability of a STA? (1/2) • By current definition (P802.11REVmd D2.0) a STA is: • (3.2)“station (STA): A logical entity that is a singly addressable instance of a medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM).” • (5.1.1.1) A MAC provides: “peer LLC sublayer entities or IEEE 802.1Q bridge ports(11ak) with the ability to exchange MSDUs” (5.1.1.1) • (8.1) A PHY can consist of the following protocol functions: • “a) A function that defines a method of mapping the MPDUs into a framing format suitable for sending and receiving user data and management information between two or more STAs. • b) A function that defines the characteristics of, and method of transmitting and receiving data through, a WM between two or more STAs” Joseph LEVY (InterDigital)

  6. Is WUR Functionality a Capability of a STA? (2/2) • Question: Is a WUR non-AP STA a singly addressable MAC and PHY? • When not in WUR wake or doze “state” this is obviously true (this is the PCR). • When in WUR wake or doze state is it true? • Does a WUR non-AP STA in WUR mode have a MAC? • Is the MAC in the PCR adequate to make this claim? • As there is no “peer” to exchange frames with in WUR doze or wake “state” is there a MAC? • Is the capability of being able to receive a frame adequate to be a MAC? • Does a WUR non-AP STA in WUR mode have a PHY? • Must a PHY support both reception and transmission? • Is the PHY in the PCR adequate to make this claim? • Is the WUR ID adequate to be considered singly addressable? Joseph LEVY (InterDigital)

  7. Joseph LEVY (InterDigital) Concerns / Intent

  8. If PCR and WURx are not independent entities • Since a non-AP STA is: • By definition is a single addressable entity (this is true for all STAs) • It only exchanges frames with it’s associated AP (BSS/ESS) – excluding TDLS • Only operates on one frequency band • Then: • A WUR non-AP STA when associated can only operate on one channel • The AP it has associated with will operate on one channel, the same channel • A STA and an AP can only set up a WUR mode parameters for themselves • Therefore: • A 2.4 GHz WUR non-AP STA can not receive a WUR PPDU that will wake up a 5 GHz non-AP STA or vice versa. Joseph LEVY (InterDigital)

  9. If the AP and WUR Tx are not independent entities • Since an AP: • is by definition is a single addressable • operates on one frequency band • Then: • A WRU AP can only send WUR PPDUs to STAs that have associated with it in one frequency band. • Therefore: • A 2.4 GHz WUR AP can not send WUR PPDUs on a 5 GHz channel, hence it cannot wake up a 5 GHz non-AP STA or vice versa. Joseph LEVY (InterDigital)

  10. If the WUR is a mode of a non-AP STA is there a “Companion Receiver”? • The WUR PAR calls for the creation of a “Companion Receiver”: • This amendment defines a physical (PHY) layer specification and defines modifications to the medium access control (MAC) layer specification that enables operation of a wake-up radio (WUR). The wake-up frames carry only control information. The reception of the wake-up frame by the WUR can trigger a transition of the primary connectivity radio out of sleep. The WUR is a companion radio to the primary connectivity radio and meets the same range requirement as the primary connectivity radio. The WUR devices coexist with legacy IEEE 802.11 devices in the same band. The WUR has an expected active receiver power consumption of less than one milliwatt. • Is a mode of a non-AP STA a “Companion Receiver”? • Therefore: • The PAR is calling for an entity to be defined which is not defined by a “mode”. Joseph LEVY (InterDigital)

  11. Joseph LEVY (InterDigital) Detailed Specification Review Sections 11, 31, 32

  12. Power Management (11.2.3.1) • The only change to the Power Management proposed in 802.11ba D1.0 was to add a WUR Mode exclusion for listening to Beacon frames. • “A STA operating in PS mode with dot11NonTIMModeActivated equal to false that is notneither in WNM sleep mode nor in WUR Mode shall periodically listen for Beacon frames, …” [1] • This supports WUR Mode, being a subset of PS mode and hence a mode of a STA. • However, 11.2.1 [2]: states: • “A STA can be in one of two power states: • — Awake: STA is fully powered. • — Doze: STA is not able to transmit or receive and consumes very low power.” • This is inconsistent with WUR being a mode of a STA, also there is no 11.2.x section describing WUR mode behavior, as there is for WNM (11.2.3.16) “ Joseph LEVY (InterDigital)

  13. Wake-Up Radio MAC specification (31. [1]) [1/4] • While the majority of this section deals with WUR AP behavior, there are several requirements for STA behavior. • WUR STA’s are required to: • Know their ID and group IDs, as assigned by the associated WUR AP • WUR non-AP STA’s: • May establish WUR duty cycle • When in WUR mode it is assumed that: PCR component is in doze state and WURx is in awake/doze state in accordance with duty cycle (31.5). • Can a single logical entity (a STA) have two components? (SI – active?) • May set their WRU Channel Switching Support subfield to 1 or 0 (31.5) Joseph LEVY (InterDigital)

  14. Wake-Up Radio MAC specification (31. [1]) [2/4] • WUR non-AP STA’s (cont.): • May be in WUR Mode or WUR Mode Suspend (31.6.1) • The specification uses the term WRU service (31.6.1) (SI: not well defined) • Is this a service for both the AP and STA? How does this relate to the WUR mode? • Uses the PCR component to “negotiate” WUR Mode Setup (31.6.1) • Either to WUR Mode or WUR Mode Suspend. • This is inconstant with prior statements that the PCR is in doze state in WUR Mode, as it is clearly the case that once the negotiation has completed the STA state is in WUR Mode with the PCR awake. • Uses the PCR to switch: WUR Mode / WUR Mode Suspend (31.6.1) • Uses the PCR to update WUR parameters Joseph LEVY (InterDigital)

  15. Wake-Up Radio MAC specification (31. [1]) [3/4] • WUR non-AP STA’s (cont.): • Uses the PCR to teardown WUR service (31.6.1) • WURx component can be in two states: WUR Awake or WUR Doze (31.6.2) • Is it a problem that a STA has two components which can be in independent states? The STA in PS can be in any of 4 states: PCR/WURx - A/A, A/D, D/A, D/D(SI - WUR mode is not a state, yet some times it seems to be. Also all of the WUR STA behavior in 31.6.2 – does not seem to be necessary, all that is necessary is the AP behavior) • (SI – in 31.6.3 – the AP has no knowledge of what the STA state is only what it agreed to, so it can only assume the STA will hear an WUR PPDUs.) • (SI – in 31.7 – there are no WUR non-AP STAs, just non-AP STAs – this is inconsistent and confusing, also all the AP is requesting is that the STA move to Awake state – this could be much simpler) Joseph LEVY (InterDigital)

  16. Wake-Up Radio MAC specification (31. [1]) [4/4] • WUR non-AP STA’s (cont.): • Protected WUR frame reception requires the STA to validate the frame (31.8.2) • Is this part of the WURx functionality, or does the frame get passed to the PCR and validated there? It seems unlikely that the WURx could support this. Or is this just related to non-WUR PPDUS? (31.8.2) • WUR FDMA operation – when supported allows the for WUR PPDUs to the STA to be sent on an “offset channel” (31.9) • The current text doesn’t state that the WURx needs to listen on that channel. • WUR Discovery uses the WURx to scan for WUR Discovery frames (WRU APs). (31.10) • The current text doesn't stay that the WURx needs to do the scanning. Joseph LEVY (InterDigital)

  17. Wake-Up Radio PHY specification (32. [1]) • WUR non-AP STAs are only briefly defined as: • “A WUR AP is a WUR transmitter STA. A WUR non-AP STA is a WUR receiver STA.” • This section discussed only discusses: • WUR transmitter STAs • WUR receiver STAs • (SI - This seems to be in conflict with the way the MAC discusses these entities, there should be more naming constancy in the specification.) Joseph LEVY (InterDigital)

  18. Joseph LEVY (InterDigital) Discussion on Current Proposed Changes

  19. Current Proposed Descriptions • “A WUR AP is a non-HT, HT, VHT, or HE AP that is capable of transmitting a WUR PPDU. A WUR non-AP STA is a non-HT, HT, VHT, or HE non-AP STA that is capable of receiving a WUR PPDU and is not capable of transmitting a WUR PPDU. (#56) A WUR non-AP STA has a capability to receive a WUR PPDU at a very low power consumption less than 1 milliwatt.”[3] • Is this definition adequate? • Doesn’t a WUR AP also need to be able to configure a WUR mode? (Are these typical AP capabilities?) • Doesn’t a WUR non-AP STA also need to be able to configure a WRU mode and also operate in activate the mode? (Are these PCR capabilities?) Joseph LEVY (InterDigital)

  20. Current Proposed WUR Frames Description • “A WUR PPDU carries a WUR frame. Four WUR frames are defined: (#489, 59 ) • The WUR Beacon frame helps mainting timing synchronizaiton between a WUR non-AP STA and the WUR AP and enables the WUR duty cycle operation. (#489, 59) • The WUR Wake-up frame provides notification to the WUR non-AP STA(s) that the WUR AP has buffered data for the WUR non-AP STA(s), which enables the WUR non-AP STAs to remain in power save for longer periods of time and enables the WUR non-AP STAs to react to incoming traffic and critical update of BSS parameters with low latency. (#489, 59) • The WUR Discovery frame supports low power discovery of WUR APs. (#489, 59) • The WUR Vendor Specific frame supports a vendor specific operation.(#489, 59)” [3] • Is this description of these frames adequate? • Do these frames need additional context as to when these frames are used? • Do the WUR configuration MAC frames need to be provided? Joseph LEVY (InterDigital)

  21. References • IEEE P802.11ba™/D1.0; Draft STANDARD for Information Technology; Telecommunications and information exchange between systems; Local and metropolitan area networks; Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 9: Wake-Up Radio Operation; August 2018 • IEEE P802.11REVmd_D2.0.pdf; Draft Standard for Information technology; Telecommunications and information exchange between systems; Local and metropolitan area networks; Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; September 2018 • 11-19/0021r2 - CR clause 4 - Minyoung Park (Intel Corp.) • 11-16/1045r9- 802.11 WUR PAR • 11-19/0053r2 - PHY CR for Clause 32 - Minyoung (Intel Corporation) • 11-19/0029r1 - Comment Resolution for Miscellaneous Topic Part II - Po-Kai Huang (Intel) Joseph LEVY (InterDigital)

More Related