WO2022066881A1

WO2022066881A1 - Apparatus, system, and method of national security and emergency preparedness (nsep) priority access

Info

Publication number: WO2022066881A1
Application number: PCT/US2021/051717
Authority: WO
Inventors: Laurent Cariou; Chittabrata GHOSH
Original assignee: Intel Corporation
Priority date: 2020-09-23
Filing date: 2021-09-23
Publication date: 2022-03-31
Also published as: CN115968576A

Abstract

For example, a National Security and Emergency Preparedness (NSEP) priority access frame may be communicated between wireless communication devices. In one example, an NSEP priority frame may be generated by and/or transmitted from an Access Point (AP) wireless communication station (STA). In another example, an NSEP priority frame may be received and/or processed by a non-AP STA. The NSEP priority access frame may include an Enhanced Distributed Channel Access (EDCA) parameter set element defining one or more EDCA parameters.

Description

APPARATUS, SYSTEM, AND METHOD OF NATIONAL SECURITY AND EMERGENCY PREPAREDNESS (NSEP) PRIORITY ACCESS

CROSS REFERENCE

[001] This application claims the benefit of and priority from US Provisional Patent Application No. 63/082,030 entitled “National Security and Emergency Preparedness (NSEP) Priority Access”, filed September 23, 2020, the entire disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

[002] Embodiments described herein generally relate to National Security and Emergency Preparedness (NSEP) priority access.

BACKGROUND

[003] Some wireless communication networks may provide high-throughput data for users of wireless communication devices. For example, some wireless communication networks may utilize wide bandwidths for wireless transmissions.

[004] There is a need for communication services to provide priority for voice and data exchanges on public networks.

BRIEF DESCRIPTION OF THE DRAWINGS

[005] For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

[006] Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.

[007] Fig. 2 is a schematic illustration of an Extremely High Throughput (EHT) Physical layer (PHY) Protocol Data Unit (PPDU) format, which may be implemented in accordance with some demonstrative embodiments.

[008] Fig. 3 is a schematic flow-chart illustration of National Security and Emergency Preparedness (NSEP) priority access, in accordance with some demonstrative embodiments. [009] Fig. 4 is a schematic flow-chart illustration of a method of NSEP priority access, in accordance with some demonstrative embodiments.

[0010] Fig. 5 is a schematic illustration of a product of manufacture, in accordance with some demonstrative embodiments.

DETAILED DESCRIPTION

[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.

[0012] Discussions herein utilizing terms such as, for example, “processing”, “computing”, “calculating”, “determining”, “establishing”, “analyzing”, “checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer’s registers and/or memories into other data similarly represented as physical quantities within the computer’ s registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.

[0013] The terms “plurality” and “a plurality”, as used herein, include, for example, “multiple” or “two or more”. For example, “a plurality of items” includes two or more items.

[0014] References to “one embodiment”, “an embodiment”, “demonstrative embodiment”, “various embodiments” etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one embodiment” does not necessarily refer to the same embodiment, although it may.

[0015] As used herein, unless otherwise specified the use of the ordinal adjectives “first”, “second”, “third” etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0016] Some aspects may be used in conjunction with various devices and systems, for example, a User Equipment (UE), a Mobile Device (MD), a wireless station (STA), a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a wearable device, a sensor device, an Internet of Things (loT) device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a Wireless Video Area Network (WVAN), a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a Wireless PAN (WPAN), and the like.

[0017] Some aspects may be used in conjunction with devices and/or networks operating in accordance with existing IEEE 802.11 standards (including IEEE 802.11- 2020 (IEEE 802.11-2020, 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, February 2021); and/or IEEE 802.11be (IEEE P802.11be/D1.0 Draft Standard for Information technology — Telecommunications and information exchange between systems Local and metropolitan area networks — Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 8: Enhancements for extremely high throughput (EHT), May 2021)) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE) and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

