Apparatus, system and method for transmitting unequal modulation and coding scheme information

Abstract

Apparatuses, systems, and methods of communicating unequal modulation and coding scheme information are disclosed. For example, an access point (AP) may be configured to set resource unit (RU) allocation information in a signal (SIG) field, the RU allocation information configured to indicate an RU allocation of a user; setting unequal modulation and coding scheme (MCS) (UEM) information of the user in the SIG field, the UEM information of the user configured to indicate an assignment of a plurality of frequency sub-channels in an RU assignment that assigns a plurality of MCSs to the user, respectively; and transmitting a downlink (DL) physical layer (PHY) protocol data unit (PPDU) including an SIG field and a data field of the user, where the data field of the user is configured according to an assignment of a plurality of frequency sub-channels in an RU allocation that assigns a plurality of MCSs to the user.

Description

Technical Field

[0001] Aspects described herein generally relate to transmitting unequal modulation and coding scheme (MCS) (UEM) information. Background Art

[0002] Devices in a wireless communication system may be configured to communicate according to communication protocols, which may utilize a modulation and coding scheme (MCS). BRIEF DESCRIPTION OF THE DRAWINGS

[0003] For simplicity and clarity of illustration, the elements shown in the drawings are not necessarily drawn to scale. For example, for clarity of presentation, the size of some elements may be exaggerated relative to other elements. In addition, reference numerals may be repeated between the drawings to indicate corresponding or similar elements. The drawings are listed below.

[0004] Figure 1 is a schematic block diagram illustration of a system according to some exemplary aspects.

[0005] Figure 2 is a schematic illustration of a user-specific field format according to some exemplary aspects.

[0006] Figure 3 is a schematic illustration of a user field format according to some exemplary aspects.

[0007] Figure 4 is a schematic illustration of a user-specific field format according to some exemplary aspects.

[0008] Figure 5 is a schematic illustration of a format of a user field used to identify one or more unequal modulation and coding scheme (MCS) (UEM) fields according to some demonstrative aspects.

[0009] Figure 6 is a schematic illustration of a user-specific field format according to some exemplary aspects.

[0010] Figure 7 is a schematic illustration of a UEM field format according to some exemplary aspects.

[0011] Figure 8 is a schematic flow chart illustration of a method of transmitting UEM information according to some exemplary aspects.

[0012] Fig. 9 is a schematic flow chart illustration of a method of transmitting UEM information according to some exemplary aspects.

[0013] Fig.10is a schematic illustration of an article of manufacture according to some exemplary aspects. DETAILED DESCRIPTION

[0014] In the following detailed description, many specific details are set forth to provide a thorough understanding of some aspects. However, it will be appreciated by those skilled in the art that some aspects may be implemented without these specific details. In other cases, well-known methods, processes, components, units, and / or circuits are not described in detail to avoid obscuring the present discussion.

[0015] Discussion herein utilizing terms such as “process,” “compute,” “calculate,” “determine,” “establish,” “analyze,” “examine,” and the like may refer to operations (or operations) and / or processes (or processes) of a computer, computing platform, 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 processing media that may store instructions to perform the operations and / or processes.

[0016] As used herein, the terms "plurality" and "plurality" include, for example, "multiple" or "two or more." For example, "a plurality of items" includes two or more items.

[0017] References to "one aspect," "an aspect," "exemplary aspects," "various aspects," etc. indicate that the aspect(s) described may include a particular feature, structure, or characteristic, but not every aspect necessarily includes the particular feature, structure, or characteristic. In addition, repeated use of the phrase "in one aspect" does not necessarily refer to the same aspect, although it may.

[0018] As used herein, unless otherwise indicated, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects simply indicates that different instances of similar objects are referenced and is not intended to imply that the objects so described must be in a given sequence in time, space, ranking, or in any other manner.

[0019] Some aspects may be used in conjunction with various devices and systems, for example, user equipment (UE), mobile device (MD), wireless station (STA), personal computer (PC), desktop computer, mobile computer, laptop computer, notebook computer, tablet computer, server computer, handheld computer, handheld device, wearable device, sensor device, Internet of Things (IoT) device, personal digital assistant (PDA) device, handheld PDA device, on-board device, off-board device, hybrid device, on-board device, off-board device, mobile or portable device, consumer device, non-mobile or non-portable device, wireless communication station, wireless communication device, wireless access point (AP), wired or wireless router, wired or wireless modem, video device, audio device, audio-visual (A / V) device, wired or wireless network, wireless area network, wireless video area network (WVAN), local area network (LAN), wireless LAN (Wireless LAN) LAN, WLAN), Personal Area Network (PAN), Wireless PAN (WPAN), and so on.

[0020] Some aspects may be used in conjunction with the following: in accordance with existing IEEE 802.11 standards (including IEEE 802.11-2020 (IEEE 802.11-2020, IEEE Standard for Information Technology--Intersystem Telecommunications and Information Exchange for Local and Metropolitan Area Networks--Specific Requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, December 2020); and / or IEEE 802.11be (IEEE Draft P802.11be / D3.1 Information technology standard - Intersystem telecommunications and information exchange for local and metropolitan area networks - Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment 8: Enhancements for Very High Throughput (EHT), March 2023)) and / or future versions and / or derivatives thereof, devices and / or networks operating in accordance with existing cellular specifications and / or protocols and / or future versions and / or derivatives thereof, units and / or devices as part of the above networks, etc.

[0021] Some aspects may be used in conjunction with: one-way and / or two-way radio communication systems, cellular radiotelephone communication systems, mobile phones, cellular phones, wireless phones, personal communication systems (PCS) devices, PDA devices including wireless communication devices, mobile or portable global positioning system (GPS) devices, devices including GPS receivers or transceivers or chips, devices including RFID elements or chips, multiple input multiple output (MIMO) transceivers or devices, single input multiple output (SIMO) transceivers or devices, multiple input single output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (e.g., smart phones), wireless application protocol (WAP) devices, and the like.

[0022] Some aspects may be used in conjunction with one or more types of wireless communication signals and / or systems, such as Radio Frequency (RF), Infra-Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Multi-User MIMO (MU-MIMO), Spatial Divisional 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 TM , Ultra-Wideband (UWB), 4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data rates for GSM Evolution (EDGE), etc. Other aspects may be used in various other devices, systems, and / or networks.

[0023] As used herein, the term "wireless device" 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, and the like. In some exemplary 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 exemplary aspects, the term "wireless device" may optionally include a wireless service.

[0024] The term "transmit" used herein for communication signals includes sending communication signals and / or receiving communication signals. For example, a communication unit capable of transmitting a communication signal may include a transmitter that sends a communication signal to at least one other communication unit, and / or a communication receiver that receives a communication signal from at least one other communication unit. The verb "transmit" can be used to refer to the action of sending or the action of receiving. In one example, the phrase "transmitting a signal" may refer to the action of sending a signal by a first device, and may not necessarily include the action of receiving a signal by a second device. In another example, the phrase "transmitting a signal" may refer to the action of receiving a signal by a first device, and may not necessarily include the action of sending a signal by a second device. The communication signal may be sent and / or received, for example, in the form of a radio frequency (RF) communication signal and / or any other type of signal.

[0025] As used herein, the term "circuit" may refer to, be a 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 executes one or more software or firmware programs, a combinational logic circuit, and / or other appropriate hardware components that provide the described functionality. In some aspects, some functions associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, the circuit may include logic that is at least partially operable in hardware.

[0026] The term "logic" may refer, for example, to computing logic embedded in the circuits of a computing device and / or computing logic stored in the memory of a computing device. For example, the logic may be accessed by a processor of a computing device to execute the computing logic to perform computing functions and / or operations. In one example, the logic may be embedded in various types of memory and / or firmware, such as silicon blocks of various chips and / or processors. The logic may be included in various circuits and / or implemented as part of various circuits, such as radio circuits, receiver circuits, control circuits, transmitter circuits, transceiver circuits, processor circuits, and the like. In one example, the 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. The logic may be executed by one or more processors using memory, such as registers, storage devices, buffers, and the like, which are coupled to one or more processors as needed to execute the logic.

[0027] Some exemplary aspects may be used in conjunction with a WLAN, such as a WiFi network. Other aspects may be used in conjunction with any other suitable wireless communication network, such as a wireless area network, a "piconet", a WPAN, a WVAN, and the like.

[0028] Some exemplary aspects may be used in conjunction with a wireless communication network that communicates in a sub-10 Gigahertz (GHz) frequency band, such as a 2.4 GHz frequency band, a 5 GHz frequency band, a 6 GHz frequency band, and / or any other frequency band below 10 GHz.

[0029] Some exemplary aspects may be used in conjunction with a wireless communication network that communicates on an Extremely High Frequency (EHF) band (also known as a "millimeter wave (mmWave)" band), for example, a band within a band between 20 GHz and 300 GHz, for example, a band above 45 GHz, for example, a 60 GHz band, and / or any other mmWave band. Some exemplary aspects may be used in conjunction with a wireless communication network that communicates on a sub-10 GHz band and / or a mmWave band, for example, as described below. However, other aspects may be implemented using any other suitable wireless communication band, for example, a 5G band, a band below 20 GHz, a sub-1 GHz (Sub1GHz, S1G) band, a WLAN band, a WPAN band, and the like.

[0030] Some exemplary aspects may be implemented by a mmWave STA (mSTA), which may, for example, include a STA having a radio transmitter capable of operating on a channel within a mmWave frequency band. In one example, mmWave communications may involve one or more directional links to communicate at a multi-gigabit per second rate, such as at least 1 gigabit per second, such as at least 7 gigabits per second, at least 30 gigabits per second, or any other rate.

[0031] In some exemplary aspects, the mmWave STA may include a Directional Multi-Gigabit (DMG) STA, which may be configured to communicate via a DMG frequency band. For example, the DMG frequency band may include a frequency band with a channel start frequency higher than 45 GHz.

[0032] In some exemplary aspects, the mmWave STA may include an Enhanced DMG (EDMG) STA, which may be configured to implement one or more mechanisms that may be configured to enable single-user (SU) and / or multi-user (MU) communications for downlink (DL) and / or uplink (UL) frames using a MIMO scheme. For example, the EDMG STA may be configured to implement one or more channel bonding mechanisms that may, for example, support communications over a channel bandwidth (BW) (also referred to as a "wide channel", "EDMG channel", or "bonded channel") comprising two or more channels (e.g., two or more 2.16 GHz channels). For example, the channel bonding mechanism may, for example, include a mechanism and / or operation by which two or more channels (e.g., 2.16 GHz channels) may be combined to, for example, obtain a higher bandwidth for packet transmission to enable a higher data rate, for example, when compared to transmission over a single channel. Some exemplary aspects are described herein for communication via a channel BW comprising two or more 2.16 GHz channels, however other aspects may be implemented for communication via a channel bandwidth (e.g., a "wide" channel) comprising any other number of two or more channels or formed by any other number of two or more channels, such as an aggregated channel comprising an aggregation of two or more channels. For example, an EDMG STA may be configured to implement one or more channel bonding mechanisms that, for example, may support an increased channel bandwidth, such as a channel BW of 4.32 GHz, a channel BW of 6.48 GHz, a channel BW of 8.64 GHz, and / or any other additional or alternative channel BW. The EDMG STA may perform other additional or alternative functions.

[0033] In other aspects, the mmWave STA may include any other type of STA and / or may perform other additional or alternative functions. Other aspects may be implemented by any other apparatus, device, and / or station.

[0034] As used herein, the term "antenna" may include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. In some aspects, an antenna may utilize separate transmit and receive antenna elements to implement transmit and receive functions. In some aspects, an antenna may utilize a common and / or integrated transmit / receive antenna element to implement transmit and receive functions. An antenna may include, for example, a phased array antenna, a single element antenna, a set of switched beam antennas, and the like.

[0035] refer to Figure 1 , which schematically illustrates a system 100 according to some exemplary aspects.

[0036] like Figure 1 As shown, in some demonstrative aspects, system 100 may include one or more wireless communication devices. For example, system 100 may include wireless communication device 102, wireless communication device 140, wireless communication device 160, and / or one or more other devices.

[0037] In some demonstrative aspects, devices 102, 140, and / or 160 may comprise mobile devices or non-mobile (eg, stationary) devices.

[0038] For example, devices 102, 140, and / or 160 may include, for example, UE, MD, STA, AP, PC, desktop computer, mobile computer, laptop computer, Ultrabook TMcomputer, laptop computer, tablet computer, server computer, handheld computer, Internet of Things (IoT) device, sensor device, handheld device, wearable device, PDA device, handheld PDA device, airborne device, non-airborne device, hybrid device (e.g., combining cellular phone functionality with PDA device functionality), consumer device, in-vehicle device, non-in-vehicle device, mobile or portable device, non-mobile or non-portable device, mobile phone, cellular phone, PCS device, PDA device including wireless communication device, mobile or portable GPS device, DVB device, relatively small computing device, non-desktop computer, "Carry Small Live Large" (CSLL) device, Ultra Mobile Device (UMD), Ultra Mobile PC (UMPC), Mobile Internet Device (MID), "Origami" device or computing device, dynamically composable computing (Dynamically Composable) Computing (DCC) devices, context-aware devices, video devices, audio devices, A / V devices, Set-Top-Box (STB), Blu-ray disc (BD) player, BD recorder, Digital Video Disc (DVD) player, High Definition (HD) DVD player, DVD recorder, HDDVD recorder, Personal Video Recorder (PVR), broadcast HD receiver, video source, audio source, video sink, audio sink, stereo tuner, broadcast radio receiver, flat panel display, personal media player (PMP), digital video camera (DVC), digital audio player, speaker, audio receiver, audio amplifier, gaming device, data source, data sink, digital still camera (DSC), media player, smart phone, television, music player, etc.

[0039] In some exemplary aspects, device 102 may include, for example, one or more of processor 191, input unit 192, output unit 193, memory unit 194, and / or storage unit 195; and / or device 140 may include, for example, one or more of processor 181, input unit 182, output unit 183, memory unit 184, and / or storage unit 185. Devices 102 and / or 140 may optionally include other suitable hardware components and / or software components. In some exemplary aspects, some or all 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 aspects, components of one or more of devices 102 and / or 140 may be distributed between multiple or separate devices.

[0040] In some exemplary aspects, 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 multi-core processor, a microprocessor, a host processor, a controller, multiple processors or controllers, a chip, a microchip, one or more circuits, circuits, logic units, integrated circuits (ICs), application-specific ICs (ASICs), or any other suitable multi-purpose or special-purpose processor or controller. Processor 191 may execute instructions of, for example, an operating system (OS) of device 102 and / or one or more suitable applications. Processor 181 may execute instructions of, for example, an operating system (OS) of device 140 and / or one or more suitable applications.

[0041] In some exemplary aspects, 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 trackball, a stylus, a microphone, or other suitable pointing devices or input devices. Output unit 193 and / or output unit 183 may include, for example, a monitor, a screen, a touch screen, a flat panel display, a light emitting diode (LED) display unit, a liquid crystal display (LCD) display unit, a plasma display unit, one or more audio speakers or headphones, or other suitable output devices.

[0042] In some exemplary aspects, memory unit 194 and / or memory unit 184 may include, for example, random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffer, short-term memory unit, long-term memory unit, or other suitable memory unit. 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 unit. 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.

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

[0044] In some exemplary aspects, WM 103 may include one or more wireless communication bands and / or channels. For example, WM 103 may include one or more channels in a sub-10 GHz wireless communication band (e.g., a 2.4 GHz wireless communication band), one or more channels in a 5 GHz wireless communication band, and / or one or more channels in a 6 GHz wireless communication band. In another example, WM 103 may additionally or alternatively include one or more channels in a mmWave wireless communication band. In other aspects, WM 103 may include any other type of channel on any other band.

[0045] In some demonstrative aspects, device 102, device 140, and / or device 160 may include one or more radios including circuitry and / or logic to perform wireless communications between devices 102, 140, 160, and / or one or more other wireless communication devices. For example, device 102 may include one or more radios 114, and / or device 140 may include one or more radios 144.

[0046] In some exemplary aspects, radio 114 and / or radio 144 may include one or more wireless receivers (Rx) that include 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.

[0047] In some exemplary aspects, radios 114 and / or 144 may include one or more wireless transmitters (Tx) that include circuitry and / or logic to transmit wireless communication signals, RF signals, frames, blocks, transport 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.

[0048] In some exemplary aspects, radios 114 and / or 144, transmitters 118 and / or 148, and / or receivers 116 and / or 146 may include circuits; logic; radio frequency (RF) components, circuits, and / or logic; baseband components, circuits, and / or logic; modulation components, circuits, and / or logic; demodulation components, circuits, and / or logic; amplifiers; analog-to-digital and / or digital-to-analog converters; filters; etc. For example, radios 114 and / or 144 may include or may be implemented as part of a wireless network interface card (NIC), etc.

