WO2016178534A1

WO2016178534A1 - Device and method for signaling information in wireless local area network system

Info

Publication number: WO2016178534A1
Application number: PCT/KR2016/004755
Authority: WO
Inventors: 엠. 조시암카우식; 타오리라케쉬
Original assignee: 삼성전자주식회사
Priority date: 2015-05-05
Filing date: 2016-05-04
Publication date: 2016-11-10

Abstract

The present disclosure relates to a 5G (5th generation) or a pre-5G communication system for supporting a higher data transmission rate following 4G (4th generation) communication systems such as LTE (long term evolution). A method of an STA (station) in a WLAN (wireless local area network) may include a process of receiving an HE PPDU (high efficiency physical layer convergence protocol (PLCP) protocol data unit) including an HE-SIG-A (high efficiency signal A) field from an AP (access point), and the received HE PPDU may further include an HE-SIG-B (high efficiency signal B) field when the format of the received HE PPDU is an HE MU PPDU used for the transmission of an MU (multiple user) that does not respond to a trigger frame.

Description

Apparatus and method for signaling information in a wireless local area network system

The descriptions below generally relate to wireless local area networks (WLANs), and more particularly, to apparatus and methods for signaling information in WLAN systems.

4G (4 ^th generation) to meet the traffic demand in the radio data communication system increases since the commercialization trend, efforts to develop improved 5G (5 ^th generation) communication system, or pre-5G communication system have been made. For this reason, a 5G communication system or a pre-5G communication system is called a Beyond 4G Network communication system or a Long Term Evolution (LTE) system (Post LTE) system.

In order to achieve high data rates, 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive array multiple input / output (Full-Dimensional MIMO, FD-MIMO) in 5G communication systems Array antenna, analog beam-forming, and large scale antenna techniques are discussed.

In addition, in order to improve the network of the system, 5G communication system has evolved small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to device communication (D2D), wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), and interference cancellation The development of such technology is being done.

In addition, in 5G systems, Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and sliding window superposition coding (SWSC), Advanced Coding Modulation (ACM), and Filter Bank Multi Carrier (FBMC), an advanced access technology ), Non Orthogonal Multiple Access (NOMA), Spar Code Multiple Access (SCMA), and the like are being developed.

Institute of electrical and electronics engineers (IEEE) 802.11 ax standards use single-user multiple-input multiple-output (SU-MIMO) to provide high performance (HE) from an access point (AP) to a single station (STA). define transmissions (HE) and define HE transmissions from an AP to multiple STAs using multi-user multiple-input multiple-output (MU-MIMO) and orthogonal frequency division multiple access (OFDMA). The transmitted data packet is referred to as a HE physical layer convergence procedure (PLCP) protocol data unit (PPDU). A particular PPDU, referred to as an MU PPDU, includes data streams meant for multiple STAs transmitted using MU-MIMO and / or OFDMA. If SU-MIMO is used, the packet is referred to as SUPPDU. The headers in the SU and MU PPDU contain the necessary information for decoding the PPDU. Since the same header must indicate different types of payload in the receiver's physical layer, the HE-SIG-A (HE-SIG-A) field in the header is transmitted along with the signaling fields. It has multiple interpretations according to certain flags. The MU PPDU has an additional HE-SIG-B field that communicates decoding information for data addressed to the STAs.

The following descriptions can provide an apparatus and method for efficient signaling and addressing in wireless local area networks (WLANs).

Apparatus of an access point (AP) in a wireless local area network (WLAN) includes a high efficiency physical layer convergence protocol (PLCP) protocol data unit including a high efficiency signal A (HE-SIG-A) field And a control unit configured to generate a) and at least one transceiver configured to transmit the generated HE PPDU to a station (STA), wherein the HE PPDU includes a trigger frame in which the format of the HE PPDU is triggered. In the case of a HE MU PPDU used for multiple user (MU) transmission that does not respond to a (trigger frame), it may further include a high efficiency signal B (HE-SIG-B) field.

An apparatus of an STA in a WLAN may include at least one transceiver configured to receive a HE PPDU including an HE-SIG-A field from an AP, wherein the received HE PPDU has a format of the received HE PPDU. In the case of the HE MU PPDU used for the MU transmission not responding to the trigger frame, the HE-SIG-B field may be further included.

The method of an AP in a WLAN may include generating a HE PPDU including a HE-SIG-A field, and transmitting the generated HE PPDU to an STA, wherein the HE PPDU is an example of the HE PPDU. If the format is a HE MU PPDU used for MU transmission that does not respond to a trigger frame, the HE-SIG-B field may be further included.

The method of an STA in a WLAN may include receiving a HE PPDU including an HE-SIG-A field from an AP, wherein the received HE PPDU does not respond to a trigger frame in a format of the received HE PPDU. In the case of the HE MU PPDU used for the MU transmission that does not, the HE-SIG-B field may be further included.

Other technical features will become apparent to those skilled in the art from the following figures, detailed description, and claims.

Before carrying out the following detailed description, it is desirable to describe the definitions of certain words and phrases used throughout this patent document. The word "connect" and its derivatives refer to any direct or indirect communication between two or more components, whether or not they are in physical contact with each other. The terms "transmit", "receive", and "communicate" as well as their derivatives encompass both direct and indirect communication. The terms "comprise" and "comprise" and their derivatives mean unlimited inclusion. The word "or" is a generic term meaning "and / or". "Associated with" and derivatives thereof, included in, interconnected with, nested, nested in, connected to, combined with, combined with, and communicating with It can mean, cooperate with, intervene, put side by side, approximate to, bondage to, have, have characteristics of, have a relationship with, and so on. The term "controller" means any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed locally or remotely. When used with a list of items, the term "at least one" means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of A, B, and C" includes any of A, B, C, A and B, A and C, B and C, and combinations of A and B and C.

In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which consists of computer readable program code and is embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof suitable for the implementation of suitable computer readable program code. The term "computer readable program code" includes all types of computer code including source code, object code, and executable code. The term "computer readable media" means a computer, such as read only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. It includes all types of media that can be accessed by. "Non-transitory" computer readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer readable media includes media on which data may be permanently stored, and media on which data may be stored and later overwritten, such as a rewritable optical disc or a removable memory device.

Definitions for other specific words and phrases are provided throughout this specification. Those skilled in the art will appreciate that in most cases, if not most, such definitions apply not only to the words and phrases so defined, but also to their subsequent use.

Various embodiments of the present disclosure may provide an apparatus and a method for efficiently generating a high efficiency PLCP protocol data unit (HE PPDU).

For a more complete understanding, the following description is made with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

1 illustrates an example of a wireless network.

2A shows an example of an access point (AP).

2B shows an example of a single station (STA).

3 shows an example of a header structure for VHT PPDU transmission.

4A shows an example of a membership status array field.

4B shows an example of a user position array field.

5 shows an example of the structure of a HE PPDU.

6 shows an example of possible resource unit (RU) sizes and positions in a 20 MHz OFDMA PPDU.

7 shows an example of possible RU sizes and locations in a 40 MHz OFDMA PPDU.

8 shows an example of possible RU sizes and locations in an 80 MHz OFDMA PPDU.

9 shows an example of RU batch indexing in the 20 MHz bandwidth.

10 illustrates an example of signaling in high efficiency signaling B (HE-SIG-B) that includes a common signaling portion.

11 shows an example of HE-SIG-B signaling.

12 illustrates an example of a concatenated or extended group ID generated by concatenating two group IDs.

13 shows an example of a user location updated based on a group ID connection.

14 shows an example of RU location indexing at 20 MHz.

15 shows an example of RU location indexing at 40 MHz.

16 shows an example of RU location indexing at 80 MHz.

17 shows an example of RU batch indexing up to 242 tone RUs.

18 shows an example of extended RU placement indexing to indicate large RU sizes.

19 shows an example of a signaling message that includes a common information portion carrying number of users per MU assignment and RU information.

20 shows an example of a signaling message that includes a common information portion carrying an MU flag and an RU placement.

21 shows an example of RU placement indexing that includes additional indices for RU placements when signaling MU-MIMO resources.

FIG. 22 shows an example of a signaling message that includes a common information portion including a resource allocation field including an MU-MIMO flag and integrated RU deployments.

23 shows an example of indexing including the number of users and RU placement for MU-MIMO resources.

FIG. 24 shows an example of a signaling message including a common information portion including the number of users and RU placement for MU-MIMO RUs in the HE-SIG-B channel.

25 shows an example of different common information types for a signaling message.

FIG. 26 shows an example of a HE-SIG-B channel transmission at 20 MHz that includes a per-user allocation information portion followed by a common information portion.

27 shows an example of a HE-SIG-B transmission in a format 40 MHz bandwidth that includes two HE-SIG-B channels.

28 shows an example of a HE-SIG-B transmission format indicating transmission over the full 40 MHz bandwidth when signaled by a 484 tone RU.

FIG. 29 shows an example of HE-SIG-B multiplexing at 80 MHz, each carrying independent information per 20 MHz HE-SIG-B and including two channels.

30 shows an example of a technique for maintaining one format for HE-SIG-B transmissions.

FIG. 31 shows an example of HE-SIG-B multiplexing in which large RUs are signaled in each channel.

32 illustrates an example of a HE-SIG-B multiplexing scheme at 80 MHz when one of the channels has 484 tone RU multiplexed.

33 shows an example of a HE-SIG-B multiplexing technique when all channels represent 40 MHz transmissions.

34 shows an example of a HE-SIG-B multiplexing technique when a single 996 tone RU is indicated at 80 MHz.

35 shows an example of a HE-SIG-B multiplexing technique that supports load balancing when multiple RUs are indicated.

36 illustrates HE-SIG-B multiplexing techniques using the HE-SIG-B multiplexing format indicating that common information is allocated in the HE-SIG-B channels.

FIG. 37 shows an example of a duplication scheme and channel structure for multiplexing control information in HE-SIG-B at 160 MHz.

38 shows an example of RU nulling for discontinuous channel bonding.

39 shows an example of RU nulling when an internal channel is nulled using discrete channel bonding.

40 shows an example of RU nulling when two channels are nulled.

41 shows an example of a process for the UE to interpret RU placement when discontinuous channel bonding is used.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly indicates otherwise. The terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by one of ordinary skill in the art as described in the present disclosure. Among the terms used in the present disclosure, terms defined in the general dictionary may be interpreted as having the same or similar meaning as the meaning in the context of the related art, and ideally or excessively formal meanings are not clearly defined in the present disclosure. Not interpreted as In some cases, even if terms are defined in the present disclosure, they may not be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach will be described as an example. However, various embodiments of the present disclosure include a technology using both hardware and software, and thus various embodiments of the present disclosure do not exclude a software-based approach.

The following descriptions are directed to an apparatus and method for efficient signaling and addressing in wireless local area networks (WLANs).

Terms referring to control information used in the following description, terms referring to entries, terms referring to network entities, terms referring to messages, terms referring to components of a device, and the like are described. It is illustrated for convenience. Thus, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

1 illustrates an example of a wireless network. The embodiment of the wireless network shown in FIG. 1 is for illustration only. Other embodiments may be utilized without departing from the scope of this disclosure.

As shown in FIG. 1, the wireless network 100 includes AP 101 and AP 103. The AP 101 and the AP 103 communicate with at least one network 130 such as the Internet, an internet protocol (IP) network, or another data network.

