Method and apparatus for performing negotiation for c-TDMA operation in multi-AP communication in wireless LAN system

Abstract

Proposed are a method and an apparatus for performing negotiation for a C-TDMA operation in multi-AP communication in a wireless LAN system. Specifically, a first AP transmits a coordination request frame to a second AP. The first AP receives a coordination response frame from the second AP. The first AP receives allocation information of a part of a TXOP on the basis of the coordination request frame and the coordination response frame. The first AP exchanges frames with a first non-AP STA during the part of the TXOP.

Description

Method and device for performing negotiation for C-TDMA operation in MULTI-AP communication in a wireless LAN system

[0001] This specification relates to a technique for performing negotiation for C-TDMA operation in multi-AP communication in a wireless LAN system, and more specifically, to a method and device for defining and exchanging information required for negotiation between multiple APs.

[0002] Wireless local area networks (WLANs) 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 communications standard. For example, the new communications standard could be the Extreme High Throughput (EHT) standard, which is currently under discussion. The EHT standard could utilize newly proposed increased bandwidth, an improved PHY layer protocol data unit (PPDU) structure, improved sequences, and the Hybrid Automatic Repeat Request (HARQ) technique. The EHT standard could also be referred to as the IEEE 802.11be standard.

[0004] New wireless LAN standards may allow for an increased number of spatial streams. This may necessitate improvements to signaling techniques within the wireless LAN system to properly utilize these increased spatial streams.

[0005] This specification proposes a method and device for performing negotiation for C-TDMA operation in multi-AP communication in a wireless LAN system.

[0006] An example of this specification proposes a method for performing negotiation for C-TDMA operation in multi-AP communication.

[0007] The present embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0008] This embodiment is performed in a first AP, and the first AP and the second AP may be configured as a shared AP or a sharing AP after the cooperation phase in multi-AP communication. The first non-AP STA of this embodiment may correspond to at least one STA (station).

[0009] This embodiment proposes a method for performing inter-AP negotiation to perform C-TDMA operation in multi-AP (Access Point) communication (or multi-AP operation). In particular, this embodiment proposes a method for defining information required for negotiation to perform C-TDMA operation. Furthermore, this embodiment is not limited to the C-TDMA technique, and other coordinated multi-AP techniques such as C-SR and CBF may be applied.

[0010] The first AP (access point) transmits a coordination request frame to the second AP.

[0011] The first AP receives a cooperation response frame from the second AP.

[0012] The first AP receives allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame.

[0013] The first AP exchanges frames with the first non-AP STA (station) during a portion of the TXOP.

[0014] The above cooperation request frame includes negotiation information for cooperation between the plurality of APs. The cooperation response frame includes information regarding a response or rejection to the cooperation request frame based on the negotiation information.

[0015] After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information. The first non-AP STA is a non-AP STA within the BSS of the first AP. That is, at the time of performing the negotiation procedure based on the cooperation request frame and the cooperation response frame, the roles of the first and second APs as Sharing APs or Shared APs may not be determined. After the negotiation procedure is completed and a specific AP obtains the TXOP, the AP can function as a Sharing AP, and the AP that is allocated or shared with resources such as the TXOP can function as a Shared AP.

[0016] That is, the present embodiment proposes a method for performing negotiations between multiple APs to implement a transmission technique for cooperation between multiple APs (or cooperation between APs in a multi-AP environment). Furthermore, the present embodiment proposes a method for defining information to be exchanged between the multiple APs during the negotiation process.

[0017] According to the embodiment proposed in this specification, APs that have successfully cooperated based on the proposed negotiation information can perform a coordinated multi-AP technique such as C-TDMA. In addition, based on the proposed negotiation information, the Sharing AP can share a TXOP with the Shared AP, and through this, the Shared AP can perform frame exchange with a non-AP STA (or UHR non-AP STA) within its BSS during the allocated TXOP. In addition, by proposing a negotiation method to effectively perform communication between multiple APs, it is possible to perform appropriate scheduling between each AP, and thereby, it is possible to expect an increase in the overall network throughput.

[0018] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0019] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0020] Figure 3 is a diagram illustrating a general link setup process.

[0021] Figure 4 illustrates one embodiment of a multi-link (ML).

[0022] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0023] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.

[0024] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0025] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.

[0026] Figure 9 shows the operation according to UL-MU.

[0027] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0028] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0029] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0030] FIG. 13 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0031] Figure 14 illustrates operation according to a conventional STX operation.

[0032] Figure 15 illustrates an example of C-OFDMA (Coordinated OFDMA).

[0033] Figure 16 illustrates an example of CBF (Coordinated beamforming).

[0034] Figure 17 illustrates an example of AP selection.

[0035] Figure 18 shows an example of JTX / JT.

[0036] Figure 19 shows an example of the operation of a 2-day MU-RTS TXS trigger frame with a value of the TXOP Sharing Mode subfield.

[0037] Figure 20 shows an example of coordinated TDMA operation including the negotiation process.

[0038] Figure 21 shows an example of C-TDMA operation according to pair-to-pair based negotiation including UHR STA support information.

[0039] Figure 22 shows an example of C-TDMA operation according to Broadcast based Negotiation including UHR STA support information.

[0040] Figure 23 illustrates an example of a PPDU of this specification.

[0041] Figure 24 illustrates a procedure for performing negotiation required for a transmitting device according to the present embodiment to perform C-TDMA operation.

[0042] Figure 25 illustrates a procedure for performing negotiation required for a receiving device according to the present embodiment to perform C-TDMA operation.

[0043] Fig. 26 illustrates a transmitting device that performs negotiation necessary to perform C-TDMA operation according to the present embodiment.

[0044] Fig. 27 illustrates a receiving device that performs negotiation necessary to perform C-TDMA operation according to the present embodiment.

[0045] Figure 28 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0046] Fig. 29 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0047] Figure 30 is a flowchart illustrating a procedure for performing negotiation to perform C-TDMA operation on the Sharing AP side according to the present embodiment.

[0048] FIG. 31 is a flowchart illustrating a procedure for performing negotiation to perform C-TDMA operation on the Shared AP side according to the present embodiment.

[0049] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

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

[0051] In this specification, “at least one of A and B” can mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” can be interpreted identically to “at least one of A and B.”

[0052] In addition, parentheses used in this specification may mean “for example.” Specifically, when “control information (UHR-Signal field)” is indicated, the “UHR-Signal field” may be suggested as an example of “control information.” In other words, the “control information” in this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be suggested as an example of “control information.” In addition, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be suggested as an example of “control information.”

[0053] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”

[0054] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”

[0055] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0056] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to wireless local area network (WLAN) systems. For example, the present specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification can be applied to the Ultra High Reliability (UHR) standard or the next-generation wireless LAN standard that enhances IEEE 802.11bn. In addition, the examples of this specification can be applied to mobile communication systems. For example, the examples of this specification can be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on the 3rd Generation Partnership Project (3GPP) standard.

[0057] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0058] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0059] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present specification may also be referred to by 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) of the present specification may also be referred to by 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) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

[0060] For example, STA (110, 120) may perform the role of an AP (access point) or a non-AP role. That is, STA (110, 120) of the present specification may perform the functions of an AP and / or a non-AP. In the present specification, AP may also be indicated as an AP STA.

[0061] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (Self-Driving, Autonomous-Driving).

[0062] In this specification, STA (110, 120) may include a medium access control (MAC) and a physical layer interface for a wireless medium that follow the provisions of the IEEE 802.11 standard.

[0063] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0064] 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 as separate chips, or at least two blocks / functions may be implemented through a single chip.

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

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

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

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

[0069] For example, in the specification below, the operation of a device indicated as AP may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is an AP, the operation of the device indicated as AP may be controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). In addition, control information related to the operation of the AP or a transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110). In addition, when the second STA (110) is an AP, the operation of the device indicated as an AP is controlled by the processor (121) of the second STA (120), and a related signal can be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signal of the AP can be stored in the memory (122) of the second STA (110).

[0070] For example, in the specification below, the operation of a device indicated as a non-AP (or User-STA) may be performed in the 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 a non-AP may be controlled by the processor (121) of the second STA (120), and a related signal may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal 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 a device indicated as a non-AP is controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110).

[0071] In the following specification, devices called (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 STA (110, 120) of 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 drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. In addition, in the example below, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation that generates a transmission / reception signal or performs data processing or operation in advance for a transmission / reception signal may include 1) an operation of determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation of determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation of determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.

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

[0073] For example, the transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the transceiver illustrated in sub-drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) illustrated in sub-drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (a) of FIG. 1 described above.

[0074] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, Base Station, Node-B, Access Point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

[0075] For example, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal being received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1 being acquired by a processor (111, 121) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 being acquired by a processing chip (114, 124) illustrated in sub-drawing (b) of FIG.

[0076] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the 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 various programming languages.

[0077] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated 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 processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM 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.

[0078] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.

[0079] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0080] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0081] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0082] Referring to the top of FIG. 2, the wireless LAN 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 have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).

[0083] A BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.

[0084] A distributed system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS, 240). An ESS (240) can be used as a term to indicate a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) can have the same SSID (service set identification).

[0085] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0086] In a BSS such as the upper part 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 implemented. However, it may also be possible to establish a network and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0087] The bottom of Figure 2 is a conceptual diagram showing IBSS.

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

[0089] Figure 3 is a diagram illustrating a general link setup process.

[0090] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning by the STA. That is, for the STA to access the network, it must find a network it can join. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0091] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist in the vicinity while moving between channels and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits the beacon frame, so the AP becomes the responder. In an IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not constant. For example, an 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 and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0092] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

[0093] An STA that discovers a network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

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

[0095] An STA can transmit an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

[0096] A successfully authenticated STA may 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 the AP transmits an association response frame to the STA in response. For example, the association request frame may include information related to various capabilities, such as a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may contain information related to various capabilities, status codes, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise Indicator (RSNI), mobility domains, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS maps, etc.

[0097] In step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0098] Figure 4 illustrates one embodiment of a multi-link (ML).

[0099] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0100] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the second link may be configured in different bands.

[0101] The AP MLD of FIG. 4 includes three affiliated APs. In the example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In the example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Furthermore, in the example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Furthermore, in the example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.

[0102] In the example of FIG. 4, AP1 may initiate a multi-link setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In the example of FIG. 4, non-AP STA1 may transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the AP illustrated in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the STA (i.e., user-STA or non-AP STA) illustrated in FIG. 1 and / or FIG. 2.

[0103] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.

[0104] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0105] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.

[0106] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.

[0107] In FIG. 5, L-STF or UHR-LTF may be called a preamble or physical preamble, and may be generated / transmitted / received / acquired / decoded in the physical layer (included in the transmitting / receiving STA).

[0108] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.

[0109] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.