[0049] In some exemplary aspects, radios 114 and / or 144 may be configured to communicate on a 2.4 GHz band, a 5 GHz band, a 6 GHz band, and / or any other band, e.g., a directional band such as a mmWave band, a 5G band, an S1G band, and / or any other band.

[0050] In some demonstrative aspects, radios 114 and / or 144 may include or may be associated with one or more antennas.

[0051] In some demonstrative aspects, device 102 may include one or more antennas 107 and / or device 140 may include one or more antennas 147 .

[0052] Antennas 107 and / or 147 may include any type of antenna 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. In some aspects, antennas 107 and / or 147 may utilize separate transmit and receive antenna elements to implement transmit and receive functions. In some aspects, antennas 107 and / or 147 may utilize common and / or integrated transmit / receive elements to implement transmit and receive functions.

[0053] In some demonstrative aspects, device 102 may include controller 124, and / or device 140 may include controller 154. Controller 124 may be configured to perform and / or trigger, cause, instruct, and / or control device 102 to perform one or more communications to generate and / or transmit one or more messages and / or transmissions, and / or perform one or more functions, operations, and / or processes between devices 102, 140, 160, and / or one or more other devices; and / or controller 154 may be configured to perform and / or trigger, cause, instruct, and / or control device 140 to perform one or more communications to generate and / or transmit one or more messages and / or transmissions, and / or perform one or more functions, operations, and / or processes between devices 102, 140, 160, and / or one or more other devices, e.g., as described below.

[0054] In some exemplary aspects, controllers 124 and / or 154 may include or may be partially or fully implemented by, for example, circuits and / or logic including one or more processors, memory circuits and / or logic, Media-Access Control (MAC) circuits and / or logic, Physical Layer (PHY) circuits and / or logic, baseband (BB) circuits and / or logic, BB processors, BB memory, Application Processor (AP) circuits and / or logic, AP processors, AP memory, and / or any other circuits and / or logic configured to respectively perform the functions of controllers 124 and / or 154. Additionally or alternatively, one or more functions of controllers 124 and / or 154 may be implemented by logic that may be executed by a machine and / or one or more processors, for example, as described below.

[0055] In one example, the controller 124 may include circuits and / or logic, such as one or more processors including circuits 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 the device 102) to perform, for example, one or more operations, communications, and / or functions described herein. In one example, the controller 124 may include at least one memory, for example, coupled to one or more processors, which may be configured to, for example, at least temporarily store at least some information processed by one or more processors and / or circuits, and / or may be configured to store logic to be utilized by the processors and / or circuits.

[0056] In one example, the controller 154 may include circuits and / or logic, such as one or more processors including circuits 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, for example, one or more operations, communications, and / or functions described herein. In one example, the controller 154 may include at least one memory, for example, coupled to one or more processors, which may be configured to, for example, at least temporarily store at least some information processed by one or more processors and / or circuits, and / or may be configured to store logic to be utilized by the processors and / or circuits.

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

[0058] In other aspects, 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 .

[0059] In some demonstrative aspects, device 102 may include a message processor 128 configured to generate, process, and / or access one or more messages transmitted by device 102 .

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

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

[0062] In some demonstrative aspects, device 140 may include a message processor 158 configured to generate, process, and / or access one or more messages transmitted by device 140 .

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

[0064] In one example, the message processor 158 may include at least one first component configured to generate a message, for example, in the form of a frame, a field, an information element, and / or a protocol data unit, such as an MPDU; at least one second component configured to convert the message into a PPDU, for example, by processing the message generated by the at least one first component, for example, by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message; and / or at least one third component configured to cause the message to be transmitted on a wireless communication medium, for example, on a wireless communication channel in a wireless communication frequency band, for example, by applying one or more transmit waveforms to one or more fields of the PPDU. In other aspects, the message processor 158 may be configured to perform any other additional or alternative functions and / or may include any other additional or alternative components to generate and / or process the message to be transmitted.

[0065] In some demonstrative aspects, message processors 128 and / or 158 may include or may be partially or fully implemented by, for example, circuits and / or logic including one or more processors, memory circuits and / or logic, MAC circuits and / or logic, PHY circuits and / or logic, BB circuits and / or logic, BB processors, BB memories, AP circuits and / or logic, AP processors, AP memories, and / or any other circuits and / or logic configured to respectively perform the functions of message processors 128 and / or 158. Additionally or alternatively, one or more functions of message processors 128 and / or 158 may be implemented by logic that may be executed by a machine and / or one or more processors, e.g., as described below.

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

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

[0068] In other aspects, 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 .

[0069] In some exemplary aspects, at least a portion of the functionality of the controller 124 and / or the message processor 128 may be implemented by an integrated circuit, e.g., a chip, such as a system on chip (SoC). In one example, the chip or SoC may be configured to perform one or more functions of the one or more radios 114. For example, the chip or SoC may include one or more elements of the controller 124, one or more elements of the message processor 128, and / or one or more elements of the one or more radios 114. In one example, the controller 124, the message processor 128, and the one or more radios 114 may be implemented as part of a chip or SoC.

[0070] In other aspects, controller 124 , message processor 128 , and / or one or more radios 114 may be implemented by one or more additional or alternative elements of device 102 .

[0071] In some exemplary aspects, at least a portion of the functionality of controller 154 and / or message processor 158 may be implemented by an integrated circuit, e.g., a chip, such as a SoC. In one example, the chip or SoC may be configured to perform one or more functions of one or more radios 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 one or more radios 144. In one example, controller 154, message processor 158, and one or more radios 144 may be implemented as part of a chip or SoC.

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

[0073] In some demonstrative aspects, device 102, device 140, and / or device 160 may include one or more STAs, operate as one or more STAs, function as one or more STAs, and / or perform one or more functions of one or more STAs. For example, device 102 may include at least one STA, device 140 may include at least one STA, and / or device 160 may include at least one STA.

[0074] In some demonstrative aspects, the device 102, the device 140, and / or the device 160 may include one or more Extremely High Throughput (EHT) STAs, operate as one or more EHT STAs, function as one or more EHT STAs, and / or perform one or more functions of one or more EHT STAs. For example, the device 102 may include one or more EHT STAs, operate as one or more EHT STAs, function as one or more EHT STAs, and / or perform one or more functions of one or more EHT STAs, and / or the device 140 may include one or more EHT STAs, operate as one or more EHT STAs, function as one or more EHT STAs, and / or perform one or more functions of one or more EHT STAs.

[0075] In some demonstrative aspects, for example, device 102, device 140, and / or device 160 may be configured to perform one or more operations and / or functions of a WiFi 8 STA.

[0076] In other aspects, for example, the devices 102, 140, and / or 160 may be configured to perform one or more operations and / or functions of an Ultra High Reliability (UHR) STA.

[0077] In other aspects, for example, devices 102, 140, and / or 160 may be configured to perform one or more operations and / or functions of any other additional or alternative types of STAs.

[0078] In other aspects, device 102, device 140, and / or device 160 may include any other wireless device and / or station, operate as any other wireless device and / or station, function as any other wireless device and / or station, and / or perform one or more functions of any other wireless device and / or station, such as a WLAN STA, a WiFi STA, and the like.

[0079] In some exemplary aspects, device 102, device 140, and / or device 160 may be configured to operate as an access point (AP), function as an AP, and / or perform one or more functions of an AP, where the AP is, for example, a high throughput (HT) AP STA, a high efficiency (HE) AP STA, an EHT AP STA, and / or a UHR AP STA.

[0080] In some demonstrative aspects, the device 102, the device 140, and / or the device 160 may be configured to operate as a non-AP STA, function as a non-AP STA, and / or perform one or more functions of a non-AP STA, where the non-AP STA is, for example, a HT non-AP STA, a HE non-AP STA, an EHT non-AP STA, and / or a UHR non-AP STA.

[0081] In other aspects, device 102, device 140, and / or device 160 may operate as, function as, and / or perform one or more functions of any other additional or alternative devices and / or stations.

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

[0083] In one example, an AP may include an entity that includes a station (STA) and provides access to a distribution service for associated STAs via a wireless medium (WM). The AP may include a STA and a distribution system access function (DSAF). The AP may perform any other additional or alternative functions.

[0084] In some demonstrative aspects, devices 102, 140, and / or 160 may be configured to communicate in a HT network, a HE network, an EHT network, a UHR network, and / or any other network.

[0085] In some exemplary aspects, devices 102, 140, and / or 160 may be configured to operate in accordance with one or more specifications, including, for example, one or more IEEE 802.11 specifications, such as the IEEE 802.11-2020 specification, the IEEE 802.11ax specification, and / or any other specifications and / or protocols.

[0086] In some demonstrative aspects, device 102 may comprise an AP STA, operate as an AP STA, function as an AP STA, and / or perform functions of an AP STA.

[0087] In some exemplary aspects, the device 140 and / or the device 160 may include one or more non-AP STAs, operate as one or more non-AP STAs, play the role of one or more non-AP STAs, and / or perform the functions of one or more non-AP STAs. For example, the device 140 may include at least one non-AP STA, operate as at least one non-AP STA, play the role of at least one non-AP STA, and / or perform the functions of at least one non-AP STA, and / or the device 160 may include at least one non-AP STA, operate as at least one non-AP STA, play the role of at least one non-AP STA, and / or perform the functions of at least one non-AP STA.

[0088] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to communicate according to a resource allocation mechanism that may assign resource units (RU) or multiple resource units (MRU) to a user (also referred to as a “user STA”), for example, as described below.

[0089] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to communicate according to a resource allocation mechanism that may support assigning RU / MRU to users using the same (e.g., equal) modulation and coding scheme (MCS), for example, as described below.

[0090] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to communicate according to a resource allocation mechanism that may support assigning RU / MRUs to users using multiple different (e.g., unequal) MCSs, for example, as described below.

[0091] In some exemplary aspects, for example, in some implementations, scenarios, use cases, and / or deployments, there may be one or more technical issues in implementations of assigning RUs or MRUs to users utilizing the same MCS (e.g., the same across the entire RU / MRU assigned to the user).

[0092] For example, when the RU assigned to a user spans primary and secondary channels, utilizing the same MCS for the entire assigned RU / MRU may result in low throughput.

[0093] For example, using the same MCS for the entire assigned RU / MRU may result in low throughput, for example, because the primary channel and the secondary channel may use different clear channel assessment (CCA) methods, signal detection CCA, and / or energy detection CCA, which may have different sensitivities for different channels. For example, on a 20 MHz primary channel and a 20 MHz secondary channel, the sensitivity thresholds may be -82 decibel-milliwatt (dBm) (signal detection CCA) and / or -62 dBm (energy detection CCA), respectively. For example, using different CCA methods for the primary channel and the secondary channel may result in a severe signal-to-noise ratio (SNR) imbalance between the primary channel and the secondary channel.

[0094] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an MCS allocation scheme (also referred to as an "unequal MCS allocation scheme") that may be configured to assign multiple MCSs to multiple different segments of a RU / MRU, for example, including two or more different MCSs, for example, as described below.

[0095] In some exemplary aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support assigning different MCSs to different segments of a RU / MRU, for example, when these segments have significant variations in SNR, for example, in order to adapt to their SNR conditions and / or achieve high throughput, for example, as described below.

[0096] In some demonstrative aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support the allocation of unequal MCS across spatial streams, e.g., as described below.

[0097] For example, unequal MCS across spatial streams may be configured to provide a technical solution to support Multiple-Input-Multiple-Output (MIMO), for example, where MIMO gain is different across different spatial streams, resulting in various SNR conditions.

[0098] In some demonstrative aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support assigning unequal MCSs across multiple frequency subchannels, e.g., as described below.

[0099] In some demonstrative aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support the assignment of unequal MCS across multiple spatial streams, e.g., as described below.

[0100] In some demonstrative aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support the assignment of unequal MCSs across multiple frequency subchannels and multiple spatial streams, e.g., as described below.

[0101] In some demonstrative aspects, an unequal MCS allocation scheme may be configured to support unequal MCS on multiple frequency channels, on multiple spatial streams, and / or on both frequency channels and spatial streams, e.g., in downlink (DL) transmissions, e.g., as described below.

[0102] In some exemplary aspects, the unequal MCS allocation scheme may include applying unequal MCS, for example, when a relatively large RU / MRU and / or a RU / MRU across primary and secondary channels is assigned to a user. For example, a relatively large RU / MRU may be split into multiple sub-RU / MRUs, and an MCS may be assigned to some or all of the sub-RU / MRUs, for example, to each sub-RU / MRU, based on an SNR level of one or more sub-RU / MRUs. For example, for a 40MHz RU, two MCSs may be assigned to two 20MHz sub-RUs, for example, based on the SNR levels of the sub-RU / MRUs.

[0103] In some exemplary aspects, for example, when MIMO technology is applied, MIMO gains may be different, for example, significantly different, on different spatial streams.

[0104] In some exemplary aspects, it may be desirable to provide a technical solution to support signaling of unequal MCS assignments. For example, some signaling fields, such as the EHT signal (SIG) EHT-SIG defined according to the IEEE 802.11be specification, may only support assigning a single MCS to each user.

[0105] In some demonstrative aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support signaling of unequal MCS assignments across multiple frequency subchannels and / or spatial streams, e.g., as described below.

[0106] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism, which may be configured to support signaling of unequal MCS assignments across multiple frequency subchannels and / or spatial streams, e.g., as described below.

[0107] In some exemplary aspects, the unequal MCS signaling mechanism may be configured to implement a technical scheme configured to support the use of unequal MCS on multiple frequency subchannels and / or on both multiple frequency subchannels and spatial streams, for example, in accordance with the IEEE 802.11be specification, for example, as described below.

[0108] In some demonstrative aspects, an unequal MCS signaling mechanism may utilize one or more user-specific fields for unequal MCS across multiple frequency subchannels, eg, where MIMO is not applied, eg, as described below.

[0109] In some exemplary aspects, an unequal MCS signaling mechanism may utilize one or more user-specific fields, for example, according to a new user-specific field format, which may be configured to implement unequal MCS on both frequency subchannels and spatial streams, for example, where MIMO is applied, for example, as described below.

[0110] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set RU allocation information in a SIG field, e.g., as described below.

[0111] In some demonstrative aspects, the RU allocation information may be configured to indicate RU allocations for users (also referred to as "user STAs"), e.g., as described below.

[0112] In some exemplary aspects, the users may include users capable of supporting unequal MCS assignments (also referred to as "unequal MCS users" or "UEM users"), as described below.

[0113] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set unequal MCS (UEM) information of a user (UEM user) in a SIG field, e.g., as described below.

[0114] In some demonstrative aspects, the user's UEM information may be configured to indicate an assignment of multiple MCSs to multiple frequency subchannels in the user's RU allocation, respectively, e.g., as described below.

[0115] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to send a DL PPDU including a SIG field and a user (UEM user) data field, e.g., as described below.

[0116] In some demonstrative aspects, the data field for the UEM user may be configured, for example, according to an assignment of multiple frequency subchannels in a RU allocation that assigns multiple MCSs to the UEM user, e.g., as described below.

[0117] In some demonstrative aspects, the SIG field may include an EHT-SIG field.

[0118] In other aspects, the SIG field may include any other type of field.

[0119] In some demonstrative aspects, a DL PPDU may include a MU PPDU for multiple users including a UE M user, e.g., as described below.

[0120] In some demonstrative aspects, the DL PPDU may include a SU PPDU for a UE M user, e.g., as described below.

[0121] In some demonstrative aspects, the DL PPDU may comprise an EHT DL PPDU, e.g., as described below.

[0122] In some demonstrative aspects, the DL PPDU may comprise a UHR DL PPDU, e.g., as described below.

[0123] In other aspects, the DL PPDU may include any other type of PPDU.

[0124] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a user field for a user and at least one UEM field for a user in a SIG field, e.g., as described below.

[0125] In some demonstrative aspects, a user field of a user may be configured to indicate that the user is a UEM user with a UEM designation, e.g., as described below.

[0126] In some demonstrative aspects, at least one UEM field of the UEM user may be configured to include UEM information of the UEM user, e.g., as described below.

[0127] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a predefined MCS type value in an MCS type subfield in a user field of a user, e.g., as described below.

[0128] In some demonstrative aspects, the predefined MCS type value may be configured to indicate that the user is a UEM user with a UEM assignment, e.g., as described below.

[0129] In some demonstrative aspects, the predefined MCS type value may be configured to indicate a type of UEM assignment from among a plurality of predefined UEM assignment types, e.g., as described below.