The AP 101 and the AP 103 provide a wireless connection to the network 130 for a plurality of STAs 111 to 114 within the coverage area 120 of the AP 101. The AP 101 and the AP 103 may communicate with each other using Wi-Fi (wireless fidelity) or other WLAN communication technologies. In addition, the AP 101 and the AP 103 may communicate with the STAs 111 through 114 using wireless fidelity (Wi-Fi) or other WLAN communication technologies.

Depending on the network type, other well-known terms such as "router" and "gateway" may be used instead of "AP" or "access point." For convenience, the term "AP" is used in this document to refer to a network infrastructure that provides wireless access to remote terminals. In addition, in a WLAN, an AP is provided for a wireless channel. In addition, the AP may represent an STA. Also, depending on the network type, "STA" or "station" means "mobile station", "subscriber station", "remote terminal", "user equipment", It may be used instead of other well-known terms such as "wireless terminal", "user device", or "user." For convenience, the term "STA" is used herein to refer to a remote wireless device that wirelessly connects to an AP or to a wireless channel in a WLAN. Although a STA is considered a mobile device (eg, a mobile phone or a smartphone) in this document, the STA may be a fixed device (eg, a desktop computer, an AP, a media player, a fixed sensor, a television, etc.).

Dotted lines show approximate extents of the

coverage areas

120 and 125. Here, the

coverage areas

120 and 125 are shown approximately in a circle for illustrative and illustrative purposes. However, the

coverage areas

120 and 125 associated with the AP 101 and the AP 103 are irregular depending on the settings of the APs and changes in the wireless environment associated with natural or artificial obstructions according to the settings of the APs. It may have other shapes including phosphor shapes.

As will be described in detail below, one or more of the APs includes circuitry and / or programming for management of UL MU transmissions in WLANs. Although FIG. 1 illustrates an example of a wireless network 100, various changes may be made in FIG. 1. For example, the wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. In addition, the AP 101 may directly communicate with any number of STAs. In addition, the AP 101 provides the STAs with a wireless broadband connection with the network 103. Similarly, each of the AP 101 and the AP 103 may communicate directly with the network 130 and provide the network 130 with a wireless broadband connection with the STAs. In addition, the AP 101 and / or AP 103 may provide connectivity with other or additional external networks, such as external telephone networks or other types of data networks.

2A shows an example of an AP. The example of the AP shown in FIG. 2A is for illustration only. In addition, the AP 103 of FIG. 1 may have the same or similar configuration as the AP 101. However, this is for the purpose of explanation only and various changes may be made in the APs without departing from the scope of the present disclosure.

As shown in FIG. 2A, the AP 101 includes multiple antennas 204a through 204n, RF transceivers 209a through 209n, a transmit processing circuit 214, and a receive processing circuit 219. The AP 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.

The RF transceivers 209a through 209n receive, via antennas 204a through 204n, received RF signals such as signals transmitted by STAs in the network 100. The RF transceivers 209a through 209n down convert the received RF signals to produce intermediate frequency (IF) or baseband signals. The IF or baseband signals are provided to the receive processing circuit 219, where the receive processing circuit 219 filters, decodes, and / or digitizes the baseband or IF signals to produce a processed baseband signal. The receive processing circuit 219 transmits the processed baseband signal to the controller / processor 224 for further processing.

The transmission processing circuit 214 receives analog or digital data, such as voice data, web data, email, or interactive video game data, from the controller / processor 224. The transmit processing circuit 214 encodes, multiplexes, and / or digitizes transmit baseband data to produce processed baseband or IF signals. The RF transceivers 209a through 209n receive the processed transmit baseband or IF signals from the transmit processing circuit 214. In addition, the RF transceivers 209a through 209n upconvert the baseband or IF signals into RF signals transmitted through the antennas 204a through 204n.

The controller / processor 224 may include at least one processor or other processing circuits that control the overall operation of the AP 101. For example, the controller / processor 224 may be configured such that the RF transceivers 209a through 209n, the receive processing circuit 219, and the transmit processing circuit 214 transmit forward channel signals, or according to a well known principle. reverse) to receive channel signals. The controller / processor 224 may support additional functions such as next generation wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations so that the transmission signals from the multiple antennas 204a to 204n have different weights in order to be transmitted in a desired direction. Any other various functions may be supported at the AP 101 by the controller / processor 224. In some embodiments, the controller / processor 224 includes at least one microprocessor or microcontroller.

Also, the controller / processor 224 may execute programs and other processes (eg, an OS) stored in the memory 229. The controller / processor 224 may move data into or out of the memory 229 according to a request by an execution processor.

In addition, the controller / processor 224 is connected to the backhaul or network interface 234. The backhaul or network interface 234 authorizes the AP 101 to communicate with systems or other devices via a network or via a backhaul connection. The interface 234 supports communication via any suitable wired or wireless connections. For example, the interface 234 permits the AP 101 to communicate with a higher entity (eg, the Internet) through a wired or wireless connection. The interface 234 includes any suitable structure for supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver.

The memory 229 is connected to the controller / processor 224. Part of the memory 229 may include random access memory (RAM), and another part may include flash memory or other read only memory (ROM).

As described in detail below, the AP 101 may include programming and / or circuitry for implementing or using efficient signaling and addressing in a WLAN system. 2A shows an example of the AP 101, but other changes may be made at e 2A. For example, the AP 101 may include each element shown in FIG. 2A in any number. In detail, the AP 101 may include a plurality of interfaces 234. In addition, the controller / processor 224 may support routing functions for routing data between different network addresses. In addition, while FIG. 2A shows one transmit processing circuit 214 and one receive processing circuit 219 per RF transceiver, the AP 101 may include multiple transmit processing circuits and multiple receive processing circuits 219 per RF transceiver. Can be. In addition, according to embodiments, like legacy APs, the AP 101 may include one antenna and one RF transceiver path. In addition, the various components in FIG. 2A may be combined, more branched, or omitted. In addition, the AP 101 may further include additional components as required.

2B shows an example of a STA. The embodiment of the STA 111 shown in FIG. 2B is for illustration only. The STAs 111 to 115 of FIG. 1 may have the same or similar configuration as the STA 111 illustrated in FIG. 2B. However, the STAs can be implemented with various settings in the scope of the present disclosure, and FIG. 2B does not limit other implementations of the STA.

As shown in FIG. 2B, the STA 111 includes multiple antennas 205, RF transceivers 210, transmit processing circuit 215, microphone 220, and receive processing circuit 225. In addition, the STA 111 includes a speaker 230, a controller / processor 240, an input / output (I / O) interface 245, a touch screen 250, a display 255, and a memory 260. The memory 260 includes an operating system (OS) 261 and at least one application 262.

The RF transceiver 210 receives a received RF signal transmitted by an AP of the network 100 through an antenna 205. The RF transceiver 210 down converts the received RF signal to produce an IF or baseband signal. The IF or baseband signal is provided to the receive processing circuit 225. Here, the reception processing circuit 225 filters, decodes, and / or digitizes the baseband or IF signal to generate a processed baseband signal. The reception processing circuit 225 transmits (eg, voice data) the processed baseband signal to the speaker 230. In addition, the receive processing circuit 225 transmits (eg, web browsing data) the processed baseband signal to the controller / processor 240 for further processing.

The transmit processing circuit 215 receives analog or digital voice data from the microphone 220 or other transmit baseband data (eg, web data, email, or interactive video game data) from the controller / processor 240. The transmit processing circuit 215 encodes, multiplexes, and / or digitizes the transmit baseband data to produce a processed baseband or IF signal. The RF transceiver 210 receives the processed transmit baseband or IF signal from a transmit processing circuit 215. In addition, the RF transceiver 210 up-converts the baseband or IF signal to an RF signal transmitted through the antenna 205.

The controller / processor 240 may include at least one processor, and executes the basic OS program 261 stored in the memory 260 to control the overall operation of the STA 111. For example, the controller / processor 240 controls the RF transceiver 210, the receive processing circuit 225, and the transmit processing circuit 215 to receive forward channel signals and transmit reverse channel signals according to well known principles. In addition, the controller / processor 240 may include processing circuitry configured to provide management of UL MU transmissions in WLANs. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.

Also, for example, the controller / processor 240 may execute other processes and programs stored in the memory 260 for operations for implementing or using efficient signaling and addressing in a WLAN system. The controller / processor 240 may move data into or out of the memory 260 according to a request of an execution process. In some embodiments, the controller / processor 240 is configured to execute a plurality of applications 262 including management of UL MU transmissions in a WLAN, such as applications for MU communication. The controller / processor 240 may execute the plurality of applications 262 based on the OS program 261 or may execute the plurality of applications 262 in response to a signal received from an AP. The controller / processor 240 may be connected to the input / output interface 245. The input / output interface 245 provides the STA 111 with the ability to connect with other equipment, such as laptop computers and handheld computers. The input / output interface 245 is a communication path between the controller / processor 240 and accessories.

The controller / processor 240 is connected to the touch screen 250 and the display 255. The operator of the STA 111 may use the touch screen 250 to input data to the STA 111. For example, the display 255 may be a liquid crystal display (LCD), a light emitting diode (LED) display, or other display capable of rendering text and / or at least one limited graphic from a website.

The memory 260 is connected to the controller / processor 240. Part of the memory 260 may include a RAM, and another part may include a flash memory or another ROM.

FIG. 2B merely illustrates an example of the STA 111, and various changes may be made in FIG. 2B. For example, the various components of FIG. 2B may be combined, further branched, or omitted. In addition, the STA 111 may further include additional components as required. For example, the STA 111 may include any number of antennas 205 for MIMO communication with the AP 101. As another example, the STA 111 may not include voice communication. In addition, the controller / processor 240 may be divided into a plurality of processors such as at least one central processing unit (CPU) and at least one graphic processing unit (GPU). In addition, while FIG. 2B illustrates the STA 111 set up as a mobile phone or a smartphone, the STAs may be configured to operate with other types of mobile or fixed devices, such as laptops, desktops, and the like.

3 shows an example of the structure of a header for PPDU transmission. The example of the header structure 300 in FIG. 3 is for illustration only. Other embodiments of the header structure 300 may be used without departing from the scope of the present disclosure.

The header 300 includes training fields and packet type indication fields. The header 300 may include a legacy short training training field (L-STF) 305, a legacy long training field (L-LTF) 310, a legacy signal field (L-SIG) 315, and a VHT signal A (VHT-SIG-A) 320 and 325. , VHT short and long training symbols field 330, and VHT-SIG-B (VHT signal B) 335. Fields with legacy prefix indicate packet type and duration to non-VHT legacy users who may stop further processing of the PPDU after decoding the legacy portions of the header 300. The VHT portion of the preamble includes the VHT-SIG-A, VHT STF, VHT-LTF, and VHT-SIG-B fields.

The VHT-SIG-A is a first portion referred to as VHT-SIG-A1 (eg, field 320 of the header 300) and a second portion referred to as VHT-SIG-A2 (eg, field 325 of the header 300). It includes. The mapping of the space-time block coding (STBC) field, the SU VHT-MCS / MU coding field, and the beamformed field in the VHT-SIG-A1 and VHT-SIG-A2 are different in the VHT-SU and MU-PPDUs. . The SU and MU-PPDUs are distinguished based on the 6-bit GROUP_ID fields carried in bit positions B4 through B9. For example, 0 or 63 represents the VHT-SU-PPDU, otherwise it represents the VHT-MU-PPDU. For each user in the MU-PPDU, the number of spatial streams is indicated using a 3-bit NSTS field. Here, '000' indicates that no spatial streams are transmitted for the user. The VHT-SIG-A field is transmitted at 1/2 code rate using binary phase-shift keying (BPSK) modulation and provides two consecutive OFDM signals.