[0018] Some aspects may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a Personal Communication Systems (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable Global Positioning System (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a Multiple Input Multiple Output (MIMO) transceiver or device, a Single Input Multiple Output (SIMO) transceiver or device, a Multiple Input Single Output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, Digital Video Broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a Smartphone, a Wireless Application Protocol (WAP) device, or the like.

[0019] Some aspects may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Infra-Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal Frequency-Division Multiplexing (OFDM), Orthogonal Frequency-Division Multiple Access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division Multiple Access (SDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code- Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra- Wideband (UWB), Global System for Mobile communication (GSM), 4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other aspects may be used in various other devices, systems and/or networks.

[0020] The term “wireless device”, as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative aspects, a wireless device may be or may include a peripheral that may be integrated with a computer, or a peripheral that may be attached to a computer. In some demonstrative aspects, the term “wireless device” may optionally include a wireless service. [0021] The term “communicating” as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase “communicating a signal” may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase “communicating a signal” may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device. The communication signal may be transmitted and/or received, for example, in the form of Radio Frequency (RF) communication signals, and/or any other type of signal.

[0022] As used herein, the term "circuitry" may refer to, be part of, or include, an Application Specific Integrated Circuit (ASIC), an integrated circuit, an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some aspects, circuitry may include logic, at least partially operable in hardware.

[0023] The term “logic” may refer, for example, to computing logic embedded in circuitry of a computing apparatus and/or computing logic stored in a memory of a computing apparatus. For example, the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and/or operations. In one example, logic may be embedded in various types of memory and/or firmware, e.g., silicon blocks of various chips and/or processors. Logic may be included in, and/or implemented as part of, various circuitry, e.g. radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, and/or the like. In one example, logic may be embedded in volatile memory and/or non-volatile memory, including random access memory, read only memory, programmable memory, magnetic memory, flash memory, persistent memory, and the like. Logic may be executed by one or more processors using memory, e.g., registers, stuck, buffers, and/or the like, coupled to the one or more processors, e.g., as necessary to execute the logic.

[0024] Some demonstrative aspects may be used in conjunction with a WLAN, e.g., a WiFi network. Other aspects may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a “piconet”, a WPAN, a WVAN and the like.

[0025] Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over a frequency band between 1GHz and 7.250Ghz, for example, a 2.4 Gigahertz (GHz) frequency band, a 5GHz frequency band, and/or a 6GHz frequency band. However, other aspects may be implemented utilizing any other suitable wireless communication frequency bands, for example, an Extremely High Frequency (EHF) band (the millimeter wave (mmWave) frequency band), e.g., a frequency band within the frequency band of between 20Ghz and 300GHz, a frequency band above 45GHz, a 5G frequency band, a frequency band below 20GHz, e.g., a Sub 1 GHz (SIG) band, a WLAN frequency band, a WPAN frequency band, a frequency band according to the WGA specification, and the like.

[0026] The term “antenna”, as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some aspects, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some aspects, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a set of switched beam antennas, and/or the like.

[0027] Some demonstrative embodiments may be implemented by an Extremely High Throughput (EHT) STA, which may include for example, a STA having a radio transmitter, which is capable of operating on a channel that is in frequency bands between 1GHz and 7.250Ghz. The EHT STA may perform other additional or alternative functionality. Other embodiments may be implemented by any other apparatus, device and/or station.

[0028] Reference is made to Fig. 1, which schematically illustrates a system 100, in accordance with some demonstrative embodiments.

[0029] As shown in Fig. 1, in some demonstrative embodiments, system 100 may include one or more wireless communication devices. For example, system 100 may include a wireless communication device 102, a wireless communication device 140, and/or one more other devices.

[0030] In some demonstrative embodiments, devices 102 and/or 140 may include a mobile device or a non-mobile, e.g., a static, device.

[0031] For example, devices 102 and/or 140 may include, for example, a UE, an MD, a STA, an AP, a Smartphone, a PC, a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, an Internet of Things (loT) device, a sensor device, a handheld device, a wearable device, a PDA device, a handheld PDA device, an onboard device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “Carry Small Live Large” (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an “Origami” device or computing device, a device that supports Dynamically Composable Computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a Set-Top-Box (STB), a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a media player, a television, a music player, a smart device such as, for example, lamps, climate control, car components, household components, appliances, and the like. [0032] In some demonstrative embodiments, device 102 may include, for example, one or more of a processor 191, an input unit 192, an output unit 193, a memory unit 194, and/or a storage unit 195; and/or device 140 may include, for example, one or more of a processor 181, an input unit 182, an output unit 183, a memory unit 184, and/or a storage unit 185. Devices 102 and/or 140 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of devices 102 and/or 140 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of devices 102 and/or 140 may be distributed among multiple or separate devices.

[0033] In some demonstrative embodiments, processor 191 and/or processor 181 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. Processor 191 may execute instructions, for example, of an Operating System (OS) of device 102 and/or of one or more suitable applications. Processor 181 may execute instructions, for example, of an Operating System (OS) of device 140 and/or of one or more suitable applications.

[0034] In some demonstrative embodiments, input unit 192 and/or input unit 182 may include, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 193 and/or output unit 183 may include, for example, a display, a screen, a touch-screen, one or more audio speakers or earphones, and/or other suitable output devices.

[0035] In some demonstrative embodiments, memory unit 194 and/or memory unit 184 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 195 and/or storage unit 185 may include, for example, a hard disk drive, a disk drive, a solid-state drive (SSD), and/or other suitable removable or non-removable storage units. Memory unit 194 and/or storage unit 195, for example, may store data processed by device 102. Memory unit 184 and/or storage unit 185, for example, may store data processed by device 140.

[0036] In some demonstrative embodiments, wireless communication devices 102 and/or 140 may be capable of communicating content, data, information and/or signals via a wireless medium (WM) 103. In some demonstrative embodiments, wireless medium 103 may include, for example, a radio channel, a cellular channel, an RF channel, a WiFi channel, a 5G channel, an IR channel, a Bluetooth (BT) channel, a Global Navigation Satellite System (GNSS) Channel, and the like.

[0037] In some demonstrative embodiments, device 102 and/or device 140 may include one or more radios including circuitry and/or logic to perform wireless communication between devices 102, 140 and/or one or more other wireless communication devices. For example, device 102 may include at least one radio 114, and/or device 140 may include at least one radio 144.

[0038] In some demonstrative embodiments, radio 114 and/or radio 144 may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio 114 may include at least one receiver 116, and/or radio 144 may include at least one receiver 146.

[0039] In some demonstrative embodiments, radio 114 and/or radio 144 may include one or more wireless transmitters (Tx) including circuitry and/or logic to transmit wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio 114 may include at least one transmitter 118, and/or radio 144 may include at least one transmitter 148.

[0040] In some demonstrative embodiments, radio 114 and/or radio 144, transmitters 118 and/or 148, and/or receivers 116 and/or 146 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; modulation elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital and/or digital to analog converters; filters; and/or the like. For example, radio 114 and/or radio 144 may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like.

[0041] In some demonstrative embodiments, radios 114 and/or 144 may be configured to communicate over a directional band, for example, a frequency band in frequency bands between 1 GHz and 7.250 GHz, for example, a 2.4GHz band, a 5GHz band, a 6GHz band, and/or any other frequency band, for example, frequency band above 45 GHz, an SIG band, and/or any other band.

[0042] In some demonstrative embodiments, radios 114 and/or 144 may include, or may be associated with one or more, e.g., a plurality of, antennas.

[0043] In some demonstrative embodiments, device 102 may include one or more, e.g., a single antenna or a plurality of, antennas 107, and/or device 140 may include on or more, e.g., a plurality of, antennas 147.

[0044] Antennas 107 and/or 147 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 107 and/or 147 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. Antennas 107 and/or 147 may include, for example, antennas suitable for directional communication, e.g., using beamforming techniques. For example, antennas 107 and/or 147 may include a single antenna, a plurality of antennas, a phased array antenna, a multiple element antenna, a set of switched beam antennas, and/or the like. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0045] In some demonstrative embodiments, antennas 107 and/or antennas 147 may be connected to, and/or associated with, one or more Radio Frequency (RF) chains.

[0046] In some demonstrative embodiments, device 102 may include one or more, e.g., a plurality of, RF chains 109 connected to, and/or associated with, antennas 107. [0047] In some demonstrative embodiments, one or more of RF chains 109 may be included as part of, and/or implemented as part of one or more elements of radio 114, e.g., as part of transmitter 118 and/or receiver 116.

[0048] In some demonstrative embodiments, device 140 may include one or more, e.g., a plurality of, RF chains 149 connected to, and/or associated with, antennas 147.

[0049] In some demonstrative embodiments, one or more of RF chains 149 may be included as part of, and/or implemented as part of one or more elements of radio 144, e.g., as part of transmitter 148 and/or receiver 146.

[0050] In some demonstrative embodiments, device 102 may include a controller 124, and/or device 140 may include a controller 154. Controller 124 may be configured to perform and/or to trigger, cause, instruct and/or control device 102 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140 and/or one or more other devices; and/or controller 154 may be configured to perform, and/or to trigger, cause, instruct and/or control device 140 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140 and/or one or more other devices, e.g., as described below.

[0051] In some demonstrative embodiments, controllers 124 and/or 154 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media- Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, baseband (BB) circuitry and/or logic, a BB processor, a BB memory, Application Processor (AP) circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of controllers 124 and/or 154, respectively. Additionally or alternatively, one or more functionalities of controllers 124 and/or 154 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0052] In one example, controller 124 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 102, and/or a wireless station, e.g., a wireless STA implemented by device 102, to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 124 may include at least one memory, e.g., coupled to the one or more processors, which may be configured, for example, to store, e.g., at least temporarily, at least some of the information processed by the one or more processors and/or circuitry, and/or which may be configured to store logic to be utilized by the processors and/or circuitry.

[0053] In one example, controller 154 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 140, and/or a wireless station, e.g., a wireless STA implemented by device 140, to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 154 may include at least one memory, e.g., coupled to the one or more processors, which may be configured, for example, to store, e.g., at least temporarily, at least some of the information processed by the one or more processors and/or circuitry, and/or which may be configured to store logic to be utilized by the processors and/or circuitry.

[0054] In some demonstrative embodiments, at least part of the functionality of controller 124 may be implemented as part of one or more elements of radio 114, and/or at least part of the functionality of controller 154 may be implemented as part of one or more elements of radio 144.

[0055] In other embodiments, the functionality of controller 124 may be implemented as part of any other element of device 102, and/or the functionality of controller 154 may be implemented as part of any other element of device 140.

[0056] In some demonstrative embodiments, device 102 may include a message processor 128 configured to generate, process and/or access one or messages communicated by device 102.

[0057] In one example, message processor 128 may be configured to generate one or more messages to be transmitted by device 102, and/or message processor 128 may be configured to access and/or to process one or more messages received by device 102, e.g., as described below. [0058] In one example, message processor 128 may include at least one first component configured to generate a message, for example, in the form of a frame, field, information element and/or protocol data unit, for example, a MAC Protocol Data Unit (MPDU); at least one second component configured to convert the message into a PHY Protocol Data Unit (PPDU), for example, by processing the message generated by the at least one first component, e.g., by encoding the message, modulating the message and/or performing any other additional or alternative processing of the message; and/or at least one third component configured to cause transmission of the message over a wireless communication medium, e.g., over a wireless communication channel in a wireless communication frequency band, for example, by applying to one or more fields of the PPDU one or more transmit waveforms. In other embodiments, message processor 128 may be configured to perform any other additional or alternative functionality and/or may include any other additional or alternative components to generate and/or process a message to be transmitted.

[0059] In some demonstrative embodiments, device 140 may include a message processor 158 configured to generate, process and/or access one or messages communicated by device 140.

[0060] In one example, message processor 158 may be configured to generate one or more messages to be transmitted by device 140, and/or message processor 158 may be configured to access and/or to process one or more messages received by device 140, e.g., as described below.

[0061] In one example, message processor 158 may include at least one first component configured to generate a message, for example, in the form of a frame, field, information element and/or protocol data unit, for example, a MAC Protocol Data Unit (MPDU); at least one second component configured to convert the message into a PHY Protocol Data Unit (PPDU), for example, by processing the message generated by the at least one first component, e.g., by encoding the message, modulating the message and/or performing any other additional or alternative processing of the message; and/or at least one third component configured to cause transmission of the message over a wireless communication medium, e.g., over a wireless communication channel in a wireless communication frequency band, for example, by applying to one or more fields of the PPDU one or more transmit waveforms. In other embodiments, message processor 158 may be configured to perform any other additional or alternative functionality and/or may include any other additional or alternative components to generate and/or process a message to be transmitted.

[0062] In some demonstrative embodiments, message processors 128 and/or 158 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, BB circuitry and/or logic, a BB processor, a BB memory, AP circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of message processors 128 and/or 158, respectively. Additionally or alternatively, one or more functionalities of message processors 128 and/or 158 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0063] In some demonstrative embodiments, at least part of the functionality of message processor 128 may be implemented as part of radio 114, and/or at least part of the functionality of message processor 158 may be implemented as part of radio 144.

[0064] In some demonstrative embodiments, at least part of the functionality of message processor 128 may be implemented as part of controller 124, and/or at least part of the functionality of message processor 158 may be implemented as part of controller 154.

[0065] In other embodiments, the functionality of message processor 128 may be implemented as part of any other element of device 102, and/or the functionality of message processor 158 may be implemented as part of any other element of device 140.

[0066] In some demonstrative embodiments, at least part of the functionality of controller 124 and/or message processor 128 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio 114. For example, the chip or SoC may include one or more elements of controller 124, one or more elements of message processor 128, and/or one or more elements of radio 114. In one example, controller 124, message processor 128, and radio 114 may be implemented as part of the chip or SoC. [0067] In other embodiments, controller 124, message processor 128 and/or radio 114 may be implemented by one or more additional or alternative elements of device 102.

[0068] In some demonstrative embodiments, at least part of the functionality of controller 154 and/or message processor 158 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio 144. For example, the chip or SoC may include one or more elements of controller 154, one or more elements of message processor 158, and/or one or more elements of radio 144. In one example, controller 154, message processor 158, and radio 144 may be implemented as part of the chip or SoC.

[0069] In other embodiments, controller 154, message processor 158 and/or radio 144 may be implemented by one or more additional or alternative elements of device 140.

[0070] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more STAs. For example, device 102 may include at least one STA, and/or device 140 may include at least one STA.

[0071] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more EHT STAs. For example, device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT STA, and/or device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT STA.

[0072] In other embodiments, devices 102 and/or 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, any other wireless device and/or station, e.g., a WLAN STA, a WiFi STA, and the like.

[0073] In some demonstrative embodiments, device 102 and/or device 140 may be configured operate as, perform the role of, and/or perform one or more functionalities of, an access point (AP), e.g., an EHT AP.

[0074] In some demonstrative embodiments, device 102 and/or device 140 may be configured to operate as, perform the role of, and/or perform one or more functionalities of, a non-AP STA, e.g., an EHT non-AP STA. [0075] In other embodiments, device 102 and/or device 140 may operate as, perform the role of, and/or perform one or more functionalities of, any other additional or alternative device and/or station.

[0076] In one example, a station (STA) may include a logical entity that is a singly addressable instance of a medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM). The STA may perform any other additional or alternative functionality.

