0% found this document useful (0 votes)

375 views144 pages

80211bd 2022

Uploaded by

Ghassan Dahman

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

375 views144 pages

80211bd 2022

Uploaded by

Ghassan Dahman

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 144

STANDARDS
IEEE 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 5:
Enhancements for Next Generation V2X

IEEE Computer Society

Developed by the
LAN/MAN Standards Committee

IEEE Std 802.11bd™‐2022
(Amendment to IEEE Std 802.11™‐2020
as amended by IEEE Std 802.11ax™‐2021,
IEEE Std 802.11ay™‐2021,
IEEE Std 802.11ba™‐2021,
IEEE Std 802.11™‐2020/Cor 1‐2022,
and IEEE Std 802.11az™‐2022)

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 802.11bd™-2022
(Amendment to IEEE Std 802.11™-2020
as amended by IEEE Std 802.11ax™-2021,
IEEE Std 802.11ay™-2021,
IEEE Std 802.11ba™-2021,
IEEE Std 802.11™-2020/Cor 1-2022,
and IEEE Std 802.11az™-2022)

IEEE 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 5:
Enhancements for Next Generation V2X

Developed by the
LAN/MAN Standards Committee
of the
IEEE Computer Society

Approved 3 December 2022

IEEE SA Standards Board

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Abstract: This amendment defines modifications to both the IEEE 802.11 physical layer (PHY)
and the medium access control (MAC) sublayer for next generation vehicle-to-everything (V2X)
communication in the 5.9 GHz and 60 GHz frequency bands.
Keywords: amendment, IEEE 802.11™, IEEE 802.11bd™, MAC, medium access control, OCB,
outside the context of BSS, PHY, physical layer, V2X, vehicular communication, vehicle-to-
everything communication, wireless local area network, WLAN

The Institute of Electrical and Electronics Engineers, Inc.

3 Park Avenue, New York, NY 10016-5997, USA

Copyright © 2023 by the Institute of Electrical and Electronics Engineers, Inc.

IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and
Electronics Engineers, Incorporated.

PDF: ISBN 978-1-5044-9521-9 STD26019

Print: ISBN 978-1-5044-9522-6 STDPD26019
IEEE prohibits discrimination, harassment and bullying.
For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior
written permission of the publisher.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Important Notices and Disclaimers Concerning IEEE Standards
Documents

