Method and device for configuring frame for MAPC agreement teardown in wireless LAN system

Abstract

Proposed are a method and a device for configuring a frame for MAPC agreement teardown in a wireless LAN system. Specifically, a first AP transmits a negotiation request frame to a second AP. The first AP tears down a MAPC agreement with the second AP on the basis of the negotiation request frame. The negotiation request frame is a public action frame having a first value of a public action field. The negotiation request frame is used for the MAPC agreement teardown.

Description

Method and device for constructing a frame to release MAPC consensus in a wireless LAN system

[0001] This specification relates to a technique for constructing a frame to tear down MAPC consensus in a wireless LAN system, and more specifically, to a method and apparatus used to tear down said MAPC consensus by defining a negotiation request frame based on a reserved value of the public action field of a public action frame.

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs, and to this end, various technologies are being considered to support high throughput, low latency, and extended range. For example, multiple APs can cooperate to perform a TXOP sharing procedure.

[0003] This specification proposes a method and apparatus for constructing a frame to release MAPC consensus in a wireless LAN system.

[0004] One example of this specification proposes a method for constructing a frame to release MAPC consensus.

[0005] This 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0006] This embodiment may be performed at a first AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be established as a coordinating AP or a coordinated AP through the MAPC negotiation.

[0007] This embodiment proposes a method for defining a frame to tear down a MAPC agreement formed through MAPC negotiation. Specifically, this embodiment proposes a method to use to tear down the MAPC agreement by defining a negotiation request frame based on the reserved value of the public action field of a public action frame.

[0008] The first AP (access point) sends a negotiation request frame to the second AP.

[0009] The above-mentioned first AP releases the Multi-AP Coordination (MAPC) agreement with the above-mentioned second AP based on the above-mentioned negotiation request frame.

[0010] The first AP mentioned above is a MAPC requesting AP that initiates negotiations for the MAPC agreement. The second AP mentioned above is a MAPC responding AP that responds to the MAPC requesting AP.

[0011] The above negotiation request frame is a public action frame having a first value of the public action field. The above negotiation request frame is used to release the above MAPC consensus.

[0012] The first value above may be set to one of the reserved values ​​of the common action field (e.g., 54 to 59 and 61 to 255) up to an 802.11be wireless LAN system. For example, the first value may be 69.

[0013] That is, the present embodiment proposes a method for releasing MAPC consensus by defining a negotiation request frame (or MAPC negotiation request frame) based on a common action frame.

[0014] According to the embodiments proposed in this specification, since the negotiation request frame defined based on the common action frame can be classified as a Class 1 frame, it has the effect of being able to be transmitted between APs that are in an un-authentication and un-association relationship, or between APs that are authentic but in an un-association relationship. In addition, since there is no need to define a separate dedicated management frame in each procedure such as discovery for MAPC and negotiation for MAPC consensus (MAPC consensus formation, MAPC consensus update, MAPC consensus release), it has the effect of being able to perform other negotiation procedures as well as release MAPC consensus based on the negotiation request frame.

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

[0016] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

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

[0018] FIG. 4 illustrates an example of a multi-link (ML).

[0019] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0020] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.

[0021] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0022] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.

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

[0024] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0025] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0026] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

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

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

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

[0030] Figure 16 illustrates an example of Coordinated Beamforming (CBF).

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

[0032] Figure 18 illustrates an example of JTX / JT.

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

[0034] Figure 20 shows an example of coordinated TDMA operation including a negotiation process.

[0035] Figure 21 illustrates an example of a MAPC element format.

[0036] Figure 22 illustrates another example of the MAPC element format.

[0037] FIG. 23 illustrates an example of a MAPC element format including a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0038] Figure 24 illustrates another example of a MAPC element format including a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0039] Figure 25 illustrates an example of a MAPC teardown operation.

[0040] Figure 26 illustrates another example of MAPC teardown operation.

[0041] FIG. 27 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0042] FIG. 28 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0043] FIG. 29 is a flowchart illustrating a procedure for receiving a frame to release MAPC agreement according to the present embodiment.

[0044] FIG. 30 is a flowchart illustrating the procedure for configuring a frame to release MAPC agreement according to the present embodiment.

[0045] In this specification, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0046] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B, or C.”

[0047] In this specification, “at least one of A and B” may 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” may be interpreted as synonymous with “at least one of A and B.”

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

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

[0050] Additionally, the expressions “based on,” “on the basis of,” or “according to” as used herein mean “based at least in part on,” and do not mean “based only on one.”

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

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

[0053] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.

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

[0055] 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 this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

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

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

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

[0059] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0060] The first STA (110) may include a processor (111), 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.

[0061] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0062] 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 transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (i.e., the received signal) and the signal to be transmitted through the transceiver (i.e., the transmitted signal).

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

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

[0065] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). Additionally, control information related to the operation of the AP or the transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals 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 AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).

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

[0067] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPDU) may be performed by the transceivers (113, 123) of FIG. 1. Additionally, in the following example, 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 processors (111, 121) of FIG. 1.For example, an example of an operation to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.

[0068] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.

[0069] For example, the transceiver (113, 123) shown in side drawing (b) of FIG. 1 can perform the same function as the transceiver shown in side drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) shown in side 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) shown in side drawing (b) of FIG. 1 can perform the same function as the processor (111, 121) and the memory (112, 122) shown in side drawing (a) of FIG. 1 described above.

[0070] 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, AP (Access Point), 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) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).

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

[0072] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in 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.

[0073] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, the processor (111, 121) or 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 a processor enhanced therefrom.

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

[0075] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0076] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0077] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0078] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).

[0079] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.

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

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

[0082] In a BSS like the one at the top of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0083] The bottom of Fig. 2 is a conceptual diagram showing IBSS.

[0084] 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 performs management functions centrally. 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 since access to the distributed system is not allowed, they form a self-contained network.

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

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

[0087] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. 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 in the same way (i.e., transmit and receive probe request / response on channel 2).

[0088] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.

[0089] The STA that discovered the 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 later. The authentication process of S320 may include the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

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

[0091] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.

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

[0093] Subsequently, 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 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.

[0094] FIG. 4 illustrates an example of a multi-link (ML).

[0095] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (i.e., AP STAs), and the non-AP MLD may include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0096] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by 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 link may be configured in different bands.

[0097] The AP MLD of FIG. 4 includes three affiliated APs. In one 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 one 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. Additionally, in one 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. Additionally, in one 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.

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

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

[0100] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0101] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.

[0102] 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 SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.

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

[0104] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be 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.

[0105] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can 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 can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.

[0106] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0107] The L-SIG field of FIG. 5 may contain, 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 contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU, or a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an 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, or 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 a UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0108] For example, a (non-AP and AP) STA can apply BCC encoding based on a code rate of 1 / 2 to 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoding. BPSK modulation can be applied to the 48 bits of encoding to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. Consequently, 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 of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0109] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. 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.

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

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

[0112] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. 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. 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.

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

[0114] A bit information (e.g., 52 un-coded bits) transmitted by 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 may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

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

[0116] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a 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 a UHR PPDU based on the PHY version identifier having the second value.

[0117] 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 is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

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

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

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

[0121] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a 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.

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

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

[0124] 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 configured individually in 80 MHz units. 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 regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding a preamble puncturing pattern).

[0125] Additionally or generally, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. 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).

[0126] 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 may contain different U-SIGs.

[0127] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one 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.

[0128] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

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

[0130] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, 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.

[0131] As shown at the top of FIG. 6, 26 units (i.e., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones are inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

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

[0133] In the example of FIG. 6, various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., are proposed. Since the specific size 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 indicated as N-tone RU, etc. For example, 26-RU may be indicated as 26-tone RU.

[0134] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0135] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.