[0130] In some demonstrative aspects, the plurality of predefined UEM assignment types may include at least one of UEM assignments on frequency subchannels, UEM assignments on spatial streams, or UEM assignments on both frequency subchannels and spatial streams, e.g., as described below.

[0131] In other aspects, the plurality of predefined UEM assignment types may include any other additional or alternative UEM assignment types.

[0132] In some demonstrative aspects, the MCS type subfield may have a size of 2 bits.

[0133] In other aspects, the MCS type subfield may have any other size.

[0134] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a UEM field indicator subfield in a user field of a user, e.g., as described below.

[0135] In some demonstrative aspects, the UEM field indicator subfield may be configured to indicate a position of a first UEM field of at least one UEM field of a user in the SIG field, e.g., as described below.

[0136] In some demonstrative aspects, at least one UEM field of a user may be configured, for example, according to a UEM field format including a plurality of MCS subfields, e.g., as described below.

[0137] In some demonstrative aspects, a first-order UEM field in at least one UEM field of a user may include a frequency fragment subfield configured to indicate a partitioning of a RU allocation of the user into a plurality of frequency subchannels, e.g., as described below.

[0138] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a spatial configuration subfield in a user field of a user to indicate an assignment of multiple spatial streams to the user, e.g., as described below.

[0139] In some demonstrative aspects, the user's UEM information may be configured to indicate an assignment of multiple MCSs to multiple spatial streams on multiple frequency subchannels, e.g., as described below.

[0140] In some demonstrative aspects, the at least one UEM field for the user may include a plurality of UEM fields for the user, e.g., as described below.

[0141] In some demonstrative aspects, a UEM field in the plurality of UEM fields for a user may include frequency channel-specific UEM information corresponding to a frequency subchannel in the plurality of frequency subchannels, e.g., as described below.

[0142] In some demonstrative aspects, the frequency channel-specific UE M information may include a plurality of frequency channel-specific MCSs for a plurality of spatial streams on a frequency subchannel, e.g., as described below.

[0143] In some demonstrative aspects, the at least one UEM field for the user may include at least a first UEM field and a second UEM field, e.g., as described below.

[0144] In some demonstrative aspects, the first UEM field may include a first plurality of MCSs for a plurality of spatial streams on a first frequency subchannel, e.g., as described below.

[0145] In some demonstrative aspects, the second UEM field may include a second plurality of MCSs for the plurality of spatial streams on the second frequency subchannel, e.g., as described below.

[0146] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a predefined MCS index in an MCS subfield in a user field of a user, e.g., as described below.

[0147] In some demonstrative aspects, the predefined MCS index may be configured to indicate that the user is a UEM user with a UEM assignment, e.g., as described below.

[0148] In some exemplary aspects, the predefined MCS index may include MCS index 14.

[0149] In other aspects, the predefined MCS index may include any other MCS index.

[0150] In some demonstrative aspects, at least one UEM field of a user may be configured, e.g., according to a UEM field format, e.g., as described below.

[0151] In some demonstrative aspects, the UEM field format may be configured to include a STA identifier (ID) (STA-ID) field used to identify a user and a plurality of MCS subfields following the STA-ID field, e.g., as described below.

[0152] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set a spatial configuration subfield in a user field of a user, e.g., to indicate an assignment of multiple spatial streams to the user, e.g., as described below.

[0153] In some demonstrative aspects, the user's UEM information may be configured to indicate an assignment of multiple MCSs to multiple spatial streams on multiple frequency subchannels, e.g., as described below.

[0154] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to encode at least one UEM field of a user into one or more UEM encoding blocks, e.g., according to a UEM encoding block format, e.g., as described below.

[0155] In some demonstrative aspects, the UEM encoding block format may be configured to include a UEM encoding block including two UEM fields, e.g., as described below.

[0156] In some demonstrative aspects, the UEM coded block format may be configured to include a cyclic redundancy check (CRC) field, for example, based on the two UEM fields, for example, as described below.

[0157] In some demonstrative aspects, at least one UE M field for a user may be located after all user fields in a SIG field, e.g., as described below.

[0158] In other aspects, the at least one UEM field for the user may be located at any other position in the SIG field.

[0159] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set the user's UEM information in a plurality of user fields of the user in the SIG field, e.g., as described below.

[0160] In some demonstrative aspects, the multiple user fields of a user may be configured to indicate multiple MCSs of unequal MCS assignments, respectively, e.g., as described below.

[0161] In some exemplary aspects, a user field among a plurality of user fields for a user may include a STA-ID field including a STA-ID used to identify the user, and an MCS field including an MCS among a plurality of MCSs, for example, as described below.

[0162] In some exemplary aspects, each of the plurality of user fields for a user may include the same STA-ID to identify the user, eg, as described below.

[0163] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set RU allocation information to indicate allocation of multiple sub-RUs to a user, e.g., as described below.

[0164] In some demonstrative aspects, a plurality of sub-RUs of a user may be configured to respectively include a plurality of frequency sub-channels, e.g., as described below.

[0165] In some exemplary aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by the device 102 to set multiple user fields for a user to indicate multiple MCSs, for example, based on an order of multiple frequency subchannels in a RU allocation for the user, for example, as described below.

[0166] In some demonstrative aspects, a first-order user field among a plurality of user fields for a user may include a STA-ID field, an MCS field following the STA-ID field, and a spatial configuration field following the MCS field, e.g., as described below.

[0167] In some demonstrative aspects, a non-first-order user field in a plurality of user fields for a user may include one or more MCS fields, e.g., while excluding a STA-ID field, e.g., as described below.

[0168] In some demonstrative aspects, the bit size of a user field in a plurality of user fields for a user may be equal to a predefined bit size of a user field for a user with a single MCS assignment (also referred to as a "non-UEM user"), e.g., as described below.

[0169] In some exemplary aspects, a user field in the plurality of user fields for a user may have a bit size of 22 bits.

[0170] In other aspects, the user field for a user may have any other bit size.

[0171] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify the RU allocation of the user STA, for example, based on the RU allocation information in the SIG field of the DLPPDU received by the user STA implemented by the device 140, for example, as described below.

[0172] In some demonstrative aspects, the received DL PPDU may comprise a DL PPDU sent by an AP (eg, an AP implemented by device 102).

[0173] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to process the UEM information of the user STA in the SIG field, for example, to identify the assignment of multiple frequency subchannels in an RU allocation that assigns multiple MCSs to the user STA, respectively, for example, as described below.

[0174] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to process a data field of the user STA in a DL PPDU, for example, based on an assignment of multiple frequency subchannels in an RU allocation that assigns multiple MCSs to the user STA, for example, as described below.

[0175] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify a user field of the user STA and at least one UEM field of the user STA in the SIG field, e.g., as described below.

[0176] In some demonstrative aspects, the user field of the user STA may be configured to indicate that the user STA is a UEM user STA with a UEM designation, e.g., as described below.

[0177] In some demonstrative aspects, at least one UEM field of a user STA may include UEM information of the user STA, e.g., as described below.

[0178] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by device 140 to recognize a predefined MCS type value in an MCS type subfield in a user field of the user STA, e.g., as described below.

[0179] In some demonstrative aspects, the predefined MCS type value may indicate that the user STA is a UEM user STA with a UEM assignment, e.g., as described below.

[0180] In some demonstrative aspects, the predefined MCS type value may be configured to indicate a type of UEM assignment from among a plurality of predefined UEM assignment types, e.g., as described below.

[0181] In some demonstrative aspects, the plurality of predefined UEM assignment types may include at least one of UEM assignments on frequency subchannels, UEM assignments on spatial streams, or UEM assignments on both frequency subchannels and spatial streams, e.g., as described below.

[0182] In some demonstrative aspects, the MCS type subfield may have a size of 2 bits.

[0183] In other aspects, the MCS type subfield may have any other size.

[0184] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by device 140 to identify a UEM field indicator subfield in a user field of the user STA, e.g., as described below.

[0185] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify a position of a first UEM field of at least one UEM field of the user STA in the SIG field, for example, based on a UEM field indicator subfield, for example, as described below.

[0186] In some demonstrative aspects, at least one UEM field of a user STA may be configured, for example, according to a UEM field format that includes a plurality of MCS subfields, e.g., as described below.

[0187] In some demonstrative aspects, a first-order UEM field in at least one UEM field of a user STA may include a frequency fragment subfield configured to indicate a division of a RU allocation of the user STA into multiple frequency subchannels, for example, as described below.

[0188] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by device 140 to identify a spatial configuration subfield in a user field of the user STA.

[0189] In some demonstrative aspects, the spatial configuration subfield in the user field of the user STA may be configured to indicate the assignment of multiple spatial streams for the user STA, e.g., as described below.

[0190] In some demonstrative aspects, the UEM information of the user STA may be configured to indicate an assignment of multiple MCSs to multiple spatial streams on multiple frequency subchannels, e.g., as described below.

[0191] In some demonstrative aspects, the at least one UEM field of the user STA may include a plurality of UEM fields of the user STA, e.g., as described below.

[0192] In some demonstrative aspects, a UEM field of the plurality of UEM fields of the user STA may include frequency channel-specific UEM information corresponding to a frequency subchannel of the plurality of frequency subchannels, e.g., as described below.

[0193] In some demonstrative aspects, the frequency channel-specific UE M information may include a plurality of frequency channel-specific MCSs for a plurality of spatial streams on a frequency subchannel, e.g., as described below.

[0194] In some demonstrative aspects, the at least one UEM field of the user STA may include a first UEM field and a second UEM field, e.g., as described below.

[0195] In some demonstrative aspects, the first UEM field may include a first plurality of MCSs for multiple spatial streams on a first frequency subchannel, and the second UEM field may include a second plurality of MCSs for multiple spatial streams on a second frequency subchannel, e.g., as described below.

[0196] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify a predefined MCS index in an MCS subfield in a user field of the user STA, and identify that the user STA has a UEM assignment based on the predefined MCS index, for example, as described below.

[0197] In some exemplary aspects, the predefined MCS index may be 14.

[0198] In other aspects, the predefined MCS index may include any other MCS index.

[0199] In some demonstrative aspects, at least one UEM field of a user STA may be configured, for example, according to a UEM field format including a STA-ID field used to identify the user STA and a plurality of MCS subfields following the STA-ID field, for example, as described below.

[0200] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify an assignment of multiple spatial streams for the user STA, for example, based on a spatial configuration subfield in a user field of the user STA, for example, as described below.

[0201] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify an assignment of multiple MCSs to multiple spatial streams on multiple frequency subchannels, for example based on UEM information of the user STA, for example, as described below.

[0202] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify at least one UEM field of the user STA by, for example, processing one or more UEM coding blocks according to a UEM coding block format, the format including a UEM coding block including two UEM fields and a CRC field based on the two UEM fields, for example, as described below.

[0203] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify at least one UE M field of the user STA located after all user fields in the SIG field, e.g., as described below.

[0204] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify the UE M information of the user STA in a plurality of user fields of the user STA in the SIG field. For example, the plurality of user fields of the user STA may be configured to indicate a plurality of MCSs, respectively, for example, as described below.

[0205] In some exemplary aspects, a user field among multiple user fields of a user STA may include a STA-ID field, which includes a STA-ID used to identify the user STA, and an MCS field, which includes an MCS among multiple MCSs, for example, as described below.

[0206] In some demonstrative aspects, each of the plurality of user fields of a user STA may include the same STA-ID to identify the user STA, eg, as described below.

[0207] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct the user STA implemented by the device 140 to identify the RU allocation information to indicate the allocation of multiple sub-RUs to the user STA, for example, as described below.

[0208] In some demonstrative aspects, a plurality of sub-RUs of a user STA may respectively include a plurality of frequency sub-channels, e.g., as described below.

[0209] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause, and / or instruct a user STA implemented by the device 140 to identify multiple user fields of the user STA to indicate multiple MCSs, for example, based on the order of multiple frequency subchannels in the RU allocation of the user STA, for example, as described below.

[0210] In some demonstrative aspects, a first-order user field among multiple user fields of a user STA may include a STA-ID field, an MCS field after the STA-ID field, and / or a spatial configuration field after the MCS field, for example, as described below.

[0211] In some demonstrative aspects, the bit size of a user field in the plurality of user fields of a user STA may be equal to a predefined bit size of a user field for a user with a single MCS assignment, e.g., as described below.

[0212] In some demonstrative aspects, a user field of the plurality of user fields of a user STA may have a bit size of 22 bits.

[0213] In some demonstrative aspects, a user field in the plurality of user fields of a user STA may have any other bit size.

[0214] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism, which may be configured to provide a technical solution to support allocation of unequal MCSs across multiple frequency subchannels, for example, as described below.

[0215] In some demonstrative aspects, a unequal MCS signaling mechanism may provide a technical solution to support delivery of information corresponding to multiple MCSs to multiple users, e.g., as described below.

[0216] In some exemplary aspects, an unequal MCS signaling mechanism may provide a technical solution to support notifying a user among multiple users of the assignment of their sub-RU / MRUs, which may be split from the RU / MRU corresponding to the user, for example, as described below.

[0217] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement a unequal MCS signaling mechanism configured to utilize user-specific fields in signaling fields, e.g., in accordance with the IEEE 802.11be specification, e.g., as described below.

[0218] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to utilize pseudo-user based user-specific fields in the signaling fields to support allocation of unequal MCSs across multiple frequency subchannels, e.g., as described below.

[0219] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to define one or more "pseudo" users to support signaling of unequal MCS on multiple frequency subchannels, e.g., as described below.

[0220] In some exemplary aspects, the unequal MCS signaling mechanism may be configured to support UEM assignments for UEM users on multiple frequency subchannels, e.g., by splitting the user's RU / MRU into M sub-RUs / MRUs with M MCSs, e.g., as described below.

[0221] For example, in the user-specific field of the EHT-SIG field, a user having M subRUs / MRUs may be considered as M users, eg, including M-1 "pseudo" users, eg, as described below.

[0222] In some exemplary aspects, a user's RU / MRU may be defined to be segmented into M sub-RUs / MRUs, e.g., if the user utilizes unequal MCSs on M frequency sub-channels, e.g., as described below. For example, one or more sub-RUs / MRUs, e.g., each sub-RU / MRU, may be assigned an MCS, e.g., based on an SNR level of the sub-RU / MRU and / or based on any other additional or alternative criteria. For example, a total of up to M different MCSs may be assigned to the user's M sub-RUs / MRUs.

[0223] In some exemplary aspects, the assignment of RUs / MRUs may include assigning sizes and placements of sub-RUs / MRUs to the RU / MRU.

[0224] In some exemplary aspects, the assignment of sub-RUs / MRUs may (e.g., may need to) be adjusted in the RU allocation subfield of the common field of the EHT-SIG field, for example, where one or more sub-RUs / MRUs (e.g., each sub-RU / MRU) may be considered as an individual RU / MRU.

[0225] For example, assignment of sub-RU / MRUs may include generating corresponding bits in the RU allocation subfield, eg, to indicate allocation of sub-RU / MRUs, eg, as "pseudo" RU / MRU allocations to respective multiple "pseudo" users.

[0226] For example, a user may identify the assignment of one or more sub-RUs / MRUs to the user, for example, after reading a common field in the EHT-SIG field.

[0227] In some demonstrative aspects, multiple sub-RUs / MRUs may (eg, may need to) be considered as multiple RUs / MRUs in the RU allocation sub-field of the common field in the EHT-SIG field.

[0228] In one example, a UEM user STA may be allocated a 52-tone RU, which may be split into two 26-tone sub-RUs, which may be assigned respective MCSs, for example. According to this example, the RU allocation of a UEM user STA may be represented by two "pseudo" 26-tone RU allocations, for example, rather than by a single 52-tone RU.

[0229] For example, the RU allocation indicated by the common field of the EHT-SIG field may be adjusted based on the allocation of two 26-tone sub-RUs to the UE M user, for example, as shown below:

[0230]

[0231] Table 1

[0232] For example, as shown in Table 1, the RU allocation subfield (eg, in the common field of the EHT-SIG field) may be set to an RU allocation value configured to indicate multiple RU allocations for multiple users.

[0233] For example, an RU with 52 subcarriers (eg, the 3rd RU) may be assigned to a third user ("User 3"), eg, the user ranked third in the order of RU allocation.

[0234] For example, as shown in the first row of Table 1, if the RU allocation of the third user is non-UEM allocation, the RU allocation subfield may be set to indicate an RU allocation value of 5 (000000101), which indicates that user 3 is allocated 52-tone RUs.

[0235] For example, as shown in the second row of Table 1, if the RU allocation for the third user is a UEM allocation on two 26-tone sub-frequency channels, the RU allocation subfield may be set to indicate an RU allocation value of 1 (000000001), indicating that a 26-tone RU is allocated to the third user and another subsequent 26-tone RU is allocated to the fourth user (e.g., a pseudo user).