IEEE Standards documents are made available for use subject to important notices and legal disclaimers.
These notices and disclaimers, or a reference to this page (https://standards.ieee.org/ipr/disclaimers.html),
appear in all standards and may be found under the heading “Important Notices and Disclaimers Concerning
IEEE Standards Documents.”

Notice and Disclaimer of Liability Concerning the Use of IEEE Standards

Documents

IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards
Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus
development process, which brings together volunteers representing varied viewpoints and interests to
achieve the final product. IEEE Standards are documents developed by volunteers with scientific, academic,
and industry-based expertise in technical working groups. Volunteers are not necessarily members of IEEE
or IEEE SA and participate without compensation from IEEE. While IEEE administers the process and
establishes rules to promote fairness in the consensus development process, IEEE does not independently
evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained
in its standards.

IEEE makes no warranties or representations concerning its standards, and expressly disclaims all
warranties, express or implied, concerning this standard, including but not limited to the warranties of
merchantability, fitness for a particular purpose and non-infringement. In addition, IEEE does not warrant or
represent that the use of the material contained in its standards is free from patent infringement. IEEE
standards documents are supplied “AS IS” and “WITH ALL FAULTS.”

Use of an IEEE standard is wholly voluntary. The existence of an IEEE Standard does not imply that there
are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to
the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and
issued is subject to change brought about through developments in the state of the art and comments
received from users of the standard.

In publishing and making its standards available, IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity, nor is IEEE undertaking to perform any duty owed by any
other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his
or her own independent judgment in the exercise of reasonable care in any given circumstances or, as
appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE
standard.

IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: THE
NEED TO PROCURE SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE
UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND
REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.

3
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Translations

The IEEE consensus development process involves the review of documents in English only. In the event
that an IEEE standard is translated, only the English version published by IEEE is the approved IEEE
standard.

Official statements

A statement, written or oral, that is not processed in accordance with the IEEE SA Standards Board
Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its
committees and shall not be considered to be, nor be relied upon as, a formal position of IEEE. At lectures,
symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that the presenter’s views should be considered the personal views of that individual rather
than the formal position of IEEE, IEEE SA, the Standards Committee, or the Working Group. Statements
made by volunteers may not represent the formal position of their employer(s) or affiliation(s).

Comments on standards

Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE or IEEE SA. However, IEEE does not provide interpretations,
consulting information, or advice pertaining to IEEE Standards documents.

Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important that any responses to comments and questions also receive the concurrence of a balance of interests.
For this reason, IEEE and the members of its Societies and subcommittees of the IEEE SA Board of
Governors are not able to provide an instant response to comments, or questions except in those cases where
the matter has previously been addressed. For the same reason, IEEE does not respond to interpretation
requests. Any person who would like to participate in evaluating comments or in revisions to an IEEE standard
is welcome to join the relevant IEEE working group. You can indicate interest in a working group using the
Interests tab in the Manage Profile & Interests area of the IEEE SA myProject system.1 An IEEE Account is
needed to access the application.

Comments on standards should be submitted using the Contact Us form.2

Laws and regulations

Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the
provisions of any IEEE Standards document does not constitute compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not
in compliance with applicable laws, and these documents may not be construed as doing so.

Data privacy

Users of IEEE Standards documents should evaluate the standards for considerations of data privacy and
data ownership in the context of assessing and using the standards in compliance with applicable laws and
regulations.

1
Available at: https://development.standards.ieee.org/myproject-web/public/view.html#landing.
2
Available at: https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html.

4
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Copyrights

IEEE draft and approved standards are copyrighted by IEEE under US and international copyright laws.
They are made available by IEEE and are adopted for a wide variety of both public and private uses. These
include both use, by reference, in laws and regulations, and use in private self-regulation, standardization,
and the promotion of engineering practices and methods. By making these documents available for use and
adoption by public authorities and private users, neither IEEE nor its licensors waive any rights in copyright
to the documents.

Photocopies

Subject to payment of the appropriate licensing fees, IEEE will grant users a limited, non-exclusive license
to photocopy portions of any individual standard for company or organizational internal use or individual,
non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance
Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400; https://
www.copyright.com/. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.

Updating of IEEE Standards documents

Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by the issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect.

Every IEEE standard is subjected to review at least every 10 years. When a document is more than 10 years
old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of
some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that
they have the latest edition of any IEEE standard.

In order to determine whether a given document is the current edition and whether it has been amended
through the issuance of amendments, corrigenda, or errata, visit IEEE Xplore or contact IEEE.3 For more
information about the IEEE SA or IEEE’s standards development process, visit the IEEE SA Website.

Errata

Errata, if any, for all IEEE standards can be accessed on the IEEE SA Website.4 Search for standard number
and year of approval to access the web page of the published standard. Errata links are located under the
Additional Resources Details section. Errata are also available in IEEE Xplore. Users are encouraged to
periodically check for errata.

Patents

IEEE Standards are developed in compliance with the IEEE SA Patent Policy.5

Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has

3
Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
4
Available at: https://standards.ieee.org/standard/index.html.
5
Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.

5
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the
IEEE SA Website at https://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may
indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without
compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of
any unfair discrimination to applicants desiring to obtain such licenses.

Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their
own responsibility. Further information may be obtained from the IEEE Standards Association.

IMPORTANT NOTICE

IEEE Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure
against interference with or from other devices or networks. IEEE Standards development activities consider
research and information presented to the standards development group in developing any safety
recommendations. Other information about safety practices, changes in technology or technology
implementation, or impact by peripheral systems also may be pertinent to safety considerations during
implementation of the standard. Implementers and users of IEEE Standards documents are responsible for
determining and complying with all appropriate safety, security, environmental, health, and interference
protection practices and all applicable laws and regulations.

6
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Participants
At the time this amendment was sent to the IEEE SA Board for approval, the IEEE 802.11 Working Group
had the following members:

Dorothy Stanley, Chair

Jon W. Rosdahl, 1st Vice Chair
Robert Stacey, 2nd Vice Chair
Stephen McCann, Secretary

Bo Sun, IEEE 802.11bd Task Group Chair

Hongyuan Zhang, IEEE 802.11bd Task Group Vice Chair
Joseph S. Levy, IEEE 802.11bd Task Group Vice Chair
Yan Zhang, IEEE 802.11bd Task Group Secretary
James Lepp, IEEE 802.11bd Task Group Former Secretary
Yujin Noh, IEEE 802.11bd Task Group Technical Editor
Bahareh Sadeghi, IEEE 802.11bd Task Group Former Technical Editor

Rana Abdelaal Alan Berkema Diana Cortes

Mohamed Abouelseoud Harry Bims Claudio da Silva
Osama S. Aboulmagd Andreas Bluschke Dibakar Das
Tomoko Adachi Lennert Bober Debashis Dash
Olubukola Adakeja David Boldy Leonard Dauphinee
Shubhodeep Adhikari Daniel Borges Rolf J. de Vegt
Peyush Agarwal Daniel Bravo Antonio DeLaOlivaDelgado
Kosuke Aio Albert Bredewoud Thomas Derham
Abdel Karim Ajami Frank Burkhardt Patrice Desmoulin
Dmitry Akhmetov Radhakrishna Canchi Rocco Di Taranto
Carlos H. Aldana Rui Cao Yanyi Ding
Vamsi Amalladinne Laurent Cariou Ali Dogukan
Song-Haur An William Carney Mingjie Dong
Amelia Andersdotter Edward Carter Xiandong Dong
Carol Ansley Dave Cavalcanti Rui Du
Diego Arlandis Gurkan Cepni Zhenguo Du
Antonio Arregui Chen-Yi Chang Peter Ecclesine
Yusuke Asai Matthew Chappell Richard Edgar
Alfred Asterjadhi Kirill Chemrov Alecsander Eitan
Oscar Au Cheng Chen Ahmed ElSherif
Ziv Avital Evelyn Chen Marc Emmelmann
Geert A. Awater Xiaogang Chen Vinko Erceg
Mehmet Aygul You-Wei Chen Serhat Erkucuk
Agustin Badenes Paul Cheng Shuang Fan
Juan Fang
SunHee Baek Phoebe Cheng
Yonggang Fang
Christy Bahn Xilin Cheng
Shuling Feng
Eugene Baik George Cherian
David Ferruz
Gabor Bajko James Chiang
Matthew J. Fischer
Hari Ram Balakrishnan Rojan Chitrakar
Ming Gan
Raja Banerjea Lin-Kai Chiu Trivikram Gangur
Dmitry Bankov Shi Baw Chng Ning Gao
stephane Baron Hangyu Cho Lalit Garg
David Barr Jinsoo Choi Thomas Gee
Anuj Batra Seungho Choo Alireza Ghaderipoor
Tuncer Baykas Liwen Chu Chittabrata Ghosh
Chris Beg Jinyoung Chun Sachin Godbole
Firouz Behnamfar Bruce Chung Bo Gong
Jianwei Bei Chulho Chung Hemamali Gorthi
Yaron Ben Arie Dana Ciochina Fumihide Goto
Friedbert Berens John Coffey Niranjan Grandhe
Christian Berger Carlos Cordeiro Michael Grigat

7
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Xiangxin Gu Sundeep Kancherla Yong Liu
Romain Guignard Srinivas Kandala Zhiqun Liu
Jing Guo HaoHua Kang Vyacheslav Loginov
Yuchen Guo Sugbong Kang Miguel Lopez
Binita Gupta Sudhir Kasargod Mikael Lorgeoux
Raghvendra Gupta Assaf Y. Kasher Hanqing Lou
Luis Gutierrez Oren Kedem Hui-Ling Lou
Muhammad Kumail Haider Richard H. Kennedy Kaiying Lu
David Halasz John Kenney Liuming Lu
Mark Hamilton Stuart J. Kerry Kurt Lumbatis
Xiao Han Naseem Khan Chaoming Luo
Zhiqiang Han Evgeny Khorov Lily Lv
Thomas Handte Jeongki Kim Mikhail Lyakh
Vlado Handziski Myeong-Jin Kim Li Ma
Christopher J. Hansen Sang Gook Kim Mengyao Ma
Daniel N. Harkins Sanghyun Kim Dmitrii Malichenko
Edward Harrison Yongho Kim Jouni K. Malinen
Brian D. Hart Youhan Kim Hiroshi Mano
Victor Hayes Akira Kishida Marcos Martinez Vazquez
Chuanfeng He Shoichi Kitazawa Sebastian Max
Jerome Henry Arik Klein Daniele Medda
Marco Hernandez Andrey Klimakov Morteza Mehrnoush
Lili hervieu Jarkko Kneckt Ezer Melzer
Guido R. Hiertz Geonjung Ko Ebubekir Memisoglu
Ryuichi Hirata Prashant Kota Dignus-Jan Moelker
Duncan Ho Michail Koundourakis Bibhu Mohanty
Oliver Holland Aleksandra Kozarev Pooya Monajemi
Ching-Wen Hsiao Bruce P. Kraemer Michael Montemurro
Hung-Tao Hsieh Chung-Ta Ku Leo Montreuil
Chien-Fang Hsu Manish Kumar Juseong Moon
Warren Kumari Hitoshi Morioka
Ostrovsky Hsu
Hiroyuki Motozuka
Chunyu Hu Chih-Chun Kuo
Robert Mueller
Mengshi Hu Aleksey Kureev
Lakshmi Narayana Mukkapati
Shengquan Hu Massinissa Lalam
Okan Mutgan
Chihan Huang Zhou Lan
Andrew Myles
Guogang Huang Leonardo Lanante
Kengo Nagata
Lei Huang James Lansford
Gaurang Naik
Po-Kai Huang Brice Le Houerou
Hiroki Nakano
Qisheng Huang Hong Won Lee Junyoung Nam
Kazi Mohammed Saidul Huq Hyeong Ho Lee Vamadevan Namboodiri
Sung Hyun Hwang Nancy Lee Nima Namvar
Ahmed Ibrahim Wookbong Lee Sai Shankar Nandagopalan
Tetsushi Ikegami Chris Levesque Narengerile Narengerile
Hirohiko Inohiza Ilya Levitsky Sharan Naribole
Salvador Iranzo Joseph S. Levy Karim Nassiri Toussi
Insun Jang Bo Li Peshal Nayak
Timothy Jeffries Jialing Li Patrice Nezou
Eunsung Jeon Qinghua Li Boon Loong Ng
Chenhe Ji Yan Li An Nguyen
Jia Jia Yapu Li Hiraku Okada
Feng Jiang Yiqing Li Hassan Omar
Jinjing Jiang Yunbo Li Stephen Orr
Hanjin Joh Dong Guk Lim Masatomo Ouchi
Allan Jones Hsin-De Lin Satoshi Oyama
Vincent Knowles Jones IV Wei Lin Basak Ozbakis
Jorge Juarez Yousi Lin Saju Palayur
Volker Jungnickel Zinan Lin Stephen Palm
Ishaque Ashar Kadampot Erik Lindskog Sheetal Pandey
Carl W. Kain Chenchen Liu Thomas Pare
Naveen K. Kakani Der-Zheng Liu Eunsung Park
Manoj Kamath Jianhan Liu Minyoung Park
Mahmoud Kamel Ying Liu Sungjin Park

8
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Abhishek Patil Shimi Shilo Hejun Wang
Gaurav Patwardhan Atsushi Shirakawa Huizhao Wang
Lan Peng Tongxin Shu Lei Wang
Ronny Peng Ulrich Sinn Qi Wang
Eldad Perahia Graham Kenneth Smith Shukun Wang
James E. Petranovich Luther Smith Steven Qi Wang
Albert Petrick Ju-Hyung Son Xiaofei Wang
Brian Petry Hao Song Zisheng Wang
Charlie Pettersson Ayush Sood Roy Want
Ron Porat Robert Sosack Lisa Ward
Dinakar Prabhakaran Sudhir Srinivasa Dong Wei
Henry S. Ptasinski Veena Srivatsa Matthias Wendt
Srinath Puducheri Adrian P. Stephens Menzo M. Wentink
Rethnakaran Pulikkoonattu Noel Stott Leif Wilhelmsson
Rajat Pushkarna Paul Strauch Hao Wu
Emily H. Qi Hang Su Kanke Wu
Saira Rafique Hongjia Su Tianyu Wu
Kapil Rai Jung Hoon Hoon Suh Wayne Wu
Alireza Raissinia Takenori Sumi John Wullert
Enrico-Henrik Rantala Li-Hsiang Sun Qing Xia
Vishnu Ratnam Sheng Sun Bo Xiao
Oded Redlich Yanjun Sun Liangxiao Xin
Kiran Rege Dennis Sundman Yan Xin
Dror Regev Frank Suraci Fangxin Xu
Mor Reich Szymon Szott Weijie Xu
Meriam Rezk Shivkumar Tadahal Yanchao Xu
Maximilian Riegel Mineo Takai Hassan Yaghoobi
Danny Tan Ryota Yamada
Mark Rison
Aiguo Yan
Joerg Robert Yusuke Tanaka
Zhongjiang Yan
Craig Rodine Rakesh Taori
Bo Yang
Benjamin Rolfe Darshak Thakore
Jay Yang
Sayak Roy Sidharth Thakur
Lin Yang
Kiseon Ryu Sri Ramya Thota
Mao Yang
Anirudha Sahoo Francois Thoumy Rui Yang
Mohamed Salem Bin Tian Steve Ts Yang
Hanadi Salman Alexander Tolpin Xun Yang
Sam Sambasivan Alejandro Torrijo Kazuto Yano
Stephan Sand Solomon B. Trainin James Yee
Ioannis Sarris Tsung-Han Tsai Peter Yee
Naotaka Sato Genadiy Tsodik Yongjiang Yi
Takuhiro Sato Yuki Tsujimaru Takahiro Yokoyama
Sigurd Schelstraete Chunjiang Tu Su Khiong Yong
Martin Schmidhammer Halise Turkmen Homin Yoo
Benedikt Schweizer Kiran Uln Jeonghwan Yoon
Andy Scott Paul Unterhuber Yuki Yoshikawa
Jonathan Segev Yoshio Urabe Christopher Young
Sangho Seo Richard D. J. Van Nee Jian Yu
Joseph Seok Allert Van Zelst Fangchao Yuan
Yongho Seok Prabodh Varshney Salah Eddine Zegrar
Nikola Serafimovski Daniel Verenzuela Ruochen Zeng
Ankit Sethi Lochan Verma Jiayi Zhang
Julien Sevin Sindhu Verma Jiayin Zhang
Rubayet Shafin Sameer Vermani Lei Zhou
Amit Shaw Santiago Vicent Colonques Pei Zhou
Andy Shen Pascal Viger Renlong Zhou
Xiaoman Shen Chao Chun Wang Juan Carlos Zuniga
Ian Sherlock Hao Wang Zhisong Zuo

9
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
The following members of the individual balloting committee voted on this revision. Balloters may have
voted for approval, disapproval, or abstention.
Osama S. Aboulmagd David Hunter Bansi Patel
Tomoko Adachi Tetsushi Ikegami Abhishek Patil
Iwan Adhicandra Yasuhiko Inoue Arumugam Paventhan
Carlos H. Aldana Raj Jain Albert Petrick
Thomas Alexander SangKwon Jeong David Piehler
Song-Haur An Pranav Jha Clinton Powell
Amelia Andersdotter Joe Natharoj Juisai Venkatesha Prasad
Carol Ansley Carl W. Kain Kapil Rai
Butch Anton Sugbong Kang Maximilian Riegel
Arthur Arrington Piotr Karocki Benjamin Rolfe
Alfred Asterjadhi John Kenney Jon W. Rosdahl
Kwok Shum Au Stuart J. Kerry Stephan Sand
Oscar Au Evgeny Khorov Naotaka Sato
Tuncer Baykas Yongbum Kim Michael Seaman
Friedbert Berens Youhan Kim Jonathan Segev
Harry Bims Shoichi Kitazawa Robert Sosack
Vern Brethour Jarkko Kneckt Robert Stacey
Koti Reddy Butukuri Jan Kruys Dorothy Stanley
William Byrd Yasushi Kudoh
Noel Stott
Radhakrishna Canchi Thomas Kurihara
Walter Struppler
Rui Cao Gavin Lai
Gerald Stueve
Paul Cardinal James Lansford
Mark Sturza
William Carney Hyeong Ho Lee
James Lepp Bo Sun
Pin Chang
Diana Cortes Joseph S. Levy Jasja Tijink
Claudio Da Silva Jialing Li Payam Torab Jahromi
Di Dieter Dieter Qinghua Li Solomon B. Trainin
Richard Edgar Daozhuang Lin Prabodh Varshney
Alecsander Eitan Jouni K. Malinen John Vergis
Marc Emmelmann Stephen McCann Lochan Verma
Ramy Fathy Jonathon Mclendon Lei Wang
Xiang Feng Michael Montemurro Xiaofei Wang
Avraham Freedman Hiroyuki Motozuka Lisa Ward
Ming Gan Ronald Murias Stephen Webb
Devon Gayle Rick Murphy Dong Wei
James Gilb Rajesh Murthy Matthias Wendt
Rainer Hach Andrew Myles Scott Willy
Xiang He Gaurang Naik Andreas Wolf
Jerome Henry N. Kishor Narang Rui Yang
Marco Hernandez Karim Nassiri Toussi James Yee
Guido R. Hiertz John Notor Yu Yuan
Werner Hoelzl Satoshi Oyama Oren Yuen

When the IEEE SA Standards Board approved this amendment on 3 December 2022, it had the following
membership:
David J. Law, Chair
Ted Burse, Vice Chair
Gary Hoffman, Past Chair
Konstantinos Karachalios, Secretary
Edward A. Addy Johnny Daozhuang Lin Mark Siira
Ramy Ahmed Fathy Kevin Lu Dorothy V. Stanley
J. Travis Griffith Daleep C. Mohla Lei Wang
Guido R. Hiertz Andrew Myles F. Keith Waters
Yousef Kimiagar Damir Novosel Karl Weber
Joseph L. Koepfinger* Annette D. Reilly Sha Wei
Thomas Koshy Robby Robson Philip B. Winston
John D. Kulick Jon Walter Rosdahl Daidi Zhong

*Member Emeritus

10
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Introduction
This introduction is not part of IEEE Std 802.11bd-2022, IEEE 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 5: Enhancements for Next Generation V2X.

This amendment defines modifications to both the IEEE 802.11 physical layer (PHY) and the medium
access control (MAC) sublayer for next generation vehicle-to-everything (V2X) communication in the
5.9 GHz and 60 GHz frequency bands.

11
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Contents
3. Definitions, acronyms, and abbreviations............................................................................................ 18

3.2 Definitions specific to IEEE Std 802.11 .................................................................................. 18

3.4 Abbreviations and acronyms ................................................................................................... 19

4. General description .............................................................................................................................. 19

4.3 Components of the IEEE Std 802.11 architecture ................................................................... 19

4.3.17 STA transmission of Data frames outside the context of a BSS ............................. 19
4.3.17a Next generation vehicle-to-everything (V2X) (NGV) STA .................................... 19
4.3.22 DMG STA................................................................................................................ 20

5. MAC service definition ....................................................................................................................... 23

5.2 MAC data service specification ............................................................................................... 23

5.2.2a NGV MAC data service specification ..................................................................... 23
5.2.3 MA-UNITDATA.request ........................................................................................ 23
5.2.3.2 Semantics of the service primitive ........................................................ 23
5.2.4 MA-UNITDATA.indication .................................................................................... 25
5.2.4.2 Semantics of the service primitive ........................................................ 25
5.2.5 MA-UNITDATA-STATUS.indication.................................................................... 27
5.2.5.2 Semantics of the service primitive ........................................................ 27

6. Layer management............................................................................................................................... 29

6.3 MLME SAP interface .............................................................................................................. 29

6.3.126 Cancel transmissions of MSDUs ............................................................................. 29
6.3.126.1 Introduction........................................................................................... 29
6.3.126.2 MLME-CANCELTX.request ............................................................... 29
6.3.126.3 MLME-CANCELTX.confirm .............................................................. 29
6.3.127 NGV radio environment measurement .................................................................... 30
6.3.127.1 General .................................................................................................. 30
6.3.127.2 MLME-RADIOENVIRONMENT.request........................................... 30
6.3.127.3 MLME-RADIOENVIRONMENT.indication ...................................... 31
6.3.128 DMG operation outside the context of a BSS.......................................................... 31
6.3.128.1 General .................................................................................................. 31
6.3.128.2 MLME-DMG-OCB-START.request.................................................... 31
6.3.128.3 MLME-DMG-OCB-START.confirm................................................... 32
6.3.128.4 MLME-DMG-OCB-STOP.request....................................................... 33
6.3.128.5 MLME-OCB-DMGDISCOVERY.indication....................................... 33
6.3.128.6 MLME-OCB-LINKSTATUS.indication .............................................. 34

9. Frame formats ...................................................................................................................................... 36

9.2 MAC frame formats................................................................................................................. 36

9.2.4 Frame fields ............................................................................................................. 36
9.2.4.7 Frame Body field .................................................................................. 36
9.2.5 Duration/ID field (QoS STA) .................................................................................. 40
9.2.5.1 General .................................................................................................. 40
9.3 Format of individual frame types............................................................................................. 40
9.3.4 Extension frames...................................................................................................... 40

7
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
9.3.4.2 DMG Beacon ........................................................................................ 40
9.4 Management and Extension frame body components ............................................................. 41
9.4.1 Fields that are not elements ..................................................................................... 41
9.4.1.46 DMG Parameters field .......................................................................... 41
9.4.2 Elements................................................................................................................... 41
9.4.2.1 General .................................................................................................. 41
9.4.2.298 Ranging Parameters element................................................................. 42
9.4.2.308 DMG OCB element .............................................................................. 42
9.5 Fields used in Management and Extension frame bodies and Control frames ........................ 43
9.5.3 Sector Sweep Feedback field ................................................................................... 43
9.7 Aggregate MPDU (A-MPDU)................................................................................................. 43
9.7.1 A-MPDU format ...................................................................................................... 43
9.7.3 A-MPDU contents ................................................................................................... 44

10. MAC sublayer functional description.................................................................................................. 43

10.2 MAC architecture .................................................................................................................... 43

10.2.3 Hybrid coordination function (HCF) ....................................................................... 43
10.2.3.2 HCF contention based channel access (EDCA).................................... 43
10.3 DCF.......................................................................................................................................... 43
10.3.6 Group addressed MPDU transfer procedure............................................................ 43
10.12 A-MPDU operation.................................................................................................................. 43
10.12.2 A-MPDU length limit rules ..................................................................................... 43
10.12.4 A-MPDU aggregation of group addressed Data frames .......................................... 44
10.13 PPDU duration constraint ........................................................................................................ 44
10.23 HCF.......................................................................................................................................... 44
10.23.2 HCF contention based channel access (EDCA) ...................................................... 44
10.23.2.8 Multiple frame transmission in an EDCA TXOP ................................. 44
10.23.2.9 TXOP limits .......................................................................................... 44
10.25 Block acknowledgment (block ack) ........................................................................................ 44
10.25.1 Introduction.............................................................................................................. 44
10.25.2 Setup and modification of the block ack parameters ............................................... 45

11. MLME ................................................................................................................................................. 47

11.1 Synchronization ....................................................................................................................... 47

11.1.3 Maintaining synchronization ................................................................................... 47
11.1.3.4 DMG beacon generation before establishment of a BSS...................... 47
11.1.4 Acquiring synchronization, scanning ...................................................................... 47
11.1.4.1 General .................................................................................................. 47
11.1.4.7 DMG discovery outside the context of a BSS ...................................... 47
11.18 STAs communicating Data frames outside the context of a BSS............................................ 49
11.21 Wireless network management procedures ............................................................................. 50
11.21.6 Fine timing measurement (FTM) procedure............................................................ 50
11.21.6.4 Measurement exchange......................................................................... 50
11.27 DMG beamformed link and BSS maintenance........................................................................ 51
11.27.1 Beamformed link maintenance ................................................................................ 51
11.27.1.1 General .................................................................................................. 51

12. Security ................................................................................................................................................ 53

12.13 Preassociation security negotiation.......................................................................................... 53

12.13.1 General..................................................................................................................... 53
12.13.3 Key establishment with PASN authentication......................................................... 53

8
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
12.13.3.1 Overview............................................................................................... 53
12.13.3.2 PASN frame construction and processing ............................................ 53

17. Orthogonal frequency division multiplexing (OFDM) PHY specification ......................................... 55

17.2 OFDM PHY specific service parameter list ............................................................................ 55

17.2.2 TXVECTOR parameters.......................................................................................... 55
17.2.2.1 General .................................................................................................. 55
17.2.2.9 TXVECTOR CH_BANDWIDTH_IN_NON_NGV............................. 55
17.2.2.10 TXVECTOR DYN_BANDWIDTH_IN_NON_NGV ......................... 55
17.2.3 RXVECTOR parameters ......................................................................................... 56
17.2.3.1 General .................................................................................................. 56
17.2.3.9 RXVECTOR CH_BANDWIDTH_IN_NON_NGV ............................ 56
17.2.3.10 RXVECTOR DYN_BANDWIDTH_IN_NON_NGV ......................... 56
17.3 OFDM PHY ............................................................................................................................. 56
17.3.2 PPDU format............................................................................................................ 56
17.3.2.2 Overview of the PPDU encoding process............................................. 56
17.3.5 DATA field .............................................................................................................. 57
17.3.5.5 PHY DATA scrambler and descrambler .............................................. 57

31. Next Generation V2X (NGV) MAC specification .............................................................................. 61

31.1 Introduction.............................................................................................................................. 61
31.2 Operation in the 5.9 GHz band ................................................................................................ 61
31.2.1 Coexistence with non-NGV STAs........................................................................... 61
31.2.2 Channel access and transmission methods for 20 MHz OCB transmission ............ 61
31.2.3 A-MSDU operation, A-MPDU operation, and BA operation ................................. 63
31.2.4 NON_NGV_10 repetition transmission................................................................... 64
31.2.5 Non-NGV duplication operation ............................................................................. 64
31.3 Operation in the 60 GHz band ................................................................................................. 65
31.3.1 DMG beamforming outside the context of a BSS ................................................... 65
31.4 NGV ranging............................................................................................................................ 66
31.5 NGV MAC data service........................................................................................................... 67
31.6 Radio environment measurement ............................................................................................ 68

32. Next Generation V2X (NGV) PHY specification ............................................................................... 69

32.1 Introduction.............................................................................................................................. 69
32.1.1 Introduction to NGV PHY ....................................................................................... 69
32.1.2 Scope........................................................................................................................ 69
32.1.3 NGV PHY functions ................................................................................................ 70
32.1.3.1 General .................................................................................................. 70
32.1.3.2 PHY layer management entity (PLME)................................................ 70
32.1.3.3 Service specification method ................................................................ 70
32.1.4 PPDU Formats ......................................................................................................... 70
32.2 NGV PHY service interface .................................................................................................... 70
32.2.1 Introduction.............................................................................................................. 70
32.2.2 TXVECTOR and RXVECTOR............................................................................... 71
32.2.3 PHY CONFIG_VECTOR........................................................................................ 75
32.2.4 Effects of CH_BANDWIDTH parameter on PPDU format.................................... 76
32.2.5 Support for NON_NGV format ............................................................................... 76
32.2.5.1 General .................................................................................................. 76
32.2.5.2 Support for NON_NGV format ............................................................ 78
32.2.5.3 Repetition transmission of NON_NGV_10 PPDU............................... 79

9
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
32.2.5.4 TXSTATUS parameters........................................................................ 79
32.3 NGV PHY................................................................................................................................ 80
32.3.1 Introduction.............................................................................................................. 80
32.3.2 NGV PPDU format .................................................................................................. 80
32.3.3 Transmitter block diagram....................................................................................... 81
32.3.4 Overview of the PPDU encoding process................................................................ 82
32.3.4.1 General .................................................................................................. 82
32.3.4.2 Construction of L-STF .......................................................................... 83
32.3.4.3 Construction of the L-LTF .................................................................... 83
32.3.4.4 Construction of the L-SIG and RL-SIG................................................ 83
32.3.4.5 Construction of the NGV-SIG and RNGV-SIG ................................... 84
32.3.4.6 Construction of NGV-STF.................................................................... 84
32.3.4.7 Construction of NGV-LTF.................................................................... 85
32.3.4.8 Construction of the Data field in an NGV PPDU ................................. 85
32.3.5 NGV modulation and coding schemes .................................................................... 85
32.3.6 Timing related parameters ....................................................................................... 86
32.3.7 Mathematical description of signals ........................................................................ 87
32.3.7.1 Notation................................................................................................. 87
32.3.7.2 Subcarrier indices in use ....................................................................... 87
32.3.7.3 Transmitted signal................................................................................. 87
32.3.7.4 Definition of tone rotation..................................................................... 90
32.3.8 NGV preamble ......................................................................................................... 91
32.3.8.1 Introduction........................................................................................... 91
32.3.8.2 Cyclic shift ............................................................................................ 91
32.3.8.3 L-STF definition ................................................................................... 91
32.3.8.4 L-LTF definition ................................................................................... 92
32.3.8.5 L-SIG definition.................................................................................... 93
32.3.8.6 RL-SIG definition ................................................................................. 94
32.3.8.7 NGV-SIG definition.............................................................................. 94
32.3.8.8 RNGV-SIG definition ........................................................................... 96
32.3.8.9 NGV-STF definition ............................................................................. 96
32.3.8.10 NGV-LTF definition ............................................................................. 97
32.3.9 Data field................................................................................................................ 101
32.3.9.1 General ................................................................................................ 101
32.3.9.2 SERVICE field.................................................................................... 101
32.3.9.3 Scrambler ............................................................................................ 102
32.3.9.4 Coding................................................................................................. 102
32.3.9.5 Stream parser....................................................................................... 102
32.3.9.6 Constellation mapping ........................................................................ 102
32.3.9.7 Pilot subcarriers................................................................................... 102
32.3.9.8 OFDM modulation.............................................................................. 103
32.3.9.9 Midambles........................................................................................... 105
32.3.9.10 Non-NGV duplicate transmission....................................................... 105
32.3.10 SU-MIMO.............................................................................................................. 106
32.3.11 Transmit specification............................................................................................ 106
32.3.11.1 Transmit spectrum mask ..................................................................... 106
32.3.11.2 Spectral flatness .................................................................................. 107
32.3.11.3 Transmit center frequency and symbol clock frequency tolerance..... 108
32.3.11.4 Modulation accuracy........................................................................... 108
32.3.12 Receiver specification............................................................................................ 110
32.3.12.1 General ................................................................................................ 110
32.3.12.2 Receiver minimum input sensitivity ................................................... 111
32.3.12.3 Adjacent channel rejection.................................................................. 111
32.3.12.4 Nonadjacent channel rejection ............................................................ 113

10
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
32.3.12.5 Receiver maximum input level ........................................................... 113
32.3.12.6 CCA sensitivity ................................................................................... 113
32.3.13 NGV transmit procedure........................................................................................ 114
32.3.14 NGV receive procedure ......................................................................................... 116
32.3.15 Regulatory requirements........................................................................................ 120
32.3.16 NGV ranging NDP................................................................................................. 120
32.4 NGV PLME ........................................................................................................................... 121
32.4.1 PLME-SAP ............................................................................................................ 121
32.4.2 PHY MIB ............................................................................................................... 122
32.4.3 TXTIME and PSDU_LENGTH calculation.......................................................... 122
32.4.4 NGV PHY.............................................................................................................. 123
32.5 Parameters for NGV-MCSs ................................................................................................... 123

Annex B (normative) Protocol Implementation Conformance Statement (PICS) proforma...................... 129

B.2 Abbreviations and special symbols.................................................................................. 129

B.2.2 General abbreviations for Item and Support columns........................................ 129
B.4 PICS proforma—IEEE Std 802.11-2020......................................................................... 129
B.4.3 IUT configuration............................................................................................... 129
B.4.24 DMG features ..................................................................................................... 130
B.4.24.1 DMG MAC features............................................................................ 130
B.4.38 NGV features...................................................................................................... 130
B.4.38.1 NGV MAC features ............................................................................ 130
B.4.38.2 NGV PHY features ............................................................................. 131
B.4.38.3 NGV extended MAC service features................................................. 132

Annex C (normative) ASN.1 encoding of the MAC and PHY MIB .......................................................... 133

C.3 MIB detail ........................................................................................................................ 133

Annex D (normative) Regulatory references.............................................................................................. 145

D.2 Radio performance specifications.................................................................................... 145

D.2.3 Transmit spectrum mask .................................................................................... 145

Annex P (informative) Location and Time Difference accuracy test ......................................................... 147

P.3 Differential Distance Computation using Fine Timing Measurement frames................. 147

11
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Tables
Table 5-1—PPDU format values ................................................................................................................... 24
Table 5-2—Channel width values ................................................................................................................. 25
Table 5-3—RSSI values ................................................................................................................................ 26
Table 9-25—Maximum data unit sizes (in octets) and durations (in microseconds) .................................... 37
Table 9-45—DMG Beacon frame body ........................................................................................................ 40
Table 9-69—The BSS Type subfield when the Discovery mode field is 1................................................... 41
Table 9-92—Element IDs .............................................................................................................................. 41
Table 9-322al—Format and Bandwidth subfield .......................................................................................... 42
Table 17-1—TXVECTOR parameters .......................................................................................................... 55
Table 17-2—RXVECTOR parameters .......................................................................................................... 56
Table 17-7—Contents of the first 7 bits of the scrambling sequence............................................................ 58
Table 17-8a—TXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV values .................................. 59
Table 17-9a—RXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV values.................................. 59
Table 17-10a—DYN_BANDWIDTH_IN_NON_NGV values .................................................................... 59
Table 31-1—Maximum NGV MPDU length ................................................................................................ 63
Table 32-1—TXVECTOR and RXVECTOR parameters............................................................................. 71
Table 32-2— Interpretation of FORMAT, NON_NGV_MODULATION, and CH_BANDWIDTH
parameters .............................................................................................................................. 76
Table 32-3—Mapping of the NGV PHY parameters for non-NGV operation ............................................. 78
Table 32-4—TXSTATUS parameters ........................................................................................................... 79
Table 32-5—Fields of the NGV PPDU ......................................................................................................... 80
Table 32-6—Timing related constants .......................................................................................................... 86
Table 32-7—Frequently used parameters...................................................................................................... 87
Table 32-8—Tone scaling factor and guard interval duration values for PHY fields ................................... 90
Table 32-9—CH_BANDWIDTH.................................................................................................................. 90
Table 32-10—Fields in the NGV-SIG field .................................................................................................. 95
Table 32-11—Number of NGV-LTFs required for different numbers of spatial streams ............................ 97
Table 32-12—SERVICE field ..................................................................................................................... 101
Table 32-13—Spectrum mask data for 20 MHz channel spacing ............................................................... 107
Table 32-14—Maximum transmit spectral flatness deviations ................................................................... 108
Table 32-15—Allowed relative constellation error versus constellation size and coding rate.................... 109
Table 32-16—Receiver minimum input level sensitivity............................................................................ 111
Table 32-17—Minimum required adjacent and nonadjacent channel rejection level ................................. 112
Table 32-18—Optional enhanced minimum required adjacent and nonadjacent channel rejection level .. 112
Table 32-19—NGV PHY MIB attributes .................................................................................................... 121
Table 32-20—NGV PHY characteristics .................................................................................................... 123
Table 32-21—NGV-MCSs for 10 MHz, NSS = 1....................................................................................... 124
Table 32-22—NGV-MCSs for 10 MHz, NSS = 2....................................................................................... 124
Table 32-23—NGV-MCSs for 20 MHz, NSS = 1....................................................................................... 125
Table 32-24—NGV-MCSs for 20 MHz, NSS = 2....................................................................................... 125

13
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Figures
Figure 9-79—Clustering Control field format if the Discovery Mode is 1 ................................................... 40
Figure 9-788fm—DMG OCB element format .............................................................................................. 42
Figure 9-788fn—DMG OCB Parameters field format .................................................................................. 42
Figure 9-848—SSW Feedback field format when transmitted as part of an ISS .......................................... 43
Figure 9-849a—SSW Feedback field format when not transmitted as part of an ISS and the
EDMG Extension Flag subfield is 0 ...................................................................................... 43
Figure 11-10a—DMG discovery outside the context of a BSS..................................................................... 48
Figure 11-10b—Beamforming training during the DMG discovery outside the context of a BSS .............. 49
Figure 17-7—Data scrambler ........................................................................................................................ 57
Figure 32-1—PHY interaction on transmit for various PPDU formats......................................................... 77
Figure 32-2—PHY interaction on receive for various PPDU formats .......................................................... 77
Figure 32-3—PHY-CONFIG and CCA interaction with Clause 17 and Clause 32...................................... 78
Figure 32-4—Example of NON_NGV_10 repetition transmission with N_PPDU_REP = 2 ...................... 79
Figure 32-5—NGV PPDU format ................................................................................................................. 80
Figure 32-6—Transmitter block diagram for the L-SIG, RL-SIG, NGV-SIG, and RNGV-SIG fields
for an NGV PPDU ................................................................................................................. 82
Figure 32-7—Transmitter block diagram for the Data field of an NGV transmission.................................. 82
Figure 32-8—Timing boundaries for NGV PPDU fields .............................................................................. 88
Figure 32-9—Generation of NGV-LTF symbols .......................................................................................... 99
Figure 32-10—Generation of NGV-LTF-1x symbols................................................................................... 99
Figure 32-11—Generation of NGV-LTF-2x-Repeat symbols .................................................................... 100
Figure 32-12—NGV PPDU with midamble and randomization procedure................................................ 105
Figure 32-13—PHY transmit procedure for NGV transmission ................................................................. 114
Figure 32-14—PHY transmit state machine................................................................................................ 116
Figure 32-15—PHY receive procedure for NGV transmission................................................................... 117
Figure 32-16—PHY receive state machine ................................................................................................. 118
Figure 32-17—NGV ranging NDP format .................................................................................................. 120
Figure 32-18—Example of NGV-LTF with NSS = 2 and LTF_REP = 1................................................... 121

12
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
IEEE 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 5:
Enhancements for Next Generation V2X

(This amendment is based on IEEE Std 802.11™-2020 as amended by IEEE Std 802.11ax™-2021,
IEEE Std 802.11ay™-2021, IEEE Std 802.11ba™-2021, IEEE Std 802.11™-2020/Cor 1-2022, and
IEEE Std 802.11az™-2022.)

NOTE—The editing instructions contained in this amendment define how to merge the material contained therein into
the existing base standard and its amendments to form the comprehensive standard.

The editing instructions are shown in bold italic. Four editing instructions are used: change, delete, insert, and replace.
Change is used to make corrections in existing text or tables. The editing instruction specifies the location of the change
and describes what is being changed by using strikethrough (to remove old material) and underscore (to add new
material). Delete removes existing material. Insert adds new material without disturbing the existing material. Insertions
may require renumbering. If so, renumbering instructions are given in the editing instruction. Replace is used to make
changes in figures or equations by removing the existing figure or equation and replacing it with a new one. Editorial
instructions, change markings and this NOTE will not be carried over into future editions because the changes will be
incorporated into the base standard.6

6
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.

17
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
IEEE Std 802.11bd-2022
IEEE Standard for Information Technology—Local and Metropolitan Area Networks—Specific Requirements—
Part 11: Wireless LAN MAC and PHY Specifications—
Amendment 5: Enhancements for Next Generation V2X

3. Definitions, acronyms, and abbreviations

3.2 Definitions specific to IEEE Std 802.11

Change the definition for “dynamic bandwidth operation” in 3.2 as follows:

dynamic bandwidth operation: A feature of a very high throughput (VHT) station (STA) or a next
generation vehicle-to-everything (NGV) STA in which the request-to-send/clear-to-send (RTS/CTS)
exchange, using non-high-throughput (non-HT) duplicate physical layer (PHY) protocol data units (PPDUs)
or non-NGV duplicate PPDUs, negotiates a potentially reduced channel width (compared to the channel
width indicated by the RTS) for subsequent transmissions within the current transmission opportunity
(TXOP).

Change the definition for “bandwidth signaling transmitter address (TA)” (as amended by IEEE Std
802.11ax-2021) in 3.2 as follows:

bandwidth signaling transmitter address (TA): A TA that is used by a very high throughput (VHT)
station (STA), or a high-efficiency (HE) STA, or a next generation vehicle-to-everything (NGV) STA to
indicate the presence of additional signaling related to the bandwidth to be used in subsequent transmission
in an enhanced distributed channel access (EDCA) transmission opportunity (TXOP). It is the IEEE medium
access control (MAC) individual address of the transmitting VHT STA but with the Individual/Group bit
equal to 1.

Insert the following definitions in 3.2 in alphabetical order:

non-next generation vehicle-to-everything (V2X) (non-NGV) duplicate: A transmission format of the

physical layer (PHY) that duplicates a 10 MHz non-NGV transmission in two adjacent 10 MHz channels
and allows a station (STA) communicating outside the context of a basic service set (BSS)(OCB) on either
of the 10 MHz channels to receive the transmission.

non-next generation vehicle-to-everything (V2X) (non-NGV) physical layer (PHY) protocol data unit
(PPDU): A PPDU with 10 MHz channel width that is transmitted outside the context of a basic service set
(BSS) (OCB) in the 5.9 GHz band and that is not a next generation V2X (NGV) PPDU.

non-next generation vehicle-to-everything (V2X) (non-NGV) station (STA): A STA that transmits or
receives non-NGV physical layer (PHY) protocol data units (PPDUs) and that is not able to transmit next
generation V2X (NGV) PPDUs.

next generation vehicle-to-everything (V2X) (NGV) physical layer (PHY) protocol data unit (PPDU):
A Clause 32 PPDU with the TXVECTOR parameter FORMAT equal to NGV or NON_NGV_10.

outside the context of a basic service set (OCB) primary channel: A 10 MHz channel that is designated
by a higher layer (via medium access control (MAC) sublayer management entity (MLME) primitives
and/or management information base (MIB) parameters). The OCB primary channel and OCB secondary
channel are contiguous and together form a 20 MHz channel for transmission of 20 MHz next generation
vehicle-to-everything (V2X) (NGV) physical layer (PHY) protocol data units (PPDUs).

outside the context of a basic service set (OCB) secondary channel: A 10 MHz channel that is designated
by a higher layer (via medium access control (MAC) sublayer management entity (MLME) primitives
and/or management information base (MIB) parameters). The OCB secondary channel and the OCB
primary channel are contiguous and together form a 20 MHz channel for the transmission of 20 MHz next
generation vehicle-to-everything (V2X) (NGV) physical layer (PHY) protocol data units (PPDUs).

18
Copyright © 2023 IEEE. All rights reserved.

3.4 Abbreviations and acronyms

Insert the following abbreviations in 3.4 in alphabetical order:

NGV next generation vehicle-to-everything (V2X)
V2X vehicle-to-everything

19
Copyright © 2023 IEEE. All rights reserved.

4. General description

4.3 Components of the IEEE Std 802.11 architecture

4.3.17 STA transmission of Data frames outside the context of a BSS

Insert the following paragraphs after the fourth paragraph of 4.3.17 (beginning “Communication of
Data frames …”):

A STA with dot11OCBActivated equal to true might operate as a DMG STA. A DMG STA with
dot11DMGOCBActivated equal to true supports the MAC and MLME functions defined in 31.3 in addition
to the MAC functions defined in Clause 10 and the MLME functions defined in Clause 11 for DMG STAs.
A DMG STA operating OCB might support EDMG features.

A STA whose MIB does not include the dot11DMGOCBActivated attribute operates as if the attribute is
false.

Insert 4.3.17a after 4.3.17 as follows:

4.3.17a Next generation vehicle-to-everything (V2X) (NGV) STA

A next generation vehicle-to-everything (NGV) STA provides MAC and PHY features as defined in
Clause 31 and Clause 32. An NGV STA supports at least twice the throughput and at least 3 dB better
receiver minimum input sensitivity than a non-NGV STA when operating OCB in high mobility channel
environments in the 5.9 GHz band as defined in E.2.3 and E.2.4. The double throughput and higher receiver
minimum input sensitivity might not be supported simultaneously. In an NGV STA
dot11NGVOptionImplemented is true. In a non-NGV STA with dot11NGVOptionImplemented, the
attribute is false. A STA whose MIB does not include the dot11NGVOptionImplemented attribute operates
as if the attribute is false.

An NGV STA might be co-located with a DMG STA for which dot11DMGOCBActivated is true in the
60 GHz frequency band (57 GHz to 71 GHz) as defined in E.1. The NGV STA might assist the DMG STA
in performing DMG discovery OCB by communicating with a peer NGV STA to exchange the higher layer
information that contains information of a peer DMG STA with which the peer NGV STA is co-located. The
information is provided from/to a DMG STA through the MLME SAP interface. The protocol to exchange
this higher layer information is outside the scope of this standard.

An NGV STA supports interoperability, coexistence, backward compatibility, and fairness in contending for
the medium with non-NGV STAs when operating OCB in the 5.9 GHz band. An NGV STA is also a
non-NGV STA that supports transmission and reception of non-NGV PHY PPDUs when operating OCB in
the 5.9 GHz band.

An NGV STA is capable of transmitting and receiving frames OCB as specified in 11.18.

The main PHY features of an NGV STA that are not present in a non-NGV STA are the following:
— Mandatory support for the 10 MHz NGV PPDU format and optional support for the 20 MHz NGV
PPDU and 20 MHz non-NGV duplicate PPDU formats
— For the 20 MHz and 10 MHz NGV PPDU, mandatory support for LDPC coding, midambles,
BPSK-DCM, and 256-QAM
— Mandatory support for transmit spectral mask C2 by a STA that transmits a 20 MHz NGV PPDU or
20 MHz non-NGV duplicate PPDU
— Mandatory support for repetitive NON_NGV_10 PPDU

19
Copyright © 2023 IEEE. All rights reserved.

— Mandatory support for coexistence with non-NGV STAs operating in the same channel
— Mandatory support for transmit spectral mask C by a STA that transmits a 10 MHz NGV PPDU and
belongs to transmit power class C
— Optional support for transmission and reception of SU MIMO with two spatial streams

Additional NGV STA PHY features are:

— Mandatory support for a single spatial stream
— Mandatory support for Clause 17 10 MHz PPDU
— Optional support for Classes A, B, and D of spectrum mask requirement for 10 MHz bandwidth

The main MAC features of an NGV STA that are not present in a non-NGV STA are the following:
— Mandatory support for coexistence with non-NGV STAs operating in the same channel
— Mandatory support for extended MAC service interface to provide higher layers with the ability to
control NGV transmissions and receive status regarding NGV receptions and the radio environment
— Mandatory support for NGV capability indication for non-NGV PPDUs encoded in the Duration/ID
field of the MAC header
— Mandatory support for block ack
— Mandatory support for reception of frame aggregation when communicating OCB
— Optional support for transmission of frame aggregation when communicating OCB
— Optional support for 20 MHz OCB communication
— For optional 20 MHz OCB communication an NGV STA supports 20 MHz channel access with
10 MHz primary and 10 MHz secondary channels
— Optional support for 20 MHz non-NGV duplicate operation

Additional NGV STA MAC features are:

— Mandatory support for 10 MHz OCB communication

An NGV STA might support positioning based on NGV ranging, which consists of a subset of fine timing
measurement (FTM) functionalities as defined in 11.21.6 and P.3:
— Fine timing Measurement procedure negotiation and termination for non-TB ranging as defined in
11.21.6.3 and non-TB ranging as described in 11.21.6.4.4
— Differential distance computation as detailed in P.3

An NGV STA might be co-located with a STA operating outside the 5.9 GHz band that supports the fine
timing measurement procedure as defined in 11.21.6.

4.3.22 DMG STA

Change the first paragraph of 4.3.22 as follows:

The IEEE 802.11 DMG STA provides PHY and MAC features that can support a throughput of 1 Gb/s and
greater, as measured at the MAC data service access point (SAP). A DMG STA supports DMG features as
identified in Clause 10, Clause 11, and Clause 20. Optionally, a DMG STA with dot11DMGOCBActivated
equal to true supports features as identified in 31.3. A DMG STA operates in a DMG BSS and supports
transmission and reception of frames that are compliant with PHY specifications as defined in Clause 20. A
DMG STA is also a QoS STA. The basic channel access of a DMG STA (see 10.39) allows it to operate in
an Infrastructure BSS, in an IBSS, and in a PBSS. Certain DMG features such as service period allocation
are available only to DMG STAs that are associated with an AP or with a PCP, while other DMG features
such as EDCA operation in a PBSS and DMG STAs operating OCB do not require association. A DMG

20
Copyright © 2023 IEEE. All rights reserved.

STA supports beamforming (BF) as described in 10.42 and 20.9 and GCM encryption as described in
12.5.5.

Change the third paragraph of 4.3.22 (as amended by IEEE Std 802.11ay-2021) as follows:

A DMG STA supports MAC features that provide channel access in an environment in which transmissions
use a directional antenna pattern. The MAC entity of a DMG STA provides frame aggregation, block
acknowledgement acknowledgment, service periods, contention based access periods, DMG protected
period, AP or PCP clustering, dynamic channel time management (see 10.39.7, 10.39.8, and 10.39.9),
reverse direction, spatial sharing, beamforming, discovery assistance, TDD channel access, and fast session
transfer in a multi-band device, transmission of Data frames OCB (see 11.18), and DMG discovery OCB
(see 11.1.4.7). A DMG STA is not a mesh STA. A DMG STA does not use any of the following: HCCA,
power save multi-poll (PSMP), TDLS, GCR.

21
Copyright © 2023 IEEE. All rights reserved.

5. MAC service definition

5.2 MAC data service specification

Insert 5.2.2a after 5.2.2 as follows:

5.2.2a NGV MAC data service specification

An NGV STA coordinates with higher layer ITS entities (e.g., IEEE 1609 [B22] family of standards) to
provide wireless communications services via the LLC sublayer. The MA-UNITDATA primitives contain
the radio environment request vector to facilitate the coordination.

5.2.3 MA-UNITDATA.request

5.2.3.2 Semantics of the service primitive

Change the first paragraph of 5.2.3.2 as follows:

The parameters of the primitive are as follows:

MA-UNITDATA.request(
source address,
destination address,
routing information,
data,
priority,
drop eligible,
service class,
station vector,
MSDU format,
radio environment request vector
)

Insert the following at the end of 5.2.3.2:

The radio environment request vector parameter contains information that allows higher layer entities to
configure the PPDU format, encoding, and MPDU handling for NGV transmission. This parameter is
present when dot11NGVOptionImplemented is true or dot11NONNGVRadioEnvironmentImplemented is
true, and absent otherwise.

The radio environment request vector parameter contains the following members pertaining to the
transmission of the MPDU that contains the MSDU associated with the request containing the vector:
— PPDU format (non-NGV/NGV)
— data rate/NGV-MCS
— number of spatial streams
— permitted aggregation
— number of repetitions
— expiry time
— channel
— primary channel
— channel width

23
Copyright © 2023 IEEE. All rights reserved.

— fallback enabled
— transmit power spectral density

The PPDU format member indicates the format of the PPDU as defined in Table 5-1 that is used to transmit
the MSDU.

Table 5-1—PPDU format values

PPDU format value Description

0 Non-NGV PPDU

1 NGV PPDU

2 The PPDU format decided by the MAC layer

The data rate/NGV-MCS member indicates the data rate of the PPDU carrying the MSDU if the PPDU
format has value 0. The data rate can be either 0 (decided by MAC layer), 3 Mb/s, 4.5 Mb/s, 6 Mb/s, 9 Mb/s,
12 Mb/s, 18 Mb/s, 24 Mb/s, or 27 Mb/s as defined in Table 17-4. If the PPDU format has value 1, the data
rate/NGV-MCS member indicates the NGV-MCS index as defined in 32.5 with an exception that the value
14 means that the actual MCS is decided by the MAC layer. If the PPDU format has value 2, the data
rate/NGV-MCS member is set to value 14 indicating that the actual data-rate/MCS is decided by the MAC
layer.

The number of spatial streams member with value 1 or 2 indicates the number of spatial streams being used
to transmit the PPDU carrying the MSDU. The number of spatial streams member with value 0 means that
the number of spatial streams is decided by the MAC layer. The permitted aggregation member indicates
whether A-MPDU aggregation can be applied to the MSDU. The value 0 means that aggregation is not
applied, the value 1 means that aggregation can be applied, while the value 2 means that it is up to the MAC
layer to decide whether the aggregation can be applied.

The number of repetitions member indicates the maximal number of repetitions that can be used to transmit
the MSDU in a broadcast MPDU of a non-NGV PPDU in a 10 MHz channel width where the values can be
in the range 0 to 3 or 15. The value 15 means that it is up to the MAC layer to decide whether the repetition
is applied to the MSDU. This parameter is reserved when the MSDU is not in a broadcast MPDU in 10 MHz
channel width.

The expiry time member indicates the time in milliseconds until the MSDU is discarded if still not
transmitted, where the value 0 means that it is up to the MAC layer to decide the expiry time of the MSDU.
NOTE 1—When an MSDU reaches its expiry time and is discarded, the CW state variable of the EDCAF associated
with that MSDU is unchanged.

The channel member indicates the channel where the MSDU is transmitted in the 5.9 GHz band as defined
in E.2.3 and E.2.4 with the exception for value 0, which means that the MAC layer selects the channel.

The primary channel indicates the primary 10 MHz channel where the MSDU is transmitted, where the
value 0 means that the MAC layer selects the primary channel. This member is present when
dot11NGVOptionImplemented is true and when the channel width member is 20 MHz and is absent
otherwise.

The channel width member indicates either 10 MHz or 20 MHz channel width used to transmit the MSDU
as defined in Table 5-2. When the channel width indicates 20 MHz, the primary channel member indicates
the OCB primary channel.

24
Copyright © 2023 IEEE. All rights reserved.

NOTE 2—An NGV STA transmitting in a 20 MHz channel maintains a single primary channel at any given time.

Table 5-2—Channel width values

Channel width value Description

0 10 MHz

1 20 MHz

2 The channel width is decided by the MAC layer

The fallback enabled member indicates whether the transmission of a 10 MHz PPDU in the OCB primary
channel is allowed by an NGV STA while the NGV STA performs channel access to transmit a 20 MHz
NGV PPDU. The value 0 means that the fallback to 10 MHz can be applied to the MSDU, the value 1 means
that the fallback to 10 MHz cannot be applied to the MSDU, while the value 3 means that it is up to the
MAC layer to decide whether the fallback is applied to the MSDU. This member is present when
dot11NGVOptionImplemented is true and when the channel width member is 20 MHz and is absent
otherwise.

The transmit power spectral density member indicates the combined transmit power at the transmit antenna
connector of all the antennas used to transmit the MSDU in units of dBm/10 MHz. The transmit power is
described with a resolution of 1 dB, with values in the range 0 to 60 representing –20 dBm/10 MHz to
40 dBm/10 MHz, respectively. Values from 61 to 126 are reserved. The value 127 means that it is up to the
MAC layer to decide the transmit power of the MSDU.

5.2.4 MA-UNITDATA.indication

5.2.4.2 Semantics of the service primitive

Change the first paragraph of 5.2.4.2 as follows:

The parameters of the primitive are as follows:

MA-UNITDATA.indication(
source address,
destination address,
routing information,
data,
reception status,
priority,
drop eligible,
service class,
station vector,
MSDU format,
radio environment status vector
)

Insert the following at the end of 5.2.4.2:

The radio environment status vector parameter provides information to higher layer entities about the
current radio environment and the most recent reception. This parameter is present when
dot11NGVOptionImplemented is true or dot11NONNGVRadioEnvironmentImplemented is true, and
absent otherwise.

25
Copyright © 2023 IEEE. All rights reserved.

The radio environment status vector parameter contains the following members pertaining to the reception
of the MPDU that contained the MSDU associated with the indication containing the vector:
— PPDU format (non-NGV/NGV)
— data rate/NGV-MCS
— aggregation
— channel
— primary channel
— channel width
— RSSI

The PPDU format member indicates the format of the received PPDU that carries the MSDU as defined in
Table 5-1.

The data rate/NGV-MCS member indicates the data rate of the PPDU carrying the MSDU if the PPDU
format has value 0. The data rate can be one of 3 Mb/s, 4.5 Mb/s, 6 Mb/s, 9 Mb/s, 12 Mb/s, 18 Mb/s,
24 Mb/s, or 27 Mb/s as defined in Table 17-4. If the PPDU format has value 1, the data rate/NGV-MCS
member indicates the NGV-MCS index as defined in 32.5.

The aggregation member indicates whether A-MPDU aggregation is applied to the received MSDU. The
value 0 means that aggregation is not applied, while the value 1 means that aggregation is applied.

The primary channel member indicates the primary 10 MHz channel where the MSDU is received.

The channel width member indicates either 10 MHz or 20 MHz channel width of the PPDU carrying the
received MSDU as defined in Table 5-2. When the channel width indicates 20 MHz, the primary channel
parameter indicates the OCB primary channel.

The RSSI parameter indicates the receive signal power, measured at the STA’s antenna connector and
averaged over the antennas, for the NGV portion of the received NGV PPDU and is defined in Table 5-3.

Table 5-3—RSSI values

RSSI Description

0 to 90 The RSSI, in units of dBm, is –113 + F val , where

F val is the subfield value
91 to 127 Reserved

26
Copyright © 2023 IEEE. All rights reserved.

5.2.5 MA-UNITDATA-STATUS.indication

5.2.5.2 Semantics of the service primitive

Change the first paragraph of 5.2.5.2 as follows:

The parameters of the primitive are as follows:

MA-UNITDATA-STATUS.indication(
source address,
destination address,
transmission status,
provided priority,
provided service class,
radio environment request vector
)

Insert the following at the end of 5.2.5.2:

The radio environment request vector parameter (see 5.2.3.2) contains information that is used by the MAC
entity to report the used format, encoding, and MPDU handling for NGV transmission. This parameter is
present when dot11NGVOptionImplemented is true or dot11NONNGVRadioEnvironmentImplemented is
true, and absent otherwise.

27
Copyright © 2023 IEEE. All rights reserved.

6. Layer management

6.3 MLME SAP interface

Insert 6.3.126, 6.3.127, and 6.3.128 after 6.3.125 (inserted by IEEE Std 802.11ba-2021) as
follows:

6.3.126 Cancel transmissions of MSDUs

6.3.126.1 Introduction

This primitive allows higher layer entities (e.g., entities based on the IEEE 1609 [B22] family of standards)
to cancel transmission of MSDUs that were previously sent to the STA and are still in the MAC entity’s
transmit queue.

6.3.126.2 MLME-CANCELTX.request

6.3.126.2.1 Function

Requests cancellation of transmission of all queued MSDUs belonging to the specified access category.

6.3.126.2.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-CANCELTX.request(
AccessCategoryIndex
)

Name Type Valid range Description

AccessCategoryIndex Integer 0–4 Specifies the access category index of the
MSDUs that are to be removed from the
transmit queue. Index 0–3 is the value of the
access category in Table 9-283 and index 4
indicates all access categories.

6.3.126.2.3 When generated

This primitive is generated by the SME when the SME receives a request (from a higher layer entity) to
remove MSDUs from the transmit queue.

6.3.126.2.4 Effect of receipt

The receipt of this primitive by the MAC entity causes the MAC entity to remove MSDUs of the specified
access category index from the transmit queue.

6.3.126.3 MLME-CANCELTX.confirm

6.3.126.3.1 Function

This primitive reports completion of the removal of MSDUs from the transmit queue.

29
Copyright © 2023 IEEE. All rights reserved.

6.3.126.3.2 Semantics of the service primitive

This primitive has no parameters.

6.3.126.3.3 When generated

The primitive is generated by the MLME to inform the SME that an MLME-CANCELTX.request primitive
has been completed, so that the SME can inform the requesting entity (a higher layer entity).

6.3.126.3.4 Effect of receipt

The SME is notified that the MAC entity has removed MSDUs of the specified access category from the
transmit queue.

6.3.127 NGV radio environment measurement

6.3.127.1 General

This primitive provides a report on the STA’s radio environment.

6.3.127.2 MLME-RADIOENVIRONMENT.request

6.3.127.2.1 Function

This primitive is used to request the status information on the state of the STA’s radio environment.

6.3.127.2.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-RADIOENVIRONMENT.request (
RadioEnvironmentMeasurementPeriod,
StationMeasurementPeriod
)

Name Type Valid range Description

RadioEnvironmentMeasure Integer 0 or 100–1000 Specifies the amount of time in milliseconds
mentPeriod during which the NGV STA measures the
channel busy percentage measurement. When
equal to 0, measurements are not made.
StationMeasurementPeriod Integer 0 or 100–1000 Specifies the amount of time in milliseconds
during which the NGV STA measures the
number of neighboring STAs and the number of
neighboring NGV STAs. When equal to 0,
measurements are not made.

6.3.127.2.3 When generated

The primitive is generated when a higher layer entity wants to acquire the status information on the state of
the STA’s radio environment.

30
Copyright © 2023 IEEE. All rights reserved.

6.3.127.3 MLME-RADIOENVIRONMENT.indication

6.3.127.3.1 Function

This primitive provides status information on the state of the STA’s radio environment.

6.3.127.3.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-RADIOENVIRONMENT.indication(
StationCount,
NGVCapabilityPercentage,
ChannelBusyPercentage
)

Name Type Valid range Description

StationCount Integer 0–65 535 Indicates the number of unique individual
station MAC addresses detected during the
most recent measurement period of duration
dot11RadioEnvironmentMeasurementPeriod.
NGVCapabilityPercentage Integer 0–100 Indicates the percentage of the stations
indicated in StationCount whose transmissions
contain indication of NGV capability. When
StationCount is equal to 0, the
NGVCapabilityPercentage shall be set to 0.
ChannelBusyPercentage Integer 0–100 The percentage of time the channel was busy
during the most recent measurement of duration
dot11RadioEnvironmentMeasurementPeriod.
The channel is busy when the NGV STA is
either transmitting or its clear channel
assessment function indicates the channel is
busy. It is calculated as follows:
100  duration as indicated channel busy
-----------------------------------------------------------------------------------------------------------
dot11RadioEnvironmentMeasurementPeriod

6.3.127.3.3 When generated

The primitive is generated by the MAC entity every dot11RadioEnvironmentMeasurementPeriod if

dot11NGVOptionImplemented is true.

6.3.128 DMG operation outside the context of a BSS

6.3.128.1 General

The following primitives support DMG operation outside the context of a BSS.

6.3.128.2 MLME-DMG-OCB-START.request

6.3.128.2.1 Function

This primitive requests the MAC entity to initiate DMG operation outside the context of a BSS.

31
Copyright © 2023 IEEE. All rights reserved.

6.3.128.2.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-DMG-OCB-START.request(
Channel number,
Discovery beacon,
DMG parameters,
DMG capabilities,
EDMG capabilities,
Unsolicited Block Ack Extension,
VendorSpecificInfo
)

Name Type Valid range Description

Channel number Integer Selected from the Specifies a channel number to perform
valid channel range discovery for peer STAs outside the context of a
for the appropriate BSS.
PHY and carrier set.
Discovery beacon Boolean true, false Indicates whether the STA is required to
transmit DMG Beacon frames to discover peer
STAs.
DMG parameters As defined in As defined in 9.3.4.2 Specifies the parameters to be advertised to peer
frame format STAs.
DMG capabilities As defined in As defined in Specifies the parameters to be advertised to peer
frame format 9.4.2.127 STAs.
EDMG capabilities As defined in As defined in Specifies the parameters to be advertised to peer
frame format 9.4.2.265 STAs.
Optionally present if
dot11EDMGOptionImplemented is true and is
absent otherwise.
Unsolicited Block Unsolicited As defined in Specifies the parameters within the Unsolicited
Ack Extension Block Ack 9.4.2.279 Block Ack Extension element that are
Extension supported by the MAC entity. Optionally
element present if dot11UnsolicitedBAActivated is true
and is absent otherwise.
VendorSpecificInfo A set of As defined in 9.4.2.25 Zero or more elements.
elements

6.3.128.2.3 When generated

The primitive is generated by the SME for a STA to initiate DMG operation outside the context of a BSS.

6.3.128.2.4 Effect of receipt

The primitive initiates a discovery procedure and data transmission outside the context of a BSS.

6.3.128.3 MLME-DMG-OCB-START.confirm

6.3.128.3.1 Function

This primitive reports the result of the initiation of a DMG operation outside the context of a BSS.

6.3.128.3.2 Semantics of the service primitive

The primitive parameters are as follows:

32
Copyright © 2023 IEEE. All rights reserved.

MLME-DMG-OCB-START.confirm(
ResultCode,
VendorSpecificInfo
)

Name Type Valid range Description

ResultCode Enumeration SUCCESS, Indicates the result of the
NOT_SUPPORTED MLME-DMG-OCB-START.request primitive.
VendorSpecificInfo A set of As defined in 9.4.2.25 Zero or more elements.
elements

6.3.128.3.3 When generated

The primitive is generated by the MLME as a result of an MLME-DMG-OCB-START.request primitive to

initiate a discovery procedure and data transmission outside the context of a BSS.

6.3.128.3.4 Effect of receipt

The SME is notified of the result of the initiation of a DMG operation outside the context of a BSS.

6.3.128.4 MLME-DMG-OCB-STOP.request

6.3.128.4.1 Function

This primitive requests the MAC entity to stop the DMG operation outside the context of a BSS previously
started by using an MLME-DMG-OCB-START.request.

6.3.128.4.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-DMG-OCB-STOP.request()

6.3.128.4.3 When generated

This primitive is generated by the SME to terminate discovery procedure and data transmission operating
outside the context of a BSS by the MAC entity. The MLME-DMG-OCB-STOP.request primitive shall be
generated only after the SME receives an MLME-DMG-OCB-START.confirm primitive with result code
equal to SUCCESS.

6.3.128.4.4 Effect of receipt

This request terminates the DMG operation outside the context of a BSS when the current frame exchange
sequence is completed.

6.3.128.5 MLME-OCB-DMGDISCOVERY.indication

6.3.128.5.1 Function

This primitive indicates discovery of peer DMG STAs outside the context of a BSS.

6.3.128.5.2 Semantics of the service primitive

The primitive parameters are as follows:

33
Copyright © 2023 IEEE. All rights reserved.

MLME-OCB-DMGDISCOVERY.indication(
PeerInfoSet,
VendorSpecificInfo
)

Name Type Valid range Description

PeerInfoSet Set of N/A The PeerInfoSet is returned to indicate the
PeerInfo results of the discovery request outside the
vectors as context of a BSS as described in 11.1.4.7. It is a
defined set containing zero or more instances of a
below PeerInfo vector.
VendorSpecificInfo A set of As defined in 9.4.2.25 Zero or more elements.
elements

Each PeerInfo vector consists of the parameters shown in the following table, in which the term peer STA
refers to the STA that transmitted the received DMG Beacon frame, SSW frame, SSW Feedback frame, or
SSW Ack frame.

Name Type Valid range Description

PeerSTAAddress MAC address Any valid individual Specifies the MAC address of the discovered
MAC address peer STA.
Sector sweep As defined in As defined in 9.3.4.2 The values from the Sector Sweep field from
frame format the DMG Beacon frame, else null.
Sector sweep As defined in As defined in 9.5.3 The values from the Sector Sweep field from
feedback frame format the SSW, SSW Feedback, or SSW Ack frame,
else null.
DMG parameters As defined in As defined in 9.3.4.2 The values from the DMG Parameters field
frame format from the DMG Beacon frame, else null.
DMG capabilities As defined in As defined in The values from the DMG Capabilities element
frame format 9.4.2.127 if such an element was present in the DMG
Beacon frame, else null.
EDMG capabilities As defined in As defined in Specifies the parameters within the EDMG
frame format 9.4.2.265 Capabilities element that are supported by the
MAC entity.

6.3.128.5.3 When generated

This primitive is generated by the MLME when the MAC entity successfully completes the beamforming
training with the discovered peer MAC entities.

6.3.128.5.4 Effect of receipt

The SME is notified of the discovered peer MAC entities.

6.3.128.6 MLME-OCB-LINKSTATUS.indication

6.3.128.6.1 Function

This primitive indicates the status change of beamformed link with a peer STA.

6.3.128.6.2 Semantics of the service primitive

The primitive parameters are as follows:

34
Copyright © 2023 IEEE. All rights reserved.

MLME-OCB-LINKSTATUS.indication(
PeerSTAAddress,
BeamLinkStatus,
VendorSpecificInfo
)

Name Type Valid range Description

PeerSTAAddress MAC address Any valid individual The MAC address of the STA that is the peer
MAC address STA in the beamformed link being reported on.
BeamLinkStatus Enumeration ESTABLISHED, Indicates the status of beamformed link as
TIMER_EXPIRED, described in 11.27.1.1.
NOT_ESTABLISHED
VendorSpecificInfo A set of As defined in 9.4.2.25 Zero or more elements.
elements

6.3.128.6.3 When generated

This primitive is generated by the MLME when the MAC entity detects the expiration of a beam link
maintenance timer or any status change on a beamformed link with peer MAC entity.

6.3.128.6.4 Effect of receipt

The SME is notified of the status of the beamformed link and beam link maintenance timer with the peer
MAC entity.

35
Copyright © 2023 IEEE. All rights reserved.

9. Frame formats

9.2 MAC frame formats

9.2.4 Frame fields

9.2.4.7 Frame Body field

9.2.4.7.1 General

Change Table 9-25 (as amended by IEEE Std 802.11ay-2021) as shown on the following three pages:

36
Copyright © 2023 IEEE. All rights reserved.

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
Table 9-25—Maximum data unit sizes (in octets) and durations (in microseconds)

Non-HT
non-VHT non-HE
non-S1G NGV
HT PPDU VHT PPDU HE PPDU S1G PPDU DMG PPDU EDMG PPDU
non-DMG PPDU PPDU
and non-HT
duplicate PPDU

MMPDU 2304 2304 See NOTE 1 See NOTE 1 See NOTE 1 2304 2304 2304
size
MSDU 2304 2304 2304 2304 2304 Without SAR agreement: for Without SAR agreement: for 2304
size the basic A-MSDU format, the basic A-MSDU format,
it is equal to the value of it is equal to the value of
A-MSDU size minus 14, or A-MSDU size minus 14, or
minus 2 for the short minus 2 for the short
A-MSDU format, if the A-MSDU format, if the
MPDU Limit subfield of the MPDU Limit subfield of the
Extended MPDU Capability Extended MPDU Capability
field of the DMG field of the DMG

37
Capabilities element is Capabilities element is
valid; otherwise, it is equal valid; otherwise, it is equal
to 7920. to 7920.
With SAR agreement: see With SAR agreement: see
IEEE Std 802.11bd-2022

NOTE 8. NOTE 8.

A-MSDU 3839 or 4065  3839 or 7935 See NOTE 3 2.4 GHz See NOTE 3 Without SAR agreement: Without SAR agreement: 7935

Copyright © 2023 IEEE. All rights reserved.

size (see NOTE 2)  (see also band:  indirectly limited by the indirectly limited by the
(HT STA, see also Table 9-184) 3839 or 7935  value of the MPDU Limit value of the MPDU Limit
Part 11: Wireless LAN MAC and PHY Specifications—

Table 9-184), or  (see also  subfield in the Extended subfield in the Extended
Amendment 5: Enhancements for Next Generation V2X

N/A  Table 9-184) MPDU Capability field of MPDU Capability field of

(non-HT STA,  the DMG Capabilities the DMG Capabilities
see also 10.11) Otherwise: element, if the subfield is element, if the subfield is
see NOTE 3 valid; otherwise, it is equal valid; otherwise, it is equal
to 7935. to 7935.
With SAR agreement: see With SAR agreement: see
NOTE 8. NOTE 8.
IEEE Standard for Information Technology—Local and Metropolitan Area Networks—Specific Requirements—

Non-HT
non-VHT non-HE
non-S1G NGV
HT PPDU VHT PPDU HE PPDU S1G PPDU DMG PPDU EDMG PPDU
non-DMG PPDU PPDU
and non-HT
duplicate PPDU

MPDU See NOTE 4 See NOTE 5 3895 or 7991 2.4 GHz 3895 or 7991 The value indicated in the The value indicated in the 7991
size or 11 454 band:  (see also MPDU Limit subfield of the MPDU Limit subfield of the
(see also see NOTE 5 Table 9-300) Extended MPDU Capability Extended MPDU Capability
Table 9-271) field of the DMG field of the DMG
Otherwise: Capabilities element if the Capabilities element if the
3895 or 7991 subfield is valid; otherwise, subfield is valid; otherwise,
or 11 454 as in NOTE 5. as in NOTE 5.
(see also
Table 9-271)

See NOTE 7

38
PSDU 212–1 216–1 4 692 480 6 500 631 797 160 218–1  222–1 244 800
size (see Table 15-5, (see (~222.16) (~222.63) (~219.60) (see Table 20-30) (see Table 28-12 and
Table 16-4, Table 19-25) (see (see (see  Table 28-19)
Table 17-21, Table 21-28) Table 27-54) Table 23-40)
IEEE Std 802.11bd-2022

Table 18-5)

PPDU See NOTE 6 5484 5484 5484 27 840  2000 2000 10 968

Copyright © 2023 IEEE. All rights reserved.

duration (HT_MF,  (see (see (see (see Table 20-30) (see Table 20-30)
see 10.27.4) Table 21-28) Table 27-54) Table 23-40)
Part 11: Wireless LAN MAC and PHY Specifications—

or 10 000
Amendment 5: Enhancements for Next Generation V2X

(HT_GF, see
Table 19-25)
IEEE Standard for Information Technology—Local and Metropolitan Area Networks—Specific Requirements—

Non-HT
non-VHT non-HE
non-S1G NGV
HT PPDU VHT PPDU HE PPDU S1G PPDU DMG PPDU EDMG PPDU
non-DMG PPDU PPDU
and non-HT
duplicate PPDU

NOTE 1—No direct constraint on the maximum MMPDU size; indirectly constrained by the maximum MPDU size (see 9.3.3.1).

NOTE 2—Indirect constraint from the maximum PSDU size: 212–1 octets minus the minimum QoS Data frame overhead (26 octets for the MAC header and 4 octets for the
FCS).

NOTE 3—No direct constraint on the maximum A-MSDU size; indirectly constrained by the maximum MPDU size.

NOTE 4—No direct constraint on the maximum MPDU size; indirectly constrained by the maximum MSDU/MMPDU or (for HT STAs only) A-MSDU size.

NOTE 5—No direct constraint on the maximum MPDU size; indirectly constrained by the maximum A-MSDU size.

39
NOTE 6—No direct constraint on the maximum duration, but an L_LENGTH value above 2332 might not be supported by some receivers (see NOTE 2 in 10.27.4).

NOTE 7—The maximum MPDU size might be greater than the size declared as supported by the recipient if the MPDU is an HE Compressed Beamforming/CQI frame.
IEEE Std 802.11bd-2022

NOTE 8—No direct constraint on the maximum MSDU or A-MSDU size; indirectly constrained by the maximum PSDU size. Each MPDU in an A-MPDU of the PSDU that
contains the MSDU or A-MSDU generates an overhead of MPDU Header (26 bytes), FCS (4 bytes), GCMP Header (8 bytes), MIC (16 bytes), and MPDU delimiter (4 bytes).

Copyright © 2023 IEEE. All rights reserved.

Part 11: Wireless LAN MAC and PHY Specifications—
Amendment 5: Enhancements for Next Generation V2X
IEEE Standard for Information Technology—Local and Metropolitan Area Networks—Specific Requirements—

9.2.5 Duration/ID field (QoS STA)

9.2.5.1 General

Insert the following paragraph at the end of 9.2.5.1:

The value in the Duration/ID field in a frame transmitted by an NGV STA is further defined in 31.2.1.

9.3 Format of individual frame types

9.3.4 Extension frames

9.3.4.2 DMG Beacon

Insert a new row above the last row of Table 9-45 as follows (unchanged rows not shown):

Table 9-45—DMG Beacon frame body

Order Information Notes

64 DMG OCB This element is present if dot11DMGOCBActivated is true; otherwise

not present.
…

Replace Figure 9-79 with the following figure (with a new column for B48):

B0 B47 B48 B49 B63

A-BFT Responder Address OCB Reserved

Bits: 48 1 15

Figure 9-79—Clustering Control field format if the Discovery Mode is 1

Change the last paragraph of 9.3.4.2 as follows:

The A-BFT Responder Address subfield contains the MAC address of the STA that is allowed to transmit
during the A-BFT, if present, that follows the BTI. If all bits of the A-BFT Responder Address subfield are
equal to 1 and the OCB subfield is equal to 1, any STA is allowed to transmit during the A-BFT, if present.

Insert the following paragraph at the end of 9.3.4.2:

The OCB subfield is set to 1 to indicate the support of communication outside the context of a BSS by the
STA transmitting the DMG Beacon frame.

40
Copyright © 2023 IEEE. All rights reserved.

9.4 Management and Extension frame body components

9.4.1 Fields that are not elements

9.4.1.46 DMG Parameters field

Change Table 9-69 as follows:

Table 9-69—The BSS Type subfield when the Discovery mode field is 1

Subfield value Responding STA role Applicable BSS types

3 AP Infrastructure BSS

2 PCP PBSS

1 Non-AP STA PBSS, IBSS, OCB

0 Any Infrastructure BSS, PBSS, IBSS,
OCB

NOTE—OCB is not a BSS Type, but rather an indication of communication outside the
context of a BSS.

9.4.2 Elements

9.4.2.1 General

Insert two rows above the last reserved row and change the last reserved row in Table 9-92 (as amended
by IEEE Std 802.11az-2022) as follows (unchanged rows not shown):

Table 9-92—Element IDs

Element ID
Element Element ID Extensible Fragmentable
Extension

Reserved 255 106–114

DMG OCB (see 255 115 Yes No

9.4.2.308)

Reserved 255 106–255

116–255

41
Copyright © 2023 IEEE. All rights reserved.

9.4.2.298 Ranging Parameters element

Insert two new rows above the last row, change the last row, and insert a table note at the end of
Table 9-322al (as inserted by IEEE Std 802.11az-2022) as follows (unchanged rows not shown):

Table 9-322al—Format and Bandwidth subfield

Field value Format Bandwidth

6 NGV 10

7 NGV 20

6–63 Reserved
Reserved
8–63

NOTE—Values 6 and 7 are supported only when dot11NGVOptionImplemented is

true.

Insert 9.4.2.308 after 9.4.2.307 (as inserted by IEEE Std 802.11az-2022) as follows:

9.4.2.308 DMG OCB element

The format of the DMG OCB element is shown in Figure 9-788fm.

Element ID Length Element ID Extension DMG OCB Parameters

Octets: 1 1 1 1

Figure 9-788fm—DMG OCB element format

The Element ID, Length, and Element ID Extension fields are defined in 9.4.2.1.

The DMG OCB Parameters field is defined in Figure 9-788fn.

B1 B2 B8

Unsolicited
Reserved
RSS

Bits: 1 7

Figure 9-788fn—DMG OCB Parameters field format

The Unsolicited RSS subfield is defined in 9.5.5.

42
Copyright © 2023 IEEE. All rights reserved.

9.5 Fields used in Management and Extension frame bodies and Control frames

9.5.3 Sector Sweep Feedback field

Replace Figure 9-848 (as amended by IEEE Std 802.11ay-2021) with the following figure (with a new
column for B17):

B0 B8 B9 B10 B11 B15 B16 B17 B18 B21 B22 B23

Total Number of Unsolicited

Poll
Sectors in RX DMG Reserved Required OCB Reserved RSS Reserved
ISS Antennas Enabled

Bits: 9 2 5 1 1 4 1 1

Figure 9-848—SSW Feedback field format when transmitted as part of an ISS

Replace Figure 9-849a (as inserted by IEEE Std 802.11ay-2021) with the following figure (with a new
column for B17):

B0 B5 B6 B7 B8 B15 B16 B17 B18 B21 B22 B23

DMG EDMG
Sector Antenna SNR Poll OCB Reserved Unsolicited Extension
Select Report Required RSS Enabled
Select Flag

Bits: 6 2 8 1 1 4 1 1

Figure 9-849a—SSW Feedback field format when not transmitted as part of an ISS and the
EDMG Extension Flag subfield is 0

Insert the following paragraph at the end of 9.5.3:

The OCB subfield is set to 1 if dot11DMGOCBActivated is true, and is set to 0 otherwise. If equal to 1, this
subfield indicates that the STA is operating outside the context of a BSS.

9.7 Aggregate MPDU (A-MPDU)

9.7.1 A-MPDU format

Change the third paragraph of 9.7.1 as follows:

In an HT or, DMG, or NGV PPDU, the final A-MPDU subframe is not padded. In a VHT, EDMG, or S1G
PPDU, padding is added as described below.

43
Copyright © 2023 IEEE. All rights reserved.

9.7.3 A-MPDU contents

Change the first paragraph of 9.7.3 as follows:

In a non-DMG PPDU, an A-MPDU is a sequence of A-MPDU subframes carried in a single PPDU with one
of the following combinations of RXVECTOR or TXVECTOR parameter values:
— The FORMAT parameter set to VHT
— The FORMAT parameter set to HT_MF or HT_GF and the AGGREGATION parameter set to 1
— The FORMAT parameter set to S1G, S1G_DUP_1M, or S1G_DUP_2M and the AGGREGATION
parameter set to 1
— The FORMAT parameter set to HE_SU, HE_MU, HE_TB, or HE_ER_SU
— The FORMAT parameter set to NGV

44
Copyright © 2023 IEEE. All rights reserved.

10. MAC sublayer functional description

10.2 MAC architecture

10.2.3 Hybrid coordination function (HCF)

10.2.3.2 HCF contention based channel access (EDCA)

Change the second paragraph of 10.2.3.2 as follows:

For each AC an enhanced variant of the DCF, called an enhanced distributed channel access function
(EDCAF), contends for TXOPs using a set of EDCA parameters. When communicating Data frames outside
the context of a BSS (dot11OCBActivated is true), the EDCA parameters are the corresponding default
values or are as set by the SME in dot11EDCATable (except for TXOP limits, which shall be when the
TXOP limits are set to 0 for each AC as specified in 10.23.2.9). For a STA operating OCB the STA’s
transmit queue for an AC may be cleared by the invocation of the MLME-CANCELTX.request primitive
(see 6.3.126). For a non-AP STA communicating within a non-mesh QoS BSS, the EDCA parameters used
are from the EDCA Parameter Set element or (for a non-AP STA prior to associating with an AP of an
infrastructure BSS, a mesh STA, or a STA that operates OCB) from the default values for the parameters.
The parameters used by the EDCAF to control its operation are defined by dot11QAPEDCATable at the AP
and by dot11EDCATable at the non-AP STA.

10.3 DCF

10.3.6 Group addressed MPDU transfer procedure

Change the fourth paragraph of 10.3.6 as follows:

A DMG STA may transmit a copy of the same group addressed MPDU using different antenna
configurations. This might be needed to provide a quasi-omni coverage or to enable transmission by an
MCS that is higher than MCS 0. A DMG STA with dot11DMGOCBActivated equal to true may transmit
copies of the same group addressed MPDU using different antenna configurations to provide sufficient
coverage to communicate with peer STAs with which the DMG STA is maintaining beam links and may
omit transmissions that use an antenna configuration over which a beamformed link is not maintained. If
multiple copies of a group addressed MPDU with a To DS subfield equal to 0 are transmitted, the STA shall
not transmit a different frame before the completion of the transmission of all copies of the group addressed
MPDU.

10.12 A-MPDU operation

10.12.2 A-MPDU length limit rules

Insert the following paragraph and note at the end of 10.12.2:

An NGV STA may transmit an A-MPDU without capability exchange as specified in 31.2.3. An NGV STA
shall support reception of an A-MPDU as specified in 31.2.3.

NOTE—An NGV STA does not use the HT Capabilities element or the VHT Capabilities element to establish the
maximum length of an A-MPDU, as an NGV STA only operates OCB and need not exchange these elements.

43
Copyright © 2023 IEEE. All rights reserved.

10.12.4 A-MPDU aggregation of group addressed Data frames

Change the first paragraph as follows:

A STA that is neither not one of an AP, nor a mesh STA, or an NGV STA shall not transmit an A-MPDU
containing an MPDU with an RA that is a group address.

10.13 PPDU duration constraint

Insert the following paragraph at the end of 10.13:

A STA shall not transmit an NGV PPDU that has a duration (as determined by the PHY-TXTIME.confirm
primitive defined in 6.5.6) that is greater than aPPDUMaxTime defined in Table 32-20.

10.23 HCF

10.23.2 HCF contention based channel access (EDCA)

10.23.2.8 Multiple frame transmission in an EDCA TXOP

Insert two new items after the item beginning “A Ranging NDP Announcement frame followed after
SIFS by an HE Ranging NDP…” (inserted by IEEE Std 802.11az-2022) at the end of the dashed list after
the first paragraph of 10.23.2.8 as follows:

— A Ranging NDP Announcement frame followed after SIFS by an NGV NDP followed after SIFS
by another NGV NDP followed after SIFS by an LMR frame.
— A Ranging NDP Announcement frame followed after SIFS by an NGV NDP followed after SIFS
by another NGV NDP followed after SIFS by an LMR frame followed after SIFS by another
LMR frame.

10.23.2.9 TXOP limits

Change the fourth paragraph of 10.23.2.9 as follows:

When dot11OCBActivated is true, dot11NGVOptionImplemented is false or not present, and

dot11DMGOCBActivated is false or not present, the TXOP limits limit shall be 0 for each AC.

10.25 Block acknowledgment (block ack)

10.25.1 Introduction

Change the second paragraph of 10.25.1 (as amended by IEEE Std 802.11ay-2021) as follows:

The block ack mechanism is initialized by an exchange of ADDBA Request/Response frames, except for
GLK-GCR block ack and block ack between two NGV STAs, or by using the unsolicited block ack
extension mechanism. After initialization, blocks of QoS Data frames may be transmitted from the originator
to the recipient. A block may be started within a polled TXOP, within an SP, or by winning EDCA contention.
The number of frames in the block is limited, and the amount of state that is to be kept by the recipient is
bounded. The MPDUs within the block of frames are acknowledged by a BlockAck frame, which is requested
by a BlockAckReq frame.

44
Copyright © 2023 IEEE. All rights reserved.

10.25.2 Setup and modification of the block ack parameters

Insert the following paragraph at the end of 10.25.2:

An NGV STA does not initialize the block ack mechanism as defined in this subclause; a block ack
agreement with parameters defined in 31.2.3 is always in place.

45
Copyright © 2023 IEEE. All rights reserved.

11. MLME

11.1 Synchronization

11.1.3 Maintaining synchronization

11.1.3.4 DMG beacon generation before establishment of a BSS

Change the now ninth paragraph of 11.1.3.4 (after insertion of a paragraph by IEEE Std 802.11ay-2021)
as follows:

A STA with dot11DMGOCBActivated equal to false that is transmitting DMG Beacon frames with the
Discovery Mode field equal to 1 should cease transmitting these beacons when it has received a DMG
Beacon frame from another STA, or when it has received acknowledgment of a transmitted Probe Response
frame. If a BSS is not initialized as a result of the channel scanning, the STA can resume transmitting DMG
Beacon frames with the Discovery Mode field equal to 1.

Insert a new paragraph after the now ninth paragraph of 11.1.3.4 as follows:

A STA with dot11DMGOCBActivated equal to true that is transmitting DMG Beacon frames with the
Discovery Mode field equal to 1 may continue transmitting these beacons for discovery as described in
11.1.4.7 even if it has received a DMG Beacon frame from another STA.

11.1.4 Acquiring synchronization, scanning

11.1.4.1 General

Insert the following at the end of 11.1.4.1:

Upon receipt of the MLME-DMG-OCB-START.request primitive, a DMG STA with

dot11DMGOCBActivated equal to true shall start a discovery procedure outside the context of a BSS as
described in 11.1.4.7 and start operation outside the context of a BSS as described in 31.3.

Insert 11.1.4.7 after 11.1.4.6 as follows:

11.1.4.7 DMG discovery outside the context of a BSS

This subclause applies to a DMG STA when dot11DMGOCBActivated is true.

Upon receipt of the MLME-DMG-OCB-START.request primitive, a DMG STA continuously discovers

new peer STAs. If the discovery beacon parameter is equal to true, the STA shall start transmitting DMG
Beacon frames with the Discovery Mode field set to 1, the OCB subfield in the Clustering Control field set
to 1, and the Beacon Interval field set to a random value as described in 11.1.3.4. If the discovery beacon
parameter is equal to false, the DMG STA shall not transmit DMG Beacon frames.

When the STA receives one or more SSW frames with the OCB subfield equal to 1 during an A-BFT or DTI
and completes SLS with the peer STA, and the address of the peer STA is an address that is newly
discovered, the STA shall issue an MLME-OCB-DMGDISCOVERY.indication with the PeerInfoSet
parameter including the PeerInfo vector defined in 6.3.128.5 for the peer STA that transmitted the SSW
frame.

When the STA receives one or more DMG Beacon frames with the OCB subfield equal to 1 from a peer
STA, and the address of the peer STA is an address that is newly discovered, the STA shall perform an SLS

47
Copyright © 2023 IEEE. All rights reserved.

with the OCB subfield set to 1 in transmitted SSW frames during the A-BFT following the DMG Beacon
frames or the DTI. If the SLS is completed, the STA shall issue an
MLME-OCB-DMGDISCOVERY.indication with the PeerInfoSet parameter including the PeerInfo for the
peer STA that transmitted the DMG Beacon frame.

When the STA completes SLS with a peer STA that transmitted an SSW frame with the OCB subfield equal
to 1 or a DMG Beacon frame with the OCB subfield equal to 1, and the address of the peer STA is not an
address that is newly detected, the STA may issue an MLME-OCB-DMGDISCOVERY.indication with the
PeerInfoSet parameter including the PeerInfo regarding the peer STA.

Upon receipt of the MLME-DMG-OCB-STOP.request primitive, a DMG STA shall terminate transmission
of DMG Beacon frames and cease discovery of peer STAs.

Figure 11-10a illustrates an example of the DMG discovery outside the context of a BSS, in which the
discovery beacon parameter is equal to true in the MLME-DMG-OCB-START.request primitive for both
STAs.

SME MAC Peer MAC Peer SME

MLME-DMG-OCB-
START.request
MLME-DMG-OCB-
START.confirm
DMG Beacon frames MLME-DMG-OCB-
START.request
DMG Beacon frames
MLME-DMG-OCB-
START.confirm
DMG Beacon frames

DMG Beacon frames

(The STAs are approaching...)

DMG Beacon frames

SSW frames (A-BFT)
MLME-OCB- SSW-Feedback frame (A-BFT) MLME-OCB-
DMGDISCOVERY.indication DMGDISCOVERY.indication

DMG Beacon frames

MLME-DMG-OCB-STOP.request
DMG Beacon frames

Figure 11-10a—DMG discovery outside the context of a BSS

48
Copyright © 2023 IEEE. All rights reserved.

Figure 11-10b illustrates an example of beamforming training during the DMG discovery outside the
context of a BSS, in which the MAC address of the peer STA is informed over a higher layer and included in
the MLME-BF-TRAINING.request primitive.

SME MAC Peer MAC Peer SME

MLME-DMG-OCB-
START.request
MLME-DMG-OCB-
START.confirm
MLME-DMG-OCB-
START.request
MLME-DMG-OCB-
START.confirm

(The STAs are approaching...)

PeerInfo vector content is

informed over higher layer

MLME-BF-TRAINING.request
SSW frames (DTI, ISS)
SSW frames (DTI, RSS)
SSW-Feedback frame
SSW-Ack frame
MLME-BF-TRAINING.indication MLME-BF-TRAINING.confirm

MLME-OCB-
DMGDISCOVERY.indication MLME-OCB-
(optional) DMGDISCOVERY.indication

Figure 11-10b—Beamforming training during the DMG discovery outside the context of a
BSS

11.18 STAs communicating Data frames outside the context of a BSS

Change item b) in the lettered list after the first paragraph of 11.18 as follows:

b) The STA may send Control frames, except those of subtype PS-Poll and CF-End. If the STA is a
DMG STA for which dot11DMGOCBActivated is true, in addition to not sending Control frames of
subtype PS-Poll and CF-End, the STA shall not send Control frames of subtype Poll, SPR, Grant,
Grant Ack, Sector Ack, Block Ack Schedule, and TDD Beamforming.

Insert a new item e) at the end of the lettered list after the first paragraph of 11.18 as follows:

e) If the STA is a DMG STA for which dot11DMGOCBActivated is true, the STA may send DMG
Beacon frames. A STA sending DMG Beacon frames shall set the Discovery Mode field to 1, and
set the CBAP Only and CBAP Source subfields in the DMG Parameters field to 1 and 0,
respectively.

49
Copyright © 2023 IEEE. All rights reserved.

11.21 Wireless network management procedures

11.21.6 Fine timing measurement (FTM) procedure

11.21.6.4 Measurement exchange

11.21.6.4.4 Non-TB ranging measurement exchange

11.21.6.4.4.2 Measurement sounding phase of non-TB ranging

Change the first paragraph of 11.21.6.4.4.2 (as inserted by IEEE Std 802.11az-2022) as follows:

An ISTA shall initiate a non-TB ranging measurement instance by transmitting a Ranging NDP
Announcement frame addressed to the RSTA, followed by an I2R NDP SIFS after. In response to the
correctly received Ranging NDP Announcement frame addressed to itself, the RSTA shall transmit an R2I
NDP; see Figure 11-37i. I2R NDP and R2I NDP refer to NGV Ranging NDPs when
dot11NGVOptionImplemented is true and HE ranging NDPs otherwise. The measurement-reporting phase
consists of an LMR frame, which is a Location Measurement Report as defined in 9.6.7.49.

Change the 11th paragraph of 11.21.6.4.4.2 (as inserted by IEEE Std 802.11az-2022) as follows:

Accordingly:
— An ISTA transmitting an I2R NDP shall set the TXVECTOR parameter CH_BANDWIDTH to the
same value as the TXVECTOR parameter CH_BANDWIDTH in the preceding Ranging NDP
Announcement frame.
— An RSTA transmitting an R2I NDP shall set the TXVECTOR parameter CH_BANDWIDTH to the
bandwidth of the Ranging NDP Announcement frame and/or the I2R NDP; which are obtained from
the RXVECTOR parameter CH_BANDWIDTH of the Ranging NDP Announcement frame or I2R
NDP, respectively. For the Ranging NDP Announcement frame, when not received in an
HE/VHT/HT/NGV PPDU: from the RXVECTOR parameter CH_BANDWIDTH_IN_NON_HT
when the Ranging NDP Announcement frame is received in a non-HT duplicate PPDU and is
20 MHz when the Ranging NDP Announcement frame is received in a non-HT PPDU.

11.21.6.4.6 Transmission of a ranging NDP

Insert the following new paragraphs at the end of 11.21.6.4.6 (as inserted by IEEE Std 802.11az-2022):

An RSTA transmitting an NGV ranging NDP to an ISTA shall set the TXVECTOR parameters as follows:
— The FORMAT parameter is set to NGV.
— The CH_BANDWIDTH parameter is set to the same value as the RXVECTOR parameter
CH_BANDWIDTH in the preceding I2R NDP.
— The NGV-LTF-TYPE parameter is set to 1 to indicate NGV_LTF_2X is used in the NGV ranging
NDP.
— The NUM_SS parameter is set to the same value as the R2I N_STS in the STA Info field in the
preceding Ranging NDP Announcement frame.
— The APEP_LENGTH parameter is set to 0.
— The LTF_REP parameter is set to the same value as the R2I LTF_REP in the STA Info field in the
preceding Ranging NDP Announcement frame.

An ISTA transmitting an NGV ranging NDP to an RSTA shall set the TXVECTOR parameters as follows:
— The FORMAT parameter is set to NGV.

50
Copyright © 2023 IEEE. All rights reserved.

— The CH_BANDWIDTH parameter is set to the same value as the TXVECTOR parameter
CH_BANDWIDTH in the preceding Ranging NDP Announcement frame.
— The NGV-LTF-TYPE parameter is set to 1 to indicate NGV_LTF_2X is used in the NGV ranging
NDP.
— The NUM_SS parameter is set to the same value as the I2R N_STS in the STA Info field in the
preceding Ranging NDP Announcement frame.
— The APEP_LENGTH parameter is set to 0.
— The LTF_REP parameter is set to the same value as the I2R LTF_REP in the STA Info field in the
preceding Ranging NDP Announcement frame.

11.27 DMG beamformed link and BSS maintenance

11.27.1 Beamformed link maintenance

11.27.1.1 General

Insert a new paragraph and note after the ninth paragraph (beginning “The recipient DMG STA shall
…”) of 11.27.1.1 (as re-numbered by IEEE Std 802.11ay-2021) as follows:

When a DMG STA with dot11DMGOCBActivated equal to true establishes a beamformed link with a peer
STA, the STA shall generate an MLME-OCB-LINKSTATUS.indication with the BeamLinkStatus
parameter set to ESTABLISHED or an MLME-OCB-DMGDISCOVERY.indication to inform the SME of
the establishment of the beamformed link with the peer STA.
NOTE—When the beamformed link was established as a result of the discovery and the STA generated an
MLME-OCB-DMGDISCOVERY.indication primitive as specified in 11.1.4.7, the STA might omit generation of an
MLME-OCB-LINKSTATUS.indication.

Insert a new paragraph after the now 15th paragraph (beginning “Any time after
dot11BeamLinkMaintenancetime has elapsed, the initiator …”) of 11.27.1.1 (as re-numbered by IEEE
Std 802.11ay-2021) as follows:

Upon expiration of dot11BeamLinkMaintenanceTime, a DMG STA for which dot11DMGOCBActivated is

true shall generate an MLME-OCB-LINKSTATUS.indication primitive with BeamLinkStatus parameter set
to EXPIRED to inform the SME of the expiration of the beam link maintenance timer with the peer STA.

51
Copyright © 2023 IEEE. All rights reserved.

12. Security

12.13 Preassociation security negotiation

12.13.1 General

Change the second paragraph of 12.13.1 (as inserted by IEEE Std 802.11az-2022) as follows (with the
following dashed list unchanged):

PASN is primarily intended for use in infrastructure networks for a STA and an AP to establish a PTKSA
using a three-message authentication frame exchange. It may also be used by two STAs each co-located
with an NGV STA (see 31.4). Some salient aspects of this protocol are:

12.13.3 Key establishment with PASN authentication

12.13.3.1 Overview

Change the first paragraph of 12.13.3.1 (as inserted by IEEE Std 802.11az-2022) as follows:

This subclause defines the procedure for establishing a PTKSA and the corresponding shared keys between
a PASN capable STA and AP or two PASN capable STAs each co-located with an NGV STA (see 31.4).
The PASN frame sequence used is depicted in Figure 12-56. It consists of three Authentication frames with
the Authentication Algorithm Number field (9.4.1.1) set to 7 (PASN authentication) and the corresponding
Authentication Transaction Sequence Number field (9.4.1.2) set to 1, 2, and 3, respectively.

Insert a note in Figure 12-56 as follows:

NOTE—Beacon is only present when the authenticator is an AP and not otherwise. For example when an authenticator
is a non-AP STA co-located with an NGV STA, beacons are not present (see 31.4).

12.13.3.2 PASN frame construction and processing

Change the first item in the dashed list after the first paragraph of 12.13.3.2 (as inserted by IEEE Std
802.11az-2022) as follows:

— Base AKMP from among AKMPs advertised by the AP or provisioned by a higher layer (applicable
for STAs co-located with NGV STAs (see 31.4) if RSNA authentication is desired. Otherwise, if
dot11NoAuthPASNActivated is true, Base AKMP chosen is the PASN AKMP, indicating that
PTKSA is to be established without mutual authentication, that is, without a corresponding PMKSA.

53
Copyright © 2023 IEEE. All rights reserved.

17. Orthogonal frequency division multiplexing (OFDM) PHY specification

17.2 OFDM PHY specific service parameter list

17.2.2 TXVECTOR parameters

17.2.2.1 General

Insert two new rows at the end of Table 17-1 as follows (unchanged rows not shown):

Table 17-1—TXVECTOR parameters

Parameter Associated primitive Value

CH_BANDWIDTH_ PHY-TXSTART.request If present, CBW10 or CBW20

IN_NON_NGV (TXVECTOR)

DYN_BANDWIDTH_ PHY-TXSTART.request If present, Static or Dynamic

IN_NON_NGV (TXVECTOR)

Insert 17.2.2.9 and 17.2.2.10 after 17.2.2.8 as follows:

17.2.2.9 TXVECTOR CH_BANDWIDTH_IN_NON_NGV

If present, this parameter is used to modify the first 7 bits of the scrambling sequence to indicate the
bandwidth of the non-NGV duplicate PPDU.
NOTE—The CH_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is transmitted by a
non-NGV STA. The CH_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is transmitted by an
NGV STA and a non-NGV STA is one of the intended recipients (including group addressed transmissions).

17.2.2.10 TXVECTOR DYN_BANDWIDTH_IN_NON_NGV

If present, this parameter is used to modify the first 7 bits of the scrambling sequence to indicate if the
transmitter is capable of Static or Dynamic bandwidth operation. If DYN_BANDWIDTH_IN_NON_NGV
is present, then CH_BANDWIDTH_IN_NON_NGV is also present.
NOTE—The DYN_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is transmitted by a
non-NGV STA. The DYN_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is transmitted by
an NGV STA and a non-NGV STA is one of the intended recipients (including group addressed transmissions).

55
Copyright © 2023 IEEE. All rights reserved.

17.2.3 RXVECTOR parameters

17.2.3.1 General

Insert two new rows at the end of Table 17-2 as follows (unchanged rows not shown):

Table 17-2—RXVECTOR parameters

Parameter Associated primitive Value

CH_BANDWIDTH PHY-RXSTART.request If present, CBW10 or CBW20

_IN_NON_NGV (RXVECTOR)

DYN_BANDWIDTH PHY-RXSTART.request If present, Static or Dynamic

_IN_NON_NGV (RXVECTOR)

Insert 17.2.3.9 and 17.2.3.10 after 17.2.3.8 as follows:

17.2.3.9 RXVECTOR CH_BANDWIDTH_IN_NON_NGV

If present and valid, this parameter indicates the bandwidth of the non-NGV duplicate PPDU. This
parameter is used by the MAC only when valid (see 10.3.2.9 and 10.6.6.6).
NOTE—The CH_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is received by a non-NGV
STA (see 10.6.12).

17.2.3.10 RXVECTOR DYN_BANDWIDTH_IN_NON_NGV

If present and valid, this parameter indicates whether the transmitter is capable of Static or Dynamic
bandwidth operation. This parameter is used by the MAC only when valid (see 10.3.2.9 and 10.6.6.6). If
DYN_BANDWIDTH_IN_NON_NGV is present, then CH_BANDWIDTH_IN_NON_NGV is also present.
NOTE—The DYN_BANDWIDTH_IN_NON_NGV parameter is not present when the frame is received by a non-NGV
STA (see 10.6.12).

17.3 OFDM PHY

17.3.2 PPDU format

17.3.2.2 Overview of the PPDU encoding process

Change item e) in the lettered list in 17.3.2.2 as follows:

e) If neither of the TXVECTOR parameters CH_BANDWIDTH_IN_NON_HT and

CH_BANDWIDTH_IN_NON_NGV is not present, initiate the scrambler with a pseudorandom
nonzero seed and generate a scrambling sequence. If the TXVECTOR parameter
CH_BANDWIDTH_IN_NON_HT or CH_BANDWIDTH_IN_NON_NGV is present, construct the
first 7 bits of the scrambling sequence from CH_BANDWIDTH_IN_NON_HT or
CH_BANDWIDTH_IN_NON_NGV, DYN_BANDWIDTH_IN_NON_HT (if present) or
DYN_BANDWIDTH_IN_NON_NGV (if present), and a pseudorandom integer constrained such

56
Copyright © 2023 IEEE. All rights reserved.

that the first 7 bits of the scrambling sequence are not all 0s; then set the scrambler state to these 7
bits and generate the remainder of the scrambling sequence. XOR the scrambling sequence with the
extended string of data bits. Refer to 17.3.5.5 for details.

17.3.5 DATA field

17.3.5.5 PHY DATA scrambler and descrambler

Replace Figure 17-7 with the following figure:

During bits 0-6 of Scrambling Sequence

when CH_BANDWIDTH_IN_NON_HT or
CH_BANDWIDTH_IN_NON_NGV is
First 7 bits of Scrambling present
Sequence as defined in
Table 17-7

Data In

X7 X6 X5 X4 X3 X2 X1

Scrambled
Data Out

Figure 17-7—Data scrambler

Change the second and third paragraphs of 17.3.5.5 as follows:

The same scrambler is used to scramble transmit data and to descramble receive data. If neither of the
TXVECTOR parameters CH_BANDWIDTH_IN_NON_HT and CH_BANDWIDTH_IN_NON_NGV is
not present, when transmitting, the initial state of the scrambler shall be set to a pseudorandom nonzero
state. If the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT or
CH_BANDWIDTH_IN_NON_NGV is present,:

— The first 7 bits of the scrambling sequence shall be set as shown in Table 17-7 (with field values
defined in Table 17-8 and, Table 17-8a, Table 17-10, and Table 17-10a) and shall be also used to
initialize the state of the scrambler.

— The scrambler with this initialization shall generate the remainder (i.e., after the first 7 bits) of the
scrambling sequence as shown in Figure 17-7.

— CH_BANDWIDTH_IN_NON_HT is transmitted LSB first. For example, if CBW80 has a value

of 2, which is 10 in binary representation, then B5=0 and B6=1.

— CH_BANDWIDTH_IN_NON_NGV is transmitted LSB first.

If the TXVECTOR parameter SCRAMBLER_RESET is set equal to RESET_SCRAMBLER and