[0077] In one example, an AP may include an entity that contains a station (STA), e.g., one STA, and provides access to distribution services, via the wireless medium (WM) for associated STAs. The AP may perform any other additional or alternative functionality.

[0078] In one example, a non-AP STA may include a STA that is not contained within an AP. The non-AP STA may perform any other additional or alternative functionality.

[0079] In some demonstrative embodiments devices 102 and/or 140 may be configured to communicate over an EHT network, and/or any other network. For example, devices 102 and/or 140 may perform Multiple-Input-Multiple-Output (MIMO) communication, for example, for communicating over the EHT networks, e.g., over an EHT frequency band, e.g., in frequency bands between 1 GHz and 7.250 GHz.

[0080] In some demonstrative embodiments, devices 102 and/or 140 may be configured to operate in accordance with one or more Specifications, for example, including one or more IEEE 802.11 Specifications, e.g., an IEEE 802.11-2020 Specification, an IEEE 802.1 Ibe Specification, and/or any other specification and/or protocol.

[0081] In some demonstrative embodiments, devices 102 and/or 140 may be configured according to one or more standards, for example, in accordance with an IEEE 802.1 Ibe Standard, which may be configured, for example, to enhance the efficiency and/or performance of an IEEE 802.11 Specification, which may be configured to provide Wi-Fi connectivity.

[0082] Some demonstrative embodiments may enable, for example, to significantly increase the data throughput defined in the IEEE 802.11-2020 Specification, for example, up to a throughput of 30 Giga bits per second (Gbps), or to any other throughput, which may, for example, satisfy growing demand in network capacity for new coming applications.

[0083] Some demonstrative embodiments may be implemented, for example, to support increasing a transmission data rate, for example, by applying MIMO and/or Orthogonal Frequency Division Multiple Access (OFDM A) techniques.

[0084] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate MIMO communications and/or OFDMA communication in frequency bands between 1 GHz and 7.250 GHz.

[0085] In some demonstrative embodiments, device 102 and/or device 140 may be configured to support one or more mechanisms and/or features, for example, OFDMA, Single User (SU) MIMO, and/or Multi-User (MU) MIMO, for example, in accordance with an IEEE 802.1 Ibe Standard and/or any other standard and/or protocol.

[0086] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, one or more EHT STAs. For example, device 102 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT STA, and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT STA.

[0087] In some demonstrative embodiments, devices 102 and/or 140 may implement a communication scheme, which may include Physical layer (PHY) and/or Media Access Control (MAC) layer schemes, for example, to support one or more applications, and/or increased throughput, e.g., throughputs up to 30 Gbps, or any other throughput.

[0088] In some demonstrative embodiments, the PHY and/or MAC layer schemes may be configured to support OFDMA techniques, SU MIMO techniques, and/or MU MIMO techniques.

[0089] In some demonstrative embodiments, devices 102 and/or 140 may be configured to implement one or more mechanisms, which may be configured to enable SU and/or MU communication of Downlink (DL) and/or Uplink frames (UL) using a MIMO scheme.