[0136] In addition, as described, 484-RU 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.

[0137] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.

[0138] FIG. 9 illustrates the operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can establish a channel connection through contending (i.e., Backoff operation) and transmit a Trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the Trigger frame (930). When the PPDU containing the Trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

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

[0140] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0141] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, 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 located between 2.4 and 2.5 GHz) are used / supported / defined.

[0142] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels 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 to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of channel indices and center frequencies may change.

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

[0144] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0145] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or higher 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 may be changed.

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

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

[0148] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0149] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.

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

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

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

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

[0154] The processor (610) of FIG. 13 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (610) of FIG. 13 may be the same as the processing chip (114, 124) of FIG. 1.

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

[0156] Referring to FIG. 13, a power management module (611) manages power for 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 associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.

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

[0158] The Multi-AP operation applicable to this specification is described below.

[0159] The above Multi-AP operation refers to a communication technique involving multiple APs in a WLAN. For example, the above 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 above Multi-AP operation, existing techniques may be expressed using various terms such as STX (Single Transmission). For example, the above STX operation may refer to a method in which a single BSS AP communicates with a single BSS STA. When communication is performed based on the above STX operation, interference may occur with adjacent APs (e.g., APs located in overlapping BSSs). Due to this interference, a problem may arise 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.

[0160] FIG. 14 illustrates operation according to a conventional STX operation. As illustrated, interference between STA and AP may occur due to AP1 and AP2 being adjacent to each other.

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

[0162] In Figure 14, STA1 and AP1 are included in the BSS, and STA2 and AP2 can be included in the OBSS (Overlapping Basic Service Set). That is, STA2 is an un-associated STA to AP1, and STA1 is an un-associated STA to AP2.

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

[0164] FIG. 15 illustrates an example of C-OFDMA (Coordinated OFDMA). The illustrated AP1 can transmit a PPDU / signal to STA1, and AP2 can transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 can be performed in the same / overlapping time interval. Transmission from AP1 to STA1 can be performed based on a first frequency band, and transmission from AP2 to STA2 can 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 BSS, and STA2 and AP2 may be included in OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0165] Although not shown in FIG. 15, an example of Co-TDMA (Coordinated 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.

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

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

[0168] FIG. 16 illustrates an example of Coordinated Beamforming (CBF). The illustrated AP1 can transmit a PPDU / signal to STA1, and AP2 can transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 can be performed in the same / overlapping time intervals. Transmission from AP1 and transmission from AP2 can be performed through the same / overlapping frequency bands. To reduce interference caused by AP1 to STA2, AP1 can perform nulling / beamforming toward STA2, and to reduce interference caused by AP2 to STA1, AP2 can perform nulling / beamforming toward STA1. For example, such nulling / beamforming can be implemented by positioning a radiation null to a neighboring unassociated STA. The aforementioned nulling / beamforming can make a specific AP invisible to a neighboring unassociated STA. For example, the aforementioned nulling / beamforming can make AP1 (or AP2) invisible to STA2 (or STA1).

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

[0170] 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 can be transmitted and received through a backhaul link between AP1 and AP2.

[0171] FIG. 17 illustrates an example of AP selection. The illustrated AP2 is determined to have better channel conditions than AP1. AP1 transmits its data / signal to AP2 via a backhaul link, and AP2 can transmit a signal to STA1 instead of AP1. For example, in FIG. 17, STA1 and AP1 may be included in BSS, and STA2 and AP2 may be included in OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0172] FIG. 18 illustrates an example of JTX / JT. The illustrated AP1 can perform transmission to STA1 together with AP2. For example, the PPDU / signal transmitted from AP2 to STA1 may be wholly or partially identical to the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be transmitted simultaneously through a frequency band that is identical to or overlaps with 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 via a backhaul link. For example, in FIG. 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 un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0173] More specifically, in FIG. 18, AP1 transmits a coordination request (or various names such as first request, control request, etc.) to AP2 and receives a coordination response (or various names such as first response, control response, etc.) from AP2. Through the exchange of the request / response, information regarding coordination between AP1 and AP2 (e.g., information regarding whether AP1 and AP2 will perform simultaneous transmission to STA1), information regarding the time when coordination begins, information regarding the time when AP1 and AP2 start simultaneous transmission to STA1, and information regarding data shared between AP1 and AP2 can be exchanged. AP1 can share its data with AP2 via a backhaul link. Subsequently, AP1 transmits a coordination trigger frame (or various names such as trigger frame, etc.) to AP2 and can perform simultaneous transmission to STA1 based on the trigger frame.

[0174] <Examples Applicable to the Present Specification>

[0175] Although a large number of APs are installed in close proximity to each other to enable terminals to maintain continuous WLAN connectivity over a wider area, issues such as radio interference and transmission collisions between APs may occur as the BSSs of multiple APs overlap. To resolve these issues, various technologies for coordinating APs in frequency, time, and spatial domains (e.g., RU selection, joint transmission, nulling, etc.) have been proposed, and attention must also be paid to the various issues that may arise during cooperation between APs.

[0176] In EHT (802.11be), a technique was proposed to allocate a portion of the 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 within the Common Info field of the existing MU-RTS Trigger frame, and a MU-RTS (Multi User-Request To Send) Trigger frame when this value is non-zero is referred to as a MU-RTS TXOP Sharing (TXS) Trigger frame (TF). If the value of 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 TXOP Sharing mode is 2, the non-AP STA supports P2P transmission in addition to (non-TB) PPDU transmission to the AP.

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

[0178] FIG. 19 shows an example of operation when the TXOP Sharing mode value is 2. When the AP transmits a MU-RTS TXS TF containing time allocation information (Time allocated in MU-RTS TXS Trigger Frame in FIG. 19) to non-AP STA 1, Non-AP STA 1 responds to this with a CTS (Clear-To-Send) and can then perform P2P transmission to non-AP STA 2.

[0179] Figure 20 shows an example of coordinated TDMA operation including a negotiation process.

[0180] 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 transmissions within the BSS of each cooperating AP into time units. That is, FIG. 20 illustrates an example of Coordinated-Time Division Multiplexing Access (Co-TDMA) based on time units among the cooperation methods between cooperating APs. In this case, the AP in the existing Triggered TXS protocol acts as the AP that shares TXOPs in the Multi-AP coordination operation, and the STA in the existing Triggered TXS protocol acts as the AP that receives shared TXOPs in the Multi-AP coordination operation. In this specification, the AP that shares TXOPs is referred to as the Sharing AP (SAP), and the AP that receives TXOPs from the SAP is referred to as the Shared AP (DAP). Here, the SAP that shares TXOPs is not limited solely to AP STAs and may also include non-AP STAs that share TXOPs. In addition, DAPs that share a TXOP are not limited to only AP STAs and may include non-AP STAs that share a TXOP (or perform transmission and reception with an AP STA that shares a TXOP). Also, frame exchanges with non-AP STAs or SAPs belonging to the DAP BSS during the time allocated to the DAP are referred to as the DAP's BSS frame exchange (FE).For example, data frame transmission and block ACK frame response following RTS / CTS frame exchange between DAP and non-AP STA, UL data frame transmission by non-AP STAs for a trigger frame transmitted from DAP, or data frame transmission by DAP for a trigger frame transmitted from SAP can be performed as frame exchange.

[0181] Basically, for Multi-AP cooperation to occur between two APs or for a Multi-AP organization (or peer) to be formed, capabilities and requirements must be exchanged in advance (negotiation), and an agreement must be reached based on the acquired information to enable the implementation of Multi-AP cooperation-based technologies (e.g., C-TDMA, C-BF, C-SR, etc.). On the other hand, if a specific AP that had engaged in Multi-AP cooperation no longer wishes to maintain the partnership due to the purpose of power saving or various other factors, a procedure to terminate the Multi-AP cooperation must be performed.