dot11MACPrivacyActivated is true, the initial state of the scrambler shall be set to a nonzero random value
not based on the scrambler value at the end of the last transmitted PPDU, before changes based on
CH_BANDWIDTH_IN_NON_HT or CH_BANDWIDTH_IN_NON_NGV defined above are applied.

57
Copyright © 2023 IEEE. All rights reserved.

Change Table 17-7 as follows:

Table 17-7—Contents of the first 7 bits of the scrambling sequence

First 7 bits of scrambling sequence

B0 B3 B4 B5 B6
Parameter Condition

Transmit order

TXVECTOR CH_BANDWIDTH_I 5-bit pseudorandom nonzero integer if CH_BANDWIDTH_

N_NON_HT is CH_BANDWIDTH_IN_NON_HT (if present) IN_NON_HT (if
present and equals CBW20 or present) or
DYN_BANDWIDTH CH_BANDWIDTH_IN_NON_NGV (if present) CH_BANDWIDTH_
_IN_NONT_HT is not equals CBW10; and a 5-bit pseudorandom integer IN_NON_NGV (if
present in otherwise present)
TXVECTOR; or
CH_BANDWIDTH_I
N_NON_NGV is
present and
DYN_BANDWIDTH
_IN_NON_NGV is
not present in
TXVECTOR

TXVECTOR CH_BANDWIDTH_I 4-bit pseudorandom DYN_BANDWIDTH

N_NON_HT is nonzero integer if _IN_NON_HT (if
present and CH_BANDWIDTH_IN_ present) or
DYN_BANDWIDTH NON_HT (if present) DYN_BANDWIDTH
_IN_NONT_HT is equals CBW20 and _IN_NON_NGV (if
present in DYN_BANDWIDTH_IN present)
TXVECTOR; or _NON_HT (if present)
CH_BANDWIDTH_I equals Static, or
N_NON_NGV is CH_BANDWIDTH_IN_
present and NON_NGV (if present)
DYN_BANDWIDTH equals CBW10 and
_IN_NON_NGV is DYN_BANDWIDTH_IN
present in _NON_NGV (if present)
TXVECTOR equals Static; and a 4-bit
pseudorandom integer
otherwise

RXVECTOR CH_BANDWIDTH_I — DYN_BANDWIDTH CH_BANDWIDTH_

N_NON_HT and _IN_NON_HT (if IN_NON_HT_INDI
DYN_BANDWIDTH present) or CATOR or
_IN_NONT_HT are DYN_BANDWIDTH CH_BANDWIDTH_
present in _IN_NON_NGV (if IN_NON_NGV_IND
RXVECTOR, or present) ICATOR (see
CH_BANDWIDTH_I Table 17-9 and
N_NON_NGV and Table 17-9a).
DYN_BANDWIDTH
_IN_NON_NGV are
present in
RXVECTOR

58
Copyright © 2023 IEEE. All rights reserved.

Insert Table 17-8a and a new paragraph after Table 17-8 as follows:

Table 17-8a—TXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV values

Enumerated value Value

CBW10 0

CBW20 1

During reception by an NGV STA, the RXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV shall

be determined from selected bits in the scrambling sequence as shown in Table 17-7 and Table 17-9a.
During reception by an NGV STA, the RXVECTOR parameter DYN_BANDWIDTH_IN_NON_NGV
shall be set to selected bits in the scrambling sequence as shown in Table 17-7 and Table 17-10a. The fields
shall be interpreted as being sent LSB-first.

Insert Table 17-9a after Table 17-9 as follows:

Table 17-9a—RXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV values

CH_BANDWIDTH_IN_NON_NGV_INDICATOR RXVECTOR parameter

field of first 7 bits of scrambling sequence CH_BANDWIDTH_IN_NON_NGV

0 CBW10

1 CBW20

Insert Table 17-10a after Table 17-10 as follows:

Table 17-10a—DYN_BANDWIDTH_IN_NON_NGV values

Enumerated value Value

Static 0

Dynamic 1

Change NOTE 2 and NOTE 3 in 17.3.5.5 as follows:

NOTE 2—The receiving PHY cannot determine whether the CH_BANDWIDTH_IN_NON_HT, and
DYN_BANDWIDTH_IN_NON_HT, CH_BANDWIDTH_IN_NON_NGV, and DYN_BANDWIDTH_IN_NON_NGV
parameters were present in the TXVECTOR of the transmitting PHY; therefore, the receiving PHY in a VHT STA always
includes values for the CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NON_HT parameters in the
RXVECTOR if the PPDU is a non-HT PPDU; the receiving PHY in an NGV STA always includes values for the
CH_BANDWIDTH_IN_NON_NGV and DYN_BANDWIDTH_IN_NON_NGV parameters in the RXVECTOR if the
PPDU is a non-NGV PPDU. It is the responsibility of the MAC to determine the validity of the RXVECTOR parameters
CH_BANDWIDTH_IN_NON_HT, and DYN_BANDWIDTH_IN_NON_HT, CH_BANDWIDTH_IN_NON_NGV,
and DYN_BANDWIDTH_IN_NON_NGV.

59
Copyright © 2023 IEEE. All rights reserved.

NOTE 3—The receiving PHY cannot determine whether the TXVECTOR parameter
CH_BANDWIDTH_IN_NON_HT or CH_BANDWIDTH_IN_NON_NGV was present, but it does not matter since
descrambling the DATA field is the same either way.

60
Copyright © 2023 IEEE. All rights reserved.

Insert new Clause 31 and Clause 32 after Clause 30 (inserted by IEEE Std 802.11ba-2021) as follows:

31. Next Generation V2X (NGV) MAC specification

31.1 Introduction

An NGV STA supports the MAC and MLME functions defined in 31.2 in addition to the MAC functions
defined in Clause 10 and the MLME functions defined in Clause 11 for STAs communicating Data frames
OCB.

If dot11DMGOCBActivated is true, a DMG STA shall support the features defined in 31.3, the MAC
functions defined in Clause 10, and the MLME functions defined in Clause 11 for DMG or EDMG STAs
communicating Data frames OCB.

31.2 Operation in the 5.9 GHz band

31.2.1 Coexistence with non-NGV STAs

In order to enable coexistence and interoperability with non-NGV STAs, if dot11NGVOptionImplemented

is true then dot11OCBActivated shall be true. Moreover, the non-NGV PPDUs transmitted by NGV STAs
carry an indication that informs the receiving NGV STAs that the transmitter is an NGV STA. This
indication is carried in the Duration/ID field of the MAC header.
NOTE 1—An NGV STA that wishes to communicate OCB with one or more neighboring non-NGV STAs is
recommended to use the non-NGV PPDU format.

When an NGV STA transmits an Ack frame solicited by an individually addressed Management or QoS
Data frame in a non-NGV PPDU and the Duration field value specified in 9.2.5.7 (Setting for control
response frames) is 0, the Duration/ID field in the Ack frame shall be set to 2. When an NGV STA transmits
an individually addressed Management or QoS Data frame in a non-NGV PPDU as the last frame of a
TXOP, the Duration/ID field of the Management or QoS Data frame shall be set to the sum of 4, SIFS, and
the transmission time of the responding Ack frame as defined in 10.6.

NOTE 2—An NGV STA can transmit either a non-NGV PPDU or an NGV PPDU. The value of the Duration field
carried in a non-NGV PPDU indicates to a receiving NGV STA whether the transmitter is an NGV STA or a non-NGV
STA.

When an NGV STA transmits a group addressed frame in a non-NGV PPDU, the Duration/ID field in the
group addressed frame shall be set to 2.

An NGV STA determines that a received non-NGV PPDU was transmitted by an NGV STA if the
non-NGV PPDU contains one of the following frames:
— An Ack or BlockAck frame with Duration/ID field equal to 2.
— An individually addressed frame with Duration/ID field equal to the sum of 4, SIFS, and the
transmission time of the responding Ack or BlockAck frame as defined in 10.6.
— A group addressed frame with Duration/ID field equal to 2.

31.2.2 Channel access and transmission methods for 20 MHz OCB transmission

An NGV 20 MHz channel consists of two contiguous 10 MHz channels: the OCB primary channel and the
OCB secondary channel.

61
Copyright © 2023 IEEE. All rights reserved.

The OCB primary channel is designated by the primary channel parameter of the radio environment vector
in the MA-UNITDATA.request primitive (see 5.2.3).

An NGV STA transmitting a 20 MHz NGV PPDU or 20 MHz non-NGV duplicate PPDU shall contend for
the medium using EDCA as defined in 10.2.3.2 and 10.3.2 based on the medium sensing results of two
contiguous 10 MHz channels, OCB primary channel and OCB secondary channel in an NGV 20 MHz
channel. An NGV STA performing 20 MHz channel access determines that the 20 MHz medium is idle if all
of the following conditions are met:
— The CS mechanism (see 10.3.2.1) indicates that the OCB primary channel is idle.
— The PHY-CCA.indication primitive indicates that the OCB secondary channel is idle.
— The virtual CS mechanism (see 10.3.2.1) indicates that the OCB secondary channel is idle, if
dot11VirtualCSonOCBSecondaryImplemented is true.

Otherwise, the NGV STA performing 20 MHz channel access determines that the 20 MHz medium is busy.
NOTE—An NGV STA transmitting a 20 MHz NGV PPDU or 20 MHz non-NGV duplicate PPDU follows rules defined
in 31.2.2 and does not follow rules defined in 11.15.9.

If either the medium of the OCB primary channel or the OCB secondary channel is determined to be busy,
an NGV STA shall invoke the random backoff procedure as described in 10.23.2.2.

When the random backoff procedure is invoked, an NGV STA transmitting a 20 MHz NGV PPDU or
20 MHz non-NGV duplicate PPDU shall perform as described in 10.23.2.4, with the exception of the
definition of the slot boundaries. In this subclause, the slot boundaries are defined as follows:
a) Following AIFSN[AC] × aSlotTime – aRxTxTurnaroundTime of idle medium on the 20 MHz
channel after SIFS (not necessarily idle medium during the SIFS) after the last busy medium on the
antenna that was the result of reception of a frame with a correct FCS.
b) Following EIFS – DIFS + AIFSN[AC] × aSlotTime + aSIFSTime – aRxTxTurnaroundTime of idle
medium on the 20 MHz channel after the last indicated busy medium as determined by the physical
CS mechanism that was the result of a frame reception that has resulted in FCS error, or of a frame
reception that has resulted in a PHY-RXEND.indication (RXERROR) primitive where the value of
RXERROR is not NoError.
c) When any other EDCAF at this STA transmitted a frame requiring immediate acknowledgment, the
earlier of:
1) The end of the AckTimeout interval timed from the PHY-TXEND.confirm primitive, followed
by AIFSN[AC] × aSlotTime + aSIFSTime – aRxTxTurnaroundTime of idle medium on the
20 MHz channel.
2) The end of the first AIFSN[AC] × aSlotTime – aRxTxTurnaroundTime of idle medium on the
20 MHz channel after SIFS (not necessarily medium idle during the SIFS, the start of the SIFS
implied by the length in the PHY header of the previous frame) when a
PHY-RXEND.indication primitive occurs as specified in 10.3.2.11.
d) Following AIFSN[AC] × aSlotTime – aRxTxTurnaroundTime of idle medium on the 20 MHz
channel after SIFS (not necessarily medium idle during the SIFS) after the last busy medium on the
antenna that was the result of transmission of a frame for any EDCAF and that did not require an
acknowledgment and after the expiration of the TXNAV timer if nonzero.
e) Following AIFSN[AC] × aSlotTime + aSIFSTime – aRxTxTurnaroundTime of idle medium on the
20 MHz channel after the last indicated busy medium as indicated by the CS mechanism on the
OCB primary channel that is not covered by a) to d).
f) Following EIFS – DIFS + AIFSN[AC] × aSlotTime + aSIFSTime – aRxTxTurnaroundTime of idle
medium on the 20 MHz channel after the last indicated busy medium as indicated by the CCA
mechanism on the OCB secondary channel that is not covered by a) to d), when the duration of
channel busy is not known.

62
Copyright © 2023 IEEE. All rights reserved.

g) Following AIFSN[AC] × aSlotTime + aSIFSTime – aRxTxTurnaroundTime of idle medium on the

20 MHz channel after the last indicated busy medium as indicated by the CS mechanism on the
OCB secondary channel that is not covered by a) to d), when the duration of channel busy is known.
h) Following aSlotTime of idle medium on the 20 MHz channel, which occurs immediately after any
of these conditions, a) to g), is met for the EDCAF.

If an NGV STA is unable to transmit a 20 MHz NGV PPDU or 20 MHz non-NGV duplicate PPDU because
the medium of the OCB secondary channel is busy and the fallback enabled member of the radio
environment request vector so allows, the STA may instead use the medium access procedure to transmit a
10 MHz PPDU on the OCB primary channel. The medium of the OCB secondary channel is busy if a
PHY-CCA.indication(BUSY, {secondary}) primitive occurs or the virtual CS indicates that the medium is
busy on the OCB secondary channel, if dot11VirtualCSonOCBSecondaryImplemented is true.

31.2.3 A-MSDU operation, A-MPDU operation, and BA operation

NGV STA frame aggregation parameters are fixed and are defined in this clause. This provides the ability to
transmit an A-MPDU and an A-MSDU outside the context of a BSS (OCB). An NGV STA may transmit an
A-MPDU or A-MSDU and shall support the reception of an A-MSDU or A-MPDU with aggregation
parameters as defined in this clause.

An NGV STA shall support receiving an MPDU of length equal to or less than the maximum NGV MPDU
length in Table 31-1. An NGV STA shall not transmit an MPDU with a length greater than the maximum
NGV MPDU length shown in Table 31-1.

Table 31-1—Maximum NGV MPDU length

1SS 10 MHz 2SS 10 MHz 1SS 20 MHz 2SS 20 MHz

NGV-MCS
(octets) (octets) (octets) (octets)

0 4524 7991 7991 7991

1 7991 7991 7991 7991
2 7991 7991 7991 7991
3 7991 7991 7991 7991
4 7991 7991 7991 7991
5 7991 7991 7991 7991
6 7991 7991 7991 7991
7 7991 7991 7991 7991
8 7991 7991 7991 7991
9 N/A N/A 7991 7991
15 2192 4524 4386 7991

NOTE 1—The maximum MPDU length is determined based on a maximum PPDU duration of 10 968 µs.
NOTE 2—The maximum PPDU duration may be reduced by regulatory authorities in some regulatory domains. If the
maximum PPDU duration is less than 10 968 µs, the maximum MPDU length may be limited to a lower value for some
MCSs.

An NGV STA shall transmit adjacent MPDUs in an A-MPDU with a minimum of 2 µs between the
MPDUs.

63
Copyright © 2023 IEEE. All rights reserved.

An NGV STA shall support block ack and does so without exchanging capabilities or creating a block ack
agreement. An NGV STA shall have the following block ack configuration:
— A-MSDU is supported
— Block ack policy is HT-immediate block ack
— No timeout
— The number of buffers available is 32
— Each buffer is capable of holding 7935 octets (the maximum size of an A-MSDU)
— The block ack frame is a Compressed BlockAck frame (see 9.3.1.8.1 and 9.3.1.8.2).

31.2.4 NON_NGV_10 repetition transmission

The NON_NGV_10 repetition transmission mode supports OCB broadcast service to both NGV STAs and
non-NGV STAs with improved frame reception reliability.

This mode allows an NGV STA to repeat one NON_NGV_10 PPDU, defined in 32.1.4, multiple times with
a time gap of SIFS between every two transmissions.

For a group addressed MPDU containing only group addressed MPDUs, the number of repetitions of the
NON_NGV_10 PPDU is decided by a higher layer and indicated by the number of repetitions element of the
radio environment request vector (5.2.3) in the MAC SAP. Otherwise, the number of repetitions of the
NON_NGV_10 PPDU is fixed to 0 by the MAC. The MAC sets the number of repetitions, N_PPDU_REP,
via the PHY service interface using the PHY-TXSTART.request(TXVECTOR) primitive, as described in
Table 32-1.
NOTE—The Duration setting of the Duration/ID field in NON_NGV_10 repetition transmission does not follow the
rules in 9.2.5. An NGV STA that transmits the frames in NON_NGV_10 repetition transmission mode follows the rules
in 10.23.2.9.

31.2.5 Non-NGV duplication operation

A 20 MHz NGV STA may transmit RTS frames in non-NGV duplicate PPDUs to protect a 20 MHz NGV
PPDU.

A 20 MHz NGV STA that is addressed by an RTS frame in a non-NGV or non-NGV duplicate PPDU that
has a bandwidth signaling TA and that has the RXVECTOR parameter
DYN_BANDWIDTH_IN_NON_NGV equal to Static behaves as follows:
— If the NAV indicates idle and CCA indicates idle for the secondary 10 MHz channel when the RTS
frame’s RXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV is equal to CBW20, then the
STA shall respond with a CTS frame carried in a non-NGV duplicate PPDU after a SIFS. The CTS
frame’s TXVECTOR parameters CH_BANDWIDTH and CH_BANDWIDTH_IN_NON_NGV
shall be set to CBW20.
— If the NAV indicates idle when the RTS frame’s RXVECTOR parameter
CH_BANDWIDTH_IN_NON_NGV is equal to CBW10, then the STA shall respond with a CTS
frame carried in a non-NGV PPDU after a SIFS. The CTS frame’s TXVECTOR parameters
CH_BANDWIDTH and CH_BANDWIDTH_IN_NON_NGV shall be set to CBW10.
— Otherwise, the STA shall not respond with a CTS frame.

64
Copyright © 2023 IEEE. All rights reserved.

then the 20 MHz NGV STA shall respond with a CTS frame in a non-NGV duplicate PPDU after a
SIFS. The CTS frame’s TXVECTOR parameters CH_BANDWIDTH and
CH_BANDWIDTH_IN_NON_NGV shall be set to CBW20.
— If the NAV indicates idle and the CCA indicates busy for the secondary 10 MHz channel when the
RTS frame’s RXVECTOR parameter CH_BANDWIDTH_IN_NON_NGV is equal to CBW20,
then the 20 MHz NGV STA shall respond with a CTS frame in a non-NGV PPDU after a SIFS. The
CTS frame’s TXVECTOR parameters CH_BANDWIDTH and
CH_BANDWIDTH_IN_NON_NGV shall be set to CBW10.
— If the NAV indicates idle when the RTS frame’s RXVECTOR parameter
CH_BANDWIDTH_IN_NON_NGV is equal to CBW10, then the 20 MHz NGV STA shall respond
with a CTS frame in a non-NGV PPDU after a SIFS. The CTS frame’s TXVECTOR parameters
CH_BANDWIDTH and CH_BANDWIDTH_IN_NON_NGV shall be set to CBW10.
— Otherwise, the STA shall not respond with a CTS frame.

If a 20 MHz NGV STA receives a frame that solicits a response and is carried in a 20 MHz NGV PPDU, it
should transmit the response in a 20 MHz non-NGV duplicate PPDU.

31.3 Operation in the 60 GHz band

31.3.1 DMG beamforming outside the context of a BSS

A DMG STA with dot11DMGOCBActivated equal to true may transmit DMG Beacon frames as described
in 10.42.4 outside the context of a BSS. The DMG STA shall set the Discovery Mode field and OCB
subfield in the Clustering Control field to 1 in each of the DMG Beacon frames when the STA performs
beamforming training with the DMG Beacon frame outside of the context of a BSS. The STA may set all the
bits in the A-BFT Responder Address subfield to 1 in a DMG Beacon frame to allow any STAs to transmit
SSW or Short SSW frames during A-BFT that follows the BTI in which the DMG Beacon frame is
transmitted, or set the A-BFT Responder Address subfield to an individual address to indicate the STA that
is allowed to transmit during the A-BFT. A DMG OCB element is optionally present in a DMG Beacon
frame to indicate the STA transmitting the DMG Beacon frame supports optional features used during
communication outside the context of a BSS.

When a DMG STA with dot11DMGOCBActivated equal to true receives a DMG beacon frame with the
OCB subfield equal to 1, the STA may perform beamforming training as described in 10.42.5. When the
DMG STA transmits SSW frames during the A-BFT after a BTI in which the STA received a DMG beacon
frame with the OCB subfield equal to 1, the STA shall set the OCB subfield to 1 in the SSW frames
transmitted during the A-BFT.

If a responder DMG STA that receives a DMG beacon frame with the OCB subfield equal to 1 has
successfully completed an SLS or a BRP with the initiator STA that transmitted the DMG Beacon frame
recently, the responder STA should not transmit SSW frames during the A-BFT following the BTI to avoid
collisions during the A-BFT.

A DMG STA with dot11DMGOCBActivated equal to true may transmit SSW frames as described in
10.42.6 outside the context of a BSS. The DMG STA shall set the OCB subfield to 1 in the SSW frames
during beamforming training outside of the context of a BSS.

A DMG STA with dot11DMGOCBActivated equal to true shall support Beamformed link maintenance
procedure as described in 11.27.1.1.

65
Copyright © 2023 IEEE. All rights reserved.

31.4 NGV ranging

An NGV STA may support NGV ranging. NGV ranging is a subset of fine timing measurement (FTM)
functionalities defined in 11.21.6; the supported functionalities are as follows:
— Fine timing measurement procedures, including FTM procedure negotiation and FTM session
termination for non-TB ranging as defined in 11.21.6.3 and in 11.21.6.6, with the modifications
specified in this subclause.
— Non-TB ranging as described in 11.21.6.4.4 with the modifications specified in this subclause. PHY
security is not specified for NGV STAs.
— NGV STAs may support differential distance computation as detailed in P.3.

Additionally, if an NGV STA is co-located with a STA that supports Fine Timing Measurement (FTM)
functionalities as defined in 11.21.6, it may support Fine Timing Measurement procedure outside the
5.9 GHz frequency band.

The capability discovery for whether an NGV STA supports ranging as specified in this subclause is out of
the scope of IEEE Std 802.11 and is expected to be conducted by higher layers. The higher layer exchanges
are over the 5.9 GHz frequency band. The higher layer negotiations are expected to identify the following:
— Whether an NGV STA supports non-TB ranging in the 5.9 GHz band.
— Whether an NGV STA is co-located with a STA that supports ranging on IEEE 802.11 bands
outside the 5.9 GHz band and if so the type of ranging: non-TB ranging and/or EDCA based ranging
(see 11.21.6.1.1 and 11.21.6.1.2).
— For an NGV STA co-located with a STA that supports ranging on 802.11 bands outside the 5.9 GHz
band, whether the co-located STA supports PASN, and if so, the contents of the PASN Parameters
element, or alternatively the security context required for exchange of protected frames.
— The channel number for ranging exchanges between peer STAs.
— Role of STA: ISTA or RSTA.
— LMR Feedback policy.
NOTE—The channel number is not limited to the 5.9 GHz band.

The fine timing measurement procedure negotiation is performed by an NGV STA as specified in 11.21.6.3
with the following differences:
— For ranging in the 5.9 GHz band, in the Ranging Parameters element included in the IFTMR frame:
— Status indication subfield and Value subfield are reserved.
— Max R2I STS > 80 MHz subfield is reserved.
— Max I2R STS > 80 MHz subfield is reserved.
— BSS Color Information subfield is reserved.
— For ranging in the 5.9 GHz band, a non-TB ranging measurement exchange is used by NGV STAs
as defined in 11.21.6.4.4 with the following changes:
— An NGV ranging NDP is transmitted instead of an HE ranging NDP.
— A Ranging NDP Announcement frame (9.3.1.19) is transmitted. The following differences in
the subfields of the STA Info fields of the Ranging NDP Announcement frame apply
compared to 9.3.1.19:
— LTF Offset is set to 0.
— R2I N_STS subfield is set to the number of spatial streams of the R2I NGV ranging NDP
minus 1.
— R2I Rep subfield is set to 0 if the NGV-LTF in the R2I NGV ranging NDP is not repeated
and is set to 1 if the NGV-LTF in the R2I NGV ranging NDP is repeated.

66
Copyright © 2023 IEEE. All rights reserved.

— I2R N_STS subfield is set to the number of spatial streams of the I2R NGV ranging NDP
minus 1.
— I2R Rep subfield is set to 0 if the NGV-LTF in the I2R NGV ranging NDP is not repeated
and is set to 1 if the NGV-LTF in the I2R NGV ranging NDP is repeated.
— The I2R N_STS and I2R Rep subfields are used to indicate the following I2R NGV
ranging NDP’s NGV-LTF configuration, 32.3.16, while the R2I N_STS and R2I Rep
subfields indicate the NGV-LTF configuration of the R2I NGV ranging NDP sent in
response by the RSTA, see 11.21.6.4.4.
— When the TXVECTOR parameter CH_BANDWIDTH is CBW10, the I2R NDP Tx
Power subfield indicates the combined average power per 10 MHz bandwidth referenced
to the antenna connector, of all antennas used to transmit the following I2R NDP.

For ranging on IEEE Std 802.11 bands outside the 5.9 GHz band, whether PASN is required is indicated by
higher layers. Two STAs co-located with NGV STAs may establish PASN authentication if so indicated by
higher layers using the procedures as defined in 12.13 with the following change: the exchanges between
ISTA and RSTA are done by two STAs each co-located with an NGV STA. Alternatively, the security
association between the two STAs may be established by higher layer exchanges in the 5.9 GHz band.

31.5 NGV MAC data service

An NGV STA shall follow the rules in 10.2.7 and the additional rules as defined in this subclause.

When a member in radio environment request vector represents “selection within MAC sublayer”, the NGV
STA shall select the related member value by itself. Otherwise the following rules shall be applied:
— When transmitting an MPDU that encapsulates an MSDU, an NGV STA shall use the PPDU format
indicated by the PPDU format member of the radio environment request vector related to the
MSDU.
— When transmitting an MPDU that encapsulates an MSDU, an NGV STA shall use the data
rate/NGV-MCS indicated by the data rate/NGV-MCS member of the radio environment request
vector related to the MSDU in the initial transmission of the MPDU. In the retransmission of the
MPDU, the data rate/NGV-MCS shall be no more than data rate/NGV-MCS indicated by the data
rate/NGV-MCS member of the radio environment request vector related to the MSDU.
— When transmitting an MPDU that encapsulates an MSDU, an NGV STA shall use the number of
spatial streams indicated by the number of spatial streams member of the radio environment request
vector related to the MSDU in the initial transmission of the MPDU. In the retransmission of the
MPDU, the number of spatial streams shall be no more than the number of spatial streams indicated
by the number of spatial streams member of the radio environment request vector related to the
MSDU.
— An NGV STA shall transmit a frame that encapsulates an MSDU in an A-MPDU if the permitted
aggregation member of the radio environment request vector related to the MSDU is equal to 1.
Otherwise the NGV STA shall not aggregate the frame in an A-MPDU.
— An NGV STA shall set the lifetime of an MSDU to the value of expiry time member of the radio
environment request vector related to the MSDU.
— An NGV STA shall transmit an MPDU that encapsulates an MSDU in the channel defined by the
channel member, primary channel member, and channel width member of the radio environment
request vector related to the MSDU with the following exception:
— If the channel width indicates 20 MHz channel width and the fallback enabled parameter
indicates 1, the channel can be 10 MHz channel.

67
Copyright © 2023 IEEE. All rights reserved.

— An NGV STA shall transmit an MPDU that encapsulates an MSDU with the transmit power
indicated by the transmit power spectral density member of the radio environment request vector
related to the MSDU.
NOTE—The higher layer sets the parameters in the radio environment request vector based on the NGV STA’s
capabilities.

When reporting a received MSDU to a higher layer, an NGV STA shall report the radio environment status
vector of the received MSDU as defined in 5.2.4.

31.6 Radio environment measurement

An NGV STA provides periodic reports on the radio environment.

If requested by a higher layer, an NGV STA with dot11RadioEnvironmentMeasurementPeriod not equal to

0 shall measure the channel busy percentage and report the measurement results to a higher layer as defined
in 6.3.127.

If requested by a higher layer, an NGV STA with dot11StationMeasurementPeriod not equal to 0 shall
measure the number of neighboring STAs (non-NGV STAs and NGV-STAs) and the number of
neighboring NGV STAs, and report these measurement results to a higher layer as defined in 6.3.127.

An NGV STA with both dot11StationMeasurementPeriod and dot11RadioEnvironmentMeasurementPeriod

not equal to 0 shall start a STA measurement period at the same time as a radio environment measurement
period.

68
Copyright © 2023 IEEE. All rights reserved.

32. Next Generation V2X (NGV) PHY specification

32.1 Introduction

32.1.1 Introduction to NGV PHY

Clause 32 specifies the PHY entity for an NGV orthogonal frequency division multiplexing (OFDM)
system. In addition to the requirements in Clause 32, an NGV STA shall be capable of transmitting and
receiving 10 MHz PPDUs specified in Clause 17.

The NGV PHY is mainly based on the VHT PHY defined in Clause 21, which in turn is based on the HT
PHY defined in Clause 19, which in turn is further based on the OFDM PHY defined in Clause 17. The
NGV PHY preamble structure, BPSK-dual carrier modulation (DCM), and midamble structure are based on
the HE PHY defined in Clause 27.

The NGV PHY provides support for both 10 MHz and contiguous 20 MHz channel widths. The NGV PHY
data subcarrier frequency spacing is a half of VHT PHY and HT PHY subcarrier frequency spacing defined
in Clause 21 and Clause 19, respectively.

The NGV PHY data subcarriers are modulated using binary phase shift keying (BPSK), BPSK-DCM,
quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), 64-QAM, and
256-QAM. The NGV PHY preamble is encoded by a convolutional encoder and the NGV PHY data
payload is encoded by an LDPC encoder. STBC is not employed.

The NGV PHY supports the regulatory requirements in 32.3.15.

An NGV STA shall support the following features:

— Single spatial stream
— NGV-MCS 0 to 9 and NGV-MCS 15
— Three LTF formats: NGV-LTF-1x, NGV-LTF-2x, and NGV-LTF-2x-Repeat
— LDPC coding (transmit and receive)
— Midamble periodicity of 4, 8, 16 OFDM symbols
— 10 MHz NGV PPDU
— NON_NGV_10 PPDU and repetitive NON_NGV_10 PPDU
— Transmit spectrum mask C2 when transmitting a 20 MHz NGV PPDU or 20 MHz non-NGV
duplicate PPDU, if 20 MHz NGV PPDU is supported
— Transmit spectrum mask A, B, C, or D when transmitting a 10 MHz NGV PPDU, if the STA
belongs to transmit power class A, B, C, or D, respectively

An NGV STA may support the following features:

— Transmission and reception of SU MIMO with two spatial streams
— NGV ranging NDP for NGV ranging as described in 31.4
— 20 MHz NGV PPDU or 20 MHz non-NGV duplicate PPDU

32.1.2 Scope

The services provided to the MAC by the NGV PHY consist of the following protocol functions:
a) A function that maps the PSDU received from the MAC into a PPDU for transmission to one or
more receiving STAs.

69
Copyright © 2023 IEEE. All rights reserved.

b) A function that defines the characteristics and method of transmitting and receiving data through a
wireless medium between two or more STAs. Depending on the PPDU format, these STAs support
a mixture of NGV and Clause 17 PHYs.

32.1.3 NGV PHY functions

32.1.3.1 General

The NGV PHY contains two functional entities: the PHY function, and the physical layer management
function (via the PLME). These functions are described in detail in 32.3 and 32.4, respectively. The NGV
PHY service is provided to the MAC through the PHY service primitives defined in Clause 8. The NGV
PHY service interface is described in 32.2.

32.1.3.2 PHY layer management entity (PLME)

The PLME performs management of the local PHY functions in conjunction with the MLME.

32.1.3.3 Service specification method

The models represented by figures and state diagrams are intended to be illustrations of the functions
provided. It is important to distinguish between a model and a real implementation. The models are
optimized for simplicity and clarity of presentation.

The service of a layer is the set of capabilities that it offers to a user in the next higher layer. Abstract
services are specified here by describing the service primitives and parameters that characterize each
service. This definition is independent of any particular implementation.

32.1.4 PPDU Formats

The structure of the PPDU transmitted by an NGV STA is determined by the TXVECTOR parameters as
defined in Table 32-1.

In an NGV STA the FORMAT parameter determines the overall structure of the PPDU and can take one of
the following values:
— Non-NGV format of 10 MHz bandwidth (NON_NGV_10), for the PPDU format as specified in
Clause 17 for 10 MHz channel spacing including non-NGV duplicate format.
— NGV format (NGV), for the PPDU format as specified in Clause 32.
NOTE—Required support for these formats is defined in 17.1 and 32.1.1.

32.2 NGV PHY service interface

32.2.1 Introduction

The PHY provides an interface to the MAC through an extension of the generic PHY service interface
defined in 8.3.4. The interface includes TXVECTOR, RXVECTOR, and PHYCONFIG_VECTOR.

The MAC uses the TXVECTOR to supply the PHY with per-PPDU transmit parameters. The PHY uses the
RXVECTOR to inform the MAC of the received PPDU parameters. The MAC uses the
PHYCONFIG_VECTOR to configure the PHY for operation that is independent of frame transmission or
reception.

70
Copyright © 2023 IEEE. All rights reserved.

32.2.2 TXVECTOR and RXVECTOR

The parameters in Table 32-1 are defined as part of the TXVECTOR parameter list in the
PHY-TXSTART.request primitive and/or as part of the RXVECTOR parameter list in the
PHY-RXSTART.indication primitives.

Table 32-1—TXVECTOR and RXVECTOR parameters

RXVECTOR
TXVECTOR
Parameter

Condition Value

Determines the format of the PPDU. Y Y

Enumerated type:
FORMAT

NON_NGV_10 indicates the PPDU format for 10 MHz

channel spacing as defined in Clause 17 or non-NGV duplicate
PPDU format as defined in 32.3.9.10.
NGV indicates NGV PPDU format as defined in Clause 32.

FORMAT is NGV Not present. N N

NOTE—The value of the Length field of the L-SIG in an NGV
L_LENGTH

PPDU is calculated as in Equation (32-8).

Otherwise Indicates the length of the PSDU in octets in the range 1 to Y Y

4095. The value is used by the PHY to determine the number
of octet transfers that occur between the MAC and the PHY.

FORMAT is NGV Not present. N N

L_DATARATE

NOTE—The RATE field in the L-SIG field in an NGV PPDU

is set to the value representing 3 Mb/s in the 10 MHz channel
spacing column of Table 17-6.

Otherwise Indicates the rate, in Mb/s, used to transmit the PSDU. Y Y

See corresponding entry in Table 17-1 and Table 17-2.

FORMAT is NGV Not present. N N

SERVICE

Otherwise Scrambler initialization, null. Y N

FORMAT is NGV The allowed values for the TXPWR_LEVEL_INDEX Y N

TXPWR_LEVEL_INDEX

parameter are in the range 1 to N/2, where N is the number of

octets in dot11TxPowerLevelExtended. This parameter is used
to indicate the available transmit output power levels defined
in dot11TxPowerLevelExtended that shall be used for the
current transmission.

Otherwise 1–8 Y N

Refer to 17.2.2.5 for the definition of

TXPWR_LEVEL_INDEX.

71
Copyright © 2023 IEEE. All rights reserved.

Table 32-1—TXVECTOR and RXVECTOR parameters (continued)

RXVECTOR
TXVECTOR
Parameter

Condition Value

FORMAT is NGV The allowed values for the RSSI parameter are in the range 0 N Y
to 255. This parameter is a measure by the PHY of the power
observed at the antenna connector used to receive the current
PPDU measured during the reception of the NGV-LTF field.
RSSI is intended to be used in a relative manner, and it shall be
RSSI

a monotonically increasing function of the received power.

Otherwise 0–RSSI maximum. N Y

See 17.2.3.3 for the definition of RSSI.

FORMAT is NGV Indicates the modulation and coding scheme used in the Y Y
transmission of the PPDU.
Integer in the range:
NGV-MCS

0 to 8 and 15 for 10 MHz PPDU.

0 to 9 and 15 for 20 MHz PPDU.

NOTE—Set to 0 for NGV ranging NDP. See 32.3.16

Otherwise Not present. N N

FORMAT is NGV Indicates the channel width of the transmitted PPDU. Y Y

CH_BANDWIDTH

Enumerated type:
CBW10 for 10 MHz.
CBW20 for 20 MHz.

Otherwise Not present. N N

FORMAT is NGV Indicates the number of transmit chains. Y N

N_TX

Otherwise Not present. N N

FORMAT is NGV Indicates the midamble periodicity in the Data field. Y Y

MIDAMBLE_PERIODICITY

Integer values:
Set to 0 to indicate the midamble periodicity of 4 OFDM
symbols.
Set to 1 to indicate the midamble periodicity of 8 OFDM
symbols.
Set to 2 to indicate the midamble periodicity of 16 OFDM
symbols.
Other values are reserved.