[0236] For example, in the case of unequal MCS allocation on the frequency channel of the third user, an RU / MRU with 52 subcarriers may be split into two subRU / MRUs, each with 26 subcarriers. Therefore, these two subRU / MRUs may (e.g., should) be considered as two RU / MRUs with 26 subcarriers in the RU Allocation subfield, and the bits in the RU Allocation subfield may (e.g., should) be changed to represent a value of 1 (00000001).

[0237] For example, a user receiving the DL PPDU may identify the assignment of one or more subRUs / MRUs to the user, for example, after reading the RU allocation subfield in the common field in the EHT-SIG field.

[0238] For example, a user may scan (eg, blind scan) all user fields in the user-specific fields of the EHT-SIG to find its user field, for example, by identifying a user field with the user's STA-ID.

[0239] For example, a UEM user may know the order and position of all of its M user fields, for example, based on the ordered positions of its M subRUs / MRUs.

[0240] For example, the M user fields of a user may provide M MCSs in the MCS subfield of the user field, indicating the MCSs of its M subRUs / MRUs.

[0241] refer to Figure 2 , which schematically illustrates a user-specific field 200 according to some exemplary aspects.

[0242] For example, device 102 ( Figure 1 ) may be configured to generate, send, receive, and / or process a frame including a SIG field, which SIG field may be configured to include a user-specific field 200 to provide user-specific information corresponding to a RU / MRU allocation 201 for one or more users.

[0243] For example, device 140 ( Figure 1 ) and / or device 160( Figure 1 ) may include one or more users, operate as one or more users, play the role of one or more users, and / or perform the functions of one or more users.

[0244] In some exemplary aspects, an AP (eg, provided by device 102 ( Figure 1 ) implemented AP) can determine RU / MRU assignments, including RU / MRU size, RU / MRU placement, and / or RU / MRU allocation to one or more users.

[0245] For example, the AP may send information of RU / MRU size and / or RU / MRU placement, for example, via the RU allocation subfield of the common field in the SIG field (e.g., EHT-SIG field) of the DL PPDU, for example, in accordance with the IEEE 802.11be specification and / or any other specification and / or protocol.

[0246] For example, the AP may set the user field in the user specific field of the EHT-SIG field to provide information on the order of RU allocation, which may be based on the order of the user field, for example, according to the IEEE 802.11be specification.

[0247] In some exemplary aspects, such as Figure 2 As shown, a plurality of RU / MRUs 201, for example, including 5 RU / MRUs, can be assigned to a plurality of users, for example, 5 users. For example, each RU / MRU 201 can be assigned to one user.

[0248] In some exemplary aspects, RU allocation 201 of RU / MRU to users may be indicated by the RU allocation subfield of the common field in the SIG field.

[0249] In some exemplary aspects, such as Figure 2 As shown, the first user (user 1) may be allocated a first RU / MRU, the second user (user 2) may be allocated a second RU / MRU, the third user (user 3) may be allocated a third RU / MRU 203, the fourth user (user 4) may be allocated a fourth RU / MRU, and / or the fifth user (user 5) may be allocated a fifth RU / MRU.

[0250] In some exemplary aspects, the first user may include a non-UEM user, which may be assigned a single MCS for the first RU / MRU; the second user may include a non-UEM user, which may be assigned a single MCS for the second RU / MRU; the fourth user may include a non-UEM user, which may be assigned a single MCS for the fourth RU / MRU; and / or the fifth user may include a non-UEM user, which may be assigned a single MCS for the fifth RU / MRU.

[0251] In some exemplary aspects, such as Figure 2 As shown, the third user may include a UEM user, which may have a first MCS assigned to a first sub-RU / MRU 207 in the third RU / MRU 203 and a second MCS assigned to a second sub-RU / MRU 209 in the third RU / MRU 203 .

[0252] In some exemplary aspects, the user-specific field 200 may include multiple user fields corresponding to multiple users. For example, the order of the user fields in the user-specific field 200 may be based on the order of RU allocation to the user, for example, the order indicated by the RU allocation subfield of the common field.

[0253] For example, the user field 205 of the first user (User 1) may be ranked first in the order of the user-specific fields 200, which may let User 1 know that its RU / MRU is also the first RU / MRU in the RU / MRU 201, for example, based on the RU / MRU assignment 201 provided by the RU allocation subfield of the common field.

[0254] In some exemplary aspects, such as Figure 2 As shown, a third user (User 3) may be assigned a plurality of user fields 202 corresponding to a plurality of subRUs / MRUs 203 assigned to the third user. Figure 2 As shown, a third user (User 3) may be assigned a user field 211 corresponding to the first sub-RU / MRU 207, and / or a user field 213 corresponding to the first sub-RU / MRU 209, for example, as described below.

[0255] In some exemplary aspects, such as Figure 2 As shown, the user-specific field 200 may be encoded to include one or more user-encoded blocks. Figure 2 As shown, the user-specific field 200 may include a user coding block 212 ("a first user coding block"), a user coding block 214 ("a second user coding block"), and / or a user coding block 216 ("a third user coding block").

[0256] In some exemplary aspects, one or more user coding blocks, eg, a majority of user coding blocks, may be configured to be encoded across two user fields, eg, the two user fields are followed by a CRC field and a tail field.

[0257] For example, Figure 2 As shown, the user coding block 212 may include a user field 205 corresponding to the RU / MRU of user 1 ("user field of user 1") and a user field 215 corresponding to the RU / MRU of user 2 ("user field of user 2"). Figure 2 As shown, user coded block 212 may include a CRC+tail field 217 , for example, based on user field 205 and user field 215 .

[0258] For example, Figure 2As shown, the user coding block 214 may include a user field 211 ("User Field-1 for User 3") corresponding to the sub-RU / MRU 207 of User 3 and a user field 213 ("User Field-2 for User 3") corresponding to the sub-RU / MRU 209 of User 3. For example, Figure 2 As shown, the user coding block 214 may include a CRC+tail field, for example, based on the user field 211 and the user field 213 .

[0259] In some exemplary aspects, the last user encoding block may encode only one user field, for example, when the number of user fields is odd.

[0260] In some exemplary aspects, such as Figure 2 As shown, the number of user fields in the user-specific field 200 may be equal to the number of RU / MRU allocations in the RU / MRU allocations 201, for example, including RU / MRU allocations for non-UEM users and sub-RU / MRU allocations for UEM users.

[0261] In some exemplary aspects, such as Figure 2 As shown, the total number of user fields for non-UEM users may be equal to the number of non-UEM users, and the non-UEM user (e.g., each non-UEM user) may have a corresponding user field, which may be configured to carry (e.g., may only carry) information of one MCS.

[0262] In some exemplary aspects, such as Figure 2 As shown, the total number of user fields of the UEM user can be equal to the total number of subRU / MRU allocations of the UEM user. For example, a UEM user (e.g., each third user) may have multiple user fields, which can be configured to carry information about the MCS of the corresponding subRU / MRU of the UEM user.

[0263] In some exemplary aspects, such as Figure 2 As shown, the user fields of the non-UEM user (eg, user fields 205 and / or 215 ) may include a STA-ID field 204 for identifying the non-UEM user (eg, User 1 ).

[0264] In some exemplary aspects, such as Figure 2 As shown, the STA-ID field 204 may be followed by an MCS field 206, which may include an MCS index assigned to the RU / MRU allocation of User 1.

[0265] In some exemplary aspects, such as Figure 2 As shown, the user field 205 may include a coding field 208 and a spatial configuration field 210 following the MCS field 206 .

[0266] For example, Figure 2 As shown, the user field 205 ("user field for user 1") in the user-specific field 200 may include an MCS field 206 that carries information of only one MCS.

[0267] In some exemplary aspects, a user may identify its user field, for example, by blindly scanning all user fields until one is found with the user's STA-ID.

[0268] In some exemplary aspects, after identifying its user field, the user can extract MCS, coding, and / or spatial stream information from its user field, such as from the MCS subfield 206, the coding field 208, and / or the spatial configuration field 210.

[0269] In some exemplary aspects, a user may be considered a UEM user on multiple frequency sub-channels.

[0270] In some demonstrative aspects, the RU / MRU of the UEM user may be partitioned into M sub-RUs / MRUs with M MCSs, which may allow the UEM user to be considered as M pseudo-users in the user-specific field 200 of the EHT-SIG field.

[0271] In some exemplary aspects, such as Figure 2 As shown, user 3 can be identified as a UEM user on multiple frequency sub-channels.

[0272] In some exemplary aspects, such as Figure 2 As shown, RU / MRU 203 (RU / MRU of User 3) may be split into two sub-RU / MRUs, such as sub-RU / MRU 207 (sub-RU / MRU 1) and sub-RU / MRU 209 (sub-RU / MRU 2), which may be assigned two respective MCSs.

[0273] For example, when configuring the RU allocation subfield of the common field in the EHT-SIG, subRU / MRU 207 and subRU / MRU 209 (e.g., the split RU / MRU fragments of user 3) can (e.g., may need to) be treated as two RU / MRUs, for example, as described in reference Table 1 above.

[0274] In some demonstrative aspects, the number of user fields for a UEM user may be equal to the number of MCSs assigned to the UEM user.

[0275] In some exemplary aspects, such as Figure 2 As shown, user 3 may have two user fields 202 corresponding to the two MCSs assigned to user 3.

[0276] In some exemplary aspects, such as Figure 2 As shown, the user field 202 may include a user field 211 (user field-1 of user 3) and a user field 213 (user field-2 of user 3), which may have the same STA-ID but may indicate different MCSs.

[0277] In some exemplary aspects, the UEM user (User 3) may identify the UEM user's RU / MRU assignment 203, for example, based on the RU / MRU allocation 201 indicated by a common field in the SIG field.

[0278] In some demonstrative aspects, the UEM user (User 3) may blindly scan one or more (eg, all) user fields in the user-specific fields 200 to find its user field, for example, through the STA-ID subfield.

[0279] In some exemplary aspects, after scanning the user fields, the UEM user may obtain information about the order and / or position of all its M user fields, for example, the ordered M subRUs / MRUs of the UEM user according to the RU / MRU allocation 201. For example, the M user fields may provide M MCSs indicating the MCSs of the M subRUs / MRUs of the UEM user.

[0280] In some exemplary aspects, the UEM user (user 3) may determine the UEM MCS allocation of the UEM user, for example, based on an MCS subfield in a user field of the UEM user. For example, the i-th user field of the UEM user may include an MCS subfield configured to indicate an MCS assigned to the i-th subRU / MRU allocated to the UEM user according to RU / MRU allocation 201.

[0281] In some exemplary aspects, the user fields of the UEM users, e.g., user fields 211 and 213, may be configured to have the same bit length as the user fields of the non-UEM users, e.g., to provide a technical solution to support users to blindly scan all user fields and find the user fields by their STA-IDs.

[0282] For example, the bit length of each of the user fields 211 and 213 may be equal to the bit length of each of the user fields 205 and 215 .

[0283] For example, the user field of an unequal MCS user may have the same bit length as the user field of a non-unequal MCS user.

[0284] For example, each of the user fields 205, 215, 211, and 213 may be configured to have a bit length of 22 bits, or any other bit length.

[0285] In some exemplary aspects, such as Figure 2 As shown, multiple user fields of a UEM user (e.g., user fields 211 and 213) can be adjacent to each other, for example, when one RU / MRU (e.g., RU / MRU 203) is divided into multiple sub-RU / MRUs (e.g., sub-RU / MRUs 207 and 209).

[0286] In some exemplary aspects, multiple RUs / MRUs may be assigned to one UEM user. For example, the user fields of the UEM user may be adjacent to each other, for example, when the assigned RUs / MRUs are adjacent to each other.

[0287] In other aspects, the user fields for UEM users may be separate from each other, for example, where the RUs / MRUs assigned to UEM users are separate from each other.

[0288] refer to Figure 3 , which schematically illustrates the format of a user field according to some exemplary aspects.

[0289] For example, device 102 ( Figure 1 )、device 140( Figure 1 ), and / or device 160 ( Figure 1 ) may be configured to generate, send, receive, and / or process a message including a user-specific field 200 ( Figure 2 ) frame, the user-specific field may include Figure 3 User field to indicate the UEM assignment to the UEM user.

[0290] In some exemplary aspects, a UEM user may have multiple user fields, and the number of user fields may be equal to the number of MCSs of the UEM user, for example, as described above with reference to Figure 2 described.

[0291] In some exemplary aspects, such as Figure 3 As shown, the user field of the UEM user may be configured according to the user field format 301, for example, when the user field is the first-order user field of the UEM user.

[0292] For example, user field 211 ( Figure 2 ) may include some or all subfields of user field 301.

[0293] In some exemplary aspects, such as Figure 3 As shown, the user field of the UEM user may be configured according to the user field format 303, for example, when the user field is a non-first-order user field of the UEM user.

[0294] For example, user field 213 ( Figure 2) may include some or all subfields of user field 303.

[0295] In some exemplary aspects, the user fields of the UEM user (e.g., user field 301 and user field 303) may be configured to have the same bit length as the user fields of the non-UEM user, for example, to provide a technical solution for the user to blindly scan one or more (e.g., all) user fields and find the user fields by their STA-ID.

[0296] In one example, if Figure 3 As shown, user field 301 and user field 303 may each have a length of 22 bits, for example, similar to the length of each of user fields 205 and 215 ( Figure 2 ).

[0297] In another example, user field 301 and / or user field 303 may have any other length.

[0298] In some exemplary aspects, the format of a user field for a UEM user may depend on the position of the user field relative to other user fields for the same UEM user, e.g., as described below.

[0299] In some exemplary aspects, such as Figure 3 As shown, the user field 301 can be configured according to a first-order user field format, which can be applied to the first-order user field of a UE M user, for example, as described below.

[0300] In some exemplary aspects, such as Figure 3 As shown, the user field 303 can be configured according to a non-first-order user field format, which can be applied to non-first-order user fields of UE M users, for example, as described below.

[0301] For example, the user field 301 may be configured according to a format of a non-UEM user field, for example, according to a user field format of the IEEE 802.11be specification.

[0302] In some exemplary aspects, such as Figure 3 As shown, a first-order user field among the plurality of user fields of a UEM user may have a format similar to (eg, the same as) a format of a user field of a non-UEM user.

[0303] In some exemplary aspects, such as Figure 3 As shown, the user field 301 may include a STA-ID subfield 302 to indicate the STA-ID of the UE user.

[0304] In some exemplary aspects, such as Figure 3As shown, the user field 301 may include an MCS subfield 304, for example, after the STA-ID subfield 302, to indicate the MCS to be applied to the corresponding first-order subRU / MRU of the UE M user.

[0305] In some exemplary aspects, such as Figure 3 As shown, the user field 301 may include a coding subfield 306 and / or a spatial configuration subfield 308 , for example, after the MCS subfield 304 .

[0306] In some demonstrative aspects, the encoding subfield 306 may be configured to indicate an encoding to be applied to multiple subRUs / MRUs of a UEM user, for example, an encoding applied to all subRUs / MRUs of a UEM user.

[0307] In some demonstrative aspects, the spatial configuration subfield 308 may be configured to indicate a spatial configuration to be applied to multiple subRUs / MRUs of a UEM user, for example, a spatial configuration applied to all subRUs / MRUs of a UEM user.

[0308] In some exemplary aspects, non-first-order user fields among the multiple user fields of the UE M user may be configured to include (eg, may only need to carry) information of the STA-ID and MCS, while filling and / or reserving the remaining bits.

[0309] For example, Figure 3 As shown, the user field 303 may be configured as a non-first-order user field for a UEM user, and may include a STA-ID subfield 312, an MCS subfield 314, and / or padding bits 316. For example, the MCS subfield 314 may be set to indicate the MCS to be applied to the corresponding non-first-order subRU / MRU of the UEM user.

[0310] In some exemplary aspects, the first-order user field of the UEM user (e.g., user field 211 ( Figure 1 )) of the STA-ID subfield 302 and the non-first-order user field of the UE M user (for example, the user field 213 ( Figure 1 ))'s STA-ID subfield 312 may be set to the same STA-ID, for example, to identify the UE M user.

[0311] In some demonstrative aspects, user field 303 may be configured to carry one or more additional indications, eg, by replacing some padding bits with one or more additional subfields, eg, as described below.

[0312] In one example, the user field 303 may be configured to include a subfield ("RU / MRU index") to indicate the index of the assigned subRU / MRU among multiple subRUs / MRUs. For example, the RU / MRU index subfield may be set to a value of 1 to indicate the second subRU / MRU among multiple subRUs / MRUs.

[0313] In another example, the user field 303 may be configured to include a subfield ("Total number of RU / MRUs") to indicate the total number of subRUs / MRUs assigned to the UEM user.