[0110] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0111] The L-SIG field of FIG. 5 may include, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4 bit Rate field, a 1 bit Reserved bit, a 12 bit Length field, a 1 bit Parity bit, and a 6 bit Tail bit. For example, the 12 bit Length field may include information about 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 (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU or UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High-Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0112] For example, (non-AP and AP) STAs can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in 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 excluding the pilot subcarriers {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 indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0113] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.

[0114] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be called by various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, the common control field, and the common control signal.

[0115] A U-SIG can contain N bits of information and can include information for identifying the type of EHT PPDU. For example, a U-SIG can be formed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., an OFDM symbol) for a U-SIG can have a duration of 4 microseconds. Each symbol of a U-SIG can be used to transmit 26 bits of information. For example, each symbol of a U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0116] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can 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 can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols allocated to each U-SIG symbol. A single 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.

[0117] For example, A bit information (e.g., 52 uncoded bits) transmitted by 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 through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits excluding the CRC / tail field within the second symbol, and may be generated based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder and may be set to, for example, "000000".

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

[0119] 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 and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

[0120] In other words, when the (AP / non-AP) STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. In other words, the receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is an UHR PPDU based on the PHY version identifier having the second value.

[0121] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field relates to UL communication, and the second value of the UL / DL flag field relates to DL communication.

[0122] For example, the version-independent bits of U-SIG may include information about the length of a transmission opportunity (TXOP) and information about the BSS color ID.

[0123] For example, if a UHR PPDU is classified into various types (e.g., a type related to SU transmission (performed based on UL or DL), a type related to DL transmission, a type related to NDP transmission, a type related to DL non-MU-MIMO, a type related to DL MU-MIMO, a type related to Multi-AP operation, a type related to CBF (Coordinated beamforming), SR (Spatial Reuse), a type related to C-OFDMA (Coordinated OFDMA), a type related to C-TDMA (Coordinated TDMA)), information about the type of the EHT PPDU (e.g., 2-bit or 3-bit information) can be included in the version-dependent bits of the U-SIG.

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

[0125] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth 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 within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

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

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

[0128] For example, U-SIG and UHR-SIG may include information regarding 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 the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).

[0129] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).

[0130] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth can contain different U-SIGs.

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

[0132] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

[0133] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on RUs (resource units) defined by multiple subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.

[0134] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.

[0135] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.

[0136] Meanwhile, the RU arrangement of FIG. 6 is utilized not only in a situation for multiple users (MUs) but also in a situation for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of FIG. 4, in which case three DC tones can be inserted.

[0137] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.

[0138] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0139] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0140] Additionally, as illustrated, 484 RUs may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.

[0141] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.

[0142] Figure 9 illustrates an operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can perform channel access through contending (i.e., backoff operation) and transmit a trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU including a trigger frame (930). When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

[0143] TB PPDUs (941, 942) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (930). The ACK frame (950) for the TB PPDU can be implemented in various forms.

[0144] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

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

[0146] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 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 indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of the channel indices and center frequencies may change.

[0147] Figure 10 exemplarily illustrates four channels within the 2.4 GHz band. The illustrated first frequency region (1010) to fourth frequency region (1040) may each include one channel. For example, the first frequency region (1010) may include channel 1 (a 20 MHz channel having an index of 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0148] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0149] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz 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 figures shown in FIG. 11 are subject to change.

[0150] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency ranges called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.

[0151] Within the 5 GHz band, multiple channels can be configured, and the bandwidth of each channel can be variously configured, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel through a 160 MHz frequency domain.

[0152] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0153] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.

[0154] For example, the 20 MHz channel of Fig. 12 can be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of Fig. 12 can have an index of 1 (or channel index, channel number, etc.), and a center frequency of 5.945 GHz can be assigned. That is, the center frequency of the index N channel can be determined as (5.940 + 0.005*N) GHz.

[0155] Accordingly, the indexes (or channel numbers) of the 20 MHz channels of FIG. 12 are 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, It can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule mentioned above, the indices of the 40 MHz channels in Fig. 12 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.

[0156] FIG. 13 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0157] The devices (e.g., AP STA, non-AP STA) illustrated in FIGS. 1 to 4 may be modified as illustrated in FIG. 13. The transceiver (630) of FIG. 13 may be identical to the transceivers (113, 123) of FIG. 1. The transceiver (630) of FIG. 13 may include a receiver and a transmitter.

[0158] The processor (610) of FIG. 13 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 13 may be identical to the processing chip (114, 124) of FIG. 1.

[0159] The memory (150) of FIG. 13 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 13 may be a separate external memory different from the memory (112, 122) of FIG. 1.

[0160] Referring to FIG. 13, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0161] Referring to FIG. 13, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).

[0162] Below, the Multi-AP operation applied to this specification is described.

[0163] The above Multi-AP operation refers to a communication technique related to multiple APs in a WLAN. For example, the Multi-AP operation may refer to an operation in which one or more APs transmit and receive information to one or more STAs. In contrast to the Multi-AP operation, existing techniques may be expressed by various terms such as STX (Single Transmission). For example, the STX operation may refer to a method in which one BSS AP performs communication with one BSS STA. When communication is performed based on the STX operation, interference with adjacent APs (e.g., APs located in an overlapping BSS) may occur. Due to such interference, a problem in which the transmission and reception performance of cell-edge users (e.g., non-AP STAs located at the edge of the BSS) is reduced may occur.

[0164] Figure 14 illustrates operation according to a conventional STX operation. As illustrated, interference between STA and AP may occur due to adjacent AP1 and AP2.

[0165] To improve the above STX operation, a new Multi-AP operation is proposed. The Multi-AP operation may be based on a technology that reduces various interferences, such as Inter-Symbol Interference (ISI), through coordination with neighboring APs (e.g., APs located in overlapping BSSs).

[0166] In Fig. 14, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS (Overlapping Basic Service Set). That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0167] For example, the Multi-AP operation can be classified into various technologies / types / formats / protocols, etc. For example, the Multi-AP operation can include Coordinated TDMA (C-TDMA) that distinguishes wireless resources allocated to multiple APs based on a time axis (time domain). Additionally or alternatively, the Multi-AP operation can include Coordinated OFDMA (C-OFDMA) that distinguishes wireless resources allocated to multiple APs based on a frequency axis (time domain). Additionally or alternatively, the Multi-AP operation can include Coordinated Spatial Reuse (C-SR) that applies Spatial Reuse (SR) to at least one AP. Additionally or alternatively, the Multi-AP operation can include Coordinated beamforming (CBF) / nulling that nulls and transmits interference generated from neighbors (e.g., adjacent APs / STAs, and / or OBSS APs / OBSS STAs). Additionally or alternatively, the Multi-AP operation may include AP selection in which an AP with a good channel condition among neighboring APs (e.g., at least one AP located within a BSS or OBSS and with a good channel condition) transmits. Additionally or alternatively, the Multi-AP operation may include Joint Transmission (JTX) or JT in which multiple APs (e.g., multiple APs included in the same BSS / OBSS, or multiple APs included in different BSS / OBSS) cooperate to perform simultaneous transmission and reception, and JTX / JT may be implemented based on Joint Beamforming or Joint MU-MIMO.

[0168] FIG. 15 illustrates an example of Coordinated OFDMA (C-OFDMA). The illustrated AP1 may transmit a PPDU / signal to STA1, and AP2 may transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 may be performed in the same / overlapping time intervals. Transmission from AP1 to STA1 may be performed based on a first frequency band, and transmission from AP2 to STA2 may be performed based on a second frequency band different from the second frequency band. For example, in FIG. 15, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0169] Although not illustrated in Figure 15, an example of Coordinated TDMA (C-TDMA) is also possible. For example, the acquired TXOP can be divided into specific time units (e.g., slots), and the divided slots can be sequentially assigned to multiple different APs.

[0170] The above-described example of C-OFDMA can be further modified as follows. For example, an AP (e.g., AP1) that has acquired a TXOP can share frequency resources with at least one AP in the vicinity (e.g., AP2 existing in the BSS / OBSS). For example, the shared frequency resources can be defined in units of RU (resource units) or subchannels, and for example, frequency resources can be shared by AP1 to AP2 in units of 20 / 40 / 80 MHz subchannels or 242 / 484 / 996-tone RUs for flexibility.

[0171] AP1, which performs C-OFDMA, can act as a sharing AP or a master AP. That is, AP1 can request at least one AP in its vicinity (e.g., AP2 in the BSS / OBSS) to report information about the channel and / or buffer status. Based on this, AP1 can obtain a TXOP and share a portion of its frequency resources (e.g., a 20 MHz subchannel or a RU of a specific size) with at least one AP in its vicinity (e.g., AP2 in the BSS / OBSS) within all or part of the time interval associated with the TXOP.

[0172] Figure 16 illustrates an example of Coordinated Beamforming (CBF). In the illustrated example, AP1 may transmit a PPDU / signal to STA1, and AP2 may transmit a PPDU / signal to STA2. Transmissions from AP1 and AP2 may be performed in the same / overlapping time intervals. Transmissions from AP1 and AP2 may be performed through the same / overlapping frequency bands. In order to reduce interference caused to STA2 by AP1, AP1 may perform nulling / beamforming toward STA2, and in order to reduce interference caused to STA1 by AP2, AP2 may perform nulling / beamforming toward STA1. For example, such nulling / beamforming may be implemented in a manner of positioning a radiation null toward a neighboring unassociated STA. The above-described nulling / beamforming may make a specific AP invisible to neighboring unassociated STAs. For example, the above-described nulling / beamforming may make AP1 (or AP2) invisible to STA2 (or STA1).

[0173] For example, in FIG. 16, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0174] Although not shown in FIG. 16, control signals (e.g., coordination frames) for nulling / beamforming between AP1 and STA2 and / or nulling / beamforming between AP2 and STA1 may be transmitted and received over the backhaul link between AP1 and AP2.

[0175] Figure 17 illustrates an example of AP selection. The illustrated AP2 is determined to have a better channel condition than AP1. AP1 transmits its data / signal to AP2 via a backhaul link, and AP2, instead of AP1, can transmit a signal to STA1. For example, in Figure 17, STA1 and AP1 may be included in the BSS, and STA2 and AP2 may be included in the OBSS. In other words, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0176] Figure 18 illustrates an example of JTX / JT. The illustrated AP1 can transmit to STA1 together with AP2. For example, the PPDU / signal transmitted from AP2 to STA1 may be all or part of the same as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be simultaneously transmitted through the same / overlapping frequency band as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be a signal transmitted from AP1 through a backhaul link. For example, in Figure 18, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0177] More specifically, in FIG. 18, AP1 can transmit a coordination request (or can be named variously, such as a first request, a control request, etc.) to AP2 and receive a coordination response (or can be named variously, such as a first response, a control response, etc.) from AP2. Through the exchange of the request / response, information about coordination between AP1 and AP2 (e.g., information about whether AP1 and AP2 will perform simultaneous transmission to STA1), information about the point in time when coordination starts, information about the point in time when AP1 and AP2 start simultaneous transmission to STA1, information about data shared between AP1 and AP2, etc. can be exchanged. AP1 can share its data with AP2 via the backhaul link. Thereafter, AP1 can transmit a coordination trigger frame (or can be named variously, such as a trigger frame) to AP2 and perform simultaneous transmission to STA1 based on the trigger frame.

