Link setup for multi-link operation

Abstract

To provide a link setup method for a multi-link operation.SOLUTION: In a wireless local area network (LAN) system, an STA of a multi-link device (MLD) transmits MAC addresses of other STAs included in the same MLD as the STA in a link setup step.SELECTED DRAWING: Figure 40

Description

[Technical field]

[0001] This specification relates to a link setup method for multi-link operation in a wireless local area network (WLAN) system. [Background technology]

[0002] WLANs (wireless local area networks) have been improved in various ways, for example, the IEEE 802.11ax standard proposed an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multi-user multiple input, multiple output (DL MU MIMO) techniques.

[0003] This specification proposes technical features that can be utilized in a new communication standard. For example, the new communication standard may be the Extreme High Throughput (EHT) standard that has been recently under discussion. The EHT standard may use newly proposed increased bandwidth, improved PHY layer protocol data unit (PPDU) structure, improved sequences, Hybrid automatic repeat request (HARQ) techniques, etc. The EHT standard may be referred to as the IEEE 802.11be standard. Summary of the Invention [Means for solving the problem]

[0004] In a wireless local area network (WLAN) system according to various embodiments, a method performed by a transmitting device includes technical features related to a link setup method for multi-link operation. In the method performed in a receiving multi-link device (MLD) of a wireless local area network (WLAN) system, the receiving MLD includes a first and a second station (STA), the first STA operates on a first link, and the second STA operates on a second link. The first STA receives multi-link information including information related to the first and second links from a transmitting MLD. The first STA transmits multi-link address information to the transmitting MLD. The multi-link address information includes a media access control (MAC) address of the second STA. Effect of the Invention

[0005] According to an example of the present specification, after multi-link setup, related information can be transmitted so that signals can be transmitted between the set up links. In the multi-link setup step, capability information between the links is exchanged, and information on which link is to be used for the multi-link operation is exchanged, but a method for starting signal transmission and reception on the link performing the multi-link operation is not specified.

[0006] According to one example of this specification, a STA performing a multi-link setup can transmit MAC address information of other STAs performing multi-link operations among those included in the same MLD as itself, so that the other party can exchange signals with the corresponding STA.

[0007] According to one example of the present specification, a STA that does not perform multilink setup can directly transmit an initial frame, which can indicate that it is a STA of an MLD that has performed multilink setup by including an MLD MAC address. [Brief description of the drawings]

[0008] [Figure 1] 1 illustrates an example of a transmitting device and / or a receiving device according to the present specification. [Diagram 2] 1 is a conceptual diagram showing the structure of a wireless RAN (WLAN). [Diagram 3] FIG. 2 is a diagram illustrating a general link setup process. [Figure 4] FIG. 1 is a diagram showing an example of a PPDU used in the IEEE standard. [Diagram 5] A diagram showing the arrangement of resource units RU used on a 20 MHz band. [Figure 6] A diagram showing the arrangement of resource units RU used on a 40 MHz band. [Figure 7] A diagram showing the arrangement of resource units RU used on the 80 MHz band. [Figure 8] The structure of the HE-SIG-B field is shown below. [Figure 9] An example is shown in which multiple user STAs are assigned to the same RU using the MU-MIMO technique. [Figure 10] Shows operation with UL-MU. [Figure 11] 1 shows an example of a trigger frame. [Figure 12] 1 shows an example of a common information field of a trigger frame. [Figure 13] 1 shows an example of subfields included in a per user information field. [Figure 14] The technical features of the UORA technique are explained. [Figure 15] An example of channels used / supported / defined within the 2.4 GHz band is shown below. [Figure 16] 1 illustrates an example of channels used / supported / defined within the 5 GHz band. [Figure 17] Illustrates an example of channels used / supported / defined within the 6 GHz band. [Figure 18] 1 shows an example of a PPDU used in this specification. [Figure 19] 1 shows a modified example of the transmitting device and / or the receiving device of the present specification. [Figure 20] FIG. 1 is a diagram illustrating an example of channel bonding. [Figure 21] FIG. 1 illustrates an embodiment of a device that supports multilink. [Figure 22] FIG. 1 illustrates an embodiment of a multi-link STR capability. [Diagram 23] FIG. 11 is a diagram showing an example of link information. [Figure 24] FIG. 11 is a diagram showing an example of link information. [Diagram 25] 1 is an example of a Multi-link setup for the basic process (A). [Figure 26] A figure showing one embodiment of an MLD Per-STA MAC address field. [Figure 27] A figure showing one embodiment of an MLD Per-STA MAC address element. [Figure 28] FIG. 1 is a diagram illustrating an embodiment of a Multi-link Element. [Figure 29] FIG. 13 is a diagram showing one embodiment of an ML IE. [Diagram 30] FIG. 13 is a diagram showing one embodiment of an ML IE. [Diagram 31] FIG. 1 is a diagram illustrating an embodiment of a method for transmitting an initial frame in a non-association link. [Diagram 32]FIG. 1 is a diagram showing an embodiment of A-1. [Diagram 33] FIG. 13 is a diagram showing an example of A-3. [Diagram 34] FIG. 13 is a diagram showing an example of the A-4 case of the B-1 method. [Diagram 35] FIG. 1 illustrates an embodiment of a multi-link setup method. [Diagram 36] FIG. 1 illustrates an example of operations related to link capabilities. [Figure 37] FIG. 1 illustrates an embodiment of a link negotiation method. [Figure 38] FIG. 1 illustrates an embodiment of a link negotiation method. [Figure 39] FIG. 1 illustrates an embodiment of a link negotiation method. [Diagram 40] FIG. 11 is a diagram illustrating an embodiment of a receiving MLD operation. [Diagram 41] FIG. 11 is a diagram illustrating an example of a transmission MLD operation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] As used herein, "A or B" can mean "A only," "B only," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "A only," "B only," "C only," or "any combination of A, B and C."

[0010] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "A only," "B only," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0011] In this specification, "at least one of A and B" can mean "A only," "B only," or "both A and B." In addition, in this specification, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted similarly to "at least one of A and B."

[0012] In addition, in this specification, "at least one of A, B and C" can mean "A only," "B only," "C only," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" and "at least one of A, B and / or C" can mean "at least one of A, B and C."

[0013] Furthermore, parentheses used in this specification may mean "for example." Specifically, when "control information (EHT-Signal)" is displayed, "EHT-Signal" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "EHT-Signal," and "EHT-Signal" may be proposed as an example of "control information." Furthermore, when "control information (i.e., EHT-signal)" is displayed, "EHT-signal" may be proposed as an example of "control information."

[0014] Technical features described individually in one drawing in this specification can be realized individually or simultaneously.

[0015] The following example of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a / g / n / ac standard or the IEEE 802.11ax standard. The present specification may also be applied to the newly proposed EHT standard or the IEEE 802.11be standard. The present specification may also be applied to a new wireless RAN standard that enhances the EHT standard or the IEEE 802.11be. The present specification may also be applied to a mobile communication system. For example, the present specification may be applied to a mobile communication system based on LTE (Long Term Evolution) based on the 3GPP (3rd Generation Partnership Project) standard and its evolution. The present specification may also be applied to a 5G NR standard communication system based on the 3GPP standard.

[0016] In order to explain the technical features of the present specification, technical features to which the present specification can be applied will be explained below.

[0017] FIG. 1 shows an example of a transmitting device and / or a receiving device according to the present specification.

[0018] The example of FIG. 1 can perform various technical features described below. FIG. 1 is related to at least one STA (station). For example, the STA (110, 120) in this specification can be called various names such as a mobile terminal, a wireless device, a wireless transmit / receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STA (110, 120) in this specification can be called various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) in this specification can be called various names such as a receiving device, a transmitting device, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

[0019] For example, the STAs (110, 120) can act as an Access Point (AP) or a non-AP. That is, the STAs (110, 120) in this specification can perform the functions of an AP and / or a non-AP. In this specification, an AP can also be referred to as an AP STA.

[0020] The STAs (110, 120) of the present specification may support various communication standards other than the IEEE 802.11 standard. For example, communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard) may be supported. The STAs of the present specification may be realized in various devices such as a mobile phone, a vehicle, a personal computer, etc. The STAs of the present specification may support communication for various communication services such as voice communication, video communication, data communication, self-driving, autonomous driving, etc.

[0021] As used herein, the STAs (110, 120) may include a medium access control (MAC) and physical layer interface to the wireless medium in accordance with the provisions of the IEEE 802.11 standard.

[0022] The STAs (110, 120) will be described below based on the sub-diagram (a) of FIG.

[0023] The first STA (110) may include a processor 111, a memory 112, and a transceiver 113. The illustrated processor, memory, and transceiver may each be implemented on a separate chip, or at least two or more of the above blocks / functions may be implemented via one chip.

[0024] The transceiver 113 of the first STA performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (for example, IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0025] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor 111 of the AP can receive signals via the transceiver 113, process the received signals, generate transmission signals, and perform control for signal transmission. The memory 112 of the AP can store signals received via the transceiver 113 (i.e., received signals) and can store signals transmitted via the transceiver (i.e., transmitted signals).

[0026] For example, the second STA (120) can perform the intended operation of a non-AP STA. For example, the non-AP transceiver 123 can transmit and receive signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0027] For example, the processor 121 of the Non-AP STA can receive signals via the transceiver 123, process the received signals, generate transmission signals, and perform control for signal transmission. The memory 122 of the Non-AP STA can store signals received via the transceiver 123 (i.e., received signals) and can store signals transmitted via the transceiver (i.e., transmitted signals).

[0028] For example, in the following specification, the operation of the device indicated by the AP may be performed by the first STA (110) or the second STA (120). For example, when the first STA (110) is an AP, the operation of the device indicated by the AP may be controlled by the processor 111 of the first STA (110), and related signals may be transmitted or received via the transceiver 113 controlled by the processor 111 of the first STA (110). Also, control information related to the operation of the AP and the transmission / reception signals of the AP may be stored in the memory 112 of the first STA (110). Also, when the second STA (110) is an AP, the operation of the device indicated by the AP may be controlled by the processor 121 of the second STA (120), and related signals may be transmitted or received via the transceiver 123 controlled by the processor 121 of the second STA (120). In addition, control information related to the operation of the AP and the AP's transmission / reception signals can be stored in the memory 122 of the second STA (110).

[0029] For example, the operation of the device indicated as non-AP (or User-STA) in the following specification may be performed by the first STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device indicated as non-AP may be controlled by the processor 121 of the second STA (120), and related signals may be transmitted or received via the transceiver 123 controlled by the processor 121 of the second STA (120). In addition, control information related to the operation of the non-AP and transmission / reception signals of the AP may be stored in the memory 122 of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of the device indicated as non-AP may be controlled by the processor 111 of the first STA (110), and related signals may be transmitted or received via the transceiver 113 controlled by the processor 111 of the first STA (120). In addition, control information related to the operation of the non-AP and the AP's transmission / reception signals can be stored in the memory 112 of the first STA (110).

[0030] In the following specification, devices referred to as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STAs (110, 120) in FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific reference numerals may also refer to the STAs (110, 120) in FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceivers 113, 123 in FIG. 1. In addition, in the following example, various STAs may generate transmission / reception signals or perform data processing or calculations in advance for transmission / reception signals in the processors 111 and 121 of Fig. 1. For example, an example of an operation of generating transmission / reception signals or performing data processing or calculations in advance for transmission / reception signals may include: 1) an operation of determining / obtaining / configuring / calculating / decoding / encoding bit information of subfields (SIG, STF, LTF, Data) included in a PPDU; 2) an operation of determining / configuring / obtaining time resources and frequency resources (e.g., subcarrier resources) used for the subfields (SIG, STF, LTF, Data) included in a PPDU; 3) an operation of determining / configuring / obtaining a specific sequence (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for the subfields (SIG, STF, LTF, Data) included in a PPDU; 4) an operation of power control and / or power saving applied to the STA; and 5) an operation related to determining / obtaining / configuring / calculating / decoding / encoding an ACK signal.In addition, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs in the following example to determine / acquire / configure / calculate / decode / encode transmitted / received signals may be stored in memories 112, 122 of FIG. 1.

[0031] The above-mentioned device / STA of sub-figure (a) of Fig. 1 can be modified as shown in sub-figure (b) of Fig. 1. Hereinafter, the STA (110, 120) of this specification will be described based on sub-figure (b) of Fig. 1.

[0032] For example, the transceivers 113, 123 shown in sub-drawing (b) of Figure 1 can perform the same functions as the transceivers shown in sub-drawing (a) of Figure 1 described above. For example, the processing chips 114, 124 shown in sub-drawing (b) of Figure 1 can include processors 111, 121 and memories 112, 122. The processors 111, 121 and memories 112, 122 shown in sub-drawing (b) of Figure 1 can perform the same functions as the processors 111, 121 and memories 112, 122 shown in sub-drawing (a) of Figure 1 described above.