[0314] In another example, the user field 303 may be configured to include a subfield ("spatial configuration") to indicate the spatial configuration of the corresponding subRU / MRU, for example, so that the same or different (one or more) spatial streams may be assigned to the subRU / MRU.

[0315] Return to reference Figure 1 In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism configured to support allocation of unequal MCSs across both multiple frequency subchannels and multiple spatial streams, e.g., as described below.

[0316] In some exemplary aspects, the SNR conditions may be different on both frequency subchannels and spatial streams. For example, the difference in SNR conditions may be caused by different primary / secondary channel detection sensitivities and / or MIMO gains.

[0317] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism, which may be configured to provide a technical solution to support allocation of UEMs on both multiple frequency subchannels and multiple spatial streams, for example, as described below.

[0318] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize a user-specific field format that may be configured to support assignment of unequal MCS across both multiple frequency subchannels and multiple spatial streams, e.g., as described below.

[0319] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to provide a technical solution to support signaling indications of unequal MCS on multiple spatial streams to unequal MCS users, e.g., as described below.

[0320] In some demonstrative aspects, a predefined MCS index, such as, for example, the EHT-MCS14 (1110) index or any other predefined index, may be used as a UE M indicator, e.g., as described below.

[0321] For example, the EHT-MCS14 (1110) index may be utilized in an EHT duplicate (DUP) transmission mode, e.g., according to the IEEE 802.11be specification, to indicate an EHT single user (SU) transmission, e.g., when the PPDU type and compression mode subfields in the U-SIG are set to 1.

[0322] In some exemplary aspects, the EHT-MCS14 (1110) index may be used to indicate the UEM assignment of the UEM user, for example, when the PPDU type and compression mode are 0 or 2, for example, indicating a non-EHT SU transmission.

[0323] In some exemplary aspects, the EHT-MCS14 (1110) index may be used to indicate the UEM designation of the UEM user, e.g., even in the case of EHT SU transmissions. For example, in the case of the UEM designation of the UEM user in SU transmissions, the PPDU Type and Compression Mode subfields may be set to a value of 3, and the MCS subfield for the UEM user may be set to the EHT-MCS14 (1110) index, e.g., to indicate the UEM designation of the UEM user.

[0324] In some exemplary aspects, a mapping from a plurality of subfield setting combinations (e.g., including PPDU type and compression subfield settings and MCS subfield settings) to a UE M user type may be defined, for example, as follows:

[0325]

[0326]

[0327] Table 2

[0328] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism, which may be configured to utilize a pseudo-user based user-specific field to support allocation of UEMS, e.g., on frequency subchannels and / or spatial streams, e.g., on both frequency subchannels and spatial streams, e.g., as described below.

[0329] refer to Figure 4 , which schematically illustrates a user-specific field 400 according to some exemplary aspects.

[0330] For example, device 102 ( Figure 1) may be configured to generate, send, receive, and / or process a frame including a SIG field, which SIG field may be configured to include a user-specific field 400 to provide user-specific information corresponding to a RU / MRU allocation 401 for one or more users.

[0331] For example, device 140 ( Figure 1 ) and / or device 160( Figure 1 ) may include one or more users, operate as one or more users, play the role of one or more users, and / or perform the functions of one or more users.

[0332] In some exemplary aspects, an AP (eg, provided by device 102 ( Figure 1 ) implemented AP) can determine RU / MRU assignments, including RU / MRU size, RU / MRU placement, and / or RU / MRU allocation to one or more users.

[0333] For example, the AP may send information of RU / MRU size and / or RU / MRU placement, for example, via the RU allocation subfield of the common field in the SIG field (e.g., EHT-SIG field) of the DL PPDU, for example, in accordance with the IEEE 802.11be specification and / or any other specification and / or protocol.

[0334] For example, the AP may set the user field in the user specific field 400 of the EHT-SIG field to provide information on the order of RU allocation, which may be according to the order of the user field, for example, according to the IEEE 802.11be specification.

[0335] In some exemplary aspects, such as Figure 4 As shown, a plurality of RU / MRUs 401, for example, including 5 RU / MRUs, may be assigned to a plurality of users, for example, 5 users. For example, each RU / MRU 401 may be assigned to one user.

[0336] In some demonstrative aspects, RU allocation 401 of RU / MRU to users may be indicated by the RU allocation subfield of the common field in the SIG field.

[0337] In some exemplary aspects, such as Figure 4 As shown, the first user (user 1) may be allocated a first RU / MRU, the second user (user 2) may be allocated a second RU / MRU, and the third user (user 3) may be allocated a third RU / MRU (for example, including RU / MRU 203 ( Figure 2 )), a fourth user (User 4) may be allocated a fourth RU / MRU 411, and / or a fifth user (User 5) may be allocated a fifth RU / MRU.

[0338] In some exemplary aspects, the first user may include a non-UEM user, which may be assigned a single MCS for the first RU / MRU; the second user may include a non-UEM user, which may be assigned a single MCS for the second RU / MRU; and / or the fifth user may include a non-UEM user, which may be assigned a single MCS for the fifth RU / MRU.

[0339] In some exemplary aspects, such as Figure 4 As shown, the third user may include a UEM user, which may have a first MCS assigned to a first sub-RU / MRU in the third RU / MRU and a second MCS assigned to a second sub-RU / MRU in the third RU / MRU, for example, as described above with reference to Figure 2 described.

[0340] In some exemplary aspects, such as Figure 4 As shown, the fourth user may include a UEM user, which may have multiple MCSs assigned to the first sub-RU / MRU 431 and the second sub-RU / MRU 433 in the fourth RU / MRU 411, for example, as described below.

[0341] In some exemplary aspects, the user-specific field 400 may include multiple user fields corresponding to multiple users. For example, the order of the user fields in the user-specific field 400 may be based on the order of RU allocation to the user, for example, the order indicated by the RU allocation subfield of the common field.

[0342] In some exemplary aspects, such as Figure 4 As shown, the third user (User 3) may be assigned multiple user fields corresponding to the multiple subRUs / MRUs assigned to the third user, for example, as described above with reference to Figure 2 described.

[0343] In some exemplary aspects, such as Figure 4 As shown, a fourth user (User 4) may be assigned a plurality of user fields 400 corresponding to a plurality of subRUs / MRUs 411 assigned to the fourth user. Figure 4 As shown, a fourth user (User 4) may be assigned a user field 435 corresponding to the first sub-RU / MRU 431 and / or a user field 437 corresponding to the first sub-RU / MRU 433, for example, as described below.

[0344] In some exemplary aspects, a RU / MRU assigned to a user may be partitioned into M sub-RUs / MRUs having M MCSs. For example, a sub-RU / MRU, e.g., each sub-RU / MRU, may have a user field that may be identified, e.g., by blindly scanning a STA-ID field in the user field, e.g., as described above.

[0345] In some exemplary aspects, a user (e.g., user 3) may be assigned an MCS as a UEM user, e.g., only on a frequency subchannel. For example, the user field of user 3 may be configured such that multiple subRUs / MRUs of user 3 may be mapped to multiple user fields 402, e.g., such that each of its subRUs / MRUs may be mapped to one user field 402.

[0346] In some exemplary aspects, such as Figure 4 As shown, user field 402 can be based on user field 301 ( Figure 3 ) and User Field 303 ( Figure 3 ). For example, one or more (e.g., each) of the user fields 402 may include a STA-ID subfield, an MCS subfield, and the first user field of the user includes a coding and / or spatial configuration subfield, for example, as described above with reference to Figure 2 and Figure 3 described.

[0347] In some demonstrative aspects, a user (e.g., user 4) may be assigned an MCS as a UE M user, e.g., on both frequency subchannels and spatial streams, e.g., as described below.

[0348] In some exemplary aspects, such as Figure 4 As shown, the user field 404 of user 4 may include a STA-ID subfield, an MCS subfield, a coding subfield, and / or a space configuration subfield, for example, similar to the user field 301 ( Figure 3 ) and User Field 303 ( Figure 3 ) format.

[0349] For example, Figure 4 As shown, the first-order user field of user 4 (e.g., user field 435) may include a STA-ID subfield, an MCS subfield 410, a coding subfield, and / or a spatial configuration subfield 412, for example, similar to user field 301 ( Figure 3 ) format.

[0350] For example, Figure 4As shown, the non-first-order user field of user 4 (e.g., user field 437) may include a STA-ID subfield, an MCS subfield 410, and a padding segment and / or an additional subfield, for example, similar to user field 303 ( Figure 3 ) format.

[0351] In some exemplary aspects, such as Figure 4 As shown, the MCS subfield 410 of the user field 404 may include a predefined MCS index, such as the EHT-MCS14 (1110) index or any other suitable predefined MCS index, for example, instead of actual MCS information.

[0352] For example, a predefined MCS index (eg, EHT-MCS14 (1110) index) may indicate that a UE M user (User 4) has a UE M assignment on multiple spatial streams.

[0353] In some exemplary aspects, such as Figure 4 As shown, user-specific fields 400 may be configured to include one or more UEM fields 406 corresponding to user 4, for example, as described below.

[0354] In some demonstrative aspects, UEM field 406 corresponding to user 4 may be configured to include UEM information for user 4, e.g., as described below.

[0355] In some demonstrative aspects, the UEM field 406 corresponding to user 4 may be configured to include assignments of multiple frequency subchannels and multiple spatial streams in the RU allocation 411 that assigns multiple MCSs to user 4, e.g., as described below.

[0356] In some demonstrative aspects, user 4 may search one or more UEM fields 406, e.g., based on identifying a predefined MCS index in MCS subfield 410, which indicates that user 4 is a UEM user on a spatial stream. For example, user 4 may search a UEM field, e.g., UEM field 406, which includes the STA-ID of user 4, to identify MCS information related to user 4.

[0357] In some exemplary aspects, such as Figure 4 As shown, one or more UEM fields, for example, all UEM fields, in the user-specific field 400 may be located after all user fields for all users.

[0358] In some demonstrative aspects, one or more UEM fields in user-specific fields 400, e.g., UEM field 406 for user 4, may be encoded in UEM encoding blocks, which may be located (e.g., may always be located) at the end of the user encoding blocks.

[0359] For example, Figure 4 As shown, a UEM encoding block 420 (eg, including a UEM field 406 ) may be located after a last user encoding block 422 .

[0360] In some exemplary aspects, one or more UEM encoding blocks (e.g., each UEM encoding block) in the user-specific field 400 may encode one or more (e.g., up to two) UEM fields, which may be from the same user or different users, for example, similar to the above reference 400. Figure 2 Discusses the format of the user code block.

[0361] For example, Figure 4 As shown, the UEM encoding block 420 may include two UEM fields 406 and a CRC field, such as a CRC field based on the two UEM fields 406 .

[0362] In some exemplary aspects, such as Figure 4 As shown, the length of the UEM field, for example, the length of each UEM field 406, can be the same as the length of each user field 404, for example, to simplify implementation and / or improve compatibility. Figure 4 As shown, the length of each UEM field 406 may be 22 bits, for example, similar to the length of each user field of the user-specific field 400 .

[0363] In some exemplary aspects, such as Figure 4 As shown, the UEM field 491 may include a STA-ID subfield 403, for example, an 11-bit STA-ID subfield, followed by a plurality of MCS subfields 405 with MCS information, for example, four MCS subfields. For example, the UEM field 491 may include a 1-bit padding subfield 407, for example, after the MCS subfield 405.

[0364] In some demonstrative aspects, user 4 may discover its UEM field 406 , for example, by blindly scanning all UEM fields to find a UEM field with user 4 's STA-ID.

[0365] In some demonstrative aspects, the MCS subfield 405 of the UEM field 491 corresponding to the subRU / MRU allocation may be configured to indicate the MCS of a plurality of respective spatial streams to be applied to the subRU / MRU allocation.

[0366] For example, the MCS subfield 405 of the UEM field 491 corresponding to the subRU / MRU allocation 431 may be configured to indicate the MCSs to be applied to up to four respective spatial streams on the subRU / MRU allocation 431 .

[0367] For example, the MCS subfield 405 of the UEM field 491 corresponding to the subRU / MRU allocation 433 may be configured to indicate the MCS to be applied to up to four respective spatial streams on the subRU / MRU allocation 433 .

[0368] In some demonstrative aspects, the MCS subfield 405 may be configured according to a differential MCS format, e.g., to provide a technical solution to support reduced overhead, e.g., as described below.

[0369] In some exemplary aspects, such as Figure 4 As shown, the first-order MCS subfield 409 in the UEM field 491 may have a size of 4 bits, for example, to support a 4-bit binary number. For example, the MCS subfield 409 may be configured to indicate the MCS index (basic MCS) of the user. For example, the MCS subfield 409 may be configured to indicate the MCS index with maximum modulation of user 4.

[0370] In some exemplary aspects, such as Figure 4 As shown, the remaining MCS subfields 493, e.g., the MCS subfields after the first MCS subfield 409, may have a reduced bit size, e.g., a size of 2 bits, e.g., to support a 2-bit binary number. For example, the 2-bit MCS subfield 493 may indicate a modulation order reduction, e.g., compared to the previous MCS 409, e.g., instead of a full 4-bit MCS index. For example, the MCSs of the same user (e.g., MCS 405 for user 4) may share the same coding rate, e.g., while the MCSs may differ only in modulation, e.g., according to the IEEE 802.11be specification.

[0371] In some exemplary aspects, such as Figure 4 As shown, the user-specific fields 400 may include a single UEM field 491 for each subRU / MRU allocation of user 4, for example, where user 4 has up to four spatial streams for the subRU / MRU allocation.

[0372] In some demonstrative aspects, the user-specific field 400 may include a multiple UEM field 491 for a subRU / MRU allocation for a UEM user, for example, where the UEM user has more than four spatial streams for the subRU / MRU allocation.

[0373] For example, user 4 may be a UEM user on both frequency subchannels and spatial streams, with six spatial streams. For example, user 4 may obtain information about the spatial streams of user 4 based on the spatial configuration subfield of the first-order user field of user 4 (e.g., user field-1 of user 4). According to this example, user 4 may have four UEM fields, for example, where every two UEM fields may correspond to corresponding RU / MRU allocations and may contain six 2-bit MCSs for the six spatial streams on the RU / MRU allocations.

[0374] In some exemplary aspects, such as Figure 4 As shown, RU / MRU 411 assigned to user 4 may be segmented into M sub-RU / MRUs, e.g., including sub-RU / MRUs 431 and 433. For example, user 4 may expect to find M user fields with the STA-ID of user 4, e.g., by blindly scanning all user fields in user-specific field 400.

[0375] In some demonstrative aspects, user 4 may identify itself as a UE M user on multiple spatial streams, for example, by reading the EHT-MCS14 index in the MCS subfield 410 of the user field including the STA-ID of user 4.

[0376] In some exemplary aspects, user 4 may know the number of its spatial streams, for example, via the spatial configuration subfield 412 in the first-order user field 435 of user 4 (user field-1 of user 4).

[0377] For example, the number of spatial streams of user 4 is S. According to this example, user 4 can expect to obtain a total of M×S MCSs in the UEM fields 406 of user 4, which can be encoded in the UEM coding block 420 located at the end of the user coding block. For example, user 4 can search its UEM field 406, for example, by blindly scanning all UEM fields to find the UEM field with the STA-ID of user 4.

[0378] In some exemplary aspects, the user-specific field 400 may be configured to reuse the format of the user field of the UEM user, for example, in accordance with the IEEE 802.11be specification. For example, the format of the user field of the UEM user, for example, the user field 435 and / or 437, may be configured to include STA-ID, MCS, and / or spatial configuration subfields, for example, according to a format compatible with the IEEE 802.11be specification.

[0379] For example, a user may search for its STA-ID in each user field. For example, it may be defined that if the STA-ID in the user field matches the STA-ID of the user, the user determines that the RU / MRU, MCS, and / or spatial stream in the user field will be allocated to the user as a UEM user.

[0380] For example, the format of the user specific field 400 may provide a technical solution to support signaling different MCSs for different frequency RUs and different spatial streams to a UE M user.

[0381] Return to reference Figure 1 In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism configured to support unequal MCS allocations on both frequency subchannels and spatial streams, for example, by signaling a UEM user as multiple pseudo-users, for example, as described above.

[0382] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize a pseudo-user based user field format to signal unequal MCS allocation information to UE M users, e.g., as described above.

[0383] In some exemplary aspects, for example, as described above, utilizing an unequal MCS signaling mechanism based on a pseudo-user's user field format may provide a technical solution to preserve the format of common fields and / or user-specific fields of the EHT-SIG field, for example, to ensure compatibility with the IEEE 802.11be specification.