[0090] In some demonstrative embodiments, device 102 and/or device 140 may be configured to implement one or more MU communication mechanisms. For example, devices 102 and/or 140 may be configured to implement one or more MU mechanisms, which may be configured to enable MU communication of DL frames using a MIMO scheme, for example, between a device, e.g., device 102, and a plurality of devices, e.g., including device 140 and/or one or more other devices.

[0091] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate over an EHT network, and/or any other network and/or any other frequency band. For example, devices 102 and/or 140 may be configured to communicate DL transmissions and/or UL transmissions, for example, for communicating over the EHT networks.

[0092] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate over a channel bandwidth, e.g., of at least 20 Megahertz (MHz), in frequency bands between 1 GHz and 7.250 GHz.

[0093] In some demonstrative embodiments, devices 102 and/or 140 may be configured to implement one or more mechanisms, which may, for example, support communication over a wide channel bandwidth (BW) (“channel width”) (also referred to as a “wide channel” or “wide BW”) covering two or more channels, e.g., two or more 20 MHz channels, e.g., as described below.

[0094] In some demonstrative embodiments, wide channel mechanisms may include, for example, a mechanism and/or an operation whereby two or more channels, e.g., 20MHz channels, can be combined, aggregated or bonded, e.g., for a higher bandwidth of packet transmission, for example, to enable achieving higher throughputs, e.g., when compared to transmissions over a single channel. Some demonstrative embodiments are described herein with respect to communication over a channel BW including two or more 20MHz channels, however other embodiments may be implemented with respect to communications over a channel bandwidth, e.g., a “wide” channel, including or formed by any other number of two or more channels, for example, a bonded or aggregated channel including a bonding or an aggregation of two or more channels.

[0095] In some demonstrative embodiments, device 102 and/or device 140 may be configured to communicate one or more transmissions over one or more channel BWs, for example, including a channel BW of 20MHz, a channel BW of 40MHz, a channel BW of 80MHz, a channel BW of 160MHz, a channel BW of 320MHz, and/or any other additional or alternative channel BW, e.g., as described below. [0096] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive a Physical Layer (PHY) Protocol Data Unit (PPDU) having a PPDU format (also referred to as “EHT PPDU format”), which may be configured, for example, for communication between EHT stations, e.g., as described below.

[0097] In some demonstrative embodiments, a PPDU, e.g., an EHT PPDU, may include at least one non-EHT field, e.g., a legacy field, which may be identified, decodable, and/or processed by one or more devices (“non-EHT devices”, or “legacy devices”), which may not support one or more features and/or mechanisms (“nonlegacy” mechanisms or “non-EHT mechanisms”). For example, the legacy devices may include non-EHT stations and/or non-High Throughput (HT) stations, which may be, for example, configured according to an IEEE 802.11-2020 Standard, and the like.

[0098] Reference is made to Fig. 2, which schematically illustrates an EHT PPDU format 200, which may be implemented in accordance with some demonstrative embodiments. In one example, devices 102 (Fig. 1) and/or 140 (Fig. 1) may be configured to generate, transmit, receive and/or process one or more EHT PPDUs having the structure and/or format of EHT PPDU 200.

[0099] In one example, devices 102 (Fig. 1) and/or 140 (Fig. 1) may communicate EHT PPDU 200, for example, as part of a transmission over a channel, e.g., an EHT channel, having a channel bandwidth including one or more 20MHz channels, for example, a channel BW of 20MHz, a channel BW of 40MHz, a channel BW of 80MHz, a channel BW of 160MHz, a channel BW of 320MHz, and/or any other additional or alternative channel BW, e.g., as described below.

[00100] In some demonstrative embodiments, EHT PPDU 200 may include an EHT SU PPDU, which may be utilized for transmission from an EHT STA, e.g., an EHT STA implemented by device 102 (Fig. 1), to one another STA, e.g., an EHT STA implemented by device 140 (Fig. 1).

[00101] In some demonstrative embodiments, EHT PPDU 200 may include an EHT MU PPDU, which may be utilized for transmission from an EHT STA, e.g., an EHT STA implemented by device 102 (Fig. 1), to one or more users, for example, one or more EHT STAs, including an EHT STA implemented by device 140 (Fig. 1). [00102] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a non-High Throughput (non-HT) (legacy) Short Training Field (STF) (L-STF) 202, followed by a non-HT (Legacy) Long Training Field (LTF) (L-LTF) 204, which may be followed by a non-HT Signal (SIG) (L-SIG) field 206.

[00103] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a repeated non-HT SIG (RL-SIG) field 208, which may follow the L-SIG field 206. The RL-SIG field 208 may be followed by a Universal SIG (U-SIG) field 210.

[00104] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a plurality of EHT-modulated fields, e.g., following the U-SIG field 210.

[00105] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT Signal (EHT-SIG) field 212.

[00106] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT STF (EHT-STF) field 214, e.g., following the EHT-SIG field 212.

[00107] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT LTF (EHT-LTF) field 216, e.g., following the EHT-STF field 214.

[00108] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, a data field 218, e.g., following the EHT-LTF field 216, and/or a Packet Extension (PE) field 220, e.g., following the data field 218.

[00109] In some demonstrative embodiments, EHT PPDU 200 may include some or all of the fields shown in Fig. 2 and/or one or more other additional or alternative fields.

[00110] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive and/or process one or more transmissions, e.g., including one or more EHT PPDUs, e.g., as described below.

[00111] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process one or more transmissions, e.g., including one or more EHT PPDUs, e.g., including one or more fields according to the EHT PPDU format of Fig. 2. [00112] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive and/or process an EHT PPDU, e.g., in accordance with an IEEE 802.11be Specification and/or any other specification, e.g., as described below.

[00113] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process the EHT PPDU as an EHT MU PPDU, for example, in accordance with the EHT PPDU formal 200 (Fig. 2).

[00114] In some demonstrative aspects, the EHT MU PPDU may include a PPDU that carries one or more PHY service data units (PSDUs) for one or more STAs using a downlink multi-user multiple input, multiple output (DL-MU-MIMO) technique, an orthogonal frequency division multiple access (DL OFDMA) technique, or a combination of the two techniques.

[00115] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process the EHT MU PPDU, for example, over a 20MHz channel width, a 40MHz channel width, a 80MHz channel width, a 160MHz channel width, and/or a 320Mhz channel width.

[00116] In other embodiments, any other additional or alternative channel width may be utilized.

[00117] In some demonstrative embodiments, device 102 and/or device 140 may be configured to perform one or more operations, functionalities, and/or procedures, which may be configured for National Security and Emergency Preparedness (NSEP) priority access, e.g., as described below.

[00118] For example, NSEP priority access may include an on-demand capability, which may provide, for example, higher priority to traffic generated by authorized non- access point (AP) stations (STA), and/or to traffic destined for authorized non-AP STAs. [00119] For example, NSEP traffic may include traffic generated by a non-AP STA, or traffic destined for a non-AP STA, for example, when the NSEP priority access is enabled.

[00120] For example, NSEP communication services may be implemented in multiple countries to provide priority for voice and data exchanges on public networks.

[00121] In one example, NSEP Services in the US, including the Government Emergency Telephone Service and the Wireless Priority Service, run on commercial operator networks and are managed by the Emergency Communications Division of the Cybersecurity and Infrastructure Security Agency within the Department of Homeland Security.

[00122] For example, NSEP Priority Access is intended to provide capabilities to support such priority services on Wi-Fi-based networks. Priority access capabilities to support these services in other types of networks are defined in appropriate international standards, e.g., multimedia priority service (MPS) in 3GPP. Or the like.