The VHT-SIG-B field is one symbol and contains 26 bits in a 20 MHz PPDU, 27 bits in a 40 MHz PPDU for each user, and 80 MHz, 160 MHz, and 80 + 80 MHz PPDUs. Contains 29 bits. Fields in the VHT-SIG-B fields are shown in Table 1 below. The interpretation of the fields for the MU or SU PPDU is derived from the 6-bit GROUP_ID field carried in bit positions B4 through B9 in VHT-SIG-A1. Here, 0 or 63 represents a VHT SU PPDU, otherwise it represents a VHT MU PPDU. The VHT-SIG-B length field for user u is

Is set to. Here, APEP-LENGTH _u is a TXVECTOR parameter for APEP_LENGTH for user u. For each user u, the VHT-SIG-B field is a binary convolutional code (BCC) encoded with R = 1/2 and is mapped to a BPSK constellation. Unlike VHT-SIG-A, which is commonly signaled for all users, VHT-SIG-B is user-specific and is N _{STS, u} space by user-specific elements of the first column of the P _VHTLTF matrix. Mapped to time streams.

Table 1: Fields in the VHT-SIG-B Field

The GROUP_ID is instructed to the STA 111 by the AP 101 according to the user location of the STA 111 in at least one group ID. The GROUP_ID is a management frame transmitted to the VHT STAs and includes a membership status array field of length 8 (shown in FIG. 4A) and a user location array field of length 16 (shown in FIG. 4B).

4A shows an example of a membership status array field. The example of the membership status array field 400 shown in FIG. 4A is for illustration only. Other embodiments of the membership status array field 400 may be used without departing from the scope of this disclosure.

In the membership state array field 400 of length 8, the 1-bit membership status sub-field for each group ID is set to 0 if the STA is not a member of the group, and set to 1 if the STA is a member of the group. .

The membership status subfields for group ID 0 (send to AP) and group ID 62 (downlink SU transmissions) are reserved.

4B shows an example of a user location array field. The example of the user location array field 450 shown in FIG. 4B is for illustration only. Other embodiments of the user location array field 450 may be used without departing from the scope of this disclosure.

The user location array field 450 is used in the group ID management frame. And a 2-bit user location subfield for each of the 64 group IDs (indexed by the group ID) of length 16. If the membership subfield for a specific group ID is 1, the corresponding user location subfield is encoded as shown in Table 2 below.

Table 2: Encoding of User Location Subfields

If the membership status subfield for the group ID is 0 (ie, the STA 111 is not a member of the group), the corresponding user location subfield in the user location array field is reserved. The user location subfields for group ID 0 (send for AP) and group ID 62 (downlink SU transmission) are reserved.

5 shows an example of the structure of a HE PPDU. The example of the HE PPDU structure 500 shown in FIG. 5 is for illustration only. Other embodiments of the HE PPDU structure 500 may be used without departing from the scope of the present disclosure.

The HE PPDU 500 includes training fields and packet type indication fields. For example, the HE PPDU 500 may be a PLCP header. The HE PPDU 500 includes a legacy short training field (L-STF) 305, a legacy long training field (L-LTF) 310, a legacy signal field (L-SIG) 315, a replicated L-SIG (RL-SIG) field 520, and a HE. HE signal A (SIG-A) field 525, HE-SIG-B (HE signal B) 530, HE short training field (HE-STF), and HE long training field (HE-LTF) 540. The fields with legacy transposition are for indicating the duration and packet type to non-VHT legacy users who may stop further processing of the PPDU after decoding the legacy portions of the header. The HE portion of the preamble includes the RL-SIG 520, HE-SIG-A 525, HE-SIG-B 530, HE-STF 535, and HE-LTF 540. In the HE-SU PPDU, the HE-SIG-B 530 field does not exist. In the HE-MU PPDU, the HE-SIG-B 530 field exists. In the HE-Extended Range PPDU, the HE-SIG-B 530 field does not exist, and the symbols of the HE-SIG-A 525 are repeated.

The HE-SIG-A 525 may include information required for interpreting the HE PPDUs.

In some embodiments, the HE-SIG-A 525 may include a bandwidth field indicating the bandwidth of PPDUs. For example, the bandwidth field is set to 0 in 20 MHz HE PPDU, set to 1 in 40 MHz HE PPDU, set to 2 in 80 MHz HE PPDU, and set to 3 in 160 MHz and 80 + 80 MHz PPDU. Can be.

In some other embodiments, the HE-SIG-A 525 may include an SIGB MCS field indicating the MCS of the HE-SIG-B 530. For example, the SIGB MCS field is set to 0 when the MCS of the HE-SIG-B 530 is MCS0. The SIGB MCS field is set to 1 when the MCS of the HE-SIG-B 530 is MCS1. When MCS of SIG-B 530 is MCS2, it is set to 2, and when MCS of HE-SIG-B 530 is MCS3, it is set to 3, and when MCS of HE-SIG-B 530 is MCS4, 4, the MCS of the HE-SIG-B 530 may be set to 5 when the MCS of the HE-SIG-B 530 is MCS5. The SIGB MCS field may consist of 3 bits.

In some other embodiments, the HE-SIG-A 525 may include an SIGB DCM field indicating whether the HE-SIG-B 530 has been modulated with dual sub-carrier modulation. . For example, when the HE-SIG-B 530 is modulated with dual sub-carrier modulation, the SIGB DCM may be set to one. For another example, when the HE-SIG-B 530 is not modulated with dual sub-carrier modulation, the SIGB DCM may be set to zero. The SIGB DMC field may consist of 1 bit.

In some other embodiments, the HE-SIG-A 525 may include a SIGB Number of Symbols field indicating the number of symbols of the HE-SIG-B 530. The number field of SIGB symbols may consist of 4 bits.

In some other embodiments, the HE-SIG-A 525 may include an SIGB Compression field indicating whether full BW MU-MIMO is applied. For example, when the full BW MU-MIMO is applied, the SIGB Compression field may be set to one. For another example, when the full BW MU-MIMO is not applied, the SIGB Compression field may be set to zero. The SIGB Compression field may consist of 1 bit.

The HE-SIG-B 530 may be independently encoded for each 20 MHz band.

The HE-SIG-B 530 may include a common block field and a user specific field. The common block field may be referred to as a common part, a common information field, or the like in this document. The user specific field may be referred to as user allocation information or the like in this document.

The common block field may be assigned to RU allocations such as RU arrangement in the frequency domain, RUs allocated for MU-MIMO, and the number of users (which may refer to the number of user fields) in MU-MIMO allocations. It may contain information about.

The user specific field may include a plurality of user block fields. Each user block field may include information about the two STAs in order to decode the payload of the two STAs. When the number of user fields indicated by RU allocation signaling in the common block field is odd, the last user block field of the plurality of user block fields may include only information for one STA.

Various embodiments of the present disclosure provide signaling and addressing techniques for the HE portion supporting OFDMA to apply MU-MIMO and multiplexing of a plurality of users in different portions of bandwidth. In particular, various embodiments provide a HE-SIG-A field 525 and a HE-SIG-B field 530 that carry information required for interpreting HE-PPDUs, respectively. Various embodiments of the present disclosure provide signaling required for supporting indication of bandwidth segments to different STAs in the OFDMA / MU-MIMO multiplexing protocol.

6 shows an example of possible RU locations in a 20 MHz OFDMA PPDU. 7 shows an example of possible RU locations in a 40 MHz OFDMA PPDU. 8 shows an example of possible RU locations in an 80 MHz OFDMA PPDU. The embodiments of the RU locations shown in FIGS. 6-8 are for illustration only. Other RU locations may be used without departing from the scope of this disclosure.

As shown in Figures 6-8, the OFDMA structure for the standard document IEEE 802.11 ax includes the following building blocks.

In the building blocks, 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 486-tone RU are each 26-subcarrier RU, 52-subcarrier RU, 106-subcarrier RU, 486-subcarrier May be referred to as RU.

Possible RU locations in a 40 MHz OFDMA PPDU are equivalent to two replicas of possible RU locations in a 20 MHz OFDMA PPDU. Possible RU locations in an 80 MHz OFDMA PPDU are equivalent to two replicas of possible RU locations in a 40 MHz OFDMA PPDU. One OFDMA PPDU may include a combination of different RU sizes at each of the 242 RU boundaries.

For RUs of different sizes and locations in different bandwidths, embodiments of the present disclosure are provided for efficient signaling and addressing in the allocation of such RUs. Various embodiments of the present disclosure provide an implicit indication of the number of allocations by RU batch indexing, HE-SIG-B multiplexing, derivation of an extension group ID by user location update and concatenation, and the use of the extension group ID. to provide. As used herein, VHT-SIG may represent HE-SIG.

9 shows an example of RU batch indexing in a 20 MHz bandwidth. The embodiment of the RU batch indexing 900 shown in FIG. 9 is for illustration only. Other embodiments of the indexing 900 may be used without departing from the scope of the present disclosure.

Various embodiments of the present disclosure provide RU batch indexing. In one or more embodiments of the present disclosure, placement index 905 of the RU deployment is transmitted in the HE-SIG. The combination of RUs consisting of different RU sizes that progressively span the indicated bandwidth is referred to as RU placement. For example, nine RUs consisting of 26 tones per RU placed at the locations indicated in FIG. 3 are combined and distributed over 20 MHz. In addition, the RU configuration encodes positional information, for example, as shown in FIG. 9, in a 20 MHz PPDU, [52 26 26 26 26 26 26 26], the arrangement 910 is [26 26 52 26 26 26 26 26] different from batch 915. Different RU deployments are indexed and the index 905 of the deployment is signaled in the common copy portion of the SIG-B. Using the index 905, the frequency domain placement of the RUs is directed to the STAs receiving the packet including the header with the HE-SIG. Using indexing of RU placement, common information for all users, embodiments of the present disclosure provide a significant amount of overhead compared to other methods of RU placement signaling that may indicate RU location per each STA scheduled in the PPDU. to reduce overhead. At 20 MHz bandwidth, there are a total of 25 different RU deployments possible. Where each RU arrangement is distributed over the bandwidth, as shown in FIG. Therefore, a total of 5 bits are used to index RU deployments in the 20 MHz bandwidth. As shown in FIG. 9, an index of 0 or 1 (eg, depending on the starting point of the index) may indicate that all RUs are composed of 26 tone RUs.

10 shows an example of HE-SIG-B content including a replicated common signaling portion. The example of HE-SIG-B content 1000 shown in FIG. 10 is for illustration only. Other embodiments of the HE-SIG-B content 1000 may be used without departing from the scope of the present disclosure.

In an embodiment of the present disclosure, user assignment for single user or multi-user PPDUs is indicated in the HE-SIG-B fields. In some other embodiments, user assignments for only multi-user PPDUs (MU PPDUs) are indicated in the HE-SIG-B fields. Allocation information for single-user MIMO PPDUs includes a binary convolution code that is replicated every 20 MHz segment 1005 over the bandwidth indicated in HE-SIG-A. Allocation information for multi-user information includes two parts. The first part is the common information part 1010. For example, the common information portion 1010 is an N_rua (BW) bit RU placement index indicating RU placement in the frequency domain (FD), N_sta bits number of STAs signaled in the allocation, and 1 bit Su per STA. Contains a list of N-bit STA-IDs according to / MU assignment. In sum, there are N_rua (BW) + N_sta (N + 2) bits indicated in the first part. The 1 bit SU / MU allocation indicates whether the STA 111 is part of MU allocation through the RU. The ordering of the STAs determines the user location in the MU assignment.