[0384] In some exemplary aspects, for example, in some implementations, use cases, and / or scenarios, there may be some overhead when utilizing a pseudo-user based user field format, for example, because padding in the STA-ID subfield and / or the user field and / or the UEM field may consume relatively more bits. For example, the pseudo-user based user field format may utilize the STA-ID subfield to support users, while the users may not be able to accurately locate their user fields and UEM fields, for example, when blindly scanning over the STA-ID subfield.

[0385] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism configured to support unequal MCS signaling via configuration of user-specific fields, e.g., as described below.

[0386] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to support unequal MCS, e.g., for Wi-Fi 8 (UHR) implementations, e.g., as described below.

[0387] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to utilize an improved user-specific field format, for example, to provide a technical solution to support reduced overhead, for example, as described below.

[0388] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to provide a technical solution to support the allocation of unequal MCS across multiple frequency subchannels and / or multiple spatial streams, e.g., as described below.

[0389] In some exemplary aspects, the unequal MCS signaling mechanism may be configured to utilize a user field format and a UEM field format, which may be configured to provide a technical solution to support the allocation of unequal MCS across multiple frequency subchannels and / or multiple spatial streams, for example, as described below.

[0390] refer to Figure 5 , which schematically illustrates a format of a user field 500 for identifying one or more UEM fields according to some demonstrative aspects.

[0391] For example, device 102 ( Figure 1 ) and / or device 140( Figure 1 ) may be configured to generate, send, receive, and / or process a frame including a user field 500 configured to indicate a UEM assignment to a UEM user.

[0392] In some exemplary aspects, such as Figure 5 As shown, user field 500 may be configured according to user field format 501 (non-UEM user field format), e.g., for a non-UEM user, e.g., as described below.

[0393] In some exemplary aspects, such as Figure 5 As shown, user field 500 may be configured according to user field format 503 (UEM user field format), e.g., for a UEM user, e.g., as described below.

[0394] In some exemplary aspects, such as Figure 5 As shown, user field 500 may be configured to have a length of 24 bits, for example, as compared to a 22-bit length of a user field according to the IEEE 802.11 specification.

[0395] In some exemplary aspects, the user field 500 may include an MCS type subfield 507 configured to identify the MCS type of the user, e.g., as described below. Figure 5 As shown, the MCS type subfield 507 may have a length of 2 bits. In other aspects, the MCS type subfield 507 may have any other length.

[0396] In some demonstrative aspects, MCS type subfield 507 may be configured to indicate whether the user of user field 500 is a non-UEM user or a UEM user, e.g., as described below.

[0397] For example, Figure 5 As shown, the MCS type subfield 507 in the user field 501 may be set to an MCS type value 502, which is configured to indicate that the user is a non-UEM user. For example, the value of the MCS type value 502 may include 00.

[0398] For example, Figure 5 As shown, the MCS type subfield 507 in the user field 503 may be set to an MCS type value 504, which is configured to indicate that the user is a UEM user. For example, the value of the MCS type value 504 may include a value other than 00.

[0399] In some demonstrative aspects, the MCS type value 504 is configured to indicate a type of UEM assignment from among a plurality of predefined UEM assignment types, e.g., as described below.

[0400] For example, the MCS type subfield 507 in the user field 503 may be set to a first predefined value 504, such as 01, indicating a UE M user on multiple frequency subchannels.

[0401] For example, the MCS type subfield 507 in the user field 503 may be set to a second predefined value 504, eg, 10, indicating a UE M user on multiple spatial streams.

[0402] For example, the MCS type subfield 507 in the user field 503 may be set to a third predefined value 504, eg, 11, indicating a UE M user on both a frequency channel and a spatial stream.

[0403] In other aspects, any other additional or alternative mappings of MCS type values ​​may be defined to indicate the MCS type.

[0404] In some exemplary aspects, such as Figure 5 As shown, it can be defined that: when the user field 500 includes the MCS type subfield 507 containing the MCS type value of the non-UEM user, the user field 500 will include the MCS index to be used by the non-UEM user, for example, included in the MCS field, for example, a 4-bit field after the MCS type subfield 507.

[0405] For example, Figure 5As shown, the user field 501 may include an MCS type value 502 that identifies the user as a non-UEM user, and the MCS type value 502 may be followed by a 4-bit MCS subfield 506. For example, the MCS subfield 506 may provide an index of the MCS to be used by the non-UEM user.

[0406] In some exemplary aspects, such as Figure 5 As shown, it can be defined that when the user field 500 includes the MCS type subfield 507 including the MCS type value of the UEM user, the user field 500 will include UEM field indication information for the UEM user to use to locate one or more UEM fields of the UEM user, for example, as described below.

[0407] For example, Figure 5 As shown, the user field 503 may include an MCS type value 504 that identifies the user as a UEM user, and may be followed by a 4-bit UEM field indicator subfield 508. For example, the UEM field indicator subfield 508 may inform the UEM user of the location of the first UEM field of the UEM user, such as the UEM field 505.

[0408] For example, the MCS type subfield 504 may have a value of 01, and the UEM field indicator subfield 508 may have a value of 0011. According to this example, the MCS type subfield 504 may indicate that the user is a UEM user on multiple frequency subchannels, and the UEM field indicator subfield 508 may indicate that the first UEM field of the UEM user is the 4th UEM field, for example, if the value 0000 is defined to indicate the first UEM field, (or the 3rd UEM field, for example, if the value 0001 is defined to indicate the first UEM field).

[0409] In some exemplary aspects, the total length of the UEM field (e.g., UEM field 505) can be the same as or shorter than the length of the user field. In one example, the UEM field can be defined as having a length of 21 bits or any other additional or alternative value.

[0410] In some exemplary aspects, the UEM field indicator subfield 508 in the user field may be configured to provide the location of the UEM field. For example, the UEM field indicator subfield 508 may be configured to provide a technical solution to avoid the need to include a STA-ID in the UEM field.

[0411] In some demonstrative aspects, the UEM field may be configured to provide information of an MCS assignment, e.g., in the form of minimum frequency segments and / or MCS, e.g., as described below.

[0412] In some exemplary aspects, the first-order UEM field (UEM field 1) of a UEM user may be configured according to a UEM field format, which may start with a 3-bit minimum frequency segment subfield, followed by four 4-bit MCS subfields and 2 bits of padding. Figure 5 As shown, the UEM field 505 may include a minimum frequency segment subfield 510 followed by four MCS subfields 512 and a padding subfield 514 .

[0413] In some exemplary aspects, a non-first-order UEM field for a UEM user may be configured according to a UEM field format that may carry (e.g., only carry) MCS information, which may include five 4-bit MCS subfields, e.g., followed by 1-bit padding. Figure 5 As shown, the UEM field 517 may include five MCS subfields 516 , for example, followed by a padding subfield 518 .

[0414] In some exemplary aspects, such as Figure 5 As shown, the minimum frequency segment subfield 510 may be implemented as the first subfield in the first UEM field (eg, UEM field 505 (UEM field-1 for unequal MCS users)) of a UEM user (eg, each UEM user).

[0415] In some demonstrative aspects, the minimum frequency fragment subfield 510 may be configured to specify the partition of the RU or MRU of the UEM user, for example, by using 3 bits to inform the UEM user of its minimum frequency fragments with different MCSs.

[0416] In one example, the RU / MRU of the user may be equally divided into a plurality of subRU / MRUs having 26 subcarriers, 52 subcarriers, 106 subcarriers, 242 subcarriers, 484 subcarriers, 996 subcarriers, 2×996 subcarriers, etc. According to this example, the minimum frequency fragment subfield 510 may indicate the number of subcarriers in each subRU / MRU having different MCSs.

[0417] In another example, a partition lookup table may be defined for each RU and / or MRU size, respectively, and an entry index may be specified in the minimum frequency segment subfield 510 .

[0418] In some exemplary aspects, a UEM user may know the bandwidth of its RU / MRU, for example, based on the RU allocation subfield in the common field, and the order of its user fields in the user-specific field. For example, the UEM user may calculate the number of its subRU / MRUs, and the number of MCSs that the UEM user may (e.g., should) search for in its UEM field, for example, based on the bandwidth of the RU / MRU assigned to the UEM user and the order of the user fields in the user-specific field. For example, if the number of MCSs of the UEM user is less than or equal to four, the UEM user may (e.g., may only need to) read one UEM field. For example, if the number of MCSs of the UEM user is more than four, the UEM user may look for other UEM fields, for example, to obtain all of its MCSs.

[0419] refer to Figure 6 , which schematically illustrates a user-specific field 600 according to some exemplary aspects.

[0420] For example, device 102 ( Figure 1 )、device 140( Figure 1 ), and / or device 160 ( Figure 1 ) may be configured to generate, send, receive, and / or process a frame including a UEM-assigned user-specific field 600 configured to indicate a UEM user.

[0421] In some exemplary aspects, such as Figure 6 As shown, the user-specific field 600 may include one or more encoding blocks. Figure 6 As shown, the user specific field 600 may include a user coding block 601 , a user coding block 603 , a user coding block 605 , and / or a UEM coding block 607 .

[0422] In some exemplary aspects, such as Figure 6 As shown, a user encoding block may include one or more user fields, and a UEM encoding block may include one or more UEM fields.

[0423] In some exemplary aspects, such as Figure 6 As shown, the UEM encoding block 607 may be configured to encode up to two UEM fields followed by a CRC and a trailer field.

[0424] In some exemplary aspects, the UEM field in the UEM encoding block 607 may belong to a UEM user.

[0425] In other aspects, the UEM fields in the UEM encoding block 607 may belong to two different UEM users.

[0426] In some exemplary aspects, such as Figure 6As shown, a UEM coding block, for example, including UEM coding block 607, may follow a user coding block.

[0427] In some exemplary aspects, the user field may have a fixed length, which may provide a technical solution so that the user can know the start bit and the end bit of each user field, for example, to perform blind scanning.

[0428] In some exemplary aspects, the UEM field may be configured to have a fixed length, and the UEM coding block may be located after the user coding block, for example, to support a technical solution so that the user can know the start and end bits of each UEM field.

[0429] In some exemplary aspects, the user field and the UEM field in the user-specific field 600 may be configured to provide a technical solution to support the user to relatively easily find the user's first UEM field (UEM field-1), for example, UEM field 606. For example, the user may be able to find the UEM field 606, for example, based on the UEM field location information provided by the UEM field indicator subfield in the user field of the user, for example, the UEM field indicator subfield 508 ( Figure 5 ).

[0430] In some exemplary aspects, a UEM field indicator subfield of a UEM user, such as UEM field indicator subfield 508 ( Figure 5 ), can be configured to provide the position of the first-order UEM field of the UEM user. For example, other UEM fields (e.g., non-first-order UEM fields) (e.g., UEM field-2 and / or UEM field-3) can (e.g., can always) be located after the first-order UEM field (UEM field-1).

[0431] In some exemplary aspects, such as Figure 6 As shown, the RU / MRU 604 assigned to a UEM user (eg, User 3) may be partitioned into six sub-RUs with six MCSs.

[0432] In some exemplary aspects, user 3 may be aware of the RU / MRU assignment including the size and location of the RU / MRU of user 3, for example, based on information in the RU allocation subfield of a common field in a SIG field (e.g., an EHT-SIG field and / or a UHR-SIG field).

[0433] In some exemplary aspects, user 3 may identify user field 602 (“user field of user 3”), e.g., by scanning all user fields in user-specific fields 600. For example, user 3 may identify user field 602 as being in the third position among all user fields, e.g., based on identifying the STA ID of user 3 in user field 602.

[0434] In some exemplary aspects, User 3 may (eg, automatically) be aware that RU / MRU 604 (eg, which is the third of the RUs / MRUs) is assigned to User 3 .

[0435] In some demonstrative aspects, user 3 may obtain encoding and / or spatial configuration information from user field 602 .

[0436] In some exemplary aspects, user 3 may identify itself as a UE M user, for example, by MCS type subfield 507 ( Figure 5 ) to identify the MCS type value.

[0437] In some exemplary aspects, user 3 may obtain the location of the first UEM field (e.g., UEM field 606) of user 3, for example, by using the UEM field indicator subfield 508 ( Figure 5 ) to obtain. For example, the UEM field indicator subfield 508 ( Figure 5 ) may include bits set to a value (e.g., 0000) indicating that the UEM field 606 is the first-order UEM field among all UEM fields.

[0438] In some exemplary aspects, user 3 may obtain information about the number of subcarriers in each subRU / MRU of user 3, for example, through the minimum frequency fragment subfield 510 ( Figure 5 ) to obtain.

[0439] In some demonstrative aspects, user 3 may be aware of the number of its subRUs / MRUs and / or MCSs, for example, based on information about the number of subcarriers in each subRU / MRU.

[0440] For example, in a case where the number of MCSs of user 3 is less than or equal to four, only one UEM field, for example, UEM field 1, may be assigned to user 3.

[0441] For example, in case the number of MCSs of user 3 is more than four, more than one UEM field may be assigned to user 3.

[0442] For example, user 3 may have six subRUs with six MCSs. Based on this example, user 3 may know that two UEM fields are assigned to user 3, for example, because each first-order UEM field may only carry four MCS subfields, while other UEM fields, for example, non-first-order UEM fields, may each carry five MCS subfields, for example, as described above.

[0443] For example, user 3 can decode the UEM field 606, which is represented by the UEM field indicator subfield 508 ( Figure 5 ) for precise positioning.

[0444] For example, user 3 may decode UEM field 608 next to UEM field 606 to obtain all six MCSs of user 3.

[0445] In some exemplary aspects, it can be defined that: when a UEM user has more than one UEM field, one or more other UEM fields of the UEM user can always be located after its first-order UEM field, so that the UEM field indicator subfield can (for example, may only need to) provide position information of the first-order UEM field of the UEM user.

[0446] Return to reference Figure 1 In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism configured to enable allocation of unequal MCS across both multiple frequency subchannels and spatial streams, e.g., as described below.

[0447] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism, which may be configured to utilize user-specific fields including user fields and / or UEM fields to provide a technical solution to support the allocation of unequal MCS on both frequency subchannels and spatial streams, for example, as described below.

[0448] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to provide a technical solution to identify whether a user is a UEM user or a non-UEM user, e.g., as described below.

[0449] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to provide a technical solution to identify whether a UE M user has an allocation of unequal MCS on multiple frequency subchannels, multiple spatial streams, or both, e.g., as described below.

[0450] refer to Figure 7 , which schematically illustrates a format of a user field 700 for identifying one or more UEM fields according to some demonstrative aspects.

[0451] For example, device 102 ( Figure 1 ) and / or device 140( Figure 1 ) may be configured to generate, send, receive, and / or process a frame including a user field 500 configured to indicate a UEM assignment to a UEM user.

[0452] In some exemplary aspects, such as Figure 7 As shown, the user field 700 can be configured according to the user field format 701 (non-UEM user field format), for example, for non-UEM users, for example, as described above with reference to Figure 5 described.

[0453] In some exemplary aspects, such as Figure 7 As shown, the user field 700 can be configured according to a user field format 703 (UEM user field format), for example, for a UEM user, for example, as described below.

[0454] In some exemplary aspects, a user may be identified by its user field 703, for example, by blindly scanning all user fields to find a user field having the STA-ID of the user.

[0455] In some exemplary aspects, the user may identify the user's MCS type based on the MCS type value 702 in the user field 703, e.g., as described above. For example, the user may be identified as a UE M user on both frequency subchannels and spatial streams based on the MCS type value 702 including the value 11, e.g., as described below.

[0456] In some exemplary aspects, a user may obtain the position and number of its spatial streams, for example, via the spatial configuration subfield 704 of the user field 703 .

[0457] In some exemplary aspects, the user may obtain the position of the user's first-order UEM field (UEM field-1 for unequal MCS users) (e.g., for example, UEM field 705), for example, via a 4-bit UEM field indicator subfield 706, for example, as described above.

[0458] In some exemplary aspects, one or more (e.g., each) UEM fields of a user having UEM allocations on both frequency subchannels and spatial streams may be configured to carry (e.g., only carry) the MCS of the spatial streams of the same (e.g., single) subRU / MRU.

[0459] For example, a user's RU / MRU may be split into two sub-RU / MRUs, and each sub-RU / MRU may have four spatial streams. According to this example, the total number of spatial streams may be eight. According to this example, a user may have two UEM fields, such as UEM field-1 and UEM field-2, each of which includes four MCSs of the respective sub-RU / MRU.

[0460] In some exemplary aspects, the format of the first-order UEM field may be different from that of the non-first-order UEM field. Figure 7 As shown, a first-order UEM field (e.g., UEM field 705) may have a unique format, for example, compared to other UEM fields (e.g., non-first-order UEM fields).