Otherwise Not present. N N

72
Copyright © 2023 IEEE. All rights reserved.

Table 32-1—TXVECTOR and RXVECTOR parameters (continued)

RXVECTOR
TXVECTOR
Parameter

Condition Value

FORMAT is NGV Indicates the type of NGV-LTF. Y Y

Set to 0 to indicate NGV-LTF-2x is used in the transmitted

PPDU.
NGV_LTF_TYPE

Set to 1 to indicate NGV-LTF-1x is used in the transmitted

PPDU.

NOTE—When NGV-MCS 15 is indicated in 10 MHz,

Repeated NGV-LTF-2x is used in the transmitted PPDU. See
32.3.8.10.

Otherwise Not present. N N

FORMAT is NGV Not present. N N

N_PPDU_REP

FORMAT is NON_NGV_10 Indicates the number of repetitive transmissions of Y Y

NON_NGV_10 PPDU after the initial transmission. The
allowed values are in the range 0 to 3.

FORMAT is NGV Indicates the number of spatial streams. Y Y

The allowed value:
NUM_SS

Set to 0 to indicate the number of spatial streams is one.

Set to 1 to indicate the number of spatial streams is two

Otherwise Not present. N N

FORMAT is NON_NGV_10 In the TXVECTOR, indicates the format of the transmitted Y Y

non-NGV PPDU.
NON_NGV_MODULATION

In the RXVECTOR, indicates the estimated format of the

received non-NGV PPDU.

Enumerated type:
OFDM indicates Clause 17 format.

NON_NGV_10_DUP_OFDM indicates non-NGV duplicate

PPDU format.

Otherwise Not present. N N

FORMAT is NGV If 0, indicates an NGV ranging NDP. Y N

APEP_LENGTH

Otherwise, indicates the number of octets in the range 1 to

aPSDUMaxLength in the A-MPDU pre-EOF padding (see
Table 32-20) that is carried in the PSDU.

Otherwise Not present. N N

73
Copyright © 2023 IEEE. All rights reserved.

Table 32-1—TXVECTOR and RXVECTOR parameters (continued)

RXVECTOR
TXVECTOR
Parameter

Condition Value

FORMAT is NGV Indicates the number of octets in the range 0 to N Y

PSDU_LENGTH

aPSDUMaxLength octets (see Table 32-20) in the NGV

PSDU. The value of 0 indicates an NGV ranging NDP.

Otherwise Not present. N N

FORMAT is NON_NGV_10 In the TXVECTOR, if present, indicates whether the O Y

transmitter is capable of Static or Dynamic bandwidth
operation.
DYN_BANDWIDTH_IN_NON_NGV

In the RXVECTOR, if valid, indicates whether the transmitter

is capable of Static or Dynamic bandwidth operation.

Enumerated type:
Static if the transmitter is capable of Static bandwidth
operation.

Dynamic if the transmitter is capable of Dynamic bandwidth

operation.

NOTE—In the RXVECTOR, the validity of this parameter is

determined by the MAC based on the contents of the received
MPDU.

Otherwise Not present. N N

FORMAT is NON_NGV_10 In the TXVECTOR, if present, indicates the channel width of O Y

the transmitted PPDU, which is signaled via the scrambling
sequence.
CH_BANDWIDTH_IN_NON_NGV

In the RXVECTOR, if valid, indicates the channel width of the

received PPDU, which is signaled via the scrambling
sequence.

Enumerated type:
CBW10, CBW20.

NOTE—In the RXVECTOR, the validity of this parameter is

determined by the MAC based on the contents of the currently
received MPDU (e.g., RTS) or the previous MPDU in an
exchange (e.g., RTS preceding a CTS).

Otherwise Not present. N N

74
Copyright © 2023 IEEE. All rights reserved.

Table 32-1—TXVECTOR and RXVECTOR parameters (continued)

RXVECTOR
TXVECTOR
Parameter

Condition Value

Enumerated type:
TIME_OF_DEPARTURE_REQUESTED

true indicates that the MAC entity requests that the PHY entity measures and reports time of
departure parameters corresponding to the time when the first frame energy is sent by the
transmitting port. false indicates that the MAC entity requests that the PHY entity neither
measures nor reports time of departure parameters.

O N

FORMAT is NGV and Indicates the number of repetitions of the NGV-LTF symbols. O N
LTF_REP

APEP_LENGTH is 0 Set to the number of repetitions.

Otherwise Not present. N N

NOTE—In the “TXVECTOR” and “RXVECTOR” columns, the following apply:

Y = Present;
N = Not present;
O = Optional.

32.2.3 PHY CONFIG_VECTOR

The PHYCONFIG_VECTOR carried in a PHY-CONFIG.request primitive for the NGV PHY contains an
OPERATING_CHANNEL parameter, which identifies the operating or primary channel. The PHY shall set
dot11CurrentPrimaryChannel to the value of parameter OPERATING_CHANNEL.

The PHYCONFIG_VECTOR carried in a PHY-CONFIG.request primitive for the NGV PHY contains a
SECONDARY_CHANNEL_OFFSET parameter, which takes one of the following values:
— SECONDARY_CHANNEL_NONE if no secondary channel is present; in this case the PHY shall
set dot11CurrentSecondaryChannel to 0.
— SECONDARY_CHANNEL_ABOVE if the channel number of the secondary channel is greater
than the channel number of the primary channel; in this case the PHY shall set
dot11CurrentSecondaryChannel to dot11CurrentPrimaryChannel + 2.
— SECONDARY_CHANNEL_BELOW if the channel number of the secondary channel is smaller
than the channel number of the primary channel; in this case the PHY shall set
dot11CurrentSecondaryChannel to dot11CurrentPrimaryChannel – 2.

75
Copyright © 2023 IEEE. All rights reserved.

32.2.4 Effects of CH_BANDWIDTH parameter on PPDU format

Table 32-2 shows the valid combinations of the FORMAT, NON_NGV_MODULATION, and
CH_BANDWIDTH parameters and the corresponding PPDU format.

Table 32-2— Interpretation of FORMAT, NON_NGV_MODULATION, and CH_BANDWIDTH

parameters

FORMAT NON_NGV_MODULATION CH_BANDWIDTH PPDU format

NGV N/A CBW10 The STA transmits an NGV PPDU

of 10 MHz bandwidth.

NGV N/A CBW20 The STA transmits an NGV PPDU

of 20 MHz bandwidth.

NON_NGV_10 OFDM N/A The STA transmits a non-NGV

PPDU of 10 MHz bandwidth.

NON_NGV_10 NON_NGV_10_DUP_OFDM N/A The STA transmits a

NON_NGV_10 PPDU with
NON_NGV_MODULATION set
to NON_NGV_10_DUP_OFDM
using two adjacent 10 MHz
channels as defined in 32.3.9.10.
The 10 MHz channel higher in
frequency is rotated +90º relative to
the 10 MHz channel lower in
frequency as defined in
Equation (32-5).

32.2.5 Support for NON_NGV format

32.2.5.1 General

An NGV STA logically contains Clause 17 and Clause 32 PHYs. The MAC interfaces to the PHYs via the
Clause 17 and Clause 32 PHY service interfaces as shown in Figure 32-1, Figure 32-2, and Figure 32-3.

76
Copyright © 2023 IEEE. All rights reserved.

Clause 32 Clause 32 PHY-TXSTART.request(TXVECTOR)

PHY-TXSTART.confirm
PHY-DATA.request FORMAT = NON_NGV_10 FORMAT = NGV
FORMAT = NON_NGV_10
PHY-DATA.confirm and and NON_NGV_MODULATION
NON_NGV_MODULATION =
PHY-TXEND.request OFDM
= NON_NGV_10_DUP_OFDM
PHY-TXEND.confirm

Clause 17 32.2.5.2
Clause 17

TXVECTOR

TXVECTOR
PHY-TXSTART.confirm PHY-TXSTART.confirm
Clause 17
PHY-DATA.request PHY-DATA.request
PHY-TXSTART.
PHY-DATA.confirm PHY-DATA.confirm
request
PHY-TXEND.request PHY-TXEND.request
(TXVECTOR)
PHY-TXEND.confirm PHY-TXEND.confirm

Clause 17 Transmit procedure Clause 17 Clause 32

Transmit 32.3.9 Non-NGV NGV-PPDU
procedure duplicate PPDU

Clause 32 Transmit procedure

Figure 32-1—PHY interaction on transmit for various PPDU formats

Clause 32 PHY-RXSTART.indication (RXVECTOR)

Clause 32
PHY-DATA.indication
PHY-RXEND.indication

32.2.5.2 Clause 17
PHY-DATA.indication
PHY-RXEND.indication

Clause 17 Clause 17
PHY-RXSTART. Receive procedure
Clause 32
indication
Receive procedure
(RXVECTOR)

NON_NGV_10 + NON_NGV_10 +
OFDM NON_NGV_10_DUP_OFDM
NGV

Format detection

Figure 32-2—PHY interaction on receive for various PPDU formats

77
Copyright © 2023 IEEE. All rights reserved.

Clause 32 PHY-CONFIG.request Clause 32 PHY-

Clause 32 PHY-CONFIG.confirm
(PHYCONFIG_VECTOR) CCARESET.request
PHY-CCARESET.confirm
PHY-CCA.indication

Configure all PHYs Configure confirmation of all PHYs

PHY-CCA and PHY-CCARESET primitives
from Clause 17 are unused (CCA requirement
are defined in Clause 32 instead)

Clause 17 PHY-
Clause 32 Clause 17 PHY-
CONFIG.request Clause 32
CONFIG.confirm
(PHYCONFIG_VECTOR)

Figure 32-3—PHY-CONFIG and CCA interaction with Clause 17 and Clause 32

32.2.5.2 Support for NON_NGV format

When a PHY-TXSTART.request(TXVECTOR) primitive with the FORMAT parameter equal to

NON_NGV_10 is issued, the behavior of the NGV PHY is defined in Clause 17 with additional
requirements described in the following subclauses:
— 32.3.11.1 instead of 17.3.9.3
— 32.3.11.4.2 instead of 17.3.9.7.2

where the Clause 32 TXVECTOR parameters in Table 32-1 are mapped to Clause 17 TXVECTOR
parameters in Table 17-1 according to Table 32-3.

When the NGV PHY receives a Clause 32 PHY-CONFIG.request(PHYCONFIG_VECTOR) primitive, the

NGV PHY shall, for the purpose of OFDM PPDU transmission and reception, behave as if it were a
Clause 17 PHY that had received a PHY-CONFIG.request(PHYCONFIG_VECTOR) primitive but with the
SECONDARY_CHANNEL_OFFSET parameter discarded from PHYCONFIG_VECTOR.

As defined in 32.3.14, once a PPDU is received and detected as a non-NGV PPDU, the behavior of the NGV
PHY is defined in Clause 17. The RXVECTOR parameters from the Clause 17 PHY-RXSTART.indication
primitive are mapped to the Clause 32 RXVECTOR parameters as defined in Table 32-3. NGV PHY
parameters not listed in the table are not present.

Table 32-3—Mapping of the NGV PHY parameters for non-NGV operation

5.9 GHz operation defined

NGV parameters Parameter list
by Clause 17

L_LENGTH L_LENGTH TXVECTOR/RXVECTOR

L_DATARATE L_DATARATE TXVECTOR/RXVECTOR

TXPWR_LEVEL_INDEX TXPWR_LEVEL_INDEX TXVECTOR

RSSI RSSI RXVECTOR

SERVICE SERVICE TXVECTOR/RXVECTOR

OPERATING_CHANNEL OPERATING_CHANNEL PHYCONFIG_VECTOR

SECONDARY_CHANNEL_OFFSET Discarded PHYCONFIG_VECTOR

78
Copyright © 2023 IEEE. All rights reserved.

32.2.5.3 Repetition transmission of NON_NGV_10 PPDU

NGV STA shall support NON_NGV_10 PPDU repetition transmission mode. When a
PHY-TXSTART.request(TXVECTOR) primitive with the FORMAT parameter equal to NON_NGV_10
and N_PPDU_REP being nonzero, the NON_NGV_10 repetition transmission mode shall be used by the
PHY layer.

In this mode, the NON_NGV_10 PPDU is transmitted 1 + N_PPDU_REP times in sequence, where
N_PPDU_REP is the number of repetitions following the first transmission, and N_PPDU_REP is indicated
through TXVECTOR.

The time separation between every two repeated transmissions is indicated by parameter aSIFSTime (see
Table 32-20), as illustrated in Figure 32-4.

NON_NGV_10 PPDU NON_NGV_10 PPDU NON_NGV_10 PPDU

aSIFSTime aSIFSTime

Figure 32-4—Example of NON_NGV_10 repetition transmission with N_PPDU_REP = 2

NOTE—All the following N_PPDU_REP repetition PPDUs use the same scrambler as the first NON_NGV_10
PPDU.

32.2.5.4 TXSTATUS parameters

The parameters listed in Table 32-4 are defined as part of the TXSTATUS parameter list in the
PHY-TXSTART.confirm(TXSTATUS) service primitive.

Table 32-4—TXSTATUS parameters

Parameter Value

TIME_OF_DEPARTURE 0 to 232 – 1. The locally measured time when the

first frame energy is sent by the transmitting port,
in units equal to
1/TIME_OF_DEPARTURE_ClockRate.
This parameter is present only if
TIME_OF_DEPARTURE_REQUESTED is true in
the corresponding request.

TIME_OF_DEPARTURE_ClockRate 0 to 216 – 1. The clock rate, in units of MHz, is

used to generate the TIME_OF_DEPARTURE
value. This parameter is present only if
TIME_OF_DEPARTURE_REQUESTED is true in
the corresponding request.

TX_START_OF_FRAME_OFFSET 0 to 232 – 1. An estimate of the offset (in

10 nanosecond units) from the point in time at
which the start of the preamble corresponding to
the frame was transmitted at the transmit antenna
connector to the point in time at which this
primitive is issued to the MAC.

79
Copyright © 2023 IEEE. All rights reserved.

32.3 NGV PHY

32.3.1 Introduction

This subclause provides the procedure by which PSDUs are converted to and from transmissions on the
wireless medium.

During transmission, a single PSDU is processed and appended to the NGV PHY preamble including
L-STF, L-LTF, L-SIG, RL-SIG, NGV-SIG, RNGV-SIG, NGV-STF, and NGV-LTF fields to create the
NGV PPDU. At the receivers, the PHY preamble is processed to aid in the detection, demodulation, and
delivery of the PSDU.

32.3.2 NGV PPDU format

A single PPDU format is defined for this PHY: the NGV PPDU format. The format of NGV PPDU is
defined in Figure 32-5.

Variable duration per

16 µs 16 µs 8 µs 8 µs 8 µs 8 µs 8 µs NGV-LTF symbol

NGV- RNGV- NGV-

L-STF L-LTF L-SIG RL-SIG SIG SIG STF
NGV-LTF NGV-data

Figure 32-5—NGV PPDU format

The fields of the NGV PPDU format are summarized in Table 32-5.

Table 32-5—Fields of the NGV PPDU

Field Description

L-STF Non-HT Short Training field

L-LTF Non-HT Long Training field

L-SIG Non-HT SIGNAL field

RL-SIG Repeated Non-HT SIGNAL field

NGV-SIG NGV Signal field

RNGV-SIG Repeated NGV Signal field

NGV-STF NGV Short Training field

NGV-LTF NGV Long Training field

Data The Data field carrying the PSDU(s)

80
Copyright © 2023 IEEE. All rights reserved.

The RL-SIG, NGV-SIG, RNGV-SIG, NGV-STF, and NGV-LTF fields are present only in NGV PPDU
formats. The RNGV-SIG field is equal to NGV-SIG field. The fields present in a non-NGV PPDU are the
L-STF, L-LTF, L-SIG, and Data fields. The number of symbols in the NGV-LTF field, N NGV-LTF , can be 1,
2, or 4 and is determined by the total number of spatial streams being transmitted in the NGV PPDU and
whether the NGV-LTF is repeated in NGV ranging NDP (see Table 32-11).

32.3.3 Transmitter block diagram

The generation of each field in an NGV PPDU uses many of the following blocks:
a) PHY padding
b) Scrambler
c) FEC (BCC or LDPC) encoders
d) Stream parser
e) BCC interleaver
f) Constellation mapper
g) Pilot insertion
h) Replication over two 10 MHz channels (for BW = 20 MHz)
i) CSD per spatial stream insertion
j) Spatial mapper
k) IDFT
l) CSD per chain insertion
m) GI insertion
n) Windowing

Figure 32-6 and Figure 32-7 show example transmitter block diagrams. The actual structure of the
transmitter is implementation dependent.

In particular, Figure 32-6 shows the transmit process for the L-SIG, RL-SIG, NGV-SIG, and RNGV-SIG
fields of an NGV PPDU. The BCC encoder and interleaver are not used when generating the L-STF and
L-LTF fields. The same BCC interleaver is applied to both the NGV-SIG field and the RNGV-SIG field
such that the baseband signals of the NGV-SIG field symbol and the RNGV-SIG field symbol are exactly
the same.

81
Copyright © 2023 IEEE. All rights reserved.

Insert GI
Analog
and
and RF
Window

Duplicate over two 10 MHz
Constellation Mapper
BCC Interleaver

if BW = 20 MHz
BCC Encoder
CSD Insert GI
Analog
per and

IDFT
and RF
chain Window

...

...
CSD Insert GI
Analog
per and
and RF
chain Window
Single Spatial Stream

NTX Transmit Chains

Figure 32-6—Transmitter block diagram for the L-SIG, RL-SIG, NGV-SIG, and RNGV-SIG
fields for an NGV PPDU

Figure 32-7 shows the transmitter blocks used to generate the Data field of an NGV transmission. The
BPSK-DCM tone mapping, which is part of the constellation mapper block, is applied only if BPSK-DCM
is indicated by NGV-MCS field value 15 in NGV-SIG field.
Constellation

Pilot Insertion

Insert GI
Mapper

Analog
IDFT

and
and RF
Post‐FEC PHY Padding
Pre‐FEC PHY Padding

Window
Spatial Mapping
Stream Parser
LDPC Encoder
Scrambler

...
Constellation

Pilot Insertion

CSD per SS

Insert GI
Mapper

Analog
IDFT

and
and RF
Window

NOTE—Transmission with two spatial streams is optional.

Figure 32-7—Transmitter block diagram for the Data field of an NGV transmission

32.3.4 Overview of the PPDU encoding process

32.3.4.1 General

This subclause provides an overview of the NGV PPDU encoding process.

82
Copyright © 2023 IEEE. All rights reserved.

32.3.4.2 Construction of L-STF

Construct the L-STF field as defined in 32.3.8.3 with the following highlights:
a) Determine the CH_BANDWIDTH from the TXVECTOR.
b) Sequence generation: Generate the L-STF sequence over the CH_BANDWIDTH as described in
32.3.8.3.
c) Phase rotation: Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
d) IDFT: Compute the inverse discrete Fourier transform.
e) CSD: Apply CSD for each transmit chain as described in 32.3.8.2.1.
f) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
g) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

32.3.4.3 Construction of the L-LTF

Construct the L-LTF field as defined in 32.3.8.4 with the following highlights:
a) Determine the CH_BANDWIDTH from the TXVECTOR.
b) Sequence generation: Generate the L-LTF sequence over the CH_BANDWIDTH as described in
32.3.8.4.
c) Phase rotation: Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
d) IDFT: Compute the inverse discrete Fourier transform.
e) CSD: Apply CSD for each transmit chain as described in 32.3.8.2.1.
f) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
g) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

32.3.4.4 Construction of the L-SIG and RL-SIG

Construct the L-SIG field as the SIGNAL field defined in 32.3.8.5 with the following highlights:
a) In an NGV PPDU set the RATE subfield in the SIGNAL field to 3 Mb/s in the 10 MHz channel
spacing column of Table 17-6. Set the Length, Parity, and Tail bits in the SIGNAL field as described
in 32.3.8.5.
b) BCC encoder: Encode the SIGNAL field by a convolutional encoder at the rate of R=1/2 as
described in 17.3.5.6.
c) BCC interleaver: Interleave as described in 17.3.5.7.
d) Constellation Mapper: BPSK modulate as described in 17.3.5.8.
e) Pilot insertion: Insert pilots as described in 17.3.5.9.
f) Duplication and phase rotation: Duplicate the L-SIG field over each 10 MHz of the
CH_BANDWIDTH. Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
g) IDFT: Compute the inverse discrete Fourier transform.
h) CSD: Apply CSD for each transmit chain as described in 32.3.8.2.1.
i) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.

83
Copyright © 2023 IEEE. All rights reserved.

j) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

Construct the RL-SIG field as the repeat SIGNAL field defined in 32.3.8.6 with the same process as for the
L-SIG field.

32.3.4.5 Construction of the NGV-SIG and RNGV-SIG

The NGV-SIG field consists of one symbol as defined in 32.3.8.7 and is constructed as follows:
a) Obtain the NGV-SIG field values from the TXVECTOR entries of NGV-MCS,
CH_BANDWIDTH, MIDAMBLE_PERIODICITY, NGV_LTF_TYPE, NUM_SS, and LTF_REP.
Add the reserved bits, append the calculated CRC, then append the tail bits as shown in 32.3.8.7.
This results in 24 uncoded bits.
b) BCC encoder: Encode the data by a convolutional encoder at the rate of R=1/2 as described in
17.3.5.6.
c) BCC interleaver: Interleave as described in 17.3.5.7.
d) Constellation Mapper: BPSK modulate the 48 interleaved bits as described in 17.3.5.8 to form the
NGV-SIG symbol.
e) Pilot insertion: Insert pilots as described in 17.3.5.9.
f) Duplication and phase rotation: Duplicate NGV-SIG over each 10 MHz of the CH_BANDWIDTH.
Apply appropriate phase rotation for each 10 MHz subchannel as described in 32.3.7.3 and 32.3.7.4.
g) IDFT: Compute the inverse discrete Fourier transform.
h) CSD: Apply CSD for each transmit chain as described in 32.3.8.2.1.
i) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
j) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

Construct the RNGV-SIG field as the repeat NGV-SIG field defined in 32.3.8.8 with the same process as for
the NGV-SIG field.

32.3.4.6 Construction of NGV-STF

The NGV-STF field is defined in 32.3.8.9 and is constructed as follows:

a) Sequence generation: Generate the NGV-STF in the frequency domain over the bandwidth indicated
by CH_BANDWIDTH as described in 32.3.8.9.
b) Phase rotation: Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
c) CSD: Apply CSD for each spatial stream as described in 32.3.8.2.2.
d) Spatial mapping: Apply the Q matrix as described in 32.3.9.8.1.
e) IDFT: Compute the inverse discrete Fourier transform.
f) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
g) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

84
Copyright © 2023 IEEE. All rights reserved.

32.3.4.7 Construction of NGV-LTF

The NGV-LTF field is defined in 32.3.8.10 and constructed as follows:

a) Sequence generation: Generate the NGV-LTF sequence in the frequency domain over the
CH_BANDWIDTH as described in 32.3.8.10.
b) Phase rotation: Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
c) ANGV-LTF matrix mapping: Apply the PNGV-LTF matrix to the data tones of the NGV-LTF sequence
and apply the RNGV-LTF matrix to the pilot tones as described in 32.3.8.10.
d) CSD: Apply CSD for each spatial stream as described in 32.3.8.2.2.
e) Spatial mapping: Apply the Q matrix as described in 32.3.9.8.1.
f) IDFT: Compute the inverse discrete Fourier transform.
g) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
h) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

32.3.4.8 Construction of the Data field in an NGV PPDU

The construction of the Data field in an NGV PPDU proceeds as follows:

a) Construct the SERVICE field as described in 32.3.9.2 and append the PSDU to the SERVICE field.
b) PHY padding: Append the PHY pad bits to the PSDU. There are no tail bits.
c) Scrambler: Scramble the PHY padded data.
d) LDPC encoder: The scrambled bits are encoded using the LDPC code with the APEP_LENGTH in
the TXVECTOR as described in 32.3.9.4.
e) Stream parser: The output of the LDPC encoder is rearranged into blocks as described in 32.3.9.5.
f) Phase rotation: Apply appropriate phase rotation for each 10 MHz subchannel as described in
32.3.7.3 and 32.3.7.4.
g) CSD: Apply CSD for each spatial stream as described in 32.3.8.2.2.
h) Spatial mapping: Apply the Q matrix as described in 32.3.9.8.1.
i) IDFT: Compute the inverse discrete Fourier transform.
j) Insert GI and apply windowing: Prepend a GI and apply windowing as described in 32.3.7.3.
k) Analog and RF: Upconvert the resulting complex baseband waveform associated with each transmit
chain to an RF signal according to the center frequency of the desired channel and transmit. Refer to
32.3.7.3 and 32.3.8 for details.

32.3.5 NGV modulation and coding schemes

The NGV-MCS is a value that determines the modulation and coding used in the Data field of the PPDU. It
is a compact representation that is carried in the NGV-SIG field and RNGV-SIG field for NGV PPDUs.
Rate dependent parameters for the full set of NGV-MCSs are shown in Table 32-21 to Table 32-24. These
tables give rate-dependent parameters for NGV-MCSs with indices n, where n = 0, ..., 15, with number of
spatial streams from 1 to 2 and bandwidth options of 10 MHz and 20 MHz. Equal modulation is applied to
all streams.

The use of BPSK-DCM on the Data field of an NGV PPDU is indicated as NGV-MCS 15 in NGV-SIG
field.

85
Copyright © 2023 IEEE. All rights reserved.

32.3.6 Timing related parameters

Table 32-6 defines the timing related parameters.

Table 32-6—Timing related constants

Parameter CBW10 CBW20 Description

NSD 52 108 Number of data subcarriers

NSP 4 6 Number of pilot subcarriers

NST 56 114 Total number of subcarriers

See NOTE
NSR 28 58 Highest data subcarrier index

F 156.25 kHz Subcarrier frequency spacing

TDFT 6.4 µs IDFT/DFT period

TGI 1.6 µs = TDFT/4 Guard interval duration

TGI2 3.2 µs Double guard interval

TSYM 8 µs = TDFT + TGI = 1.25×TDFT Symbol interval

TL-STF 16 µs = 10 × TDFT/4 Non-HT Short Training field duration

TL-LTF 16 µs = 2 × TDFT + TGI2 Non-HT Long Training field duration

TL-SIG 8 µs Non-HT SIGNAL field duration

TRL-SIG 8 µs Repeated Non-HT SIGNAL field duration

TNGV-SIG 8 µs NGV SIGNAL field duration

TRNGV-SIG 8 µs Repeated NGV SIGNAL field duration

TNGV-STF 8 µs NGV Short Training field duration

TNGV-LTF-2X 8 µs Duration of each NGV-LTF-2x symbol

TNGV-LTF-1X 4.8 µs Duration of each NGV-LTF-1x symbol

TNGV-LTF-2X-Repeat 14.4 µs Duration of each repeated NGV-LTF-2x
symbol

TNGV-LTF TNGV-LTF-2X , TNGV-LTF-1X or Duration of each OFDM symbol in NGV-LTF

TNGV-LTF-2X-Repeat depending field
on the LTF format used
Nservice 16 Number of bits in the SERVICE field

Ntail 6 Number of tail bits per BCC encoder

NOTE —NST = NSD + NSP

86
Copyright © 2023 IEEE. All rights reserved.

Table 32-7 defines parameters used frequently in Clause 32.

Table 32-7—Frequently used parameters

Symbol Explanation

N CBPS Number of coded bits per symbol

N CBPSS Number of coded bits per symbol per spatial stream

N DBPS Number of data bits per symbol

N BPSCS Number of coded bits per subcarrier per spatial stream

N RX Number of receive chains

N SS Number of spatial streams
N TX Number of transmit chains
N NGV-LTF Number of NGV-LTF symbols
R R is the coding rate

32.3.7 Mathematical description of signals

32.3.7.1 Notation

For a description of the conventions used for the mathematical description of the signals, see 17.3.2.5, and
21.3.7.1.

32.3.7.2 Subcarrier indices in use

For a 10 MHz non-NGV PPDU, the signal is transmitted on subcarriers –26 to –1 and 1 to 26, with 0 being
the center (DC) subcarrier. See 17.3.2.6.

For a 10 MHz NGV PPDU transmission, the 10 MHz is divided into 64 subcarriers. The signal is
transmitted on subcarriers –28 to –1 and 1 to 28, with 0 being the center (DC) subcarrier.

For a 20 MHz NGV PPDU transmission, the 20 MHz is divided into 128 subcarriers. The signal is
transmitted on subcarriers –58 to –2 and 2 to 58.

32.3.7.3 Transmitted signal

The transmitted signal is described in complex baseband signal notation. The actual transmitted signal is
related to the complex baseband signal by the relation shown in Equation (32-1).

i i
= Re  r PPDU (t) exp (j2f c t)  i TX = 1  N TX
TX TX
r RF (32-1)

where
iTX
r PPDU (t) represents the complex baseband signal of transmit chain iTX
fc represents the center frequency of the PPDU

87
Copyright © 2023 IEEE. All rights reserved.

The transmitted RF signal is derived by upconverting the complex baseband signal, which consists of
several fields. The timing boundaries for the various fields are shown in Figure 32-8, where NNGV-LTF is the
number of NGV-LTF symbols as defined in Table 32-11.

Non‐NGV portion NGV portion
Pre‐NGV modulated fields NGV modulated fields

NGV‐LTF Data

NGV‐ RNGV‐ NGV‐ NGV‐LTF Data Data Data

L‐STF L‐LTF L‐SIG RL‐SIG ….. Midamble …..
SIG SIG STF Symbols Symbol Symbol Symbol

NNGV‐LT F M NNGV‐LT F

NSYM +NMA∙NNGV‐LT F
t = 0 tL‐LT F tL‐SIG tRL‐SIG tNGV‐SIG tRNGV‐SIG tNGV‐STF tNGV‐LT F tNGV‐Data

Figure 32-8—Timing boundaries for NGV PPDU fields

The time offset, t Field , determines the starting time of the corresponding field relative to the start of
L-STF (t = 0).

The signal transmitted on transmit chain i TX shall be as shown in Equation (32-2).

i i i
 t  = r L-STF  t  + r L-LTF  t – t L-LTF 
TX TX TX
r PPDU (32-2)
i TX i TX i TX
+ r L-SIG  t – t L-SIG  + r RL-SIG  t – t RL-SIG  + r NGV-SIG  t – t NGV-SIG 
i TX i TX i TX
+ r RNGV-SIG  t – t RNGV-SIG  + r NGV-STF  t – t NGV-STF  + r NGV-LTF t – t NGV-LTF 
i TX
+ r NGV-Data  t – t NGV-Data 

where

1  i TX  N TX

t L-LTF = T L-STF

t L-SIG = t L-LTF + T L-LTF

t RL-SIG = t L-SIG + T L-SIG

t NGV-SIG = t RL-SIG + T RL-SIG

t RNGV-SIG = t NGV-SIG + T NGV-SIG

t NGV-STF = t RNGV-SIG + T RNGV-SIG

t NGV-LTF = t NGV-STF + T NGV-STF

t NGV-Data = t NGV-LTF + N NGV-LTF  T NGV-LTF .

i
 t  , is defined as the summation of one or more subfields, where each subfield is defined to
TX
Each field, r Field
be an inverse discrete Fourier transform as specified in Equation (32-3).

88
Copyright © 2023 IEEE. All rights reserved.

N SR N SS
i TX 1 m
r Subfield (t) = -------------------------------------- w TSubfield(t) Field    Q k  i ,m  k ,BW X k exp  j2k F  t (32-3)
Tone TX
N Field  N Norm k = – N SR m = 1

– T GI ,Field – T CS ,NGV  m   

This general representation holds for all subfields. The total power of the time domain NGV modulated field
signals summed over all transmit chains should not exceed the total power of the time domain pre-NGV
modulated field signals summed over all transmit chains. For notational simplicity, the parameter BW is
omitted from some bandwidth dependent terms.

In Equation (32-3), the following notations are used:

Tone Tone
N Field Table 32-8 summarizes the various values of N Field as a function of bandwidth.
NNorm For pre-NGV modulated fields, NNorm = NTX. For NGV modulated fields NNorm = NSS,
where NSS is given in Table 32-7.
w TSubfield  t  is a windowing function. An example function, w TSubfield  t  , is given in 17.3.2.5.
T Subfield is T L-STF for L-STF, T L-LTF for L-LTF, T L-SIG for L-SIG, T RL-SIG for RL-SIG,
T NGV-SIG for NGV-SIG, T RNGV-SIG for RNGV-SIG, T NGV-STF for NGV-STF, T NGV-LTF for
NGV-LTF symbol and midamble symbol, and T SYM for Data symbol.
Qk is the spatial mapping matrix for the subcarrier k. For pre-NGV modulated fields, Q k is a
i
TX
F CS – j2k T i
column vector with NTX elements with element iTX being e , where T CSTX
represents the cyclic shift for transmitter chain i TX whose values are given in Table 21-10.
For NGV modulated fields, Q k is a matrix with NTX rows and NSS columns as further
described in 32.3.9.8.1.
 k BW is defined in 32.3.7.4.
F is the subcarrier frequency spacing given in Table 32-6.
m m
Xk is the frequency domain symbol in subcarrier k of spatial stream m. Some of the X k within
– N SR  k  N SR have a value of 0. Examples of such cases include the DC tones, guard
tones on each side of the transmit spectrum, as well as the unmodulated tones of L-STF and
NGV-STF fields.
k m
NOTE—The multiplication matrices A NGV-LTF and P NGV-LTF are included in the calculation of X k for the NGV-LTF
field.

T GI ,Field is the guard interval duration used for each OFDM symbol in the field. For L-STF and
NGV-STF, T GI ,Field = T GI but it can be omitted from Equation (32-3) due to the periodic
property of L-STF and NGV-STF over every 1.6 µs. For the L-SIG, RL-SIG, NGV-SIG,
RNGV-SIG, NGV-LTF, and Data fields, T GI ,Field is defined in the “Guard interval
duration” column of Table 32-8.
T CS ,NGV  m  For pre-NGV modulated fields, T CS ,NGV  m  = 0 . For NGV modulated fields, T CS ,NGV  m 
represents the cyclic shift per spatial stream, whose value is given in 21.3.8.3.2, where the
row for NSTS,total = 1 corresponds to NSS = 1 and the row for NSTS,total = 2 corresponds to
NSS = 2.

89
Copyright © 2023 IEEE. All rights reserved.

 Field is the power scale factor of a given field within an OFDM symbol for NGV PPDU. For the
L-STF and L-LTF fields,  Field is 2 when NGV-MCS 0 or NGV-MCS 15 and one spatial
stream is used for data field in 10 MHz NGV PPDU; otherwise it is 1. For other fields of
NGV PPDU,  Field = 1 .

Table 32-8—Tone scaling factor and guard interval duration values for PHY fields

Tone
N Field
Field Guard interval duration
10 MHz 20 MHz

L-STF 12 24 —

L-LTF 52 104 TGI2

L-SIG 52 104 TGI
RL-SIG 52 104 TGI
NGV-SIG 52 104 TGI
RNGV-SIG 52 104 TGI
NGV-STF 12 24 —

NGV-LTF-1x 28 58 TGI
NGV-LTF-2x 56 114 TGI
NGV-LTF-2x-Repeat 56 114 TGI
Data 56 114 TGI
NON_NGV_10_DUP — 104 TGI
_OFDM-Data

32.3.7.4 Definition of tone rotation

The function  k BW is used to represent a rotation of the tones. The value of BW in  k BW is determined by
the TXVECTOR parameter CH_BANDWIDTH as defined in Table 32-9.

Table 32-9—CH_BANDWIDTH

CH_BANDWIDTH  k BW

CBW10  k 10
CBW20  k 20

For a 10 MHz NGV PPDU transmission:

 k 10 = 1 (32-4)

90
Copyright © 2023 IEEE. All rights reserved.

For a 20 MHz NGV PPDU transmission:

 1 k  0
 k 20 =  (32-5)
 j k  0

32.3.8 NGV preamble

32.3.8.1 Introduction

An NGV preamble is defined to carry the required information to operate in a system with multiple transmit
and multiple receive antennas. To maintain compatibility with non-NGV STAs, specific non-NGV fields are
defined that can be received by non-NGV STAs compliant with Clause 17. The non-NGV fields are
followed by NGV fields specific to NGV STAs.

32.3.8.2 Cyclic shift

32.3.8.2.1 Cyclic shift for pre-NGV modulated fields

i TX
The cyclic shift value N CS for the L-STF, L-LTF, L-SIG, RL-SIG, NGV-SIG, and RNGV-SIG fields of the
PPDU for transmit chain i TX out of a total of N TX are defined in Table 21-10.

32.3.8.2.2 Cyclic shift for NGV modulated fields

The cyclic shift values defined in this subclause apply to the NGV-STF, NGV-LTF, and Data fields of the
NGV PPDU.