The reserve STA-ID may indicate that there is no allocation through a specific RU. For example, STA-ID 0 may indicate that the RU is left blank and no data is carried through the RU. The common information portion 1010 may be specified differently for each 20 MHz segments 1005 while data is being transmitted.

The second part is the user specific part 1015 containing user-specific information carried in the 20 MHz segment 1005 when the user's data is transmitted. The user specific portion 1015 in each 20 MHz segment 1005 contains appropriate decoding information for STAs scheduled in RUs within the 20 MHz segment. Each 20 MHz segment 1005 contains the largest batch of RUs in the 242 RU allocation. An allocation less than the 242 RU is carried in a 20 MHz channel, where the center frequency of the 20 MHz channel is closest to the allocation. The allocation per 20 MHz indication carries STA specific information (eg, STBC, beamformed, LDPC coding, LDPC extra symbols, number of spatial streams, MCS of the assignment, etc.). In one example, this information is encoded in CRC, respectively. As another example, this information of all STAs scheduled in the 20 MHz segment is co-encoded by the AP 101 using blind convolutional codes. Since STA-IDs are indicated in the common information portion 1010, the information is arranged in the order in which the STAs are listed in the common information portion 1010 of the signaling.

Users scheduled as part of an MU-MIMO assignment have different information content compared to a single user assignment. For example, the MCS of MU-MIMO information may be the same for all users, and the MCS field may be common for users scheduled in MU-MIMO. When users are scheduled using MU-MIMO over the full bandwidth, the user specific information portion 1015 is common in all 20 MHz segments 1005 and replicated in each segment 1005. STAs scheduled in this MU-MIMO allocation may derive the information from the SU / MU bit indicator and the RU placement index in HE-SIG-A. As another example, the STAs may derive this information from a 2-bit SU / MU indicator where the 2-bit index indicates MU-MIMO over the full bandwidth.

Allocations larger than 20 MHz or scheduling information for users scheduled in the center 26 tone RU of the 80 MHz allocation may be carried in one or more portions. For example, the center 26 tone scheduling information may be carried as the last allocation information at 20 MHz, where the 20 MHz subcarrier index is located before the first subcarrier index of the center 26 tone RU. As another example, the center 26 tone scheduling information may be carried as the first allocation information in the 20 MHz segment, where the subcarrier index of the 20 MHz segment is greater than the first subcarrier index of the center 26 tone RU. As another example, central 26 tone scheduling information may be replicated in 20 MHz segments around 26 tone allocations. The order of the STA-IDs indicated in the common part is maintained when carrying information about the center 26 ton RU carried using any of the three examples described above.

In an embodiment of the present disclosure, user assignments for multi-user PPDUs are indicated in the HE-SIG-B fields. Allocation information for multi-user information may include a common portion indicating an allocation index and other common fields (eg, common information portion 1010) and a signaling portion per 20 MHz (eg, having fields carried as described above). User specific portion 1015). Allocation information for a single user PPDU is carried in the HE-SIG-A.

11 shows an example of HE-SIG-B signaling. The example of HE-SIG-B signaling 1100 shown in FIG. 11 is for illustration only. Other embodiments of the HE-SIG-B signaling 1100 may be used without departing from the scope of the present disclosure.

In an embodiment of the present disclosure, the user data indicated by the HE-SIG-B per 20 MHz carrying signaling information and the signaling information is carried in the same 20 MHz frequency channels as shown in FIG. 11.

In the embodiment shown in FIG. 11, the MCS used for common fields and user specific fields of the HE-SIG-B in each 20 MHz segment may be different. MCS for HE-SIG-B may be signaled in one or two ways. As an example, the MCS for each 20 MHz segment is indicated in HE-SIG-A. As another example, the MCS for each 20 MHz segment is carried in a section of HE-SIG-B common fields. This section of the HE-SIG-B common fields may indicate an MCS for resource allocation and remaining allocation information, and may be independently encoded according to a fixed MCS.

In an embodiment of the present disclosure, the common part and the user specific part of the allocations per 20 MHz may be encoded together using a blind convolutional code. STAs decode each HE-SIG-B in a 20 MHz segment to identify whether the section carries information for the STAs.

In an embodiment of the present disclosure, the common part including the STA-IDs and the user assignment may be encoded per 20 MHz segment independently from the user specific part. In this embodiment, the user specific portion is encoded in an independent convolutional code.

In an embodiment of the present disclosure, a 26 tone RU divided around DC tones may remain unused in an 80 MHz MU PPDU.

In an embodiment of the present disclosure, resource allocation for a 26 ton RU divided around DC tones of an 80 MHz MU PPDU is indicated by an extra bit in any one of the 20 MHz segments or all 20 MHz segments around DC tones. Can be replicated in the field. The presence of the additional bits is triggered by bandwidth signaling when set to 80 MHz. The additional bit is located immediately before the 5-bit RU placement indication for the 20 MHz segment. The STA ID and the user specific portion are subsequently placed in the order of the same as the RU placement indication.

12 shows an example of an extended group ID or a connection group ID generated by connecting two group IDs. The example of group ID 1200 shown in FIG. 12 is for illustration only. Other embodiments of the group ID 1200 may be used without departing from the scope of this disclosure.

Embodiments of the present disclosure provide an extended group ID 1200 and an updated user location. In an embodiment of the present disclosure, a new MU-MIMO allocation for the entire bandwidth or a new MU-MIMO allocation in a particular RU is indicated by an extension group ID derived by concatenating two

group IDs

1205 and 1210. Here, the concept of group ID is defined in the IEEE 802.11 ac standard. STAs are indicated which group they belong to using user location management messages and a group ID.

Group IDs

1205 and 1210, each 6 bits, represent a group of four users. Here each user is instructed using 0 (00) to 3 (11). As shown in FIG. 12, the concatenation of

group IDs

1205 and 1210 generates an extended group ID 1200 of 12 bits. 6 bits of the 12 bits represent the first group ID 1205 and the remaining 6 bits represent the second group ID 1210.

User locations are updated to reflect this connection. That is, as shown in FIG. 13, users in the first group ID maintain their positions from 0 (000) to 3 (011) and users in the second group have their (4) from 4 (100) to 7 (111). Update your location. The concatenation of group IDs extends the number of users that can be scheduled in the MU-MIMO allocation to eight.

13 shows an example of a user location updated based on a group ID connection. Other embodiments may be utilized without departing from the scope of this disclosure. In the remaining six bits of the connection group ID 1200, the user of the reserve group ID index (eg, group ID 0 or group ID 63) in the system indicates a no-enlargement of the MU-MIMO user group, and the MU The maximum number of users scheduled in a MIMO user group is four. Only the six bits of users of connection group ID 1200 are scheduled in the MU-MIMO assignment.

Embodiments of the present disclosure provide the use of a group ID and the number of derived assignments. In this embodiment, user assignments for both single and multi-user PPDUs are indicated in the HE-SIG-B fields. Allocation information for single-user MIMO PPDUs includes a binary convolutional code component that is replicated every 20 MHz segments 1005 for the bandwidth indicated in HE-SIG-A. As mentioned above, the allocation information for multi-user information includes two parts. The common information portion 1010 is a list of group IDs (for MU-MIMO allocation) or N bits of STA-ID (for SU allocation) according to 1 bit SU / MU allocation per ID and N_rua bits indicating RU placement in the frequency domain. RU placement index. Overall, there are N_rua (BW) + N_sta (N + 1) information bits indicated in common information portion 1010. The 1 bit SU / MU allocation indicates whether a successful N bit ID is a group ID or a STA ID. The group ID used may be the connection group ID described in the embodiments as described above, or may be a new extended group ID mechanism used for 802.11 ax. User locations are updated when the association of group ID is used. The reserve STA-ID may indicate that there is no assignment for a particular RU. For example, STA-ID 0 may indicate that the RU is empty and no data is carried through the RU. The common information portion 1010 may be specified for each 20 MHz segment and may be different for each 20 MHz segment through the data transmitted.

The second portion is user specific information portion 1015 including user specific information from which user data is transmitted and carried within a 20 MHz segment. Each 20 MHz segment contains an arrangement of RUs with up to 242 RU allocations. As shown in FIG. 10, all RU deployments deployed in these 242 RUs are carried in a 20 MHz channel, with the center frequency of the 20 MHz channel as close as possible to the allocation. This allocation per 20 MHz indication carries, for example, STA specific information, STBC, beamforming or not, LDPC coding, LDPC additional symbols, number of spatial streams, MCS of allocation, and so forth. In one example, this information is encoded separately including the CRC. As another example, the information of all STAs scheduled in the 20 MHz segment is commonly encoded by the AP 101 using a blind convolutional code. Since the STA-IDs are indicated in the common information portion 101, the information is arranged in the order in which the STAs are listed in the common information portion 1010 of the signaling.

Users scheduled to be part of the MU-MIMO assignment may have different information content than a single user assignment. For example, the MCS of the MU-MIMO information may be the same for all users, and the MCS field may be common for users scheduled in MU-MIMO. If users are scheduled using MU-MIMO for all bandwidths, the user specific information portion 1015 is common in all 20 MHz segments 1005 and replicated for each segment 1005. STAs scheduled in this MU-MIMO allocation may derive the information from the SU / MU bit indicator and the RU placement index in HE-SIG-A. As another example, the STAs may derive this information from the 2-bit SU / MU indicator in the case where a particular 2-bit index indicates MU-MIMO for the entire bandwidth.

Scheduling information for users scheduled in the central 26-ton RU of allocations above 20 MHz or in the 80 MHz allocation may be carried in one or more portions. As an example, the center 26 tone scheduling information may be carried as the last allocation information at 20 MHz, where the subcarrier index of 20 MHz is located before the first subcarrier index of the center 26 tone RU. As another example, the center 26 tone scheduling information may be carried as first allocation information in a 20 MHz segment, where the subcarrier index of the 20 MHz segment is greater than the first subcarrier index of the center 26 tone RU. As another example, the central 26 tone scheduling information may be replicated in 20 MHz segments around the central 26 tone allocation. The order of the STA-IDs indicated in the common part is maintained when carrying information for the center 26 ton RU in the case of carrying using any of the three examples described above.

In an embodiment of the present disclosure, user assignment for multi-user PPDUs is indicated in the HE-SIG-B fields. The allocation information for multi-user information includes a common portion representing the allocation index and other common fields as described above (eg, common information portion 1010) and a signaling portion per 20 MHz having fields carried as described above ( For example, user specific portion 1015). Allocation information for a single user PPDU is carried in the HE-SIG-A.

In an embodiment of the present disclosure, the number of OFDM symbols used to carry the common portion may vary, and the number of OFDM symbols is within a pilot symbol of a recent OFDM symbol carrying the common portion HE-SIG-B. Can be indicated by a phase change. The number of OFDM symbols used to carry the signaling portion per 20 MHz may vary, and the number of OFDM symbols may be indicated by the phase change in the pilot symbols of recent OFDM symbols carrying the signaling portion per 20 MHz. . In another embodiment, the number of OFDM symbols used in the signaling portion per 20 MHz of the HE-SIG-B may be derived from the allocation size in the common portion and may not be explicitly signaled.