[0182] Accordingly, the present specification defines and proposes a frame transmitted by an AP that has established Multi-AP cooperation to terminate Multi-AP cooperation. Through the MAP (or MAPC) Teardown frame (tentative name) proposed in the present specification, an AP that has established Multi-AP cooperation can terminate Multi-AP cooperation.

[0183] To clarify the terminology, the above cooperative relationship can be referred to as a Multi-AP Coordination (MAPC) relationship or a MAPC agreement. An AP initiating the MAPC (or MAPC negotiation for at least one MAPC technique) can be referred to as a MAPC requesting AP or a coordinating AP. An AP responding to the MAPC requesting AP can be referred to as a MAPC responding AP or a coordinated AP. The coordinating AP is an AP that shares a portion of the TXOP (transmission opportunity) resources by allocating a time portion to the coordinated AP or by allowing simultaneous transmission as part of the MAPC procedure.

[0184] Specific designations (names) proposed in this specification may be changed and are not limited to any one.

[0185] Through a Co-TDMA or Co-TDMA (coordinated TDMA) procedure, the AP can transmit at least one PPDU by sharing the time portion of the acquired TXOP with another AP belonging to the AP set (which may consist of a single AP).

[0186] The Co-TDMA procedure includes a polling phase, a TXOP allocation phase, and a TXOP return phase.

[0187] During the polling phase, the Co-TDMA shared AP may request a poll response transmitted via TB PPDU from other APs only if the other APs support a response via TB PPDU. The Co-TDMA shared AP indicates its intention to share the time portion of the TXOP obtained from the Initial Control Frame (ICF) transmitted at the start of the TXOP with other APs. When the ICF receives a time allocation from the Co-TDMA shared AP within the TXOP, it polls one or more APs to request a response in order to determine the intent of the polled AP. The Duration field of the ICF is set to the value obtained by adding the time required to transmit the requested response from the polled AP to one SIFS. The ICF that polls to determine the intent of the AP when receiving a time allocation from the Co-TDMA shared AP within the TXOP is a trigger frame. The Co-TDMA shared AP identifies each AP to be polled by setting the AID12 subfield of the polled AP's user information field in the trigger frame to the AP ID of the polled AP.

[0188] The polled AP provides the following in response to the received ICF above.

[0189] - Indicates the intention not to receive time allocations from the Co-TDMA shared AP during the current TXOP (Note: If the Co-TDMA shared AP does not receive a response from the polled AP, the Co-TDMA shared AP indicates that the polled AP does not intend to receive time allocations from the Co-TDMA shared AP during the current TXOP).

[0190] - Indicates the intention to receive a time allocation from the Co-TDMA shared AP during the current TXOP

[0191] - Signaling details (including traffic instructions)

[0192] In the TXOP allocation step, the Co-TDMA shared AP may allocate a time portion of an acquired TXOP to another AP that is not collocated with the Co-TDMA shared AP. To share the time portion of a TXOP acquired by the Co-TDMA shared AP, the AP must send a MU-RTS TXS trigger frame to another AP that is not collocated with the Co-TDMA shared AP.

[0193] The Duration field of the above MU-RTS TXS trigger frame is set to the value obtained by adding the time required to transmit the requested CTS response frame to one SIFS. The Co-TDMA coordinated AP identifies the Co-TDMA coordinated AP to share the time portion of the acquired TXOP by setting the AID12 subfield of the user information field of the above MU-RTS TXS trigger frame to the AP ID of the Co-TDMA coordinated AP. When the Co-TDMA coordinated AP receives the above MU-RTS TXS trigger frame from the Co-TDMA coordinated AP, the AP may transmit and / or receive one or more PPDUs within the time allocation indicated in the above MU-RTS TXS trigger frame. The first PPDU of the exchange must deliver a CTS frame. The time allocated to the Co-TDMA coordinated AP identified in the above MU-RTS TXS trigger frame is specified in the Allocation Duration subfield of the above MU-RTS TXS trigger frame.

[0194] In the TXOP return step, the Co-TDMA cooperative AP can return the remainder of the time allocated to the Co-TDMA shared AP (if any).

[0195] This specification defines and proposes a frame transmitted by an AP that has established Multi-AP coordination (MAPC) to release MAPC. The MAPC Teardown frame for releasing MAPC proposed in this specification can be defined and designed as presented in Section 1 below.

[0196] 1. Multi-AP Coordination Teardown frame format

[0197] 1.1. Definition of Action field format of MAPC Teardown frame

[0198] An AP that has established an MAPC can transmit a newly defined MAPC Teardown frame to release the MAPC. The MAPC Teardown frame can be redefined as a (Public) Action frame, which is one type of Management frame. Since standard Management frames are relatively large, redefining it as a (Public) Action frame has the advantage of reducing overhead related to frame size.

[0199] Specifically, a new Public Action frame format for MAPC teardown can be defined using the Reserved values ​​(e.g., 54-59, 61-255) of the Public Action field. Additionally or alternatively, a new Public Action frame format for overall MAPC operation can be defined and classified and defined by the MAPC Type field (e.g., Discovery, Negotiation, and Teardown) of the MAPC element within the corresponding Management frame. Additionally or alternatively, a new Public Action frame format for overall MAPC operation can be defined and first classified by the MAPC Type field (e.g., Discovery, Negotiation) of the MAPC element within the corresponding Management frame, and then classified and defined as MAPC Teardown through the MAPC Operation Type field of the MAPC Negotiation frame.

[0200] In this specification, this is referred to as a MAPC Teardown frame, and the specific name may be changed. The MAPC Teardown frame may include an element / field containing common information regarding Multi-AP cooperation and / or an element / field containing information regarding individual Multi-AP cooperation schemes (e.g., C-SR / BF / TDMA, etc.).

[0201] For example, the Action field format of the MAPC Teardown frame may be as shown in Table 1.

[0202] Order Information Notes 1 Category The Category field is determined (Action field). - Indicates Code 4 (Public) when assuming a Public Action frame. 2 Public Action Indicates the value corresponding to the Public Action field values. - Uses Reserved values ​​(e.g., 54-59, 61-255) to indicate that it is a MAPC Teardown frame format for MAPC teardown. 3 SSID (or AP ID, Multi-AP ID) e.g., the SSID (MAC address) of the peer AP. Additionally or alternatively, the Multi-AP ID (or AP ID) locally assigned / given to the peer AP during the negotiation process for Multi-AP cooperation. Additionally or alternatively, the Multi-AP ID (or AP ID) locally assigned / given by the peer AP during the negotiation process for Multi-AP cooperation. 4 Multi-AP Coordination Management or MAPC element A Multi-AP Coordination Management element containing various management information utilized during the negotiation process for Multi-AP cooperation or during Multi-AP cooperation operations.

[0203] 1.2. The following information is included within the Multi-AP Coordination Management element (or MAPC element) of the MAPC Teardown frame.

[0204] In this case, the Multi-AP Coordination Management element (i.e., MAPC element) of the MAPC Teardown frame may contain information based on one or more combinations presented below. The names of such contents may be changed, new contents may be added, and are not limited thereto.

[0205] A. Length: Indicates the number of octets within the element, excluding the Length field.

[0206] B. MAPC Protocol Identifier: Indicates the protocol type of the currently established or formed Multi-AP cooperation.

[0207] For example, unauthenticated (Unauthenticated) Multi-AP coordination protocol

[0208] For example, an authenticated Multi-AP coordination protocol

