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 of a user station (STA) in a user information (info) field of the user STA, the RU allocation information of the user STA configured to indicate an RU allocation for a trigger-based (TB) uplink (UL) transmission from the user STA; determining unequal modulation and coding scheme (MCS) (UEM) information of the user STA, the UEM information of the user STA configured to indicate an assignment of a plurality of UL resources in an RU allocation that assigns a plurality of MCSs to the user STA, respectively, where the plurality of UL resources include at least one of a plurality of frequency sub-channels or a plurality of spatial streams; and transmitting a trigger frame including a user information field of the user STA and UEM information of the user STA.

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 user information (info) list fields according to some exemplary aspects.

[0006] Figure 3 is a schematic illustration of an Extremely High Throughput (EHT) variant user information field format that may be implemented according to some exemplary aspects.

[0007] Figure 4 is a schematic illustration of user information list fields according to some exemplary aspects.

[0008] Figure 5 is a schematic illustration of an Unequal Modulation and Coding Scheme (MCS) (UEM) signaling format according to some demonstrative aspects.

[0009] Figure 6 is a schematic illustration of a UEM signaling format according to some exemplary aspects.

[0010] Figure 7 is a schematic illustration of signaling of UEM field locations according to some demonstrative 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.10 is 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 of ordinary skill 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 its future versions and / or derivatives, devices and / or networks operating in accordance with existing cellular specifications and / or protocols and / or their future versions and / or derivatives, units and / or devices that are 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 a communication signal includes sending a communication signal and / or receiving a communication signal. 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, such as 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 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 occur.