[0033] In the following description, a mobile terminal, a wireless device, a wireless transmit / receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving device, a transmitting device, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and / or a transmitting apparatus may refer to the STA (110, 120) shown in the sub-drawing (a) / (b) of Fig. 1, or may refer to the processing chips 114, 124 shown in the sub-drawing (b) of Fig. 1. That is, the technical features of the present specification may be performed by the STA (110, 120) shown in the sub-drawing (a) / (b) of Fig. 1, or may be performed only by the processing chips 114, 124 shown in the sub-drawing (b) of Fig. 1. For example, the technical feature of the transmitting STA transmitting a control signal can be understood as a technical feature in which a control signal generated by the processor 111, 121 shown in sub-drawing (a) / (b) of Fig. 1 is transmitted via the transceiver 113, 123 shown in sub-drawing (a) / (b) of Fig. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal can be understood as a technical feature in which a control signal transmitted to the transceiver 113, 123 is generated by the processing chip 114, 124 shown in sub-drawing (b) of Fig. 1.

[0034] For example, the technical feature of the receiving STA receiving the control signal can be understood as the technical feature of the control signal being received by the transceivers 113 and 123 shown in sub-drawing (a) of Fig. 1. Or, the technical feature of the receiving STA receiving the control signal can be understood as the technical feature of the control signal received by the transceivers 113 and 123 shown in sub-drawing (a) of Fig. 1 being acquired by the processors 111 and 121 shown in sub-drawing (a) of Fig. 1. Or, the technical feature of the receiving STA receiving the control signal can be understood as the technical feature of the control signal received by the transceivers 113 and 123 shown in sub-drawing (b) of Fig. 1 being acquired by the processing chips 114 and 124 shown in sub-drawing (b) of Fig. 1.

[0035] 1, software code 115, 125 may be provided within memory 112, 122. The software code 115, 125 may include instructions that control the operation of the processor 111, 121. The software code 115, 125 may be included in a variety of programming languages.

[0036] The processor 111, 121 or the processing chip 114, 124 shown in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, the processor 111, 121 or the processing chip 114, 124 shown in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processors 111, 121 or processing chips 114, 124 shown in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOS™ series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or an enhanced processor thereof.

[0037] In this specification, the uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted via the uplink. Also, in this specification, the downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted via the downlink.

[0038] FIG. 2 is a conceptual diagram showing the structure of a wireless RAN (WLAN).

[0039] The top part of Figure 2 shows the structure of an IEEE (Institute of electrical and electronic engineers) 802.11 infrastructure basic service set (BSS).

[0040] Referring to the top of FIG. 2, the wireless RAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP, 225) and a station (STA1, 200-1), that can successfully synchronize and communicate with each other, and are not a concept that refers to a specific area. The BSS (205) may also include one AP (230) and one or more STAs (205-1, 205-2) that can be joined.

[0041] The BSS may include at least one STA, APs (225, 230) that provide a distribution service, and a distribution system (DS, 210) that connects a plurality of APs.

[0042] The distributed system 210 can realize an extended service set (ESS, 240) by connecting several BSSs (200, 205). The ESS (240) can be used as a term indicating a network formed by connecting one or more APs via the distributed system 210. The APs included in one ESS (240) can have the same service set identification (SSID).

[0043] The portal (220) can act as a bridge between the wireless RAN network (IEEE 802.11) and other networks (e.g., 802.X).

[0044] In the BSS shown at the top of FIG. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be realized. However, it may be possible to set up a network between STAs without APs (225, 230) and communicate with each other. A network in which a network is set up between STAs without APs (225, 230) and communicates with each other is defined as an Ad-Hoc network or an independent basic service set (IBSS).

[0045] The bottom part of FIG. 2 is a conceptual diagram showing the IBSS.

[0046] Referring to the bottom of FIG. 2, an IBSS is a BSS that operates in an ad-hoc mode. Since an IBSS does not include an AP, there is no centralized management entity that performs management functions. That is, in an IBSS, STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In an IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) may be mobile STAs, and connection to a distributed system is not permitted, forming a self-contained network.

[0047] FIG. 3 is a diagram illustrating a general link setup process.

[0048] In the illustrated step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access a network, it must search for a network that it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks that exist in a specific area is called scanning. There are two scanning methods: active scanning and passive scanning.

[0049] FIG. 3 illustrates a network discovery operation including an active scanning process as an example. An STA performing active scanning transmits a probe request frame to search for APs in the vicinity while changing channels, and waits for a response to the probe request frame. A responder transmits a probe response frame to the STA that transmitted the probe request frame as a response to the probe request frame. Here, the responder can be the STA that transmitted a signal frame (beacon frame) last in the BSS of the channel being scanned. In the BSS, the AP transmits a signal frame, so the AP becomes the responder, and in the IBSS, the STAs in the IBSS transmit signal frames in order, so the responder is not fixed. For example, a STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame, move to the next channel (e.g., channel 2) and perform scanning in the same manner (i.e., probe request / response transmission / reception on channel 2).

[0050] Although not shown in the example of FIG. 3, the scanning operation may be performed in a passive scanning manner. A STA performing scanning based on passive scanning may wait for a signal frame while changing channels. A signal frame is one of management frames in IEEE 802.11, and is periodically transmitted to notify the existence of a wireless network and to allow a scanning STA to search for and join a wireless network. In a BSS, an AP plays a role of periodically transmitting a signal frame, and in an IBSS, STAs in the IBSS transmit signal frames in turn. When a scanning STA receives a signal frame, it stores information about the BSS included in the signal frame, and moves to another channel while recording signal frame information in each channel. A STA receiving a signal frame may store BSS-related information included in the received signal frame, move to the next channel, and perform scanning in the next channel in the same manner.

[0051] The STA that has discovered the network can perform an authentication process through step S320. This authentication process can be called a first authentication process to clearly distinguish it from the security setup operation in step S340 described below. The authentication process in S320 can include a process in which the STA transmits an authentication request frame to the AP, and in response, the AP transmits an authentication response frame to the STA. The authentication frame used in the authentication request / response corresponds to a management frame.

[0052] The authentication frame may include information regarding an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), a Finite Cyclic Group, and the like.

[0053] The STA can send an authentication request frame to the AP. The AP can determine whether to allow authentication for the STA based on information included in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

[0054] The successfully authenticated STA can perform an association process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA. For example, the association request frame can include information related to various capabilities, such as a signal listen interval, a service set identifier (SSID), supported rates, supported channels, an RSN, a mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may include information related to various capabilities, a status code, an association ID (AID), supported rates, an Enhanced Distributed Channel Access (EDCA) parameter set, a Received Channel Power Indicator (RCPI), a Received Signal to Noise Indicator (RSNI), a mobility domain, a timeout interval (association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a QoS map, and the like.

[0055] Thereafter, in step S340, the STA may perform a security setup process. The security setup process in step S340 may include, for example, a private key setup process via 4-way handshaking via an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0056] FIG. 4 is a diagram showing an example of a PPDU used in the IEEE standard.

[0057] As shown in the figure, various types of PPDUs (PHY protocol data units) are used in standards such as IEEE a / g / n / ac. Specifically, the LTF and STF fields contain training signals, SIG-A and SIG-B contain control information for a receiving station, and the data field contains user data corresponding to the PSDU (MAC PDU / Aggregated MAC PDU).

[0058] Also, Figure 4 includes an example of an HE PPDU of the IEEE 802.11ax standard. The HE PPDU of Figure 4 is an example of a PPDU for multiple users, and HE-SIG-B is included only for multiple users, and the HE-SIG-B can be omitted in a PPDU for a single user.

[0059] As shown in the figure, the HE-PPDU for multiple users (MUs) may include a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A (HE-SIG-A), a high efficiency-signal-B (HE-SIG-B), a high efficiency-short training field (HE-STF), a high efficiency-long training field (HE-LTF), a data field (or MAC payload), and a Packet Extension (PE) field. Each field may be transmitted during the time interval shown in the figure (i.e., 4 or 8 μs, etc.).

[0060] The resource unit RU used in the PPDU will be described below. The resource unit may include multiple subcarriers (or tones). The resource unit may be used when transmitting signals to multiple STAs based on the OFDMA technique. The resource unit may also be defined when transmitting a signal to one STA. The resource unit may be used for STF, LTF, data field, etc.

[0061] FIG. 5 is a diagram showing the arrangement of resource units RU used on a 20 MHz band.

[0062] As shown in Fig. 5, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to configure some fields of the HE-PPDU. For example, resources may be allocated to the HE-STF, HE-LTF, and data fields in the illustrated RU units.

[0063] As shown at the top of FIG. 5, 26-units (i.e., units corresponding to 26 tones) may be arranged. In the leftmost band of the 20 MHz band, 6 tones may be used as a guard band, and in the rightmost band of the 20 MHz band, 5 tones may be used as a guard band. In addition, 7 DC tones may be inserted in the center band, i.e., the DC band, and 26-units corresponding to 13 tones may exist on each of the left and right sides of the DC band. In addition, 26-units, 52-units, and 106-units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

[0064] On the other hand, the RU arrangement of Figure 5 can be utilized not only in a situation for multiple users MU but also in a situation for a single user SU, in which case, as shown at the bottom of Figure 5, one 242-unit can be used, in which case three DC tones can be inserted.

[0065] In the example of Figure 5, various sizes of RUs are proposed, i.e., 26-RU, 52-RU, 106-RU, 242-RU, etc., but the specific sizes of such RUs can be expanded or increased, so this embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones).

[0066] FIG. 6 is a diagram showing the arrangement of resource units RU used on a 40 MHz band.

[0067] Just as various sizes of RUs are used in the example of Fig. 5, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. may be used in the example of Fig. 6. In addition, 5 DC tones may be inserted into the center frequency, 12 tones may be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 40 MHz band.

[0068] Also, as shown in the figure, when used for a single user, 484-RU may be used, while the specific number of RUs may be changed, as in the example of FIG.

[0069] FIG. 7 is a diagram showing the arrangement of resource units RU used on the 80 MHz band.

[0070] As various sizes of RUs are used in the examples of Figures 5 and 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may be used in the example of Figure 7. Seven DC tones may be inserted into the center frequency, 12 tones may be used as a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 80 MHz band. Also, 26-RU using 13 tones on each side of the DC band may be used.

[0071] Also, as shown, if used for a single user, 996-RU may be used, in which case five DC tones may be inserted.

[0072] The RU described in this specification can be used for UL (Uplink) communication and DL (Downlink) communication. For example, when UL-MU communication solicited by a Trigger frame is performed, a transmitting STA (e.g., AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA through the Trigger frame. Then, the first STA can transmit a first Trigger-based PPDU based on the first RU, and the second STA can transmit a second Trigger-based PPDU based on the second RU. The first and second Trigger-based PPDUs are transmitted to the AP in the same time period.

[0073] For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA. That is, the transmitting STA (e.g., AP) can transmit the HE-STF, HE-LTF, and Data fields for the first STA via the first RU and the HE-STF, HE-LTF, and Data fields for the second STA via the second RU in one MU PPDU.

[0074] Information regarding the location of the RU can be signaled via HE-SIG-B.

[0075] FIG. 8 shows the structure of the HE-SIG-B field.

[0076] As shown, the HE-SIG-B field 810 includes a common field 820 and a user-specific field 830. The common field 820 may include information that is commonly applied to all users (i.e., user STAs) that receive the SIG-B. The user-specific field 830 may be referred to as a user-specific control field. When the SIG-B is transmitted to multiple users, the user-specific field 830 may be applied to only some of the multiple users.

[0077] As shown in FIG. 8, the common field 820 and the user-specific field 830 can be encoded separately.

[0078] The common field 820 may include N*8 bits of RU allocation information. For example, the RU allocation information may include information regarding the location of the RU. For example, as shown in FIG. 5, when a 20 MHz channel is used, the RU allocation information may include information regarding which RU (26-RU / 52-RU / 106-RU) is located in which frequency band.

[0079] An example of the RU allocation information consisting of 8 bits is as follows:

[0080] [Table 1]

[0081] As shown in the example of FIG. 5, a maximum of nine 26-RUs may be allocated to a 20 MHz channel. When the RU allocation information of the common field 820 is set to "00000000", as shown in Table 1, nine 26-RUs may be allocated to the corresponding channel (i.e., 20 MHz). Also, when the RU allocation information of the common field 820 is set to "00000001", as shown in Table 1, seven 26-RUs and one 52-RU are arranged in the corresponding channel. That is, in the example of FIG. 5, a 52-RU may be allocated to the rightmost side, and seven 26-RUs may be allocated to the left of that.

[0082] The example in Table 1 shows only a portion of the RU locations that can be displayed in the RU allocation information.

[0083] For example, the RU allocation information may include an example of Table 2 below.

[0084] [Table 2]

[0085] "01000y2y1y0" refers to an example in which a 106-RU is assigned to the leftmost side of a 20 MHz channel, and five 26-RUs are assigned to the right of the 106-RU. In this case, a plurality of STAs (e.g., User-STAs) can be assigned to the 106-RU based on the MU-MIMO technique. Specifically, a maximum of eight STAs (e.g., User-STAs) can be assigned to the 106-RU, and the number of STAs (e.g., User-STAs) assigned to the 106-RU is determined based on the 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., User-STAs) assigned to the 106-RU based on the MU-MIMO technique can be N+1.

[0086] Generally, multiple STAs (e.g., User STAs) that are different from each other may be assigned to multiple RUs. However, multiple STAs (e.g., User STAs) may be assigned to an RU that is a certain size (e.g., 106 subcarriers) or larger based on the MU-MIMO technique.