[0178] <Embodiments applicable to this specification>

[0179] To enable terminals to maintain continuous WLAN connectivity over a wider area, numerous APs are being installed adjacent to each other. However, overlapping BSSs of multiple APs can lead to issues such as radio interference and transmission collisions between APs. To address these issues, various technologies have been proposed to coordinate APs across frequency, time, and spatial domains (e.g., RU selection, joint transmission, nulling, etc.). Furthermore, attention should be paid to the various issues that can arise during inter-AP cooperation.

[0180] In EHT (802.11be), a technology was proposed to allocate some time within the TXOP acquired by the AP to support peer-to-peer (P2P) transmission to non-AP STAs. To this end, a new TXOP Sharing Mode subfield was defined in the Common Info field of the existing MU-RTS Trigger frame, and the MU-RTS (Multi User-Request To Send) Trigger frame when this value is nonzero is referred to as an MU-RTS TXOP Sharing (TXS) Trigger frame (TF). If the value of the TXOP Sharing mode is 1, the non-AP STA supports one or more (non-TB) PPDU transmissions to the AP, and if the value of the TXOP Sharing mode is 2, the non-AP STA supports P2P transmission in addition to (non-TB) PPDU transmissions to the AP.

[0181] Figure 19 shows an example of the operation of a 2-day MU-RTS TXS trigger frame with a value of the TXOP Sharing Mode subfield.

[0182] Fig. 19 shows an example of operation when the TXOP Sharing mode value is 2. When the AP transmits an MU-RTS TXS TF including time allocation information (Time allocated in MU-RTS TXS Trigger Frame of Fig. 19) to non-AP STA 1, non-AP STA 1 can perform P2P transmission to non-AP STA 2 after responding with CTS (Clear-To-Send).

[0183] Figure 20 shows an example of coordinated TDMA operation including the negotiation process.

[0184] Meanwhile, if the existing Triggered TXOP Sharing protocol is utilized for multi-AP coordination, frame exchange can be performed without affecting each other by dividing the transmission within the BSS of each cooperative AP by time unit. That is, FIG. 20 shows an example of Coordinated-Time Division Multiplexing Access (C-TDMA) according to the time unit among the cooperation methods between cooperative APs. At this time, the AP in the existing Triggered TXS protocol can play the role of an AP that shares TXOP in the multi-AP coordination operation, and the STA in the existing Triggered TXS protocol can play the role of an AP that shares TXOP in the multi-AP coordination operation. In this specification, an AP that shares TXOP is referred to as a Sharing AP (SAP), and an AP that receives TXOP from an SAP is referred to as a Shared AP (DAP). Here, the SAP that shares TXOP is not limited to only AP STAs, and may also include non-AP STAs that share TXOP. Additionally, the DAPs that share TXOPs are not limited to AP STAs, and may also include non-AP STAs that share TXOPs (or transmit and receive with AP STAs that share TXOPs). Furthermore, frame exchanges with non-AP STAs or SAPs belonging to the DAP BSS during the time allocated to the DAP are referred to as BSS frame exchanges (FEs) of the DAP.For example, frame exchange may be performed by transmitting data frames and responding to block ACK frames following RTS / CTS frame exchange between a DAP and a non-AP STA, transmitting UL data frames by non-AP STAs in response to a trigger frame transmitted from the DAP, or transmitting data frames by the DAP in response to a trigger frame transmitted from the SAP.

[0185] Basically, for Multi-AP cooperation to occur between two APs, they must be in a connected / joined state, or after exchanging their capabilities and requirements in advance (i.e., negotiation), Multi-AP cooperation technology (e.g., C-TDMA, C-OFDMA, C-SR, etc.) can be performed based on the acquired information. In other words, for the C-TDMA operation considered in this specification to be performed smoothly, negotiation for C-TDMA operation must occur in advance between the SAP and DAP described above. However, the negotiation process for C-TDMA operation between APs and the information required for the negotiation have not yet been defined. In addition, C-TDMA, which can be newly defined / applied in UHR, requires various rules and signaling to be defined / added depending on whether it supports legacy devices, whereas relatively little signaling may be required if it only supports UHR devices. Alternatively, a separate spec change may not be required.

[0186] Therefore, this specification defines not only the basic information required during the negotiation process between APs prior to C-TDMA operation in a multi-AP cooperative environment, but also additional information that can be used for negotiation between APs that only support UHR non-AP STAs. Furthermore, it presents the negotiation procedure for exchanging the defined information.

[0187] The negotiation process proposed in this specification enables each AP to perform C-TDMA operations and, based on the information acquired during the negotiation process, seamlessly exchange frames with UHR non-AP STAs. The specific designations (names) proposed in this specification are subject to change and are not limited to one.

[0188] That is, this specification defines information for indicating whether UHR STA is supported in the process of negotiating to perform coordinated TDMA between APs in a multi-AP environment, and describes how the information is negotiated.

[0189] 1. How to define the negotiation procedure and necessary information required for APs to perform C-TDMA operations in a multi-AP environment.

[0190] This specification defines the negotiation procedures required for APs to perform C-TDMA operations in a multi-AP environment, as well as the information that must be exchanged between APs during this negotiation process. Specifically, Section 1.1 defines the negotiation information exchanged between APs, and Section 1.2 presents the inter-AP negotiation procedure for exchanging the defined information. Furthermore, Section 1.3 presents an example of C-TDMA operation.

[0191] 1.1 Inter-AP negotiation information to support UHR STA in C-TDMA

[0192] This section describes the information that APs participating in C-TDMA must exchange through pre-negotiation. Furthermore, this section describes the information that APs must exchange in a multi-AP environment when they support C-TDMA only to UHR non-AP STAs.

[0193] The negotiation information according to the present disclosure can be used by each AP to operate in C-TDMA, and can also operate based on this when exchanging frames with each non-AP STAs (or UHR non-AP STAs). For example, the negotiation information according to the present specification allows the AP that first acquires the TXOP to act as an SAP to determine the length of the TXOP duration to share with the DAP, and to match the operating bandwidth and channel between each AP for smooth cooperation. In addition, by specifying / indicating that the AP participating in C-TDMA is an AP or BSS that only supports UHR non-AP STAs, the sharing AP that shares the TXOP with the corresponding AP may not require additional rules or signaling.

[0194] The information defined below can be included in Coordination Request / Response frames (e.g., SCS request / response, A-Control field) exchanged during negotiation between APs participating in multi-AP cooperation and transmitted individually from each AP. It is assumed that the coordination request and response frames can be defined as new frames or as new elements to be transmitted together with existing request and response frames.

[0195] 1) coordination request frame

[0196] The coordination request frame transmitted during the negotiation process for C-TDMA proposed in this specification may include negotiation information based on one or more combinations of A to H below.

[0197] A. Multi-AP group ID: ID for the set of APs that constitute multi-AP coordination (e.g., 0, 1, 2, ...)

[0198] B. Multi-AP ID: ID assigned from AP within the configured Multi-AP group (e.g., 0, 1, 2, ...)

[0199] C. Multi-AP coordination type: Information on multi-AP cooperative transmission techniques such as C-OFDMA, C-TDMA, J-TX, and C-SR.

[0200] D. Operating channel: Information on the primary and punctured channels in operation.

[0201] -> For example, common channel information for smooth cooperation between APs participating in C-TDMA

[0202] -> For example, primary channel information on which APs participating in C-TDMA can operate in common

[0203] Specifically, the Operating channel can be defined as a new field that plays the role of the CCSF0 field in the EHT Operation Information field to indicate the channel center frequency index for the 20 / 40 / 80 MHz channel.

[0204] Specifically, the Operating channel can be defined as a new field that plays the role of the CCSF0 field in the EHT Operation Information field to indicate the channel center frequency for the primary 80 MHz channel of a 160 MHz channel or the channel center frequency for the primary 160 MHz channel of a 320 MHz channel.

[0205] Additionally, the Operating channel can be defined as a new field that plays the role of the CCSF1 field in the EHT Operation Information field to indicate the channel center frequency for a 160 MHz channel or the channel center frequency for a 320 MHz channel.

[0206] -> For example, punctured channel information of an AP participating in C-TDMA

[0207] Specifically, the Operating channel can be defined as a new field that serves as the Disabled Subchannel Bitmap field in the EHT Operation Information field, and the equipped 20 MHz subchannel can be indicated using a bitmap.

[0208] Ex) A bit value of 0 in the bitmap indicates that the corresponding 20 MHz subchannel is not punctured / A bit value of 1 in the bitmap indicates that the corresponding 20 MHz subchannel is punctured

[0209] -> The primary channel of DAP can be included within the channel where SAP operates.

[0210] -> DAP's primary channel can be included within the operating channel excluding SAP's punctured channel.

[0211] E. Operating bandwidth: Operating bandwidth and maximum bandwidth information

[0212] -> For example, BW information that operates in common for smooth cooperation between APs participating in C-TDMA.

[0213] Specifically, the operating channel and primary channel information described above can be utilized.

[0214] -> For example, maximum bandwidth information of APs participating in C-TDMA

[0215] Specifically, the Operating bandwidth can be defined as a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field, thereby indicating the channel width, which is the BSS BW information of each AP.

[0216] Ex) Setting the above field to 0: 20 MHz bandwidth indication / Setting the above field to 1: 40 MHz bandwidth indication / Setting the above field to 2: 80 MHz bandwidth indication / Setting the above field to 3: 160 / 80+80 MHz bandwidth indication / Setting the above field to 4: 320 / 160+160 MHz bandwidth indication / The remaining values ​​5 to 7 of the above field can be set as reserved.

[0217] -> For example, BW field information within the SIG-A field

[0218] -> For example, UL BW field information included in the Common Info field of MU-RTS TXS TF

[0219] -> The bandwidth of the DAP may be included within the total bandwidth over which the SAP operates.

[0220] -> For example, a new field for bandwidth indication can be added by changing / redefining the Medium Time field of the QoS Characteristics element to include a new subfield.

[0221] Specifically, the Operating bandwidth can be defined as a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field, thereby indicating the channel width, which is the BSS BW information of each AP.

[0222] Ex) Setting the above field to 0: 20 MHz bandwidth indication / Setting the above field to 1: 40 MHz bandwidth indication / Setting the above field to 2: 80 MHz bandwidth indication / Setting the above field to 3: 160 / 80+80 MHz bandwidth indication / Setting the above field to 4: 320 / 160+160 MHz bandwidth indication / The remaining values ​​5 to 7 of the above field can be set as reserved.

[0223] F. Required TXOP duration: Information related to the TXOP duration that each AP wishes to share.

[0224] -> For example, you can specify this by defining a new field containing Required TXOP Duration.