[0209] C. Link ID: Used to identify a link where Multi-AP cooperation has been established or formed, and indicates the Multi-AP cooperation link.

[0210] D. Reason Code: Reason information regarding the teardown of Multi-AP cooperation

[0211] Specifically, Reason codes defined in the existing Reason Code field can be utilized.

[0212] -> For example, set Reason code = 1 (UNSPECIFIED_REASON) to instruct to disable Multi-AP cooperation by unspecified reason.

[0213] For example, set Reason code = 2 (INVALID_AUTHENTICATION) to indicate that Multi-AP cooperation is disabled because the previous authentication is no longer valid.

[0214] -> For example, set Reason code = 39 (TIMEOUT) to instruct to disable Multi-AP cooperation due to a timeout.

[0215] E. MAPC PMK: Includes / indicates the PMKID (PMK identifier) ​​used to derive the PTK (Pairwise Transient Key: a temporary key valid for one session and dynamically generated) when configuring Multi-AP cooperation with neighboring APs, and identifies the PMK (Pairwise Master Key: a secret key shared between APs and non-AP STAs) used to protect the Management frame exchanged between APs.

[0216] For example, the Chosen PMK (optional) field within an existing Mesh Peering Management element can be used. The Chosen PMK field exists when dot11MeshSecurityActivated is true and the sender and receiver of the frame containing the element share a PMK. The Chosen PMK field includes a PMKID that identifies the PMK used to protect Mesh Peering Management.

[0217] F. Address: Address information of the target AP (e.g., BSS color, BSSID for Multi-AP, or MAC address)

[0218] G. MAPC group ID: ID for the set of APs constituting the MAPC (e.g., 0, 1, 2, ...)

[0219] H. MAPC agreement ID: Indicates the individual ID (i.e., MAPC agreement ID) for the multi-AP agreement.

[0220] I. AP ID: An ID locally assigned by each AP within a configured group / set of multiple APs (e.g., 0, 1, 2, ...)

[0221] For example, the corresponding AP ID may be included in the AID12 field within the User Info field of the TF (Trigger Frame).

[0222] Additionally, or alternatively, the AP ID may be included within the AID12 field of the UHR Special User Info field, which may be newly defined for UHR.

[0223] For example, the corresponding AP ID may be included in the AID11 field within the STA Info field of the UHR NDP Announcement frame.

[0224] L. MAPC Schemes Type: Specifies Multi-AP cooperative transmission techniques such as Co-TDMA / SR / BF.

[0225] For example, within the MAPC element, there may be a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field, and the MAPC Schemes Info field may distinguish MAPC schemes using a Subelement ID that acts as the MAPC Type field and may include separate information.

[0226] For example, signaling can be performed as follows based on each bit value.

[0227] -> 0: Co-TDMA

[0228] -> 1: Co-SR

[0229] -> 2: Co-BF

[0230] -> ...

[0231] For example, signaling can be done based on a bitmap as follows.

[0232] -> B0: Co-TDMA

[0233] -> B1: Co-SR

[0234] -> B2: Co-BF

[0235] -> ...

[0236] For example, the corresponding Multi-AP cooperative transmission can be torn down by specifying the MAPC Scheme Type within a separate subelement that may exist for each scheme for the corresponding Multi-AP cooperative transmission technique (e.g., Co-BF / SR / TDMA / RTWT).

[0237] In other words, teardown can be performed simultaneously on one or more Multi-AP schemes using a single Teardown frame, and in this case, profiles for one or more schemes may exist.

[0238] Specifically, the MAPC Scheme Type field may be included in the MAPC Scheme Info of FIG. 24 instead of the Subelement ID field to indicate which scheme the corresponding subelement contains information about or which scheme to perform teardown on. That is, the specific scheme of the corresponding subelement can be indicated through a separate MAPC Scheme Info field instead of the Subelement ID field.

[0239] 1.3 MAPC element structure

[0240] An example of a MAPC element format containing one or more of the information presented above may be as shown in FIG. 21.

[0241] Figure 21 illustrates an example of a MAPC element format.

[0242] Referring to FIG. 21, the MAPC element includes a Length field, a MAPC Protocol Identifier field, a Link ID field, a Reason Code field, and a MAPC PMK field.

[0243] Additionally or alternatively, an example of a MAPC element format including MAPC-related ID and Type may be as shown in FIG. 22.

[0244] Figure 22 illustrates another example of the MAPC element format.

[0245] Referring to FIG. 22, the MAPC element includes a Length field, a MAPC Protocol Identifier field, a Link ID (or AP ID) field, a MAPC agreement ID (or MAPC group ID) field, a MAPC Type field, a Reason Code field, and a MAPC PMK field.

[0246] Additionally or alternatively, an example of a MAPC element format including a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field may be as shown in FIGS. 23 and FIGS. 24.

[0247] FIG. 23 illustrates an example of a MAPC element format including a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0248] Figure 23 shows an example of a MAPC element format in which Teardown is separated into one of the MAPC Type fields within the MAPC Control field, and separate MAPC Discovery, MAPC Negotiation, and MAPC Teardown frames can be defined.

[0249] Figure 24 illustrates another example of a MAPC element format including a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0250] On the other hand, FIG. 24 shows an example of a MAPC element format in which Teardown is classified as one of the MAPC Operation Types within the MAPC Scheme Control field in the MAPC Scheme Info field, indicating that the MAPC Negotiation frame was transmitted for the purpose of a specific MAPC Operation Type (e.g., Teardown). The MAPC element of FIG. 24 has the advantage of being able to perform teardown individually for each MAPC scheme.

[0251] 2. Multi-AP Coordination Teardown processing

[0252] An AP that receives a MAPC Teardown frame must reject the frame if the value of the SSID (or AP ID, Multi-AP ID) element within the frame does not match its own SSID (or the AP ID, Multi-AP ID assigned by neighboring APs in a cooperative relationship). Otherwise, it must accept the MAPC Teardown frame and discard some or all of the information exchanged for Multi-AP cooperation with the AP that transmitted the frame.

[0253] FIGS. 25 and 26 show an example of MAPC teardown based on FIGS. 23 and 24 presented in Section 1 above.

[0254] 2.1. Example of MAPC teardown operation-1

[0255] Figure 25 illustrates an example of a MAPC teardown operation.

[0256] FIG. 25 shows an example in which an individual MAPC Teardown frame is transmitted with the MAPC Type field directly designated as Teardown. Upon receiving the MAPC Teardown frame, AP 2 tears down the agreements for all MAPC schemes previously established with AP 1.

[0257] 2.2. Example of MAPC teardown operation-2

[0258] Figure 26 illustrates another example of MAPC teardown operation.

[0259] On the other hand, FIG. 26 shows an example in which a MAPC Negotiation Request frame for teardown purposes is transmitted by setting the MAPC Operation Type field, which can be included within a subelement of a specific MAPC scheme, to Teardown. Upon receiving the MAPC Negotiation Request frame, AP 2 tears down only the agreement for the corresponding MAPC scheme (i.e., Co-BF in FIG. 26) and maintains the agreement for the existing Co-SR.

[0260] This specification defines and proposes a MAPC Teardown frame transmitted by an AP that has established Multi-AP cooperation to terminate Multi-AP cooperation. Through the MAPC Teardown frame (tentative name) proposed in this specification, an AP that has established Multi-AP cooperation can terminate Multi-AP cooperation with a target AP.

[0261] A Management frame (or Action frame, Public Action frame, or MAPC Teardown frame) for the purpose of teardown in Multi-AP cooperation may belong to the Management frame.

[0262] The description of Multi-AP Coordination (MAPC) is as follows.