[00123] For example, NSEP priority access may be utilized to provide priority to system resource access for authorized users, e.g., to enhance their probability of successful communication during periods of network congestion.

[00124] For example, priority access may involve preferential treatment in obtaining channel access and in allocation of network resources.

[00125] For example, the priority access service may be made available in a restricted manner, e.g., only to designated, authorized individuals, or devices who normally represent a small fraction of the overall user base.

[00126] For example, APs that have NSEP priority access activated may advertise this capability, e.g., in beacon and/or probe response frames.

[00127] For example, non-AP STAs with NSEP priority access activated may query APs that advertise NSEP priority access, e.g., to gain additional details prior to association.

[00128] For example, during association, APs may verify the authority of non-AP STAs to use NSEP priority access. This could be accomplished, for example, using a subscription service provider’s authorization infrastructure, e.g., via a Subscription Service Provider Network (SSPN) interface. For example, the AP might store the results of this authorization process locally, e.g., to enable subsequent verification. The AP might also use this information to confirm authority, e.g., during (re)Association.

[00129] For example, the NSEP priority access may be operated as not an always-on function, but rather may operate in an on-demand fashion. For example, when an authorized user or the managed service provider detects the need for priority, it invokes NSEP priority access, e.g., via a higher layer function within the STA. For example, a functionality of detecting the need for priority may be defined under different scope.

[00130] In one example, the non-AP STA may request NSEP priority access, e.g., by sending a request to the AP. The AP may confirm the authority of the non-AP STA to use NSEP priority access, e.g., using the locally stored verification information or reaching out to an NSEP service provider, e.g., via the SSPN interface. The AP may send a response to the requesting non-AP STA.

[00131] In another example, the AP may enable NSEP priority access by sending an unsolicited request to a non-AP STA, and the non-AP STA may confirm the request, e.g., by sending a response.

[00132] For example, while NSEP priority access is enabled, all traffic to and from the non-AP may be provided with preferential treatment.

[00133] For example, either the AP or the non-AP STA may be allowed to disable NSEP priority access, for example, by sending another request.

[00134] For example, to enable STAs to communicate their need for NSEP priority access during periods of network congestion, a STA may be allowed to use NSEP priority access, e.g., when transmitting NSEP priority access request and response frames. For example, a means by which the AP determines the need for priority may be defined under different scope.

[00135] For example, a STA with a value of true for dotl INSEPPriorityAccessActivated shall set to 1 the NSEP priority access field of Extended Capabilities elements that it transmits and is called an NSEP STA. If the STA is an AP, the AP is called an NSEP AP.

[00136] For example, during the (re) association process, the AP shall obtain information describing the authority of the non-AP STA to use NSEP priority access. For example, this authorization information may be retrieved from a NSEP service provider via an SSPN interface. Other methods of obtaining this authorization information may be defined.

[00137] For example, an NSEP non-AP STA shall request the use of NSEP priority access by transmitting an NSEP priority access request frame with a value of Enable in the request type field to an associated NSEP AP, e.g., when instructed to do so by a higher-layer function. The AP may verify the authority of the non-AP STA to use NSEP priority access. For example, if the requesting non-AP STA is verified for NSEP priority access, the NSEP AP may respond to the request, e.g., by transmitting an NSEP priority access response action frame with a value of SUCCESS in the status code field. Alternatively, the NSEP AP may instruct the non-AP STA to enable NSEP priority access by transmitting an NSEP priority access request frame with the value of Enable in the request type field to the STA. The non-AP STA shall confirm receipt of the NSEP priority access request frame by transmitting an NSEP priority access response frame with a value of SUCCESS in the status code field.

[00138] For example, a mechanism by which the AP verifies the authority to use NSEP priority access may be defined under different scope. For example, a method by which the AP recognizes that NSEP priority access should be enabled for an associated STA may be a higher-layer function, which may be defined under different scope.

[00139] For example, if the NSEP priority access response frame transmitted by the AP or the non-AP STA contained a status code of SUCCESS, then the AP and non-AP STA shall apply NSEP priority access to all MAC PDUs (MPDUs) exchanged between the AP and the non-AP STA.

[00140] For example, priority access shall remain in effect until disabled by either the AP or the non-AP STA.

[00141] For example, to disable NSEP priority access, a non-AP STA shall send an NSEP priority access request frame with the value of DISABLE in the request type field to the AP. An AP that receives an NSEP priority access request frame from an associated STA shall transmit an NSEP priority access response frame to the STA. To disable NSEP priority access, an AP shall send a request action frame with the value of DISABLE in the request type field to the non-AP STA. A non-AP STA that received an NSEP priority access request frame shall transmit an NSEP priority access response frame to the AP. A STA may use NSEP priority access when transmitting NSEP priority access request and response frames.

[00142] In some demonstrative embodiments, there may be a need to provide a technical solution to address a technical issue for supporting the NSEP priority access, e.g., to efficiently support and/or ensure that higher priority is given to NSEP traffic.

[00143] In some demonstrative embodiments, in some use cases, scenarios, and/or implementation, there may be one or more technical problems, inefficiencies and/or disadvantages, if the NSEP traffic is handled as Voice Access Category (AC) (AC-VO) traffic, e.g., as described below.

[00144] For example, in some use cases, scenarios, and/or implementation, there may be one or more technical problems, inefficiencies and/or disadvantages, in defining that NSEP priority access is achieved by transmitting each MPDU using the Enhanced Distributed Channel Access (EDC A) category of AC_VO. For example, APs should give priority to frames transmitted between itself and NSEP non-AP STAs compared to AC_VO traffic to or from other non-NSEP STAs.

[00145] For example, there may be a technical problem in defining that NSEP priority access is achieved by transmitting each MPDU using the EDCA category of AC_VO, since treating everything with the AC_VO will not really work as it will likely lead to a lot of collisions.

[00146] In some demonstrative embodiments, NSEP priority access may be implemented using an EDCA parameter set element to define one or more EDCA parameters for the NSEP traffic, e.g., as described below.

[00147] In some demonstrative embodiments, the EDCA parameter set element may be included and communicated as part of one ore mor action frames, which may be communicated between the AP STA and the non-AP STA, e.g., as described below.

[00148] For example, an NSEP non-AP STA shall request the use of NSEP priority access by transmitting an NSEP priority access request frame, e.g., with a value of enable in the request type field, to an associated NSEP AP, for example, when instructed to do so by a higher-layer function. For example, the AP may verify the authority of the non-AP STA to use NSEP priority access. For example, if the requesting non-AP STA is verified for NSEP priority access, the NSEP AP responds to the request, e.g., by transmitting an NSEP priority access response action frame, e.g., with a value of SUCCESS in the status code field. Alternatively, the NSEP AP may instruct the non-AP STA to enable NSEP priority access by transmitting an NSEP priority access request frame, e.g., with the value of Enable in the request type field, to the STA. For example, the non-AP STA shall confirm receipt of the NSEP priority access request frame, for example, by transmitting an NSEP priority access response frame, e.g., with a value of SUCCESS in the status code field.

[00149] In some demonstrative embodiments, a mechanism for NSEP priority access may facilitate that the AP STA includes in an NSEP priority access response action frame, or in an NSEP priority access request action frame, an EDCA parameter set element that will define the EDCA parameters for the non-AP STA, e.g., as described below.

[00150] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate that if the response is accepted (e.g., status code SUCCESS), the STA shall update its EDCA parameters with the parameters provided in the NSEP priority access action frame, and use it, for example, until the NSEP session is terminated, e.g., as described below.