[0225] Specifically, a new Required Duration field (tentative name) can be defined to indicate information required for C-TDMA operation and the Required TXOP Duration value.

[0226] -> For example, you can indicate this by defining a new element that includes Required TXOP Duration.

[0227] Specifically, a new C-TDMA Operation element (tentative name) can be defined to indicate information required for C-TDMA operation and the Required TXOP Duration value.

[0228] -> For example, the Required TXOP Duration can be indicated by including it in the QoS Characteristic element that can be used to include negotiation information during the pre-negotiation process for C-TDMA operation or in an element that can be newly defined for negotiation in C-TDMA.

[0229] -> For example, the Required TXOP Duration can be included in the UHR Operation element that can be used to include announcement information in the announcement process of each AP for C-TDMA operation, or in an element that can be newly defined for announcement in C-TDMA.

[0230] G. Low Latency Traffic Information: Information related to low latency traffic that each AP wants to transmit and receive.

[0231] -> For example, information of the QoS Characteristic element included in the SCS request / response frame, especially the Delay Bound field information among the information of the QoS Characteristic element, can be utilized.

[0232] Specifically, the Delay Bound field value for the QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0233] Through this, SAP can use the above field to check whether TXOP sharing is necessary or to update the existing value with a DAP that can complete transmission of an MSDU or A-MSDU within the end of the TXOP interval to be shared (i.e., shorter than the time allocated by the pre-negotiated Low Latency Traffic information or Delay Bound field value).

[0234] -> For example, you can utilize the MSDU Lifetime field information among the QoS Characteristic element information.

[0235] Specifically, the MSDU Lifetime field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0236] This allows SAP to use the above field to check whether TXOP sharing is necessary for a DAP that does not discard MSDUs within the end of the TXOP interval it wants to share (i.e., pre-negotiated Low Latency Traffic information or MSDU Lifetime field value does not expire within the allocated time) or to update the existing value.

[0237] -> For example, you can utilize the Service Start Time field information among the QoS Characteristic element information.

[0238] Specifically, the Service Start Time field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0239] Through this, SAP can use the above field to check whether TXOP sharing is necessary or to update the existing value with the DAP that can start the expected Service Period and frame exchange within the end of the TXOP interval to be shared (i.e., shorter than the time allocated by the pre-negotiated Low Latency Traffic information or the Service Start Time field value).

[0240] -> For example, TXOP sharing request information requested / instructed by an AP that requires transmission of low latency traffic.

[0241] -> For example, time-bound information of Low Latency Traffic requested / instructed by an AP that requires transmission of Low Latency Traffic (e.g., minimum time-bound within which transmission of Low Latency Traffic must begin or maximum time-bound within which transmission of Low Latency Traffic must successfully end)

[0242] -> For example, arrival rate information of Low Latency Traffic requested / instructed by an AP that requires periodic transmission of Low Latency Traffic (e.g., arrival rate of Low Latency Traffic since the last reporting event).

[0243] H. UHR STA support: Information indicating whether only UHR non-AP STAs are supported.

[0244] -> For example, it is defined as 1 bit signaling to indicate UHR STA support information within the coordination request / response frame.

[0245] Ex) bit 0: Indicates that only UHR non-AP STAs are supported / bit 1: Indicates that HE / EHT / UHR non-AP STAs are supported

[0246] -> For example, the information in the Special User Info field included in the Trigger frame, especially the PHY Version Identifier among the information in the Special User Info field, is utilized.

[0247] -> For example, the QoS Characteristic element included in the SCS request / response frame, specifically, the Reserved bit of Control Info among the information of the QoS Characteristic element, is utilized. That is, it is defined as 1 bit signaling to indicate UHR STA support information among the Reserved bits.

[0248] Ex) bit 0: Indicates that only UHR non-AP STAs are supported / bit 1: Indicates that HE / EHT / UHR non-AP STAs are supported

[0249] -> The information / signaling may be defined to indicate that the AP supports only UHR non-AP STAs, or to indicate that it supports not only UHR but also HE / EHT non-AP STAs, but is not limited thereto.

[0250] - The ID and signaling names defined above may be changed, and information that forms the basis for Multi-AP operation (e.g., channel information, DAP buffer information, etc.) may be included.

[0251] 2) coordination response frame (+ Status Code)

[0252] In addition, the coordination response frame transmitted during the negotiation process of C-TDMA proposed in this specification may include negotiation information based on one or more combinations of A to I below.

[0253] A. Multi-AP group ID: ID for the set of APs that constitute multi-AP coordination (e.g., 0, 1, 2, ...)

[0254] B. Multi-AP ID: ID assigned from AP within the configured Multi-AP group (e.g., 0, 1, 2, ...)

[0255] C. Multi-AP coordination type: Information on multi-AP cooperative transmission techniques such as C-OFDMA, C-TDMA, J-TX, and C-SR.

[0256] D. Operating channel: Information on the primary and punctured channels in operation.

[0257] -> For example, common channel information for smooth cooperation between APs participating in C-TDMA

[0258] -> For example, primary channel information on which APs participating in C-TDMA can operate in common

[0259] Specifically, the Operating channel can be defined as a new field that plays the role of the CCSF0 field in the EHT Operation Information field to indicate the channel center frequency index for the 20 / 40 / 80 MHz channel.

[0260] Specifically, the Operating channel can be defined as a new field that plays the role of the CCSF0 field in the EHT Operation Information field to indicate the channel center frequency for the primary 80 MHz channel of a 160 MHz channel or the channel center frequency for the primary 160 MHz channel of a 320 MHz channel.

[0261] Additionally, the Operating channel can be defined as a new field that plays the role of the CCSF1 field in the EHT Operation Information field to indicate the channel center frequency for a 160 MHz channel or the channel center frequency for a 320 MHz channel.

[0262] -> For example, punctured channel information of an AP participating in C-TDMA

[0263] Specifically, the Operating channel can be defined as a new field that serves as the Disabled Subchannel Bitmap field in the EHT Operation Information field, thereby indicating the punctured 20 MHz subchannel using a bitmap.

[0264] Ex) A bit value of 0 in the bitmap indicates that the corresponding 20 MHz subchannel is not punctured / A bit value of 1 in the bitmap indicates that the corresponding 20 MHz subchannel is punctured

[0265] -> The primary channel of DAP can be included within the channel where SAP operates.

[0266] -> DAP's primary channel can be included within the operating channel excluding SAP's punctured channel.

[0267] E. Operating bandwidth: Operating bandwidth and maximum bandwidth information

[0268] -> For example, BW information that operates in common for smooth cooperation between APs participating in C-TDMA.

[0269] Specifically, the operating channel and primary channel information described above can be utilized.

[0270] -> For example, maximum bandwidth information of APs participating in C-TDMA

[0271] Specifically, the Operating bandwidth can be defined as a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field, thereby indicating the channel width, which is the BSS BW information of each AP.

[0272] Ex) Setting the above field to 0: 20 MHz bandwidth indication / Setting the above field to 1: 40 MHz bandwidth indication / Setting the above field to 2: 80 MHz bandwidth indication / Setting the above field to 3: 160 / 80+80 MHz bandwidth indication / Setting the above field to 4: 320 / 160+160 MHz bandwidth indication / The remaining values ​​5 to 7 of the above field can be set as reserved.

[0273] -> For example, BW field information within the SIG-A field

[0274] -> For example, UL BW field information included in the Common Info field of MU-RTS TXS TF

[0275] -> The bandwidth of the DAP may be included within the total bandwidth over which the SAP operates.

[0276] -> For example, a new field for bandwidth indication can be added by changing / redefining the Medium Time field of the QoS Characteristics element to include a new subfield.

[0277] Specifically, the Operating bandwidth can be defined as a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field, thereby indicating the channel width, which is the BSS BW information of each AP.

[0278] Ex) Setting the above field to 0: 20 MHz bandwidth indication / Setting the above field to 1: 40 MHz bandwidth indication / Setting the above field to 2: 80 MHz bandwidth indication / Setting the above field to 3: 160 / 80+80 MHz bandwidth indication / Setting the above field to 4: 320 / 160+160 MHz bandwidth indication / The remaining values ​​5 to 7 of the above field can be set as reserved.

[0279] F. Required TXOP duration: Information related to the TXOP duration that each AP wishes to share.

[0280] -> For example, you can specify this by defining a new field containing Required TXOP Duration.

[0281] Specifically, a new Required Duration field (tentative name) can be defined to indicate information required for C-TDMA operation and the Required TXOP Duration value.

[0282] -> For example, you can indicate this by defining a new element that includes Required TXOP Duration.

[0283] Specifically, a new C-TDMA Operation element (tentative name) can be defined to indicate information required for C-TDMA operation and the Required TXOP Duration value.

[0284] -> For example, the Required TXOP Duration can be indicated by including it in the QoS Characteristic element that can be used to include negotiation information during the pre-negotiation process for C-TDMA operation or in an element that can be newly defined for negotiation in C-TDMA.

[0285] -> For example, the Required TXOP Duration can be included in the UHR Operation element that can be used to include announcement information in the announcement process of each AP for C-TDMA operation, or in an element that can be newly defined for announcement in C-TDMA.

[0286] G. Low Latency Traffic Information: Information related to low latency traffic that each AP wants to transmit and receive.

[0287] -> For example, information of the QoS Characteristic element included in the SCS request / response frame, especially the Delay Bound field information among the information of the QoS Characteristic element, can be utilized.

[0288] Specifically, the Delay Bound field value for the QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0289] Through this, SAP can use the above field to check whether TXOP sharing is necessary or to update the existing value with a DAP that can complete transmission of an MSDU or A-MSDU within the end of the TXOP interval to be shared (i.e., shorter than the time allocated by the pre-negotiated Low Latency Traffic information or Delay Bound field value).

[0290] -> For example, you can utilize the MSDU Lifetime field information among the QoS Characteristic element information.

[0291] Specifically, the MSDU Lifetime field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0292] This allows SAP to use the above field to check whether TXOP sharing is necessary for a DAP that does not discard MSDUs within the end of the TXOP interval it wants to share (i.e., pre-negotiated Low Latency Traffic information or MSDU Lifetime field value does not expire within the allocated time) or to update the existing value.

[0293] -> For example, you can utilize the Service Start Time field information among the QoS Characteristic element information.

[0294] Specifically, the Service Start Time field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0295] Through this, SAP can use the above field to check whether TXOP sharing is necessary or to update the existing value with the DAP that can start the expected Service Period and frame exchange within the end of the TXOP interval to be shared (i.e., shorter than the time allocated by the pre-negotiated Low Latency Traffic information or the Service Start Time field value).

[0296] -> For example, TXOP sharing request information requested / instructed by an AP that requires transmission of low latency traffic.

[0297] -> For example, time-bound information of Low Latency Traffic requested / instructed by an AP that requires transmission of Low Latency Traffic (e.g., minimum time-bound within which transmission of Low Latency Traffic must begin or maximum time-bound within which transmission of Low Latency Traffic must successfully end)