[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, eg, 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, such as 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, such as 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 demonstrative 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, function as one or more non-AP STAs, and / or perform 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, function as at least one non-AP STA, and / or perform 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, function as at least one non-AP STA, and / or perform 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 a primary channel and one or more secondary channels, utilizing the same MCS for the entire RU / MRU assigned to the user may result in low throughput.

[0093] For example, the RU / MRU assigned to a user may be affected by different Signal-to-Noise Ratio (SNR) conditions for different frequencies, for example, due to interference and / or varying sensitivity to primary and secondary channels.

[0094] For example, utilizing 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 employ 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, employing 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.

[0095] 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 (UEM) allocation scheme"), which may be configured to assign multiple MCSs, e.g., including two or more different MCSs, to multiple wireless resources, e.g., multiple different segments, in RU / MRU allocations to a user, e.g., as described below.

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

[0097] In some exemplary aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support improving the throughput of a Wi-Fi system.

[0098] In some exemplary aspects, the unequal MCS allocation scheme may be configured to provide a technical solution to support increased throughput, for example, when wireless resources (e.g., spatial streams and / or frequency subchannels) are affected by different (e.g., significantly different) wireless environments and / or conditions (e.g., varying SNR conditions).

[0099] 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.

[0100] 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.

[0101] For example, when MIMO technology is applied, multiple spatial streams may be implemented to enhance throughput, eg, when multiple data streams may occur simultaneously on the same wireless channel.

[0102] For example, MIMO gain may vary across different spatial streams, which may result in varying SNR conditions. According to this example, unequal MCS across spatial streams may be configured to provide a technical solution to adaptively assign different MCSs to different spatial streams, for example, to accommodate different SNRs.

[0103] 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.

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

[0105] 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.

[0106] 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 subchannels and spatial streams, e.g., in uplink (UL) transmissions, e.g., as described below.

[0107] In some exemplary aspects, it may be desirable to provide a technical solution to support signaling of unequal MCS assignments for UL resources. For example, some trigger frame formats and / or fields, such as the trigger frame format according to the IEEE 802.11be specification, may only support assigning a single MCS to each user, such that the user can only use a single MCS for trigger-based (TB) UL transmissions.

[0108] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS allocation scheme, which may be configured to provide a technical solution to support signaling of unequal MCS assignments on multiple frequency subchannels and / or spatial streams, for example, in TB UL transmissions, for example, as described below.

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

[0110] In some exemplary aspects, an unequal MCS signaling mechanism may utilize one or more user information (info) fields in a trigger frame, for example, according to a new user-specific field format, which may be configured to implement unequal MCS on multiple frequency subchannels and / or spatial streams, for example, in a TB UL transmission, for example, as described below.

[0111] In some exemplary aspects, the unequal MCS signaling mechanism may utilize one or more user information (info) fields in a trigger frame to assign multiple MCSs, e.g., different MCSs, to multiple UL resources, e.g., different UL resources in a RU / MRU, for example, as described below.

[0112] In some exemplary aspects, the unequal MCS signaling mechanism may utilize one or more user information (info) fields in a trigger frame to assign multiple MCSs, e.g., different MCSs, to multiple frequency subchannels, e.g., different frequency subchannels in a RU / MRU, for example, as described below.

[0113] In some exemplary aspects, an unequal MCS signaling mechanism may utilize one or more user information fields in a trigger frame to assign multiple MCSs, e.g., different MCSs, to multiple spatial streams, e.g., different spatial streams, e.g., where MIMO is applied, e.g., as described below.

[0114] In some demonstrative aspects, a unequal MCS signaling mechanism may utilize one or more user information fields in a trigger frame to assign multiple MCSs to both frequency subchannels and spatial streams, e.g., as described below.

[0115] In some exemplary aspects, an unequal MCS signaling mechanism may utilize one or more trigger frames that may be configured according to a trigger frame format, e.g., a new trigger frame format, which may be configured to apply (e.g., adaptively apply) unequal MCS to multiple UL resources, e.g., including frequency subchannels (e.g., different frequency subchannels) and / or spatial streams, e.g., as described below.

[0116] In some exemplary aspects, the unequal MCS signaling mechanism can be a triggered frame format that can be configured to signal unequal MCS to be applied to multiple UL resources (e.g., frequency subchannels and / or spatial streams) within a changing wireless environment, such as in a triggered PPDU UL transmission, for example, as described below.

[0117] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more user information fields of a trigger frame, which may be configured to inform a user whether the user is an unequal MCS user or a non-unequal MCS user, e.g., as described below.

[0118] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more user information fields of a trigger frame, which may be configured to provide information to a user regarding the user's UEM field, e.g., as described below.

[0119] For example, the unequal MCS signaling mechanism may utilize a UEM field, which may be configured to carry (eg, only carry) unequal MCS information.

[0120] In some exemplary aspects, the unequal MCS signaling mechanism may utilize a predefined field in the user information field, such as the EHT-MCS14 subfield, to, for example, signal and / or indicate to a user that the user is a unequal MCS user, e.g., as described below.

[0121] For example, both the user information field and the UEM field may be identified by a user identifier (AID12), for example, to preserve the user information field format, for example, to achieve excellent compatibility with the IEEE 802.11be specification.

[0122] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more subfields in the User Information field, which may be configured to simplify (e.g., effectively simplify) the format of the UEM field, e.g., as described below.

[0123] For example, the format of the UEM field may be simplified to provide a technical solution to avoid inserting AID12 in each UEM field, thereby facilitating resource (bit) conservation and / or low overhead, for example, as described below.

[0124] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more MCS type subfields configured to indicate the MCS type of the user, e.g., as described below.

[0125] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more UEM field indicator subfields, which may be configured to provide the location of the UEM field, e.g., as described below.

[0126] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to provide a technical solution to enable the use of unequal MCS on multiple frequency subchannels and / or spatial streams in TB PPDU UL transmission in a Wi-Fi system.

[0127] For example, the unequal MCS signaling mechanism may be configured to provide a technical solution to enable selection (eg, adaptive selection) of an MCS, eg, to meet varying wireless environments of different frequency subchannels and / or spatial streams, eg, to provide higher throughput.

[0128] In some exemplary aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct the AP implemented by the device 102 to set the RU allocation information of the user (also referred to as "user STA") in the user information (info) field of the user STA, for example, as described below.

[0129] 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.

[0130] In some demonstrative aspects, the RU allocation information of the user STA may be configured to indicate the RU allocation for TB UL transmission from the user STA, for example, as described below.

[0131] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to determine UE M information of a user STA, e.g., as described below.

[0132] In some demonstrative aspects, the UEM information of the user STA may be configured to indicate an assignment of multiple MCSs to multiple UL resources in an RU allocation of the user STA, respectively, for example, as described below.

[0133] In some demonstrative aspects, the plurality of UL resources in the RU allocation of the user STA may include a plurality of frequency subchannels in the RU allocation of the user STA, e.g., as described below.

[0134] In some demonstrative aspects, the multiple UL resources in the RU allocation of the user STA may include multiple spatial streams in the RU allocation of the user STA, e.g., as described below.

[0135] In some demonstrative aspects, the plurality of UL resources may include a plurality of frequency subchannels and a plurality of spatial streams, e.g., as described below.

[0136] In some demonstrative aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by the device 102 to send a trigger frame including a user information field of a user STA and UEM information of the user STA, e.g., as described below.

[0137] In some demonstrative aspects, the trigger frame may include an EHT trigger frame, eg, as described below.

[0138] In some demonstrative aspects, the trigger frame may comprise a UHR trigger frame, eg, as described below.

[0139] In other aspects, the trigger frame may include any other type of frame.

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

[0141] In some demonstrative aspects, at least one UE M field of a user STA may be located after a user information field of the user STA, e.g., as described below.

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

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

[0144] In some demonstrative aspects, the predefined MCS index may be configured to indicate that a user STA has a UE M assignment, e.g., as described below.

[0145] In some demonstrative aspects, the predefined MCS index may include MCS index 14, eg, an EHT MCS 14 index.

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

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

[0148] In some demonstrative aspects, the UEM field format may include a station (STA) identifier (ID) (STA-ID) field to identify a user STA, e.g., as described below.

[0149] In some demonstrative aspects, the UEM field format may include multiple MCS subfields, such as after the STA-ID field, e.g., as described below.

[0150] In other aspects, the UEM field format may include any other additional or alternative subfields.

[0151] 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, which may be configured to, for example, indicate a division of the RU allocation of the user STA into multiple frequency subchannels, for example, as described below.

[0152] In some demonstrative aspects, the bit length of the UEM field (eg, each UEM field) of the user STA may be equal to the bit length of the user information field of the user STA, e.g., as described below.

[0153] In other aspects, the bit length of the UEM field (eg, each UEM field) of a user STA may be any other length.

[0154] In some demonstrative aspects, at least one UEM field of the user STA may be located after all user information fields in the trigger frame, e.g., as described below.

[0155] In some demonstrative aspects, at least one UE M field of a user STA may be located immediately after a user information field of the user STA, e.g., as described below.

[0156] In other aspects, at least one UEM field of the user STA may be located at any other position in the trigger frame.

[0157] In some demonstrative aspects, the trigger frame may include one or more other user information fields following at least one UE M field of the user STA, e.g., as described below.

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

[0159] In some demonstrative aspects, the predefined MCS type value may be configured to indicate that the user STA has a UE M assignment, e.g., as described below.

[0160] In some demonstrative aspects, the MCS type subfield may comprise a single-bit subfield, e.g., as described below.

[0161] In other aspects, the MCS type subfield may include a subfield of any other length.

[0162] In some demonstrative aspects, the predefined MCS type values ​​may include a value of one, e.g., as described below.

[0163] In other aspects, the predefined MCS type values ​​may include any other values.

[0164] 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 information field of a user STA, e.g., as described below.

[0165] 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 STA in a trigger frame, e.g., as described below.

[0166] In some demonstrative aspects, the UEM field indicator subfield may be configured to indicate a distance between a user information field of a user STA and a first UEM field of at least one UEM field of the user STA, e.g., as described below.

[0167] 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.

[0168] 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, which may be configured to, for example, indicate a division of the RU allocation of the user STA into multiple frequency subchannels, for example, as described below.

[0169] In some demonstrative aspects, at least one UEM field for a user STA may be located after all user information fields in a trigger frame, e.g., when a UEM field indicator is used, e.g., as described below.

[0170] In some demonstrative aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by the device 102 to set the UE M information of the user STA in multiple MCS subfields in the user information field of the user STA, for example, as described below.

[0171] 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 information field of a user STA, e.g., as described below.

[0172] In some demonstrative aspects, the spatial configuration subfield in the user information 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.

[0173] In some demonstrative aspects, the UE M information of the user STA may be configured to indicate an assignment of multiple MCSs to multiple spatial streams of the user STA, e.g., as described below.

[0174] In some demonstrative aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by the device 102 to process a UL PPDU from a user STA, for example, according to an assignment of multiple MCSs to multiple UL resources as indicated by UEM information in a trigger frame sent by the AP, for example, as described below.

[0175] In some demonstrative aspects, the controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by the device 102 to determine an assignment of multiple MCSs to multiple UL resources of a user STA, for example, based on wireless communication conditions on the multiple UL resources, for example, as described below.

[0176] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 to set other user information fields in a trigger frame, e.g., as described below.

[0177] In some demonstrative aspects, the other user information field may include other RU allocation information to indicate other RU allocations of other user STAs, e.g., as described below.

[0178] In some demonstrative aspects, the MCS subfield in the other user information field may include an MCS index to indicate the MCS to be applied to the entire RU allocation of other user STAs, e.g., as described below.

[0179] 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 user information field of the user STA in a trigger frame from the AP, for example, to identify RU allocation of the user STA, for example, based on RU allocation information in the user information field of the user STA implemented by the device 140, for example, as described below.

[0180] In some demonstrative aspects, the received trigger frame may comprise a trigger frame sent by an AP implemented by device 102, e.g., as described above.

[0181] 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 UEM information of the user STA in a trigger frame, for example, to identify an assignment of multiple UL resources in an RU allocation that assigns multiple MCSs to the user STA, respectively, for example, as described below.

[0182] In some demonstrative aspects, the plurality of UL resources may comprise a plurality of frequency subchannels in an RU allocation for a user STA, e.g., as described below.

[0183] In some demonstrative aspects, the multiple UL resources may include multiple spatial streams in a RU allocation for a user STA, e.g., as described below.

[0184] 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 send a TB UL transmission from the user STA, for example, based on an assignment of multiple UL resources in an RU allocation that assigns multiple MCSs to the user STA, for example, 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 UEM information of the user STA in at least one UEM field of the user STA, e.g., as described below.

[0186] In some demonstrative aspects, at least one UE M field of a user STA may be located after a user information field of the user STA, e.g., as described below.

[0187] In other aspects, at least one UEM field of the user STA may be located at any other position of the trigger frame.

[0188] 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 process a subfield in a user information field of the user STA to identify that the user STA has a UEM assignment, e.g., as described below.

[0189] 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 recognize that the user STA has a UEM assignment, for example, based on a predefined MCS index in an MCS subfield in a user information field of the user STA, for example, as described below.

[0190] In some demonstrative aspects, the predefined MCS index may include MCS index 14, eg, an EHT MCS 14 index.

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

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

[0193] In some demonstrative aspects, the UEM field format may include a STA-ID field to identify a user STA, e.g., as described below.

[0194] In some demonstrative aspects, the UEM field format may include a plurality of MCS subfields following the STA-ID field, e.g., as described below.

[0195] 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, which may, for example, be configured to indicate a division of the RU allocation of the user STA into multiple frequency subchannels, for example, as described below.

[0196] In some demonstrative aspects, the bit length of the UEM field (eg, each UEM field) of the user STA may be equal to the bit length of the user information field of the user STA, e.g., as described below.

[0197] In other aspects, the UEM field of a user STA may have any other length.

[0198] In some demonstrative aspects, at least one UEM field for a user STA may be located after all user information fields in a trigger frame, e.g., as described below.

[0199] In some demonstrative aspects, at least one UE M field of a user STA may be located immediately after a user information field of the user STA, e.g., as described below.

[0200] In other aspects, at least one UEM field of the user STA may be located at any other position in the trigger frame.

[0201] In some demonstrative aspects, the trigger frame may include one or more other user information fields following at least one UE M field of the user STA, e.g., 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 recognize that the user STA has a UEM assignment, for example, based on a predefined MCS type value in an MCS type subfield in a user information field of the user STA, for example, as described below.

[0203] In some demonstrative aspects, the MCS type subfield may comprise a single-bit subfield, e.g., as described below.

[0204] In some demonstrative aspects, the predefined MCS type value may comprise a value of one.

[0205] In other aspects, the predefined MCS type values ​​may include any other values.

[0206] 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 process a UEM field indicator subfield in a user information field of the user STA, for example, to identify a position of a first UEM field in at least one UEM field of the user STA in a trigger frame, for example, as described below.

[0207] 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 process a UEM field indicator subfield, for example, to identify a distance between a user information field of the user STA and a first UEM field of at least one UEM field of the user STA, for example, as described below.

[0208] 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.

[0209] 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, which may, for example, be configured to indicate a division of the RU allocation of the user STA into multiple frequency subchannels, for example, as described below.

[0210] In some demonstrative aspects, at least one UEM field of the user STA may be located after all user information fields in the trigger frame, for example, when the user information field of the user STA includes a UEM field indicator subfield, for example, as described below.

[0211] 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 the UEM information of the user STA in a plurality of MCS subfields in a user information field of the user STA, e.g., as described below.

[0212] 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 process a spatial configuration subfield in a user information field of the user STA, for example, to identify an assignment of multiple spatial streams to the user STA, for example, as described below.

[0213] 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 process the UEM information of the user STA, for example, to identify an assignment of multiple MCSs to multiple spatial streams, for example, as described below.

[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 the allocation of unequal MCS across multiple frequency subchannels and / or spatial streams, for example, as described below.

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

[0216] In some exemplary aspects, a unequal MCS signaling mechanism may provide a technical solution to support assigning unequal MCS in TB UL transmissions, e.g., as described below.

[0217] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more user information fields, which may be configured to provide information of multiple MCSs to a user, e.g., as described below.

[0218] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more user information fields in a trigger frame, which may be configured to provide unequal MCS information, e.g., as described below.

[0219] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more user information fields in a trigger frame that may be configured for TB PPDU UL transmission with unequal MCS, e.g., as described below.

[0220] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize one or more UEMF fields, which may be configured to provide (e.g., only provide) unequal MCS related information, e.g., as described below.

[0221] For example, the unequal MCS related information may include user ID information (eg, user's AID12), information of minimum RU fragments having different MCSs, multiple MCSs, and / or any other additional or alternative information.

[0222] In some demonstrative aspects, the information carried by the UEM field (e.g., unequal MCS-related information) may vary, for example, based on the format and / or content of the User Information field, e.g., as described below.

[0223] In some demonstrative aspects, the user information field of the user may be configured to convey more specific information about the UEM field, e.g., as described below.

[0224] In some exemplary aspects, a user information field of a user may include information about the location of a corresponding UEM field, and the UEM field may (e.g., may only need to) carry a reduced amount (e.g., a minimum amount) of information, such as information about a minimum RU fragment having a plurality of different MCSs, and / or information about a plurality of MCSs of the user. According to these aspects, the UEM field may not be required to include a user ID (AID12) for identifying the user to which the UEM field belongs, for example, because the user can identify its UEM field based on the location information in the user information field.

[0225] In other aspects, the UEM field may (e.g., should) carry a user ID (AID12) for identifying the user to which the UEM field belongs, for example, when the user's user information field does not include information identifying the location of the user's UEM field, for example, as described below.

[0226] In some exemplary aspects, a unequal MCS user may have multiple UEM fields, e.g., if one UEM field is insufficient to carry all MCSs of the unequal MCS user, e.g., as described below.

[0227] In some exemplary aspects, the user information field and the UEM field may (e.g., should) have the same bit length, for example, to enable a user to identify the start bit and / or end bit of each user information field and / or each UEM field, for example, the position of one or more (e.g., each) of the user information field and / or the UEM field, for example, as described below.

[0228] Some exemplary aspects described herein are directed to a trigger frame including one or more UEM fields to include UEM information of a UEM user, e.g., as described below.

[0229] In other aspects, the trigger frame may be configured to include the user's UEM information in a user information field of the user.

[0230] For example, a trigger frame, such as may be configured according to a new trigger frame type and / or subtype, may be configured to accommodate a relatively long length, which may support a relatively long user information field. According to this example, the user information field of the UEM user may be long enough to accommodate multiple MCS subfields to signal multiple MCSs of the UEM user. According to this example, the trigger frame may be configured to carry the UEM information of the UEM user in multiple MCS subfields in the user information field of the user STA, for example, instead of using the UEM field.

[0231] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to transmit a trigger frame including a user information list field including a plurality of user information fields for a plurality of users, eg, as described below.

[0232] In some demonstrative aspects, the plurality of user information fields may include one or more user information fields for one or more UEM users, e.g., as described below.

[0233] In some demonstrative aspects, the user information field of the UEM user may include RU allocation information to indicate RU allocation for the UEM user, e.g., as described below.

[0234] In some demonstrative aspects, device 102, device 140, and / or device 160 may be configured to transmit a trigger frame including at least one UEM field for a UEM user, e.g., as described below.

[0235] In some demonstrative aspects, the UEM field of the UEM user may include UEM information configured to indicate an assignment of multiple MCSs to multiple UL resources in a RU allocation of the UEM user, respectively, e.g., as described below.

[0236] refer to Figure 2 , which schematically illustrates a user information list field 200 according to some exemplary aspects.

[0237] For example, device 102 ( Figure 1 ) may be configured to generate and / or send a trigger frame including a user information list field 200, which may be configured to include one or more user information fields of one or more users.

[0238] 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 to receive and / or process a trigger frame including a user information list field 200.

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

[0240] For example, the AP may send the RU / MRU allocation information via the user information field of one or more users.

[0241] In some exemplary aspects, the trigger frame may include RU / MRU allocations for multiple users. For example, the multiple users may include user 202 (triggered user 1), user 204 (triggered user 2), user 206 (triggered user 3), and / or user 208 (triggered user 4).

[0242] In some exemplary aspects, such as Figure 2 As shown, user 204 may include a non-UEM user (equal MCS user), whose entire RU / MRU allocation for user 204 may be assigned a single MCS; and / or user 208 may include a non-UEM user, whose entire RU / MRU allocation for user 208 may be assigned a single MCS.

[0243] In some exemplary aspects, such as Figure 2 As shown, user 202 may include a UEM user, and multiple UL resources in the RU / MRU allocation of user 202 may be assigned with multiple MCSs; and / or user 206 may include a UEM user, and multiple UL resources in the RU / MRU allocation of user 206 may be assigned with multiple MCSs.

[0244] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include a user information field 210 for the user 202, which may indicate that the user 202 has a UEM assignment.

[0245] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include two UEM fields of the user 202, for example, the UEM field 220 and the UEM field 222, which may be configured to include the UEM information of the user 202. For example, the UEM information of the user 202 may indicate the assignment of multiple MCSs to multiple UL resources in the RU allocation of the user 202, respectively.

[0246] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include a user information field 212 for the user 204 , for example, after the user information field 210 .

[0247] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include a user information field 214 for the user 206, for example, after the user information field 212. For example, the user information field 214 for the user 206 may indicate that the user 206 has a UEM assignment.

[0248] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include a UEM field 224 of the user 206, which may be configured to include the UEM information of the user 206. For example, the UEM information of the user 206 may indicate the assignment of multiple MCSs to multiple UL resources in the RU allocation of the user 206, respectively.

[0249] In some exemplary aspects, such as Figure 2 As shown, the user information list field 200 in the trigger frame may include a user information field 216 for the user 208 , for example, after the user information field 214 .

[0250] In some demonstrative aspects, a user information field for a non-UEM user, such as the user information field 212 of the non-UEM user 204 and / or the user information field 216 of the non-UEM user 208, may include RU allocation information for the non-UEM user, which may be configured to define the RU allocation for the non-UEM user, and an indication of an MCS (equal MCS) to be applied to the RU allocation for the non-UEM user, for example, in accordance with the IEEE 802.11be specification.

[0251] In some demonstrative aspects, a user information field of a non-UEM user, e.g., the user information field 212 of the non-UEM user 204 and / or the user information field 216 of the non-UEM user 208, may include an EHT variant user information field, e.g., in accordance with the IEEE 802.11be specification.

[0252] refer to Figure 3 , which schematically illustrates an EHT variant user information field 300 that can be implemented according to some exemplary aspects.

[0253] In some exemplary aspects, the user information field 212 ( Figure 2 ) and / or user information field 216 ( Figure 2 ) can be configured according to the format of the EHT variant user information field 300.

[0254] In some exemplary aspects, such as Figure 3 As shown, the EHT variant user information field 300 may include an AID12 subfield 302 that is configured to identify a user, for example, according to the IEEE 802.11be specification. For example, a user (e.g., each user) that receives a trigger frame including the EHT variant user information field 300 may be able to identify its user information field, for example, by looking up the user's identification in the AID12 subfield 302, for example, the user's AID12.

[0255] In some exemplary aspects, such as Figure 3As shown, the EHT variant user information field 300 may include multiple subfields, for example, including a RU allocation subfield 304 and a PS160 subfield 316, which may be configured to indicate to the user the size and / or location of the RU allocated to the user.

[0256] For example, a user (e.g., each user) that receives a trigger frame including the EHT variant user information field 300 may be able to allocate a specific user information field based on the information in the RU allocation subfield 304 and the PS160 subfield 316, for example, together with the special user information field ( Figure 3 The size and / or position of the RU allocated to the user may be identified by using information in a UL BW subfield (eg, a common information field and / or a UL BW extension subfield) in the UE.

[0257] In some exemplary aspects, the EHT variant user information field 300 may support single RU allocation for a user (eg, each user), thereby allowing (eg, may only allow) each user to be assigned one RU / MRU.

[0258] In some exemplary aspects, such as Figure 3 As shown, the EHT variant user information field 300 may include a UL EHT-MCS subfield 308, which may be configured to indicate to the user its assigned MCS, eg, a single MCS to be used over the entire RU / MRU allocation for the user.

[0259] In some exemplary aspects, such as Figure 3 As shown, the EHT variant user information field 300 may include a spatial stream (SS) allocation / RA-RU information subfield 312, which may be configured to indicate to the user its assigned spatial stream (SS).

[0260] For example, the EHT variant user information field 300 may support a single MCS allocation for a user (eg, each user), such that each user may have (eg, may only have) one MCS, which may be represented by a 4-bit MCS index value in the UL EHT-MCS subfield 308.

[0261] Return to reference Figure 2 In some demonstrative embodiments, a UEM field, e.g., all UEM fields, e.g., UEM field 220, UEM field 222, and / or UEM field 224, may (e.g., may always) be located after the user information fields in user information list 200, e.g., after the last user information field 216.

[0262] In some demonstrative aspects, the padding for the trigger frame may (eg, should) be changed to accommodate the addition of one or more UEM fields, which may be added at the end of the user information list 200 of the trigger frame.

[0263] For example, in the case where the user information list only includes user information fields of users with equal MCS, padding bits may follow the last bit of the user information field for the last user.

[0264] In some exemplary aspects, such as Figure 2 As shown, in the case where a user information list (e.g., user information list 200) includes one or more user information fields and UEM fields for users with unequal MCSs, it can be defined that a padding bit can follow the last information field or the last bit of the UEM field for the last user.

[0265] In some exemplary aspects, a user receiving a trigger frame including the user information list 200 may identify its corresponding user information field, for example, by decoding and / or obtaining its user ID (AID12). For example, the user 202 may identify that the user information field 210 is for the user 202, for example, based on identifying that the user information field 210 includes the user ID (AID12) of the user 202; the user 204 may identify that the user information field 212 is for the user 204, for example, based on identifying that the user information field 212 includes the user ID (AID12) of the user 204; the user 206 may identify that the user information field 214 is for the user 206, for example, based on identifying that the user information field 214 includes the user ID (AID12) of the user 206; and / or the user 208 may identify that the user information field 216 is for the user 208, for example, based on identifying that the user information field 216 includes the user ID (AID12) of the user 208.

[0266] In some exemplary aspects, if the user is a non-UEM, the user information field of the user may include a user information field in a format according to a non-UEM user. For example, the user information field 212 and / or the user information field 216 may include the user information field 300 ( Figure 3 ) format, where the UL EHT-MCS subfield 308 ( Figure 3 ) can provide a single MCS for a non-UEM user. According to this example, the non-UEM user can operate as a user (e.g., a traditional user), and such a user can stop reading other fields in the user information list 200 after finding its user information field, for example.

[0267] In some exemplary aspects, where the user is a UEM, the user field of the user may indicate to the user that the user is a UEM user, e.g., as described below. For example, the user information field 210 may include an indication that the user 202 is a UEM user; and / or the user information field 214 may include an indication that the user 206 is a UEM user, e.g., as described below.

[0268] In some demonstrative aspects, the UL EHT-MCS subfield in the User Information field of the UE M user may not provide any MCS for the UE M user, e.g., as described below.

[0269] In some demonstrative aspects, the UL EHT-MCS subfield in the User Information field of the UE M user may be utilized to provide unequal MCS related information for the UE M user, e.g., as described below.

[0270] In some demonstrative aspects, a UL EHT-MCS subfield in a user information field of a UEM user may be utilized to provide an indication that the user of the user information field is a UEM user with a UEM assignment, e.g., as described below.

[0271] In some demonstrative aspects, a UL EHT-MCS subfield in a user information field of a UEM user may be utilized to provide an indication of a UEM field including multiple unequal MCSs assigned to the UEM user, e.g., as described below.

[0272] In some demonstrative aspects, the UL EHT-MCS subfield in the User Information field of the UEM user may be configured to provide a location of a UEM field including a plurality of unequal MCSs assigned to the UEM user, e.g., as described below.

[0273] In some exemplary aspects, the UEM user may identify a user information field of the UEM user, and, for example, after reading the user information field of the UEM user, the UEM user may look for its UEM field to obtain multiple unequal MCSs in the user's RU allocation.

[0274] For example, the UEM user may identify the user information field corresponding to the UEM user by searching for the user information field in the user information list 200 until a user information field including the AID12 of the UEM user is identified in the AID12 subfield of the user information field.

[0275] For example, the user may learn that the user is a UEM user through the UEM related information in the user information field, for example, as described below.

[0276] For example, the UEM user may continue to parse and / or find corresponding UEM fields, for example, until all UEM fields corresponding to the UEM user are obtained. For example, the UEM user may determine that all corresponding UEM fields for the UEM user have been obtained, for example, when the UEM user no longer finds a UEM field that matches its AID 12, rather than stopping parsing once its user information field is found.

[0277] In some exemplary aspects, the UEM field of the UEM user may be identified by the AID 12 of the UEM user, e.g., as described below.

[0278] In some exemplary aspects, the UEM fields of the UEM user may be located and / or precisely located by the user information field of the UEM user, e.g., if the user information field conveys location information of the UEM fields corresponding to the UEM user, e.g., as described below.

[0279] In some demonstrative aspects, the UEM user may find and / or decode a corresponding UEM field of the UEM user and obtain multiple unequal MCSs on multiple UL resources of the UEM user, e.g., as described below.

[0280] For example, the multiple UL resources of the UE M user may include multiple frequency sub-channels, multiple spatial streams, and / or both frequency sub-channels and spatial streams.

[0281] In some exemplary aspects, configuring a user information list (e.g., user information list 200) to include a UEM field (e.g., all UEM fields) after a user information field (e.g., after all user information fields) can provide a technical solution to support overhead reduction for triggered users (e.g., particularly triggered non-UEM users).

[0282] For example, a triggered non-unequal MCS user may stop its operation, for example, until its user information field is found and / or decoded, and it only has the user information field. For example, when the UEM field is located after all user information fields, for example, Figure 2 As shown, a non-unequal MCS user may (eg, may only need to) decode a limited number of other users' user information fields, eg, until its own user information field is found with less overhead.

[0283] In some exemplary aspects, configuring a user information list (e.g., user information list 200) to include a UEM field (e.g., all UEM fields) after a user information field (e.g., after all user information fields) can provide a technical solution to support overhead reduction for unequal MCS users, for example, if the user information field is configured to provide (e.g., directly provide) the location of its UEM field to the unequal MCS users, for example, as described below.

[0284] In some demonstrative aspects, a user information list, such as user information list 200, may be configured to include a UEM field, such as all UEM fields, after a user information field, such as after all user information fields, e.g., as described above.

[0285] In some exemplary aspects, the user information list may be configured to include UEM fields of the UEM user after the user information field of the user, e.g., immediately after the user information field of the user, e.g., all UEM fields of the UEM user, e.g., as described below.

[0286] refer to Figure 4 , which schematically illustrates a user information list field 400 according to some exemplary aspects.

[0287] For example, device 102 ( Figure 1 ) may be configured to generate and / or send a trigger frame including a user information list field 400, which may be configured to include one or more user information fields of one or more users.

[0288] 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 to receive and / or process a trigger frame including a user information list field 400.

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

[0290] For example, the AP may send the RU / MRU allocation information via a user information field of one or more users.

[0291] In some exemplary aspects, the trigger frame may include RU / MRU allocations for multiple users. For example, the multiple users may include user 402 (triggered user 1), user 404 (triggered user 2), user 406 (triggered user 3), and / or user 408 (triggered user 4).

[0292] In some exemplary aspects, such as Figure 4 As shown, user 404 may include a non-UEM user (equal MCS user), and the entire RU / MRU allocation of the non-UEM user for user 404 may be assigned a single MCS; and / or user 408 may include a non-UEM user, and the entire RU / MRU allocation of the non-UEM user for user 408 may be assigned a single MCS.

[0293] In some exemplary aspects, such as Figure 4 As shown, user 402 may include a UEM user, and multiple UL resources in the RU / MRU allocation of user 402 may be assigned with multiple MCSs; and / or user 406 may include a UEM user, and multiple UL resources in the RU / MRU allocation of user 406 may be assigned with multiple MCSs.

[0294] In some exemplary aspects, such as Figure 4 As shown, the user information list field 400 in the trigger frame may include a user information field 410 for the user 402, which may indicate that the user 402 has a UEM assignment.

[0295] In some exemplary aspects, such as Figure 4 As shown, the user information list field 400 in the trigger frame may include two UEM fields of the user 402, for example, the UEM field 412 and the UEM field 414, which may be configured to include the UEM information of the user 402. For example, the UEM information of the user 402 may indicate the assignment of multiple MCSs to multiple UL resources in the RU allocation of the user 402, respectively.

[0296] In some exemplary aspects, such as Figure 4 As shown, the UEM field of the user 402 may be after the user information field 410 of the user 402 , for example, immediately after the user information field 410 .

[0297] In some exemplary aspects, such as Figure 4 As shown, the user information list field 400 in the trigger frame may include a user information field 416 for the user 404 , for example, after the UEM fields 412 and 414 .

[0298] In some exemplary aspects, such as Figure 4As shown, the user information list field 400 in the trigger frame may include a user information field 420 for the user 406, for example, after the user information field 416. For example, the user information field 420 for the user 406 may indicate that the user 406 has a UEM assignment.

[0299] In some exemplary aspects, such as Figure 4 As shown, the user information list field 400 in the trigger frame may include a UEM field 422 of the user 406, which may be configured to include the UEM information of the user 406. For example, the UEM information of the user 406 may indicate the assignment of multiple MCSs to multiple UL resources in the RU allocation of the user 406, respectively.

[0300] In some exemplary aspects, such as Figure 4 As shown, the user information list field 400 in the trigger frame may include a user information field 424 for the user 408 , for example, after the UEM field 422 .

[0301] In some exemplary aspects, the user information field of the non-UEM user, such as the user information field 416 of the non-UEM user 404 and / or the user information field 424 of the non-UEM user 408, may include RU allocation information of the non-UEM user, which may be configured to define RU allocation for the non-UEM user, and an indication of an MCS (equal MCS) to be applied to the RU allocation for the non-UEM user, for example, according to the IEEE 802.11be specification. For example, the user information field 416 and / or the user information field 424 may be configured according to the EHT variant user information field 300 ( Figure 3 ) to configure, for example, as described above.

[0302] In some exemplary aspects, such as Figure 4 As shown, the UEM field corresponding to the UEM user may be located, for example, immediately after the user information field corresponding to the UEM user.

[0303] For example, Figure 4 As shown, the UEM field 412 and / or the UEM field 414 of the user 402 may be located immediately after the user information field 410 of the user 402 .

[0304] For example, Figure 4 As shown, the UEM field 422 of the user 406 may be located immediately after the user information field 420 of the user 406 .

[0305] In some exemplary aspects, when the UEM field of the UEM user is located immediately after the user information field of the user, for example, Figure 4As shown, the UEM field (eg, each UEM field) may be configured (eg, should be configured) to start with a user identification (AID12) of a UEM user to which the UEM belongs.

[0306] In some exemplary aspects, user 404 and / or user 408, which may include non-unequal MCS users, may operate in accordance with the IEEE 802.11be specification.

[0307] For example, the non-UEM user may, for example, stop parsing the user information list 400 after finding a corresponding user information field with a user ID (e.g., AID12) matching the user ID of the user, and after obtaining the single MCS information of the user from the corresponding user information field. For example, the user 404 may stop parsing the user information list 400 after finding the user information field 416 and obtaining the single MCS of the user 404 from the user information field 416; and / or the user 408 may stop parsing the user information list 400 after finding the user information field 424 and obtaining the single MCS of the user 408 from the user information field 424.

[0308] In some exemplary aspects, a user identified as a UEM user may continue (e.g., may need to continue) parsing the user information list 400, e.g., after finding a corresponding user information field with its AID 12, e.g., until the UEM user is able to collect one or more UEM fields (e.g., all UEM fields) for the UEM user. For example, the UEM user may continue to parse the user information list 400, e.g., until no more UEM fields matching its AID 12 are left.

[0309] For example, user 402 may parse user information list 400 to identify user information field 410 including a user ID (e.g., AID12) of user 402. For example, user 402 may identify that user 410 is a UEM, for example, based on UEM-related information in user field 410, for example, as described below. For example, user 402 may continue to parse user information list 400, for example, until user 402 is able to collect UEM fields 412 and 414 of user 402.

[0310] For example, user 406 may parse user information list 400 to identify user information field 420 including a user ID (e.g., AID12) of user 406. For example, user 406 may identify that user 406 is a UEM, for example, based on UEM-related information in user field 420, e.g., as described below. For example, user 406 may continue to parse user information list 400, for example, until user 406 is able to collect UEM field 422 of user 406.

[0311] In some demonstrative aspects, one or more UEM fields (eg, each UEM field) in user list field 400 may (eg, should) have the same bit length as the bit length of each user information field in user list field 400 .

[0312] In some demonstrative aspects, a UEM field (eg, each UEM field) in user list field 400 may (eg, should) be identified by a user ID (eg, AID12) of the user to which the UEM belongs.

[0313] In some exemplary aspects, when the UEM field of a UEM user is located immediately after the user information field of the user, for example, Figure 4 As shown, it may not be necessary to provide the position information of the UEM field in the user information field, for example, because the UEM field of the user is located immediately after its user information field and between the user information fields of other users.

[0314] In some exemplary aspects, for example, when the UEM field of a UEM user is located immediately after the user information field of the user, for example, as Figure 4 As shown, it may be necessary to identify the UEM with the user ID of the user (e.g., AID12). For example, if the UEM field of the UEM user is located immediately after the user information field of the user, and the UEM field does not start with the AID12 subfield, there may be a possibility that the first 12 bits of the UEM field may be (e.g., accidentally) the same as the AID12 of another user. According to this example, the other user may (e.g., mistakenly) identify the UEM field as its own UEM field.

[0315] In some exemplary aspects, the user information list may be configured to include the UEM fields of the UEM user, e.g., all the UEM fields of the UEM user, after the user information field of the user, e.g., immediately after the user information field of the user, e.g., as described above with reference to Figure 4 Such configuration of the user information list may provide a technical solution for signaling UEM information, which may have some overhead, for example, for non-UEM users. For example, a non-unequal MCS user may have to decode more fields, for example, including user information fields of other users and UEM fields, which may be located before the user information fields of the non-unequal MCS user. According to this example, a non-unequal MCS user may have to decode more fields before decoding its own user information fields.

[0316] In some exemplary aspects, the user information list may be configured to include a UEM field of the UEM user immediately after the user information field of the UEM user, for example, to provide a technical solution for reducing overhead in supporting unequal MCS users.

[0317] For example, the UEM user may ignore the remaining user information fields and / or UEM fields in the user information list, for example, after decoding the user information field of the UEM user and all UEM fields of the UEM user (immediately after the user information field of the user).

[0318] For example, if a user ID (e.g., AID12) is defined to be applicable to both the user information field and the UEM field for user identification, then configuring the user information list to include the UEM field of the UEM user immediately after the user information field of the UEM user can provide a technical solution with reduced overhead, for example, compared to configuring the user information list to include the UEM field after all user information fields. For example, if the user information list is configured to include the UEM field after all user information fields, then the unequal MCS user may need to decode all user information fields and all UEM fields, for example, before the UEM user can find and decode its own UEM field.

[0319] In some exemplary aspects, the user information list may be configured to include the UEM field of the UEM user immediately following the user information field of the UEM user, for example, to provide a technical solution to provide more time for the UEM user to prepare for the upcoming TB PPDU transmission. For example, in the case where the UEM field is located after all user information fields, the UEM user may have only a limited time left to prepare for the upcoming TB PPDU transmission.

[0320] Return to reference Figure 1 In some exemplary aspects, device 102, device 140, and / or device 160 may be configured to implement an unequal MCS signaling mechanism that may utilize a user information field format that may be applied in accordance with the IEEE 802.11be specification, such as directly applied, for example, without even making any additional changes to the trigger frame and / or preliminary conditions, for example, as described below.

[0321] For example, the user information field format may be adapted to include a user information list field 200 ( Figure 2 ) and / or user information list field 400 ( Figure 4 )’s trigger frame.

[0322] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize a user information field format that may be configured as a UEM field that identifies a UEM user, e.g., by a user ID of the user (e.g., AID12), e.g., as described below.

[0323] In some demonstrative aspects, the unequal MCS signaling mechanism may utilize a user information field format that may be configured to inform a user whether the user is an unequal MCS user, e.g., as described below.

[0324] refer to Figure 5 , which schematically illustrates a UEM signaling format 500 according to some demonstrative aspects.

[0325] For example, device 102 ( Figure 1 ) may be configured to generate and / or send a trigger frame, which may include a user information list, which is configured according to the UEM signaling format 500 to include UEM information of the UEM user.

[0326] 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 to receive and / or process a trigger frame including UEM information of a UEM user according to the UEM signaling format 500.

[0327] In some exemplary aspects, such as Figure 5 As shown, the UEM signaling format 500 may include at least one user information field 501 corresponding to a UEM user, for example, as described below.

[0328] For example, the user information field 210 ( Figure 2 ) may include a user information field 501 to provide the UEM user 202 ( Figure 2 ) to inform the UEM of the relevant information; User information field 214 ( Figure 2 ) may include a user information field 501 to provide the UEM user 206 ( Figure 2 ) to inform the UEM of relevant information; User information field 410 ( Figure 4 ) may include a user information field 501 to provide the UEM user 402 ( Figure 4 ) to inform the UEM of relevant information; and / or user information field 420 ( Figure 4 ) may include a user information field 501 to provide the UEM user 406 ( Figure 4 ) Send a letter to inform UEM of the relevant information.

[0329] In some exemplary aspects, such as Figure 5 As shown, the user information field 501 may be configured in accordance with the EHT variant user information field 300 ( Figure 3 ) format, for example, as described below.

[0330] In some exemplary aspects, such as Figure 5 As shown, the user information field 501 may include an AID12 subfield 502 for identifying the user to which the user information field 501 belongs.

[0331] In some exemplary aspects, a user may find and decode its corresponding user information field in a received trigger frame, eg, based on a user ID in the user information field, eg, AID12.

[0332] In some exemplary aspects, such as Figure 5 As shown, the user information field 501 may include a UL EHT-MCS subfield 508, which may be configured to indicate that the user is a UE M user and has a UE M assignment.

[0333] In some exemplary aspects, such as Figure 5 As shown, the UL EHT-MCS subfield 508 may include a predefined MCS index, such as the EHT-MCS14 (1110) index, or any other suitable predefined MCS index, for example, instead of the user's actual MCS information.

[0334] For example, a predefined MCS index (eg, EHT-MCS14 (1110) index) may indicate to a user that the user is a UEM user with a UEM assignment.

[0335] For example, the EHT-MCS14 (1110) index may be used to indicate a UEM user, for example, because the EHT-MCS14 (1110) index is not currently used in the user information field of a non-UEM user for TB PPDU UL transmission.

[0336] In some exemplary aspects, the EHT-MCS14 (1110) index may be utilized, for example, as signaling, for example, particularly for UEM users, rather than an index of an MCS. For example, if a user obtains the EHT-MCS14 (1110) index after decoding the UL EHT-MCS subfield 508 in its user information field 502, the user may be aware of the fact that the user is a UEM user. According to this example, the EHT-MCS14 (1110) index may indicate that the UEM user is to search one or more corresponding UEM fields, for example, to obtain UEM information indicating unequal MCSs of the UEM user.

[0337] In some exemplary aspects, the UL EHT-MCS subfield 508 may be set to any other suitable EHT-MCS index, such as an MCS index in the range between EHT-MCS 0 and EHT-MCS 13 or EHT-MCS 15, which may be used by non-UEM users. For example, the non-UEM user may decode the UL EHT-MCS subfield 508 to provide a single MCS for the non-UEM user.

[0338] In some exemplary aspects, such as Figure 5 As shown, the AID12 subfield 502 may be followed by a RU allocation subfield 504, which may include RU allocation information for the user, such as the RU size and / or any other RU allocation information.

[0339] In some exemplary aspects, as indicated by arrow 511, when the UL EHT-MCS subfield 508 includes a predefined MCS index (eg, EHT-MCS14 (1110) index), the user may be identified as a UE M user.

[0340] In some exemplary aspects, such as Figure 5 As shown, the user information list according to the UEM signaling format 500 may include one or more UEM fields of the UEM user of the user information field 501, for example, the UEM field 503 (UEM field-1) and / or the UEM field 505 (UEM field-2).

[0341] In some exemplary aspects, such as Figure 5 As shown, the UEM field 503 and / or the UEM field 505 may have one or more (e.g., three) types of subfields, including an AID12 subfield, a minimum (min) frequency segment subfield, and / or an MCS subfield, for example, as described below.

[0342] In some demonstrative aspects, UEM field 503 and / or UEM field 505 may be configured to have the same bit length as user information field 501, for example, to support a user in locating the position of each user information field and / or each UEM field.

[0343] In some exemplary aspects, UEM fields, e.g., UEM field 503 and / or UEM field 505, may be configured to have a total length that is the same as or shorter than the length of user information field 501, e.g., to support a user in locating the position of each user information field and / or each UEM field.

[0344] In some exemplary aspects, such as Figure 5As shown, UEM fields, such as UEM field 503 and / or UEM field 505, may be identified by decoding the AID12 subfield, for example, similar to the user information field.

[0345] In some exemplary aspects, such as Figure 5 As shown, the user's UEM field, such as UEM field 503 and / or UEM field 505, may include a user ID field, such as an AID12 field, for example, when the user's UEM field is located immediately after the user information field of the user, for example, as described above with reference to Figure 4 described.

[0346] In some exemplary aspects, such as Figure 5 As shown, the user's UEM fields, such as UEM field 503 and / or UEM field 505, may optionally exclude the user ID field, such as the AID12 field, for example, when the user's UEM fields are located after all user information fields, for example, as described above with reference to Figure 2 described.

[0347] In some demonstrative aspects, a user's UEM field, e.g., UEM field 503 and / or UEM field 505, may be configured to provide information of an MCS assignment for the user, e.g., in the form of minimum frequency segments and / or MCS, e.g., as described below.

[0348] 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 12-bit AID12 subfield, followed by a 3-bit minimum frequency segment subfield, followed by one or more (e.g., N) 4-bit MCS subfields, and padding. Figure 5 As shown, a first-order UEM field, such as UEM field 503, may include an AID12 subfield 520, a minimum frequency fragment subfield 522, followed by N MCS subfields 524, and any padding 526 (if necessary).

[0349] In some exemplary aspects, the non-first-order UEM fields of a UEM user may be configured according to a UEM field format, which may carry (e.g., may only carry) an identifier of the user (e.g., in the form of a 12-bit AID12 subfield) and MCS information, which may include one or more 4-bit MCS subfields, e.g., followed by padding (if necessary). For example, Figure 5As shown, a non-first-order UEM field, such as UEM field 505, may include an AID12 subfield 530 and one or more MCS subfields 532, such as followed by padding (if necessary).

[0350] In some exemplary aspects, the minimum frequency fragment subfield 510 may be configured to specify the partition of the RU for the UEM user, for example, by using 3 bits to inform the UEM user of its minimum frequency fragments with different MCSs. For example, the minimum frequency fragment subfield may be used to indicate the subcarrier numbers assigned with different MCSs in the RU.

[0351] In one example, the size and / or bandwidth of the RU of the user may be provided by the RU allocation subfield of the user information field of the user (e.g., RU allocation subfield 504). For example, the RU of the user may have 996 subcarriers. According to this example, the minimum frequency fragment subfield 522 may be set to indicate that every 242 subcarriers of the 996 subcarriers may be assigned with unequal MCS.

[0352] For example, a user may determine, for example, based on the EU allocation subfield 504 and the minimum frequency fragment subfield 522, that the user should expect four MCSs in each spatial stream of its 996 subcarrier RU. In one example, the user's RU may be equally divided into multiple partitions with 26 subcarriers, 52 subcarriers, 106 subcarriers, 242 subcarriers, 484 subcarriers, 996 subcarriers, 2×996 subcarriers, etc. For example, the minimum frequency fragment subfield 522 may utilize 3 bits to represent all possible partitions with unequal MCSs.

[0353] In some exemplary aspects, the UEM user may use the information in the minimum frequency fragment subfield 522 to determine how many MCSs the UEM user may expect in a subsequent MCS subfield.

[0354] For example, if the RU assigned to a user has M subcarriers and the user's minimum frequency segment is A, then the number of unequal MCSs assigned to the user in each spatial stream can be determined as ceil(N / A), where ceil(·) represents rounding to the nearest integer greater than or equal to (·).

[0355] For example, if the number of spatial streams of a user is S, the user may have a total of S×ceil(N / A) MCSs. For example, the user may obtain the number of spatial streams based on the SS allocation / RA-RU information subfield 510 in the user information field 501 .

[0356] In some exemplary aspects, such as Figure 5As shown, the UEM field 503 may include multiple MCS subfields 524. For example, the MCS subfield 524 may include a 40-bit subfield for carrying a 4-bit binary number representing an MCS index.

[0357] In some exemplary aspects, such as Figure 5 As shown, padding may be applied, for example, to ensure that each UEM field has the same length as the User Information field.

[0358] In some exemplary aspects, one or more non-first-order UEM fields may follow the first-order UEM field, for example, if a single UEM field may not be sufficient to carry all different MCSs. Figure 5 As shown, the non-first-order UEM field 505 may follow the first-order UEM field 503 .

[0359] In some exemplary aspects, such as Figure 5 As shown, a user may have more than one UEM field, for example, when one UEM field may not be able to carry all different MCSs.

[0360] In some exemplary aspects, such as Figure 5 As shown, a non-first-order UEM field (e.g., UEM field 505) may have (e.g., only have) an AID12 subfield 530 to identify the UEM user, followed by one or more MCS subfields 532, which may contain the remaining different MCSs that the first-order UEM field 503 cannot carry, for example, due to insufficient space.

[0361] For example, if the UEM user cannot obtain S×ceil(N / A) MCSs in the first-order UEM field 503, the UEM user may know that it should search other UEM fields, for example, until all S×ceil(N / A) MCSs are obtained.

[0362] In some exemplary aspects, a user (eg, a user of device 140 ( Figure 1 ) implemented by STA) can receive a trigger frame including UEM signaling format 500.

[0363] For example, the user may find and decode its user information field, such as user information field 501 , in the received trigger frame, for example, by searching for the user's user identification (AID12).

[0364] For example, if the user detects that EHT-MCS 14 (1110) is included in the UL EHT-MCS subfield 508, the user can determine that it is an unequal MCS user. For example, based on the determination that the user is a UE MCS user, the user can look for its UE MCS fields, which carry its unequal MCS information. Alternatively, if the user detects any other EHT-MCS (e.g., in the range of 0-13 or 15) in the UL EHT-MCS subfield 508, the user can process its user information field as a non-unequal MCS user, which obtains its single MCS from the UL EHT-MCS subfield 508.

[0365] For example, if the user is a UEM user, the user may find its first UEM field (UEM field-1), for example, using the AID12 subfield.

[0366] For example, a UEM user can calculate the total number of unequal MCSs for a user, for example, based on the RU size provided by the RU allocation subfield 504 of the user information field 501, the size of the minimum frequency fragment with unequal MCS (e.g., provided by the minimum frequency fragment subfield 522 of its first UEM field (UEM field-1)), and the number of spatial streams (e.g., provided by the SS allocation / RA-RU information subfield 510 of the user information field 501).

[0367] For example, the UEM user may determine how many UEM fields the UEM user may have, and may find any other UEM fields thereof, such as UEM field-2, such as by AID 12. For example, the UEM user may decode any UEM fields of the UEM user, such as until all of its unequal MCSs are obtained.

[0368] In some exemplary aspects, the UEM signaling format 500 can provide a technical solution to support the signaling of unequal MCS for TB ULPPDU transmission, for example, by redefining the use of EHT-MCS14 in TB transmission, and introducing a new field format, for example, a UEM field format, for example, with excellent compatibility with the IEEE 802.11be specification. For example, excellent compatibility can be achieved by retaining the format and / or size of the user information field, for example, in accordance with the IEEE 802.11be specification. According to this example, the UEM signaling format 500 can be easily applied in the current Wi-Fi 7 system, for example, according to the IEEE 802.11be specification.

[0369] Return to reference Figure 1In some exemplary 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 the allocation of unequal MCS across multiple frequency subchannels and / or spatial streams, for example, as described below.

[0370] In some demonstrative aspects, the unequal MCS signaling mechanism may provide a technical solution to support signaling of UE M information corresponding to multiple unequal MCSs for multiple users, for example, in a trigger frame, e.g., as described below.

[0371] In some exemplary aspects, the unequal MCS signaling mechanism may provide a technical solution to support resource (bit) conservation and low overhead, e.g., when signaling UE M information corresponding to multiple unequal MCSs, e.g., as described below.

[0372] In some demonstrative aspects, the unequal MCS signaling mechanism may provide a technical solution to support providing (eg, directly providing) location information of a UEM field to one or more unequal MCS users, for example, as described below.

[0373] In some exemplary aspects, providing (e.g., directly providing) location information of the UEM field to one or more unequal MCS users can provide a technical solution for overhead reduction, for example, by excluding the AID12 subfield (each AID12 subfield occupies 12 bits) from the UEM field, for example, as described below.

[0374] In some exemplary aspects, providing (e.g., directly providing) location information of the UEM field to one or more unequal MCS users may provide a technical solution, wherein the unequal MCS user may not need to blindly scan and / or decode all UEM fields to find a UEM field that matches its AID12.

[0375] In some demonstrative aspects, the unequal MCS signaling mechanism may be configured to utilize a user information field of the UEM user to provide location information to the UEM user to indicate the location of the UEM field, e.g., as described below.

[0376] In some exemplary aspects, the unequal MCS signaling mechanism may utilize a trigger frame that may include a field format according to the user information list field format 200 ( Figure 2 ) configured with one or more user information fields, for example, as described below.

[0377] For example, using the user information list field format 200 ( Figure 2 ) can enable the removal of the AID12 subfield from one or more UEM fields of the user information list field.

[0378] For example, according to the user information list field format 400 ( Figure 4 ), the AID12 field may not be removed from the UEM field located between the user information fields. For example, if according to the user information list field format 400 ( Figure 4 ) does not start with AID12, the first 12 bits of the UEM field may be accidentally interpreted by another user and mistakenly identify the UEM field as its own UEM field, for example, as described above.

[0379] In some exemplary aspects, the unequal MCS signaling mechanism may utilize a trigger frame that may be configured to support TB UL PPDU transmissions that are, for example, compliant with next generation Wi-Fi systems, e.g., according to the future 802.11UHR (Wi-Fi 8) specification, e.g., as described below.

[0380] In some demonstrative aspects, the unequal MCS signaling mechanism may implement one or more additional changes to the trigger frame, e.g., to accommodate signaling of UEM information, e.g., as described below.

[0381] For example, a new trigger frame format may be defined that may be incompatible with the IEEE 802.11be specification. According to this example, users communicating according to the IEEE 802.11be specification and / or previous Wi-Fi system versions may be (e.g., should be) blocked from reading and / or decoding trigger frames according to the new trigger frame format.

[0382] In some demonstrative aspects, one or more attributes may be defined, for example, to distinguish trigger frames configured according to different formats, for example, as described below.

[0383] In some exemplary aspects, non-UHR users, such as non-HT users, HT users, Very High Throughput (VHT) users, EHT users, and / or any other type of users, may (e.g., should) be blocked from decoding trigger frames dedicated to UHR users. For example, such distinction between UHR users and non-UHR users may be implemented, for example, by defining signaling in a trigger type subfield of a common information field in a trigger frame, for example, as shown below:

[0384]

[0385]

[0386] Table 1

[0387] For example, as shown in Table 1, in a non-UHR trigger frame, the trigger type subfield may only use trigger type subfield values ​​from 0 to 7 to, for example, represent different trigger frame variants, while values ​​from 8 to 15 are reserved.

[0388] For example, trigger type subfield values ​​8 to 15 may be applied to one or more (eg, all) trigger frame variants dedicated to UHR users, as shown in Table 1, for example.

[0389] For example, when a non-UHR user finds that the value in the trigger type subfield of the trigger frame is in the range between 8 and 15, the non-UHR user may stop decoding the rest of the trigger frame, for example, because the non-UHR user may not be able to recognize the type of the trigger frame.

[0390] For example, when a UHR user reads a value in the range between 0 and 7 in the trigger type subfield of a trigger frame, the UHR user may terminate decoding of the rest of the trigger frame, for example, because the UHR user may know that the trigger frame is sent for a non-UHR user.

[0391] For example, users triggered by a trigger frame may (eg, should) know the total number of triggered users, for example, in order to recognize how many user information fields exist in the trigger frame.

[0392] In some exemplary aspects, the user information list configuration may define that all UEM fields are located after the user information field, and all user information fields are located before the UEM field, for example, as described above with reference to Figure 2 described.

[0393] For example, when the total number of triggered users is U, the user may determine that the first U fields in the user information list are user information fields.

[0394] For example, if the user checks all U user information fields and fails to find the user's AID 12, the user can determine that the user is not triggered in the current trigger frame. According to this example, for example, if the user determines that the user is not triggered in the current trigger frame, the user can stop decoding the rest of the trigger frame.

[0395] According to this example, the UEM field may not be decoded by unintended users, including untriggered users and / or triggered users that do not own the UEM field. For example, only the user who is the owner of the UEM field can decode the UEM field. For example, the location of the UEM field may be provided by a user information field of the user, for example, as described below.

[0396] Therefore, it may not be required to include the AID12 subfield in the UEM field.The ability to exclude the AID subfield from the UEM field may provide a technical solution to save bits and reduce overhead.

[0397] In some demonstrative aspects, the number of triggered users of a trigger frame may be provided, for example, by a 7-bit EHT reserved subfield (eg, bits B56 to B62) of a common information field of the trigger frame.

[0398] In some exemplary aspects, the number of triggered users of a trigger frame may be provided, for example, by three reserved bits (e.g., bits B37 to B39) of the special user information field of the trigger frame, for example, if the number of triggered users is generally less than or equal to eight.

[0399] In other aspects, the number of triggered users may be provided in any other field or subfield of the trigger frame.

[0400] refer to Figure 6 , which schematically illustrates a UEM signaling format 600 according to some demonstrative aspects.

[0401] For example, device 102 ( Figure 1 ) can be configured to generate and / or send a trigger frame, which can be configured according to the UEM signaling format 600.

[0402] 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 to receive and / or process a trigger frame configured according to the UEM signaling format 600.

[0403] In some exemplary aspects, an AP (eg, provided by device 102 ( Figure 1 ) implemented AP) can determine RU / MRU assignments, including RU / MRU allocations for one or more users.

[0404] For example, the user may process a user information field of the user in a trigger frame received from the AP.

[0405] In some exemplary aspects, such as Figure 6 As shown, the trigger frame configured according to the UEM signaling format 600 may include a user information field 601 for a non-UEM user, a user information field 603 for a UEM user, and one or more UEM fields for the UEM user, for example, a UEM field 605 (UEM field-1) and / or a UEM field 607 (UEM field-2).

[0406] In some exemplary aspects, a user may find and decode its user information field in a received trigger frame, for example, by user identification (AID12).

[0407] In some exemplary aspects, such as Figure 6 As shown, the user information field 601 and / or the user information field 603 may be configured to include a new subfield, for example, the MCS type subfield 602 and / or the MCS type subfield 604. For example, it may be defined that the MCS type subfield may exist in the user information fields of both unequal MCS users and non-unequal MCS users.

[0408] For example, the MCS type subfield 602 in the user information field 601 may be configured to inform the user that it is a non-UEM user. For example, the MCS type subfield 602 may include a 1-bit MCS type subfield, which may be set to a first predefined value, such as 0, to indicate, for example, that the user of the user information field 601 is a non-UEM user.

[0409] For example, the MCS type subfield 604 in the user information field 603 may be configured to inform the user that it is a UEM user. For example, the MCS type subfield 604 may include a 1-bit MCS type subfield, which may be set to a second predefined value, such as 1, to indicate, for example, that the user of the user information field 603 is a UEM user.

[0410] In some exemplary aspects, the MCS type subfield, e.g., MCS type subfield 602 and / or MCS type subfield 604, may be located at bit 26 in the user information field. For example, this bit 26 may be reserved, e.g., according to the EHT variant user information field 300 format ( Figure 3 ).

[0411] In some demonstrative aspects, the definition of the 4-bit subfield preceding the MCS type subfield may be defined, for example, according to the value of the MCS type subfield.

[0412] For example, if the value of the MCS type subfield is 0 (non-unequal MCS user), the 4-bit subfield preceding the MCS type subfield may be used as a UL EHT-MCS subfield, eg, to provide an index of a single MCS for non-UEM users.

[0413] For example, Figure 6 As shown, the 4-bit subfield 611 before the MCS type subfield 602 may be set to the UL EHT-MCS subfield 611 to indicate a single MCS index for non-UEM users.

[0414] For example, if the value of the MCS type subfield is 1 (unequal MCS user), the 4-bit subfield preceding the MCS type subfield may be used as a UEM field indicator subfield to indicate the location of the UEM field for the UEM user, for example, as described below.

[0415] For example, Figure 6 As shown, the 4-bit subfield 606 before the MCS type subfield 604 may be set as a UEM field indicator subfield 606 to indicate the location of the UEM fields 605 and / or 607 of the UEM user, for example, as described below.

[0416] In some demonstrative aspects, the UEM field indicator subfield 606 may be configured to inform the UEM user of the location of a first UEM field (UEM field-1) (eg, UEM field 605) corresponding to the UEM user, e.g., as described below.

[0417] In some demonstrative aspects, the UEM field indicator subfield 606 of the user information field 603 may utilize 4 bits to provide a distance from a current user information field (eg, user information field 603) to an indicated UEM field-1 (eg, UEM field 605).

[0418] refer to Figure 7 , which schematically illustrates a signaling scheme 700 for signaling a UEM field location according to some demonstrative aspects.

[0419] In some exemplary aspects, the UEM field indicator subfield 606 ( Figure 6 ) may be configured to include a value d, which may be configured to indicate a distance 702 between a user information field 703 and a UEM field 705 of a UEM user, for example, as described below.

[0420] In some exemplary aspects, such as Figure 7 As shown, the user information field 703 may be the i-th field in the trigger frame, for example, a field representing a user information field or a UEM field.

[0421] In some exemplary aspects, such as Figure 7 As shown, the value of the 4-bit UEM field indicator subfield, for example, the value of the UEM field indicator subfield 606 ( Figure 6 ), may be set to d, for example, to indicate that the first UEM field of a UEM user, for example, UEM field 705, is d fields (user information field / UEM field) away from the user information field 703. For example, the UEM field indicator subfield 606 ( Figure 6) can be configured to indicate that the UEM field 705 is in the (i+d)th field.

[0422] For example, it should be noted that Figure 7 The scheme of indicating the position of the UEM field shown in may depend on the condition that the user information field and the UEM field have the same bit length.

[0423] Return to reference Figure 6 In some exemplary aspects, one or more UEM fields (e.g., UEM field 605 and / or UEM field 607) may not require AID12 for user identification, for example, because the position of the first-order UEM field (UEM field-1) can be directly provided by the UEM field indicator subfield 606 in the user information field 603.

[0424] In some exemplary aspects, such as Figure 6 As shown, the format of the UEM field 605 can be simplified.

[0425] For example, Figure 6 As shown, the first-order UEM field (eg, UEM field 605 ) may include (eg, may only include) a minimum frequency segment subfield 610 , followed by a plurality of MCS subfields 612 , and padding bits 614 (if necessary).

[0426] For example, Figure 6 As shown, a non-first-order UEM field (eg, UEM field 607 ) may include (eg, may only include) a plurality of MCS subfields 620 , and padding bits 622 (if necessary).

[0427] For example, one or more non-first-order UEM fields (e.g., UEM field-2) may (e.g., may always) be located next to its UEM field- 1. Therefore, it may be sufficient to precisely locate the position of the first-order UEM field (e.g., UEM field-1) of a user through the user information field of the user.

[0428] For example, after locating the user's UEM field-1, the user can automatically identify the locations of the user's other UEM fields.

[0429] For example, a user may calculate the total number of unequal MCSs assigned to a user, for example, after decoding the minimum frequency segment subfield of UEM field-1, such as minimum frequency segment subfield 610. According to this example, a user may determine how many additional UEM fields immediately following UEM field-1 are used to carry all unequal MCSs assigned to a user.

[0430] In some exemplary aspects, the user can find and decode its user information field in the trigger frame received from the AP. For example, the user can find its user information field based on the user identification (AID12) in the AID12 subfield (e.g., AID12 subfield 608 and / or AID12 subfield 609).

[0431] In some demonstrative aspects, a user may determine whether the user is a non-UEM user or a UEM user, for example, through an MCS type subfield of a corresponding user information field, such as MCS type subfield 602 and / or MCS type subfield 604.

[0432] For example, in the case where the user is a non-UEM user, the user may obtain its single MCS in the ULEHT-MCS subfield 611 located before the MCS type subfield 602 .

[0433] For example, in the case where the user is a UEM user, the user may read the location information of its first-order UEM field (UEM field-1) through the UEM field indicator subfield 606 located before the MCS type subfield 604, for example.

[0434] In some exemplary aspects, a user may, for example, directly locate and / or decode a corresponding first-order UEM field (UEM field-1).

[0435] For example, a user can calculate the total number of unequal MCSs assigned to a user based on, for example, the user's RU size provided by the RU allocation subfield 613 of the user information field 603, the size of the user's minimum frequency fragment with unequal MCS provided by the minimum frequency fragment subfield 609 of the UEM field-1, and / or the number of spatial streams provided by the SS allocation / RA-RU information subfield 615 of the user information field 603.

[0436] For example, a user may determine how many UEM fields to obtain and how many UEM fields the user has.

[0437] For example, a user may decode all of its other UEM fields, which may be located next to the user's UEM field-1, for example, in order to obtain all of the unequal MCSs assigned to the user.

[0438] In some demonstrative aspects, the UEM signaling format 600 may be configured to provide a technical solution to enable the user information field of the trigger frame to provide (eg, directly provide) location information of the UEM field to unequal MCS users, for example, as described above.

[0439] In some exemplary aspects, new subfields in the user information field may be defined, such as an MCS type subfield and a UEM field indicator subfield, such as MCS type subfield 602, MCS type subfield 604, and / or UEM field indicator subfield 606, to indicate the MCS type of the user and the location of the UEM field-1 carrying unequal MCS information, for example, as described above.

[0440] In some exemplary aspects, the UEM signaling format 600 may be configured to provide a technical solution to support the format of the UEM field to be simplified, for example, while supporting the exclusion of the AID12 subfield from the UEM field. Therefore, the MCS signaling format 600 may be configured to provide a technical solution to save a relatively large amount of bits, thereby reducing overhead.

[0441] In some demonstrative aspects, UEM signaling format 600 may be configured to provide a technical solution for implementation by future and / or new protocols and / or specifications (e.g., Wi-Fi 8 (UHR)).

[0442] 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 ).

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

[0444] As shown at block 804, the method may include determining UEM information of the user STA. For example, the UEM information of the user STA may be configured to indicate the assignment of multiple UL resources in the RU allocation of the user STA to assign multiple MCSs respectively. For example, the multiple UL resources may include at least one of multiple frequency subchannels and / or multiple spatial streams. For example, the controller 124 ( Figure 1 ) may be configured to cause, trigger, and / or control device 102 ( Figure 1 ) determines the UEM information of the user STA, for example, to indicate the assignment of multiple UL resources in the RU allocation of multiple MCSs to the user STA, for example, as described above.

[0445] As shown at block 806, the method may include sending a trigger frame including a user information field of the user STA and UEM information of the user STA. For example, the controller 124 ( Figure 1 ) may be configured to cause, trigger, and / or control device 102 ( Figure 1 ) sends a trigger frame including a user information field of the user STA and the UEM information of the user STA, for example, as described above.

[0446] 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 ).

[0447] As shown at block 902, the method may include processing, at the user STA, a user information field of the user STA in a trigger frame from the AP to identify, for example, an RU allocation of the user STA based on RU allocation information in the user information field of the user STA. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger, and / or control device 140 ( Figure 1 ) device 140 ( Figure 1 ) to, for example, based on the user information field of device 140 ( Figure 1 ) to identify the device 140 ( Figure 1 )'s RU allocation, for example, as described above.

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

[0449] As shown at block 906, the method may include sending a TB UL transmission from the user STA based on assigning multiple MCSs to multiple UL resources in the 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 ) of the RU allocation, from device 140 ( Figure 1 ) sends a TB UL transmission, for example, as described above.

[0450] 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.

[0451] 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).