[00151] In some demonstrative embodiments, these EDCA parameters may be configured to be, and/or expected to be, more aggressive, e.g., than the EDCA parameters that are otherwise provided, e.g., by the AP, to the entire Basis Service Set (BSS), e.g., in beacons and/or probe responses, e.g., as described below.

[00152] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate that the non-AP STA that is using these EDCA parameters, e.g., as provided by the AP in the NSEP priority access action frame, shall not update the EDCA parameters based on the information provided in beacons and/or probe responses from the AP, e.g., as described below.

[00153] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate a timer field, which may be included in the frame, for example, to indicate duration of the NS/EP service requested. This implementation may provide an efficient technical solution, for example, where STAs are not required to send unicast action frames to terminate NS/EP service each time.

[00154] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate periodicity of NS/EP data to be served, and/or an interval of service in each period. For example, a Target Wake Time (TWT) element may be included as part of signaling.

[00155] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate trigger-based service requested and/or EDCA-based service requested implementations .

[00156] In some demonstrative embodiments, the mechanism for NSEP priority access may facilitate use of a protected period and/or restricted TWT Service Periods (SPs).

[00157] In some demonstrative embodiments, controller 154 may be configured to trigger, cause, instruct and/or control device 140 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures, of an AP STA, e.g., as described below.

[00158] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set an Enhanced Distributed Channel Access (EDCA) parameter set element defining one or more EDCA parameters for National Security and Emergency Preparedness (NSEP) priority access for a non-AP STA, e.g., as described below.

[00159] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to transmit an NSEP priority access frame to enable NSEP priority access for the non-AP STA, wherein the NSEP priority access frame includes the EDCA parameter set element, e.g., as described below.

[00160] In some demonstrative embodiments, the NSEP priority access frame may include an NSEP priority access response frame, e.g., in response to an NSEP priority access request frame from the non-AP STA.

[00161] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to transmit the NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA, e.g., as described above.

[00162] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set a value of success in a status code field of the NSEP priority access response frame, e.g., as described above.

[00163] In some demonstrative embodiments, the NSEP priority access frame may include an unsolicited NSEP priority access request frame.

[00164] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to process an NSEP priority access response frame from the non-AP STA to confirm the unsolicited NSEP priority access request frame. For example, the NSEP priority access response frame from the non-AP STA may include a value of success in a status code field, e.g., as described above.

[00165] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to transmit an other frame defining one or more EDCA parameters for non-NSEP access for one or more other non-AP STAs, e.g., as described below.

[00166] In some demonstrative embodiments, the one or more EDCA parameters defined by the other frame may be different from the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

[00167] In some demonstrative embodiments, the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame may be configured to provide prioritized access relative to the EDCA parameters defined by the other frame.

[00168] In some demonstrative embodiments, the other frame may include a beacon frame or a probe response frame.

[00169] In some demonstrative embodiments, controller 124 may be configured to trigger, cause, instruct and/or control device 102 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures, of a non-AP STA, e.g., as described below. [00170] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process an NSEP priority access frame received from an AP STA.

[00171] In some demonstrative embodiments, the NSEP priority access frame received by the non-AP STA implemented by device 102 may include an EDCA parameter set element defining one or more EDCA parameters.

[00172] For example, the NSEP priority access frame received by the non-AP STA implemented by device 102 may include the NSEP priority access frame transmitted by the AP STA implemented by device 140, e.g., as described above.

[00173] In some demonstrative embodiments, the NSEP priority access frame received by the non-AP STA implemented by device 102 may include an NSEP priority access response frame.

[00174] For example, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit an NSEP priority access request frame to the AP STA, e.g., to the AP STA implemented by device 140. For example, the NSEP priority access frame received by the non-AP STA implemented by device 102 may be in response to the NSEP priority access request frame transmitted from the non-AP STA to the AP STA.

[00175] In some demonstrative embodiments, the NSEP priority access response frame include a value of success in a status code field, e.g., as described above.

[00176] In some demonstrative embodiments, the NSEP priority access frame received by the non-AP STA implemented by device 102 may include an unsolicited NSEP priority access request frame from the AP STA, e.g., the AP STA implemented by device 140.

[00177] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit an NSEP priority access response frame to the AP STA, for example, to confirm the unsolicited NSEP priority access request frame. [00178] In some demonstrative embodiments, the NSEP priority access response frame from the non-AP STA implemented by device 102 may include a value of success in a status code field, e.g., as described above.

[00179] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to update EDCA parameters of the non-STA according to the one or more EDCA parameters in the EDCA parameter set element from the AP STA, e.g., as described below.

[00180] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to communicate NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element.

[00181] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to select not to update the EDCA parameters of the non-AP STA based on EDCA parameters defined by one or more other frames from the AP STA.

[00182] In some demonstrative embodiments, controller 124 may be configured to disable the non-AP STA implemented by device 102 from updating the EDCA parameters of the non-AP STA based on EDCA parameters defined by the one or more other frames from the AP STA.

[00183] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to ignore EDCA parameters in the one or more other frames from the AP STA.

[00184] In some demonstrative embodiments, the one or more other frames from the AP STA may include, for example, a beacon frame, and/or a probe response frame. In other embodiments, the one or more other frames from the AP STA may include any other type frame, which may include, indicate, and/or define EDCA parameters.

[00185] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to set the EDCA parameters of the non-AP STA according to EDCA parameters defined by a beacon or probe response from the AP STA. [00186] For example, the non-AP STA implemented by device 102 may receive the beacon or probe response from the AP STA, for example, when the non-AP STA implemented by device 102 is not operating in an enabled NSEP priority access mode.

[00187] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to, based on receipt of the NSEP priority access frame from the AP STA, update the EDCA parameters of the non-AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

[00188] In some demonstrative embodiments, the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame from the AP STA may be configured, for example, to provide prioritized access, e.g., relative to the EDCA parameters defined by the beacon or probe response from the AP STA, e.g., as described above.

[00189] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to select not to update the EDCA parameters of the STA based on EDCA parameters defined by a subsequent beacon or probe response from the AP STA, which is received after the NSEP priority access frame.

[00190] In some demonstrative embodiments, controller 124 may be configured to disable the non-AP STA implemented by device 102 from updating the EDCA parameters of the STA based on EDCA parameters defined by the subsequent beacon or probe response from the AP STA.

[00191] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to ignore the on EDCA parameters defined by the subsequent beacon or probe response from the AP STA.

[00192] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to select not to update the EDCA parameters of the STA based on EDCA parameters defined by the subsequent beacon or probe response from the AP STA, which may be received when the non-AP STA implemented by device 102 is operating in the enabled NSEP priority access mode. [00193] In some demonstrative embodiments, an NSEP priority access request frame format may be defined to include an indication of one or more EDCA parameters, e.g., as described below.

[00194] In some demonstrative embodiments, the NSEP priority access request frame may be transmitted by a requesting STA to request a priority-access related action from another STA.

[00195] For example, the NSEP priority access request frame may be configured according to the following format of the NSEP priority access request frame action field:

Table 1

[00196] In some demonstrative embodiments, the Category field may be defined as an Action field.

[00197] In some demonstrative embodiments, the NSEP Action field may be defined, e.g., in accordance with a definition for NSEP priority access action frame details. [00198] In some demonstrative embodiments, the Dialog Token field may be set by the requesting STA.

[00199] In some demonstrative embodiments, the NSEP Request Type field may specify the particular action sought by the requesting STA. The format of the NSEP Request Type field may include a size of on octet. [00200] In some demonstrative embodiments, the NSEP Request Type field may be set according to the following definition of values :