[0263] MAPC is a framework in which multiple APs cooperate to reduce interference, improve channel utilization efficiency, and enhance reliability and latency; key schemes may include Co-BF (Coordinated Beamforming), Co-SR (Coordinated Spatial Reuse), Co-TDMA (Coordinated TDMA), Co-RTWT (Coordinated Restricted Target Wake Time), and Co-CR (Coordinated Channel Reservation).

[0264] Common procedures for MAPC include the MAPC Discovery procedure and the MAPC Agreement Negotiation procedure. In the MAPC Discovery procedure, an AP can notify other APs of its MAPC capabilities and parameters through the MAPC Discovery Request / Response frame or the management frame. The MAPC Agreement Negotiation procedure may be a process for negotiating, establishing, updating, or terminating an agreement on a specific MAPC scheme among APs. Detailed procedures for the MAPC agreement may include forming the MAPC agreement, assigning an AP ID to identify cooperating APs, updating parameters of the existing MAPC agreement, and terminating the MAPC agreement.

[0265] FIG. 27 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0266] An example of FIG. 27 can be performed on a transmitting STA or a transmitting device (AP and / or non-AP STA).

[0267] Some of the steps (or detailed sub-steps described later) of the example in Fig. 27 may be omitted or changed.

[0268] Through step S2710, the transmitting device (transmitting STA) can obtain information regarding the above-described 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.

[0269] Through step S2720, the transmitting device can construct / generate a PPDU based on acquired control information. The step of constructing / generating the PPDU may include the step of constructing / generating each field of the PPDU. That is, step S2720 includes the step of constructing an EHT-SIG field containing control information regarding a Tone Plan. That is, step S2720 may include the step of constructing a field containing control information (e.g., N bitmap) indicating the size / location of the RU and / or the step of constructing a field containing an identifier (e.g., AID) of the STA receiving the RU.

[0270] Additionally, step S2720 may include the step of generating an STF / LTF sequence transmitted through a specific RU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence.

[0271] Additionally, step S2720 may include a step of generating a data field (i.e., MPDU) transmitted through a specific RU.

[0272] The transmitting device can transmit the PPDU configured through step S2720 to the receiving device based on step S2730.

[0273] While performing step S2730, the transmitting device may perform at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, GI insertion, etc.

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

[0275] FIG. 28 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

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

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

[0278] Some of the steps (or detailed sub-steps described later) of each example in FIG. 28 may be omitted.

[0279] A receiving device (receiving STA) can receive all or part of the PPDU through step S2810. The received signal may be in the form of FIG. 5.

[0280] The sub-step of step S2810 can be determined based on step S2730 of FIG. 27. That is, step S2810 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insert operation applied in step S2730.

[0281] In step S2820, the receiving device can perform decoding of 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.

[0282] 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 contained in the L-SIG and EHT-SIG fields. Information regarding various Tone Plans (i.e., RU) described in this specification may be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.

[0283] In step S2830, the receiving device can decode the remainder of the PPDU based on information regarding the Tone Plan (i.e., RU) obtained through step S2820. For example, the receiving STA can decode the STF / LTF fields of the PPDU based on information regarding the one Plan (i.e., RU). Additionally, the receiving STA can decode the data fields of the PPDU based on information regarding the Tone Plan (i.e., RU) and obtain the MPDU contained in the data fields.

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

[0285] Hereinafter, the above-described embodiment will be explained with reference to FIGS. 1 to 28.

[0286] FIG. 29 is a flowchart illustrating a procedure for receiving a frame to release MAPC agreement according to the present embodiment.

[0287] An example of FIG. 29 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0288] An example of FIG. 29 can be performed at a second AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be established as a coordinating AP or a coordinated AP through the MAPC negotiation.

[0289] This embodiment proposes a method for defining a frame to tear down a MAPC agreement formed through MAPC negotiation. Specifically, this embodiment proposes a method to use to tear down the MAPC agreement by defining a negotiation request frame based on the reserved value of the public action field of a public action frame.

[0290] In step S2910, the second AP (access point) receives a negotiation request frame from the first AP.

[0291] In step S2920, the second AP releases the Multi-AP Coordination (MAPC) agreement with the first AP based on the negotiation request frame.

[0292] The first AP mentioned above is a MAPC requesting AP that initiates negotiations for the MAPC agreement. The second AP mentioned above is a MAPC responding AP that responds to the MAPC requesting AP.

[0293] The above negotiation request frame is a public action frame having a first value of the public action field. The above negotiation request frame is used to release the above MAPC consensus.

[0294] The first value above may be set to one of the reserved values ​​of the common action field (e.g., 54 to 59 and 61 to 255) up to an 802.11be wireless LAN system. For example, the first value may be 69.

[0295] That is, the present embodiment proposes a method for releasing MAPC consensus by defining a negotiation request frame (or MAPC negotiation request frame) based on a public action frame. Since the negotiation request frame defined based on the public action frame can be classified as a Class 1 frame, it has the effect of being able to be transmitted between APs that are in an un-authentication and un-association relationship, or between APs that are authentic but in an un-association relationship. In addition, since there is no need to define a separate dedicated management frame in each procedure, such as discovery for MAPC and negotiation for MAPC consensus (MAPC consensus formation, MAPC consensus update, MAPC consensus release), it has the effect of being able to perform other negotiation procedures as well as release MAPC consensus based on the negotiation request frame.

[0296] A method of defining the above negotiation request frame based on the above public action frame (or the reserved value of the above public action field) may have the following effects.

[0297] 1) Ensuring standardization, compatibility, and interoperability

[0298] Since the Public Action frame contains a universal action that all STAs can understand, among management frames, if an action to release MAPC consensus is defined in the Public Action field, it can be interpreted and processed commonly across heterogeneous devices without being dependent on a specific vendor or STA.

[0299] In other words, it is possible to secure the effects of backward compatibility and multi-vendor interoperability.

[0300] 2) Simplified frame processing / Reduced signaling overhead

[0301] If identification and processing are performed within the Public Action field without defining a separate dedicated management frame, the STA / AP side can utilize the existing Public Action frame parsing procedure as is, supporting backward compatibility and reducing implementation complexity. Additionally, signaling overhead can be reduced by minimizing the extension of the frame format.

[0302] 3) Strengthening security and reliability

[0303] Since Public Action frames follow a standardized field structure, it is easy to apply frame forgery / tampering verification and integrity check procedures (e.g., MFP - Management Frame Protection).

[0304] Therefore, the reliability of tear-down signaling for release can be ensured.

[0305] In addition, the method of releasing the MAPC consensus based on the above negotiation request frame may have the following effects.

[0306] 1) Procedure Integration (Integrated Management Effect)

[0307] Previously, setup / negotiation and release / tear down could be handled by separate mechanisms; however, if these are performed integrally within the MAPC Negotiation Request frame, they can be managed within the same protocol context to simplify control procedures and enable rapid session release without unnecessary additional frame exchanges.

[0308] 2) Improvement of resource management efficiency

[0309] If tear down is performed quickly, resources allocated to the AP / STA can be rapidly returned and reallocated to new sessions or other STAs. In other words, this can have the effect of optimizing frequency / time resource utilization.

[0310] 3) Energy efficiency improvement

[0311] -> From the STA's perspective, if it clearly recognizes that the MAPC session has been released, it can immediately switch to doze mode, thereby reducing unnecessary reception waiting time. This can be a particularly meaningful effect for low-power IoT (Internet of Things) STAs.

[0312] 4) Rapid recovery from errors / crashes

[0313] In a multi-AP coordination situation where multiple APs cooperate, if a tear down is notified immediately when cooperation breaks down, interference and redundant resource occupation caused by maintaining abnormal sessions can be reduced, and a new agreement procedure can be quickly initiated.