[0452] In some exemplary aspects, logic 1004 may include instructions, data, and / or code that, if 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.

[0453] 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.

[0454] Example

[0455] The following examples relate to further aspects.

[0456] Example 1 includes a device comprising logic and circuits configured to enable an access point (AP) to set resource unit (RU) allocation information of a user station (STA) in a user information (info) field of the user STA, wherein the RU allocation information of the user STA is configured to indicate an RU allocation for a triggered (TB) uplink (UL) transmission from the user STA; determine unequal modulation and coding scheme (MCS) (UEM) information of the user STA, wherein the UEM information of the user STA is configured to indicate an assignment of multiple MCSs to multiple UL resources in the RU allocation of the user STA, respectively, wherein the multiple UL resources include at least one of multiple frequency subchannels or multiple spatial streams; and send a trigger frame comprising a user information field of the user STA and the UEM information of the user STA.

[0457] Example 2 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 STA in at least one UEM field of the user STA, wherein the at least one UEM field of the user STA is after the user information field of the user STA.

[0458] Example 3 includes the subject matter of Example 2, and optionally, wherein the apparatus is configured to cause the AP to set a subfield in a user information field of the user STA to indicate that the user STA has a UEM designation.

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

[0460] Example 5 includes the subject matter of Example 4, and optionally, wherein the predefined MCS index is 14.