[0087] As shown in FIG. 8, the user-specific field 830 may include a plurality of user fields. As described above, the number of STAs (e.g., User STAs) to be allocated to a specific channel may be determined based on the RU allocation information of the common field 820. For example, when the RU allocation information of the common field 820 is "00000000", one User STA may be allocated to each of the nine 26-RUs (i.e., a total of nine User STAs may be allocated). That is, up to nine User STAs may be allocated to a specific channel by the OFDMA technique. In other words, up to nine User STAs may be allocated to a specific channel by the non-MU-MIMO technique.

[0088] For example, when RU allocation is set to "01000y2y1y0", multiple user STAs can be allocated to the 106-RU located on the far left side by the MU-MIMO technique, and five user STAs can be allocated to the five 26-RUs located to the right side by the non-MU-MIMO technique. This case is embodied by the example of FIG. 9.

[0089] FIG. 9 shows an example in which multiple user STAs are assigned to the same RU using the MU-MIMO technique.

[0090] For example, when RU allocation is set to "01000010" as shown in FIG. 9, a 106-RU may be allocated to the leftmost side of a particular channel, and five 26-RUs may be allocated to the right of the 106-RU based on Table 2. Also, a total of three user STAs may be allocated to the 106-RU by the MU-MIMO technique. As a result, since a total of eight user STAs are allocated, the user-specific field 830 of the HE-SIG-B may include eight user fields.

[0091] The eight user fields may be included in the order shown in Figure 9. Also, as shown in Figure 8, two user fields may be implemented in one user block field.

[0092] The user fields shown in Figures 8 and 9 may be configured based on two formats. That is, the user field related to the MU-MIMO technique may be configured in a first format, and the user field related to the non-MU-MIMO technique may be configured in a second format. Referring to the example of Figure 9, user fields 1 to 3 may be based on the first format, and user fields 4 to 8 may be based on the second format. The first format or the second format may include bit information of the same length (e.g., 21 bits).

[0093] Each user field may have the same size (eg, 21 bits). For example, the user field of the first format (the format of the MU-MIMO technique) may be configured as follows.

[0094] For example, the first bits (e.g., B0-B10) in the User field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of a User STA to which the User field is assigned. Also, the second bits (e.g., B11-B14) in the User field (i.e., 21 bits) may include information regarding spatial configuration. Specifically, an example of the second bits (i.e., B11-B14) may be as shown in Tables 3 to 4 below.

[0095] [Table 3]

[0096] [Table 4]

[0097] As shown in Table 3 and / or Table 4, the second bit (i.e., B11-B14) may include information regarding the number of spatial streams allocated to a plurality of user STAs allocated by the MU-MIMO technique. For example, as shown in FIG. 9, when three user STAs are allocated to 106-RU based on the MU-MIMO technique, N_user is set to "3", and the values ​​of N_STS[1], N_STS[2], and N_STS[3] may be determined as shown in Table 3. For example, when the value of the second bit (B11-B14) is "0011", N_STS[1]=4, N_STS[2]=1, and N_STS[3]=1 may be set. That is, in the example of FIG. 9, four spatial streams may be allocated to user field 1, one spatial stream may be allocated to user field 2, and one spatial stream may be allocated to user field 3.

[0098] As an example of Table 3 and / or Table 4, information on the number of spatial streams for a user station (User STA) (i.e., second bits, B11-B14) may be composed of 4 bits. Also, information on the number of spatial streams for a user station (User STA) (i.e., second bits, B11-B14) may support up to 8 spatial streams. Also, information on the number of spatial streams (i.e., second bits, B11-B14) may support up to 4 spatial streams for one User STA.

[0099] In addition, the third bit (i.e., B15-18) in the User field (i.e., 21 bits) may include MCS (Modulation and coding scheme) information. The MCS information may be applied to a data field in the PPDU in which the SIG-B is included.

[0100] As used herein, MCS, MCS information, MCS index, MCS field, etc. may be represented by a specific index value. For example, MCS information may be represented by index 0 to index 11. MCS information may include information on characteristic modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information on coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). MCS information may exclude information on channel coding type (e.g., BCC or LDPC).

[0101] Also, the fourth bit (ie, B19) in the User field (ie, 21 bits) can be a Reserved field.

[0102] In addition, the fifth bit (i.e., B20) in the User field (i.e., 21 bits) may include information on the coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) may include information on the type of channel coding (e.g., BCC or LDPC) applied to the data field in the PPDU in which the SIG-B is included.

[0103] The above example relates to the User field of the first format (format of the MU-MIMO technique). An example of the User field of the second format (format of the non-MU-MIMO technique) is as follows.

[0104] The first bit (e.g., B0-B10) in the User field of the second format may include identification information of the User STA. The second bit (e.g., B11-B13) in the User field of the second format may include information regarding the number of spatial streams applied to the RU. The third bit (e.g., B14) in the User field of the second format may include information regarding whether a beamforming steering matrix is ​​applied. The fourth bit (e.g., B15-B18) in the User field of the second format may include MCS (Modulation and coding scheme) information. The fifth bit (e.g., B19) in the User field of the second format may include information regarding whether DCM (Dual Carrier Modulation) is applied. The sixth bit (i.e., B20) in the User field of the second format may include information regarding a coding type (e.g., BCC or LDPC).

[0105] 10 shows the operation of the UL-MU. As shown in the figure, a transmitting STA (e.g., AP) can perform channel connection through contention (i.e., Backoff operation) and transmit a Trigger frame (1030). That is, the transmitting STA (e.g., AP) can transmit a PPDU including a Trigger Frame (1330). If a PPDU including a Trigger Frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

[0106] The TB PPDUs (1041, 1042) are transmitted during the same time period and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger Frame (1030). The ACK frame 1050 for the TB PPDU can be realized in various forms.

[0107] Specific features of the trigger frame will be described with reference to Figures 11 to 13. When UL-MU communication is used, the orthogonal frequency division multiple access (OFDMA) technique or the MU MIMO technique can be used, or the OFDMA and MU MIMO techniques can be used simultaneously.

[0108] Figure 11 shows an example of a trigger frame. The trigger frame in Figure 11 allocates resources for uplink MU transmission (Uplink Multiple-User transmission) and can be transmitted, for example, from an AP. The trigger frame can be configured as a MAC frame and can be included in a PPDU.

[0109] Some of the fields shown in Figure 11 may be omitted and other fields may be added, and the length of each of the fields may be varied other than as shown.

[0110] The frame control field 1110 in FIG. 11 includes information regarding the version of the MAC protocol and other additional control information, and the duration field 1120 may include information regarding time information for NAV setting and an STA identifier (e.g., AID).

[0111] Also, the RA field 1130 includes address information of the STA receiving the trigger frame, and may be omitted as necessary. The TA field 1140 includes address information of the STA (e.g., AP) transmitting the trigger frame, and the common information field 1150 includes common control information applied to the receiving STA receiving the trigger frame. For example, a field indicating the length of the L-SIG field of the upward PPDU transmitted in response to the trigger frame, and information controlling the contents of the SIG-A field (i.e., the HE-SIG-A field) of the upward PPDU transmitted in response to the trigger frame may be included. Also, the common control information may include information on the length of the CP of the upward PPDU transmitted in response to the trigger frame and information on the length of the LTF field.

[0112] Also, it is preferable to include per user information fields 1160#1 to 1160#N corresponding to the number of receiving STAs that receive the trigger frame of Fig. 11. The per user information fields may also be called "allocation fields."

[0113] The trigger frame of FIG. 11 may also include a padding field 1170 and a frame check sequence field 1180.

[0114] Each of the per user information fields 1160#1 to 1160#N shown in FIG. 11 may further include multiple subfields.

[0115] 12 shows an example of a common information field of a trigger frame. Some of the subfields in FIG. 12 may be omitted, and other subfields may be added. Also, the length of each of the subfields shown in the figure may be modified.

[0116] The illustrated length field 1210 has the same value as the length field of the L-SIG field of the upstream PPDU transmitted corresponding to the trigger frame, and the length field of the L-SIG field of the upstream PPDU indicates the length of the upstream PPDU. As a result, the length field 1210 of the trigger frame can be used to indicate the length of the corresponding uplink PPDU.

[0117] In addition, the cascade indicator field 1220 indicates whether or not a cascade operation is performed. Cascade operation means that downlink link MU transmission and uplink link MU transmission are both performed within the same TXOP. In other words, it means that after a downlink link MU transmission, an uplink link MU transmission is performed after a preset time (e.g., SIFS). During cascade operation, there can be only one transmitting device (e.g., AP) performing downlink communication, and there can be multiple transmitting devices (e.g., non-AP) performing uplink communication.

[0118] The CS request field 1230 indicates whether the receiving device that has received the trigger frame should take into consideration the state of the wireless medium, NAV, etc., when transmitting the corresponding uplink PPDU.

[0119] The HE-SIG-A information field 1240 may include information that controls the content of the SIG-A field (i.e., the HE-SIG-A field) of the upstream PPDU transmitted in response to the trigger frame.

[0120] The CP and LTF type field 1250 may include information on the LTF length and CP length of the upstream PPDU transmitted in response to the trigger frame. The trigger type field 1260 may indicate the purpose for which the trigger frame is used, such as normal triggering, triggering for beamforming, or a request for Block ACK / NACK.

[0121] In this specification, the trigger type field 1260 of the trigger frame may be assumed to indicate a Basic type trigger frame for normal triggering. For example, a Basic type trigger frame may be referred to as a Basic trigger frame.

[0122] Figure 13 shows an example of subfields included in a per user information field. The user information field 1300 in Figure 13 can be understood as any one of the individual user information fields 1160#1 to 1160#N previously mentioned in Figure 11. Some of the subfields included in the user information field 1300 in Figure 13 can be omitted, and other subfields can be added. Also, the length of each of the illustrated subfields can be modified.

[0123] The User Identifier field 1310 in FIG. 13 represents an identifier of a STA (i.e., a receiving STA) corresponding to per user information, and an example of the identifier may be all or a part of the AID (association identifier) ​​value of the receiving STA.

[0124] Also, an RU Allocation field 1320 may be included. That is, when a receiving STA identified in the user identifier field 1310 transmits a TB PPDU corresponding to the trigger frame, the TB PPDU is transmitted via an RU indicated by the RU Allocation field 1320. In this case, the RU indicated by the RU Allocation field 1320 may be an RU shown in FIG. 5, FIG. 6, or FIG. 7.

[0125] 13 may include a coding type field 1330. The coding type field 1330 may indicate a coding type of the TB PPDU. For example, if BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to '1', and if LDPC coding is applied, the coding type field 1330 may be set to '0'.

[0126] 13 may include an MCS field 1340. The MCS field 1340 may indicate an MCS scheme applied to the TB PPDU. For example, if BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to '1', and if LDPC coding is applied to the TB PPDU, the coding type field 1330 may be set to '0'.

[0127] The UORA (UL OFDMA-based Random Access) technique will be described below.

[0128] FIG. 14 illustrates the technical features of the UORA technique.

[0129] A transmitting STA (e.g., AP) may allocate six RU resources as shown in FIG. 14 via a trigger frame. Specifically, the AP may allocate a first RU resource AID 0, RU 1, a second RU resource AID 0, RU 2, a third RU resource AID 0, RU 3, a fourth RU resource AID 2045, RU 4, a fifth RU resource AID 2045, RU 5, and a sixth RU resource AID 3, RU 6). Information on AID 0, AID 3, or AID 2045 may be included in, for example, the user identification field 1310 of FIG. 13. Information on RUs 1 to 6 may be included in, for example, the RU allocation field 1320 of FIG. 13. AID=0 may indicate UORA resources for associated STAs, and AID=2045 may indicate UORA resources for un-associated STAs. As a result, the first to third RU resources in FIG. 14 can be used as UORA resources for associated STAs, the fourth to fifth RU resources in FIG. 14 can be used as UORA resources for un-associated STAs, and the sixth RU resource in FIG. 14 can be used as a resource for a normal UL MU.

[0130] In the example of Fig. 14, the OBO (OFDMA random access BackOff) counter of STA1 is decremented to 0, and STA1 randomly selects the second RU resource AID 0, RU 2. Also, since the OBO counter of STA2 / 3 is greater than 0, no uplink resource is assigned to STA2 / 3. Also, in Fig. 14, STA4 includes its own AID (i.e., AID=3) in the trigger frame, so the resource of RU 6 is assigned without backoff.

[0131] Specifically, since STA1 in FIG. 14 is an associated STA, there are a total of three eligible RA RUs for STA1 (RU 1, RU 2, RU 3), and thus STA1 has decreased its OBO counter by 3, resulting in the OBO counter becoming 0. Also, since STA2 in FIG. 14 is an associated STA, there are a total of three eligible RA RUs for STA2 (RU 1, RU 2, RU 3), and thus STA2 has decreased its OBO counter by 3, but the OBO counter is greater than 0. Also, since STA3 in FIG. 14 is an un-associated STA, there are a total of two eligible RA RUs for STA3 (RU 4, RU 5), and thus STA3 has decreased its OBO counter by 2, but the OBO counter is greater than 0.

[0132] FIG. 15 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0133] The 2.4 GHz band may be referred to by other names such as the first band, etc. Also, the 2.4 GHz band may refer to a frequency range in which channels with center frequencies adjacent to 2.4 GHz (e.g., channels with center frequencies within 2.4 to 2.5 GHz) are used / supported / defined.