[0298] -> For example, arrival rate information of Low Latency Traffic requested / instructed by an AP that requires periodic transmission of Low Latency Traffic (e.g., arrival rate of Low Latency Traffic since the last reporting event).

[0299] H. UHR STA support: Information indicating whether only UHR non-AP STAs are supported.

[0300] -> For example, it is defined as 1 bit signaling to indicate UHR STA support information within the coordination request / response frame.

[0301] Ex) bit 0: Indicates that only UHR non-AP STAs are supported / bit 1: Indicates that HE / EHT / UHR non-AP STAs are supported

[0302] -> For example, the information in the Special User Info field included in the Trigger frame, especially the PHY Version Identifier among the information in the Special User Info field, is utilized.

[0303] -> For example, the QoS Characteristic element included in the SCS request / response frame, specifically, the Reserved bit of Control Info among the information of the QoS Characteristic element, is utilized. That is, it is defined as 1 bit signaling to indicate UHR STA support information among the Reserved bits.

[0304] Ex) bit 0: Indicates that only UHR non-AP STAs are supported / bit 1: Indicates that HE / EHT / UHR non-AP STAs are supported

[0305] -> The information / signaling may be defined to indicate that the AP supports only UHR non-AP STAs, or to indicate that it supports not only UHR but also HE / EHT non-AP STAs, but is not limited thereto.

[0306] I. Status Code: Accept / Reject / Recommendation information for the coordination request

[0307] -> For example, Accept or Success (eg, SUCCESS)

[0308] -> For example, Reject or Reject with Recommendation (specifically, Reject code with Reject reason (e.g., REJECTED_BAD_SUPPORTED_CHANNELS) or Reject code with Recommendation (e.g., REJECTED_WITH_SUGGESTED_CHANGES))

[0309] If the Status Code value includes Reject or Recommendation, it may include information for a new negotiation. That is, the neighboring AP receiving the request frame may include additional information about the Operating channel and bandwidth, Required TXOP duration, Low Latency Traffic Information, and UHR STA support described above.

[0310] - The ID and signaling names defined above may be changed, and information that forms the basis for Multi-AP operation (e.g., channel information, DAP buffer information, etc.) may be included.

[0311] 1.2 C-TDMA inter-AP negotiation procedure (preliminary procedure for request / response frame exchange)

[0312] The proposed inter-AP negotiation process for multi-AP cooperation in this section enables target APs to participate and operate in C-TDMA. Since the AP-to-AP negotiation process has not yet been defined, the previously defined Request / Response negotiation process between APs and non-AP STAs can be utilized for the inter-AP negotiation process for C-TDMA operation. However, because the subject of the coordination request / response for multi-AP cooperation and C-TDMA operation, as well as the criteria / conditions for the coordination request, may be less clear than the negotiation between APs and non-AP STAs, these need to be specified.

[0313] First, the criteria for an AP willing to participate in multi-AP cooperation to transmit a coordination request frame can be determined by the following example.

[0314] Option 1) Individual coordination request based on AP's coordination needs

[0315] When multi-AP cooperation is required, each AP can individually transmit a coordination request frame to a specific AP based on frames (e.g., management, control, and data frames) overheard from neighboring APs. The need for multi-AP coordination may arise from burst data transmission by individual APs and the occurrence of low-latency traffic. Upon receiving a coordination request frame transmitted according to the coordination need of an individual AP, a specific AP can transmit a response frame to the corresponding coordination request based on the status code.

[0316] Option 2) Coordination request that modifies and utilizes the Beacon frame

[0317] Each AP can overhear the periodically transmitted beacon frame to determine whether there are other APs interested in multi-AP cooperation and C-TDMA. To achieve this, new signaling bits can be defined and added to the beacon frame. For example, 1-bit signaling can be utilized (using the reserved bit in the Capability Information field within the frame body).

[0318] Ex) bit 0: Indicates participation in multi-AP cooperation / bit 1: Indicates not participation in multi-AP cooperation

[0319] That is, when an AP that receives a beacon frame including the new signaling bit (equal to 1) described above wishes to participate in multi-AP cooperation, it can decode the information and elements following the signaling bit and obtain additional information related to multi-AP cooperation. After that, the AP can secure a channel through medium contention and transmit a coordination request frame to the corresponding neighboring AP. The neighboring AP that receives the coordination request frame can transmit a coordination response frame based on the status code. On the other hand, a non-AP STA can ignore the signaling bit information regarding multi-AP cooperation above.

[0320] Based on the criteria for requesting the above-described negotiation, the negotiation process for coordination between an AP (e.g., AP 1) and a neighboring AP (e.g., AP 2) can be performed in two ways as follows.

[0321] Step 1) The AP transmits a coordination request frame to the neighboring AP.

[0322] Step 2) The neighboring AP that receives the coordination request frame transmits a coordination response frame to the AP that sent the coordination request frame.

[0323] At this time, the neighboring AP that receives the coordination request frame in Step 2) can transmit a coordination response frame including response information for the coordination request based on the Status Code. For example, if the coordination response frame includes a code for Accept or Success, coordination for C-TDMA operation can be considered successful. On the other hand, if the AP receives a coordination response frame with a Reject code or a Reject code including a Recommendation, the AP can retransmit the coordination request frame to the neighboring AP. That is, the AP can include the same information as the information included in the coordination request frame transmitted during the initial negotiation process or include changed information based on the Rejection reason or Recommendation in the received coordination response frame. In addition, if the AP that received the coordination response frame with a Reject code or a Reject code including a Recommendation does not retransmit the coordination request frame, coordination can be considered to have failed (due to rejection).

[0324] 1.3 Example of C-TDMA operation according to negotiation

[0325] Figure 21 shows an example of C-TDMA operation according to pair-to-pair based negotiation including UHR STA support information.

[0326] Section 2.1 defines negotiation information for C-TDMA operation, and Section 2.2 presents a negotiation procedure for C-TDMA based on this information. Section 2.3 presents an example of C-TDMA operation based on the negotiation information and procedure. Figure 21 illustrates an embodiment of C-TDMA operation between APs that have performed a pair-to-pair negotiation procedure including UHR STA support information.

[0327] In Fig. 21, APs whose roles as SAPs or DAPs have not been determined before acquiring a TXOP transmit and receive coordination request frames and corresponding coordination response frames with neighboring APs, and perform a preliminary negotiation procedure for multi-AP cooperation. Through the negotiation procedure of exchanging request and response frames containing information for C-TDMA operation, APs wishing to operate in multi-AP cooperation and C-TDMA can obtain information about each other. An AP that can acquire a TXOP and perform the SAP role can decide based on the negotiation information whether to first perform individual FEs (Frame Exchanges) with STAs within its BSS or to share the TXOP with a specific DAP.

[0328] At this time, an AP that receives a coordination request or response frame containing and indicating UHR STA support information indicating whether it only supports UHR STAs can assume that the corresponding AP intends to perform FE (Frame Exchange) only for UHR STAs. If a specific AP that is aware of this acquires a TXOP and acts as a SAP, it can define additional signaling that may be required from the SAP for FE with legacy devices within the DAP's BSS. Alternatively, the SAP can preferentially share the TXOP with UHR STA support DAPs that do not require new procedures (or based on an agreement through negotiation).

[0329] Figure 22 shows an example of C-TDMA operation according to Broadcast based Negotiation including UHR STA support information.

[0330] In Fig. 22, before acquiring a TXOP, each AP whose role as a SAP or DAP has not been determined can broadcast a TF containing C-TDMA-related information to participate in multi-AP cooperation and receive TB PPDUs from corresponding APs. APs that wish to operate in multi-AP cooperation and C-TDMA can obtain information about each other through a broadcast-based negotiation procedure that exchanges TFs and TB PPDUs containing information for C-TDMA operation. An AP that can acquire a TXOP and act as a SAP can decide based on the negotiation information whether to first perform individual FEs with STAs within its BSS or to share the TXOP with a specific DAP.

[0331] At this time, an AP that has acquired UHR STA support information indicating whether it only supports UHR STAs can assume that the AP intends to perform FE only for UHR STAs. If a specific AP that is aware of this acquires a TXOP and acts as a SAP, it can define additional signaling that may be required from the SAP for FE with legacy devices within the DAP's BSS. Alternatively, the SAP can preferentially share the TXOP with UHR STA-supporting DAPs that do not require new procedures (or based on an agreement through negotiation).

[0332] This specification defines the negotiation process that must occur between APs before C-TDMA operation in a multi-AP cooperation environment, as well as the information that each AP must exchange during the negotiation process. Based on the negotiation information based on one or more combinations described in Section 1.1, APs that have successfully completed coordination can perform C-TDMA operation. That is, based on the negotiation information defined in Section 1.1, each AP can exchange the necessary information in advance through the negotiation process in Sections 1.2 and 1.3, and then finally create a multi-AP table for operating multi-AP coordination. Based on the table and information, the SAP can support transmission based on a coordination scheme to a specific DAP or a DAP that only supports UHR non-AP STAs. Through this, the DAP can perform frame exchange with (UHR) non-AP STAs within its BSS within the allocated time or resources.

[0333] 2. Device / method in which an example of this specification operates

[0334] 2.1. PPDU in which the signal of this specification is transmitted / received

[0335] Figure 23 illustrates an example of a PPDU of this specification.

[0336] Fig. 23 is an example of a SU / MU PPDU that can be used in a UHR system, which may include some of the features of the format of the EHT-PPDU described above. All or part of all parts (i.e., fields) illustrated may be divided into multiple subparts / subfields. Each field (and subfield) may be transmitted in units of 4us * N (N is an integer). In addition, the PPDU may include a Guard Interval (or Short GI) of a conventional WIFI standard. A common subcarrier frequency spacing value (delta_f = 312.5 kHz / N or 312.5 kHz * N, where N is an integer) may be applied to all of the illustrated fields, or a first delta_f may be applied to the first part (e.g., all Legacy-Part, all / part of SIG-Part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0337] Some of the fields shown may be omitted, and the order of the fields is shown as an example and may be changed in various ways. For example, it is possible that the subfields of SIG-Part (200) (e.g., U-SIG) are placed before STF-Part (300), and the remaining subfields of SIG-Part (200) (e.g., UHR-SIG) are placed after STF-Part (300).

[0338] The illustrated Legacy Part (100) may include at least one of a conventional Non-HT Short Training Field (L-STF), a Non-HT Long Training Field (L-LTF), and a Non-HT Signal Field (L-SIG).

[0339] The illustrated SIG-Part (200) may include various control information for the transmitted PPDU. For example, it may include control information for decoding the STF-Part (300), LTF-Part (400), and Data (500). For example, it may include all / part of the information included in the U-SIG information described above and the information included in the EHT-SIG information.

[0340] The illustrated STF-Part (300) may include an STF sequence.

[0341] The illustrated LTF-Part (400) may include a training field (i.e., an LTF sequence) for channel estimation.

[0342] The data field (500) includes user data and may include a packet for an upper layer. That is, it may include an MPDU (MAC Frame).