[0461] Example 6 includes the subject matter of Example 4 or 5, 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.

[0462] Example 7 includes the subject matter as described in Example 6, and optionally, wherein a first-order UEM field in at least one UEM field of the user STA includes a frequency fragment subfield, which is configured to indicate the division of the RU allocation of the user STA into the multiple frequency subchannels.

[0463] Example 8 includes the subject matter of any one of Examples 4-7, and optionally, wherein a bit length of each UE M field of the user STA is equal to a bit length of a user information field of the user STA.

[0464] Example 9 includes the subject matter of any one of Examples 4-8, and optionally, wherein at least one UEM field of the user STA is subsequent to all user information fields in the trigger frame.

[0465] Example 10 includes the subject matter of any of Examples 4-8, and optionally, wherein the at least one UE M field of the user STA immediately follows a user information field of the user STA.

[0466] Example 11 includes the subject matter of Example 10, and optionally, wherein the trigger frame includes one or more other user information fields after at least one UEM field of the user STA.

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

[0468] Example 13 includes the subject matter of Example 12, and optionally, wherein the MCS type subfield comprises a single-bit subfield, wherein the predefined MCS type value comprises a value of one.

[0469] Example 14 includes the subject matter of Example 12 or 13, and optionally, wherein the apparatus is configured to cause the AP to set a UEM field indicator subfield in a user information field of the user STA, 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 STA in the trigger frame.