Table 2

[00201] In some demonstrative aspects, the EDC A Parameter Set element may be included if the AP is the transmitter of the NSEP priority access request frame, e.g., as described above.

[00202] For example, controller 154 may be configured to cause the AP STA implemented by device 140 to include the EDC A Parameter Set element in the NSEP priority access request frame according to Table 1, e.g., as described above. [00203] In some demonstrative embodiments, an NSEP priority access response frame format may be defined to include an indication of one or more EDCA parameters, e.g., as described below.

[00204] In some demonstrative embodiments, the NSEP priority access response frame may be transmitted in response to an NSEP priority access request frame, e.g., as described above.

[00205] For example, the NSEP priority access response frame may be configured according to the following format of the NSEP priority access response frame action field:

Table 3

[00206] In some demonstrative embodiments, the Category field may be defined as an Action field.

[00207] In some demonstrative embodiments, the NSEP Action field may be defined, e.g., in accordance with a definition for NSEP Priority Access Action frame details.

[00208] In some demonstrative embodiments, the Dialog Token field value may be copied from the Dialog Token field in the corresponding NSEP priority access request frame.

[00209] In some demonstrative embodiments, the Status Code may be defined according to a plurality of predefined Status code values.

[00210] In some demonstrative aspects, the EDC A Parameter Set element may be included if the AP is the transmitter of the NSEP priority access response frame, e.g., as described above.

[00211] For example, controller 154 may be configured to cause the AP STA implemented by device 140 to include the EDC A Parameter Set element in the NSEP priority access response frame according to Table 3, e.g., as described above.

[00212] Reference is made to Fig. 3, which schematically illustrates a method of NSEP priority access, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 3 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).

[00213] As indicated at block 302, the method may include processing at a non-AP STA an NSEP priority access frame from an AP STA, the NSEP priority access frame including an EDCA parameter set element, the EDCA parameter set element defining one or more EDCA parameters. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to process the NSEP priority access frame from device 140, e.g., as described above.

[00214] As indicated at block 304, the method may include updating EDCA parameters of the non-AP STA according to the one or more EDCA parameters in the EDCA parameter set element. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to update EDCA parameters of the non-AP STA implemented by device 102 (Fig. 1) according to the one or more EDCA parameters in the EDCA parameter set element, e.g., as described above.

[00215] As indicated at block 306, the method may include communicating NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to communicate NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element, e.g., as described above.

[00216] Reference is made to Fig. 4, which schematically illustrates a method of NSEP priority access, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 4 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).

[00217] As indicated at block 402, the method may include setting at an AP STA an EDCA parameter set element defining one or more EDCA parameters for NSEP priority access for a non-AP STA. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to set the EDCA parameter set element defining one or more EDCA parameters for NSEP priority access for the non-AP STA implemented by device 102 (Fig. 1), e.g., as described above.

[00218] As indicated at block 404, the method may include transmitting from the AP STA an NSEP priority access frame to enable NSEP priority access for the non-AP STA, the NSEP priority access frame including the EDCA parameter set element. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to transmit the NSEP priority access frame to enable NSEP priority access for the non-AP STA, e.g., as described above.

[00219] Reference is made to Fig. 5, which schematically illustrates a product of manufacture 500, in accordance with some demonstrative embodiments. Product 500 may include one or more tangible computer-readable (“machine-readable”) non- transitory storage media 502, which may include computer-executable instructions, e.g., implemented by logic 504, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at device 102 (Fig. 1), device 140 (Fig. 1), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), and/or receiver 146 (Fig. 1); to cause device 102 (Fig. 1), device 140 (Fig. 1), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), and/or receiver 146 (Fig. 1) to perform, trigger and/or implement one or more operations and/or functionalities; and/or to perform, trigger and/or implement one or more operations and/or functionalities described with reference to the Figs. 1, 2, 3, and/or 4, and/or one or more operations described herein. The phrases “non-transitory machine-readable medium” and “computer-readable non-transitory storage media” may be directed to include all machine and/or computer readable media, with the sole exception being a transitory propagating signal.

[00220] In some demonstrative embodiments, product 500 and/or machine readable storage media 502 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine readable storage media 502 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide- silicon (SONOS) memory, a hard drive, an optical disk, a magnetic disk, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.

[00221] In some demonstrative embodiments, logic 504 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

[00222] In some demonstrative embodiments, logic 504 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

[00223] The following examples pertain to further embodiments. [00224] Example 1 includes an apparatus comprising logic and circuitry configured to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to process a National Security and Emergency Preparedness (NSEP) priority access frame from an AP STA, the NSEP priority access frame comprising an Enhanced Distributed Channel Access (EDC A) parameter set element, the EDC A parameter set element defining one or more EDCA parameters; update EDCA parameters of the non-AP STA according to the one or more EDCA parameters in the EDCA parameter set element; and communicate NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element.

[00225] Example 2 includes the subject matter of Example 1, and optionally, wherein the apparatus is configured to cause the non-AP STA to select not to update the EDCA parameters of the non-AP STA based on EDCA parameters defined by one or more other frames from the AP STA, the one or more other frames comprising at least one of a beacon frame or a probe response frame.

[00226] Example 3 includes the subject matter of Example 1 or 2, and optionally, wherein the apparatus is configured to cause the non-AP STA to ignore EDCA parameters in one or more other frames from the AP STA, the one or more other frames comprising at least one of a beacon frame or a probe response frame.

[00227] Example 4 includes the subject matter of any one of Examples 1-3, and optionally, wherein the apparatus is configured to cause the non-AP STA to set the EDCA parameters of the non-AP STA according to EDCA parameters defined by a beacon or probe response from the AP STA; and based on receipt of the NSEP priority access frame from the AP STA, update the EDCA parameters of the non-AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

[00228] Example 5 includes the subject matter of Example 4, and optionally, wherein the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame are configured to provide prioritized access relative to the EDCA parameters defined by the beacon or probe response from the AP STA.

[00229] Example 6 includes the subject matter of Example 4 or 5, and optionally, wherein the apparatus is configured to cause the non-AP STA to select not to update the EDCA parameters of the non-AP STA based on EDCA parameters defined by a subsequent beacon or probe response from the AP STA, which is received after the NSEP priority access frame.

[00230] Example 7 includes the subject matter of any one of Examples 1-6, and optionally, wherein the NSEP priority access frame comprises an NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA.

[00231] Example 8 includes the subject matter of Example 7, and optionally, wherein the NSEP priority access response frame comprises a value of success in a status code field.

[00232] Example 9 includes the subject matter of any one of Examples 1-6, and optionally, wherein the NSEP priority access frame comprises an unsolicited NSEP priority access request frame.

[00233] Example 10 includes the subject matter of Example 9, and optionally, wherein the apparatus is configured to cause the non-AP STA to transmit an NSEP priority access response frame to the AP STA to confirm the unsolicited NSEP priority access request frame, the NSEP priority access response frame comprising a value of success in a status code field.

[00234] Example 11 includes the subject matter of any one of Examples 1-10, and optionally, comprising a radio to communicate the NSEP priority access frame and the NSEP priority access traffic with the AP STA.

[00235] Example 12 includes the subject matter of Example 11, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the non-AP STA.