In an embodiment of the present disclosure, resource allocation information may be indicated according to user specific information in a self-included block. Here the user has all the information necessary to encode the data assigned to it. Each block includes information such as STA_ID, MCS / MIMO, and other fields needed to decode the data, resource location index, and CRC from which the STA_ID can be derived. The STA 111 decodes each block and checks whether allocations transmit to the above-mentioned information. The STA 111 continues decoding until all allocation blocks are fully decoded. Multiple RUs may be assigned to the STA. In an embodiment of the present disclosure, each self-inserted block is encoded independently using a convolutional code. In an embodiment of the present disclosure, multiple self-inserted blocks supporting the same MCS may be encoded together using a convolutional code.

14 shows an example of RU location indexing for 20 MHz. 15 shows an example of RU location indexing for 40 MHz. 16 shows an example of RU location indexing for 80 MHz. The example embodiment of RU location indexing shown in FIGS. 14-16 is for illustration only. Other RU location indexing may be used without departing from the scope of this disclosure.

In the embodiments shown in FIGS. 14-16, the resource allocation information carried in the self-inserted block includes the index of the RU carrying the MPDU for the signaled STA. The RU index is an algebraic index of the RU according to the size of the RU. For example, nine 26 tone RUs, four 52 tone RUs, two 106 tone RUs, and one 242 tone RUs (ie, four bits for 20 MHz as shown in FIG. 14). It can be described by the 16 RU index that can be represented by (). For the 40 MHz bandwidth scenario, FIG. 15 shows 33 different RU indices using 6 bits to represent the various indices. For the 80 MHz bandwidth scenario, FIG. 16 shows 69 different RU indices. Here, the AP 101 transmits 7 bits for RU indexing.

The size of the RU location index carried in the block of user allocation information varies with the bandwidth information signaled in the HE-SIG-A. When the size of a block of user assignment is fixed, additional bits required for RU location indication may be derived by reducing the size of the partial STA-ID signaled in the block. For example, in a 20 MHz MU PPDU, the STA-ID may use 9 bits, and RU location indexing is 5 bits (4 bits + 1 bit reserved). In a 40 MHz MU PPDU, the STA-ID may use 8 bits and the RU location indexing may be 6 bits. In an 80 MHz MU PPDU, the STA-ID may use 7 bits and the RU location indexing may be 7 bits.

In an embodiment of the present disclosure, a block of allocation information for the STA 111 in the MU PPDU may be derived from a 20 MHz segment different from the 20 MHz segment carrying data for the STA. This fluidity applies better packing efficiency and load balancing for HE-SIG-B. RU location indexing represents any one RU in the bandwidth, so that a block of allocation information for STA 111 in the MU PPDU may be carried at either 20 MHz, without proximity to the location of the assigned RU in the bandwidth. .

In an embodiment of the present disclosure, MCSs used for differently self-inserted blocks or groups of self-inserted blocks are different. The MCS used for each group is signaled in the HE-SIG-A or in common information in the HE-SIG-B. The use of different MCSs may be different for different OFDM symbols and / or portions of bandwidth provided by the HE-SIG-B.

17 shows an example of RU batch indexing 1700 up to 242 tone RUs. The example of the RU batch indexing 1700 shown in FIG. 17 is for illustration only. Other embodiments of the header structure 1700 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 17, RU placement indexing 1700 includes a plurality of indices 1705 that indicate a particular RU placement 1710 for a 20 MHz resource bandwidth. When a fixed location of RUs is provided in an OFDMA tone plan, a list of possible RU placements for a particular bandwidth is specified and signaled. The RU batch indexing 1700 for a 20 MHz bandwidth with distribution up to 242 ton RUs is used as a building block for larger bandwidth indexing. The process of specifying the RU placement applies liquidity to the signal of the supported RU placements for the specified bandwidth. When using four building blocks, a 26 ton RU, a 52 ton RU, a 106 ton RU, and a 242 ton RU, the 20 MHz channel applies 26 different RU arrangements as shown in FIG. 17. Thus, the AP 101 uses five signaling bits to indicate the RU placement indexed according to FIG. 17. In addition, to remove the bandwidth characteristic, five signaling bits can be used to indicate the size of the four RU building blocks as well as the RU placement (26 RU placements).

18 shows an example of extended RU placement indexing to indicate large RU sizes. The example of extended RU placement indexing 1800 shown in FIG. 18 is for illustration only. Other embodiments of extended RU placement indexing 1800 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 18, the RU batch indexing 1800 can be directed to use up to a 5-bit budget (ie, 5-bit can signal 32 different probabilities) as described above. Expanded to provide six or more RU deployments. Extended RU batch indexing 1800 represents larger RU building blocks. As shown in FIG. 18, the 484 tone RU, the 996 tone RU, and the 1992 (2 * 996) tone RU may be signaled by transmitting an index 1805 encoding the RU placement.

The standard document IEEE 802.11 ax will support MU-MIMO in RUs of sizes greater than 106 tones. RU arrangements indicating usage of RUs above 106 tone RUs may be included in the MU transmission. Accordingly, various embodiments of the present disclosure provide signaling for RU placement that is accommodated to represent MU-MIMO resources. In particular, the signaling provides content of a common arrangement that specifies RU placement and MU-MIMO resource information. The provided signaling not only identifies MU-resources, but also indicates the number of users scheduled in the MU-resources.

In an embodiment of the present disclosure, the number of users scheduled using MU-MIMO is explicitly signaled. If MU-MIMO capable of RU is signaled in the RU deployment, the bits after the RU deployment indicate the number of users per MU allocation. Since some RU sizes may support MU-MIMO, the bit sequence will be all zero if the RU sizes do not support MU-MIMO or if no MU-MIMO is used in the PPDU. If RU deployments are indicated at 242 tone RUs or 20 MHz, there may be a maximum of two RUs distributed in the same bandwidth as the 242 tone RU that can carry MU-MIMO in the PPDU. If up to eight users can be carried in the MU-MIMO PPDU, each RU capable of transmitting MU-MIMO uses three bits. Therefore, a maximum of 6 bits may be used with a granularity of 242 tone RU per SIG-B channel (ie, 3 bits per 106 tone RU). Common information includes a 6 bit indication and 5 bit RU placement for the number of users in the MU-MIMO resource. If an RU size larger than 106 tons RU is indicated in the deployment, a least significant bit (LSB) 3 bits is used to indicate MU-MIMO users. A non-zero indication of 3 bits indicates that MU-MIMO is activated, and a specific value of 3 bits indicates the number of users signaled in the MU-MIMO resource. If the RU deployment cannot use MU-MIMO, AP 101 sets the number of STA users per MU field to '000000'.

19 shows an example of a signaling message that includes the number of users per MU allocation and a portion of common information that carries RU information. The example of signaling message 1900 shown in FIG. 19 is for illustration only. Other embodiments of the signaling message 1900 may be used without departing from the scope of this disclosure.

As shown in FIG. 19, the RU Placement Field 1910 and the Number of Users per MU-MIMO Resource field 1915 form the common information portion 1905 of the HE-SIG-B channel in the 20 MHz segment. The signaling part 1920 per user located after the number of users per MU-MIMO resource field 1915 carries information for each user separately. The number of users for the information carried is derived from the number of users indicated in MIMO resources and the number of RUs indicated in RU placement field 1910. The total number of information elements per STA carried is derived from the number of users and the number of RUs in MU-MIMO. Each of the information elements per STA carries a STA-ID field having a bit width to identify the STA 111 scheduled in the MU-PPDU. Information elements per STA are encoded together in groups as shown in FIG. 19.

20 shows an example of a signaling message that includes a common information portion carrying an MU flag and an RU placement. The example of signaling message 2000 shown in FIG. 20 is for illustration only. Other embodiments of the signaling message 2000 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 20, the signaling message 2000 includes an MU flag field 2015 located after the RU placement field 2010 indicating whether an RU capable of carrying MU-MIMO carries MU-MIMO in a transmitted PPDU. do. If RU deployments are indicated at 242 ton RUs or a granularity of 20 MHz, there are up to two RUs distributed in the same bandwidth as the 242 ton RU that can carry MU-MIMO in the PPDU. Therefore, the 2-bit MU flag in the field 2015 indicates whether the MU is supported in RU size (1 bit per 106-tone RU). In this example, the flag is set to zero if MU-MIMO is not used in the PPDU or if the RU deployment does not use MU-MIMO. The flag is set to 1 when the indicated RU carries MU-MIMO (e.g., the first bit of the flag representing a first RU of 106 tons in size and the second RU of 106 tons in size Second bit). For 106 ton RU or 242 ton RU and larger sized RU deployments, the LSB of the 2-bit flag may indicate that the MU resource for the indicated RUs may be set to indicate the presence of MU-MIMO in the resource. have. The RU placement field 2010 and the MU flag field 2015 are included in the common information portion 2005 in the HE-SIG-B channels as shown in FIG. 20.

The per-user signaling portion 2020 is located after the common information portion 2005 in the HE-SIG-B and carries information used to identify users as well as to decode information for the data PPDU for the users. Resource allocations assigned to a single user are identified by the STA-ID and have a specific size. MU-MIMO RU assignments are identified using S IDs and a group ID of a different size. Information for all users scheduled using MU-MIMO at the RU is carried together, and the users are identified using a common group ID. The size of the MU allocation information is different from the size of the SU allocation information. MU users are signaled and encoded together. SU assignment information is signaled independently, and groups of SU assignments can be encoded together or independently. If the MU flag indicates the presence of the MU-MIMO allocation, the STA 111 identifies that the allocation information is the MU allocation at a position corresponding to the RU position in the bandwidth, and has a different size from the STA allocation as shown in FIG. 20. .

FIG. 22 shows an example of a signaling message that includes a common information portion 2205 that includes a resource allocation field that includes an integrated MU-MIMO RU flag and an integrated RU configuration. The example of the signaling message 2200 shown in FIG. 22 is for illustration only. Other embodiments of the signaling message 2200 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 22, the RU placement and MU-MIMO flags are encoded together in the RU placement and MU field 2210. RU Placement and MU field 2210 is a transmission sequence of bits that form the common information portion 2205 of the HE-SIG-B channel. In addition to the 29 indices representing the RU deployments as shown in FIGS. 17 and 18, additional additional placement fields representing the same RU deployments but different are added. One batch field indicates the SU batch, and the other batch field indicates the presence of MU-MIMO. For example, index 3 (e.g., Figure 17), 30, 31, and 32 (e.g., Figure 21) indicate that index 3 represents SU, and that

indexes

30, 31, and 32 represent MU-MIMO in all or part of a 106-ton RU. The same configuration is indicated except for the presence of [106 26 106]. From 20 indexes without MU-MIMO, there are 15 additional indexes with at least one RU used in MU-MIMO. As a result, a total of 44 RU indices increase signaling overhead by 6 bits and are carried in the common information portion 2205 of the HE-SIG-B as shown in FIG. Additional placement indexes 2105 are indicated in FIG. 21. 21 shows an example of RU placement indexing 2100 that includes additional indexes 2105 for RU placements in signaling MU-MIMO resources. The example of RU batch indexing 2100 shown in FIG. 22 is for illustration only. Other embodiments of RU batch indexing 2100 may be used without departing from the scope of this disclosure.