[0134] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz in the 2.4 GHz band may have multiple channel indexes (e.g., index 1 through index 14). For example, the center frequency of a 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407+0.005*N) GHz. The channel index may be referred to by various names such as a channel number. The specific numerical values ​​of the channel index and center frequency may be changed.

[0135] FIG. 15 exemplarily illustrates four channels in the 2.4 GHz band. The illustrated first to fourth frequency regions 1510 to 1540 may each include one channel. For example, the first frequency region 1510 may include channel 1 (a 20 MHz channel having an index of 1). At this time, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region 1520 may include channel 6. At this time, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region 1530 may include channel 11. At this time, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region 1540 may include channel 14. At this time, the center frequency of channel 14 may be set to 2484 MHz.

[0136] FIG. 16 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0137] The 5 GHz band may be referred to by other names such as a second band / band. The 5 GHz band may refer to a frequency range in which channels with center frequencies of 5 GHz or more and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific values ​​shown in FIG. 16 may be changed.

[0138] The channels in the 5 GHz band include the Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 can be referred to as UNII Low. UNII-2 can include frequency regions called UNII Mid and UNII-2Extended. UNII-3 can be referred to as UNII-Upper.

[0139] A plurality of channels may be set within the 5 GHz band, and the bandwidth of each channel may be set to various values, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency region / range within UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency region / range may be divided into four channels via a 40 MHz frequency region. The 5170 MHz to 5330 MHz frequency region / range may be divided into two channels via an 80 MHz frequency region. Or, the 5170 MHz to 5330 MHz frequency region / range may be divided into one channel via a 160 MHz frequency region.

[0140] FIG. 17 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0141] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with center frequencies of 5.9 GHz or higher are used / supported / defined. The specific values ​​shown in FIG. 17 may be changed.

[0142] For example, the 20 MHz channels in Figure 17 may be defined from 5.940 GHz. Specifically, the leftmost channel of the 20 MHz channels in Figure 17 may have an index (or channel index, channel number, etc.) of 1, and may be assigned a center frequency of 5.945 GHz. That is, the center frequency of the index N channel may be determined to be (5.940+0.005*N) GHz.

[0143] Thus, the indices (or channel numbers) of the 20 MHz channels in FIG. 17 can be 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, following the (5.940+0.005*N) GHz rule mentioned above, the indices for the 40 MHz channels in FIG. 17 can be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

[0144] In the example of FIG. 17, 20, 40, 80 and 160 MHz channels are shown, although 240 MHz and 320 MHz channels can be added.

[0145] The PPDU transmitted / received by the STA in this specification is described below.

[0146] FIG. 18 shows an example of a PPDU used in this specification.

[0147] 18 may be referred to by various names such as an EHT PPDU, a transmit PPDU, a receive PPDU, a first type, or an Nth type PPDU. For example, in this specification, a PPDU or an EHT PPDU may be referred to by various names such as a transmit PPDU, a receive PPDU, a first type, or an Nth type PPDU. Also, an EHT PPU may be used in an EHT system and / or a new wireless RAN system that improves on an EHT system.

[0148] The PPDU in FIG. 18 may indicate some or all of the PPDU types used in the EHT system. For example, the example in FIG. 18 may be used for both the single-user (SU) mode and the multi-user (MU) mode. In other words, the PPDU in FIG. 18 is a PPDU for one receiving STA or multiple receiving STAs. When the PPDU in FIG. 18 is used for the Trigger-based (TB) mode, the EHT-SIG in FIG. 18 may be omitted. In other words, a STA that has received a Trigger frame for Uplink-MU (UL-MU) communication may transmit a PPDU in the example in FIG. 18 with the EHT-SIG omitted.

[0149] In FIG. 18, the L-STF to EHT-LTF can be referred to as a preamble or a physical preamble, and can be generated / transmitted / received / acquired / decoded in the physical layer.

[0150] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields in Fig. 18 may be determined to be 312.5 kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and Data fields may be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be represented in units of 312.5 kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and Data fields may be represented in units of 78.125 kHz.

[0151] The L-LTF and L-STF in the PPDU of FIG. 18 above can be the same as conventional fields.

[0152] The L-SIG field in FIG. 18 may include, for example, 24-bit bit information. For example, the 24-bit information may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity bit, and 6-bit Tail bits. For example, the 12-bit Length field may include information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT, HT, VHT PPDU, or an EHT PPDU, the value of the Length field may be determined to be a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined to be a "multiple of 3+1" or a "multiple of 3+2". In other words, for a non-HT, HT, VHT PPDU, or EHT PPDU, the value of the Length field can be determined to be a multiple of 3, and for a HE PPDU, the value of the Length field can be determined to be "a multiple of 3 + 1" or "a multiple of 3 + 2".

[0153] For example, the transmitting STA can apply BCC encoding based on a code rate of 1 / 2 to the 24-bit information of the L-SIG field. Then, the transmitting STA can obtain 48 BCC coded bits. BPSK modulation can be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions other than the pilot subcarrier {subcarrier index -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols can be mapped to subcarrier indexes -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can further map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0154] The transmitting STA can generate a RL-SIG, which is generated similarly to the L-SIG. BPSK modulation can be applied to the RL-SIG. The receiving STA can know that the received PPDU is a HE PPDU or an EHT PPDU based on the presence of the RL-SIG.

[0155] A Universal SIG (U-SIG) may be inserted after the RL-SIG in Figure 18. The U-SIG may be called various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, etc.

[0156] The U-SIG may include N-bit information and may include information for identifying the type of EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4us. Each symbol of the U-SIG may be used to transmit 26-bit information. For example, each symbol of the U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.

[0157] For example, A-bit information (e.g., 52 un-coded bits) may be transmitted via the U-SIG (or U-SIG field), and the first symbol of the U-SIG may transmit the first X-bit information (e.g., 26 un-coded bits) of the total A-bit information, and the second symbol of the U-SIG may transmit the remaining Y-bit information (e.g., 26 un-coded bits) of the total A-bit information. For example, the transmitting STA may obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52-coded bits and perform interleaving on the 52-coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols assigned to each U-SIG symbol. One U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.

[0158] For example, A-bit information (e.g., 52 un-coded bits) transmitted by a U-SIG may include a CRC field (e.g., a 4-bit long field) and a tail field (e.g., a 6-bit long field). The CRC field and the tail field may be transmitted via the second symbol of the U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of a convolutional decoder, and may be set to, for example, "000000".

[0159] The A-bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits may be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of the U-SIG, or the version-independent bits may be assigned to both the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names such as first control bits and second control bits.

[0160] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted / received PPDU. For example, a first value of the 3-bit PHY version identifier may indicate that the transmitted / received PPDU is an EHT PPDU. In other words, when transmitting an EHT PPDU, the transmitting STA may set the 3-bit PHY version identifier to a first value. In other words, the receiving STA may determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value.

[0161] For example, the version-independent bits of the U-SIG may include a one-bit UL / DL flag field, where a first value of the one-bit UL / DL flag field is associated with UL communication and a second value of the UL / DL flag field is associated with DL communication.

[0162] For example, the version-independent bits of the U-SIG may include information regarding the length of the TXOP and information regarding the BSS color ID.

[0163] For example, when the EHT PPDU is divided into various types (e.g., an EHT PPDU supporting an SU, an EHT PPDU supporting an MU, an EHT PPDU associated with a Trigger Frame, an EHT PPDU associated with an Extended Range transmission, etc.), information regarding the type of the EHT PPDU can be included in the version-dependent bits of the U-SIG.

[0164] For example, the U-SIG may include information regarding 1) a bandwidth field including information regarding the bandwidth, 2) a field including information regarding the MCS technique applied to the EHT-SIG, 3) an indication field including information related to whether a dual subcarrier modulation (DCM) technique is applied to the EHT-SIG, 4) a field including information regarding the number of symbols used for the EHT-SIG, 5) a field including information regarding whether the EHT-SIG is generated across the entire band, 6) a field including information regarding the type of EHT-LTF / STF, and 7) a field indicating the length of the EHT-LTF and the CP length.

[0165] Preamble puncturing may be applied to the PPDU in FIG. 18. Preamble puncturing refers to applying puncturing to a portion of the entire band of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band of the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0166] For example, the preamble puncturing pattern may be preset. For example, when the first puncturing pattern is applied, puncturing may be applied only to the secondary 20 MHz band in the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing may be applied only to one of the two secondary 20 MHz bands included in the secondary 40 MHz band in the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing may be applied only to the secondary 20 MHz band included in the primary 80 MHz band in the 160 MHz band (or the 80+80 MHz band). For example, when the fourth puncturing pattern is applied, the primary 40 MHz band included in the primary 80 MHz band in the 160 MHz band (or the 80+80 MHz band) is present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

[0167] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or the EHT-SIG, for example, a first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and a second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0168] For example, the U-SIG and the EHT-SIG may include information on preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG may include information on the 160 MHz bandwidth, and the second field of the first U-SIG may include information on the preamble puncturing applied to the first 80 MHz band (i.e., information on the preamble puncturing pattern). Also, the first field of the second U-SIG may include information on the 160 MHz bandwidth, and the second field of the second U-SIG may include information on the preamble puncturing applied to the second 80 MHz band (i.e., information on the preamble puncturing pattern). On the other hand, the EHT-SIG subsequent to the first U-SIG may include information regarding the preamble puncturing applied to the second 80 MHz band (i.e., information regarding the preamble puncturing pattern), and the EHT-SIG subsequent to the second U-SIG may include information regarding the preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern).

[0169] Additionally or alternatively, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method: The U-SIG may include information about preamble puncturing for all bands (i.e., information about preamble puncturing patterns). That is, the EHT-SIG does not include information about preamble puncturing, and only the U-SIG may include information about preamble puncturing (i.e., information about preamble puncturing patterns).

[0170] The U-SIG can be configured in 20 MHz units. For example, when an 80 MHz PPDU is configured, the U-SIG can be duplicated. That is, the same four U-SIGs can be included in the 80 MHz PPDU. PPDUs that exceed the 80 MHz bandwidth can contain different U-SIGs.

[0171] The EHT-SIG in FIG. 18 may include control information for the receiving STA. The EHT-SIG may be transmitted over at least one symbol, and one symbol may have a length of 4us. Information regarding the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0172] The EHT-SIG may include the technical features of the HE-SIG-B described through Figures 8 to 9. For example, the EHT-SIG may include a common field and a user-specific field, as in the example of Figure 8. The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0173] As in the example of FIG. 8, the common field of the EHT-SIG and the user-specific field of the EHT-SIG can be coded separately. One user block field included in the user-specific field can include information for two users, while the last user block field included in the user-specific field can include information for one user. That is, one user block field of the EHT-SIG can include up to two user fields. As in the example of FIG. 9, each user field can be associated with a MU-MIMO allocation or a non-MU-MIMO allocation.

[0174] Similar to the example of FIG. 8, the common field of the EHT-SIG may include CRC bits and Tail bits, where the length of the CRC bits may be determined by 4 bits, and the length of the Tail bits may be determined by 6 bits and set to “000000”.

[0175] As in the example of FIG. 8, the common field of the EHT-SIG may include RU allocation information. The RU allocation information may refer to information regarding the location of RUs to which multiple users (i.e., multiple receiving STAs) are assigned. The RU allocation information may be configured in 8-bit (or N-bit) units as in Table 1.

[0176] Tables 5 to 7 are examples of 8-bit (or N-bit) information for various RU allocations. The indexes shown in each table are changeable, and some entries in Tables 5 to 7 can be omitted and entries that are not shown can be added.

[0177] Examples of Tables 5 to 7 relate to information about the locations of RUs allocated to a 20 MHz band. For example, "Index 0" in Table 5 can be used in a situation where nine 26-RUs are individually allocated (e.g., a situation where nine 26-RUs are individually allocated as shown in FIG. 5).

[0178] On the other hand, in an EHT system, multiple RUs can be assigned to one STA. For example, in the case of "Index 60" in Table 6, one 26-RU is assigned to one user (i.e., the receiving STA) on the far left side of the 20 MHz band, one 26-RU and one 52-RU are assigned to another user (i.e., the receiving STA) on the right side, and five 26-RUs can be assigned individually to the right of that.

[0179] [Table 5]

[0180] [Table 6]

[0181] [Table 7]

[0182] A mode in which the common field of the EHT-SIG is omitted may be supported. The mode in which the common field of the EHT-SIG is omitted may be called a compressed mode. When the compressed mode is used, multiple users of the EHT PPDU (i.e., multiple receiving STAs) can decode the PPDU (e.g., the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) received via the same frequency band. On the other hand, when the non-compressed mode is used, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., the data field of the PPDU) via different frequency bands.

[0183] The EHT-SIG may be configured based on various MCS techniques. As described above, information related to the MCS technique applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on the DCM technique. For example, among N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation technique may be applied to consecutive half tones, and a second modulation technique may be applied to the remaining consecutive half tones. That is, the transmitting STA may modulate specific control information to a first symbol based on a first modulation technique and allocate it to the consecutive half tones, and modulate the same control information to a second symbol based on a second modulation technique and allocate it to the remaining consecutive half tones. As described above, information related to whether the DCM technique is applied to the EHT-SIG (e.g., a 1-bit field) may be included in the U-SIG.