[0470] Example 15 includes the subject matter of Example 14, and optionally, wherein the UEM field indicator subfield is configured to indicate a distance between a user information field of the user STA and a first UEM field of the at least one UEM field of the user STA.

[0471] Example 16 includes the subject matter of any of Examples 12-15, 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.

[0472] Example 17 includes the subject matter of Example 16, 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.

[0473] Example 18 includes the subject matter of any of Examples 12-17, and optionally, wherein at least one UE M field of the user STA is subsequent to all user information fields in the trigger frame.

[0474] Example 19 includes the subject matter of Example 1, and optionally, wherein the apparatus is configured to cause the AP to set the UEM information of the user STA in a plurality of MCS subfields in a user information field of the user STA.

[0475] Example 20 includes the subject matter of any one of Examples 1-19, and optionally, wherein the apparatus is configured to cause the AP to set the spatial configuration subfield in the user information field of the user STA to indicate the assignment of the multiple spatial streams to the user STA, wherein the UEM information of the user STA is configured to indicate the assignment of the multiple MCSs to the multiple spatial streams.

[0476] Example 21 includes the subject matter of any of Examples 1-20, and optionally, wherein the apparatus is configured to cause the AP to process a UL physical layer (PHY) protocol data unit (PPDU) from the user STA based on an assignment of the multiple MCSs to the multiple UL resources.