The process of encoding MU-MIMO RUs according to RU placement cannot clearly distinguish the number of users per MU-MIMO RU when STA-ID addressing is used. In an embodiment, additional signaling bits are used to indicate the number of users and carried in the common information portion 2205 of the HE-SIG-B channel.

As shown in FIG. 22, the signaling portion 2220 per user is located after the common information portion 2205 for the HE-SIG-B channel and carries information used to identify the users as well as decoding information for the data PPDU for the users. do. RU resources allocated to a single user are identified by STA-ID and have a specific size. MU-MIMO RU assignments have a different size from SU assignments and are identified using the group ID. Information for all users scheduled using MU-MIMO at the RU is carried together and identified using a common group ID. The size of MU-allocation information is different from SU allocations. Multiple users are signaled and encoded together. The S assignment information can be groups of SU assignments that can be signaled independently and encoded independently or together. When the RU configuration indicates an MU-MIMO RU, the STA 111 indicates that the allocation information of the location corresponding to the RU location in bandwidth is MU allocation and has a different size from the STA allocation as shown in FIG. 22. It can be recognized.

FIG. 24 shows an example of a signaling message including common information portion 2405 that includes both the number of users and RU placement for MU-MIMO RUs in the HE-SIG-B. The example of signaling message 2400 shown in FIG. 24 is for illustration only. Other embodiments of the signaling message 2400 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 24, the resource allocation index signaled in the common information portion 2405 of the HE-SIG-B channel includes RU placement, whether MU-MIMO-capable RUs can carry MU-MIMO, and MU-MIMO. An indication of the number of users multiplexed using. The resource allocation index transmitted will differ only when different RU deployments are used or the number of different users multiplexed using MU-MIMO and used for the same RU deployments. Since up to eight users can be multiplexed in the MU-MIMO allocation, eight indices representing different numbers of users in MU-MIMO are available at the RU in the same RU deployment. Listed indices that jointly encode the number of users and RU placement in the MU-MIMO index are shown in FIG. 23. 23 here shows an example of indexing including the number of users and RU deployments for MU-MIMO resources. The example of indexing 2300 shown in FIG. 23 is for illustration only. Other embodiments of the indexing 2300 may be used without departing from the scope of the present disclosure.

For example, as shown in FIG. 23,

indexes

3 and 4 indicate RU placement over the channel [106 26 106]. Index 4 represents MU MIMO in the first RU with two users and S in the remaining RUs, while index 3 represents S transmissions in the RU. There are a total of 64 different indices representing the same RU configuration [106 26 106]. Here, each of the different indices is for different users in MU-MIMO available 106 tone RUs. In order to enable different RU sizes and placements, a total of 175 different 175 indices can be signaled and eight carried in the common information portion 2405 of the HE-SIG-B channel as shown in FIG. 24. Use signaling bits.

The joint representation of the total number of MU-MIMO users and the RU placement in MU-MIMO is derived through the compact common information field and identifies the number of information fields per user placed after the compressed common information field. The per-user signaling portion 2420 is located after the common information portion for the HE-SIG-B and carries information needed to identify the users as well as decoding information for the data PPDU for the users. In MU-MIMO, both group ID addressing and STA-ID are authorized. An information element per user for each user identified through the STA-ID is shown in FIG. 24.

In some embodiments, the RU allocation index may communicate indices representing resources not used and resources used. The total number of information fields per STA is changed according to the number of used resources indicated by the index. Resource fields per STA may not be transmitted for resources indicating that they are not used in the resource allocation index. For certain deployments with more than RU sizes, a central 26 ton RU may not be used and may be assigned to any STA-ID to improve padding efficiency as shown in Table 3 below.

Table 3: RU Indexes for Improved Padding Efficiency

Four different settings for representing RU placement and MU-MIMO resources in the common information portion of the HE-SIG-B have been described in the description of FIGS. 19, 20, 22, and 24. The contents of signaling selection for the four different settings and the user signaling portion, indicating the number of bits used or required for each of the four different settings, are collectively shown in FIG. 25. Examples of the four different settings are for illustration only. Other embodiments of the above-described settings may be used without departing from the scope of the present disclosure.

Settings

1 and 4 clearly identify the number of users in the MU-MIMO allocation used at the RU and are flexible. These settings tend to perform STA-ID signaling with improved efficiency, but are flexible to accommodate either dynamic ID for either the STA-ID or the next user signaling portion.

Settings

2 and 4 may be supported using group IDs indicating users in MU-MIMO allocation since the MU-flag that is independently or jointly indicated does not clearly indicate the number of users in the MU-MIMO allocation. .

As described above, the common block field in the HE-SIG-B 530 may carry RU allocation subfields. According to the PPDU bandwidth, the common block field may include a plurality of RU allocation subfields. The RU allocation subfield in the common block field of the HE-SIG-B 530 may be configured with 8 bits. In addition, the RU allocation subfield may include information on RU arrangement and information on the number of user fields.

The RU placement in the frequency domain indexes the size of the RUs and the location of the RUs in the frequency domain. The number of user fields in each RU in the HE-SIG-B content channel indicates the number of users multiplexed in the RUs indicated by the RU placement. For example, the number of user fields in the RU indicates the number of users multiplexed using MU-MIMO, for RUs of 106 tones or more that support MU-MIMO.

The mapping of the 8-bit RU allocation subfield to the number of user fields per RU and RU placement may be defined as shown in Table 4 below.

Table 4- RU Allocation Signaling: Number and Placement of MU-MIMO Allocations

In Table 4, "Number of entries" represents the number of 8-bit indexes indicating that the same RU arrangement in the frequency domain, but the number of user fields per RU is different. The RU placement and the number of user fields per RU indicate the number of user fields in the user specific field of the HE-SIG-B.

In addition, the user specific field in the HE-SIG-B 530 is composed of a plurality of user fields. The user fields are located after the common block field of the HE-SIG-B. The location of the RU assignment subfield in the common block field and the user field in the user specific field identifies the RU used to transmit data of the STA.

Each of the user fields may include a STA ID field addressing an STA and an MCS field indicating an MCS.

FIG. 26 shows an example of a HE-SIG-B channel transmission format at 20 MHz that includes a common information portion such that the per-user allocation information portion is located behind. The example of the HE-SIG-B channel transmission format 2600 shown in FIG. 26 is for illustration only. Other embodiments of the HE-SIG-B channel transmission format 2600 may be used without departing from the scope of the present disclosure.

In the embodiment shown in FIG. 26, the HE-SIG-B format 2600 in a 20 MHz MU PPDU is configured using the common information portion 2605 to allow allocation information portion 2610 per user to be located behind. The RU placement and MU-MIMO information is signaled to the common information portion 2605 which causes the per-user allocation information portion 2610 to be located behind. The STA 111 uses the location and common information portion 2605 of the per-user assignment of the STA to explicitly identify the RU containing the STA's data.

FIG. 27 shows an example of a HE-SIG-B channel transmission format in a 40 MHz bandwidth including two HE-SIG-B channels. The example of the HE-SIG-B channel transmission format 2700 shown in FIG. 27 is for illustration only. Other embodiments of the HE-SIG-B channel transmission format 2700 may be used without departing from the scope of the present disclosure.

In the embodiment shown in FIG. 27, the HE-SIG-B format 2700 in a 40 MHz MU PPDU includes two

channels

2715 and 2720. The HE-SIG-

B channels

2715 and 2720 each carry different information and indicate RU standing in up to 242 tone RUs distributed over the 20 MHz channel in which the RU is carried. Thus, HE-SIG-B channels contain control information in a 20 MHz subcarrier located close to the data subcarriers.

Channels

2715 and 2720 each contain RU allocation information for the scheduled user and include common information portion 2705 as well as user specific information portion 2710. The common part and the user specific part in the first HE-SIG-B channel 2715 indicate allocation information for users scheduled at the first 20 MHz, and the user specific part and the common part in the second HE-SIG-B channel 2720 are the second part. Represents allocation information for a user scheduled at 20 MHz. HE-SIG-

B channels

2715 and 2720 may be of different sizes and may represent different numbers of users. However, the

channels

2715 and 2720 end in the same symbol. If the number of users indicated is different for each HE-SIG-B channel, the HE-SIG-B channel indicating fewer users requires padding to equalize the length of all HE-SIG-Bs, ensuring symbol alignment. do.

FIG. 28 shows an example of a HE-SIG-B transmission format when a 484 tone RU is signaled to indicate transmission for the entire 40 MHz bandwidth. The example of the HE-SIG-B channel transmission format 2800 shown in FIG. 28 is for illustration only. Other embodiments of the HE-SIG-B channel transmission format 2800 may be used without departing from the scope of the present disclosure.

In the embodiment shown in FIG. 28, when the 484 unit RU is scheduled in a 40 MHz MU PPDU, the two HE-SIG-

B channels

2815 and 2820 will indicate the same information. That is, the contents of the first HE-SIG-B channel 2815 are duplicated in the second HE-SIG-B channel 2820 as shown in FIG. 28.

In some other embodiments, if a 484 unit RU is scheduled in a 40 MHz PPDU, the allocation information per user may be uniformly distributed over two HE-SIG-B channels. For example, if N users are scheduled in the MU-PPDU, each HE-SIG-B channel is

It can contain up to 25 assignment fields. Where from 1 to

User allocation information is carried in the first HE-SIG-B channel,

+1 to N user allocation information is carried in the second HE-SIG-B channel. Common information signaling in MU-PPDU with 484 tone RU configuration may be duplicated in each HE-SIG-B channel or indicated in HE-SIG-A. When signaled in the HE-SIG-A, common information is not present in the HE-SIG-B channels.

FIG. 29 shows an example of a HE-SIG-B multiplexing scheme at 80 MHz that includes two channels each carrying independent information for each 20 MHz HE-SIG-B channel. The example of the HE-SIG-B multiplexing technique 2900 shown in FIG. 29 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 2900 may be used without departing from the scope of the present disclosure.

In the embodiments shown in FIG. 29, the HE-SIG-B multiplexing technique 2900 in an 80 MHz MU PPDU includes two

channels

2915 and 2920 as shown in FIG. 29. HE-SIG-

B channels

2915 and 2920 each carry different information, and HE-SIG-

B channels

2915 and 2920 are replicated every 40 MHz. That is, the second HE-SIG-B channel 2920 is carried in channels B and D of 80 MHz, while the first HE-SIG-B channel 2915 is carried in channels A and C of 80 MHz. The 80 MHz channel comprises four 20 MHz segments identified as channels A, B, C, and D in FIG. 29, and multiplexed or used to decode the PPDU for users scheduled in each of these segments. Lexing information should be mapped to two HE-SIG-B channels replicated every 40 MHz.

Channels A, B, C, and D may be defined as segments to indicate subcarrier granularity corresponding to 242 tone RUs, and smaller RU sizes when concatenated and distributed to the same specification as 242 tone RUs May signal RU deployments. Per user allocation information and RU placement information for segments A, B, C, and D are mapped to two HE-SIG-B channels as described below.