[0343] The MU-RTS Trigger frame described in this specification belongs to one of the types of Trigger frames corresponding to MAC frames. That is, the illustrated data field (500) may include an MU-RTS Trigger frame.

[0344] 2.2. Method of this specification

[0345] 2.2.1. Transmission Method

[0346] Figure 24 illustrates a procedure for performing negotiation required for a transmitting device according to the present embodiment to perform C-TDMA operation.

[0347] An example of FIG. 24 can be performed at a transmitting device (AP and / or non-AP STA).

[0348] The SAP and DAP described in this specification may be included in the AP.

[0349] Some of the steps (or detailed sub-steps described below) in the example of Fig. 24 may be omitted or changed.

[0350] S100: The coordination request / response frame generated by the transmitting device (transmitting STA) may include negotiation information based on one or more combinations for C-TDMA operation in the multi-AP cooperation defined in section 1.1 above.

[0351] S200: In step S200, the transmitting device may configure an MPDU including a coordination request / response frame including negotiation information for C-TDMA configured in S100. In addition, the transmitting device may configure / generate a PPDU including the MPDU in a data field. This step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S200 includes a step of configuring U-SIG and UHR-SIG fields and a data field. This may include a step of configuring a field including control information indicating the size / position of the RU (i.e., N bitmap) and / or a step of configuring a field including an identifier of an STA receiving the RU (i.e., AID).

[0352] Additionally, step S200 may include a step of generating an STF / LTF sequence to be transmitted via a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0353] Additionally, step S200 may include a step of generating an MPDU to be transmitted through a specific RU.

[0354] A transmitting device can transmit a PPDU configured as above to a receiving device.

[0355] During PPDU transmission, the transmitting device may perform at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, GI insertion, etc.

[0356] A signal / field / sequence configured according to this specification can be transmitted in the form of FIG. 23.

[0357] 2.2.2. Receiving Method

[0358] Figure 25 illustrates a procedure for performing negotiation required for a receiving device according to the present embodiment to perform C-TDMA operation.

[0359] The above-described PPDU can be received according to an example of FIG. 25.

[0360] An example of FIG. 25 can be performed at a receiving device (AP and / or non-AP STA).

[0361] Some of the steps (or detailed sub-steps described below) in the example of Fig. 25 may be omitted.

[0362] S300: A receiving device (receiving STA) may receive all or part of a PPDU through step S300. The received signal may be in the form of FIG. 23.

[0363] The sub-step of step S300 can be determined based on step S200. That is, step S300 can perform an operation to restore the results of CSD, Spatial Mapping, IDFT / IFFT operations, and GI insertion operations applied in step S200.

[0364] S400: The receiving device can decode all or part of a PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.

[0365] More specifically, the receiving device can decode the L-SIG, U-SIG and UHR-SIG of the PPDU based on the Legacy STF / LTF, and obtain information included in the L-SIG, U-SIG and UHR-SIG fields.

[0366] Additionally, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) acquired through step S400. For example, the receiving device can decode the STF / LTF field of the PPDU based on the information about the Tone Plan. Additionally, the receiving device can decode the data field of the PPDU based on the information about the Tone Plan and acquire the MPDU included in the data field.

[0367] Additionally, the receiving device can perform a processing operation to transmit the decoded data through step S400 to a higher layer (i.e., MAC layer). Furthermore, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation can be performed.

[0368] S500: The receiving device can obtain the negotiation information for C-TDMA described in Section 1.1 of this specification when decoding the data field.

[0369] The receiving STA can then perform a processing operation to transmit the decoded data from the data field to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data transmitted to the higher layer, a subsequent operation can be performed.

[0370] Based on the data acquired through step S500, the receiving STA can either accept or reject the coordination request. If rejecting, a recommendation (suggestion) may be included.

[0371] 2.3. Device of this specification

[0372] 2.3.1. Transmitter

[0373] Fig. 26 illustrates a transmitting device that performs negotiation necessary to perform C-TDMA operation according to the present embodiment.

[0374] A PPDU including the above-described MPDU can be transmitted based on the device of FIG. 26.

[0375] An example of FIG. 26 relates to an example of a transmitting device (AP and / or non-AP STA).

[0376] As illustrated in FIG. 26, the transmitting device may include a memory (1920), a processor (1910), and a transceiver (1930).

[0377] The above memory (1920) can store one or more negotiation information regarding one or more APs participating in the C-TDMA described herein.

[0378] The processor (1910) may generate a coordination request / response frame based on information stored in the memory (1920) and generate an MPDU including the coordination request / response frame. In addition, a PPDU including the MPDU may be configured. An example of a PPDU generated by the processor (1910) may be as shown in FIG. 23.

[0379] Additionally, the processor (1910) may be configured to transmit a PPDU containing the generated coordination request / response frame via the transceiver (1930).

[0380] The above processor (1910) can perform all / part of the operations illustrated in FIG. 24.

[0381] The illustrated transceiver (1930) includes an antenna and can perform analog signal processing. Specifically, the processor (1910) can control the transceiver (1930) to transmit a PPDU generated by the processor (1910).

[0382] Alternatively, the processor (1910) may generate a transmission PPDU and store information about the transmission PPDU in the memory (1920).

[0383] 2.3.2. Receiving device

[0384] Fig. 27 illustrates a receiving device that performs negotiation necessary to perform C-TDMA operation according to the present embodiment.

[0385] A PPDU including the above-described MPDU can be received based on the device of FIG. 27.

[0386] As illustrated in FIG. 27, the receiving device may include a memory (2020), a processor (2010), and a transceiver (2030).

[0387] The transceiver (2030) can receive a PPDU based on the control of the processor (2010). For example, the transceiver (2030) may include a plurality of sub-units (not shown). For example, the transceiver (2030) may include at least one receiving antenna and a filter for the receiving antenna.

[0388] The PPDU received via the transceiver (2030) may be stored in the memory (2020). The processor (2010) may process decoding of the received PPDU via the memory (2020). The processor (2010) may obtain negotiation information regarding an AP that wishes to participate in C-TDMA or other Multi-AP schemes (e.g., C-BF, C-SR) from the coordination request / response frame included in the PPDU, and store the obtained information in the memory (2020).

[0389] For example, the processor (2010) may be configured to receive a PPDU through the transceiver (2030), decode the received PPDU, and obtain an MPDU (e.g., a coordination request / response frame). In addition, the processor (2010) may be configured to decode / parse the coordination request / response frame to obtain C-TDMA negotiation information (or information on Multi-AP schemes) about an AP connected to the receiving device. In addition, the processor (2010) may be configured to allow the receiving STA to accept or reject a coordination request based on the negotiation information about the AP, and to exchange frames with other devices through the transceiver (2030).

[0390] The processor (2010) can perform decoding on the received PPDU. Specifically, it can perform operations to restore the results of CSD, Spatial Mapping, IDFT / IFFT operations, and GI insertion applied to the PPDU. The operations to restore the results of CSD, Spatial Mapping, IDFT / IFFT operations, and GI insertion can be performed by multiple processing units (not shown) individually implemented within the processor (2010).

[0391] Additionally, the processor (2010) can decode the data field of the PPDU received through the transceiver (2030).

[0392] Additionally, the processor (2010) may process the decoded data. For example, the processor (2010) may perform a processing operation to transmit information regarding the decoded data field to a higher layer (e.g., a MAC layer). Additionally, if the upper layer instructs the PHY layer to generate a signal in response to the data transmitted to the upper layer, a subsequent operation may be performed.

[0393] Figure 28 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0394] An example of FIG. 28 may be performed at a transmitting STA or transmitting device (AP and / or non-AP STA).

[0395] Some of the steps (or detailed sub-steps described below) in the example of Fig. 28 may be omitted or changed.

[0396] Through step S2810, the transmitting device (transmitting STA) can obtain information regarding the aforementioned Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.

[0397] Through step S2820, the transmitting device can configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S2820 may include a step of configuring an EHT-SIG field including control information regarding a Tone Plan. That is, step S2820 may include a step of configuring a field including control information indicating the size / position of an RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the RU.

[0398] Additionally, step S2820 may include a step of generating an STF / LTF sequence to be transmitted through a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0399] Additionally, step S2820 may include a step of generating a data field (i.e., MPDU) to be transmitted via a specific RU.

[0400] The transmitting device can transmit the PPDU configured through step S2820 to the receiving device based on step S2830.

[0401] While performing step S2830, the transmitting device may perform at least one of operations such as CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion.

[0402] A signal / field / sequence configured according to this specification can be transmitted in the form of FIG. 5.

[0403] Fig. 29 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0404] The above-described PPDU can be received according to an example of FIG. 29.

[0405] An example of FIG. 29 may be performed at a receiving STA or receiving device (AP and / or non-AP STA).

[0406] Some of the steps (or detailed sub-steps described below) in the example of Fig. 29 may be omitted.

[0407] A receiving device (receiving STA) may receive all or part of a PPDU through step S2910. The received signal may have the form of FIG. 5.

[0408] The sub-step of step S2910 can be determined based on step S2830 of Fig. 28. That is, step S2910 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operations, and GI insert operations applied in step S2830.

[0409] At step S2920, the receiving device can decode all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.

[0410] More specifically, the receiving device can decode the L-SIG and EHT-SIG of the PPDU based on the Legacy STF / LTF and obtain information included in the L-SIG and EHT SIG fields. Information regarding various Tone Plans (i.e., RUs) described herein can be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.

[0411] In step S2930, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) acquired through step S2920. For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about one Plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the Tone Plan (i.e., RU) and acquire the MPDU included in the data field.

[0412] Additionally, the receiving device may perform a processing operation to transmit the decoded data to a higher layer (e.g., MAC layer) through step S2930. Additionally, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation may be performed.

[0413] Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 29.

[0414] Figure 30 is a flowchart illustrating a procedure for performing negotiation to perform C-TDMA operation on the Sharing AP side according to the present embodiment.

[0415] An example of FIG. 30 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0416] An example of FIG. 30 is performed in a second AP, and the second AP and the first AP may be configured as a shared AP or a sharing AP after the cooperation phase in multi-AP communication. The first non-AP STA of the present embodiment may correspond to at least one STA (station).

[0417] This embodiment proposes a method for performing inter-AP negotiation to perform C-TDMA operation in multi-AP (Access Point) communication (or multi-AP operation). In particular, this embodiment proposes a method for defining information required for negotiation to perform C-TDMA operation. Furthermore, this embodiment is not limited to the C-TDMA technique, and other coordinated multi-AP techniques such as C-SR and CBF may be applied.

[0418] In step S3010, the second AP (access point) receives a coordination request frame from the first AP.

[0419] In step S3020, the second AP transmits a cooperation response frame to the first AP.

[0420] In step S3030, after the second AP acquires TXOP (Transmission Opportunity), if the second AP is set as a Sharing AP that controls cooperation between multiple APs, allocation information for a portion of the TXOP time is transmitted to the first AP based on the cooperation request frame and the cooperation response frame.