Throughout the NGV modulated fields of the preamble, cyclic shifts are applied to prevent unintended
beamforming when correlated signals are transmitted in multiple spatial streams. The same cyclic shift is
also applied to these streams during the transmission of the Data field of the NGV PPDU. The cyclic shift
value for the NGV modulated fields for spatial stream m out of N SS , the number of spatial streams, is shown
in Table 21-11 where the values in the row for N STS = m is used.

32.3.8.3 L-STF definition

The frequency domain sequence of the L-STF field for a 10 MHz or 20 MHz transmission is defined by
Equation (19-8) and Equation (19-9), respectively, in 19.3.9.3.3.

The time domain representation of the signal on transmit chain i TX shall be as specified in Equation (32-6).

91
Copyright © 2023 IEEE. All rights reserved.

N 10 MHz – 1 26
 i TX  1
r L-STF  t  = ------------------------------------ w T L-STF  t  L – STF
Tone
     k – Kshift  iBW   BW S k 10
N TX  N L-STF i BW = 0 k = – 26
(32-6)
i TX
 exp  j2  k – K shift  i BW   F  t – T CS   

where
 L – STF is the modulation dependent power scaling factor for the L-STF field with the following
value:
 when NGV-MCS 0 or NGV-MCS 15 and one spatial stream is
 2 used on Data field for 10 MHz transmission
 L – STF = 

 1 otherwise

 1 If CH_BANDWIDTH is CBW10
N 10 MHz = 
 2 If CH_BANDWIDTH is CBW20

K shift  i  =  N 10 MHz – 1 – 2i   32
i 
T CSTX represents the cyclic shift for transmit chain i TX with a value given in 32.3.8.2.1
 k BW is defined in Equation (32-4) and Equation (32-5)
Tone
N L-STF has the value given in Table 32-8
S k 10 is defined as S –26 26 in Equation (19-8)

32.3.8.4 L-LTF definition

For a 10 MHz or 20 MHz transmission, the L-LTF pattern in the NGV preamble is defined by
Equation (19-11) and Equation (19-12) in 19.3.9.3.4, respectively.

The time domain representation of the signal on transmit chain i TX shall be as defined in
Equation (32-7).

N 10 MHz – 1 26
 i TX  1
r L-LTF  t  = -----------------------------------
Tone
- w T L-LTF  t  L – LTF      k – K shift  iBW   BW L k 10
N TX  N L-LTF i BW = 0 k = – 26 (32-7)
i
 exp  j2  k – K shift  i BW   F  t – T CS
TX


where
 L – LTF is a modulation dependent scaling factor for the L-LTF field with the same value as
 L – STF
i 
T CSTX represents the cyclic shift for transmit chain i TX with a value given in 32.3.8.2.1
 k BW is defined in Equation (32-4) and Equation (32-5)
Tone
N L-LTF has the value given in Table 32-8
N 10 MHz is defined in 32.3.8.3

92
Copyright © 2023 IEEE. All rights reserved.

K shift  i  =  N 10 MHz – 1 – 2i   32
L k 10 is defined as L – 26 26 in Equation (19-11)

32.3.8.5 L-SIG definition

The L-SIG field is used to communicate rate and length information. The structure of the L-SIG field is
defined in Figure 17-5.

In an NGV PPDU, the RATE field shall be set to the value representing 3 Mb/s in the 10 MHz channel
spacing column of Table 17-6. In a non-NGV duplicate PPDU, the RATE field is defined in 17.3.4.2 using
the L_DATARATE parameter in the TXVECTOR.

The Length field shall be set to the value given by Equation (32-8).

TXTIME – 40
Length = ----------------------------------  3 – 3 (32-8)
8

where
TXTIME (in µs) is defined in 32.4.3.

The LSB of the binary expression of the value of the Length field shall be mapped to B5. In a non-NGV
duplicate PPDU, the LENGTH field is defined in 17.3.4.3 using the L_LENGTH parameter in the
TXVECTOR.

The Reserved (R) field shall be set to 0.

The Parity (P) field has the even parity of bits 0–16.

The SIGNAL TAIL field shall be set to 0.

The L-SIG field shall be encoded, interleaved, and mapped following the steps described in 17.3.5.6,
17.3.5.7, and 17.3.5.8. The stream of 48 complex numbers generated by these steps is denoted
by d k k = 0  47 and are mapped to subcarriers [–26, 26]. Pilots shall be inserted as described in
17.3.5.9.

The time domain waveform of the L-SIG field shall be as given by Equation (32-9).

N 10 MHz – 1 26
 i TX  1
r L-SIG  t  = ----------------------------------
Tone
- w T L-SIG  t      k – Kshift  iBW   BW  D k 10 + p 0 P k 
N TX  N L-SIG i BW = 0 k = – 26 (32-9)
i TX
 exp  j2  k – K shift  i BW   F  t – T GI – T CS 

where
N 10 MHz is defined in 32.3.8.3
K shift  i  =  N 10 MHz – 1 – 2i   32

93
Copyright © 2023 IEEE. All rights reserved.


 0 k = 0  7  21
D k 10 = 
 d Mr10  k  otherwise



 k + 26 – 26  k  – 22

 k + 25 – 20  k  – 8
r  k + 24 –6  k  –1
M 10  k  =  (32-10)
 k + 23 1k6

 k + 22 8  k  20
 k + 21 22  k  26


Pk is defined in 17.3.5.10
p0 is the first pilot value in the sequence defined in 17.3.5.10
Tone
N L-SIG has the value given in Table 32-8
 k ,BW is defined in Equation (32-4) and Equation (32-5)
i
TX
T CS represents the cyclic shift for transmit chain i TX with a value given in 32.3.8.2.1
r
NOTE— M 10  k  is a “reverse” function of the M  k  defined in 17.3.5.10.

32.3.8.6 RL-SIG definition

The RL-SIG field is a repeat of the L-SIG field and is used to differentiate an NGV PPDU from a non-NGV
PPDU. RL-SIG field shall be modulated the same as L-SIG field.

The time domain waveform of the RL-SIG field shall be as given by Equation (32-11).

N 10 MHz – 1 26
 i TX  1
r RL-SIG  t  = -------------------------------------w TL-SIG  t 
Tone
    k – Kshift  iBW   BW  D k 10 + p 1 P k 
N TX  N RL-SIG i BW = 0 k = – 26
(32-11)
i TX
 exp  j2  k – K shift  i BW   F  t – T GI – T CS 

where
Tone
N RL-SIG has the value given in Table 32-8.
p1 is the second pilot value in the sequence defined in 17.3.5.10

32.3.8.7 NGV-SIG definition

The NGV-SIG field carries information required to interpret NGV PPDUs. The NGV-SIG field contains the
fields listed in Table 32-10.

The NGV-SIG field is composed of one OFDM symbol, containing 24 data bits, as shown in Table 32-10.
NGV-SIG is transmitted before RNGV-SIG. The NGV-SIG symbol shall be BCC encoded at rate, R = 1/2,
be interleaved, be mapped to a BPSK constellation, and have pilots inserted following the steps described in
17.3.5.6, 17.3.5.7, 17.3.5.8, and 17.3.5.9. The stream of 48 complex numbers generated by these steps
(before pilot insertion) is denoted by d k k = 0 , ,47 .

94
Copyright © 2023 IEEE. All rights reserved.

Table 32-10—Fields in the NGV-SIG field

Bit Field Number of bits Description

B0–B1 PHY Version 2 Set to 0 for NGV PHY. Values 1–3 are reserved.

B2 Bandwidth 1 Set to 0 for 10 MHz, and set to 1 for 20 MHz.

B3–B6 NGV-MCS 4 For 10 MHz PPDU, set to n for NGV-MCS n,

where n = 0 1 2  8 , and 15. Value 9 is not
valid and values 10–14 are reserved.
For 20 MHz PPDU, set to n for NGV-MCS n,
where n = 0 1 2  9 , and 15. MCS 10–14
are reserved.

B7 N SS 1 Set to 0 for one spatial stream, and set to 1 for two

spatial streams.

B8–B9 Midamble Periodicity 2 Set to 0 for 4 symbols.

Set to 1 for 8 symbols.
Set to 2 for 16 symbols.
Value 3 is reserved.

B10 LTF Format 1 Set to 0 for NGV-LTF-2x.

Set to 1 for NGV-LTF-1x.

NOTE—If NGV-LTF-2x-Repeat is used (see

32.3.8.10) with B2 set to 0, B3–B6 set to 15 and
B7 set to 0, this field is reserved and set to 1.

B11 LDPC Extra OFDM 1 Set to 1 if the LPDC PPDU encoding process
Symbol results in an extra OFDM symbol as described in
21.3.10.5.4.
Set to 0 otherwise.

B12 LTF Repetition 1 Set to 1 for NGV ranging NDP with NGV-LTF
repetition.
Set to 0 otherwise.

B13 Reserved 1 Reserved and set to 1.

B14–B17 CRC 4 CRC is calculated as in 27.3.11.7.3 with

L = 13 .
B18–B23 Tail 6 Used to terminate the trellis of the convolutional
decoder.
Set to 0.

The time domain waveform for the NGV-SIG field in an NGV PPDU shall be as specified in
Equation (32-12).

N 10 MHz – 1 26
 i TX  1
r NGV-SIG  t  = -----------------------------------------
Tone
- w T NGV-SIG  t      k – K shift  iBW   BW  D k 10 + p 2 P k 
N TX  N NGV-SIG i BW = 0 k = – 26 (32-12)
i
 exp  j2  k – K shift  i BW   F  t – T GI – T CS 
TX

95
Copyright © 2023 IEEE. All rights reserved.

where

N 10 MHz and K shift  i  are defined in 32.3.8.5


 0 k = 0  7  21
D k ,10 = 
 d M r10  k  otherwise

r
M 10  k  is defined in Equation (32-10)
P k and p 2 are defined in 17.3.5.10
Tone
N NGV-SIG has the value given in Table 32-8
 k ,BW is defined in Equation (32-4) and Equation (32-5)
i
TX
T CS represents the cyclic shift for transmit chain i TX with a value given in 32.3.8.2.1

NOTE—In NGV PPDUs, the NGV-SIG is transmitted with the same number of subcarriers and the same cyclic shifts as
the preceding non-NGV portion of the preamble.

32.3.8.8 RNGV-SIG definition

The RNGV-SIG field is a repeat of the NGV-SIG field and is configured identically to the NGV-SIG.

The time domain waveform of the RNGV-SIG field shall be as given by Equation (32-13).

N 10 MHz – 1 26
 i TX  1
r RNGV-SIG  t  = --------------------------------------------
Tone
- w T RNGV-SIG  t      k – Kshift  iBW   BW  D k 10 + p 3 P k  (32-13)
N TX  N RNGV-SIG i BW = 0 k = – 26

i
 exp  j2  k – K shift  i BW   F  t – T GI – T CS
TX


where

Tone
N RNGV-SIG has the value given in Table 32-8
p3 is the fourth pilot value in the sequence defined in 17.3.5.10

32.3.8.9 NGV-STF definition

The main purpose of the NGV-STF field is to improve automatic gain control estimation in a MIMO
transmission. The duration of the NGV-STF field is 8 µs. The frequency domain sequence used to construct
the NGV-STF field in a 10 MHz transmission is identical to the VHT-STF field for 20 MHz transmission. In
a 20 MHz transmission, the NGV-STF field is constructed by using the frequency domain sequence for the
VHT-STF field of 40 MHz transmission and applying appropriate phase rotations per 10 MHz subchannel.

For a 10 MHz transmission, the frequency domain sequence is given by Equation (32-14).

NGVS – 28,28 = VHTS – 28,28 (32-14)

where VHTS – 28,28 is defined in Equation (21-29).

96
Copyright © 2023 IEEE. All rights reserved.

For a 20 MHz transmission, the frequency domain sequence is given by Equation (32-15).

NGVS – 58,58 = VHTS – 58,58 (32-15)

where VHTS – 58,58 is defined in Equation (21-30).

NOTE—Equation (32-14) and Equation (32-15) do not show the phase rotation per 10 MHz subchannel.

The time domain representation of the signal on transmit chain i TX shall be as specified in Equation (32-16).

N SR N SS
 i TX  1
r NGV-STF  t  = ------------------------------------------ w T NGV-STF  t     Q k  i ,m  k BW NGVS k
Tone TX (32-16)
N SS  N NGV-STF k = – N SR m = 1

 exp  j2k F  t – T CS ,NGV  m   

where

Tone
N NGV-STF has the value given in Table 32-8

T CS ,NGV  m  is given in 32.3.8.2.2

Qk is defined in 32.3.7.3

 k ,BW is defined in defined in Equation (32-4) and Equation (32-5)

32.3.8.10 NGV-LTF definition

The NGV-LTF field provides means for the receiver to estimate the MIMO channel between the set of
constellation mapper outputs and the receive chains. The transmitter provides training for NSS spatial
streams (spatial mapper inputs) used for the transmission of the PSDU(s). For each tone, the MIMO channel
that can be estimated is an NRX  NSS matrix. An NGV transmission has a preamble that contains NGV-LTF
symbols, where the data tones of each NGV-LTF symbol are multiplied by entries belonging to a matrix
PNGV-LTF, to enable channel estimation at the receiver. The pilot tones of each NGV-LTF symbol are
multiplied by the entries of a matrix RNGV-LTF defined in the following text. The multiplication of the pilot
tones in the NGV-LTF symbol by the RNGV-LTF matrix instead of the PNGV-LTF matrix allows receivers to
track phase and frequency offset during MIMO channel estimation using the NGV-LTF. The number of
NGV-LTF symbols, NNGV-LTF, is a function of the number of spatial streams, NSS, as shown in Table 32-11
and LTF_REP as shown in 32.3.16. As a result the NGV-LTF field consists of one, two, or four symbols.

Table 32-11—Number of NGV-LTFs required for different numbers of spatial streams

N SS N NGV-LTF

1 1  (LTF_REP + 1)

2 2  (LTF_REP + 1)

97
Copyright © 2023 IEEE. All rights reserved.

An NGV PPDU supports three NGV-LTF formats: NGV-LTF-1x, NGV-LTF-2x, and

NGV-LTF-2x-Repeat. NGV-LTF-2x is the default LTF format; NGV-LTF-1x is used for high efficiency
transmission of one spatial stream and NGV-LTF-2x-Repeat is used for extended range transmissions. A
transmitter shall use the NGV-LTF-2x-Repeat format if and only if the NGV Data field of a 10 MHz NGV
PPDU is modulated with BPSK-DCM and one spatial stream; the transmitter shall use the NGV-LTF-2x if
the NGV Data field is modulated with two spatial streams; the transmitter shall use the NGV-LTF-2x for
NGV ranging NDP; otherwise, the transmitter can choose either NGV-LTF-2x or NGV-LTF-1x. The
NGV-LTF format of NGV-LTF-1x or NGV-LTF-2x is signaled by B10 in NGV-SIG field. The
NGV-LTF-2x-Repeat format is signaled by the combination of B2 set to 0, B3–B6 set to 15 and B7 set to 0
in NGV-SIG field, and B10 is Reserved and set to 1. The duration of each NGV-LTF symbol is TNGV-LTF,
defined in Equation (32-17).

 T NGV-LTF-1X if NGV-LTF-1x

T NGV-LTF =  T NGV-LTF-2X , if NGV-LTF-2x (32-17)

 T NGV-LTF-2X-Repeat , if NGV-LTF-2x-Repeat

Let LTFleft and LTFright be the sequences defined in Equation (32-18) and Equation (32-19), respectively.

LTF left =  1 1 – 1 – 1 1 1 – 1 1 – 1 1 1 1 1 1 1 – 1 – 1 1 1 – 1 1 – 1 1 1 1 1  (32-18)

LTF right =  1 – 1 – 1 1 1 – 1 1 – 1 1 – 1 – 1 – 1 – 1 – 1 1 1 – 1 – 1 1 – 1 1 – 1 1 1 1 1  (32-19)

NOTE 1— LTFleft is identical to the leftmost 26 elements of Equation (17-8), and LTFright is identical to the rightmost
26 elements of Equation (17-8).

In a 10 MHz transmission, the NGV-LTF-1x sequence transmitted is given by Equation (32-20).

NGV-LTF – 28,28 =  1 0 1 0 – 1 0 1 0 – 1 0 – 1 0 1 0 1 0 1 0 – 1 0 1 0 1 0 1 0 1 (32-20)

0 0 0 – 1 0 1 0 – 1 0 – 1 0 – 1 0 – 1 0 – 1 0 1 0 – 1 0 – 1 0 – 1 0 1 0 1 0 – 1 

In a 10 MHz transmission, the NGV-LTF-2x sequence transmitted is given by Equation (32-21).

NGV-LTF – 28,28 =  1 1 LTF left 0 LTF right – 1 – 1  (32-21)

= VHT-LTF – 28,28

where

VHT-LTF –28,28 is defined in Equation (21-36).

In a 20 MHz transmission, the NGV-LTF-1x sequence transmitted is given by Equation (32-22).

NGV-LTF – 58,58 =  1 0 – 1 0 1 0 – 1 0 – 1 0 1 0 1 0 1 0 – 1 0 1 0 1 0 (32-22)

1 0 1 0 1 0 – 1 0 1 0 – 1 0 – 1 0 – 1 0 – 1 0 – 1 0 1 0 – 1 0 – 1 0 – 1 0
1  0 1 0 – 1  0  1  0  0  0  – 1  0 1  0  1  0  – 1  0  1  0  – 1  0  – 1  0  1  0  1  0  1  0 
– 1 0 1 0 1 0 1 0 1 0 1 0 – 1 0 1 0 – 1 0 – 1 0 – 1 0 – 1 0 – 1 0 1 0 – 1
0  – 1  0  – 1  0 1  0  1 

98
Copyright © 2023 IEEE. All rights reserved.

In a 20 MHz transmission, the NGV-LTF-2x sequence transmitted is given by Equation (32-23).

NGV-LTF – 58,58 =  LTF left 1 LTF right – 1 – 1 – 1 1 0 0 0 – 1 1 1 – 1 LTF left 1 LTF right  (32-23)
= VHT-LTF – 58,58

where

VHT-LTF –58,58 is defined in Equation (21-37).

NOTE 2—Equation (32-20), Equation (32-21), Equation (32-22), and Equation (32-23) do not show the phase rotation
per 10 MHz subchannel.

The generation of the time domain NGV-LTF symbols is shown in Figure 32-9.

𝑘
𝐴NGV-LTF 1, n

𝑁𝐺𝑉- LTF 𝑘
X IDFT

...
𝑘
...

...

CSD Q NGV-LTF 1: NSS

IDFT

𝑘
𝐴NGV-LTF NSS , n

Figure 32-9—Generation of NGV-LTF symbols

The generation of a time domain symbol of NGV-LTF-1x is equivalent to modulating every other tone in an
OFDM symbol of 6.4 μs excluding GI, and then only transmit the first half of the OFDM symbol in the time
domain, as shown in Figure 32-10.

Truncate ½ of Insert GI
Analog
IDFT time symbol and
and RF
Modulate every 2 tones

Window
Spatial Mapping

Truncate ½ of Insert GI
ANGV-LTF

IDFT Analog
time symbol and
and RF
Window
...

...

...
...

CSD per
SS Truncate ½ of Insert GI
IDFT Analog
time symbol and
and RF
Window

Figure 32-10—Generation of NGV-LTF-1x symbols

NGV-LTF-2x-Repeat is constructed by repeating the time domain symbol of NGV-LTF-2x excluding GI

and preappend one cyclic prefix of duration 1.6 µs. The generation of a time domain symbol of

99
Copyright © 2023 IEEE. All rights reserved.

NGV-LTF-2x-Repeat is equivalent to modulating every tone in an OFDM symbol of 6.4 μs excluding GI,
and then the OFDM symbol is repeated in the time domain, as shown in Figure 32-11.

Repetition of Insert GI
Analog
IDFT time symbol and
and RF
Window
Modulate every tones

Spatial Mapping
Repetition of Insert GI
ANGV-LTF

IDFT Analog
time symbol and
and RF
Window

...

...
...
CSD per Insert GI
Repetition of Analog
SS IDFT and
time symbol and RF
Window

Figure 32-11—Generation of NGV-LTF-2x-Repeat symbols

k
A NGV-LTF is given by Equation (32-24).

k  R NGV-LTF if k  K pilot
A NGV-LTF =  (32-24)
 P NGV-LTF otherwise

where

K pilot is the set of subcarrier indices for the pilot tones:

For a 10 MHz transmission, K pilot =   8 ,  22 
For a 20 MHz transmission, K pilot =   12 ,  26 ,  54 
R NGV-LTF is an N SS  N NGV-LTF matrix whose elements are defined in Equation (32-25) and
Equation (32-26)

 R NGV-LTF  m ,n =  P NGV-LTF  1 ,n , 1  n  N NGV-LTF 1  m  N SS (32-25)

P NGV-LTF =  P 2  2 P 2  2  (32-26)

where

P 2  2 = P 4  4  1:2   1:2  is a submatrix of P 4  4 with elements of the first two rows and two columns of
P 4  4 , which is defined in Equation (19-27)

The time domain representation of the waveform transmitted on transmit chain i TX shall be as described
by Equation (32-27).

100
Copyright © 2023 IEEE. All rights reserved.

N NGV-LTF – 1
 i TX  1
r NGV-LTF  t  = ------------------------------------------
Tone
 w TNGV-LTF  t – nT NGV-LTF 
N SS  N NGV-LTF n=0
N SR
N SS k
    Qk i
TX ,m
 k BW  A NGV-LTF  m , n + 1  NGV-LTF k (32-27)
k = – N SR m = 1

 exp  j2k F  t – nT NGV-LTF – T GI – T CS ,NGV  m   

where

Tone
N NGV-LTF has the value given in Table 32-8
T CS ,NGV  m  is given in 32.3.8.2.2
Qk is defined in 32.3.7.3
 k BW is defined in Equation (32-4) and Equation (32-5)
k
A NGV-LTF is defined in Equation (32-24)

32.3.9 Data field

32.3.9.1 General

The number of OFDM symbols in the Data field is determined by the Length field in L-SIG (see
Equation (32-8)), the preamble duration, and the setting of the NGV-LTF and Midamble field in NGV-SIG
(see 32.3.8).
For LDPC encoding, the Data field shall consist of the SERVICE field, the PSDU, and the PHY pad bits.
The padding flow is as follows. The MAC delivers a PSDU that fills the available octets in the Data field of
the PPDU. The PHY determines the number of pad bits to add and appends them to the PSDU. The number
of pad bits added always is 0 to 7. The PHY padding bits are calculated using Equation (32-28).

N PAD = N SYM ,init N DBPS – 8  PSDU_LENGTH – N service (32-28)

where
PSDU_LENGTH is defined in 32.4.3
N SYM ,init is given by Equation (21-62) with m STBC = 1

32.3.9.2 SERVICE field

The SERVICE field is as shown in Table 32-12.

Table 32-12—SERVICE field

Bits Field Description

B0–B6 Scrambler Initialization Set to 0

B7–B15 Reserved Set to 0

101
Copyright © 2023 IEEE. All rights reserved.

32.3.9.3 Scrambler

The SERVICE, PSDU, and PHY pad parts of the Data field shall be scrambled by the scrambler defined in
17.3.5.5. The Clause 17 TXVECTOR parameters CH_BANDWIDTH_IN_NON_HT and
DYN_BANDWIDTH_IN_NON_HT are not present; therefore, the initial state of the scrambler is set to a
pseudorandom nonzero seed.

32.3.9.4 Coding

The Data field of an NGV PPDU shall be encoded using LDPC coding. The LDPC code and encoding
process shall follow as described in 21.3.10.5.4 for a VHT SU PPDU with parameter mSTBC set to 1 and the
LDPC Extra Symbol field setting in NGV-SIG.

32.3.9.5 Stream parser

After coding and puncturing, the data bit streams at the output of the FEC encoder are processed in groups of
NCBPS bits. Each of these groups is rearranged into NSS blocks of NCBPSS bits. This operation is referred to
as stream parsing and is described in 21.3.10.6 for a SU transmission.

32.3.9.6 Constellation mapping

The mapping between bits at the output of the stream parser and complex constellation points for BPSK,
QPSK, 16-QAM, and 64-QAM follows the rules defined in 17.3.5.8 and 256-QAM follows the rules defined
in 21.3.10.9.

The streams of complex numbers out of constellation mapping are denoted as shown in Equation (32-29).

d k m n 0  k  N SD – 1 ; 1  m  N SS ; 0  n  N SYM – 1 (32-29)

For NGV data portion modulated with NGV-MCS 15, the input stream is broken into groups of N CBPS bits
 B 0 B 1  B NCBPS – 1 . Each bit B k is BPSK modulated to a sample d k . This generates the samples for the
lower half of the data subcarriers as d k 1 n = d k . For the upper half of the subcarriers, the samples are
j  k + N SD 
generated as d k + N  1 n = d k 1 n  e , with k = 0 1  N SD – 1 . The N SD here refers to the
SD

N SD for NGV-MCS 15, which is half the value of N SD for NGV-MCS 0.

32.3.9.7 Pilot subcarriers

In a 10 MHz transmission, four pilot tones shall be inserted in subcarriers k =  – 22 – 8 8 22  .

k
The pilot mapping P n for subcarrier k for symbol n shall be as specified in Equation (32-30).

 – 22 , – 8 , 8 , 22  1 1 1 1

Pn =   1 n mod 4   1  n + 1  mod 4   1  n + 2  mod 4   1  n + 3  mod 4 
(32-30)
k   – 22 , – 8 , 8 , 22 
Pn = 0

where
1
 1 m is given by the N STS = 1 row of Table 19-19

In a 20 MHz transmission, six pilot tones shall be inserted in subcarriers k =  – 54 – 26 – 12 12 26 54  .
k
The pilot mapping P n for subcarrier k for symbol n shall be as specified in Equation (32-31).

 – 54 , – 26 , – 12 , 12 , 26 , 54  1 1 1

Pn =   1 n mod 6   1  n + 1  mod 6    1  n + 5  mod 6 
(32-31)
k   – 54 , – 26 , – 12 , 12 , 26 , 54 
Pn = 0

where
1
 1 m is given by the N STS = 1 row of Table 19-20

The above pilot mapping shall be copied to all spatial streams before the spatial stream cyclic shifts are
applied.

The pilot subcarrier locations in the NGV-LTF field for NGV-LTF-1x, NGV-LTF-2x, and
NGV-LTF-2x-Repeat are the same as the pilot subcarrier locations in the Data field.

32.3.9.8 OFDM modulation

32.3.9.8.1 Transmission in NGV format

The time domain waveform of the Data field of an NGV PPDU from transmit chain i TX 1  i TX  N TX shall
be as defined in Equation (32-32) and Equation (32-33).

i  N SYM – 1
n- T  q r  iTX 
w TSYM  t – nT SYM – ----  n 
t = 
TX
r NGV-Data MA n NGV-Data ,n  t – ----- T MA +
 M M
n=0 (32-32)
N MA – 1
 i TX 
 p iMA r NGV-LTF  t –  i MA + 1 M  T SYM – i MA T MA 
i MA = 0

N N
 i TX  1 SR SS
 k
r NGV-Data ,n  t  = -----------------------------------------------    Qk i TX m
 k ,BW  D k m n BW + p n + 4 P n 
Tone
N NGV-Data N SS k = – NSR m = 1 (32-33)
 exp  j2k F  t – nT SYM – T GI Data – T CS NGV  m   


where
i  th
,n  t  is the n OFDM data symbol in the Data field, 0  n  N SYM – 1
TX
r NGV-Data
M is the midamble periodicity defined in 32.3.9.9
 i TX 
r NGV-LTF t is defined in Equation (32-27)
T MA = T NGV-LTF N NGV-LTF is the duration of one midamble
pn is defined in 17.3.5.10

 1 for n  M
qn =  p
– M-  for n  M
 n-------------
M

i MA is the index for the midambles, 0  i MA  N MA – 1

k
Pn is defined in 32.3.9.7
 k BW is defined in Equation (32-4) and Equation (32-5)

D k m n BW is the transmitted constellation at subcarrier k, spatial stream m, and Data

field OFDM symbol n and is defined in Equation (32-34) and
Equation (32-35)
Tone
N NGV-Data has the value given in Table 32-8

T CS NGV  n  is defined in Table 21-11

T GI Data is the guard interval duration. T GI Data = T GI

In a 10 MHz NGV PPDU transmission:

 0 k = 0  8  22
D k m n 10 =  (32-34)
 d M 10r (k) m n otherwise

where

 k + 28 – 28  k  – 23
 k + 27 – 21  k  – 9

r  k + 26 –7  k  –1
M 10 (k) = 
 k + 25 1k7
 k + 24 9  k  21

 k + 23 23  k  28

In a 20 MHz NGV PPDU transmission:

 0 k = 0  12  26  54
D k m n 20 =  (32-35)
 d M r20(k) m n otherwise

where

 k + 58 – 58  k  – 55
 k + 57 – 53  k  – 27

 k + 56 – 25  k  – 13

r  k + 55 – 11  k  – 2
M 20(k) = 
 k + 52 2  k  11
 k + 51 13  k  25

 k + 50 27  k  53

 k + 49 55  k  58

Qk is a spatial mapping/steering matrix with NTX rows and NSS columns for subcarrier k. Qk may be
frequency dependent. Refer to the examples of Qk listed in 19.3.11.11.2 for examples of Qk that could be
used for NGV PPDU.

NOTE—Implementations are not restricted to the spatial mapping matrix examples listed in 19.3.11.11.2 and the
number of transmit chains NTX could be more than one. The beamforming steering matrices are implementation specific.

32.3.9.9 Midambles

An NGV STA shall include midambles in an NGV PPDU transmission when the number of midamble
periods, NMA, is greater than zero in accordance with Equation (32-36). Midambles facilitate updating of the
channel estimate during the NGV PPDU reception.

Midambles are present in the Data field of the NGV PPDU every M OFDM symbols, where M is either 4, 8,
or 16 as indicated by the Midamble Periodicity field in the NGV-SIG field (see Table 32-10).

The Midamble field shall use the same format as the NGV-LTF field of the same PPDU, which format is
signalled in the NGV-SIG field. The generation of midamble is defined in 32.3.8.10.

The midambles and succeeding Data field OFDM symbols shall be randomized to prevent the generation of
spectral lines in the NGV PPDU spectrum. The nth midamble and M Data field OFDM symbols following
immediately after the nth midamble shall be multiplied by p n , n = 0  N MA – 1 , where p n is defined in
17.3.5.10. The midamble and the randomization procedure in an NGV PPDU are shown in Figure 32-12.
Identical to NGV‐LTF field
in the preamble

NGV‐LTF ... NGV‐LTF

M Data field symbols M Data field symbols M Data field symbols M Data field symbols

NGV preamble ... midamble ... midamble ... ... midamble ... ...

p0 p1 pn

Figure 32-12—NGV PPDU with midamble and randomization procedure

If present, the number of midamble periods, NMA, in a PPDU is calculated using Equation (32-36).

N SYM – 1
N MA = --------------------- (32-36)
M

where N SYM is the total number of data symbols in the Data field, is given in 21.3.10.5.4, and computed
using Equation (19-41) in step d) of 19.3.11.7.5.

As shown in Figure 32-12, the first midamble is inserted immediately after the Mth OFDM symbol in the
Data field, and a midamble is not inserted after the last data OFDM symbol if mod  N SYM , M  = 0 .

32.3.9.10 Non-NGV duplicate transmission

When the TXVECTOR parameter FORMAT is NON_NGV_10 and the TXVECTOR parameter
NON_NGV_MODULATION is NON_NGV_10_DUP_OFDM, the transmitted PPDU is a non-NGV
duplicate. Non-NGV duplicate transmission is used to transmit to STAs that support non-NGV OFDM and
may be present in a part of a 20 MHz channel (see Table 32-2). The RL-SIG, NGV-SIG, RNGV-SIG,
NGV-STF, and NGV-LTF fields are not transmitted. The L-STF, L-LTF, and L-SIG fields shall be
transmitted in the same way as in the NGV transmission, except that the L-SIG field’s Rate and Length
fields shall be as defined in 17.3.4. The Data field shall be as defined in Equation (32-37).

NOTE—For L-STF and L-LTF fields, the power scale factor is 1 in 20 MHz non-NGV duplicate PPDU.

N SYM – 1
 i TX  1
r Non-NGV-Data  t  = ----------------------------------------------------------------------------------------
Tone
 w TSYM  t – nT SYM  (32-37)
N TX N n=0
NON_NGV_10_DUP_OFDM-Data
26
i TX
   D k n + p n + 1 P k   exp(j2  k – 32  F  t – nT SYM – T GI – T CS  
k = – 26

i
+j  exp  j2  k + 32  F  t – nT SYM – T GI – T CS
TX


where
P k and pn are defined in 17.3.5.10

 0 k = 0  7  21
D k n =  (32-38)
 d M 10r (k) 1 n otherwise

r
M 10 (k) is defined in Equation (32-10)
i TX
T CS represents the cyclic shift of the transmit chain i TX and is defined in
32.3.8.2.1
Tone
N NON_NGV_10_DUP_OFDM-Data has the value given in Table 32-8

32.3.10 SU-MIMO

SU-MIMO is defined for an NGV transmitter to transmit two spatial streams to an NGV receiver to improve
throughput.

An NGV transmitter equipped with more than one antenna may use the SU-MIMO technique to transmit an
NGV PPDU with two spatial streams. The choice of number of spatial streams is described in 31.5.

The steering matrix Q k , defined in 32.3.7.3, used by the transmitter is implementation specific.
NOTE—The channel in the vehicular environment is fast-varying, so a SU-MIMO transmitter cannot obtain accurate
channel information through sounding. Therefore, there is no explicit sounding protocol defined for an NGV transmitter
to obtain the channel information prior to the transmission.

32.3.11 Transmit specification

32.3.11.1 Transmit spectrum mask

The transmit spectrum mask by regulatory domain is defined in Annex D and Annex E.

For any STA transmitting a 10 MHz NGV PPDU, the transmit spectrum mask is defined in 17.3.9.3.

For any STA using 20 MHz channel spacing and transmitting a 20 MHz NGV PPDU or 20 MHz non-NGV
duplicate PPDU, the transmitted spectral density shall have a 0 dBr bandwidth not exceeding 19 MHz and
shall not exceed the spectrum mask created using the permitted power spectral density levels listed in
Table 32-13.

The transmission of a 20 MHz NGV PPDU or 20 MHz non-NGV duplicate PPDU shall meet transmit
spectrum mask C2 regardless of the transmit power class to which the STA belongs.

NOTE 1—In the presence of additional regulatory restrictions, the device needs to meet both the regulatory
requirements and the mask defined in this subclause.
NOTE 2—For rules regarding TX center frequency leakage levels, see 32.3.11.4.2. The spectral mask requirements in
this subclause do not apply to the RF LO.

Table 32-13—Spectrum mask data for 20 MHz channel spacing

Permitted power spectral density, dBr

STA transmit
power class ± 9.5 MHz ± 10.0 MHz ± 10.5 MHz ± 15 MHz ± 25 MHz
offset offset offset offset offset
(±f1) (±f2) (±f3) (±f4) (±f5)

Any Class 0 –26 –32 –40 –50

32.3.11.2 Spectral flatness

Spectral flatness measurements shall be conducted using BPSK modulated PPDUs. Demodulate the PPDUs
according to the following (or equivalent) procedure:
a) Start of PPDU shall be detected.
b) Transition from L-STF to L-LTF shall be detected and fine timing shall be established.
c) Coarse and fine frequency offsets shall be estimated.
d) Symbols in a PPDU shall be derotated according to estimated frequency offset.
e) For each NGV-LTF symbol, transform the symbol into subcarrier received values, estimate the
phase from the pilot subcarriers, and derotate the subcarrier values according to the estimated phase.
f) For each of the data OFDM symbols: transform the symbol into subcarrier received values.

The spectral flatness test shall be performed over at least 20 PPDUs. The PPDUs under test shall be at least
16 data OFDM symbols long.

Evaluate spectral flatness using the subcarrier received values or the magnitude of the channel estimation.

Let E i ,avg denote the magnitude of the channel estimation on subcarrier i or the average constellation energy
of a BPSK modulated subcarrier i in an NGV data symbol.

For the spectral flatness test, the transmitting STA shall be configured to use a spatial mapping matrix Qk
(see 32.3.9.8) with flat frequency response. Each output port under test of the transmitting STA shall be
connected through a cable to one input port of the testing instrumentation. The requirements are defined in
Table 32-14 and apply to both 10 MHz and 20 MHz transmissions.

Table 32-14—Maximum transmit spectral flatness deviations

Bandwidth of Average subcarrier Tested subcarrier indices Maximum

Format
transmission (MHz) indices (inclusive) (inclusive) deviation (dB)