The common information portion 2905 in the first HE-SIG-B channel 2915 includes common information for segments A and C, and indicates an RU placement of up to 242 ton RU granularity in segments A and C, and the number of users ( As well as MU-MIMO resources. Common information for both segments A and C is encoded together using a convolutional code. The per user allocation information portion 2910 follows the common portion, where the per user allocation information indicated by segment A is transmitted before the per user allocation information indicated by segment C. The number of allocations per user is derived from the common information for each segment, and the total number of allocations per user is the sum of the allocations derived from the placement for each segment.

The common information portion 2905 in the second HE-SIG-B channel 2920 includes common information in segments B and D, indicates a granularity RU placement of up to 242 ton RUs in the segments, as well as the number of users (if needed) Represents MU-MIMO resources. Common information in segments B and D is encoded together using a convolutional code. Per user allocation information is located after the common information. Here, the per user allocation information indicated by the RUs in segment B is transmitted before the per user allocation information indicated by the RUs in segment D. The number of allocations per user is derived from common information in each segment, and the total number of allocations per user is the sum of the allocations derived from the placement for each segment.

The common information portion 2905 of one of the HE-SIG-Bs includes one bit indicating whether a central 26 tone RU is assigned to the user. For convenience, this indication may be carried in the first HE-SIG-B channel 2915 after the RU placement for the segments is indicated and encoded together. If the bit is set to 1, after user assignments for segments A and C are carried, the per-user assignment information is carried at the end.

The STA 111 determines the location of the allocation in the segment based on the RU placements indicated by minus the offset determined by the number of user allocations for segments carried before the current segment in the same HE-SIG-B channel. Compute the RU index of the data PPDU for the user. For the first segment indicated, no offset needs to be calculated. In terms of reliability constraints, replication of HE-SIG-B channels applies control information to have redundancy within 20 MHz subcarriers located close to the data subcarriers, and each HE-SIG associated with the data MCS used. -Apply MCS application on channel B.

Embodiments of the present disclosure may cover that the efficiency of the HE-SIG-B multiplexing technique shown in FIG. 29 may be scaled up so that larger RU sizes (eg, larger than 242 tone RU) may be used. Thus, embodiments of the present disclosure provide a variant to maintain efficiency at larger RU sizes. 30 shows an example of a technique for maintaining one format for HE-SIG-B transmission. In the example shown in FIG. 30, for 80 MHz bandwidth signaling [484 26 484] deployment, maintaining granular mapping in two segments and 242 tone segments per HE-SIG-B channel is all replicated HE. Output SIG-B (ie, the same information is carried in each of the HE-SIG-B channels).

31 shows an example of a HE-SIG-B multiplexing scheme 3100 in which larger RUs are signaled in each channel. The example of the HE-SIG-B multiplexing technique 3100 shown in FIG. 31 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 3100 may be used without departing from the scope of the present disclosure.

In this embodiment, the HE-SIG-B multiplexing scheme 3100 switches to the size of the RU to be signaled and flexibly configures particle size mapping to provide an efficient approach for maintaining information distinguished in the HE-SIG-

B channels

3115 and 3120. to provide. Information about larger RU sizes is based on the RU size carried by signaling mapping granularity per HE-SIG-B channel and used in the MU-PPDU. For example, if two 484 tone RUs are signaled in the MU PPDU, the RU placement at [80 MHz] is [484 26 484], and for channels C and D distributed in the 484 tone RU as shown in FIG. Common information is carried in the second HE-SIG-B channel 3120, while common information for channels A and B distributed in the 484 tone RU is carried in the first HE-SIG-B channel 3115. The allocation information portion 3110 per user is located behind the common information portion 3105 and carries information for users scheduled in the segment for each channel. HE-SIG-

B channels

3115 and 3120 are replicated every 40 MHz. The common information portion 3105 of one of the HE-SIG-

B channels

3115 or 3120 includes one bit indicating whether a central 26 tone RU has been assigned to the user. For convenience, this indication may be carried in the first HE-SIG-B channel 3115 after the RU placement for the 484 tone RU is indicated and encoded together. If the bit is set to 1, the per user allocation information is carried at the end after the user allocation assigned to the 484 ton RU is carried.

The amount of common information varies between the examples of the multiplexing technique shown in FIGS. 29 and 31. Receivers in STAs need to know the number of bits in common information in order to prepare for decoding, so this change in common information is signaled preferentially over HE-SIG-B decoding.

The embodiments described below that illustrate exemplary scenarios have the benefit of redefining segment mapping granularity. For each scenario described below, the amount of common information in each HE-SIG-B channel is changed and signaled before HE-SIG-B decoding.

32 shows an example of a HE-SIG-B multiplexing scheme 3200 at 80 MHz when only one of the channels has a multiplexed 484 tone RU. The example of the HE-SIG-B multiplexing technique 3200 shown in FIG. 32 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 3200 may be used without departing from the scope of the present disclosure. In the embodiments shown in FIG. 32, one 484 tone RU present in the 80 MHz PPDU leads to different mapping strategies for the HE-SIG-

B channels

3215 and 3220.

33 shows an example of a HE-SIG-B multiplexing scheme 3300 when all channels represent a 40 MHz transmission. The example of the HE-SIG-B multiplexing technique 3300 shown in FIG. 33 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 3300 may be used without departing from the scope of the present disclosure. In the embodiments shown in FIG. 33, two 484 tone RUs appearing at 80 MHz derive compressed common information portion 3305 for HE-SIG-

B channels

3315 and 3320.

34 shows a HE-SIG-B multiplexing scheme 3400 when one 996 tone RU is indicated for 80 MHz. The example of the HE-SIG-B multiplexing technique 3400 shown in FIG. 34 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 3400 may be used without departing from the scope of the present disclosure. In the embodiments shown in FIG. 34, one 996 tone RU appearing in an 80 MHz PPDU is one HE carrying unique information indicating the RU placement of signaling

information portion

3410 and 996 tones per user following the RU placement indication in a common part. -Derive SIG-B channel 3415. This information can be carried in the first HE-SIG-B channel 3415 as shown in FIG. 34, replicated in the second HE-SIG-B channel 3420, and replicated in another 40 MHz (ie , HE-SIG-B fully replicated over 80 MHz). As another example, as also shown in FIG. 34, the AP 101 transmits information only on the first HE-SIG-B channel 3415 and does not transmit on the second HE-SIG-B channel 3420. Over 80 MHz, HE-SIG-B is replicated only in channels A & C, while channels B and D are empty. Only one of the two example settings may be required to be supported and implemented.

Various embodiments of the present disclosure provide multiplexing options for HE-SIG-B supporting load balancing. Applying a balanced load between the HE-SIG-B channels by applying the flexibility of mapping four segment decoding information to the HE-SIG-B channel, and performing padding on one of the channels for symbol alignment. Reducing scenarios are provided. Such scenarios are particularly needed when an asymmetric distribution of users and RUs occurs between segments A, B, C, and D. Flexibility depends on the segment size considered and the associated mapping rule.

35 shows an example of a HE-SIG-B multiplexing scheme 3500 that supports load balancing when multiple RUs are indicated. The example of the HE-SIG-B multiplexing technique 3500 shown in FIG. 35 is for illustration only. Other embodiments of the HE-SIG-B multiplexing technique 3500 may be used without departing from the scope of the present disclosure.

In the embodiments shown in FIG. 35, an example of a scenario of mapping segments to HE-SIG-B channels is supported by an indication before the STA 111 performs HE-SIG-B decoding. As shown in FIG. 35, when four 242 tone RU segments are indicated at 80 MHz, the common and per user information portions 3505 and 3510 in segments A and B are multiplexed together in the first HE-SIG-B channel 3515. And common and per user information in segments C and D are multiplexed together in a second HE-SIG-B channel 3520. Relocation of the segment mapping is supported with the mapping as described below with respect to FIG. 29. During scheduling, depending on the number of users and RU placement in each segment, the AP 101 determines an option to reduce and minimize padding overhead in the HE-SIG-B channel for symbol alignment. If one 484 tone RU is indicated at 80 MHz, the common information is multiplexed using two additional cases similar to those shown in FIG. Mapping a combination of different segments to the HE-SIG-B channel may be used. For example, channel D is mapped in the second channel HE-SIG-B channel, while channels A, B, and C are mapped to the first HE-SIG-B channel. Non-continuous channel bonding may be provided when no preambles and data are transmitted on at least one 20 MHz second channel.

The AP 101 may include a HE-SIG-B multiplexing format field that signals the multiplexing format. Two reasons may be caused or needed to indicate the multiplexing format prior to HE-SIG-B decoding. First, when larger RU sizes are used in an 80 MHz PPDU, indicating multiplexing format provides efficient signaling. For example, a scenario with 996 ton RU in the HE-SIG-B channel and at least three scenarios with 484 ton RU in all or one of the HE-SIG-B channels is provided from prior to the indication of the multiplexing technique as described above. do. Second, indicating the multiplexing format provides load balancing. For example, two scenarios with four 242 tone segments are signaled, and specific settings of the segments in the HE-SIG-B channel mapping are provided before the indication of the multiplexing format. Along with the scenarios shown in FIG. 29, eight scenarios change the multiplexing format and content in either of the HE-SIG-B channels. A total of three signaling bits are used for 80 MHz and the multiplexing format is indicated to STA 111 before HE-SIG-B decoding.

36 illustrates an HE-SIG-B multiplexing scheme 3600 using a HE-SIG-B multiplexing format field that indicates how common information is disposed in HE-SIG-B channels. The example of HE-SIG-B multiplexing techniques 3600 shown in FIG. 36 is for illustration only. Other embodiments of HE-SIG-B multiplexing techniques 3600 may be used without departing from the scope of the present disclosure.

In the embodiments shown in FIG. 36, HE-SIG-B multiplexing fields 3602 indicate how information of four segments in common information portion 3605 is mapped in two HE-SIG-B channels 3615 and 3620. The HE-SIG-B multiplexing format field 3602 is 3 bits in an 80 MHz PPDU, with a value of 3 bits indicating how segments are mapped to two HE-SIG-B channels 3615 and 3620. HE-SIG-B multiplexing format field 3602 is carried in HE-SIG-A. In general, the HE-SIG-B format field 3602 indicates how common information is placed, how load balancing is supported, if the number of users is indicated in the HE-SIG-B format field to be carried in HE-SIG-A. It is composed of N bits used to signal how balancing is supported, how there are other compressions including the lack of common information in the HE-SIG-B in the MU-MIMO PPDU over the entire bandwidths.

In some embodiments, if a 484 ton RU or larger sized RU is scheduled in an 80 MHz PPDU, the allocation information per user is divided into two HE-SIG-B channels 3615 and 3620. For example, if a 484-ton RU is scheduled in segments A and B and there are N users scheduled in the MU-PPDU, then each HE-SIG-B channel will have an assignment field per user.

Can contain as many as dogs. Where from 1 to

User allocation information is carried in the first HE-SIG-B channel,

+1 to

User assignments are carried in a second HE-SIG-B channel. If a 484 tone RU is scheduled in segments B and C, and there are N users scheduled in the MU-PPDU, then each HE-SIG-B channel is

It can contain as many user-assigned fields. Where from 1 to

User allocation information is carried in the second HE-SIG-B,

+1 to

User assignments are carried in the first HE-SIG-B channel. If the per user allocation field is distributed across the HE-SIG-B channels, the user allocation information for RU placement indicated in the common field of the HE-SIG-B channel is the per user allocation information distributed from the other channels that follow. It is transported first.

In general, for larger size RUs in which multiple HE-SIG-B channels are distributed, the per-user allocation information for users scheduled in the RU is fairly split in the HE-SIG-B channels. For M HE-SIG-B channels and N users,

The two users are carried in every HE-SIG-B, with the RU allocation distributed with any remaining users carried in the last channel.

37 shows an example of a channel structure and a replication scheme for multiplexing control information in the HE-SIG-B at 160 MHz. The example of the HE channel structure and replication scheme 3700 shown in FIG. 37 is for illustration only. Other embodiments of the channel structure and replication scheme 3700 may be used without departing from the scope of this disclosure.

Various embodiments of the present disclosure provide extended multiplexing that supports 160 MHz bandwidth allocation. In the embodiments shown in FIG. 37, eight 20 MHz segments are mapped to HE-SIG-

B channels

3715 and 3720 replicated per 40 MHz in an MU PPDU distributed at 160 MHz. The 160 MHz tone plan consists of two connected 80 MHz tone plans that are not aligned into 20 MHz segments. The redefinition channels A1, B1, C1, D1, A2, B2, C2, and D, which are the segments of FIG. 36, represent the granularity of subcarriers corresponding to 242 tone RUs, the same interval as the 242 tone RUs. Signaling the RU placement for a small sized RU distributed at The common information portion 3705 in the first HE-SIG-B channel 3715 is segments A1, C1 indicating RU placement up to the number of users (if necessary) as well as MU-MIMO resources and granularity of 242 ton RUs in the segments. Common information for, A2, and C2. Common information portion 3705 for segments A1, C1, A2, and C2 is encoded together using a convolutional code. The per-user allocation information portion 3710 is located after the common portion. Here, the per-user allocation information indicated in the RUs of segment A1 is transmitted before the per-user allocation information indicated in the RUs of A2, C1, and C2. The number of allocations per user is derived from common information in each segment, and the total number of allocations per user is the sum of the allocations derived from placement in each segment.

In the second HE-SIG-B channel 3720, the common information portion is segments B1, D1, B2 indicating the number of users (if necessary) as well as the RU placement up to the granularity of 242 ton RU in the MU-MIMO resources and segments. , And common information in D2. The common information portion 3705 in all of the segments B1, D1, B2, D2 is encoded together using a convolutional code. The allocation information 3710 per user is located after the common part. The per user information for the users indicated by the RUs in segment B1 is transmitted before the per user information for the users indicated by the RUs in segments D1, B2, and D2. The number of allocations per user is derived from common information in each segment, and the total number of allocations per user is the sum of the allocations derived from allocations in each segment.

Two 26 tone RUs are independently signaled using 1 bit. For convenience, some of the channels are referred to as a first HE-SIG-B channel 3175 and some others are referred to as a second HE-SIG-B channel 3720. The common information portion 3705 in the HE-SIG-

B channels

3715 and 3720 also includes one bit indicated if a central 26 tone RU is assigned to the user. For convenience, this indication may be carried in the first HE-SIG-B channel after the RU placements for the segments are indicated and encoded together. If the bit is set to 1, the per-user allocation information is carried at the end after the user allocation for the other segments has been carried.

Embodiments of the present disclosure derive efficiencies similar to those mentioned above for 80 MHz bandwidth allocation for RUs larger than 242 tone RU. An efficient approach is to configure the mapping granularity, which is tuned to the RU size that is signaled and flexible, to maintain distinct information in the two HE-SIG-B channels. In an embodiment of the present disclosure, information on larger RU sizes is carried by signaling mapping granularity per HE-SIG-B and is based on the RU size used in the MU-PPDU. The redefined segment definition is carried before HE-SIG-B decoding. Depending on the given bandwidth size, there are a large number of multiplexing formats that provide the size. For example, as shown in Table 5 below, 25 different cases have a multiplexing format in which they are signaled. Five signaling bits are used by AP 101 to indicate all multiplexing formats in the HE-SIG-B multiplexing format field in the HE-SIG-A at 160 MHz.

Table 5: When 160 MHz Bandwidth Is Ordered When Common Information Changes in HE-SIG-B

In some embodiments of the present disclosure, the HE-SIG-B multiplexing format field is of a fixed size regardless of the bandwidth of the MU-PPDU and is signaled in the HE-SIG-A. In some embodiments of the present disclosure, the HE-SIG-B multiplexing technique is derived by the STA 111 by blind decoding the common information section under different size assumptions. The common information section for each section may have an N size. The STA 111 attempts a decoding code block corresponding to each size and uses only information that passes the CRC.

38 shows an example of RU nulling for non-continuous channel bonding. 39 shows an example of RU nulling when an internal channel is nulled using non-continuous channel bonding. 40 shows an example of RU nulling when two channels are nulled. The examples of

RU nulling

3800, 3900, and 4000 shown in FIGS. 38 to 40, respectively, are for illustrative purposes only. Other examples of the RU nullings may be used without departing from the scope of the present disclosure.

In the embodiments of FIGS. 38-40, when non-continuous channel bonding is indicated in a request to transmit (RTS) / clear to transmit (CTS) transaction or HE-SIG-A, Edge RUs carry no information and no per STA information fields can be carried in the RUs. Although the RU placement indicates the use or presence of RU \, the presence of information fields per STA is determined based on whether the non-contiguous channel bonding field is set to indicate specific unused channels. For example, if one SEC (secondary) channel is not used, the primary (primary) channel adjacent to the SEC channel will not use the edge RU as shown in FIG. Depending on the deployment, 26 ton RUs may be unused at the edge and 52 ton edge RUs may be nulled. For different channels to be nulled, common information including RU placement may not be carried. For channels carrying data, common control and per user signaling fields are mapped to respective HE-SIG-B channels per mapping rules. Different types of channel bonding may be supported as shown in FIGS. 38-40.

41 shows an example of a process for the STA 111 to interpret RU placement when non-continuous channel bonding is used. For example, process 4100 may be performed by the STA 111 based on signaling from the AP 101. The example of the process 4100 shown in FIG. 41 is for illustration only. Other embodiments of the process 4100 may be used without departing from the scope of this disclosure.

In the embodiment shown in FIG. 41, according to the nulling indicated in HE-SIG-A, the RU placement for the channels carrying data indicates where the data is carried and indicates the edge RUs that are required to be ignored. do. The process is initiated by the STA 111 determining whether a non-continuous channel bonding field is set to indicate null channels (step 4105). For example, in step 4105, the STA 111 In the packet header such as the packet header 300 of FIG. 3, a non-continuous channel bonding field may be identified from the HE-SIG-A field.

If the STA 111 is configured for a non-continuous channel bonding field to indicate nulling channels, the STA 111 interprets the RU placement in the common information portion having null RUs adjacent to the nulled channels, and the RU placement and channel bonding field. The number of fields per STA is determined based on the step 4110. For example, in step 4110, the STA 111 may interpret null RUs as shown in FIGS. 38 to 40.

However, if the STA 111 does not have a non-continuous channel bonding field set to indicate null channels, the STA 111 controls the RU placement as indicated in the HE-SIG-B. For example, in step 4115, the STA 111 processes the information in the HE-SIG-B as described above without null channels.

Methods according to the embodiments described in the claims or the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in a computer readable storage medium are configured for execution by one or more processors in an electronic device. One or more programs include instructions that cause an electronic device to execute methods in accordance with embodiments described in the claims or specifications of this disclosure.

Such programs (software modules, software) may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms It can be stored in an optical storage device, a magnetic cassette. Or, it may be stored in a memory composed of some or all of these combinations. In addition, each configuration memory may be included in plural.

In addition, the program may be configured through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable storage device that is accessible. Such a storage device may be connected to a device that performs an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device that performs an embodiment of the present disclosure.

In the above-described specific embodiments of the present disclosure, the components included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expressions are selected to suit the circumstances presented for convenience of description, and the present disclosure is not limited to the singular or plural elements, and the singular or plural elements may be used in the singular or the singular. Even expressed components may be composed of a plurality.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described. However, various modifications may be possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

Claims

Apparatus of an access point (AP) in a wireless local area network (WLAN),

A control unit configured to generate a high efficiency physical layer convergence protocol (PLCP) protocol data unit (HE PPDU) including a high efficiency signal A (HE-SIG-A) field;

At least one transceiver configured to transmit the generated HE PPDU to a station (STA),

The HE PPDU is,

If the format of the HE PPDU is an HE MU PPDU used for multiple user (MU) transmission that does not respond to a trigger frame, a HE-SIG-B field (HE-SIG-B) Device further comprising.
The method according to claim 1, wherein the HE PPDU,

And if the format of the HE PPDU is a HE extended range SU PPDU used for single user (SU) transmission, the apparatus includes the repeated HE-SIG-A field.
The method according to claim 1, wherein the HE PPDU,

Carry at least one of a 26-subcarrier resource unit (RU), a 52-subcarrier RU, a 106-subcarrier RU, a 242-subcarrier RU, and a 484-subcarrier RU according to a format of the HE PPDU,

The 26-subcarrier resource unit (RU), 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU,

Device carried in a predefined position.
The method according to claim 1, wherein the HE-SIG-A field,

Carries information required to interpret the HE PPDU,

And a field indicating a bandwidth of the HE PPDU.
The method according to claim 4, wherein when the format of the HE PPDU is HE MU PPDU, the HE-SIG-A field,

A field indicating the MCS of the HE-SIG-B, a field indicating whether the HE-SIG-B has been modulated by dual sub-carrier modulation, and a symbol of the HE-SIG-B The apparatus further comprises a field indicating the number of.
The method according to claim 1, wherein the HE-SIG-B field,

Including common block fields and user specific fields,

The common block field is

A subfield including information indicating resource unit placement in a frequency domain, and information indicating the number of user fields included in the user specific field;

Each of the user fields included in the user specific field is

And information for the two STAs to decode the payload of the two STAs.
Apparatus of a station (STA) in a wireless local area network (WLAN),

At least one transceiver configured to receive a high efficiency physical layer convergence protocol (PLCP) protocol data unit (HE PPDU) including a high efficiency signal A (HE-SIG-A) field from an access point (AP),

The received HE PPDU is,

When the format of the received HE PPDU is an HE MU PPDU used for multiple user (MU) transmission that does not respond to a trigger frame, HE-SIG-B (high efficiency signal B). ) Further comprising a field.
The method of claim 7, wherein the received HE PPDU,