[0421] Transmitting allocation information for a portion of the time of the TXOP to the first AP includes sharing or allocating time resources of the second AP to the first AP.

[0422] Frames are exchanged between the first AP and the first non-AP STA (station) during a portion of the above TXOP or a time shared or allocated from the second AP.

[0423] The above cooperation request frame includes negotiation information for cooperation between the plurality of APs. The cooperation response frame includes information regarding a response or rejection to the cooperation request frame based on the negotiation information.

[0424] After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information. The first non-AP STA is a non-AP STA within the BSS of the first AP. That is, at the time of performing the negotiation procedure based on the cooperation request frame and the cooperation response frame, the roles of the first and second APs as Sharing APs or Shared APs may not be determined. After the negotiation procedure is completed and a specific AP obtains the TXOP, the AP can function as a Sharing AP, and the AP that is allocated or shared with resources such as the TXOP can function as a Shared AP.

[0425] That is, the present embodiment proposes a method for performing negotiation between multiple APs to perform a transmission technique for cooperation between multiple APs (or cooperation between APs in a multi-AP environment). In addition, the present embodiment proposes a method for defining information to be exchanged between the multiple APs during the negotiation process. As a result, APs that have successfully cooperated based on the proposed negotiation information can perform a coordinated multi-AP technique such as C-TDMA. In addition, based on the proposed negotiation information, the Sharing AP can share a TXOP with the Shared AP, and through this, the Shared AP can perform frame exchange with a non-AP STA (or UHR non-AP STA) within its BSS during the allocated TXOP. In addition, by proposing a negotiation method for effectively performing communication between multiple APs, it is possible to perform appropriate scheduling between each AP, and thus, an increase in the overall network throughput can be expected.

[0426] The above cooperation request frame may include at least one of the first to eighth pieces of information.

[0427] The first information may include information about an identifier for a group of APs that constitute cooperation between the plurality of APs. The second information may include information about identifiers for APs within the group. The third information may include information about a technique for cooperation between the plurality of APs. The fourth information may include information about an operating channel. The fifth information may include information about an operating bandwidth. The sixth information may include section information for the TXOP. The seventh information may include information about low latency traffic. The eighth information may include information about UHR STA support.

[0428] The above cooperative response frame may include at least one of the first to eighth information and the ninth information.

[0429] The above ninth information may include information about a status code. The information about the status code may include information about a response (accept) or rejection (reject) to the cooperation request frame.

[0430] The above-described technique for cooperation between multiple APs may include Coordinated-Time Division Multiplexing Access (C-TDMA), Coordinated-Spatial Reuse (C-SR), Coordinated-beamforming (C-BF), or Coordinated-Orthogonal Frequency Division Multiple Access (C-OFMA).

[0431] Information about the above-mentioned operating channel may include information on a channel in which the first and second APs operate in common or information on punctured channels of the first and second APs. The primary channel of the first AP may be included in the channel in which the second AP operates. The primary channel of the first AP may be included in the operating channels excluding the punctured channel of the second AP.

[0432] The information about the above operating bandwidth may include information about the bandwidth at which the first and second APs operate in common or information about the maximum bandwidth of the first and second APs. The bandwidth of the first AP may be included within the total bandwidth at which the second AP operates.

[0433] The information about the low-latency traffic may include information about the time-bound of the low-latency traffic required by the first or second AP or information about the arrival rate.

[0434] The information about the UHR STA support may include information about whether the first non-AP STA is supported only as a UHR non-AP STA. For example, if the information about the UHR STA support is set to 0, the first non-AP STA may be configured only as the UHR non-AP STA. If the information about the UHR STA support is set to 1, the first non-AP STA may be configured as a HE (High efficiency) non-AP STA, an EHT (Extreme High Throughput) non-AP STA, or a UHR non-AP STA.

[0435] By adding information about the UHR STA support to the above cooperation request / response frame, it is possible to specify that the AP participating in the cooperation between the multiple APs is an AP or BSS that supports only UHR non-AP STAs, thereby eliminating the need for the Sharing AP to define additional rules or signaling for the Shared AP.

[0436] In addition, the operation for the procedure of determining an AP participating in cooperation between the above multiple APs and transmitting a cooperation request frame to the AP is as follows.

[0437] The first AP may overhear a beacon frame from a neighboring AP. Based on the beacon frame, the first AP may determine an AP participating in the cooperation among the multiple APs as the neighboring AP. Based on the beacon frame, the first AP may transmit the cooperation request frame to the neighboring AP.

[0438] The above beacon frame may include a first bit. For example, if the first bit is set to 0, it may indicate that the neighboring AP participates in cooperation among the plurality of APs. If the first bit is set to 1, it may indicate that the neighboring AP does not participate in cooperation among the plurality of APs. The neighboring AP may be the second AP.

[0439] This embodiment proposes a pair-to-pair negotiation procedure using the cooperation request frame and cooperation response frame. Furthermore, this embodiment can also propose a broadcast-based negotiation procedure. In this case, a trigger frame may be used instead of the cooperation request frame, and a TB (Trigger-Based) PPDU may be used instead of the cooperation response frame. In this case, the trigger frame may be broadcast.

[0440] After the second AP acquires the TXOP, the second AP may transmit a MU-RTS (Multi User-Request to Send) TXS (TXOP sharing) trigger frame to the first AP. The second AP may receive a CTS (Clear to Send) frame from the first AP in response to the MU-RTS TXS trigger frame. The MU-RTS TXS trigger frame may include allocation information for a portion of the TXOP.

[0441] In addition, after the second AP acquires the TXOP, the second AP may exchange frames with a second non-AP STA during the TXOP (or a part of the TXOP). The second non-AP STA may be a non-AP STA within the BSS of the second AP, and may be a legacy non-AP STA or a UHR non-AP STA. Accordingly, the information about the UHR STA support may further include information about whether the second non-AP STA is supported only as a UHR non-AP STA.

[0442] FIG. 31 is a flowchart illustrating a procedure for performing negotiation to perform C-TDMA operation on the Shared AP side according to the present embodiment.

[0443] An example of FIG. 31 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0444] An example of FIG. 31 is performed in a first AP, and the first AP and the second AP may be configured as a shared AP or a shared AP after the cooperation phase in multi-AP communication. The first non-AP STA of the present embodiment may correspond to at least one STA (station).

[0445] This embodiment proposes a method for performing inter-AP negotiation to perform C-TDMA operation in multi-AP (Access Point) communication (or multi-AP operation). In particular, this embodiment proposes a method for defining information required for negotiation to perform C-TDMA operation. Furthermore, this embodiment is not limited to the C-TDMA technique, and other coordinated multi-AP techniques such as C-SR and CBF may be applied.

[0446] In step S3110, the first AP (access point) transmits a coordination request frame to the second AP. Alternatively, the second AP may transmit a coordination request frame to the first AP.

[0447] In step S3120, the first AP receives a cooperation response frame from the second AP. Alternatively, the second AP may receive a cooperation response frame from the first AP.

[0448] In step S3130, the first AP receives allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame.

[0449] Receiving allocation information for a portion of the above TXOP time includes sharing or being allocated time resources of the second AP.

[0450] At step S3140, the first AP exchanges frames with the first non-AP STA (station) for a portion of the TXOP.

[0451] The above cooperation request frame includes negotiation information for cooperation between the plurality of APs. The cooperation response frame includes information regarding a response or rejection to the cooperation request frame based on the negotiation information.

[0452] After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information. The first non-AP STA is a non-AP STA within the BSS of the first AP. That is, at the time of performing the negotiation procedure based on the cooperation request frame and the cooperation response frame, the roles of the first and second APs as Sharing APs or Shared APs may not be determined. After the negotiation procedure is completed and a specific AP obtains the TXOP, the AP can function as a Sharing AP, and the AP that is allocated or shared with resources such as the TXOP can function as a Shared AP.

[0453] That is, the present embodiment proposes a method for performing negotiation between multiple APs to perform a transmission technique for cooperation between multiple APs (or cooperation between APs in a multi-AP environment). In addition, the present embodiment proposes a method for defining information to be exchanged between the multiple APs during the negotiation process. As a result, APs that have successfully cooperated based on the proposed negotiation information can perform a coordinated multi-AP technique such as C-TDMA. In addition, based on the proposed negotiation information, the Sharing AP can share a TXOP with the Shared AP, and through this, the Shared AP can perform frame exchange with a non-AP STA (or UHR non-AP STA) within its BSS during the allocated TXOP. In addition, by proposing a negotiation method for effectively performing communication between multiple APs, it is possible to perform appropriate scheduling between each AP, and thus, an increase in the overall network throughput can be expected.

[0454] The above cooperation request frame may include at least one of the first to eighth pieces of information.

[0455] The first information may include information about an identifier for a group of APs that constitute cooperation between the plurality of APs. The second information may include information about identifiers for APs within the group. The third information may include information about a technique for cooperation between the plurality of APs. The fourth information may include information about an operating channel. The fifth information may include information about an operating bandwidth. The sixth information may include section information for the TXOP. The seventh information may include information about low latency traffic. The eighth information may include information about UHR STA support.

[0456] The above cooperative response frame may include at least one of the first to eighth information and the ninth information.

[0457] The above ninth information may include information about a status code. The information about the status code may include information about a response (accept) or rejection (reject) to the cooperation request frame.

[0458] The above-described technique for cooperation between multiple APs may include Coordinated-Time Division Multiplexing Access (C-TDMA), Coordinated-Spatial Reuse (C-SR), Coordinated-beamforming (C-BF), or Coordinated-Orthogonal Frequency Division Multiple Access (C-OFMA).

[0459] Information about the above-mentioned operating channel may include information on a channel in which the first and second APs operate in common or information on punctured channels of the first and second APs. The primary channel of the first AP may be included in the channel in which the second AP operates. The primary channel of the first AP may be included in the operating channels excluding the punctured channel of the second AP.

[0460] The information about the above operating bandwidth may include information about the bandwidth at which the first and second APs operate in common or information about the maximum bandwidth of the first and second APs. The bandwidth of the first AP may be included within the total bandwidth at which the second AP operates.

[0461] The information about the low-latency traffic may include information about the time-bound of the low-latency traffic required by the first or second AP or information about the arrival rate.

[0462] The information about the UHR STA support may include information about whether the first non-AP STA is supported only as a UHR non-AP STA. For example, if the information about the UHR STA support is set to 0, the first non-AP STA may be configured only as the UHR non-AP STA. If the information about the UHR STA support is set to 1, the first non-AP STA may be configured as a HE (High efficiency) non-AP STA, an EHT (Extreme High Throughput) non-AP STA, or a UHR non-AP STA.

[0463] By adding information about the UHR STA support to the above cooperation request / response frame, it is possible to specify that the AP participating in the cooperation between the multiple APs is an AP or BSS that supports only UHR non-AP STAs, thereby eliminating the need for the Sharing AP to define additional rules or signaling for the Shared AP.