[0184] The EHT-STF of FIG 18 can be used to improve automatic gain control estimation in a multiple input multiple output (MIMO) environment or an OFDMA environment, and the EHT-LTF of FIG 18 can be used to estimate a channel in a MIMO environment or an OFDMA environment.

[0185] The EHT-STF of FIG. 18 can be set to various types. For example, the first type of STF (i.e., 1x STF) can be generated based on a first type STF sequence in which a non-zero coefficient is arranged at 16 subcarrier intervals. The STF signal generated based on the first type STF sequence can have a period of 0.8 μs, and the 0.8 μs periodic signal can be repeated five times to become a first type STF having a length of 4 μs. For example, the second type of STF (i.e., 2x STF) can be generated based on a second type STF sequence in which a non-zero coefficient is arranged at 8 subcarrier intervals. The STF signal generated based on the second type STF sequence can have a period of 1.6 μs, and the 1.6 μs periodic signal can be repeated five times to become a second type EHT-STF having a length of 8 μs. In the following, an example of a sequence (i.e., an EHT-STF sequence) for configuring an EHT-STF is presented. The following sequence can be modified in various manners.

[0186] The EHT-STF can be constructed based on the following M-sequence:

[0187] [Number 1] M={-1, -1, -1, 1, 1, 1, -1, 1, 1, 1, -1, 1, 1, -1, 1}

[0188] The EHT-STF for 20 MHz PPDU may be configured based on the following formula. The following example may be a first type (i.e., 1x STF) sequence. For example, the first type sequence may be included in an EHT-PPDU that is not a TB (trigger-based) PPDU. In the following formula, (a:b:c) may mean an interval defined from a tone index (i.e., subcarrier index) to c tone index at b tone intervals (i.e., subcarrier intervals). For example, the following formula 2 may represent a sequence defined at 16 tone intervals from tone index -112 to 112 index. Since a subcarrier spacing of 78.125 kHz is applied to the EHT-STF, the 16 tone interval may mean that the EHT-STF coefficient (or element) is arranged at 78.125*16=1250 kHz intervals. Also, * means multiplication, and sqrt() means square root.

[0189] [Number 2] EHT-STF(-112:16:112)={M}*(1+j) / sqrt(2)

[0190] EHT-STF(0)=0

[0191] The EHT-STF for 40 MHz PPDU may be configured based on the following formula: An example of the following may be a first type (ie, 1x STF) sequence.

[0192] [Number 3] EHT-STF(-240:16:240)={M, 0, -M}*(1+j) / sqrt(2)

[0193] The EHT-STF for 80 MHz PPDU may be configured based on the following formula: An example of the following may be a first type (ie, 1x STF) sequence.

[0194] [Number 4] EHT-STF(-496:16:496)={M, 1, -M, 0, -M, 1, -M}*(1+j) / sqrt(2)

[0195] The EHT-STF for the 160 MHz PPDU may be configured based on the following formula: The following example may be a first type (ie, 1x STF) sequence.

[0196] [Number 5] EHT-STF(-1008:16:1008)={M, 1, -M, 0, -M, 1, -M, 0, -M, -1, M, 0, -M, 1, -M}*(1+j) / sqrt(2)

[0197] The sequence for the lower 80 MHz of the EHT-STF for the 80+80 MHz PPDU may be the same as Equation 4. The sequence for the upper 80 MHz of the EHT-STF for the 80+80 MHz PPDU may be configured based on the following equation.

[0198] [Number 6] EHT-STF(-496:16:496)={-M, -1, M, 0, -M, 1, -M}*(1+j) / sqrt(2)

[0199] Below, Equations 7 to 11 relate to an example of a second type (ie, 2x STF) sequence.

[0200] [Number 7] EHT-STF(-120:8:120)={M, 0, -M}*(1+j) / sqrt(2)

[0201] The EHT-STF for 40 MHz PPDU can be constructed based on the following formula:

[0202] [Number 8] EHT-STF(-248:8:248)={M, -1, -M, 0, M, -1, M}*(1+j) / sqrt(2)

[0203] EHT-STF(-248)=0

[0204] EHT-STF(248)=0

[0205] The EHT-STF for 80 MHz PPDU can be constructed based on the following formula:

[0206] [Number 9] EHT-STF(-504:8:504)={M, -1, M, -1, -M, -1, M, 0, -M, 1, M, 1, -M, 1, -M}*(1+j) / sqrt(2)

[0207] The EHT-STF for 160 MHz PPDU can be constructed based on the following formula:

[0208] [Number 10] EHT-STF(-1016:16:1016)={M, -1, M, -1, -M, -1, M, 0, -M, 1, M, 1, -M, 1, -M, 0, -M, 1, -M, 1, M, 1, -M, 0, -M, 1, M, 1, -M, 1, -M}*(1+j) / sqrt(2)

[0209] EHT-STF(-8)=0, EHT-STF(8)=0,

[0210] EHT-STF(-1016)=0, EHT-STF(1016)=0

[0211] Of the EHT-STF for the 80+80 MHz PPDU, the sequence for the lower 80 MHz may be the same as Equation 9. Of the EHT-STF for the 80+80 MHz PPDU, the sequence for the upper 80 MHz may be configured based on the following equation.

[0212] [Number 11] EHT-STF(-504:8:504)={-M, 1, -M, 1, M, 1, -M, 0, -M, 1, M, 1, -M, 1, -M}*(1+j) / sqrt(2)

[0213] EHT-STF(-504)=0,

[0214] EHT-STF(504)=0

[0215] The EHT-LTF may have a first, second, or third type (i.e., 1x, 2x, or 4x LTF). For example, the first / second / third type LTF may be generated based on an LTF sequence in which a non-zero coefficient is arranged at 4 / 2 / 1 subcarrier intervals. The first / second / third type LTF may have a time length of 3.2 / 6.4 / 12.8 μs. In addition, GIs of various lengths (e.g., 0.8 / 1 / 6 / 3.2 μs) may be applied to the first / second / third type LTF.

[0216] Information regarding the type of STF and / or LTF (including information regarding the GI applied to the LTF) may be included in the SIG A field and / or SIG B field of FIG.

[0217] The PPDU of FIG. 18 (ie, EHT-PPDU) can be constructed based on the examples of FIG. 5 and FIG.

[0218] For example, an EHT PPDU transmitted on a 20 MHz band, i.e., a 20 MHz EHT PPDU, can be configured based on the RU in Figure 5. That is, the RU locations of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU can be determined as shown in Figure 5.

[0219] An EHT PPDU transmitted on a 40 MHz band, i.e., a 40 MHz EHT PPDU, can be configured based on the RU in Fig. 6. That is, the RU locations of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU can be determined as shown in Fig. 6.

[0220] Since the RU locations in Figure 6 correspond to 40 MHz, a tone-plan for 80 MHz can be determined by repeating the pattern in Figure 6 twice, i.e., the 80 MHz EHT PPDU can be transmitted based on a new tone-plan in which the RUs in Figure 6, which are not the RUs in Figure 7, are repeated twice.

[0221] When the pattern of FIG. 6 is repeated twice, 23 tones (i.e., 11 guard tones + 12 guard tones) can be configured in the DC region. That is, the tone plan for an 80 MHz EHT PPDU allocated based on OFDMA can have 23 DC tones. In contrast, an 80 MHz EHT PPDU allocated based on non-OFDMA (i.e., non-OFDMA full bandwidth 80 MHz PPDU) can be configured based on 996RU and can include 5 DC tones, 12 left guard tones, and 11 right guard tones.

[0222] The tone plan for 160 / 240 / 320 MHz can be constructed by repeating the pattern of FIG. 6 multiple times.

[0223] The PPDU in FIG. 18 can be determined (or identified) as an EHT PPDU based on the following method.

[0224] The receiving STA can determine the type of the received PPDU as EHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) an RL-SIG in which the L-SIG of the received PPDU is repeated is detected, and 3) a result of applying "modulo 3" to the value of the Length field of the L-SIG of the received PPDU is detected as "0", the received PPDU can be determined as EHT PPDU. If the received PPDU is determined as EHT PPDU, the receiving STA can detect the type of EHT PPDU (e.g., SU / MU / Trigger-based / Extended Range type) based on bit information included in the symbols after the RL-SIG of FIG. 18. In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol after the L-LTF signal, which is the BSPK, 2) the RL-SIG that follows the L-SIG field and is the same as the L-SIG, 3) the L-SIG including a Length field in which the result of applying "modulo 3" is set to "0", and 4) the 3-bit PHY version identifier (e.g., a PHY version identifier having a first value) of the U-SIG mentioned above.

[0225] For example, the receiving STA can determine that the type of the received PPDU is HE PPDU based on the following: 1) the first symbol after the L-LTF signal is BPSK, 2) an RL-SIG in which the L-SIG is repeated is detected, and 3) the result of applying "modulo 3" to the Length value of the L-SIG is detected as "1" or "2", the received PPDU can be determined as HE PPDU.

[0226] For example, the receiving STA can determine the type of the received PPDU as non-HT, HT, or VHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) an RL-SIG in which the L-SIG is repeated is not detected, the received PPDU can be determined as non-HT, HT, or VHT PPDU. Also, even if the receiving STA detects a repetition of the RL-SIG, if the result of applying "modulo 3" to the Length value of the L-SIG is detected as "0", the received PPDU can be determined as non-HT, HT, or VHT PPDU.

[0227] In the following example, signals indicated as (transmit / receive / upward / downward) signals, (transmit / receive / upward / downward) frames, (transmit / receive / upward / downward) packets, (transmit / receive / upward / downward) data units, (transmit / receive / upward / downward) data, etc. may be signals transmitted and received based on the PPDU of FIG. 18. The PPDU of FIG. 18 may be used to transmit and receive various types of frames. For example, the PPDU of FIG. 18 may be used for a control frame. Examples of the control frame may include RTS (request to send), CTS (clear to send), PS-Poll (Power Save-Poll), BlockACKReq, BlockAck, NDP (Null Data Packet) announcement, and Trigger Frame. For example, the PPDU of FIG. 18 may be used for a management frame. Examples of the management frame include a Beacon frame, a (Re-)Association Request frame, a (Re-)Association response frame, a Probe Request frame, and a Probe Response frame. For example, the PPDU in FIG. 18 can be used for a data frame. For example, the PPDU in FIG. 18 can be used to simultaneously transmit at least two or more of a control frame, a management frame, and a data frame.

[0228] FIG. 19 shows a modified example of the transmitting device and / or the receiving device of this specification.

[0229] Each device / STA in sub-drawings (a) / (b) of Fig. 1 can be modified as shown in Fig. 19. The transceiver 630 in Fig. 19 can be the same as the transceivers 113 and 123 in Fig. 1. The transceiver 630 in Fig. 19 can include a receiver and a transmitter.

[0230] The processor 610 in Figure 19 may be the same as the processors 111, 121 in Figure 1. Or, the processor 610 in Figure 19 may be the same as the processing chips 114, 124 in Figure 1.

[0231] Memory 150 in Figure 19 can be the same as memories 112, 122 in Figure 1. Alternatively, memory 150 in Figure 19 can be a separate external memory that is different from memories 112, 122 in Figure 1.

[0232] 19, the power management module 611 manages power to the processor 610 and / or the transceiver 630. The battery 612 provides power to the power management module 611. The display 613 outputs results processed by the processor 610. The keypad 614 receives inputs used by the processor 610. The keypad 614 can be displayed on the display 613. The SIM card 615 can be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and associated keys used to identify and authenticate a subscriber on mobile phone devices such as mobile phones and computers.

[0233] 19, the speaker 640 can output sound-related results processed by the processor 610. The microphone 641 can receive sound-related input for use by the processor 610.

[0234] The technical features of the STA-assisted channel bonding herein are described below.

[0235] For example, in an IEEE 802.11n system, two 20 MHz channels can be bonded to implement 40 MHz channel bonding, and in an IEEE 802.11ac system, 40 / 80 / 160 MHz channel bonding can be implemented.

[0236] For example, a STA can perform channel bonding for a Primary 20 MHz channel (P20 channel) and a Secondary 20 MHz channel (S20 channel). A back-off count / counter can be used in the channel bonding process. The back-off count value can be selected as a random value and decremented during the back-off interval. Generally, when the back-off count value becomes 0, the STA can attempt to connect to the channel.

[0237] The STA performing channel bonding determines whether the S20 channel has maintained an idle state for a certain period (e.g., PIFS (point coordination function interframe space)) at the time when the P20 channel is determined to be in an idle state during the backoff interval and the backoff count value for the P20 channel becomes 0. If the S20 channel is in an idle state, the STA can perform bonding for the P20 channel and the S20 channel. That is, the STA can transmit a signal (PPDU) through a 40 MHz channel (i.e., a 40 MHz bonding channel) including the P20 channel and the S20 channel.

[0238] Figure 20 shows an example of channel bonding. As shown in Figure 20, a Primary 20 MHz channel and a Secondary 20 MHz channel can configure a 40 MHz channel (Primary 40 MHz channel) through channel bonding. That is, the bonded 40 MHz channel can include a Primary 20 MHz channel and a Secondary 20 MHz channel.