[00236] Example 13 includes an apparatus comprising logic and circuitry configured to cause an Access Point (AP) wireless communication station (STA) to set an Enhanced Distributed Channel Access (EDCA) parameter set element defining one or more EDCA parameters for National Security and Emergency Preparedness (NSEP) priority access for a non-AP STA; and transmit an NSEP priority access frame to enable NSEP priority access for the non-AP STA, the NSEP priority access frame comprising the EDCA parameter set element. [00237] Example 14 includes the subject matter of Example 13, and optionally, wherein the apparatus is configured to cause the AP STA to transmit an other frame defining one or more EDCA parameters for non-NSEP access for one or more other non-AP STAs, wherein the one or more EDCA parameters defined by the other frame are different from the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

[00238] Example 15 includes the subject matter of Example 14, and optionally, wherein the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame are configured to provide prioritized access relative to the EDCA parameters defined by the other frame.

[00239] Example 16 includes the subject matter of Example 14 or 15, and optionally, wherein the other frame comprises a beacon frame or a probe response frame.

[00240] Example 17 includes the subject matter of any one of Examples 13-16, and optionally, wherein the NSEP priority access frame comprises an NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA.

[00241] Example 18 includes the subject matter of Example 17, and optionally, wherein the apparatus is configured to cause the AP STA to set a value of success in a status code field of the NSEP priority access response frame.

[00242] Example 19 includes the subject matter of any one of Examples 13-16, and optionally, wherein the NSEP priority access frame comprises an unsolicited NSEP priority access request frame.

[00243] Example 20 includes the subject matter of Example 19, and optionally, wherein the apparatus is configured to cause the AP STA to process an NSEP priority access response frame from the non-AP STA to confirm the unsolicited NSEP priority access request frame, the NSEP priority access response frame comprising a value of success in a status code field.

[00244] Example 21 includes the subject matter of any one of Examples 13-20, and optionally, comprising a radio to transmit the NSEP priority access frame. [00245] Example 22 includes the subject matter of Example 21, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the AP STA.

[00246] Example 23 comprises an apparatus comprising means for executing any of the described operations of Examples 1-22.

[00247] Example 24 comprises a product comprising one or more tangible computer- readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a computing device to perform any of the described operations of Examples 1- 22.

[00248] Example 25 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of Examples 1-22.

[00249] Example 26 comprises a method comprising any of the described operations of Examples 1-22.

[00250] Functions, operations, components and/or features described herein with reference to one or more aspects, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other aspects, or vice versa.

[00251] While certain features have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Claims

CLAIMS What is claimed is:

1. An apparatus comprising logic and circuitry configured to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to: process a National Security and Emergency Preparedness (NSEP) priority access frame from an AP STA, the NSEP priority access frame comprising an Enhanced Distributed Channel Access (EDC A) parameter set element, the EDC A parameter set element defining one or more EDC A parameters; update EDCA parameters of the non-AP STA according to the one or more EDCA parameters in the EDCA parameter set element; and communicate NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element.

2. The apparatus of claim 1 configured to cause the non-AP STA to select not to update the EDCA parameters of the non-AP STA based on EDCA parameters defined by one or more other frames from the AP STA, the one or more other frames comprising at least one of a beacon frame or a probe response frame.

3. The apparatus of claim 1 configured to cause the non-AP STA to ignore EDCA parameters in one or more other frames from the AP STA, the one or more other frames comprising at least one of a beacon frame or a probe response frame.

4. The apparatus of claim 1 configured to cause the non-AP STA to: set the EDCA parameters of the non-AP STA according to EDCA parameters defined by a beacon or probe response from the AP STA; and based on receipt of the NSEP priority access frame from the AP STA, update the EDCA parameters of the non-AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

5. The apparatus of claim 4, wherein the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame are configured to provide prioritized access relative to the EDCA parameters defined by the beacon or probe response from the AP STA.

43

6. The apparatus of claim 4 configured to cause the non-AP STA to select not to update the EDCA parameters of the non-AP STA based on EDCA parameters defined by a subsequent beacon or probe response from the AP STA, which is received after the NSEP priority access frame.

7. The apparatus of any one of claims 1-6, wherein the NSEP priority access frame comprises an NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA.

8. The apparatus of claim 7, wherein the NSEP priority access response frame comprises a value of success in a status code field.

9. The apparatus of any one of claims 1-6, wherein the NSEP priority access frame comprises an unsolicited NSEP priority access request frame.

10. The apparatus of claim 9 configured to cause the non-AP STA to transmit an NSEP priority access response frame to the AP STA to confirm the unsolicited NSEP priority access request frame, the NSEP priority access response frame comprising a value of success in a status code field.

11. The apparatus of any one of claims 1-6 comprising a radio to communicate the NSEP priority access frame and the NSEP priority access traffic with the AP STA.

12. The apparatus of claim 11 comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the non-AP STA.

13. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to: process a National Security and Emergency Preparedness (NSEP) priority access frame from an AP STA, the NSEP priority access frame comprising an Enhanced Distributed Channel Access (EDCA) parameter set element, the EDCA parameter set element defining one or more EDCA parameters;

44 update EDCA parameters of the non-AP STA according to the one or more EDCA parameters in the EDCA parameter set element; and communicate NSEP priority access traffic with the AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element.

14. The product of claim 13, wherein the instructions, when executed, cause the non-AP STA to: set the EDCA parameters of the non-AP STA according to EDCA parameters defined by a beacon or probe response from the AP STA; and based on receipt of the NSEP priority access frame from the AP STA, update the EDCA parameters of the non-AP STA according to the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

15. The product of claim 13 or 14, wherein the NSEP priority access frame comprises an NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA.

16. The product of claim 13 or 14, wherein the NSEP priority access frame comprises an unsolicited NSEP priority access request frame.

17. An apparatus comprising logic and circuitry configured to cause an Access Point (AP) wireless communication station (STA) to: set an Enhanced Distributed Channel Access (EDCA) parameter set element defining one or more EDCA parameters for National Security and Emergency Preparedness (NSEP) priority access for a non-AP STA; and transmit an NSEP priority access frame to enable NSEP priority access for the non-AP STA, the NSEP priority access frame comprising the EDCA parameter set element.

18. The apparatus of claim 17 configured to cause the AP STA to transmit an other frame defining one or more EDCA parameters for non-NSEP access for one or more other non-AP STAs, wherein the one or more EDCA parameters defined by the other frame are different from the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.

45

19. The apparatus of claim 18, wherein the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame are configured to provide prioritized access relative to the EDCA parameters defined by the other frame.

20. The apparatus of any one of claims 17-19, wherein the NSEP priority access frame comprises an NSEP priority access response frame in response to an NSEP priority access request frame from the non-AP STA.

21. The apparatus of any one of claims 17-19, wherein the NSEP priority access frame comprises an unsolicited NSEP priority access request frame.

22. The apparatus of any one of claims 17-19 comprising a radio to transmit the NSEP priority access frame.

23. The apparatus of claim 22 comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the AP STA.

24. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause an Access Point (AP) wireless communication station (STA) to: set an Enhanced Distributed Channel Access (EDCA) parameter set element defining one or more EDCA parameters for National Security and Emergency Preparedness (NSEP) priority access for a non-AP STA; and transmit an NSEP priority access frame to enable NSEP priority access for the non-AP STA, the NSEP priority access frame comprising the EDCA parameter set element.

25. The product of claim 24, wherein the instructions, when executed, cause the AP STA to transmit an other frame defining one or more EDCA parameters for non- NSEP access for one or more other non-AP STAs, wherein the one or more EDCA parameters defined by the other frame are different from the one or more EDCA parameters defined by the EDCA parameter set element of the NSEP priority access frame.