[0461] In some exemplary aspects, such as Figure 7 As shown, the UEM field 705 may include a minimum frequency segment subfield 710 , a 4-bit MCS subfield 712 , and seven 2-bit MCS subfields 714 .

[0462] For example, the minimum frequency fragment subfield 710 may indicate the number of subcarriers in each subRU / MRU having different MCSs.

[0463] In some demonstrative aspects, the UEM user may use the information in the minimum frequency segment subfield 710 to calculate how many subRUs / MRUs the UEM user has and / or how many MCSs the UEM user may (e.g., should) search for in the UEM field corresponding to the UEM user.

[0464] In some exemplary aspects, the MCS may be listed as spatial stream first or sub-RU / MRU first.

[0465] For example, it may be assumed that the RU / MRU assigned to the user has N subcarriers and the minimum frequency slice is A. According to this example, the number of sub-RU / MRUs may be determined as ceil(N / A), which means rounded to the nearest integer greater than or equal to N / A.

[0466] For example, it can be assumed that the number of spatial streams of a user is S. According to this example, a user can have ceil(N / A) UEM fields, for example, each of which includes S MCSs.

[0467] In some exemplary aspects, one or more non-first-order UEM fields may follow the first-order UEM field. Figure 7 As shown, the non-first-order UEM field 707 may follow (eg, immediately follow) the first-order UEM field 705 .

[0468] In some exemplary aspects, such as Figure 7 As shown, the UEM field 707 may include (eg, may only include) an MCS subfield, which may be followed by padding bits.

[0469] In some exemplary aspects, such as Figure 7 As shown, only the first MCS subfield in the UEM field may include a 4-bit binary number representing the first MCS index, while other MCS subfields may include 2-bit binary numbers representing other MCS indexes based on the first MCS index, for example, as described above.

[0470] For example, the MCS subfield 712 may indicate an MCS index having an MCS of a first subRU / MRU and a first spatial stream.

[0471] In some exemplary aspects, to reduce overhead, other (e.g., non-first) MCS subfields may include a 2-bit (or 3-bit) MCS binary number. In one example, the non-first MCS subfield may indicate a decrease or increase in the modulation order relative to the MCS of the previous spatial stream or the MCS of the previous subRU / MRU on the same spatial stream.

[0472] In some exemplary aspects, a non-first MCS subfield may be configured to indicate a change in modulation order and coding rate, e.g., relative to a previous spatial stream or subRU / MRU, e.g., to provide a technical solution for supporting horizontal coding.

[0473] In some exemplary aspects, the UEM fields of a user may (e.g., may always) be arranged in order, for example, such that a UEM field indicator subfield of the user field may (e.g., may only need to) indicate the position of the first UEM field (e.g., UEM field-1), while the remaining UEM fields may be automatically determined.

[0474] In some exemplary aspects, new user-specific fields may be designed and proposed, such as user field 500 ( Figure 5 ), user specific field 600 ( Figure 6 ), and / or user field 700 ( Figure 7 ) to provide a technical solution to enable allocation of unequal MCS on frequency subchannels and / or on both frequency channels and spatial streams, for example, as described above.

[0475] In some exemplary aspects, new user-specific fields may be defined, such as user field 500 ( Figure 5 ) and / or user field 700 ( Figure 7 ), and / or new UEM fields, for example, UEM field 505 ( Figure 5 )、UEM field 507( Figure 5)、UEM field 705( Figure 7 ), and / or UEM field 707 ( Figure 7 ) to signal the user's MCS type and the location of the UEM field carrying the MCS information, for example, via a new subfield, an MCS type subfield, and / or a UEM field indicator subfield, for example, as described above.

[0476] In some exemplary aspects, user field 500 ( Figure 5 ), user specific field 600 ( Figure 6 ), and / or user field 700 ( Figure 7 ) can be configured to provide a technical solution to support the use of only one user field for each user, for example, while the UEM field may not need to carry the STA-ID subfield for blind scanning. Therefore, the user field 500 ( Figure 5 ), user specific field 600 ( Figure 6 ), and / or user field 700 ( Figure 7 ) can be configured to provide a technical solution to save a large number of bits, thereby reducing overhead.

[0477] In some exemplary aspects, user field 500 ( Figure 5 ), user specific field 600 ( Figure 6 ), and / or user field 700 ( Figure 7 ) can be configured to provide a technical solution to be implemented by future and / or new protocols and / or specifications, for example, for Wi-Fi 8 (UHR).

[0478] refer to Figure 8 , which schematically illustrates a method for transmitting UEM information according to some exemplary aspects. For example, Figure 8 One or more operations of the method may be performed by a system (e.g., system 100 ( Figure 1 )) is performed by one or more elements, such as one or more wireless devices, such as device 102 ( Figure 1 )、device 140( Figure 1 ), and / or device 160 ( Figure 1 ), a controller, for example, controller 124 ( Figure 1 ) and / or controller 154 ( Figure 1 ), radio stations, such as radio station 114 ( Figure 1 ) and / or Radio 144 ( Figure 1 ), and / or a message processor, such as message processor 128 ( Figure 1 ) and / or message processor 158 ( Figure 1 ).

[0479] As shown at block 802, the method may include setting RU allocation information in the SIG field at the AP. For example, the RU allocation information may be configured to indicate the RU allocation of the user. For example, the controller 124 ( Figure 1 ) may be configured to cause, trigger, and / or control device 102 ( Figure 1 )Set RU allocation information in the SIG field, for example, to indicate the RU allocation of the user, for example, as described above.

[0480] As shown at block 804, the method may include setting the user's UEM information in the SIG field. For example, the user's UEM information may be configured to indicate that multiple MCSs are assigned to multiple frequency subchannels in the RU allocation of the user. For example, the controller 124 ( Figure 1 ) may be configured to cause, trigger, and / or control device 102 ( Figure 1 )Set the user's UEM information in the SIG field, for example, to indicate the assignment of multiple MCSs to multiple frequency subchannels in the user's RU allocation, for example, as described above.

[0481] As shown at block 806, the method may include sending a DL PPDU including a SIG field and a user's data field. For example, the user's data field may be configured based on an assignment of multiple frequency subchannels in an RU allocation that assigns multiple MCSs to the user. For example, the controller 124 ( Figure 1 ) may be configured to cause, trigger, and / or control device 102 ( Figure 1 ) sends a DL PPDU including a SIG field and a user's data field, for example, as described above.

[0482] refer to Fig. 9 , which schematically illustrates a method for transmitting UEM information according to some exemplary aspects. For example, Fig. 9 One or more operations of the method may be performed by a system (e.g., system 100 ( Figure 1 )) is performed by one or more elements, such as one or more wireless devices, such as device 102 ( Figure 1 )、device 140( Figure 1 ), and / or device 160 ( Figure 1 ), a controller, for example, controller 124 ( Figure 1 ) and / or controller 154 ( Figure 1 ), radio stations, such as radio station 114 ( Figure 1 ) and / or Radio 144 ( Figure 1 ), and / or a message processor, such as message processor 128 ( Figure 1 ) and / or message processor 158 ( Figure 1 ).

[0483] As shown at block 902, the method may include identifying, at the user STA, the RU allocation of the user STA based on the RU allocation information in the SIG field of the DL PPDU. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger, and / or control device 140 ( Figure 1 ) identifies device 140 based on RU allocation information in the SIG field of the DL PPDU ( Figure 1 )'s RU allocation, for example, as described above.

[0484] As shown at block 904, the method may include processing the UE information of the user STA in the SIG field to identify the assignment of multiple frequency subchannels in the RU allocation that assigns multiple MCSs to the user STA respectively. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger, and / or control device 140 ( Figure 1 ) Processing device 140 in the SIG field ( Figure 1 ) to identify the multiple MCSs assigned to the device 140 ( Figure 1 )'s assignment of multiple frequency subchannels in an RU allocation, for example, as described above.

[0485] As shown at block 906, the method may include processing a data field of a user STA in a DL PPDU based on an assignment of multiple MCSs to multiple frequency subchannels in an RU allocation of the user STA. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger, and / or control device 140 ( Figure 1 ) based on assigning multiple MCSs to device 140 ( Figure 1 ) to process the device 140 ( Figure 1 ) data field, for example, as described above.

[0486] refer to Fig.10 , which schematically illustrates an article 1000 of manufacture according to some exemplary aspects. Article 1000 may include one or more tangible computer-readable ("machine-readable") non-transitory storage media 1002, which may include computer-executable instructions, such as instructions implemented by logic 1004, which, when executed by at least one computer processor, are operable to enable the at least one computer processor to perform operations on a device 102 ( Figure 1 )、device 140( Figure 1 )、Device 160( Figure 1 )、Controller 124( Figure 1 )、Controller 154( Figure 1)、Message processor 128( Figure 1 ), message processor 158 ( Figure 1 )、Radio 114( Figure 1 )、Radio 144( Figure 1 )、Transmitter 118( Figure 1 )、Transmitter 148( Figure 1 ), receiver 116 ( Figure 1 ), and / or receiver 146 ( Figure 1 ) to implement one or more operations; so that device 102 ( Figure 1 )、device 140( Figure 1 )、Device 160( Figure 1 )、Controller 124( Figure 1 )、Controller 154( Figure 1 )、Message processor 128( Figure 1 ), message processor 158 ( Figure 1 )、Radio 114( Figure 1 )、Radio 144( Figure 1 )、Transmitter 118( Figure 1 )、Transmitter 148( Figure 1 ), receiver 116 ( Figure 1 ), and / or receiver 146 ( Figure 1 ) execute, trigger, and / or implement one or more operations and / or functions; and / or execute, trigger, and / or implement reference Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , and / or Fig. 9 One or more operations and / or functions described herein, and / or one or more operations described herein. The phrases "non-transitory machine-readable medium" and "computer-readable non-transitory storage medium" may be directed to include all machine- and / or computer-readable media, with the only exception being transitory propagating signals.

[0487] In some exemplary aspects, the product 1000 and / or the machine-readable storage medium 1002 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, writable or rewritable memory, etc. For example, the machine-readable storage medium 1002 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, disk, hard drive, etc. Computer-readable storage media may include any appropriate media that participates in downloading or transferring a computer program carried in a data signal embodied in a carrier wave or other propagation medium from a remote computer to a requesting computer via a communication link (e.g., a modem, radio, or network connection).

[0488] In some exemplary aspects, logic 1004 may include instructions, data, and / or code that, when executed by a machine, may cause the machine to perform methods, processes, 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, etc., and may be implemented using any suitable combination of hardware, software, firmware, etc.

[0489] In some exemplary aspects, logic 1004 may include or may be implemented as software, a software module, an application, a program, a subroutine, an instruction, an instruction set, a computing code, a word, a value, a symbol, and the like. Instructions may include any suitable type of code, such as source code, compiled code, parsed code, executable code, static code, dynamic code, and the like. Instructions may be implemented according to a predefined computer language, manner, or syntax for instructing a processor to perform a specific function. Instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled, and / or parsed programming language, machine code, and the like.

[0490] Example

[0491] The following examples relate to further aspects.

[0492] Example 1 includes a device comprising logic and circuits configured to enable an access point (AP) to set resource unit (RU) allocation information in a signal (SIG) field, the RU allocation information being configured to indicate a user's RU allocation; to set the user's unequal modulation and coding scheme (MCS) (UEM) information in the SIG field, the user's UEM information being configured to indicate an assignment of multiple MCSs to multiple frequency subchannels in the user's RU allocation, respectively; and to send a downlink (DL) physical layer (PHY) protocol data unit (PPDU) comprising the SIG field and the user's data field, wherein the user's data field is configured according to the assignment of the multiple MCSs to multiple frequency subchannels in the user's RU allocation.

[0493] Example 2 includes the subject matter of Example 1, and optionally, wherein the apparatus is configured to cause the AP to set a user field of the user and at least one UEM field of the user in the SIG field, wherein the user field of the user is configured to indicate that the user has a UEM assignment, and wherein the at least one UEM field of the user includes UEM information of the user.

[0494] Example 3 includes the subject matter of Example 2, and optionally, wherein the apparatus is configured to cause the AP to set a predefined MCS type value in an MCS type subfield in a user field of the user, the predefined MCS type value indicating that the user has the UEM assignment.

[0495] Example 4 includes the subject matter of Example 3, and optionally, wherein the predefined MCS type value is configured to indicate the UEM assigned type from a plurality of predefined UEM assigned types.

[0496] Example 5 includes the subject matter of Example 4, and optionally, wherein the plurality of predefined UEM assignment types include at least one of: UEM assignment on a frequency subchannel, UEM assignment on a spatial stream, or UEM assignment on both a frequency subchannel and a spatial stream.

[0497] Example 6 includes the subject matter of any of Examples 3-5, and optionally, wherein the MCS type subfield has a size of 2 bits.

[0498] Example 7 includes the subject matter of any one of Examples 3-6, and optionally, wherein the apparatus is configured to cause the AP to set a UEM field indicator subfield in a user field of the user, wherein the UEM field indicator subfield is configured to indicate a position of a first UEM field of at least one UEM field of the user in the SIG field.

[0499] Example 8 includes the subject matter of any of Examples 3-7, and optionally, wherein the at least one UEM field of the user is configured according to a UEM field format including a plurality of MCS subfields.

[0500] Example 9 includes the subject matter of Example 8, and optionally, wherein a first-order UEM field in at least one UEM field of the user includes a frequency fragment subfield configured to indicate a division of the user's RU allocation into the multiple frequency subchannels.

[0501] Example 10 includes the subject matter of any one of Examples 3-9, and optionally, wherein the apparatus is configured to cause the AP to set the spatial configuration subfield in the user field of the user to indicate the assignment of multiple spatial streams to the user, wherein the UEM information of the user is configured to indicate the assignment of the multiple MCSs to the multiple spatial streams on the multiple frequency subchannels.

[0502] Example 11 includes the subject matter of Example 10, and optionally, wherein the at least one UEM field of the user includes multiple UEM fields of the user, wherein a UEM field in the multiple UEM fields of the user includes frequency channel-specific UEM information corresponding to a frequency subchannel in the multiple frequency subchannels.

[0503] Example 12 includes the subject matter of Example 11, and optionally, wherein the frequency channel specific UE M information comprises a plurality of frequency channel specific MCSs for a plurality of spatial streams on the frequency subchannel.

[0504] Example 13 includes the subject matter of any of Examples 10-12, and optionally, wherein the at least one UEM field of the user includes a first UEM field and a second UEM field, wherein the first UEM field includes a first plurality of MCSs for multiple spatial streams on a first frequency subchannel, and wherein the second UEM field includes a second plurality of MCSs for multiple spatial streams on a second frequency subchannel.

[0505] Example 14 includes the subject matter of Example 2, and optionally, wherein the apparatus is configured to cause the AP to set a predefined MCS index in an MCS subfield in a user field of the user, wherein the predefined MCS index is configured to indicate that the user has the UEM assignment.

[0506] Example 15 includes the subject matter of Example 14, and optionally, wherein the predefined MCS index is 14.

[0507] Example 16 includes the subject matter of Example 14 or 15, and optionally, wherein at least one UEM field of the user is configured according to a UEM field format, the UEM field format including a station (STA) identifier (ID) (STA-ID) field used to identify the user and multiple MCS subfields following the STA-ID field.

[0508] Example 17 includes the subject matter of any one of Examples 14-16, and optionally, wherein the apparatus is configured to cause the AP to set the spatial configuration subfield in the user field of the user to indicate the assignment of multiple spatial streams to the user, wherein the UEM information of the user is configured to indicate the assignment of the multiple MCSs to the multiple spatial streams on the multiple frequency subchannels.

[0509] Example 18 includes the subject matter of any of Examples 2-17, and optionally, wherein the apparatus is configured to cause the AP to encode at least one UEM field of the user into one or more UEM coding blocks according to a UEM coding block format, wherein the UEM coding block format includes a UEM coding block including two UEM fields and a cyclic redundancy check (CRC) field based on the two UEM fields.

[0510] Example 19 includes the subject matter of any of Examples 2-18, and optionally, wherein the at least one UEM field of the user follows all user fields in the SIG field.

[0511] Example 20 includes the subject matter as described in Example 1, and optionally, wherein the device is configured to cause the AP to set the UEM information of the user in multiple user fields of the user in the SIG field, and the multiple user fields of the user are configured to indicate the multiple MCSs respectively.

[0512] Example 21 includes the subject matter of Example 20, and optionally, wherein a user field among the multiple user fields of the user includes a STA-ID field including a station (STA) identifier (ID) (STA-ID) used to identify the user and an MCS field including an MCS among the multiple MCSs.

[0513] Example 22 includes the subject matter of Example 20 or 21, and optionally, wherein each of the plurality of user fields for the user comprises a same station (STA) identifier (ID) (STA-ID) used to identify the user.