[0239] Channel bonding can be performed when the channel following the Primary channel is in an Idle state. That is, the Primary 20MHz channel, the Secondary 20MHz channel, the Secondary 40MHz channel, and the Secondary 80MHz channel can be bonded in sequence. If the Secondary 20MHz channel is determined to be in a Busy state, channel bonding may not be performed even if all other Secondary channels are in an Idle state. Also, if the Secondary 20MHz channel is in an Idle state and the Secondary 40MHz channel is determined to be in a Busy state, channel bonding may be performed only for the Primary 20MHz channel and the Secondary 20MHz channel.

[0240] In the following, STA-assisted preamble puncturing in this specification is described.

[0241] For example, in the example of FIG. 20, when the Primary 20MHz channel, the Secondary 40MHz channel, and the Secondary 80MHz channel are all in an idle state and the Secondary 20MHz channel is in a busy state, bonding to the Secondary 40MHz channel and the Secondary 80MHz channel is impossible. In this case, the STA can configure a 160MHz PPDU, puncture the preamble (e.g., L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF, EHT-SIG, EHT-STF, EHT-LTF, etc.) transmitted through the Secondary 20MHz channel, and transmit a signal through a channel in an idle state. In other words, the STA can perform preamble puncturing on a part of the band of the PPDU. Information regarding preamble puncturing (e.g., information regarding the 20 / 40 / 80 MHz channel / band to which puncturing is applied) may be included in the signal field of the PPDU (e.g., HE-SIG-A, U-SIG, EHT-SIG).

[0242] Hereinafter, technical features of the Multi-link (ML) supported by the STA of this specification will be described.

[0243] The STA (AP and / or non-AP STA) in this specification can support Multi Link (ML) communication. ML communication can mean communication supporting multiple links. Links related to ML communication can include channels (e.g., 20 / 40 / 80 / 160 / 240 / 320 MHz channels) of the 2.4 GHz band disclosed in FIG. 15, the 5 GHz band disclosed in FIG. 16, and the 6 GHz band disclosed in FIG. 17.

[0244] The multiple links used for ML communication can be set in various ways. For example, the multiple links supported by one STA for ML communication are multiple channels in the 2.4 GHz band, multiple channels in the 5 GHz band, and multiple channels in the 6 GHz band. Or, the multiple links supported by one STA for ML communication are a combination of at least one channel in the 2.4 GHz band (or 5 GHz / 6 GHz band) and at least one channel in the 5 GHz band (or 2.4 GHz / 6 GHz band). Meanwhile, at least one of the multiple links supported by one STA for ML communication is a channel to which preamble puncturing is applied.

[0245] The STA can perform ML setup to perform ML communication. The ML setup can be performed based on a management frame or a control frame such as a Beacon, a Probe Request / Response, or an Association Request / Response. For example, information on the ML setup can be included in an element field included in a Beacon, a Probe Request / Response, or an Association Request / Response.

[0246] When the ML setup is completed, an enabled link for ML communication can be determined. The STA can perform frame exchange through at least one of the links determined as the enabled link. For example, the enabled link can be used for at least one of a management frame, a control frame, and a data frame.

[0247] When one STA supports multiple links, the transceiver supporting each link can operate as one logical STA. For example, one STA supporting two links can be represented as one Multi-Link Device (MLD) including a first STA for the first link and a second STA for the second link. For example, one AP supporting two links can be represented as one AP MLD including a first AP for the first link and a second AP for the second link. Also, one non-AP supporting two links can be represented as one non-AP MLD including a first STA for the first link and a second STA for the second link.

[0248] Below, more specific features regarding the ML setup are described.

[0249] MLD (AP MLD and / or non-AP MLD) can transmit information about links that the MLD can support through ML setup. The information about the links can be configured in various ways. For example, the information about the links can include at least one of the following: 1) information about whether the MLD (or STA) supports simultaneous RX / TX operation; 2) information about the number / upper limit of uplink / downlink links supported by the MLD (or STA); 3) information about the location / band / resource of uplink / downlink links supported by the MLD (or STA); 4) information about frame types (management, control, data, etc.) available or preferred in at least one uplink / downlink link; 5) ACK policy information available or preferred in at least one uplink / downlink link; and 6) information about traffic identifiers (TIDs) available or preferred in at least one uplink / downlink link. TIDs are expressed by eight types of values ​​according to the conventional WLAN standard, and are related to the priority of traffic data. That is, eight TID values ​​corresponding to four access categories (AC) according to the conventional WLAN standard (AC_BK (background), AC_BE (best effort), AC_VI (video), and AC_VO (voice)) can be defined.

[0250] For example, it may be preset that all TIDs are mapped to uplink / downlink links. Specifically, if no negotiation is performed through ML setup, all TIDs are used for ML communication, and if mapping between uplink / downlink links and TIDs is negotiated through additional ML setup, the negotiated TIDs may be used for ML communication.

[0251] Through ML setup, multiple links that can be used by a transmitting MLD and a receiving MLD related to ML communication can be set, which can be called "enabled links." An "enabled link" can be called in various ways, such as a first link, a second link, a transmitting link, a receiving link, etc.

[0252] ' After the ML setup is completed, the MLD can update the ML setup. For example, the MLD can transmit information about a new link when an update to information about a link is required. The information about the new link can be transmitted based on at least one of a management frame, a control frame, and a data frame.

[0253] The introduction of HARQ is being considered for EHT (extreme high throughput), a standard being discussed after IEEE802.11ax. The introduction of HARQ can have the effect of expanding coverage in low SNR (signal to noise ratio) environments, i.e. environments where the distance between the transmitting terminal and the receiving terminal is long, and can achieve higher throughput in high SNR environments.

[0254] The device described below is the device in FIG. 1 and / or FIG. 19, and the PPDU is the PPDU in FIG. 18. The device is an AP or a non-AP STA. The device described below is an AP MLD (multi-link device) that supports multi-link or a non-AP STA MLD.

[0255] EHT (extremely high throughput), a standard being discussed after 802.11ax, takes into account a multi-link environment in which one or more bands are used simultaneously. When a device is multi-link or supports multi-link, the device can use one or more bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 60 GHz, etc.) simultaneously or alternately.

[0256] Although the following description will be given in the form of a multi-link, the frequency band may be configured in various forms other than the above. In this specification, the terms multi-link, multi-link, etc. may be used, but for convenience of explanation, some embodiments may be described based on the multi-link.

[0257] In the following specification, MLD means multi-link device. MLD has one or more connected STAs and has one MAC SAP (service access point) connected to an upper link layer (Logical Link Control, LLC). MLD can mean a physical device or a logical device. Hereinafter, device can mean MLD.

[0258] In the following specification, the transmitting device and the receiving device may refer to MLD. The first link of the receiving / transmitting device is a terminal (e.g., STA or AP) included in the receiving / transmitting device that performs signal transmission / reception through the first link. The second link of the receiving / transmitting device is a terminal (e.g., STA or AP) included in the receiving / transmitting device that performs signal transmission / reception through the second link.

[0259] In IEEE 802.11be, two types of multi-link operation can be supported. For example, STR (simultaneous transmit and receive) and non-STR operation can be considered. For example, STR can be referred to as asynchronous multi-link operation, and non-STR can be referred to as synchronous multi-link operation. Multi-link can include multiple bands. That is, multi-link can mean links included in multiple frequency bands, or multiple links included in one frequency band.

[0260] EHT (11be) considers multi-link technology, where multi-link can include multi-band. That is, multi-link can refer to links of multiple bands, and can also refer to multiple multi-links within one band. Two types of multi-link operation are considered: asynchronous operation, which allows simultaneous TX / RX on multiple links, and synchronous operation, which does not. In the following, the capability to simultaneously receive and transmit on multiple links is called STR (simultaneous transmit and receive), STA with STR capability is called STR MLD (multi-link device), and STA without STR capability is called non-STR MLD.

[0261] FIG. 21 is a diagram illustrating an embodiment of a device that supports multilink.

[0262] Referring to FIG. 21, a STA MLD (or AP MLD) may include three STAs and have three links, and each link may have a Primary channel (PCH). The availability of STR capability for AP MLD and STA MLD may vary depending on the channel of each link. The STR capability needs to be negotiated. That is, the STR capability of AP MLD may vary depending on the channel of the link set by AP MLD, and the multi-link operation of the two MLDs may vary depending on the capability of the STA MLD and which link each STA in the STA MLD selects. The operation negotiation (e.g., multi-link setup) between AP MLD and STA MLD based on STR capability will be described below.

[0263] Nomenclature herein may be changed and a STA may include an AP STA or a non-AP STA.

[0264] The multi-link operation for all active links can change depending on the STR capability of the link set selected by the AP / STA MLD.

[0265] FIG. 22 is a diagram showing an embodiment of the STR capability of a multi-link.

[0266] 22, link1 and link2 of the left STA MLD are in a non-STR relationship, i.e., a link set that cannot transmit and receive simultaneously on multiple links, and link2 and link3 are also in a non-STR relationship. Here, even if link1 and link3 are STR, link1, link2, and link3 must operate in non-STR due to link2.

[0267] In the right STA MLD in Figure 22, link1 and link2 are in a non-STR relationship, and link3 and link4 are also in a non-STR relationship. However, since link2 and link3 are in an STR relationship, non-STR can be considered for each of link1 / 2 and link3 / 4.

[0268] MLD can have link sets with non-STR relationships, which are referred to herein as non-STR link sets. The basic process (A) is as follows.

[0269] 1) AP MLD provides link information to STA MLD

[0270] 2) STA MLD requests the link it wishes to operate on

[0271] 3) The AP MLD responds by determining the link on which the STA MLD operates based on the request.

[0272] Here, the STA MLD does not necessarily have to request a link that includes the link on which the current negotiation is being performed. That is, the STA MLD can flexibly request a link depending on the capability. The scenario for this will be described later in this specification.

[0273] Here, AP MLD does not necessarily have to select all links requested by STA MLD. If AP MLD always selects all requested links, it can operate according to the capability, but performance may be significantly degraded.

[0274] - Method of requesting / responding link set and / or STR capability in steps 2) and 3)

[0275] The order is determined according to the link information announced by the AP, and if the non-STR link set is also known to the STA, it can be represented by a bitmap for each link.

[0276] Ex) 1: Select or request link, 0: Do not select or do not request link

[0277] FIG. 23 is a diagram showing an example of link information.

[0278] Referring to FIG. 23, the link information can be expressed in 3 bits. For example, if a STA requests links 2 and 3, the link information can indicate 011.

[0279] FIG. 24 is a diagram showing an example of link information.

[0280] Referring to FIG. 24, if the order is determined, the bitmap can indicate whether each link set is an STR in the order, such as [link1, link2], [link1, link3], ..., and then the requested or selected link set can be indicated in bitmap form.

[0281] Ex) STR availability can be indicated with 1 bit for all link sets that can be made with N links: STR availability of links 1, 2, ..., STR availability of links 1, N, STR availability of links 2, 3, ..., STR availability of links N-1, N can each be indicated with 1 bit. For example, STR availability of each link set can be indicated with 1 bit information with a value of 1 if it is STR and 0 if it is not STR.

[0282] Ex) Link request / selection 1: Select or request link, 0: Do not select or do not request link

[0283] For example, in Figures 23 and 24, the STR availability is 110 if link2 and link3 are non-STR (i.e., the 1st bit indicates the STR availability of [link1, 2], the 2nd bit indicates the STR availability of [link1, 3], and the 3rd bit indicates the STR availability of [link2, 3], so 110 contains the information that only the third link set, [link2, 3], is non-STR), and if the STA requests link2 and 3, it can be represented as 011. Therefore, the total indication bitmap can be 110011.

[0284] Alternatively, along with the STR availability indication for each link set, it is also possible to indicate whether the link set is requested or selected. The number of bits is the same as in the above method, and the same example can be indicated as 101001. That is, the last 2 bits, 01, indicate that it is a non-STR link set and that the STA has requested link2 and link3. For example, the first 2 bits "10" can mean that [link1, 2] are STR and not requested, the second 2 bits "10" can mean that [link1, 3] are STR and not requested, and the third 2 bits "01" can mean that [link2, 3] are non-STR and are requested.

[0285] FIG. 25 is an example of a Multi-link setup for the basic process (A).

[0286] Referring to FIG. 25, the AP MLD has four links and can announce link information through a Beacon frame or a Probe Response frame. The link information can include information on AP / Link capabilities, channel information, and Non-STR link sets. For example, Links 1 and 2 and Links 3 and 4 are non-STR link sets. The Non-AP MLD has three STAs, and each STA can be connected through a link and can discover the AP MLD through link 4. The Non-AP MLD can request Links 2, 3, and 4 as links to operate through link 4, and the AP MLD can respond based on this request so that the Non-AP MLD can operate on links 2, 3, and 4. For example, if the STA MLD does not have the capability to operate on link 4, it does not request link 4.

[0287] In the above step (A), when the three link pairs in the Multi-link Setup are {STA1<->AP4}, {STA2<->AP3}, and {STA3<->AP2}, STA2 and STA3 have not yet performed initial frame exchange with the AP. In this case, a method is required for STA2 and STA3 to be able to exchange frames with AP2 and AP3, respectively, on the corresponding links. The method is as follows, but is not limited thereto.