–16 to –1 and +1 to +16 ±4

10 –16 to –1 and +1 to +16
–28 to –17 and +17 to +28 +4/–6
NGV
–42 to –2 and +2 to +42 ±4
20 –42 to –2 and +2 to +42
–58 to –43 and +43 to +58 +4/–6

32.3.11.3 Transmit center frequency and symbol clock frequency tolerance

The symbol clock frequency and transmit center frequency tolerance shall be ±20 ppm maximum. The
transmit center frequency and the symbol clock frequency for all transmit antennas and frequency segments
shall be derived from the same reference oscillator.

32.3.11.4 Modulation accuracy

32.3.11.4.1 Introduction to modulation accuracy tests

Transmit modulation accuracy specifications are described in 32.3.11.4.2 and 32.3.11.4.3. The test method
is described in 32.3.11.4.4.

32.3.11.4.2 Transmitter center frequency leakage

TX LO leakage shall meet the following requirements for all bandwidths:

— When the RF LO is in the center of the transmitted PPDU BW, the power measured at the center of
transmission BW using resolution BW 156.25 kHz shall not exceed the average power per
subcarrier of the transmitted PPDU, or equivalently,  P – 10 log  N ST   , where P is the transmit
power per antenna in dBm, and NST is defined in Table 32-6.

— When the RF LO is not at the center of the transmitted PPDU BW, the power measured at the
location of the RF LO using resolution BW 156.25 kHz shall not exceed the maximum of –32 dB
relative to the total transmit power and –20 dBm, or equivalently max  P – 32 ,– 20  , where P is the
transmit power per antenna in dBm.

The transmit center frequency leakage is specified per antenna.

32.3.11.4.3 Transmitter constellation error

The relative constellation RMS error, calculated by first averaging over subcarriers, NGV PPDUs, and
spatial streams (see Equation (19-89)) shall not exceed a data-rate dependent value according to
Table 32-15. The number of spatial streams under test shall be equal to the number of utilized transmitting
STA antenna (output) ports and also equal to the number of utilized testing instrumentation input ports. In
the test, NSS = NSTS (no STBC) shall be used and no beamforming steering matrix shall be used. Each output
port of the transmitting STA shall be connected through a cable to one input port of the testing
instrumentation. The requirements apply to both 10 MHz and 20 MHz transmissions.

32.3.11.4.4 Transmitter modulation accuracy (EVM) test

The transmit modulation accuracy test shall be performed by instrumentation capable of converting the
transmitted signals into a stream of complex samples at a sampling rate greater than or equal to the
bandwidth of the signal being transmitted.

In this case, transmit modulation accuracy shall meet the required value in Table 32-15 using only the
subcarriers within the channel width.

Table 32-15—Allowed relative constellation error versus constellation size and coding rate

Relative constellation
Modulation Coding rate
error (dB)

BPSK-DCM 1/2 –5

BPSK 1/2 –5

QPSK 1/2 –10

QPSK 3/4 –13

16-QAM 1/2 –16

16-QAM 3/4 –19

64-QAM 2/3 –22

64-QAM 3/4 –25

64-QAM 5/6 –27

256-QAM 3/4 –30

256-QAM 5/6 –32

The instrument shall have sufficient accuracy in terms of I/Q arm amplitude and phase balance, DC offsets,
phase noise, and analog to digital quantization noise. A possible embodiment of such a setup is converting
the signals to a low IF frequency with a microwave synthesizer, sampling the signal with a digital
oscilloscope and decomposing it digitally into quadrature components. The sampled signal shall be
processed in a manner similar to an actual receiver, according to the following steps, or equivalent
procedure:
a) Start of PPDU shall be detected.
b) Transition from L-STF to L-LTF shall be detected and fine timing shall be established.
c) Coarse and fine frequency offsets shall be estimated.
d) Symbols in a PPDU shall be derotated according to estimated frequency offset.
e) For each NGV-LTF symbol, transform the symbol into subcarrier received values, estimate the
phase from the pilot subcarriers, and derotate the subcarrier values according to the estimated phase.
f) Estimate the complex channel response coefficient for each of the subcarriers and each of the
transmit streams. If midambles are present in the Data field of the PPDU, the channel response
coefficients shall be based upon the most recently received midamble symbols.
g) For each of the data OFDM symbols: transform the symbol into subcarrier received values, estimate
the phase from the pilot subcarriers, derotate the subcarrier values according to the estimated phase,
group the results from all of the receiver chains in each subcarrier to a vector, and multiply the
vector by a zero-forcing equalization matrix generated from the estimated channel.

h) For each data-carrying subcarrier in each spatial stream, find the closest constellation point and
compute the Euclidean distance from it. If midambles are present in the Data field of the PPDU, the
midamble symbols shall not be used to compute the Euclidean distance.
i) Compute the average across PPDUs of the RMS of all errors per PPDU as given by
Equation (19-89).

The test shall be performed over at least 20 PPDUs [Nf as defined in Equation (19-89)]. The PPDUs under
test shall be at least 16 data OFDM symbols long. Random data shall be used for the symbols.

32.3.11.4.5 Time of departure accuracy

The time of departure accuracy test evaluates TIME_OF_DEPARTURE against aTxPHYTxStartRMS and
aTxPHYTxStartRMS against TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH as defined in
Annex P with the following test parameters:
— MULTICHANNEL_SAMPLING_RATE is:
fH – fL 
10  10 6  1 + -------------------
- sample/s, for a CH_BANDWIDTH parameter equal to CBW10
 10 MHz 
fH – fL 
20  10 6  1 + -------------------
- sample/s, for a CH_BANDWIDTH parameter equal to CBW20
 10 MHz 
where
fH is the nominal center frequency in Hz of the highest channel in the channel set
fL is the nominal center frequency in Hz of the lowest channel in the channel set. The channel
set is the set of channels used for transmitting measurement frames, the channel set
comprises channels uniformly spaced across f H – f L  50 MHz .
— FIRST_TRANSITION_FIELD is L-STF.
— SECOND_TRANSITION_FIELD is L-LTF.
— TRAINING_FIELD is the long symbols windowed in a manner that should approximate the
windowing described in 17.3.2.5 with TTR = 100 ns for 20 MHz channel spacing, TTR = 200 ns for
10 MHz channel spacing.
— TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH is 80 ns.
NOTE—The indicated windowing applies to the time of departure accuracy test equipment, and not the transmitter or
receiver.

32.3.12 Receiver specification

32.3.12.1 General

For receiver minimum input sensitivity, adjacent channel rejection, nonadjacent channel rejection, receiver
maximum input level, and CCA sensitivity requirements described in this subclause, the input levels are
measured at the antenna connector and are referenced as the average power per receive antenna. The number
of spatial streams under test shall be equal to the number of utilized transmitting STA antenna (output) ports
and also equal to the number of utilized device under test input ports. Each output port of the transmitting
STA shall be connected through a cable to one input port of the device under test.

The requirements on receiver minimum input sensitivity in 32.3.12.2, adjacent channel rejection in
32.3.12.3, and nonadjacent channel rejection in 32.3.12.4 apply to NGV PPDUs. NGV-LTF-2x-Repeat
format is used if the NGV PPDUs are modulated with NGV-MCS 15 and NSS = 1 in 10 MHz, otherwise,
NGV-LTF-2x format is used.
NOTE—Similar receiver minimum input sensitivity requirements, adjacent channel rejection requirements, and
nonadjacent channel rejection requirements are defined for VHT PPDUs specified in 21.3.18.

32.3.12.2 Receiver minimum input sensitivity

The packet error ratio (PER) shall be less than 10% for a PSDU with the rate dependent input levels listed in
Table 32-16. The PSDU length shall be 2048 octets for BPSK-DCM or 4096 octets for all other
modulations.

Table 32-16—Receiver minimum input level sensitivity

Minimum sensitivity Minimum sensitivity

Modulation Rate (R) (10 MHz PPDU) (20 MHz PPDU)
(dBm) (dBm)

BPSK-DCM 1/2 –88 –82

BPSK 1/2 –85 –82

QPSK 1/2 –82 –79

QPSK 3/4 –80 –77

16-QAM 1/2 –77 –74

16-QAM 3/4 –73 –70

64-QAM 2/3 –69 –66

64-QAM 3/4 –68 –65

64-QAM 5/6 –67 –64

256-QAM 3/4 –62 –59

256-QAM 5/6 N/A –57

32.3.12.3 Adjacent channel rejection

Adjacent channel rejection for W MHz channels (where W is 10 or 20) shall be measured by setting the
desired signal’s strength 3 dB above the rate-dependent sensitivity specified in 32.3.12.2 and raising the
power of the interfering signal of W MHz bandwidth until 10% PER is caused for a PSDU length of 2048
octets for BPSK-DCM or 4096 octets for all other modulations. The difference in power between the signals
in the interfering channel and the desired channel is the corresponding adjacent channel rejection. The center
frequency of the adjacent channel shall be placed W MHz away from the center frequency of the desired
signal.

The interfering signal in the adjacent channel shall be a signal compliant with the NGV PHY,
unsynchronized with the signal in the channel under test, and shall have a minimum duty cycle of 50%. The
corresponding rejection shall be no less than specified in Table 32-17.

An optional enhanced performance specification is provided for systems requiring improved immunity to
out-of-channel interfering emissions. If a STA has dot11ACRType equal to 2, the adjacent channel rejection
shall be no less than specified in Table 32-18. The interfering signal in the adjacent channel shall be a signal
compliant with the NGV PHY, using class C transmit mask for 10 MHz channel and C2 transmit mask for
20 MHz channel (see D.2.2), unsynchronized with the signal in the channel under test. The corresponding
minimum receiver sensitivities for each modulation and coding rate are the same as in Table 32-16.

Table 32-17—Minimum required adjacent and nonadjacent channel rejection level

Adjacent channel rejection Nonadjacent channel rejection

Modulation Rate (R) (dB) (dB)
(10 MHz/20 MHz PPDU) (10 MHz/20 MHz PPDU)

BPSK-DCM 1/2 19 (10 MHz), 16 (20 MHz) 35 (10 MHz), 32 (20 MHz)

BPSK 1/2 16 32

QPSK 1/2 13 29

QPSK 3/4 11 27

16-QAM 1/2 8 24

16-QAM 3/4 4 20

64-QAM 2/3 0 16

64-QAM 3/4 –1 15

64-QAM 5/6 –2 14

256-QAM 3/4 –7 9

256-QAM 5/6 –9 7

NOTE—The values defined for 256-QAM with 5/6 coding rate only apply to 20 MHz channel.

Table 32-18—Optional enhanced minimum required adjacent and nonadjacent channel

rejection level

Adjacent channel rejection Nonadjacent channel rejection

Modulation Rate (R) (dB) (dB)
(10 MHz/20 MHz PPDU) (10 MHz/20 MHz PPDU)

BPSK-DCM 1/2 31 (10 MHz), 28 (20 MHz) 45 (10 MHz), 42 (20 MHz)

BPSK 1/2 28 42
QPSK 1/2 25 39

QPSK 3/4 23 37

16-QAM 1/2 20 34

16-QAM 3/4 16 30

64-QAM 2/3 12 26

64-QAM 3/4 11 25

64-QAM 5/6 10 24

256-QAM 3/4 5 19

256-QAM 5/6 3 17

NOTE—The values defined for 256-QAM with 5/6 coding rate only apply to 20 MHz channel.

32.3.12.4 Nonadjacent channel rejection

Nonadjacent channel rejection for W MHz channels (where W is 10 or 20) shall be measured by setting the
desired signal’s strength 3 dB above the rate-dependent sensitivity specified in Table 32-16, and raising the
power of the interfering signal of W MHz bandwidth until a 10% PER occurs for a PSDU length of 2048
octets for BPSK-DCM or 4096 octets for all other modulations. The difference in power between the signals
in the interfering channel and the desired channel is the corresponding nonadjacent channel rejection. The
nonadjacent channel rejection shall be met with any nonadjacent channels located at least 2 × W MHz away
from the center frequency of the desired signal.

The interfering signal in the nonadjacent channel shall be a signal compliant with the NGV PHY,
unsynchronized with the signal in the channel under test, and shall have a minimum duty cycle of 50%. The
corresponding rejection shall be no less than specified in Table 32-17.

An optional enhanced performance specification is provided for systems requiring improved immunity to
out-of-channel interfering emissions. If a STA has dot11ACRType equal to 2, the nonadjacent channel
rejection shall be no less than specified in Table 32-18. The interfering signal in the nonadjacent channel
shall be a signal compliant with the NGV PHY, using class C transmit mask for 10 MHz channel and C2
transmit mask for 20 MHz channel (see D.2.2), unsynchronized with the signal in the channel under test.
The corresponding minimum receiver sensitivities for each modulation and coding rate are the same as in
Table 32-16.

32.3.12.5 Receiver maximum input level

The receiver shall provide a maximum PER of 10% at a PSDU length of 2048 octets for BPSK-DCM or
4096 octets for all other modulations, for a maximum input level of –30 dBm, measured at each antenna
connector for any baseband NGV modulation.

32.3.12.6 CCA sensitivity

32.3.12.6.1 General

The thresholds in this subclause are compared with the signal level at each receiving antenna.

32.3.12.6.2 CCA sensitivity for signals occupying the primary 10 MHz channel

An NGV STA with a W MHz operating channel width shall detect, with > 90% probability, the start of a
PPDU that occupies at least the primary 10 MHz channel in an otherwise idle W MHz operating channel
width, and issue a PHY CCA.indication(BUSY, {primary}) primitive within a period of aCCATime
(see 17.4.4) if one of the following conditions is met:
— The start of a NON_NGV_10 PPDU as defined in 17.3.10.6.
— The start of a 20 MHz non-NGV duplicate or NGV PPDU for which the power measured within the
primary 10 MHz channel is above –85 dBm.

The CCA signal shall be held busy (PHY-CCA.indication(BUSY, {primary}) primitive) for the duration of
the PPDU.

The receiver shall issue a PHY-CCA.indication(BUSY, {primary}) primitive for any signal that exceeds a
threshold of –65 dBm in the primary 10 MHz channel within a period of aCCATime after the signal arrives
at the receiver’s antenna(s); then the receiver shall not issue a PHY-CCA.indication(BUSY, {secondary}),
or PHYCCA.indication(IDLE) primitive while the threshold continues to be exceeded.

32.3.12.6.3 CCA sensitivity for signals not occupying the primary 10 MHz channel

The PHY shall issue a PHY-CCA.indication(BUSY, {secondary}) primitive if the conditions for issuing a
PHY-CCA.indication(BUSY, {primary}) primitive are not present and one of the following conditions are
present in an otherwise idle 20 MHz operating channel width:
— Any signal within the secondary 10 MHz channel at or above a threshold of –65 dBm within a
period of aCCATime after the signal arrives at the receiver’s antenna(s); then the PHY shall not
issue a PHY-CCA.indication(IDLE) primitive while the threshold continues to be exceeded.
— A 10 MHz NON_NGV, or NGV PPDU detected in the secondary 10 MHz channel at or above
–85 dBm with > 90% probability within a period aCCAMidTime (see 32.4.4).

32.3.13 NGV transmit procedure

There are two paths for the transmit PHY procedure:

— The first path, for which typical transmit procedures are shown in Figure 32-13, is selected if the
FORMAT parameter of the PHY-TXSTART.request(TXVECTOR) primitive is NGV. These
transmit procedures do not describe the operation of optional features, such as SU-MIMO.
— The second path is selected if the FORMAT parameter of the
PHY-TXSTART.request(TXVECTOR) primitive is NON_NGV_10. Transmit parameter
N_PPDU_REP is set via the PHY service interface using the
PHY-TXSTART.request(TXVECTOR) primitive, as described in Table 32-1 to indicate the number
of repetitions of NON_NGV_10 PPDU transmission.
PHY-TXSTART.confirm

PHY-TXEND.request
PHY-TXSTART.request

PHY-Data.confirm

PHY-Data.confirm
PHY-Data.request

PHY-Data.request

PHY-TXEND.confirm
(TXVECTOR)

MAC

A-MPDU

NGV- PHY Padding if needed

L-SIG Service PSDU
SIG

Scrambling + Encoding for Data

Midambles if needed
PHY

NGV- RNGV NGV Training Data (Variable number of coded OFDM

L-STF L-LTF L-SIG RL-SIG
SIG -SIG Symbols symbols) and midambles
Coded Coded
OFDM OFDM
BPSK, BPSK,
Rate ½ Rate ½
Coded Coded
OFDM OFDM
BPSK, BPSK,
Rate ½ Rate ½

Figure 32-13—PHY transmit procedure for NGV transmission

In the second path, the transmission follows the transmit procedure in Clause 17 except that the signal
referred to in Clause 17 is instead generated with the Duration/ID field to report transmitter is an NGV STA
as defined in 31.2.1. If N_PPDU_REP is nonzero, the first NON_NGV_10 PPDU may be stored in the
memory, and the same PPDU is transmitted N_PPDU_REP times after the initial transmission, with each
repetition occurring after a SIFS following the previous NON_NGV_10 PPDU transmission.

In both paths, in order to transmit data, the MAC generates a PHY-TXSTART.request primitive, that causes
the PHY entity to enter the transmit state. Further, the PHY is set to operate at the appropriate frequency
through station management via PLME, as specified in 32.4. Other transmit parameters, such as NGV-MCS,
Coding types, and transmit power, are set via the PHY SAP using the
PHY-TXSTART.request(TXVECTOR) primitive, as described in Table 32-1. The remainder of the clause
applies to the first path.

Transmission of the PPDU shall be initiated by the PHY after receiving the
PHY-TXSTART.request(TXVECTOR) primitive. The TXVECTOR parameters for the
PHY-TXSTART.request primitive are specified in Table 32-1.

Transmission of the PHY preamble shall start immediately provided that

TIME_OF_DEPARTURE_REQUESTED is true, based on the parameters passed in the
PHY-TXSTART.request primitive.

After the PHY preamble transmission is started, the PHY entity immediately initiates data scrambling and
data encoding. The encoding method for the Data field is based on the CH_BANDWIDTH, NUM_SS, and
NGV-MCS parameters of the TXVECTOR, as described in 32.3.2.

The SERVICE field and PSDU are scrambled and encoded as described in 32.3.3. The data shall be
exchanged between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives
issued by the MAC, and PHY-DATA.confirm primitives issued by the PHY. PHY padding bits are
appended to the PSDU to make the number of bits in the coded SERVICE field and PSDU an integer
multiple of the number of coded bits per OFDM symbol. Midambles are inserted every M OFDM symbols if
present, where M is indicated by the Midamble Periodicity field in the NGV-SIG field.

Transmission can be prematurely terminated by the MAC through the PHY-TXEND.request primitive.
PSDU transmission is terminated by receiving a PHY-TXEND.request primitive. Each
PHY-TXEND.request primitive is acknowledged with a PHY-TXEND.confirm primitive from the PHY.
Normal termination occurs after the transmission of the final bit of the last PSDU octet, according to the
number of OFDM symbols indicated by NSYM (see 21.3.10.5.4).

In the PHY, the GI is inserted in every data OFDM symbol as a countermeasure against delay spread.

When the PPDU transmission is completed the PHY entity enters the receive state.

A typical state machine implementation of the transmit PHY is provided in Figure 32-14. Request (.request)
and confirmation (.confirm) primitives are issued as shown. This state machine does not describe the
operation of optional features, such as SU-MIMO.

NOTE 1 —This state machine does not

describe the operation of optional features,
such as SU-MIMO.
NOTE 2 — otherwise is the condition that
PHY-TXSTART.request
TX PSDU OCTET buffer contains a lack of data to fill symbol
(TXVECTOR)
which is not last.

Get octet from MAC, PHY-DATA.request(DATA)

scramble, encode and
buffer

PHY-data.confirm
FORMAT = NON_NGV_10
Set TX parameters
Buffer contains a
symbol’s worth of

Refer to Clause 17
N_PPDU_REP > 0? data or last octet otherwise &&
received from MAC PHY-DATA.request(DATA)
FORMAT = NGV
Yes

Last Symbol?

TX L-STF set repetition counter: Yes

TX L-LTF r = N_PPDU_REP; No
TX L-SIG (BPSK) Store NON_NGV_10
PPDU.
PADDING

Add PHY
padding bits,
scramble, encode, and
buffer
TX RL-SIG (BPSK)
TX NGV-SIG (BPSK)
TX RNGV-SIG (BPSK) Decrease counter r = r – 1;
TX NGV Training Symbols

Yes TX Symbol
r > 0?
Set i = i + 1

Use NGV-MCS and number No

of spatial stream set by
TXVECTOR Switch RX state
16-bit service field Yes
prepended and TX Midamble except
padding appended to PSDU i is M? Last Symbol with
mod(NSYM, M) = 0
Set i = 0
No

Decrement Symbol

PHY-DATA.request(DATA) Decrement symbol

PHY-TXSTART.confirm Count Symbol count > 0
Set symbol count to NSYM
Set i = 0

Symbol Count = 0

Switch RX state
At any stage in the
A above flow diagram, if a A
PHYTXEND.request is
received.

Figure 32-14—PHY transmit state machine

32.3.14 NGV receive procedure

A typical PHY receive procedure is shown in Figure 32-15 for NGV format. A typical state machine
implementation of the receive PHY is given in Figure 32-16. This receive procedure and state machine do
not describe the operation of optional features, such as SU-MIMO. If the detected format indicates a
NON_NGV_10 PPDU:
— If combined detection of NON_NGV_10 PPDU with repetition is not considered, refer to the
receive procedure and state machine in Clause 17.
— Else the receiver checks whether the currently received PPDU is qualified as a repetition of
previously received NON_NGV_10 PPDU. The repetition may be determined by checking whether
the gap between the time of arrival of the currently detected PPDU and the ending time of the

previously received NON_NGV_10 PPDU is SIFS or not. Other repetition detection techniques may
be exploited to improve the detection reliability.
— If the current reception is not a repetition, refer to the receive procedure and state machine in
Clause 17 to decode the PPDU, and overwrite the memory with current PPDU for potential
combining with next repetition.
— Else, the receiver may combine the currently received PPDU with the previously stored
NON_NGV_10 PPDU and decode the combined PPDU according to the receive procedure
and state machine in Clause 17. Update the memory with combined PPDU for potential
reception of more repetitions.

Further, through station management (via the PLME) the PHY is set to the appropriate frequency, as
specified in 32.4. Receive parameters, such as RSSI and indicated DATARATE, may be accessed via the
PHY SAP.

CS/CCA state RX state

PHY-RXSTART.indication

PHY-RXEND.indication
(NoError, RXVECTOR)
PHY-DATA.indication
PHY-DATA.indication

PHY-DATA.indication

PHY-CCA.indication
PHY-CCA.indication
(BUSY, channel-list)

(RXVECTOR)
…………..…………

(IDLE)
MAC

A-MPDU

Decoding Delay NGV-

L-SIG PSDU
SIG Padding (if
present)
Decoded and
descrambled
Measure RSSI

Measure RCPI
Measure RSSI

PHY

NGV- RNGV NGV training Data (variable number of coded OFDM

L-STF L-LTF L-SIG RL-SIG
SIG -SIG symbols symbols) and midambles
Coded Coded
OFDM OFDM
BPSK, BPSK,
Rate ½ Rate ½
Coded Coded
OFDM OFDM
BPSK, BPSK,
Rate ½ Rate ½

Figure 32-15—PHY receive procedure for NGV transmission

Upon receiving the transmitted PHY preamble in a greater than or equal to 10 MHz channel, the PHY
measures a receive signal strength. This activity is indicated by the PHY to the MAC via a
PHY-CCA.indication primitive. A PHY-CCA.indication(BUSY, channel-list) primitive is also issued as an
initial indication of reception of a signal as specified in 32.3.12.6. The channel-list parameter of the
PHY-CCA.indication primitive is absent when the operating channel width is 10 MHz. The channel-list
parameter is present when the operating channel width is 20 MHz.

NOTE—This state machine does not describe the

RX IDLE state operation of optional features, such as SU-MIMO

CS/CCA

Set PHY_CCA.indication(BUSY,OCB primary) Repetition Check

Determine PPDU
repetition based on
packet arrival time.

Detect RL-SIG
End of Wait
RL-SIG detection
Rx and determine whether
Set PHY_CCA failed
1st and 2nd symbols after L- NON_NGV_10
indication() in Carrier lost: LTF are the same Repetition?
Non-NGV No
accordance Set
preamble
with 32.3.12.6 PHY_RXEND.indicat RL-SIG detected
(CCA ion(CarrierLost)
sensitivity) Parity or
RX L-SIG RATE
check
RX and combine L-SIG and RL-
failed Yes
SIG. Decode, test parity,
determine whether RATE is 3
Mb/s Rx Combining

Carrier lost: Combine received

Detect NGV-SIG PPDU with the
Set
PHY_RXEND.indication(CarrierLost) stored PPDU.
RX NGV-SIG
Refer to 17.3.12

RX Symbol

RX NGV-SIG
Carrier lost Valid signal
Invalid CRC: Set RX and combine NGV-SIG and
PHY_RXEND.indicat RNGV-SIG. Decode and test Signal Not Valid Decode Symbol
ion(FormatViolation) CRC
Decode and
Set RxEndStatus =
descramble
CRC OK (CarrierLost, Null)
symbol

N_symbol > 0
Evaluate NGV-SIG
Decrement Time Decrement N_symbol

Unsupported mode: Check contents in NGV- Wait for intended PHY_DATA.indication(DAT

Set SIG for supported mode end of PSDU based A)
PHY_RXSTART.indication( on RXTIME (bit removing if needed)
RXVECTOR) then set Supported mode Decrement symbol count
PHY_RXEND.indication Time = 0
(UnsupportedRate) N_symbol = 0
Reserved NGV-SIG Indication: End of PSDU RX
Set PHY Setup PSDU RX
RXEND.indication(FormatViolation) Set RxEndStatus =
Set N_symbols = NSYM,RX (NoError, RXVECTOR);
Set
PHY_RXSTART.indication
(RXVECTOR)
End of Wait
End of Wait

For unsupported modes, Carrier Set PHY_CCA.indication(IDLE)

Lost, Reserved NGV-SIG Indication,
NGV-SIG CRC failure: set
PHY_CCA.indication(IDLE) when
predicted duration based on RXTIME
defined in 32.3.14 (NGV receive
procedure) has elapsed

Figure 32-16—PHY receive state machine

The PHY shall not issue a PHY-RXSTART.indication primitive in response to a PPDU that does not
overlap the OCB primary 10 MHz channel.

The PHY includes the most recently measured RSSI value in the PHY-RXSTART.indication(RXVECTOR)
primitive issued to the MAC.

After the PHY-CCA.indication(BUSY, channel-list) primitive is issued, the PHY entity shall begin
receiving the training symbols and searching for the preambles for non-NGV and NGV PPDUs. For
detecting the NGV preamble, the PHY entity shall search for L-SIG and RL-SIG in order to set the
maximum duration of the data stream. If RL-SIG is detected, the PHY entity should check the parity bit and
RATE fields in L-SIG and RL-SIG. If RL-SIG detection fails, the check of the parity bit is invalid, or the
RATE field is not equal to 3 Mb/s, a PHY-RXSTART.indication primitive is not issued, and instead the
PHY should continue to detect the received signal using NON_NGV_10 Repetition check. If a valid parity
bit and the RATE with 3 Mb/s are indicated in L-SIG and RL-SIG, the NGV PHY shall maintain the
PHY-CCA.indication(BUSY, channel-list) primitive for the predicted duration of the transmitted PPDU, as
defined by RXTIME in Equation (32-41), for all supported modes, unsupported modes, Reserved NGV-SIG
Indication, and invalid SIG CRC. Reserved NGV-SIG Indication is defined as an NGV-SIG with the
Reserved bits equal to 0 or any other NGV-SIG field bit combinations that do not correspond to modes of
PHY operation defined in Clause 32. If the NGV-SIG indicates an unsupported mode, the PHY shall issue a
PHY-RXEND.indication(UnsupportedRate) primitive. If the NGV-SIG indicates an invalid CRC or
Reserved NGV-SIG indication, the PHY shall issue the error condition
PHY-RXEND.inidcation(FormatViolation).primitive.

After receiving a valid L-SIG, RL-SIG, NGV-SIG, and RNGV-SIG indicating a supported mode, the PHY
entity shall begin receiving the NGV training symbols.
The PHY entity shall check the PHY Version in the NGV-SIG field. If the PHY Version does not contain an
intended value with 0 for NGV PHY in Table 32-10, the PHY entity shall issue a
PHY-RXSTART.indication(RXVECTOR) and then issue a PHY-RXEND.indication(Filtered).
Following training fields, the Data field shall be received. The number of symbols in the Data field is
determined by Equation (32-39).

 NSYM RX , if LDPC Extra Symbol = 0

N SYM RX =  (32-39)
 NSYM RX – 1, if LDPC Extra Symbol = 1

where
LDPC Extra Symbol is a field in the NGV-SIG field (see Table 32-10).

NSYM ,RX =  -----------------------------------------------------

L_LENGTH + 3   8
- – T NGV-PREAMBLE – N MA RX  N NGV-LTF  T NGV-LTF  T SYM
 3 

where
L_LENGTH is the LENGTH field in L-SIG
T NGV-PREAMBLE = T RL-SIG + T NGV-SIG + T RNGV-SIG + T NGV-STF + N NGV-LTF  T NGV-LTF
T RL-SIG , T NGV-SIG , T RNGV-SIG , T NGV-STF , and T NGV-LTF , are defined in Table 32-6
N NGV-LTF is defined in Table 32-7
N MA RX may be computed by multiple methods that get the same results, an example method
is provided in Equation (32-40)

 L_LENGTH + 3   8
------------------------------------------------------ – T NGV-PREAMBLE – T SYM
N MA ,R X = 3 (32-40)
--------------------------------------------------------------------------------------------------------------------
N NGV-LTF  T NGV-LTF + M  T SYM

where M is the midamble periodicity as defined in Table 32-10.

If signal loss occurs during reception prior to completion of the PSDU reception, the error condition shall be
reported to the MAC using a PHY-RXEND.indication(CarrierLost) primitive. After waiting for the intended
end of the PSDU as determined by Equation (32-41), the PHY shall generate a PHY-CCA.indication(IDLE)
primitive and return to RX IDLE state.

RXTIME =  L_LENGTH + 3   8 + 40 (32-41)

--------------------------------------------
3

The received PSDU bits are assembled into octets, decoded, and presented to the MAC using a series of
PHY-DATA.indication(DATA) primitive exchanges. Any final bits that cannot be assembled into a
complete octet are considered pad bits and discarded. After the reception of the final bit of the last PSDU
octet, and possible padding, the receiver shall be returned to the RX IDLE state, as shown in Figure 32-16. A
PHY-RXEND.indication(NoError) primitive shall be issued on entry to the RX IDLE state.

32.3.15 Regulatory requirements

Wireless LANs (WLANs) implemented in accordance with this standard are subject to equipment
certification and operating requirements established by regional and national regulatory administrations. The
PHY specification establishes minimum technical requirements for interoperability, based upon established
regulations at the time this standard was issued. These regulations are subject to revision or may be
superseded. Requirements that are subject to local geographic regulations are annotated within the PHY
specification. Regulatory requirements that do not affect interoperability are not addressed in this standard.
Implementers are referred to the regulatory sources in Annex D for further information. Operation in
countries within defined regulatory domains might be subject to additional or alternative national
regulations.

32.3.16 NGV ranging NDP

The NGV ranging NDP is a variant of NGV PPDU but without the Data field. The format of an NGV
ranging NDP is shown in Figure 32-17.

16 µs 16 µs 8 µs 8 µs 8 µs 8 µs 8 µs NNGV‐LTF × TNGV‐LTF

RNGV‐
L‐STF L‐LTF L‐SIG RL‐SIG NGV‐SIG NGV‐STF NGV‐LTF symbols
SIG

Figure 32-17—NGV ranging NDP format

The NGV ranging NDP has the following properties:

— The TXVECTOR parameter NUM_SS is used to encode the NSS field of the NGV-SIG and
RNGV-SIG.
— The TXVECTOR parameter LTF_REP indicates the number of repetitions of the NGV-LTF
symbols.
— The TXVECTOR parameter NGV-MCS shall be set to 0.

In an NGV ranging NDP, the NGV-LTF symbol format shall be NGV-LTF-2x.

The number of NGV-LTF symbols in an NGV ranging NDP is the product of the TXVECTOR parameter
NUM_SS and (LTF_REP + 1), see Table 32-11. The number of LTF repetitions equals LTF_REP. When
LTF repetition is used, LTF_REP is 1. Otherwise, LTF_REP is 0.

The construction of the NGV-LTFs in an NGV ranging NDP is done by performing the steps in 32.3.4.7
LTF_REP + 1 times. An example of NGV_LTF with two spatial streams and one LTF repetition is shown in
Figure 32-18.

8 µs 8 µs 8 µs 8 µs 8 µs

... NGV‐LTF‐2x NGV‐LTF‐2x NGV‐LTF‐2x NGV‐LTF‐2x

NGV‐STF
symbol symbol symbol symbol

NSS NSS

NNGV‐LTF

Figure 32-18—Example of NGV-LTF with NSS = 2 and LTF_REP = 1

32.4 NGV PLME

32.4.1 PLME-SAP

Table 32-19 lists the MIB attributes that may be accessed by the PHY entities and the intralayer of higher
level LMEs. These attributes are accessed via the PLME-GET, PLME-SET, PLME-RESET, and
PLME-CHARACTERISTICS primitives defined in 6.5.

Table 32-19—NGV PHY MIB attributes

Operational
Managed object Default value/range
semantics

dot11PHYOperationTable

dot11PHYType ngv Static

dot11PHYTxPowerTable

dot11NumberSupportedPowerLevelsImplemented Implementation dependent Static

dot11TxPowerLevel1 Implementation dependent Static

dot11TxPowerLevel2 Implementation dependent Static

dot11TxPowerLevel3 Implementation dependent Static

dot11TxPowerLevel4 Implementation dependent Static

dot11TxPowerLevel5 Implementation dependent Static

dot11TxPowerLevel6 Implementation dependent Static

dot11TxPowerLevel7 Implementation dependent Static

dot11TxPowerLevel8 Implementation dependent Static

dot11CurrentTxPowerLevel Implementation dependent Static

Table 32-19—NGV PHY MIB attributes (continued)

Operational
Managed object Default value/range
semantics

dot11TxPowerLevelExtended Implementation dependent Static

dot11PHYNGVTable

dot11CurrentChannelWidth Implementation dependent Dynamic

dot11CurrentPrimaryChannel Implementation dependent Dynamic

dot11CurrentSecondaryChannel Implementation dependent Dynamic

dot11NGVDYN20MAllowed Implementation dependent Static

32.4.2 PHY MIB

NGV PHY MIB attributes are defined in C.3 with specific values defined in Table 32-19. The “Operational
semantics” column in Table 32-19 contains two types: Static and Dynamic.
— Static MIB attributes are fixed and cannot be modified for a given PHY implementation.
— Dynamic MIB attributes are interpreted according to the MAX-ACCESS field of the MIB attribute.
When MAX-ACCESS is read-only, the MIB attribute value may be updated by the PLME and read from
the MIB attribute by management entities. When MAX-ACCESS is read-write, the MIB attribute may be
read and written by management entities but shall not be updated by the PLME.

32.4.3 TXTIME and PSDU_LENGTH calculation

The value of the TXTIME parameter returned by the PLME-TXTIME.confirm primitive shall be calculated
for an NGV PPDU using Equation (32-42).

TXTIME = 40 + T RL-SIG + T NGV-SIG + T RNGV-SIG + T NGV-STF + N SYM  T SYM +

(32-42)
N NGV-LTF  T NGV-LTF + N MA  N NGV-LTF  T NGV-LTF
8  ------------------------------------------------------------------------------------------------------------------------------
-
8

where
T RL-SIG , T NGV-SIG , T RNGV-SIG , T NGV-STF , and T SYM are defined in Table 32-6
N NGV-LTF is defined in Table 32-7
N MA is defined in 32.3.9.9

For an NGV PPDU using LDPC encoding, the total number of data symbols in the Data field, N SYM , is
given in 21.3.10.5.4 and computed using Equation (19-41) in step d) of 19.3.11.7.5.

The value of the PSDU_LENGTH parameter returned in the PLME-TXTIME.confirm primitive for an NGV
SU PPDU using LDPC encoding is calculated using Equation (32-43).

N SYM ,init N DBPS – N service

PSDU_LENGTH = -------------------------------------------------------------
- (32-43)
8

where
N SYM ,init is given by Equation (21-62) with m STBC = 1 .

32.4.4 NGV PHY

The static NGV PHY characteristics, provided through the PLME-CHARACTERISTICS service primitive,
shall be as shown in Table 17-21 with 10 MHz channel spacing unless otherwise listed in Table 32-20. The
definitions for these characteristics are given in 6.5.4.