[0464] In addition, the operation for the procedure of determining an AP participating in cooperation between the above multiple APs and transmitting a cooperation request frame to the AP is as follows.

[0465] The first AP may overhear a beacon frame from a neighboring AP. Based on the beacon frame, the first AP may determine an AP participating in the cooperation among the multiple APs as the neighboring AP. Based on the beacon frame, the first AP may transmit the cooperation request frame to the neighboring AP.

[0466] The above beacon frame may include a first bit. For example, if the first bit is set to 0, it may indicate that the neighboring AP participates in cooperation among the plurality of APs. If the first bit is set to 1, it may indicate that the neighboring AP does not participate in cooperation among the plurality of APs. The neighboring AP may be the second AP.

[0467] This embodiment proposes a pair-to-pair negotiation procedure using the cooperation request frame and cooperation response frame. Furthermore, this embodiment can also propose a broadcast-based negotiation procedure. In this case, a trigger frame may be used instead of the cooperation request frame, and a TB (Trigger-Based) PPDU may be used instead of the cooperation response frame. In this case, the trigger frame may be broadcast.

[0468] After the second AP acquires the TXOP, the second AP may transmit a MU-RTS (Multi User-Request to Send) TXS (TXOP sharing) trigger frame to the first AP. The second AP may receive a CTS (Clear to Send) frame from the first AP in response to the MU-RTS TXS trigger frame. The MU-RTS TXS trigger frame may include allocation information for a portion of the TXOP.

[0469] In addition, after the second AP acquires the TXOP, the second AP may exchange frames with a second non-AP STA during the TXOP (or a part of the TXOP). The second non-AP STA may be a non-AP STA within the BSS of the second AP, and may be a legacy non-AP STA or a UHR non-AP STA. Accordingly, the information about the UHR STA support may further include information about whether the second non-AP STA is supported only as a UHR non-AP STA.

[0470] <Device Configuration>

[0471] The technical features of the present specification described above can be applied to various devices and methods. For example, the technical features of the present specification described above can be performed / supported by the devices of FIG. 1 and / or FIG. 13. For example, the technical features of the present specification described above can be applied only to a part of FIG. 1 and / or FIG. 13. For example, the technical features of the present specification described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and the memory (112, 122) of FIG. 1, or based on the processor (610) and the memory (620) of FIG. 13. For example, the device of the present specification transmits a coordination request frame to a second access point (AP); receives a coordination response frame from the second AP; Receive allocation information for a portion of a TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame; and exchange frames with a first non-AP STA (station) during a portion of the TXOP time.

[0472] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable recording medium containing instructions that are executed by at least one processor.

[0473] The CRM may store instructions for performing operations including the steps of: transmitting a coordination request frame to a second access point (AP); receiving a coordination response frame from the second AP; receiving allocation information for a portion of a TXOP (Transmission Opportunity) from the second AP based on the coordination request frame and the coordination response frame; and exchanging frames with a first non-AP STA (station) during a portion of the TXOP. The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to the CRM of the present specification may be the processor (111, 121) or the processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 13. Meanwhile, the CRM of this specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 13, or a separate external memory / storage medium / disk, etc.

[0474] The technical features of this specification described above are applicable 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).

[0475] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0476] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0477] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.

[0478] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0479] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.

[0480] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.

[0481] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.

[0482] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.

[0483] Additionally, the above-described technical features can be applied to wireless communication of robots.

[0484] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.

[0485] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.

[0486] Additionally, the above-described technical features can be applied to devices that support extended reality.

[0487] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0488] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0489] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

[0490] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a wireless LAN system, A step in which a first AP (access point) transmits a coordination request frame to a second AP; A step in which the first AP receives a cooperation response frame from the second AP; A step in which the first AP receives allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame; and The first AP includes a step of exchanging frames with a first non-AP STA (station) for a portion of the TXOP, The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. method.

2. In paragraph 1, The above cooperation request frame includes at least one piece of information from the first to eighth pieces of information, The above first information includes information about an identifier for a group of APs that constitute cooperation between the plurality of APs, The second information includes information about identifiers for APs within the group, The third information includes information on a technique for cooperation between the plurality of APs, The fourth information includes information about the operating channel, The fifth information includes information about the operating bandwidth, The above sixth information includes section information for the TXOP, The seventh information includes information about low latency traffic, The above eighth information includes information about UHR STA support. method.

3. In paragraph 2, The above cooperative response frame includes at least one of the first to eighth information and the ninth information, The above 9th information includes information about the status code, Information about the above status code includes information about a response (accept) or rejection (reject) to the above cooperation request frame. method.

4. In paragraph 2, The above-mentioned techniques for cooperation between multiple APs include Coordinated-Time Division Multiplexing Access (C-TDMA), Coordinated-Spatial Reuse (C-SR), Coordinated-beamforming (C-BF), or Coordinated-Orthogonal Frequency Division Multiple Access (C-OFMA). method.

5. In paragraph 2, The step of the first AP overhearing a beacon frame from a neighboring AP; The step of the first AP determining an AP participating in cooperation between the plurality of APs as the neighboring AP based on the beacon frame; and The first AP further includes a step of transmitting the cooperation request frame to the neighboring AP based on the beacon frame, The above beacon frame includes a first bit, If the first bit is set to 0, it indicates that the neighboring AP participates in cooperation between the plurality of APs, If the first bit is set to 1, it indicates that the neighboring AP does not participate in cooperation between the plurality of APs, The above neighboring AP is the second AP method.

6. In paragraph 5, The information about the above-mentioned operating channel includes information about a channel on which the first and second APs commonly operate or information about a punctured channel of the first and second APs, The primary channel of the first AP is included within the channel on which the second AP operates, The primary channel of the first AP is included in the operating channel excluding the punctured channel of the second AP. method.

7. In paragraph 5, The information about the above operating bandwidth includes information about the bandwidth at which the first and second APs commonly operate or information about the maximum bandwidth of the first and second APs, The bandwidth of the first AP is included within the total bandwidth in which the second AP operates. method.

8. In paragraph 5, The information about the low-latency traffic includes information about the time-bound of the low-latency traffic required by the first or second AP or information about the arrival rate, The information about the above UHR STA support includes information about whether the first non-AP STA is supported only by the UHR non-AP STA, If the information about the above UHR STA support is set to 0, the first non-AP STA is set only as the UHR non-AP STA, When the information about the above UHR STA support is set to 1, the first non-AP STA is set to a HE (High efficiency) non-AP STA, an EHT (Extreme High Throughput) non-AP STA, or a UHR non-AP STA. method.

9. In a wireless LAN system, the first AP (access point) is memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Transmit a coordination request frame to the second AP; Receive a cooperation response frame from the second AP; Receive allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame; and Exchange frames with the first non-AP STA (station) during a portion of the above TXOP, The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. 1st AP.

10. In a wireless LAN system, A step in which a second AP (access point) receives a coordination request frame from a first AP; The second AP transmits a cooperation response frame to the first AP; and The second AP comprises a step of transmitting allocation information for a portion of the time of TXOP (Transmission Opportunity) to the first AP based on the cooperation request frame and the cooperation response frame, During a portion of the above TXOP, frames are exchanged between the first AP and the first non-AP STA (station), The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. method.

11. In paragraph 10, The above cooperation request frame includes at least one piece of information from the first to eighth pieces of information, The above first information includes information about an identifier for a group of APs that constitute cooperation between the plurality of APs, The second information includes information about identifiers for APs within the group, The third information includes information on a technique for cooperation between the plurality of APs, The fourth information includes information about the operating channel, The fifth information includes information about the operating bandwidth, The above sixth information includes section information for the TXOP, The seventh information includes information about low latency traffic, The above eighth information includes information about UHR STA support. method.

12. In paragraph 11, The above cooperative response frame includes at least one of the first to eighth information and the ninth information, The above 9th information includes information about the status code, Information about the above status code includes information about a response (accept) or rejection (reject) to the above cooperation request frame. method.

13. In paragraph 11, The above-mentioned techniques for cooperation between multiple APs include Coordinated-Time Division Multiplexing Access (C-TDMA), Coordinated-Spatial Reuse (C-SR), Coordinated-beamforming (C-BF), or Coordinated-Orthogonal Frequency Division Multiple Access (C-OFMA). method.

14. In paragraph 11, The information about the above-mentioned operating channel includes information about a channel on which the first and second APs commonly operate or information about a punctured channel of the first and second APs, The primary channel of the first AP is included within the channel on which the second AP operates, The primary channel of the first AP is included in the operating channel excluding the punctured channel of the second AP. method.

15. In paragraph 11, The information about the above operating bandwidth includes information about the bandwidth at which the first and second APs commonly operate or information about the maximum bandwidth of the first and second APs, The bandwidth of the first AP is included within the total bandwidth in which the second AP operates. method.

16. In paragraph 11, The information about the low-latency traffic includes information about the time-bound of the low-latency traffic required by the first or second AP or information about the arrival rate, The information about the above UHR STA support includes information about whether the first non-AP STA is supported only by the UHR non-AP STA, If the information about the above UHR STA support is set to 0, the first non-AP STA is set only as the UHR non-AP STA, When the information about the above UHR STA support is set to 1, the first non-AP STA is set to a HE (High efficiency) non-AP STA, an EHT (Extreme High Throughput) non-AP STA, or a UHR non-AP STA. method.

17. In a wireless LAN system, the second AP (access point) is memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Receive a coordination request frame from the first AP; Transmitting a cooperation response frame to the first AP; and Based on the above cooperation request frame and the above cooperation response frame, allocation information for a portion of the TXOP (Transmission Opportunity) time is transmitted to the first AP. During a portion of the above TXOP, frames are exchanged between the first AP and the first non-AP STA (station), The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. 2nd AP.

18. At least one computer-readable medium containing instructions based on being executed by at least one processor, A step of transmitting a coordination request frame to a second AP (access point); A step of receiving a cooperation response frame from the second AP; A step of receiving allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame; and A step of exchanging frames with a first non-AP STA (station) during a portion of the above TXOP, The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. Recording medium.

19. In a wireless LAN system, for a device, memory; and A processor operatively coupled to the memory, the processor comprising: Transmit a coordination request frame to the second AP (access point); Receive a cooperation response frame from the second AP; Receive allocation information for a portion of the TXOP (Transmission Opportunity) time from the second AP based on the cooperation request frame and the cooperation response frame; and Exchange frames with the first non-AP STA (station) during a portion of the above TXOP, The above cooperation request frame includes negotiation information for cooperation between multiple APs, The above cooperation response frame includes information about a response or rejection to the cooperation request frame based on the above negotiation information, After the second AP obtains the TXOP based on the cooperation request frame and the cooperation response frame, the second AP is set as a Sharing AP that controls cooperation between multiple APs, and the first AP is set as a Shared AP that is allocated or shared with resources from the Sharing AP based on the negotiation information, and The above first non-AP STA is a non-AP STA within the BSS of the first AP. device.

Images