[0314] The above negotiation request frame may include MAPC elements. The above MAPC elements may include a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0315] The above MAPC control field may include an AP ID (Identifier) ​​presence field and a reserved field. Based on the value of the AP ID presence (Present) field, an AP ID field may be optionally included in the above MAPC common information field. The above AP ID field may be used to assign an AP ID to a peer AP with which MAPC consensus has been formed.

[0316] For example, if the AP ID of the second AP and the AP ID included in the AP ID field do not match, the MAPC agreement with the second AP may be released.

[0317] The above MAPC scheme information field may include a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field.

[0318] Based on the value of the above Subelement ID field, the above MAPC technique information field can be defined as a Per-Scheme Profile subelement.

[0319] The above MAPC scheme control field may include a MAPC scheme type (Scheme Type) field. The above MAPC scheme type field may indicate a value that identifies the MAPC scheme.

[0320] The above MAPC technique request set field may include a MAPC Operation Type field. Based on the value of the MAPC Operation Type field, an operation to form the MAPC consensus, update the MAPC consensus, or release the MAPC consensus may be indicated. For example, the MAPC consensus may be formed based on the value of the MAPC Operation Type field being 0. The MAPC consensus may be updated based on the value of the MAPC Operation Type field being 1. The MAPC consensus may be released based on the value of the MAPC Operation Type field being 2.

[0321] The profile sub-elements for each of the above MAPC techniques may include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile.

[0322] The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile can be identified based on the value of the MAPC technique type field. For example, based on the value of the MAPC technique type field being 0, the Co-BF profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 1, the Co-SR profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 2, the Co-TDMA profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 3, the Co-RTWT profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 4, the Co-SR profile may be included in the profile sub-element by MAPC technique.

[0323] The above MAPC technique request set field can be defined for each of the Co-BF profile, the Co-SR profile, the Co-TDMA profile, the Co-RTWT profile, and the Co-CR profile.

[0324] Since the MAPC technique request set field is defined for each MAPC technique, the operation of forming the MAPC consensus, updating the MAPC consensus, or releasing the MAPC consensus can also be indicated for each MAPC technique based on the value of the MAPC operation type field.

[0325] For example, based on the value of the MAPC operation type field of the Co-BF profile being set to 2, the MAPC consensus may be disabled only for Co-BF. Based on the value of the MAPC operation type field of the Co-SR profile being set to 2, the MAPC consensus may be disabled only for Co-SR. Based on the value of the MAPC operation type field of the Co-TDMA profile being set to 2, the MAPC consensus may be disabled only for Co-TDMA. Based on the value of the MAPC operation type field of the Co-RTWT profile being set to 2, the MAPC consensus may be disabled only for Co-RTWT. Based on the value of the MAPC operation type field of the Co-CR profile being set to 2, the MAPC consensus may be disabled only for Co-CR.

[0326] Although the above-described embodiment only describes an operation to release a MAPC consensus where the value of the MAPC operation type field is set to 2, the value of the MAPC operation type field may be set for each MAPC technique so that a specific technique instructs to release the MAPC consensus, and another technique instructs to form or update the MAPC consensus.

[0327] For example, based on the value of the MAPC action type field of the Co-BF profile being set to 2, the MAPC consensus for Co-BF may be disabled. Conversely, based on the value of the MAPC action type field of the Co-SR profile being set to 1, the MAPC consensus for Co-SR may be updated.

[0328] After the above MAPC agreement is released, information regarding the above MAPC agreement is discarded, and the above 2 AP may be excluded from the above MAPC agreement.

[0329] The second AP may transmit a negotiation response frame to the first AP. (Or, the first AP may receive a negotiation response frame from the second AP.)

[0330] The above negotiation response frame may be a public action frame defined based on the second value of the above public action field.

[0331] The second value may be set to one of the reserved values ​​of the common action field (e.g., 54 to 59 and 61 to 255) up to an 802.11be wireless LAN system. For example, the second value may be 70.

[0332] Likewise, the above negotiation response frame may also include MAPC elements. The above MAPC elements may include a MAPC action type field. In the above negotiation response frame, the request for the negotiation request frame can be accepted, rejected, or alternated based on the value of the MAPC action type field.

[0333] The above negotiation request frame or the above negotiation response frame may include at least one of information regarding length, information regarding a MAPC protocol identifier, information regarding a Link ID, information regarding the reason for the release of the MAPC consensus, information regarding a MAPC PMK (Pairwise Master Key), information regarding the address of an AP, information regarding a group ID of the MAPC, information regarding an individual ID for the MAPC consensus, information regarding the IDs of multiple APs, or information regarding a MAPC-based transmission technique.

[0334] FIG. 30 is a flowchart illustrating the procedure for configuring a frame to release MAPC agreement according to the present embodiment.

[0335] 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0336] An example of FIG. 30 can be performed at a first AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be established as a coordinating AP or a coordinated AP through the MAPC negotiation.

[0337] This embodiment proposes a method for defining a frame to tear down a MAPC agreement formed through MAPC negotiation. Specifically, this embodiment proposes a method to use to tear down the MAPC agreement by defining a negotiation request frame based on the reserved value of the public action field of a public action frame.

[0338] In step S3010, the first AP (access point) transmits a negotiation request frame to the second AP.

[0339] In step S3020, the first AP releases the Multi-AP Coordination (MAPC) agreement with the second AP based on the negotiation request frame.

[0340] The first AP mentioned above is a MAPC requesting AP that initiates negotiations for the MAPC agreement. The second AP mentioned above is a MAPC responding AP that responds to the MAPC requesting AP.

[0341] The above negotiation request frame is a public action frame having a first value of the public action field. The above negotiation request frame is used to release the above MAPC consensus.

[0342] The first value above may be set to one of the reserved values ​​of the common action field (e.g., 54 to 59 and 61 to 255) up to an 802.11be wireless LAN system. For example, the first value may be 69.

[0343] That is, the present embodiment proposes a method for releasing MAPC consensus by defining a negotiation request frame (or MAPC negotiation request frame) based on a public action frame. Since the negotiation request frame defined based on the public action frame can be classified as a Class 1 frame, it has the effect of being able to be transmitted between APs that are in an un-authentication and un-association relationship, or between APs that are authentic but in an un-association relationship. In addition, since there is no need to define a separate dedicated management frame in each procedure, such as discovery for MAPC and negotiation for MAPC consensus (MAPC consensus formation, MAPC consensus update, MAPC consensus release), it has the effect of being able to perform other negotiation procedures as well as release MAPC consensus based on the negotiation request frame.

[0344] A method of defining the above negotiation request frame based on the above public action frame (or the reserved value of the above public action field) may have the following effects.

[0345] 1) Ensuring standardization, compatibility, and interoperability

[0346] Since the Public Action frame contains a universal action that all STAs can understand, among management frames, if an action to release MAPC consensus is defined in the Public Action field, it can be interpreted and processed commonly across heterogeneous devices without being dependent on a specific vendor or STA.

[0347] In other words, it is possible to secure the effects of backward compatibility and multi-vendor interoperability.

[0348] 2) Simplified frame processing / Reduced signaling overhead

[0349] If identification and processing are performed within the Public Action field without defining a separate dedicated management frame, the STA / AP side can utilize the existing Public Action frame parsing procedure as is, supporting backward compatibility and reducing implementation complexity. Additionally, signaling overhead can be reduced by minimizing the extension of the frame format.

[0350] 3) Strengthening security and reliability

[0351] Since Public Action frames follow a standardized field structure, it is easy to apply frame forgery / tampering verification and integrity check procedures (e.g., MFP - Management Frame Protection).