[0288] That is, the method of starting signal transmission / reception for a STA that is set to perform a multi-link operation but does not directly perform link setup can be divided into a method in the multi-link setup step and a method after multi-link setup. Among the links to be set up, the link through which the association request / response frame is transmitted is called an association link, and the other setup links are called non-association links. For example, in FIG. 25, if the setup links are links 2, 3, and 4, link 4 becomes the association link, and links 2 and 3 become non-association links. However, this is merely a designation, and the STAs and APs of the non-association links have already performed association.

[0289] 1) Method in the Multi-link Setup step

[0290] 1-1) MAC Address Signaling: A STA (i.e., an association link STA) that transmits a management frame (e.g., a probe request / response frame, a beacon frame, an association request / response frame) can transmit the MAC address of another STA (i.e., a non-association link STA) that belongs to the same MLD as itself. This MAC address is recognized by a STA operating on a non-association link to enable frame exchange. Methods including but not limited to the following are provided below.

[0291] A. New element or field definition: A new element or field to be included in the management frame can be defined. Basically, the MLD Per-STA MAC address field can be defined as follows:

[0292] FIG. 26 is a diagram illustrating one embodiment of the MLD Per-STA MAC address field.

[0293] 26, since AP MLD has link IDs that can distinguish each AP, it is possible to indicate the MAC addresses of STAs (i.e., APs) operating on non-association links in the order of link IDs. If STA IDs that can distinguish each STA are defined in non-AP MLD, it is possible to indicate MAC addresses in the order of STA IDs. In addition, for reliable indication, a link ID or STA ID can be included before each MAC address.

[0294] For example, a STA that transmits a management frame may not specify the MAC addresses of all STAs that belong to the same MLD as itself. For example, in FIG. 25, STA1 may not transmit the MAC address of STA2. In such a case, the number of STAs (or the number of links (in the case of an AP)) may be additionally specified.

[0295] In the case of a non-MLD, the relevant field may not be included, so the MLD address field presented in FIG. 26, which is not a field, may also be included in the element.

[0296] FIG. 27 is a diagram illustrating one embodiment of the MLD Per-STA MAC address element.

[0297] B. Multi-link element includes: The MAC address of the STA operating on the non-association link can be included in the common info or per-STA info field of the ML information element (IE).

[0298] FIG. 28 is a diagram illustrating an embodiment of a multi-link element.

[0299] The order, name, and size of the fields in the format of the Multi-link Element can be changed, and additional fields can be present. Referring to FIG. 28, Common info can include common information between STAs in the MLD, and specific information for each STA can be included in the Per-STA Profile.

[0300] FIG. 29 is a diagram showing one embodiment of the ML IE.

[0301] Referring to Figure 29, the MLD Per-STA MAC address field in Figure 26 can be included in Common Info as in Figure 29. If the MAC address field exists in Common Info and the MAC address should always be included in the ML IE, the Per-STA Profile is not required. However, since each MAC address is different for each STA, the Per-STA Profile is semantically appropriate.

[0302] FIG. 30 is a diagram showing one embodiment of the ML IE.

[0303] 30, the MAC address field may be included in the Link info field. The MAC address field or element of each STA may be included in the Per-STA Info.

[0304] 2) Method after Multi-link setup

[0305] 2-1) Initial frame transmission on non-association link

[0306] To trigger frame exchange, an initial frame can be sent over a non-association link. When the transmitter sends an initial request frame, the receiver can respond via an initial response frame (e.g., ACK). The transmitter can be an AP or a non-AP. For example, after multi-link setup, the STA that first gets a channel access opportunity over a non-association link can transmit. For example, a STA that receives an initial frame can know the MAC address of the transmitter STA via the TA (transmitter address) of the initial frame.

[0307] The Initiation Request frame can be defined as a new frame, or can use the existing QoS Data frame, QoS Null frame, etc. The frame sent in the Initial Request frame can include information on the Transmitter MLD and / or information on the Receiver MLD to inform that the corresponding link is available for operation after the multi-link setup.

[0308] FIG. 31 is a diagram illustrating an embodiment of a method for transmitting an initial frame in a non-association link.

[0309] A. Address Setting: The MLD MAC address can be set in the initial frame.

[0310] A-1) Setting the MLD MAC address for the Receiver in the Receiver Address (RA) field: During the multi-link setup process, the Association Request / Response frame contains the ML IE, allowing the MLD MAC addresses of each other to be known, so by including the MLD MAC address of the MLD that is the receiver in the RA, it is possible to notify that the link is currently operational. Additionally, the Source Address (SA) can contain the MLD MAC address of the transmitter MLD to notify that it is the MLD that performed the multi-link setup.

[0311] FIG. 32 is a diagram showing one embodiment of A-1.

[0312] Referring to FIG. 32, when STA2 transmits an initial Request frame on link3, TA can be set to the MAC address of STA2, RA can be set to the AP MLD MAC address, and SA can be set to the MAC address of the non-AP MLD.

[0313] A-2) Setting the Broadcast address in the RA: The Receiver can know the sender's address via the TA, but it is difficult to accurately distinguish whether it is an MLD that has performed a multi-link setup.

[0314] A-3) Setting the Broadcast address in RA and setting the MLD MAC address for the Receiver in Destination Address (DA): This has the same purpose as A-1), but the address setting method is different. Additionally, the Source address (SA) can contain the MLD MAC address of the transmitter MLD to let the MLD know that it is the MLD that performed the multi-link setup.

[0315] FIG. 33 is a diagram showing one embodiment of A-3.

[0316] Referring to FIG. 33, when STA2 sends an initial Request frame on link3, TA can be set to the MAC address of STA2, RA to the Broadcast address, SA to the MAC address of the non-AP MLD, and DA to the AP MLD MAC address.

[0317] A-4) The MLD MAC address of the transmitter MLD and / or receiver MLD can be included in a control field (e.g., the A-control field of a QoS Null / Data frame) in the MAC frame body or MAC header included in the initial frame.

[0318] B. MLD ID setting: The MLD ID can be set in the initial frame.

[0319] B-1) The MLD MAC addresses of the transmitter and receiver set in the address fields presented in A-1), A-2), A-3), and A-4) can also be replaced with MLD IDs that can distinguish the MLDs. For example, when replaced by method A-4), the MLD IDs of the transmitter MLD and / or receiver MLD can be included in the control field (e.g., the A-control field of the QoS Null / Data frame) in the MAC frame body or MAC header included in the initial frame. In the case of the MLD ID included in the address field, the field size is significantly smaller than that of the MLD MAC address, so the number of remaining bits can be increased.

[0320] FIG. 34 is a diagram showing an example of the A-4 case of the B-1 method.

[0321] Referring to FIG. 34, when STA2 sends an Initial Request frame on link3, the A-Control field of the Initial Request frame may include the non-AP MLD ID of STA2, which is the transmitter, and the AP MLD ID of AP4, which is the receiver.

[0322] 2-2) Define additional rules: Non-AP STAs do not transmit frames until they receive a beacon on the non-association link. In other words, they wait until they receive a beacon. Basically, this rule can be applied because the TBTT (target beacon transmission time) information of other APs can be known during the multi-link setup process. For example, in Figure 34, STA2 and STA3 do not transmit frames until they receive a beacon from AP3 and AP2, respectively.

[0323] Upon receiving the link information, the STA MLD can send an association-like request (or initiation) frame on each link, i.e., the STA MLD can exchange additional frames on each link on which it wishes to operate.

[0324] FIG. 35 illustrates one embodiment of a multi-link setup method.

[0325] 35, after receiving information on Links 1 to 4, the STA MLD can request setup for Links 2, 3, and 4 that it wants to operate on, and the AP MLD can respond. The setup request / response can be sent for each link.

[0326] For example, even if the AP MLD has a link set that is STR-enabled, the STA MLD has a non-STR link set. Therefore, the STA MLD can transmit information related to STR-related capabilities when requesting a link.

[0327] FIG. 36 illustrates one embodiment of operations related to link capabilities.

[0328] 36, when using Link 3 and Link 4, the AP MLD should operate in Non-STR, and can operate in STR for other sets. Also, STA1 of the STA MLD can discover the AP MLD via Link 4. Here, the link that STA1 and STA2 of the STA MLD request and whether or not the link has STR capability can affect the link selection by the MLD.

[0329] AP MLD can accept, change, or reject the requested link depending on the STA MLD requested link and whether the link is STR capable. In particular, performance using multi-link may be degraded depending on whether AP MLD is accepted. For example, STA MLD is non-STR on links 1 and 2, but AP can accept it. However, performance may be degraded compared to when all links are STR.

[0330] Based on the above scenario, an example of the negotiation process regarding the STR capability of AP MLD and STA MLD and the requested link is as follows.

[0331] -STA MLD selects Link3, 4 and is non-STR

[0332] FIG. 37 illustrates an embodiment of a link negotiation method.

[0333] 37, the STA MLD can request links 3 and 4, and this link set is a non-STR set for the STA MLD. The AP MLD can simply select links 3 and 4 and respond to the STA MLD.

[0334] -STA MLD selects Link3, 4 and is STR

[0335] FIG. 38 illustrates an embodiment of a link negotiation method.

[0336] 38, the STA MLD can request links 3 and 4, which are link sets for which STR is possible for the STA MLD. If the AP MLD were to directly select links 3 and 4, the performance of the STA MLD may degrade. Therefore, the AP MLD can respond to the STA MLD by selecting links 2 and 3 as the link set.

[0337] Also, if the STA MLD cannot support link2 due to band or other issues, the AP MLD can select only link3 to respond.

[0338] -STR MLD selects link2, 3 and is non-STR

[0339] FIG. 39 illustrates an embodiment of a link negotiation method.

[0340] 39, the STA MLD can request links 2 and 3, and this link set is a non-STR set for the STA MLD. Therefore, the AP MLD can modify / select links 3 and 4 to respond to the STA MLD in order to prevent performance degradation.

[0341] FIG. 40 is a diagram showing an embodiment of a receiving MLD operation.

[0342] Referring to FIG. 40, the receiving MLD may include a first STA and a second STA.

[0343] The receiving MLD includes a first and a second STA (station), the first STA can operate on a first link, and the second STA can operate on a second link.

[0344] The receiving MLD may receive multilink information (S4010). For example, the first STA may receive multilink information including information related to the first and second links from the transmitting MLD. For example, the multilink information may include information related to whether the first link and the second link are a simultaneous transmit and receive (STR) link set or a non-STR link set.

[0345] For example, the transmitting MLD may include a third STA and a fourth STA, and the multilink information may further include information that the first STA and the third STA are communicating, and that the second STA and the fourth STA are communicating.

[0346] The receiving MLD may transmit the multi-link address information (S4020). For example, the first STA may transmit the multi-link address information to the transmitting MLD, and the multi-link address information may include a media access control (MAC) address of the second STA.

[0347] For example, the receiving MLD may further include a third STA, the third STA operating on a third link, the multi-link information may further include information related to the third link, and the multi-link address information may further include a MAC address of the third STA.

[0348] For example, the MAC address of the second STA and the MAC address of the third STA may be included in the multi-link address information in the order of link identifiers of the links on which the second and third STAs operate.

[0349] For example, the MAC address of the second STA and the MAC address of the third STA may be included in the multilink address information in the order of STA IDs (identifiers) of the second and third STAs.

[0350] For example, a STA (i.e., an association link STA) that transmits a management frame (e.g., a probe request / response frame, a beacon frame, an association request / response frame) can transmit the MAC address of another STA (i.e., a non-association link STA) that belongs to the same MLD as itself. This MAC address is recognized by a STA operating on a non-association link to enable frame exchange. Methods including, but not limited to, the following are provided below.

[0351] A. New element or field definition: A new element or field to be included in the management frame can be defined. Basically, the MLD Per-STA MAC address field can be defined as follows:

[0352] For example, AP MLD has link IDs that can distinguish each AP, so it can indicate the MAC addresses of STAs (i.e., APs) operating on non-association links in the order of link IDs. Non-AP MLD can also indicate MAC addresses in the order of STA IDs if STA IDs that can distinguish each STA are defined. Also, a link ID or STA ID can be included before each MAC address for reliable indication.

[0353] For example, a STA that transmits a management frame may not specify the MAC addresses of all STAs that belong to the same MLD as itself. For example, in FIG. 25, STA1 may not transmit the MAC address of STA2. In such a case, the number of STAs (or the number of links (in the case of an AP)) may be additionally specified.

[0354] For example, if it is not an MLD, the corresponding field may not be included, so the MLD address field presented in FIG. 26, which is not a field, may be included in the element.

[0355] B. Multi-link element includes: The MAC address of the STA operating on the non-association link can be included in the common info or per-STA info field of the ML information element (IE).

[0356] For example, the order, names, and sizes of the fields in the format of the Multi-link Element can be changed, and additional fields can exist. Common info can include common information between STAs in the MLD, and specific information for each STA can be included in the Per-STA Profile.

[0357] For example, the MLD Per-STA MAC address field in Fig. 26 can be included in Common Info as in Fig. 29. If the MAC address field exists in Common Info and the MAC address should always be included in the ML IE, the Per-STA Profile is not required. However, since each MAC address is different for each STA, the Per-STA Profile is semantically appropriate.