[0477] Example 22 includes the subject matter of any one of Examples 1-21, and optionally, wherein the apparatus is configured to cause the AP to determine an assignment of the multiple MCSs to the multiple UL resources based on wireless communication conditions on the multiple UL resources.

[0478] Example 23 includes the subject matter of any one of Examples 1-22, and optionally, wherein the apparatus is configured to cause the AP to set other user information fields in the trigger frame, the other user information fields including other RU allocation information to indicate other RU allocations of other user STAs, wherein the MCS subfield in the other user information field includes an MCS index to indicate the MCS to be applied to the entire RU allocation of the other user STAs.

[0479] Example 24 includes the subject matter of any of Examples 1-23, and optionally, wherein the plurality of UL resources comprises a plurality of frequency subchannels in an RU allocation for the user STA.

[0480] Example 25 includes the subject matter of any of Examples 1-24, and optionally, wherein the plurality of UL resources comprises a plurality of spatial streams in an RU allocation for the user STA.

[0481] Example 26 includes the subject matter of any of Examples 1-25, and optionally, wherein the trigger frame comprises an Extreme High Throughput (EHT) trigger frame.

[0482] Example 27 includes the subject matter of any of Examples 1-25, and optionally, wherein the trigger frame comprises an ultra high reliability (UHR) trigger frame.