[0352] Therefore, the reliability of tear-down signaling for release can be ensured.

[0353] In addition, the method of releasing the MAPC consensus based on the above negotiation request frame may have the following effects.

[0354] 1) Procedure Integration (Integrated Management Effect)

[0355] Previously, setup / negotiation and release / tear down could be handled by separate mechanisms; however, if these are performed integrally within the MAPC Negotiation Request frame, they can be managed within the same protocol context to simplify control procedures and enable rapid session release without unnecessary additional frame exchanges.

[0356] 2) Improvement of resource management efficiency

[0357] If tear down is performed quickly, resources allocated to the AP / STA can be rapidly returned and reallocated to new sessions or other STAs. In other words, this can have the effect of optimizing frequency / time resource utilization.

[0358] 3) Energy efficiency improvement

[0359] -> From the STA's perspective, if it clearly recognizes that the MAPC session has been released, it can immediately switch to doze mode, thereby reducing unnecessary reception waiting time. This can be a particularly meaningful effect for low-power IoT (Internet of Things) STAs.

[0360] 4) Rapid recovery from errors / crashes

[0361] In a multi-AP coordination situation where multiple APs cooperate, if a tear down is notified immediately when cooperation breaks down, interference and redundant resource occupation caused by maintaining abnormal sessions can be reduced, and a new agreement procedure can be quickly initiated.

[0362] The above negotiation request frame may include MAPC elements. The above MAPC elements may include a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[0363] The above MAPC control field may include an AP ID (Identifier) ​​presence field and a reserved field. Based on the value of the AP ID presence (Present) field, an AP ID field may be optionally included in the above MAPC common information field. The above AP ID field may be used to assign an AP ID to a peer AP with which MAPC consensus has been formed.

[0364] For example, if the AP ID of the second AP and the AP ID included in the AP ID field do not match, the MAPC agreement with the second AP may be released.

[0365] The above MAPC scheme information field may include a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field.

[0366] Based on the value of the above Subelement ID field, the above MAPC technique information field can be defined as a Per-Scheme Profile subelement.

[0367] The above MAPC scheme control field may include a MAPC scheme type (Scheme Type) field. The above MAPC scheme type field may indicate a value that identifies the MAPC scheme.

[0368] The above MAPC technique request set field may include a MAPC Operation Type field. Based on the value of the MAPC Operation Type field, an operation to form the MAPC consensus, update the MAPC consensus, or release the MAPC consensus may be indicated. For example, the MAPC consensus may be formed based on the value of the MAPC Operation Type field being 0. The MAPC consensus may be updated based on the value of the MAPC Operation Type field being 1. The MAPC consensus may be released based on the value of the MAPC Operation Type field being 2.

[0369] The profile sub-elements for each of the above MAPC techniques may include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile.

[0370] The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile can be identified based on the value of the MAPC technique type field. For example, based on the value of the MAPC technique type field being 0, the Co-BF profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 1, the Co-SR profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 2, the Co-TDMA profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 3, the Co-RTWT profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 4, the Co-SR profile may be included in the profile sub-element by MAPC technique.

[0371] The above MAPC technique request set field can be defined for each of the Co-BF profile, the Co-SR profile, the Co-TDMA profile, the Co-RTWT profile, and the Co-CR profile.

[0372] Since the MAPC technique request set field is defined for each MAPC technique, the operation of forming the MAPC consensus, updating the MAPC consensus, or releasing the MAPC consensus can also be indicated for each MAPC technique based on the value of the MAPC operation type field.

[0373] For example, based on the value of the MAPC operation type field of the Co-BF profile being set to 2, the MAPC consensus may be disabled only for Co-BF. Based on the value of the MAPC operation type field of the Co-SR profile being set to 2, the MAPC consensus may be disabled only for Co-SR. Based on the value of the MAPC operation type field of the Co-TDMA profile being set to 2, the MAPC consensus may be disabled only for Co-TDMA. Based on the value of the MAPC operation type field of the Co-RTWT profile being set to 2, the MAPC consensus may be disabled only for Co-RTWT. Based on the value of the MAPC operation type field of the Co-CR profile being set to 2, the MAPC consensus may be disabled only for Co-CR.

[0374] Although the above-described embodiment only describes an operation to release a MAPC consensus where the value of the MAPC operation type field is set to 2, the value of the MAPC operation type field may be set for each MAPC technique so that a specific technique instructs to release the MAPC consensus, and another technique instructs to form or update the MAPC consensus.

[0375] For example, based on the value of the MAPC action type field of the Co-BF profile being set to 2, the MAPC consensus for Co-BF may be disabled. Conversely, based on the value of the MAPC action type field of the Co-SR profile being set to 1, the MAPC consensus for Co-SR may be updated.

[0376] After the above MAPC agreement is released, information regarding the above MAPC agreement is discarded, and the above 2 AP may be excluded from the above MAPC agreement.

[0377] The second AP may transmit a negotiation response frame to the first AP. (Or, the first AP may receive a negotiation response frame from the second AP.)

[0378] The above negotiation response frame may be a public action frame defined based on the second value of the above public action field.

[0379] The second value may be set to one of the reserved values ​​of the common action field (e.g., 54 to 59 and 61 to 255) up to an 802.11be wireless LAN system. For example, the second value may be 70.

[0380] Likewise, the above negotiation response frame may also include MAPC elements. The above MAPC elements may include a MAPC action type field. In the above negotiation response frame, the request for the negotiation request frame can be accepted, rejected, or alternated based on the value of the MAPC action type field.

[0381] The above negotiation request frame or the above negotiation response frame may include at least one of information regarding length, information regarding a MAPC protocol identifier, information regarding a Link ID, information regarding the reason for the release of the MAPC consensus, information regarding a MAPC PMK (Pairwise Master Key), information regarding the address of an AP, information regarding a group ID of the MAPC, information regarding an individual ID for the MAPC consensus, information regarding the IDs of multiple APs, or information regarding a MAPC-based transmission technique.

[0382] <Device Configuration>

[0383] The technical features of the specification described above may be applied to various devices and methods. For example, the technical features of the specification described above may be performed or supported through the device of FIG. 1 and / or FIG. 13. For example, the technical features of the specification described above may be applied only to parts of FIG. 1 and / or FIG. 13. For example, the technical features of the specification described above may be implemented based on the processing chips (114, 124) of FIG. 1, or based on the processor (111, 121) and memory (112, 122) of FIG. 1, or based on the processor (610) and memory (620) of FIG. 13. For example, the device of the specification transmits a negotiation request frame to a second AP (access point); and releases a Multi-AP Coordination (MAPC) agreement with the second AP based on the negotiation request frame.

[0384] The technical features of this specification may be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable medium comprising instructions based on execution by at least one processor.

[0385] The above CRM may store instructions for performing operations including the step of transmitting a negotiation request frame to a second AP (access point); and the step of releasing a Multi-AP Coordination (MAPC) agreement with the second AP based on the negotiation request frame. Instructions stored in the CRM of this specification may be executed by at least one processor. At least one processor associated with the CRM of this specification may be the processor (111, 121) or 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.

[0386] The technical features of the present specification described above are applicable to various applications or business models. For example, the technical features described above may be applied for wireless communication in devices supporting Artificial Intelligence (AI).

[0387] Artificial intelligence refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems addressed within the field of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0388] An Artificial Neural Network (ANN) is a model used in machine learning that can refer to any model capable of problem-solving, composed of artificial neurons (nodes) that form a network through the connection of synapses. An artificial neural network can be defined by connection patterns between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.

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