[0358] For example, the MAC address field may be included in the Link info field. The MAC address field or element of each STA may be included in the Per-STA Info.

[0359] The receiving MLD can transmit data (S4030). For example, each STA of the receiving MLD in which a multi-link has been set up can transmit data via its own link.

[0360] FIG. 41 is a diagram showing an embodiment of a transmission MLD operation.

[0361] Referring to FIG. 41, the receiving MLD may include a first STA and a second STA.

[0362] The transmitting MLD includes a first and a second STA (station), the first STA can operate on a first link, and the second STA can operate on a second link.

[0363] The transmitting MLD may transmit multilink information (S4110). For example, the first STA may transmit multilink information including information related to the first and second links to the receiving MLD. For example, the multilink information may include information related to whether the first link and the second link are a simultaneous transmit and receive (STR) link set or a non-STR link set.

[0364] For example, the receiving MLD may include a third STA and a fourth STA, and the multilink information may further include information that the first STA and the third STA are communicating, and that the second STA and the fourth STA are communicating.

[0365] The sending MLD may receive multi-link address information (S4120). For example, the first STA may receive multi-link address information from a third STA of the receiving MLD, and the multi-link address information may include a media access control (MAC) address of a fourth STA of the receiving MLD. For example, the receiving MLD may include a third STA and a fourth STA. For example, the third STA may operate on a first link, and the fourth STA may operate on a second link.

[0366] For example, the transmitting MLD may further include a fifth STA, the fifth STA operating on a third link, the multi-link information may further include information related to the third link, and the multi-link address information may further include a MAC address of the fifth STA.

[0367] For example, the MAC address of the fourth STA and the MAC address of the fifth STA may be included in the multi-link address information in the order of link identifiers of the links on which the second and fifth STAs operate.

[0368] For example, the MAC address of the fourth STA and the MAC address of the fifth STA may be included in the multilink address information in the order of the STA IDs (identifiers) of the second and third STAs.

[0369] For example, a STA (i.e., an association link STA) that transmits a management frame (e.g., a probe request / response frame, a beacon frame, an association request / response frame) can transmit the MAC address of another STA (i.e., a non-association link STA) that belongs to the same MLD as itself. This MAC address is recognized by a STA operating on a non-association link to enable frame exchange. Methods including, but not limited to, the following are provided below.

[0370] A. New element or field definition: A new element or field to be included in the management frame can be defined. Basically, the MLD Per-STA MAC address field can be defined as follows:

[0371] For example, AP MLD has link IDs that can distinguish each AP, so it can indicate the MAC addresses of STAs (i.e., APs) operating on non-association links in the order of link IDs. Non-AP MLD can also indicate MAC addresses in the order of STA IDs if STA IDs that can distinguish each STA are defined. Also, a link ID or STA ID can be included before each MAC address for reliable indication.

[0372] For example, a STA that transmits a management frame may not specify the MAC addresses of all STAs that belong to the same MLD as itself. For example, in FIG. 25, STA1 may not transmit the MAC address of STA2. In such a case, the number of STAs (or the number of links (in the case of an AP)) may be additionally specified.

[0373] For example, if it is not an MLD, the corresponding field may not be included, so the MLD address field presented in FIG. 26, which is not a field, may be included in the element.

[0374] B. Multi-link element includes: The MAC address of the STA operating on the non-association link can be included in the common info or per-STA info field of the ML information element (IE).

[0375] For example, the order, names, and sizes of the fields in the format of the Multi-link Element can be changed, and additional fields can exist. Common info can include common information between STAs in the MLD, and specific information for each STA can be included in the Per-STA Profile.

[0376] For example, the MLD Per-STA MAC address field in Fig. 26 can be included in Common Info as in Fig. 29. If the MAC address field exists in Common Info and the MAC address should always be included in the ML IE, the Per-STA Profile is not required. However, since each MAC address is different for each STA, the Per-STA Profile is semantically appropriate.

[0377] For example, the MAC address field may be included in the Link info field. The MAC address field or element of each STA may be included in the Per-STA Info.

[0378] The transmitting MLD can receive the data (S4130). For example, each STA of the transmitting MLD in which the multi-link is set up can receive the data via its own link.

[0379] Some of the detailed steps shown in the examples of Figures 40 and 41 are not essential steps and may be omitted. Other steps may be added in addition to the steps shown in Figures 40 and 41, and the order of the steps may be changed. Some of the steps may have their own technical meaning.

[0380] The technical features detailed herein may be applied to various apparatuses and methods. For example, the technical features detailed herein may be implemented / supported via the apparatus of FIG. 1 and / or FIG. 19. For example, the technical features detailed herein may be applied to only a portion of FIG. 1 and / or FIG. 19. For example, the technical features detailed herein may be implemented based on the processing chips 114, 124 of FIG. 1, or based on the processors 111, 121 and memories 112, 122 of FIG. 1, or based on the processor 610 and memory 620 of FIG. 19. For example, in a receiving MLD (multi-link device) apparatus of the present specification, the transmitting MLD includes a first STA (station) and a second STA, the first STA operating on a first link and the second STA operating on a second link, and the apparatus includes a memory; and a processor operably coupled to the memory; the processor may be configured to: cause the first STA to receive multi-link information from the transmitting MLD, the multi-link information including information related to the first and second links; and cause the first STA to transmit multi-link address information to the transmitting MLD, the multi-link address information being configured to include a MAC (media access control) address of the second STA.

[0381] The technical features of the present specification may be embodied based on a computer readable medium (CRM). For example, the CRM proposed by the present specification may store instructions for performing operations including the steps of: in at least one computer readable recording medium including instructions executed by at least one processor of a receiving multi-link device (MLD) of a wireless local area network (WLAN) system, the receiving MLD includes first and second stations (STAs), the first STA operates on a first link, the second STA operates on a second link, the first STA receives multi-link information including information related to the first and second links from a transmitting MLD; and the first STA transmits multi-link address information to the transmitting MLD, the multi-link address information including a media access control (MAC) address of the second STA.

[0382] The instructions stored in the CRM of the present specification may be executed by at least one processor. The at least one processor associated with the CRM of the present specification may be the processors 111 and 121 or the processing chips 114 and 124 of Fig. 1, or the processor 610 of Fig. 19. Meanwhile, the CRM of the present specification may be the memory 112 and 122 of Fig. 1, or the memory 620 of Fig. 19, or a separate external memory / storage medium / disk, etc.

[0383] The technical features of the present specification described above can be applied to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).

[0384] Artificial intelligence refers to the field that studies artificial intelligence or the methodology that can create it, and machine learning refers to the field that defines various problems that are dealt with in the field of artificial intelligence and studies the methodology to solve them. Machine learning can also be defined as an algorithm that improves the performance of any task through continuous experience with that task.

[0385] An artificial neural network (ANN) is a model used in machine learning, and can refer to any model with problem-solving capabilities that is composed of artificial neurons (nodes) that form a network through synaptic connections. An artificial neural network can be defined by the connection pattern between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.

[0386] An artificial neural network can have an input layer, an output layer, and optionally one or more hidden layers. Each layer can include one or more neurons, and an artificial neural network can include synapses connecting the neurons. In an artificial neural network, each neuron can output a function value of an activation function for an input signal, weights, and biases input via a synapse.

[0387] Model parameters are parameters that are determined through learning, and include weights of synaptic connections and biases of neurons, etc. Hyperparameters are parameters that must be set before learning in a machine learning algorithm, and include the learning rate, number of iterations, mini-batch size, initialization function, etc.

[0388] The objective of training an artificial neural network can be regarded as determining model parameters that minimize a loss function. The loss function can be used as an index for determining optimal model parameters during the training process of an artificial neural network.

[0389] Depending on the learning method, machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning.

[0390] Supervised learning refers to a method of training an artificial neural network when a label for training data is given, and the label can mean the correct answer (or result value) that the artificial neural network should infer when training data is input to the artificial neural network. Unsupervised learning can mean a method of training an artificial neural network when no label for training data is given. Reinforcement learning can mean a learning method of training an agent defined in an environment to select an action or action sequence that maximizes cumulative compensation in each state.

[0391] Machine learning realized by a deep neural network (DNN) with multiple hidden layers in an artificial neural network is sometimes called deep learning, and deep learning is a part of machine learning. In the following, machine learning is used to include deep learning.

[0392] Furthermore, the above-described technical features can be applied to wireless communication of a robot.

[0393] A robot can mean a machine that automatically processes or operates a given task using its own capabilities. In particular, a robot that has the ability to recognize the environment and make its own decisions and take action can be called an intelligent robot.

[0394] Robots can be classified into industrial, medical, domestic, military, etc., depending on the purpose and field of use. Robots can perform various physical actions such as moving robot joints by having a driving part with an actuator or a motor. In addition, a mobile robot can run on the ground or fly in the air by using a driving part that includes wheels, brakes, propellers, etc.

[0395] Furthermore, the above-described technical features can be applied to a device that supports augmented reality.

[0396] Augmented reality is a collective term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides real-world objects and backgrounds only as CG images, AR technology provides virtual CG images on real-world images, and MR technology is a computer graphics technology that combines and presents virtual objects in the real world.

[0397] MR technology is similar to AR technology in that it displays both real and virtual objects, but it differs in that AR technology uses virtual objects to complement real objects, whereas MR technology uses virtual objects and real objects with equal characteristics.

[0398] XR technology can be applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and a device to which XR technology is applied can be called an XR device.

[0399] The claims and the like described in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to be realized as an apparatus, and the technical features of the apparatus claims of this specification may be combined to be realized as a method. In addition, the technical features of the method claims and the technical features of the apparatus claims of this specification may be combined to be realized as an apparatus, and the technical features of the method claims and the technical features of the apparatus claims of this specification may be combined to be realized as a method.

Claims

1. 1. A method in a wireless local area network (WLAN) system, comprising: A first station (STA) of a receiving MLD (multi-link device) receives an association request frame including multi-link information from a transmitting MLD, the receiving MLD including the first STA and a second STA, the first STA operates on a first link, the second STA operates on a second link, and the multi-link information includes information related to the first link and the second link; The multilink information further includes a multilink control field, a common info field contiguous with the multilink control field, and a link info field contiguous with the common info field, the common info field including an MLD Media Access Control (MAC) address field of the transmitting MLD, the multilink control field including an MLD MAC address present field associated with the presence of the MLD MAC address field, and the link info field including a MAC address field of each STA; The multilink information further includes information related to whether the first link and the second link are consecutive transmit and receive, a STR link set, or a non-STR link set; and a step of the first STA of the receiving MLD sending an association response frame including multi-link address information to the transmitting MLD, the multi-link address information including a media access control (MAC) address of the second STA.

2. The method of claim 1 , wherein the information relating to whether the first link and the second link are the STR link set or the non-STR link set is configured as one-bit information.

3. 2. The method of claim 1, wherein the Link Info field further comprises a Link ID field for the first link, the Link ID field having a length of 4 bits.

4. A receiving multi-link device (MLD) in a wireless local area network (wireless LAN) system, A first STA (station); A second STA is included, the first STA operates on a first link and the second STA operates on a second link; The first STA, receiving an association request frame including multilink information including information related to the first link and the second link from a transmitting MLD; The multilink information further includes a multilink control field, a common info field contiguous with the multilink control field, and a link info field contiguous with the common info field, the common info field including an MLD Media Access Control (MAC) address field of the transmitting MLD, the multilink control field including an MLD MAC address present field associated with the presence of the MLD MAC address field, and the link info field including a MAC address field of each STA; The multilink information further includes information related to whether the first link and the second link are consecutive transmit and receive, a STR link set, or a non-STR link set; Transmitting an association response frame including multilink address information to the transmitting MLD; The multi-link address information includes a media access control (MAC) address of the second STA.

5. The receiving MLD of claim 4 , wherein information relating to whether the first link and the second link are the STR link set or the non-STR link set is configured as 1-bit information.

6. 5. The receive MLD of claim 4, wherein the Link Info field further includes a Link ID field for the first link, the Link ID field having a length of 4 bits.

7. 1. A method in a wireless local area network (WLAN) system, comprising: A step of transmitting an association request frame including multi-link information from a first STA (station) of a transmitting MLD (multi-link device) to a third STA of a receiving MLD, the transmitting MLD including the first STA and a second STA, the first STA operating on a first link, the second STA operating on a second link, and the multi-link information including information related to the first link and the second link; The multilink information further includes a multilink control field, a common info field contiguous with the multilink control field, and a link info field contiguous with the common info field, the common info field including an MLD Media Access Control (MAC) address field of the transmitting MLD, the multilink control field including an MLD MAC address present field associated with the presence of the MLD MAC address field, and the link info field including a MAC address field of each STA; The multilink information further includes information related to whether the first link and the second link are consecutive transmit and receive, a STR link set, or a non-STR link set; and receiving an association response frame including multi-link address information from the third STA of the receiving MLD by the first STA of the transmitting MLD, the multi-link address information including a media access control (MAC) address of a fourth STA of the receiving MLD.

8. The method of claim 7 , wherein the information relating to whether the first link and the second link are the STR link set or the non-STR link set is configured as one-bit information.

9. 8. The method of claim 7, wherein the Link Info field further comprises a Link ID field for the first link, the Link ID field having a length of 4 bits.

Images