[0483] Example 28 includes the subject matter of any of Examples 1-27, and optionally, includes at least one radio station to send the trigger frame.

[0484] Example 29 includes the subject matter of Example 28 and optionally, comprising one or more antennas coupled to the radio station and a processor to execute instructions of an operating system.

[0485] Example 30 includes a device comprising logic and circuits configured to enable a user station (STA) to process a user information (info) field of the user STA in a trigger frame from an access point (AP) to identify a resource unit (RU) allocation of the user STA based on resource unit (RU) allocation information in the user information field of the user STA; process unequal modulation and coding scheme (MCS) (UEM) information of the user STA in the trigger frame to identify an assignment of multiple MCSs to multiple UL resources in the RU allocation of the user STA, respectively, wherein the multiple UL resources include at least one of multiple frequency subchannels or multiple spatial streams; and send a triggered (TB) uplink (UL) transmission from the user STA based on the assignment of the multiple MCSs to the multiple UL resources in the RU allocation of the user STA.

[0486] Example 31 includes the subject matter of Example 30, and optionally, wherein the apparatus is configured to enable the user STA to identify UEM information of the user STA in at least one UEM field of the user STA, wherein the at least one UEM field of the user STA is after a user information field of the user STA.

[0487] Example 32 includes the subject matter of Example 31, and optionally, wherein the apparatus is configured to cause the user STA to process a subfield in a user information field of the user STA to identify that the user STA has a UEM designation.