And if the format of the received HE PPDU is a HE extended range S PPDU used for single user (SU) transmission, the apparatus includes the repeated HE-SIG-A field.
The method according to claim 7, wherein the received PPDU,

According to the format of the HE PPDU, carry at least one of 26-subcarrier resource unit (RU), 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU,

The 26-subcarrier resource unit (RU), 52-subcarrier RU, 106-subcarrier RU, 242-subcarrier RU, and 484-subcarrier RU,

Device carried in a predefined position.
The method according to claim 7, wherein the HE-SIG-A field,

Carries information required to interpret the HE PPDU,

And a field indicating a bandwidth of the HE PPDU.
The method according to claim 10, wherein if the format of the received HE PPDU is HE MU PPDU, the HE-SIG-A field,

A field indicating the MCS of the HE-SIG-B, a field indicating whether the HE-SIG-B has been modulated by dual sub-carrier modulation, and a symbol of the HE-SIG-B The apparatus further comprises a field indicating the number of.
The method according to claim 7, wherein the HE-SIG-B field,

Including common block fields and user specific fields,

The common block field is

A subfield including information indicating a resource unit arrangement in a frequency domain, information indicating a number of user fields included in the user specific field,

Each of the user fields included in the user specific field is

And information for the two STAs to decode the payload of the two STAs.
A method of an access point (AP) implemented with an apparatus of any one of claims 1 to 6.
A method of a station (STA) implemented with an apparatus of any one of claims 7 to 12.