[0390] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters, on the other hand, refer to parameters that must be set prior to training in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0391] The objective of training an artificial neural network can be viewed as determining model parameters that minimize the loss function. The loss function can be used as an indicator to determine optimal model parameters during the training process of an artificial neural network.

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

[0393] Supervised learning refers to a method of training an artificial neural network with labels provided for the training data; a label can refer to the correct answer (or result) that the neural network must infer when training data is input. Unsupervised learning refers to a method of training an artificial neural network without labels provided for the training data. Reinforcement learning refers to a learning method in which an agent defined within an environment is trained to select an action or sequence of actions that maximizes the cumulative reward in each state.

[0394] Machine learning implemented using a Deep Neural Network (DNN) that includes multiple hidden layers among artificial neural networks is also called Deep Learning, and Deep Learning is a part of Machine Learning. Hereinafter, Machine Learning is used in a sense that includes Deep Learning.

[0395] In addition, the aforementioned technical features can be applied to the wireless communication of robots.

[0396] A robot can refer to a machine that automatically processes or operates a given task based on its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions can be called an intelligent robot.

[0397] Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, and propellers in their drive units, enabling them to drive on the ground or fly in the air.

[0398] In addition, the aforementioned technical features can be applied to devices that support augmented reality.

[0399] Extended Reality is a collective term for Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on real-world images, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.

[0400] MR technology is similar to AR technology in that it displays real-world objects and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual objects and real-world objects are used as equals in MR technology.

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

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

Claims

1. In a wireless LAN system, The first AP (access point) transmits a negotiation request frame to the second AP; and The above first AP includes the step of releasing the Multi-AP Coordination (MAPC) agreement with the above second AP based on the above negotiation request frame, wherein The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement method.

2. In Paragraph 1, The above negotiation request frame includes MAPC elements, and The above MAPC element includes a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field, and The above MAPC control field includes an AP ID (Identifier) ​​existence field and a reserved field, and Based on the value of the AP ID Present field, the AP ID field is optionally included in the MAPC common information field, and The above AP ID field is used to assign an AP ID to the peer AP where the above MAPC consensus has been formed. method.

3. In Paragraph 2, The above MAPC scheme information field includes a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field, and Based on the value of the above Subelement ID field, the above MAPC technique information field is defined as a Per-Scheme Profile subelement, and The above MAPC scheme control field includes a MAPC scheme type (Scheme Type) field, and The above MAPC technique type field indicates a value identifying the MAPC technique, and The above MAPC technique request set field includes a MAPC Operation Type field, and An action is indicated in which the MAPC consensus is formed, the MAPC consensus is updated, or the MAPC consensus is released based on the value of the above MAPC action type field. method.

4. In Paragraph 3, The profile sub-elements for each of the above MAPC techniques include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile. The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile are identified based on the value of the MAPC technique type field, and The above MAPC technique request set field is defined for each of the above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile. method.

5. In Paragraph 4, Based on the value of the MAPC action type field of the above Co-BF profile being set to 2, the above MAPC consensus is disabled only for Co-BF, and Based on the value of the MAPC action type field of the above Co-SR profile being set to 2, the above MAPC consensus is disabled only for Co-SR, and Based on the value of the MAPC operation type field of the above Co-TDMA profile being set to 2, the MAPC consensus is disabled only for Co-TDMA, and Based on the value of the MAPC action type field of the above Co-RTWT profile being set to 2, the above MAPC consensus is disabled only for Co-RTWT, and Based on the value of the MAPC action type field of the above Co-CR profile being set to 2, the MAPC consensus is disabled only for Co-CR. method.

6. In Paragraph 1, The above first AP further includes the step of receiving a negotiation response frame from the above second AP, wherein The above negotiation response frame is a public action frame defined based on the second value of the above public action field, and The first value is 69 and the second value is 70. method.

7. In Paragraph 1, After the above MAPC agreement is released, information regarding the above MAPC agreement is discarded, and the above 2 AP is excluded from the above MAPC agreement. method.

8. In a wireless LAN system, the first AP (access point) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: The first AP (access point) sends a negotiation request frame to the second AP; and The above-mentioned first AP releases the Multi-AP Coordination (MAPC) agreement with the above-mentioned second AP based on the above-mentioned negotiation request frame, The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement 1st AP.

9. In wireless LAN systems, The second AP (access point) receives a negotiation request frame from the first AP; and The above second AP includes the step of releasing the Multi-AP Coordination (MAPC) agreement with the first AP based on the negotiation request frame, wherein The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement method.

10. In Paragraph 9, The above negotiation request frame includes MAPC elements, and The above MAPC element includes a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field, and The above MAPC control field includes an AP ID (Identifier) ​​existence field and a reserved field, and Based on the value of the AP ID Present field, the AP ID field is optionally included in the MAPC common information field, and The above AP ID field is used to assign an AP ID to the peer AP where the above MAPC consensus has been formed. method.

11. In Paragraph 10, The above MAPC scheme information field includes a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field, and Based on the value of the above Subelement ID field, the above MAPC technique information field is defined as a Per-Scheme Profile subelement, and The above MAPC scheme control field includes a MAPC scheme type (Scheme Type) field, and The above MAPC technique type field indicates a value identifying the MAPC technique, and The above MAPC technique request set field includes a MAPC Operation Type field, and An action is indicated in which the MAPC consensus is formed, the MAPC consensus is updated, or the MAPC consensus is released based on the value of the above MAPC action type field. method.

12. In Paragraph 11, The profile sub-elements for each of the above MAPC techniques include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile. The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile are identified based on the value of the MAPC technique type field, and The above MAPC technique request set field is defined for each of the above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile. method.

13. In Paragraph 12, Based on the value of the MAPC action type field of the above Co-BF profile being set to 2, the above MAPC consensus is disabled only for Co-BF, and Based on the value of the MAPC action type field of the above Co-SR profile being set to 2, the above MAPC consensus is disabled only for Co-SR, and Based on the value of the MAPC operation type field of the above Co-TDMA profile being set to 2, the MAPC consensus is disabled only for Co-TDMA, and Based on the value of the MAPC action type field of the above Co-RTWT profile being set to 2, the above MAPC consensus is disabled only for Co-RTWT, and Based on the value of the MAPC action type field of the above Co-CR profile being set to 2, the MAPC consensus is disabled only for Co-CR. method.

14. In Paragraph 9, The above second AP further includes the step of transmitting a negotiation response frame to the above first AP, wherein The above negotiation response frame is a public action frame defined based on the second value of the above public action field, and The first value is 69 and the second value is 70. method.

15. In Paragraph 9, After the above MAPC agreement is released, information regarding the above MAPC agreement is discarded, and the above 2 AP is excluded from the above MAPC agreement. method.

16. In a wireless LAN system, the second AP (access point) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Receive a negotiation request frame from the 1st AP; and Release the agreement between the first AP and the Multi-AP Coordination (MAPC) based on the above negotiation request frame, The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement 2nd AP.

17. At least one computer-readable medium comprising an instruction based on execution by at least one processor, A step of transmitting a negotiation request frame to a second AP (access point); and The method includes the step of releasing the Multi-AP Coordination (MAPC) agreement with the second AP based on the negotiation request frame, wherein The first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement Recording media.

18. In a device in a wireless LAN system, Memory; and The processor comprises the above memory and operablely coupled thereto, wherein the processor is: Sending a negotiation request frame to the second AP (access point); and Based on the above negotiation request frame, the above 2nd AP and Multi-AP Coordination (MAPC) agreement shall be terminated, The first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP, and The above negotiation request frame is a public action frame having a first value of a public action field, and The above negotiation request frame is used to release the above MAPC agreement device.

Images