[0514] Example 23 includes the subject matter of any one of Examples 20-22, and optionally, wherein the apparatus is configured to cause the AP to set the RU allocation information to indicate an allocation of multiple sub-RUs to the user, wherein the multiple sub-RUs of the user respectively include multiple frequency sub-channels.

[0515] Example 24 includes the subject matter of any of Examples 20-23, and optionally, wherein the apparatus is configured to cause the AP to set the multiple user fields of the user to indicate the multiple MCSs according to an order of multiple frequency subchannels in an RU allocation to the user.

[0516] Example 25 includes the subject matter of any of Examples 20-24, and optionally, wherein a first-order user field among the multiple user fields of the user includes a station (STA) identifier (ID) (STA-ID) field, an MCS field after the STA-ID field, and a space configuration field after the MCS field.

[0517] Example 26 includes the subject matter of any of Examples 20-25, and optionally, wherein a bit size of a user field in the plurality of user fields for the user is equal to a predefined bit size of a user field for a user having a single MCS assignment.

[0518] Example 27 includes the subject matter of any of Examples 20-26, and optionally, wherein a user field in the plurality of user fields for the user has a bit size of 22 bits.

[0519] Example 28 includes the subject matter of any of Examples 1-27, and optionally, wherein the SIG field comprises an Extremely High Throughput (EHT) SIG (EHT-SIG) field.

[0520] Example 29 includes the subject matter of any of Examples 1-28, and optionally, wherein the DL PPDU comprises a multi-user (MU) PPDU for a plurality of users including the user.

[0521] Example 30 includes the subject matter of any of Examples 1-28, and optionally, wherein the DL PPDU comprises a single user (SU) PPDU for the user.

[0522] Example 31 includes the subject matter of any of Examples 1-30, and optionally, wherein the DL PPDU comprises an extremely high throughput (EHT) DL PPDU.

[0523] Example 32 includes the subject matter of any of Examples 1-31, and optionally, wherein the DL PPDU comprises an ultra high reliability (UHR) DL PPDU.

[0524] Example 33 includes the subject matter of any of Examples 1-32, and optionally, comprising at least one radio station to transmit the DL PPDU.

[0525] Example 34 includes the subject matter of Example 33, and optionally, includes one or more antennas coupled to the radio station and a processor to execute instructions of an operating system of the AP.

[0526] Example 35 includes a device comprising logic and circuits configured to enable a user station (STA) to identify a downlink (DL) physical layer (PHY) protocol data unit (PPDU) based on resource unit (RU) allocation information in a signal (SIG) field of the user STA; process the unequal modulation and coding scheme (MCS) (UEM) information of the user STA in the SIG field to identify an assignment of multiple MCSs to multiple frequency subchannels in the RU allocation of the user STA; and process a data field of the user STA in the DL PPDU based on the assignment of the multiple MCSs to the multiple frequency subchannels in the RU allocation of the user STA.

[0527] Example 36 includes the subject matter of Example 35, and optionally, wherein the apparatus is configured to cause the user STA to process a user field of the user STA and at least one UEM field of the user STA in the SIG field to identify that the user STA has a UEM assignment, wherein the at least one UEM field of the user STA includes UEM information of the user STA.

[0528] Example 37 includes the subject matter of Example 36, and optionally, wherein the apparatus is configured to cause the user STA to identify that the user STA has the UEM assignment based on a predefined MCS type value in an MCS type subfield in a user field of the user STA.

[0529] Example 38 includes the subject matter of Example 37, and optionally, wherein the predefined MCS type value is configured to indicate the UEM assigned type from a plurality of predefined UEM assigned types.

[0530] Example 39 includes the subject matter of Example 38, and optionally, wherein the plurality of predefined UEM assignment types include at least one of: UEM assignment on a frequency subchannel, UEM assignment on a spatial stream, or UEM assignment on both a frequency subchannel and a spatial stream.

[0531] Example 40 includes the subject matter of any of Examples 37-39, and optionally, wherein the MCS type subfield has a size of 2 bits.

[0532] Example 41 includes the subject matter of any of Examples 37-40, and optionally, wherein the apparatus is configured to cause the user STA to identify a position of a first UEM field of at least one UEM field of the user STA in the SIG field based on a UEM field indicator field in a user field of the user STA.

[0533] Example 42 includes the subject matter of any of Examples 37-41, and optionally, wherein at least one UEM field of the user STA is configured according to a UEM field format including a plurality of MCS subfields.

[0534] Example 43 includes the subject matter of Example 42, and optionally, wherein a first-order UEM field in at least one UEM field of the user STA includes a frequency fragment subfield configured to indicate a division of the RU allocation of the user STA into the multiple frequency subchannels.

[0535] Example 44 includes the subject matter of any one of Examples 37-43, and optionally, wherein the apparatus is configured to enable the user STA to identify an assignment of multiple spatial streams to the user STA based on a spatial configuration subfield in a user field of the user STA, wherein the UEM information of the user STA is configured to indicate an assignment of the multiple MCSs to the multiple spatial streams on the multiple frequency subchannels.

[0536] Example 45 includes the subject matter of Example 44, and optionally, wherein at least one UEM field of the user STA includes multiple UEM fields of the user STA, wherein a UEM field in the multiple UEM fields of the user STA includes frequency channel-specific UEM information corresponding to a frequency subchannel in the multiple frequency subchannels.

[0537] Example 46 includes the subject matter of Example 45, and optionally, wherein the frequency channel specific UE M information comprises a plurality of frequency channel specific MCSs for a plurality of spatial streams on the frequency subchannel.

[0538] Example 47 includes the subject matter of any of Examples 44-46, and optionally, wherein at least one UEM field of the user STA includes a first UEM field and a second UEM field, wherein the first UEM field includes a first plurality of MCSs for multiple spatial streams on a first frequency subchannel, and wherein the second UEM field includes a second plurality of MCSs for multiple spatial streams on a second frequency subchannel.

[0539] Example 48 includes the subject matter of Example 36, and optionally, wherein the apparatus is configured to cause the user STA to identify that the user has the UE M assignment based on a predefined MCS index in an MCS subfield in a user field of the user STA.

[0540] Example 49 includes the subject matter of Example 48, and optionally, wherein the predefined MCS index is 14.

[0541] Example 50 includes the subject matter of Example 48 or 49, and optionally, wherein at least one UEM field of the user STA is configured according to a UEM field format, the UEM field format including a station (STA) identifier (ID) (STA-ID) field used to identify the user STA and multiple MCS subfields after the STA-ID field.

[0542] Example 51 includes the subject matter of any one of Examples 48-50, and optionally, wherein the apparatus is configured to enable the user STA to identify an assignment of multiple spatial streams to the user STA based on a spatial configuration subfield in a user field of the user STA, wherein the UEM information of the user STA is configured to indicate an assignment of the multiple MCSs to the multiple spatial streams on the multiple frequency subchannels.

[0543] Example 52 includes the subject matter of any one of Examples 36-51, and optionally, wherein the apparatus is configured to cause the user STA to decode at least one UEM field of the user STA from one or more UEM coding blocks according to a UEM coding block format, wherein the UEM coding block format includes a UEM coding block including two UEM fields and a cyclic redundancy check (CRC) field based on the two UEM fields.

[0544] Example 53 includes the subject matter of any of Examples 36-52, and optionally, wherein at least one UE M field of the user STA follows all user fields in the SIG field.

[0545] Example 54 includes the subject matter of Example 35, and optionally, wherein the apparatus is configured to enable the user STA to identify the UEM information of the user in a plurality of user fields of the user in the SIG field, the plurality of user fields of the user being configured to indicate the plurality of MCSs respectively.

[0546] Example 55 includes the subject matter of Example 54, and optionally, wherein a user field among the multiple user fields of the user STA includes a STA-ID field including a station (STA) identifier (ID) (STA-ID) used to identify the user STA and an MCS field including an MCS among the multiple MCSs.

[0547] Example 56 includes the subject matter of Example 54 or 55, and optionally, wherein each of the plurality of user fields of the user STA comprises a same station (STA) identifier (ID) (STA-ID) used to identify the user STA.

[0548] Example 57 includes the subject matter of any one of Examples 54-56, and optionally, wherein the apparatus is configured to cause the user STA to process the RU allocation information to identify an allocation of multiple sub-RUs to the user STA, wherein the multiple sub-RUs of the user respectively include multiple frequency sub-channels.

[0549] Example 58 includes the subject matter of any of Examples 54-57, and optionally, wherein the apparatus is configured to cause the user STA to process the multiple user fields of the user to identify the multiple MCSs based on an order of multiple frequency subchannels in an RU allocation of the user STA.

[0550] Example 59 includes the subject matter of any one of Examples 54-58, and optionally, wherein a first-order user field among the multiple user fields of the user STA includes a station (STA) identifier (ID) (STA-ID) field, an MCS field after the STA-ID field, and a space configuration field after the MCS field.

[0551] Example 60 includes the subject matter of any of Examples 54-59, and optionally, wherein a bit size of a user field in the plurality of user fields of the user STA is equal to a predefined bit size of a user field of a user STA having a single MCS assignment.

[0552] Example 61 includes the subject matter of any of Examples 54-60, and optionally, wherein a user field of the plurality of user fields of the user STA has a bit size of 22 bits.

[0553] Example 62 includes the subject matter of any of Examples 35-61, and optionally, wherein the SIG field comprises an Extremely High Throughput (EHT) SIG (EHT-SIG) field.

[0554] Example 63 includes the subject matter of any of Examples 35-62, and optionally, wherein the DL PPDU comprises a multi-user (MU) PPDU for multiple users including the user STA.

[0555] Example 64 includes the subject matter of any of Examples 35-62, and optionally, wherein the DL PPDU comprises a single user (SU) PPDU for the user STA.

[0556] Example 65 includes the subject matter of any of Examples 35-64, and optionally, wherein the DL PPDU comprises an extremely high throughput (EHT) DL PPDU.

[0557] Example 66 includes the subject matter of any of Examples 35-65, and optionally, wherein the DL PPDU comprises an ultra high reliability (UHR) DL PPDU.

[0558] Example 67 includes the subject matter of any of Examples 35-66, and optionally, comprising at least one radio station to receive the DL PPDU.

[0559] Example 68 includes the subject matter of Example 67, and optionally, includes one or more antennas coupled to the radio station and a processor executing instructions of an operating system of the user STA.

[0560] Example 69 includes a wireless communication device comprising an apparatus as described in any of Examples 1-68.

[0561] Example 70 includes a mobile device comprising an apparatus as described in any of Examples 1-68.

[0562] Example 71 includes an apparatus comprising means for performing any of the described operations of any of Examples 1-68.

[0563] Example 72 includes a product comprising one or more tangible computer-readable non-transitory storage media, the media comprising instructions that, when executed by at least one processor, are operable to cause the at least one processor to cause a wireless communication device to perform any operations described in any of Examples 1-68.

[0564] Example 73 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any operations described in any of Examples 1-68.

[0565] Example 74 includes a method comprising the operations of any of the descriptions of any of Examples 1-68.

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

[0567] While certain features have been illustrated and described herein, numerous modifications, substitutions, changes, and equivalents will 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 that fall within the true spirit of the disclosure.

Claims

1. An apparatus comprising a controller configured to cause an access point (AP): Setting resource unit (RU) allocation information in a signal (SIG) field, wherein the RU allocation information is configured to indicate RU allocation of a user; Setting unequal modulation and coding scheme (MCS) (UEM) information of the user in the SIG field, the UEM information of the user being configured to indicate assignment of multiple MCSs to multiple frequency subchannels in an RU allocation of the user, respectively; and sending a downlink (DL) physical layer (PHY) protocol data unit (PPDU) including the SIG field and the data field of the user, wherein: The data field of the user is configured according to the assignment of the multiple frequency subchannels in the RU allocation that assigns the multiple MCSs to the user.

2. The apparatus according to claim 1, configured to cause the AP to set a user field of the user and at least one UEM field of the user in the SIG field, wherein: The user fields of the user are configured to indicate that the user has a UEM designation, wherein at least one UEM field of the user includes UEM information of the user.

3. The apparatus of claim 2, configured to cause the AP to set a predefined MCS type value in an MCS type subfield in a user field of the user, the predefined MCS type value indicating that the user has the UEM assignment.

4. The device according to claim 3, wherein: The predefined MCS type value is configured to indicate the UEM assigned type from a plurality of predefined UEM assigned types.

5. The device according to claim 4, wherein: The plurality of predefined UEM assignment types include at least one of: UEM assignment on a frequency subchannel, UEM assignment on a spatial stream, or UEM assignment on both a frequency subchannel and a spatial stream.

6. The apparatus of claim 3, configured to cause the AP to set a UEM field indicator subfield in a user field of the user, wherein: The UEM field indicator subfield is configured to indicate a position of a first UEM field of the at least one UEM field of the user in the SIG field.

7. The device of claim 3, wherein: The at least one UEM field of the user is configured according to a UEM field format including a plurality of MCS subfields.

8. The device according to claim 7, wherein: A first-order UEM field in the at least one UEM field of the user includes a frequency fragment subfield configured to indicate a division of the RU allocation of the user into the plurality of frequency subchannels.

9. The apparatus of claim 3, configured to cause the AP to set a spatial configuration subfield in a user field of the user to indicate assignment of multiple spatial streams to the user, wherein: The UEM information of the user is configured to indicate an assignment of the plurality of MCSs to the plurality of spatial streams on the plurality of frequency subchannels.

10. The device of claim 9, wherein: The at least one UEM field of the user includes a plurality of UEM fields of the user, wherein a UEM field of the plurality of UEM fields of the user includes frequency channel specific UEM information corresponding to a frequency subchannel of the plurality of frequency subchannels.

11. The device of claim 10, wherein: The frequency channel specific UE M information includes a plurality of frequency channel specific MCSs for a plurality of spatial streams on the frequency subchannel.

12. The device of claim 10, wherein: The at least one UEM field of the user includes a first UEM field and a second UEM field, wherein the first UEM field includes a first plurality of MCSs for multiple spatial streams on a first frequency subchannel, and wherein the second UEM field includes a second plurality of MCSs for multiple spatial streams on a second frequency subchannel.

13. The apparatus of claim 2, configured to cause the AP to set a predefined MCS index in an MCS subfield in a user field of the user, wherein: The predefined MCS index is configured to indicate that the user has the UE M assignment.

14. The device of claim 2, wherein: At least one UEM field of the user follows all user fields in the SIG field.

15. The apparatus according to claim 1, configured to enable the AP to set the UE M information of the user in a plurality of user fields of the user in the SIG field, wherein the plurality of user fields of the user are configured to indicate the plurality of MCSs respectively.

16. The device of claim 15, wherein: Each of the plurality of user fields for the user includes a same station (STA) identifier (ID) (STA-ID) used to identify the user.

17. The apparatus according to any one of claims 1 to 16, comprising at least one radio station to transmit the DLPPDU.

18. The apparatus of claim 17, comprising one or more antennas coupled to the radio station and a processor to execute instructions of an operating system.

19. A method performed at an access point (AP), the method comprising: Setting resource unit (RU) allocation information in a signal (SIG) field, wherein the RU allocation information is configured to indicate RU allocation of a user; Setting unequal modulation and coding scheme (MCS) (UEM) information of the user in the SIG field, the UEM information of the user being configured to indicate assignment of multiple MCSs to multiple frequency subchannels in an RU allocation of the user, respectively; and A downlink (DL) physical layer (PHY) protocol data unit (PPDU) is sent including the SIG field and a data field of the user, wherein the data field of the user is configured according to an assignment of the multiple MCSs to multiple frequency subchannels in an RU allocation of the user.

20. The method of claim 19, comprising: A user field of the user and at least one UEM field of the user are set in the SIG field, wherein the user field of the user is configured to indicate that the user has a UEM assignment, wherein the at least one UEM field of the user includes UEM information of the user.

21. The method of claim 20, comprising: A predefined MCS type value is set in an MCS type subfield in a user field of the user, the predefined MCS type value indicating that the user has the UEM assignment.

22. The method of claim 20, comprising: A UEM field indicator subfield in the user field of the user is set, wherein the UEM field indicator subfield is configured to indicate a position of a first UEM field in the at least one UEM field of the user in the SIG field.

23. The method of claim 19, comprising: The UEM information of the user is set in a plurality of user fields of the user in the SIG field, and the plurality of user fields of the user are configured to indicate the plurality of MCSs respectively.

24. A product comprising one or more tangible computer-readable non-transitory storage media, the media comprising instructions that, when executed by at least one processor, are operable to enable the at least one processor to cause an access point (AP) to perform the method of any one of claims 19 to 23.

25. An apparatus comprising means for causing an access point (AP) to perform the method of any one of claims 19 to 23.

Images