Table 32-20—NGV PHY characteristics

Characteristics Value

aSlotTime If dot11OperatingClassesRequired is false, 13 µs.

If dot11OperatingClassesRequired is true, 13 µs plus any

coverage-class-dependent aAirPropagationTime
(see Table 9-95).
aSIFSTime 32 µs

aCCAMidTime 45 µs

aPPDUMaxTime 10.968 ms

aPSDUMaxLength 244 800 octets (see NOTE 1)

aRxPHYStartDelay 64 µs (see NOTE 2)

NOTE 1—This is the maximum length in octets for an NGV PPDU with a bandwidth of
20 MHz, NGV-MCS 9, and two spatial streams, and limited by 1360 possible data symbols in
aPPDUMaxTime. This is the maximum PSDU length an NGV PHY could support assuming
no restrictions in MAC. See 10.3.2 and 9.2.4.7.1 for additional restrictions on the maximum
number of octets the MAC could support.

NOTE 2—This value arises from the time to the end of RNGV-SIG (see Figure 32-5).

32.5 Parameters for NGV-MCSs

The rate-dependent parameters for 10 MHz and 20 MHz are given in Table 32-21 to Table 32-24.

Table 32-21—NGV-MCSs for 10 MHz, NSS = 1

Data rate (Mb/s)

NGV-MCS
Modulation R NBPSCS NSD NCBPS NDBPS 1.6 μs GI
index
NGV-LTF-2x

0 BPSK 1/2 1 52 52 26 3.3

1 QPSK 1/2 2 52 104 52 6.5

2 QPSK 3/4 2 52 104 78 9.8

3 16-QAM 1/2 4 52 208 104 13.0

4 16-QAM 3/4 4 52 208 156 19.5

5 64-QAM 2/3 6 52 312 208 26.0

6 64-QAM 3/4 6 52 312 234 29.3

7 64-QAM 5/6 6 52 312 260 32.5

8 256-QAM 3/4 8 52 416 312 39.0

9 Not valid

10–14 Reserved

15 BPSK-DCM 1/2 1 26 26 13 1.6

Table 32-22—NGV-MCSs for 10 MHz, NSS = 2

Data rate (Mb/s)

NGV-MCS
Modulation R NBPSCS NSD NCBPS NDBPS 1.6 μs GI
index
NGV-LTF-2x

0 BPSK 1/2 1 52 104 52 6.5

1 QPSK 1/2 2 52 208 104 13.0

2 QPSK 3/4 2 52 208 156 19.5

3 16-QAM 1/2 4 52 416 208 26.0

4 16-QAM 3/4 4 52 416 312 39.0

5 64-QAM 2/3 6 52 624 416 52.0

6 64-QAM 3/4 6 52 624 468 58.5

7 64-QAM 5/6 6 52 624 520 65.0

8 256-QAM 3/4 8 52 832 624 78.0

9 Not valid

10–15 Reserved

Table 32-23—NGV-MCSs for 20 MHz, NSS = 1

Data rate (Mb/s)

NGV-MCS
Modulation R NBPSCS NSD NCBPS NDBPS 1.6 μs GI
index
NGV-LTF-2x

0 BPSK 1/2 1 108 108 54 6.8

1 QPSK 1/2 2 108 216 108 13.5

2 QPSK 3/4 2 108 216 162 20.3

3 16-QAM 1/2 4 108 432 216 27.0

4 16-QAM 3/4 4 108 432 324 40.5

5 64-QAM 2/3 6 108 648 432 54.0

6 64-QAM 3/4 6 108 648 486 60.8

7 64-QAM 5/6 6 108 648 540 67.5

8 256-QAM 3/4 8 108 864 648 81.0

9 256-QAM 5/6 8 108 864 720 90.0

10–14 Reserved

15 BPSK-DCM 1/2 1 54 54 27 3.4

Table 32-24—NGV-MCSs for 20 MHz, NSS = 2

Data rate (Mb/s)

NGV-MCS
Modulation R NBPSCS NSD NCBPS NDBPS 1.6 μs GI
index
NGV-LTF-2x

0 BPSK 1/2 1 108 216 108 13.5

1 QPSK 1/2 2 108 432 216 27.0

2 QPSK 3/4 2 108 432 324 40.5

3 16-QAM 1/2 4 108 864 432 54.0

4 16-QAM 3/4 4 108 864 648 81.0

5 64-QAM 2/3 6 108 1296 864 106.0

6 64-QAM 3/4 6 108 1296 972 121.5

7 64-QAM 5/6 6 108 1296 1080 135.0

8 256-QAM 3/4 8 108 1728 1296 162.0

9 256-QAM 5/6 8 108 1728 1440 180.0

10–15 Reserved

Annex B
(normative)

Protocol Implementation Conformance Statement (PICS)

proforma

B.2 Abbreviations and special symbols

B.2.2 General abbreviations for Item and Support columns

Insert the following abbreviation in B.2.2 in alphabetical order:

NGV Next Generation V2X

B.4 PICS proforma—IEEE Std 802.11-20207

Change the rows for items *CFDMG, *CFOCB, *CFEDMG, and *CFNTB and insert two new rows at the
end of the table in B.4.3 as follows (unchanged rows not shown):

B.4.3 IUT configuration

Item IUT configuration References Status Support

…
*CFDMG Directional multi-gigabit (DMG) PHY 9.4.2.127 O.2 Yes  No 
CFDMG:M
CFEDMG:M
CFTDD:M
CFNGV60:M
…
*CFOCB Operation outside the context of a BSS 11.18 O.1 Yes  No 
(OCB) CF5G9:M
CFNGV:M
CFNGV60:M
…
*CFEDMG Enhanced directional multi-gigabit 9.4.2.265 CFEDMG:M Yes  No 
(EDMG) PHY CFNGV60:O
…
*CFNTB Support for FTM non-TB sounding 11.21.6.4.4 CFHE:O Yes  No 
CFNGV:O
…
*CFNGV Next generation V2X (NGV) operation 31.2 O Yes  No 
in the 5.9 GHz band

7
Copyright release for PICS proforma: Users of this standard may freely reproduce the PICS proforma in this annex so that it can be
used for its intended purpose and may further publish the completed PICS.

B.4.3 IUT configuration (continued)

Item IUT configuration References Status Support

*CFNGV60 Next generation V2X (NGV) operation 31.3 O Yes  No 
in the 60 GHz band

B.4.24 DMG features

Change the row for item DMG-M15.1.2 in the table in B.4.24.1 as follows (unchanged rows not shown):

B.4.24.1 DMG MAC features

Item Protocol capability References Status Support

DMG- Beamformed link maintenance procedure 11.27.1 DMG-M15.1.1:O Yes  No 

M15.1.2 NGVM1.2:M N/A 

Insert B.4.38 after B.4.37 (inserted by IEEE Std 802.11az-2022) as follows:

B.4.38 NGV features

B.4.38.1 NGV MAC features

Item Protocol capability References Status Support

Are the following MAC protocol features
supported?
NGVM1 Operating band

NGVM1.1 NGV operation in the 5.9 GHz band 31.2 CFNGV:M Yes  No  N/A 
NGVM1.2 NGV operation in the 60 GHz band 31.3 CFNGV60:M Yes  No  N/A 
NGVM2 NGV fallback procedure

NGVM2.1 20 MHz transmission fallback to 10 MHz 31.2.2 CFNGV:O Yes  No  N/A 

NGVM3 DMG operation

NGVM3.1 DMG OCB element 9.4.2.308 CFNGV60:M Yes  No  N/A 

NGVM3.2 DMG beamforming outside the context of 31.3.1 CFNGV60:M Yes  No  N/A 
a BSS
NGVM4 NGV ranging

NGVM4.1 Support for NGV ranging 31.4 CFNGV:O Yes  No  N/A 

*NGVM4.2 Support for NGV ranging in the 5.9 GHz 31.4 (CFNGV Yes  No  N/A 
frequency band AND
CFNTB):O

B.4.38.2 NGV PHY features

Item Protocol capability References Status Support

Are the following PHY protocol features
supported?
NGVP1 Operating bandwidth

*NGVP1.1 10 MHz operation in the 5.9 GHz band 32.5 CFNGV:M Yes  No  N/A 
*NGVP1.2 20 MHz operation in the 5.9 GHz band 32.5 CFNGV:O Yes  No  N/A 
NGVP2 Modulation and coding schemes (MCS)

NGVP2.1 NGV-MCS with Index = 0–8, or 15 and 32.5 NGVP1.1:M Yes  No  N/A 
10 MHz and NSS = 1
NGVP2.2 NGV-MCS with Index = 0–8 and 10 MHz 32.5 NGVP1.1:O Yes  No  N/A 
and NSS = 2
NGVP2.3 NGV-MCS with Index = 0–9, or 15 and 32.5 NGVP1.2:M Yes  No  N/A 
20 MHz and NSS = 1
NGVP2.4 NGV-MCS with Index = 0–9 and 20 MHz 32.5 NGVP1.2:O Yes  No  N/A 
and NSS = 2
NGVP3 Transmit spectrum masks

NGVP3.1 Spectrum mask, Class A D.2.3 CFNGV:O Yes  No  N/A 

(10 MHz channel spacing)
NGVP3.2 Spectrum mask, Class B D.2.3 CFNGV:O Yes  No  N/A 
(10 MHz channel spacing)
NGVP3.3 Spectrum mask, Class C D.2.3 NGVP1.1:M Yes  No  N/A 
(10 MHz channel spacing)
NGVP3.4 Spectrum mask C2, Class C D.2.3 NGVP1.2:M Yes  No  N/A 
(20 MHz channel spacing)
NGVP3.5 Spectrum mask, Class D D.2.3 CFNGV:O Yes  No  N/A 
(10 MHz channel spacing)
NGVP4 NGV PPDU format

NGVP4.1 Midambles 32.3 CFNGV:M Yes  No  N/A 

NGVP4.2 LDPC support 32.3 CFNGV:M Yes  No  N/A 
NGVP4.3 NGV ranging NDP 31.4 NGVM4.2:M Yes  No  N/A 

B.4.38.3 NGV extended MAC service features

Item Feature References Status Support

Are the following NGV extended MAC
service features supported?
NGVE1 NGV extended MAC service features
NGVE1.1 NGV extended MAC service features— 10.2.3.2 CFNGV:M Yes  No  N/A 
MLME; 5.9 GHz band
(MLME-CANCELTX)
NGVE1.2 NGV extended MAC service features— 11.1.4. CFNGV60:M Yes  No  N/A 
MLME; DMG 11.27
(MLME-DMG-OCB-START,
MLME-DMG-OCB-STOP,
MLME-OCB-DMGDISCOVERY,
MLME-OCB-LINKSTATUS)

Annex C
(normative)

ASN.1 encoding of the MAC and PHY MIB

C.3 MIB detail

Change the item “dot11UnsolicitedBAActivated” (inserted by IEEE Std 802.11ay-2021) at the end of the
list in the object definition that begins with “Dot11StationConfigEntry ::=” in C.3 and insert five new
items after it as follows:

dot11UnsolicitedBAActivated TruthValue,
dot11NONNGVRadioEnvironmentImplemented TruthValue,
dot11NGVOptionImplemented TruthValue,
dot11RadioEnvironmentMeasurementPeriod Unsigned32,
dot11VirtualCSonOCBSecondaryImplemented TruthValue,
dot11StationMeasurementPeriod Unsigned32

Insert the following definitions in C.3 above the three lines containing “End of dot11StationConfig
TABLE” in { dot11StationConfigEntry n } order:

dot11NONNGVRadioEnvironmentImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a capability variable. Its value is determined by device
capabilities. A non-NGV STA supports the radio environment transmit vector
and the radio environment status vector when this attribute is true."
::= { dot11StationConfigEntry 219 }

dot11NGVOptionImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a capability variable. Its value is determined by device
capabilities. This attribute, when true, indicates that the STA supports
NGV features. This STA also has dot11OCBActivated equal to true."
::= { dot11StationConfigEntry 203 }

dot11RadioEnvironmentMeasurementPeriod OBJECT-TYPE
SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This is a control variable. It is written by an external management
entity or the SME. Changes take effect as soon as practical in the
implementations. This attribute indicates the amount of time an NGV STA
conducts the radio measurement before reporting its radio environment.
When equal to 0, measurements are not made."
DEFVAL { 0 }
::= { dot11StationConfigEntry 204 }

dot11VirtualCSonOCBSecondaryImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a capability variable. Its value is determined by device
capabilities. This attribute, when true, indicates that virtual CS
operation in the OCB secondary channel is implemented."
::= { dot11StationConfigEntry 220 }

dot11StationMeasurementPeriod OBJECT-TYPE
SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This is a control variable. It is written by an external management
entity or the SME. Changes take effect as soon as practical in the
implementations. This attribute indicates the amount of time an NGV STA
conducts the STA measurement before reporting its radio environment. When
equal to 0, measurements are not made."
DEFVAL { 0 }
::= { dot11StationConfigEntry 221 }

Change the item “dot11DMGSTATxActivityReportActivated” (inserted by IEEE Std 802.11ay-2021) at

the end of the list in the object definition that begins with “Dot11DMGSTAConfigEntry ::=” in C.3 and
insert a new item after it as follows:

dot11DMGSTATxActivityReportActivated TruthValue,
dot11DMGOCBActivated TruthValue

Insert new text after the object definition that begins with “dot11DMGSTATxActivityReportActivated
OBJECT-TYPE” (inserted by IEEE Std 802.11ay-2021) in C.3 as follows:

dot11DMGOCBActivated OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This is a control variable.
It is written by the SME or an external management entity.
Changes take effect at the next occurrence of an MLME-START.request or
MLME-DMG-OCB-START.request primitive.

This attribute, when true, indicates that the STA supports communication
outside the context of a BSS. This STA also has dot11OCBActivated equal to
true."
DEFVAL { false }
::= { dot11DMGSTAConfigEntry 17 }

Change the object definition that begins with “dot11PHYType OBJECT-TYPE” in C.3 as follows:

dot11PHYType OBJECT-TYPE
SYNTAX INTEGER {
dsss(2),
ofdm(4),
hrdsss(5),
erp(6),
ht(7),
dmg(8),

vht(9),
tvht(10),
s1g(11),
cdmg(12),
cmmg(13),
he(14),
edmg(15),
ngv(17)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a status variable.
It is written by the PHY.

This is an 8-bit integer value that identifies the supported PHY type.
Currently defined values and their corresponding PHY types are:

DSSS 2.4 GHz = 2, OFDM = 4, HRDSSS = 5, ERP = 6, HT = 7, DMG = 8, VHT = 9,

TVHT = 10, S1G = 11, CDMG = 12, CMMG = 13, HE = 14, EDMG = 15, NGV = 17."
::= { dot11PhyOperationEntry 1 }

Insert the following in C.3 after the three lines containing “End of dot11 TVHT Transmit Beamforming
Config TABLE”:

-- **********************************************************************
-- * dot11 Phy NGV TABLE
-- **********************************************************************

dot11PhyNGVTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot11PhyNGVEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry of attributes for dot11PhyNGVTable. Implemented as a table indexed
on ifIndex to allow for multiple instances on an Agent."
::= { dot11phy 37 }

dot11PhyNGVEntry OBJECT-TYPE
SYNTAX Dot11PhyNGVEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in dot11PhyNGVEntryTable. ifIndex - Each IEEE Std 802.11
interface is represented by an ifEntry. Interface tables in this MIB
module are indexed by ifIndex."
INDEX {ifIndex}
::= { dot11PhyNGVTable 1 }

Dot11PhyNGVEntry ::= SEQUENCE

{
dot11NGVCurrentChannelWidth INTEGER,
dot11NGVCurrentPrimaryChannel Unsigned32,
dot11NGVCurrentSecondaryChannel Unsigned32,
dot11NGVDYN20MAllowed TruthValue
}

dot11NGVCurrentChannelWidth OBJECT-TYPE
SYNTAX INTEGER { cbw10(0), cbw20(1) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a status variable.

Written by the PHY.

This attribute indicates the operating channel width."

DEFVAL { cbw10 }
::= { dot11PhyNGVEntry 1 }

dot11NGVCurrentPrimaryChannel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a status variable.
It is written by the PHY.

This attribute indicates the operating channel. If 10/20 MHz OCB is

currently in use then this attribute indicates the primary channel."
::= { dot11PhyNGVEntry 2 }

dot11NGVCurrentSecondaryChannel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a status variable.
It is written by the PHY.

This attribute indicates the channel number of the secondary channel. If

10/20 MHz OCB is not currently in use, this attribute value shall be 0."
::= { dot11PhyNGVEntry 3 }

dot11NGVDYN20MAllowed OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a capability variable.
Its value is determined by device capabilities.

This attribute, when true, indicates that the NGV STA implementation
supports dynamic 20 MHz operation. This capability is disabled otherwise."
::= { dot11PhyNGVEntry 6}

Change the item “dot11DMGSTATxActivityReportActivated” (inserted by IEEE Std 802.11ay-2021) at

the end of the list in the object definition that begins with “dot11DMGComplianceGroup
OBJECT-GROUP” in C.3 and insert a new item after it as follows:

dot11DMGSTATxActivityReportActivated,
dot11DMGOCBActivated

Insert new text after the object definition that begins with “dot11CDMGComplianceGroup1
OBJECT-GROUP” in C.3 as follows:

dot11NGVComplianceGroup OBJECT-GROUP
OBJECTS {
dot11NGVOptionImplemented,
dot11RadioEnvironmentMeasurementPeriod,
dot11VirtualCSonOCBSecondaryImplemented,
dot11NONNGVRadioEnvironmentImplemented,
dot11StationMeasurementPeriod }
STATUS current
DESCRIPTION

"Attributes that configure the NGV Group for IEEE Std 802.11."
::= { dot11Groups 125 }

dot11PhyNGVComplianceGroup OBJECT-GROUP
OBJECTS {
dot11NGVCurrentChannelWidth,
dot11NGVCurrentPrimaryChannel,
dot11NGVCurrentSecondaryChannel,
dot11NGVDYN20MAllowed }
STATUS current
DESCRIPTION
"Attributes that configure the NGV PHY."
::= { dot11Groups 126 }

Change the beginning of “dot11Compliance MODULE-COMPLIANCE” in the “Compliance

Statements” part of C.3 as follows:

dot11Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities that implement the IEEE
802.11 MIB."
MODULE -- this module
MANDATORY-GROUPS {
dot11SMTbase16,
dot11MACbase5,
dot11CountersGroup5,
dot11SmtAuthenticationAlgorithms,
dot11ResourceTypeID,
dot11PhyOperationComplianceGroup2,
dot11EDMGComplianceGroup }

GROUP dot11PhyDSSSComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is
dsss.
This group is mutually exclusive to the following groups:
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyOFDMComplianceGroup3
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is
ofdm.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup

dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyHRDSSSComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is
hrdsss.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyERPComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is erp.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyHTComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is ht.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyVHTComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is vht.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11DMGComplianceGroup
dot11PhyHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyTVHTComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is
tvht.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyS1GComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType is s1g.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyHEComplianceGroup
DESCRIPTION
"Implementation of this group is required when object dot11PHYType has the
value of HE.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup

dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyNGVComplianceGroup"

GROUP dot11PhyNGVComplianceGroup
DESCRIPTION
"Implementation of this group is required when the object dot11PHYType has
the value of ngv.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11HTComplianceGroup
dot11DMGComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11EDMGComplianceGroup"

Change the object definition that begins with “GROUP dot11EDMGComplianceGroup” (inserted by
IEEE Std 802.11ay-2021) in C.3 as follows:

GROUP dot11EDMGComplianceGroup
DESCRIPTION
"Implementation of this group is required when the object dot11PHYType has
the value of EDMG.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11PhyNGVComplianceGroup"

Change the object definition that begins with “GROUP dot11DMGComplianceGroup” (as amended by
IEEE Std 802.11ax-2021) in C.3 as follows:

GROUP dot11DMGComplianceGroup
DESCRIPTION
"Implementation of this group is required when the object
dot11PHYType is dmg.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup

dot11PhyS1GComplianceGroup
dot11CDMGComplianceGroup1
dot11CMMGComplianceGroup
dot11PhyHEComplianceGroup
dot11PhyNGVComplianceGroup"

Change the object definition that begins with “GROUP dot11CDMGComplianceGroup1” in C.3 as
follows:

GROUP dot11CDMGComplianceGroup1
DESCRIPTION
"Implementation of this group is required when the object
dot11PHYType has the value of CDMG.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11DMGComplianceGroup
dot11CMMGComplianceGroup
dot11PhyNGVComplianceGroup"

Change the object definition that begins with “GROUP dot11CMMGComplianceGroup” in C.3 as
follows:

GROUP dot11CMMGComplianceGroup
DESCRIPTION
"Implementation of this group is required when the object
dot11PHYType has the value of CMMG.
This group is mutually exclusive to the following groups:
dot11PhyDSSSComplianceGroup
dot11PhyOFDMComplianceGroup3
dot11PhyHRDSSSComplianceGroup
dot11PhyERPComplianceGroup
dot11PhyHTComplianceGroup
dot11PhyVHTComplianceGroup
dot11PhyTVHTComplianceGroup
dot11DMGComplianceGroup
dot11CDMGComplianceGroup
dot11PhyNGVComplianceGroup"

Insert the following text into “dot11Compliance MODULE-COMPLIANCE” before the line
“-- OPTIONAL-GROUPS {“ in C.3:

GROUP dot11NGVComplianceGroup
DESCRIPTION
"NGV Compliance Group"

Insert the following text after “Compliance Statements - WUR” (inserted by IEEE Std 802.11ba-2021) in
C.3:

-- ********************************************************************
-- * Compliance Statements - NGV
-- ********************************************************************

dot11NGVCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"This object class provides the objects from IEEE 802.11
MIB required to manage Next Generation V2X functionality."
MODULE - this module
MANDATORY-GROUPS {
dot11NGVComplianceGroup,
dot11PhyNGVComplianceGroup }
-- OPTIONAL-GROUPS { }
::= { dot11Compliances 27 }

Annex D
(normative)

Regulatory references

D.2 Radio performance specifications

D.2.3 Transmit spectrum mask

Change the second paragraph of D.2.3 as follows:

For operation in the 5.85–5.925 GHz band the transmitted spectrum shall be as follows:
a) For any STA using 5 MHz channel spacing, the transmitted spectral density shall have a 0 dBr
bandwidth not exceeding 4.5 MHz and shall not exceed the spectrum mask created using the
permitted power spectral density levels listed in Table D-5 for the transmit power class of the STA.
b) For any STA using 10 MHz channel spacing, the transmitted spectral density shall have a 0 dBr
bandwidth not exceeding 9 MHz and shall not exceed the spectrum mask created using the permitted
power spectral density levels listed in Table D-6 for the transmit power class of the STA.
c) For any STA using 20 MHz channel spacing and transmitting a PPDU that is not a 20 MHz NGV
PPDU or 20 MHz non-NGV duplicate PPDU, the transmitted spectral density shall have a 0 dBr
bandwidth not exceeding 18 MHz and shall not exceed the spectrum mask created using the
permitted power spectral density levels listed in Table D-7 for the transmit power class of the STA.
NOTE—The conditions under which conformance to transmit spectral mask C2 is required are specified in 32.3.11.1.

Annex P
(informative)

Location and Time Difference accuracy test

P.3 Differential Distance Computation using Fine Timing Measurement

frames

Change the two equations in P.3 to give them equation numbers as follows:

D SR = c   T SO – T RO  (P-1)

D SR = c   t c1 – t c2 – T –  t 1 – t 4   (P-2)

Insert the following paragraph and Figure P-2 at the end of P.3 as follows:

In Figure P-2 the observing or passive STA (PSTA) that supports NGV non-TB ranging is able to listen to
the NGV non-TB ranging measurement exchange between ISTA and RSTA. The time of flight of a line of
sight transmission between the ISTA and RSTA is denoted as T. At the PSTA, the TOAs of the I2R NDP
and the R2I NDP are respectively t c1 and t c2 . At the ISTA, the TOD of the I2R NDP and the TOA of the
R2I NDP are t 1 and t 4 , respectively. DSR can now be computed according to Equation (P-2). The PSTA
might obtain t 1 and t 4 by receiving the I2R LMR frame or by higher layer information exchange.

t1 = TOD(I2R NDP)

t2 = TOA (I2R NDP)

t3 = TOD(R2I NDP)

t4 = TOA(R2I NDP)

tc1 = TOA (I2R NDP)

tc2 = TOA (R2I NDP)

RSTA PSTA ISTA

Figure P-2—Parameters recorded by PSTA when monitoring non-TB ranging measurement

exchange

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.
RAISING THE
WORLD’S
STANDARDS
Connect with us on:
Twitter: twitter.com/ieeesa
Facebook: facebook.com/ieeesa
LinkedIn: linkedin.com/groups/1791118
Beyond Standards blog: beyondstandards.ieee.org
YouTube: youtube.com/ieeesa

standards.ieee.org
Phone: +1 732 981 0060

Authorized licensed use limited to: Bibliothèque ÉTS. Downloaded on May 01,2023 at 13:41:47 UTC from IEEE Xplore. Restrictions apply.

IEEE STD 3004.8TM-2016 Recommended Practice For Motor Protection in Indusctrial and Commercial Power Systems
100% (2)
IEEE STD 3004.8TM-2016 Recommended Practice For Motor Protection in Indusctrial and Commercial Power Systems
163 pages
IEEE - 15288.1 - Application of Systems Engineering On Defense Programs
100% (3)
IEEE - 15288.1 - Application of Systems Engineering On Defense Programs
65 pages
Ieee 484-2019
No ratings yet
Ieee 484-2019
29 pages
IEEE STD 1547.1 2020
No ratings yet
IEEE STD 1547.1 2020
282 pages
802 3bp-2016
No ratings yet
802 3bp-2016
211 pages
603-2018 IEEE Standard Criteria For Safety Systems For Nuclear Power Generating Stations
100% (1)
603-2018 IEEE Standard Criteria For Safety Systems For Nuclear Power Generating Stations
44 pages
Ieee 1547
100% (3)
Ieee 1547
138 pages
Ieee 323 2003
100% (1)
Ieee 323 2003
28 pages
Ieee Guide For Onsite Acceptance Tests of Electrical Equipment A
100% (5)
Ieee Guide For Onsite Acceptance Tests of Electrical Equipment A
70 pages
IEEE STD 3006.3 - 2017: Power Systems Reliability
100% (3)
IEEE STD 3006.3 - 2017: Power Systems Reliability
34 pages
IEEE Guide For Array and Battery
100% (1)
IEEE Guide For Array and Battery
34 pages
IEEE Guide For Array and BatterySizing in Stand-Alone Photovoltaic (PV) Systems
100% (1)
IEEE Guide For Array and BatterySizing in Stand-Alone Photovoltaic (PV) Systems
34 pages
C57.111-1989 Silicone Oil
No ratings yet
C57.111-1989 Silicone Oil
20 pages
Ieee Guide For Animal Deterrents For Electric Power Supply Subst
100% (1)
Ieee Guide For Animal Deterrents For Electric Power Supply Subst
34 pages
80211bb 2023
No ratings yet
80211bb 2023
37 pages
80211ai 2016 Wireless LAN IEEE 2 27nov20
No ratings yet
80211ai 2016 Wireless LAN IEEE 2 27nov20
164 pages
8021AS 2020 - Cor1 2021
No ratings yet
8021AS 2020 - Cor1 2021
33 pages
IEEE Standard For Ethernet
No ratings yet
IEEE Standard For Ethernet
267 pages
IEEE Standard For Low Rate Wireless Networks
No ratings yet
IEEE Standard For Low Rate Wireless Networks
34 pages
8021CB 2017
No ratings yet
8021CB 2017
102 pages
IEEE STD 802.3bt-2018
No ratings yet
IEEE STD 802.3bt-2018
291 pages
15 15 0658 00 003e Proposal For Ieee802 15 3e Mac
No ratings yet
15 15 0658 00 003e Proposal For Ieee802 15 3e Mac
48 pages
IEEE 8023cr-2021 ISOLATION
No ratings yet
IEEE 8023cr-2021 ISOLATION
130 pages
Ieee Standard For Ethernet Amendment 9physical Layer Specificati
100% (1)
Ieee Standard For Ethernet Amendment 9physical Layer Specificati
267 pages
IEEE Standard 802.15.3
No ratings yet
IEEE Standard 802.15.3
324 pages
IEEE Standard For Local and Metropolitan Area Networks: Overview and Architecture
No ratings yet
IEEE Standard For Local and Metropolitan Area Networks: Overview and Architecture
74 pages
( ( (6WDQGDUGIRU, Qirupdwlrqwhfkqrorj/ 7hohfrppxqlfdwlrqvdqglqirupdwlrq H (Fkdqjhehwzhhqv/Vwhpv /rfdodqgphwursrolwdqduhdqhwzrunv 6shflàfuhtxluhphqwv
No ratings yet
( ( (6WDQGDUGIRU, Qirupdwlrqwhfkqrorj/ 7hohfrppxqlfdwlrqvdqglqirupdwlrq H (Fkdqjhehwzhhqv/Vwhpv /rfdodqgphwursrolwdqduhdqhwzrunv 6shflàfuhtxluhphqwv
51 pages
Ieee Standard For Application: Programming Interfaces (Apis) For Deep Learning (DL) Inference Engines
No ratings yet
Ieee Standard For Application: Programming Interfaces (Apis) For Deep Learning (DL) Inference Engines
31 pages
Media Access Control (MAC) Security Amendment 1: Galois Counter Mode - Advanced Encryption Standard - 256 (GCM-AES-256) Cipher Suite
No ratings yet
Media Access Control (MAC) Security Amendment 1: Galois Counter Mode - Advanced Encryption Standard - 256 (GCM-AES-256) Cipher Suite
52 pages
IEEE Standard 802.11f-2003
No ratings yet
IEEE Standard 802.11f-2003
78 pages
8021AE-2018-Media Access Control (MAC) Security
No ratings yet
8021AE-2018-Media Access Control (MAC) Security
239 pages
Ieee Standard For Devops: Building Reliable and Secure Systems Including Application Build, Package, and Deployment
No ratings yet
Ieee Standard For Devops: Building Reliable and Secure Systems Including Application Build, Package, and Deployment
91 pages
Ieee Standard For Information Technology Telecommunications and
No ratings yet
Ieee Standard For Information Technology Telecommunications and
202 pages
Ieee STD 16 - 2020
No ratings yet
Ieee STD 16 - 2020
50 pages
IEEE STD 3001.11-2017 - Practice For Application of Controllers and Automation
No ratings yet
IEEE STD 3001.11-2017 - Practice For Application of Controllers and Automation
91 pages
IEEE Standard 802.11j 2004
No ratings yet
IEEE Standard 802.11j 2004
53 pages
IEEE Standard For Flame-Propagation Testing of Wire and Cable
No ratings yet
IEEE Standard For Flame-Propagation Testing of Wire and Cable
26 pages
802 11ad-2012
No ratings yet
802 11ad-2012
628 pages
Previews 1999889 Pre
No ratings yet
Previews 1999889 Pre
56 pages
IEEE STD 1559-2022
No ratings yet
IEEE STD 1559-2022
46 pages
IEEE Standard For POSIX Realtime and Embedded Application
No ratings yet
IEEE Standard For POSIX Realtime and Embedded Application
189 pages
IEEE STD C37.20.2a - 2020
0% (1)
IEEE STD C37.20.2a - 2020
14 pages
IEEE Standard For Layer 2 Transport Protocol For Time-Sensitive Applications in Bridged Local Area Networks
No ratings yet
IEEE Standard For Layer 2 Transport Protocol For Time-Sensitive Applications in Bridged Local Area Networks
57 pages
IEEE 497 - Post-Accident Monitoring Instrumentation
No ratings yet
IEEE 497 - Post-Accident Monitoring Instrumentation
36 pages
IEEE Standard For Local and Metropolitan Area Networks: Overview and Architecture Amendment 2: Registration of Object Identifiers
No ratings yet
IEEE Standard For Local and Metropolitan Area Networks: Overview and Architecture Amendment 2: Registration of Object Identifiers
11 pages
Physical Layers Specifications and Management Parameters
No ratings yet
Physical Layers Specifications and Management Parameters
256 pages
IEEE Recommended Practice For Inductive Coordination of Electric Supply and Communication Lines
No ratings yet
IEEE Recommended Practice For Inductive Coordination of Electric Supply and Communication Lines
72 pages
IEEE Standard For Interconnection and Interoperability of Distributed Energy Resources With Associated Electric Power Systems Interfaces
No ratings yet
IEEE Standard For Interconnection and Interoperability of Distributed Energy Resources With Associated Electric Power Systems Interfaces
16 pages
2988-2024 IEEE Standard VSG
No ratings yet
2988-2024 IEEE Standard VSG
52 pages
2988-2024 IEEE Standard VSG
No ratings yet
2988-2024 IEEE Standard VSG
52 pages
8023ch 2020
No ratings yet
8023ch 2020
207 pages
Amendment To IEEE STD 802 - 2001
No ratings yet
Amendment To IEEE STD 802 - 2001
12 pages
2140.1-2020 - IEEE Standard For General Requirements For Cryptocurrency Exchanges
No ratings yet
2140.1-2020 - IEEE Standard For General Requirements For Cryptocurrency Exchanges
18 pages
IEEE 8023bw 2015
No ratings yet
IEEE 8023bw 2015
88 pages
IEEE STD 802.1qav™-2009
No ratings yet
IEEE STD 802.1qav™-2009
87 pages
Ieeestd 2018 8479380
No ratings yet
Ieeestd 2018 8479380
226 pages
IEEE STD 802c™-2017
No ratings yet
IEEE STD 802c™-2017
26 pages
Ieee 802
No ratings yet
Ieee 802
74 pages
802 16 2-2004
No ratings yet
802 16 2-2004
169 pages
IEEE Standard For Test Access Architecture For Three-Dimensional Stacked Integrated Circuits
100% (1)
IEEE Standard For Test Access Architecture For Three-Dimensional Stacked Integrated Circuits
73 pages
IEEE Standard 802.15.1 2005
No ratings yet
IEEE Standard 802.15.1 2005
600 pages
IEEE Standard For Sensor Performance Parameter Definitions: IEEE Electron Devices Society
No ratings yet
IEEE Standard For Sensor Performance Parameter Definitions: IEEE Electron Devices Society
64 pages
Previews 2099211 Pre
No ratings yet
Previews 2099211 Pre
11 pages
IEEE STD 387 2017 Diesel Generators - PDF For Nuclear Stations
No ratings yet
IEEE STD 387 2017 Diesel Generators - PDF For Nuclear Stations
52 pages
Ieee Standard For Practices and Requirements For Semiconductor P
No ratings yet
Ieee Standard For Practices and Requirements For Semiconductor P
13 pages
IEEE Standard For Electrical Power System Device Function Numbers, Acronyms, and Contact Designations
100% (1)
IEEE Standard For Electrical Power System Device Function Numbers, Acronyms, and Contact Designations
62 pages
Ieee C57.12.24 - 2016
No ratings yet
Ieee C57.12.24 - 2016
31 pages
IEEE STD C57.110-2018
No ratings yet
IEEE STD C57.110-2018
3 pages
Previews IEEE 524-2003 Pre
0% (1)
Previews IEEE 524-2003 Pre
7 pages
BS Iso Iec Ieee 18882-2017
No ratings yet
BS Iso Iec Ieee 18882-2017
54 pages
Ieee C57.127-2018
No ratings yet
Ieee C57.127-2018
72 pages
International Standard: Iso/Iec/ Ieee 21450
No ratings yet
International Standard: Iso/Iec/ Ieee 21450
340 pages
IEEE Standards Style Manual
No ratings yet
IEEE Standards Style Manual
70 pages
Ieee STD 2140-2021
No ratings yet
Ieee STD 2140-2021
20 pages
Ieee Sa
No ratings yet
Ieee Sa
13 pages
Ieee 259-1999
No ratings yet
Ieee 259-1999
17 pages
IEEE Guide For Electric Power Distribution Reliability Indices
No ratings yet
IEEE Guide For Electric Power Distribution Reliability Indices
13 pages
Ieee Standard For Polemounted Equipmentenclosure Integrity For C PDF
100% (1)
Ieee Standard For Polemounted Equipmentenclosure Integrity For C PDF
22 pages
Line Trap Standards
100% (1)
Line Trap Standards
46 pages
Understanding The IEEE STD 1547-2018
No ratings yet
Understanding The IEEE STD 1547-2018
9 pages
GUÍA IEEE STD C37.30.2™ 2015
No ratings yet
GUÍA IEEE STD C37.30.2™ 2015
36 pages
10 1109@ieeestd 2018 8546832
No ratings yet
10 1109@ieeestd 2018 8546832
68 pages