[0488] Example 33 includes the subject matter of Example 31 or 32, and optionally, wherein the apparatus is configured to cause the user STA to identify that the user STA has a UEM assignment based on a predefined MCS index in an MCS subfield in a user information field of the user STA.

[0489] Example 34 includes the subject matter of Example 33, and optionally, wherein the predefined MCS index is 14.

[0490] Example 35 includes the subject matter of Example 33 or 34, 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.

[0491] Example 36 includes the subject matter of Example 35, 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.

[0492] Example 37 includes the subject matter of any of Examples 33-36, and optionally, wherein a bit length of each UEM field of the user STA is equal to a bit length of a user information field of the user STA.

[0493] Example 38 includes the subject matter of any of Examples 33-37, and optionally, wherein at least one UEM field of the user STA is subsequent to all user information fields in the trigger frame.

[0494] Example 39 includes the subject matter of any of Examples 33-37, and optionally, wherein the at least one UEM field of the user STA immediately follows a user information field of the user STA.

[0495] Example 40 includes the subject matter of Example 39, and optionally, wherein the trigger frame includes one or more other user information fields after at least one UEM field of the user STA.

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

[0497] Example 42 includes the subject matter of Example 41, and optionally, wherein the MCS type subfield comprises a single-bit subfield, wherein the predefined MCS type value comprises a value of one.

[0498] Example 43 includes the subject matter of Example 41 or 42, and optionally, wherein the apparatus is configured to cause the user STA to process a UEM field indicator subfield in a user information field of the user STA to identify a position of a first UEM field of at least one UEM field of the user STA in the trigger frame.

[0499] Example 44 includes the subject matter of Example 43, and optionally, wherein the apparatus is configured to cause the user STA to process the UEM field indicator subfield to identify a distance between a user information field of the user STA and a first UEM field of at least one UEM field of the user STA.

[0500] Example 45 includes the subject matter of any of Examples 41-44, 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.

[0501] Example 46 includes the subject matter of Example 45, 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.

[0502] Example 47 includes the subject matter of any of Examples 41-46, and optionally, wherein at least one UEM field of the user STA is subsequent to all user information fields in the trigger frame.

[0503] Example 48 includes the subject matter of Example 30, and optionally, wherein the apparatus is configured to cause the user STA to identify the UE M information of the user STA in a plurality of MCS subfields in a user information field of the user STA.

[0504] Example 49 includes the subject matter of any one of Examples 30-48, and optionally, wherein the apparatus is configured to cause the user STA to process the spatial configuration subfield in the user information field of the user STA to identify the assignment of the multiple spatial streams to the user STA, and to process the UEM information of the user STA to identify the assignment of the multiple MCSs to the multiple spatial streams.

[0505] Example 50 includes the subject matter of any of Examples 30-49, and optionally, wherein the plurality of UL resources comprises a plurality of frequency subchannels in an RU allocation for the user STA.

[0506] Example 51 includes the subject matter of any of Examples 30-50, and optionally, wherein the plurality of UL resources comprises a plurality of spatial streams in an RU allocation for the user STA.

[0507] Example 52 includes the subject matter of any of Examples 30-51, and optionally, wherein the TB UL transmission comprises an extremely high throughput (EHT) transmission.

[0508] Example 53 includes the subject matter of any of Examples 30-51, and optionally, wherein the TB UL transmission comprises an ultra-high reliability (UHR) transmission.

[0509] Example 54 includes the subject matter of any of Examples 30-53, and optionally, comprising at least one radio station to transmit the TB UL transmission.

[0510] Example 55 includes the subject matter of Example 54 and optionally, comprising one or more antennas coupled to the radio station and a processor executing instructions of an operating system.

[0511] Example 56 includes a wireless communication device comprising an apparatus as described in any of Examples 1-55.

[0512] Example 57 includes a mobile device comprising an apparatus as described in any of Examples 1-55.

[0513] Example 58 includes an apparatus comprising means for performing any of the described operations of any of Examples 1-55.

[0514] Example 59 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 of the operations described in any of Examples 1-55.

[0515] Example 60 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any described operations of any of Examples 1-55.

[0516] Example 61 includes a method comprising any of the described operations of any of Examples 1-55.

[0517] 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.

[0518] 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 of a user station (STA) in a user information (info) field of the user STA, the RU allocation information of the user STA being configured to indicate RU allocation for a triggered (TB) uplink (UL) transmission from the user STA; Determine unequal modulation and coding scheme (MCS) (UEM) information of the user STA, wherein the UEM information of the user STA is configured to indicate that multiple MCSs are respectively assigned to multiple UL resources in the RU allocation of the user STA, wherein The plurality of UL resources include at least one of a plurality of frequency subchannels or a plurality of spatial streams; and A trigger frame is sent, where the trigger frame includes a user information field of the user STA and UEM information of the user STA.

2. The apparatus according to claim 1, configured to enable the AP to set the UEM information of the user STA in at least one UEM field of the user STA, wherein: At least one UEM field of the user STA is subsequent to the user information field of the user STA.

3. The apparatus of claim 2, configured to cause the AP to set a subfield in a user information field of the user STA to indicate that the user STA has a UEM designation.

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

5. The device according to claim 4, wherein: The predefined MCS index is 14.

6. The device according to claim 2, wherein: At least one UEM field of the user STA is configured according to a UEM field format, which includes a station (STA) identifier (ID) (STA-ID) field used to identify the user STA and a plurality of MCS subfields after the STA-ID field.

7. The device according to claim 6, wherein: A first-order UEM field among the at least one UEM field of the user STA includes a frequency segment subfield, and the frequency segment subfield is configured to indicate a division of RU allocation of the user STA into the plurality of frequency subchannels.

8. The device of claim 2, wherein: The bit length of each UE M field of the user STA is equal to the bit length of the user information field of the user STA.

9. The device of claim 2, wherein: At least one UEM field of the user STA is after all user information fields in the trigger frame.

10. The device of claim 2, wherein: The at least one UEM field of the user STA is immediately followed by the user information field of the user STA.

11. The device of claim 10, wherein: The trigger frame includes one or more other user information fields after the at least one UE M field of the user STA.

12. 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 information field of the user STA, the predefined MCS type value indicating that the user STA has a UEM assignment.

13. The apparatus according to claim 12, configured to enable the AP to set a UEM field indicator subfield in a user information field of the user STA, wherein: The UEM field indicator subfield is configured to indicate a position of a first UEM field among the at least one UEM field of the user STA in the trigger frame.

14. The device of claim 12, wherein: At least one UEM field of the user STA is after all user information fields in the trigger frame.

15. The apparatus according to any one of claims 1 to 14, configured to enable the AP to set the spatial configuration subfield in the user information field of the user STA to indicate the assignment of the multiple spatial streams to the user STA, wherein: The UE M information of the user STA is configured to indicate assignment of the multiple MCSs to the multiple spatial streams.

16. The apparatus of any one of claims 1 to 14, configured to cause the AP to process a UL physical layer (PHY) protocol data unit (PPDU) from the user STA according to an assignment of the multiple MCSs to the multiple UL resources.

17. The apparatus of any one of claims 1 to 14, comprising at least one radio station to transmit the trigger frame.

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 of a user station (STA) in a user information (info) field of the user STA, the RU allocation information of the user STA being configured to indicate RU allocation for a triggered (TB) uplink (UL) transmission from the user STA; Determine unequal modulation and coding scheme (MCS) (UEM) information of the user STA, wherein the UEM information of the user STA is configured to indicate assignment of multiple MCSs to multiple UL resources in an RU allocation of the user STA, respectively, wherein the multiple UL resources include at least one of multiple frequency subchannels or multiple spatial streams; and A trigger frame is sent, where the trigger frame includes a user information field of the user STA and UEM information of the user STA.

20. The method of claim 19, comprising: The UEM information of the user STA is set in at least one UEM field of the user STA, wherein the at least one UEM field of the user STA is after the user information field of the user STA.

21. The method of claim 20, comprising: A subfield in the user information field of the user STA is set to indicate that the user STA has a UEM assignment.

22. The method of claim 20, wherein: The bit length of each UE M field of the user STA is equal to the bit length of the user information field of the user STA.

23. The method of claim 19, comprising: The spatial configuration subfield in the user information field of the user STA is set to indicate the assignment of the multiple spatial streams to the user STA, wherein the UEM information of the user STA is configured to indicate the assignment of the multiple MCSs to the multiple spatial streams.

24. A product comprising one or more tangible computer-readable non-transitory storage media, the media comprising instructions operable, when executed by at least one processor, 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