Trigger frame design for TXOP sharing in multi-AP cooperation in wireless LAN system

Abstract

The present disclosure relates to a trigger frame design for transmission opportunity (TXOP) sharing in multi-access point (AP) cooperation in a wireless LAN system. According to an embodiment of the present disclosure, a method performed by a first AP in a wireless LAN system comprises the steps of: performing, with a second AP, a negotiation procedure for multi-AP cooperation; receiving, from the second AP, a TXOP sharing frame including information about TXOP sharing in the multi-AP cooperation; acquiring information related to an allocation period for the first AP from the TXOP sharing frame; and performing frame exchange in the allocation period.

Description

Trigger Frame Design for TXOP Sharing in Multi-AP Cooperation in Wireless LAN Systems

[0001] The present disclosure relates to a trigger frame design for transmission opportunity (TXOP) sharing in multi-AP (access point) cooperation in a wireless LAN system.

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs. To this end, various technologies are being considered to support high throughput, low latency, and extended range. For example, APs can perform negotiation procedures for multi-AP cooperation and share TXOPs among APs. Accordingly, a trigger frame design for TXOP sharing in multi-AP cooperation is required.

[0003] The present disclosure provides a method and device for designing a trigger frame for TXOP sharing in multi-AP cooperation in a wireless LAN system.

[0004] According to an embodiment of the present disclosure, a method performed by a first AP in a wireless LAN system includes the steps of: performing a negotiation procedure for multi-AP cooperation with a second AP; receiving, from the second AP, a TXOP (transmission opportunity) shared frame including information on sharing of TXOP in the multi-AP cooperation; obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

[0005] According to an embodiment of the present disclosure, a method performed by a second AP in a wireless LAN system includes the steps of: performing a negotiation procedure for multi-AP cooperation with a first AP; and transmitting, to the first AP, a TXOP (transmission opportunity) shared frame including information about TXOP sharing in the multi-AP cooperation, wherein the first AP is configured to perform operations including: obtaining information related to an allocation period for the first AP from the TXOP shared frame; and performing frame exchange in the allocation period.

[0006] In various embodiments, devices for implementing the above-described methods are provided.

[0007] The present disclosure may have various advantageous effects.

[0008] For example, according to various embodiments of the present disclosure, the structure and / or format of a trigger frame transmitted by a SAP to share a TXOP with a DAP in a Co-TDMA operation may be defined. Using the trigger frame provided in the present disclosure, the SAP may perform / initiate a TXOP sharing procedure to share a TXOP with the DAP.

[0009] The beneficial effects that can be achieved through specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, various technical effects may be understood and / or derived from the present disclosure by those skilled in the art. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure.

[0010] FIG. 1 illustrates an example of a transmitting device and / or a receiving device of the present disclosure.

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

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

[0013] Figure 4 illustrates an embodiment of multi-link (ML).

[0014] FIG. 5 illustrates a modified example of a transmitting device and / or a receiving device of the present disclosure.

[0015] FIG. 6 illustrates an example of a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of the present disclosure.

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

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

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

[0019] Figure 10 shows the operation according to UL-MU.

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

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

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

[0023] Figure 14 illustrates an example of a procedure related to NAV setting.

[0024] Figure 15 shows the trigger frame format.

[0025] Figure 16 shows an example of the user information field format of MU-RTS TXS TF.

[0026] Figure 17 shows an example of operation when the value of the TXOP shared mode subfield is 2.

[0027] Figure 18 shows an example of a single TXOP-based coordinated time division multiple access (Co-TDMA) operation diagram between cooperating APs.

[0028] FIG. 19 illustrates an example of a method performed by a first AP according to an embodiment of the present disclosure.

[0029] FIG. 20 illustrates an example of signal flow between a first AP and a second AP according to an embodiment of the present disclosure.

[0030] FIG. 21 illustrates an example of a frame format based on TXS mode 2 according to an embodiment of the present disclosure.

[0031] FIG. 22 illustrates an example of a frame format based on a novel TXS mode according to an embodiment of the present disclosure.

[0032] FIG. 23 illustrates an example of a MAP trigger frame format according to an embodiment of the present disclosure.

[0033] FIG. 24 illustrates an example of a MAP-RTS trigger frame format according to an embodiment of the present disclosure.

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

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

[0036] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

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

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

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

[0040] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

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

[0042] In order to explain the technical features of the present disclosure, technical features to which the present disclosure can be applied are described below.

[0043] FIG. 1 illustrates an example of a transmitting device and / or a receiving device of the present disclosure.

[0044] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present disclosure may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present disclosure may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present disclosure may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

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

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

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

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

[0049] The first STA (110) may include a processor (111), a memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.

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

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

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

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

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

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

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

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

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

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

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

[0061] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] Figure 4 illustrates an example of multi-link (ML).

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

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

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

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

[0087] The specific features of the present disclosure 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.

[0088] FIG. 5 illustrates a modified example of a transmitting device and / or a receiving device of the present disclosure.

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

[0090] The processor (510) of FIG. 5 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (510) of FIG. 5 may be identical to the processing chip (114, 124) of FIG. 1.

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

[0092] Referring to FIG. 5, a power management module (511) manages power to a processor (510) and / or a transceiver (530). A battery (512) supplies power to the power management module (511). A display (513) outputs results processed by the processor (510). A keypad (514) receives input to be used by the processor (510). The keypad (514) may be displayed on the display (513). A SIM card (515) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0093] Referring to FIG. 5, the speaker (540) can output sound-related results processed by the processor (510). The microphone (541) can receive sound-related input to be used by the processor (510).

[0094] FIG. 6 illustrates an example of a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of the present disclosure.

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

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

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

[0098] Each block illustrated in Fig. 6 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 6, 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.

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

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

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

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

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

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

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

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

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

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

[0109] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0131] Figure 9 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of the resource units (RUs) used in the present disclosure may vary. For example, the layout of the resource units (RUs) used in the 80MHz band may vary.

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

[0133] TB PPDUs (1041, 1042) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (1030). The ACK frame (1050) for the TB PPDU can be implemented in various forms. For example, the ACK frame (1050) for the TB PPDU can be implemented in the form of a BA (block ACK).

[0134] In FIG. 10, transmission(s) of a Trigger Frame (1030), a TB PPDU (1041, 1042) and / or an ACK frame (1050) may be performed within a TXOP (1025).

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

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

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

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

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

[0140] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 12 are subject to change.

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

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

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

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

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

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

[0147] Meanwhile, STAs that have data to transmit can perform CCA (clear channel assessment) to sense the medium for a specific period (e.g., DIFS (distributed coordination function (DCF) inter-frame space)) before transmitting the data. At this time, if the medium is idle, the STA can perform transmission using the medium. However, if the medium is busy, it can be assumed that multiple STAs are already waiting to use the medium, and the STA can transmit data after waiting for a random backoff period in addition to the DIFS. The random backoff period helps avoid collisions because, assuming that there are multiple STAs to transmit data, each STA will have a different backoff period value probabilistically, resulting in different transmission times. Once one STA starts transmitting, other STAs cannot use the medium.

[0148] In a random backoff procedure, when a specific medium changes from busy to idle, multiple STAs begin preparing to transmit data. To minimize collisions, each STA wishing to transmit data selects a random backoff count and waits for the slot time corresponding to the selected counter. The random backoff count is a pseudo-random integer value, and one of the values ​​is uniformly distributed in the range [0 CW]. CW stands for contention window. The CW parameter takes the CWmin value as the initial value, but if transmission fails, the value is doubled. For example, if an ACK response is not received for a transmitted data frame, it can be considered a collision. When the CW value reaches the CWmax value, the CWmax value is maintained until the data transmission is successful, and if the data transmission is successful, the CW value is reset to the CWmin value. At this time, CW, CWmin, and CWmax are set for convenience of implementation and operation. can be expressed as . Meanwhile, when the random backoff procedure starts, the STA selects a random backoff count within the range [0 CW] and continuously monitors the medium while the backoff slot is counting down. If the medium becomes busy during this time, the countdown is stopped, and when the medium becomes idle again, the countdown for the remaining backoff slots is resumed.

[0149] Figure 14 illustrates an example of a procedure related to NAV setting.

[0150] Referring to FIG. 14, when a Source (e.g., AP STA / non-AP STA) that wants to transmit data transmits an RTS (request to send) frame to a Destination (e.g., AP STA / non-AP STA) that receives the data, the Destination can notify surrounding terminals that it will receive the data by transmitting a CTS (clear to send) frame. In other words, the Destination designated as a receiver through the RTS frame can transmit a CTS frame. If the Source that transmitted the RTS frame receives the CTS frame, the Source can start transmitting data to the Destination.

[0151] Meanwhile, if an STA other than the Destination designated as the receiver through the RTS frame receives the RTS frame, or if an STA other than the Source that transmitted the RTS frame receives the CTS frame, the STA may set a network allocation vector (NAV). An STA that has set a NAV may not transmit data during the NAV period, thereby avoiding collisions between the STA and the Source / Destination. On the other hand, if the Destination designated as the receiver through the RTS frame receives the RTS frame, or if the Source that transmitted the RTS frame receives the CTS frame, the Source / Destination does not set a NAV.

[0152] If a CTS frame (e.g., PHY-RXSTART.indication primitive) is not received within a certain period from the time when the RTS frame is received (e.g., the time when the MAC receives the PHY-RXEND.indication primitive corresponding to the RTS frame), STAs that have set or updated the NAV through the RTS frame may reset the NAV (e.g., 0). The certain period may be (2*aSIFSTime + CTS_Time + aRxPHYStartDelay + 2*aSlotTime). The CTS_Time may be calculated based on the length of the CTS frame and the data rate indicated by the RTS frame.

[0153] In Fig. 14, for convenience, setting or updating NAV through RTS frame or CTS frame is illustrated, but NAV setting / resetting / updating may also be performed based on the ¡ field (e.g., duration field in MAC header of MAC frame) of various other frames, for example, non-HT PPDU, HT PPDU, VHT PPDU or HE PPDU. For example, if the RA field in the received MAC frame does not match its own address (e.g., MAC address), the STA may set / reset / update NAV based on the value of the duration field in the received MAC frame.

[0154] Non-AP STAs must maintain two NAVs, and APs can maintain two NAVs: an intra-BSS NAV and a basic NAV. The intra-BSS NAV can be updated / set by PPDUs within the BSS. The basic NAV can be updated / set by inter-BSS PPDUs, or PPDUs that cannot be classified as inter-BSS or intra-BSS.

[0155] The MAC frames included in the data field of the PPDU of the present disclosure can be classified into various types. For example, the MAC frames of the present disclosure can be classified into a control frame, a management frame, and a data frame.

[0156] For example, the management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLAN. For the management frame, the values ​​of the type fields (B3 and B2) of the MAC header are set to 00. In addition, the values ​​of the subtype fields (B7, B6, B5, B4) of the MAC header are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).

[0157] For example, the control frame includes Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLAN. For the control frame, the value of the type field (B3 and B2) of the MAC header is set to 01. Additionally, the values ​​of the subtype fields (B7, B6, B5, B4) of the MAC header are as follows: Trigger (0010), Beamforming Report Poll (0100), NDP Announcement (0101), Control Frame Extension (0110), Control Wrapper (0111), BlockAckReq (1000), BlockAck (1001), PS-Poll (1010), RTS (1011), CTS (1100), Ack (1101), CF-End (1110).

[0158] For example, the data frame includes (QoS) Data, (QoS) Null, etc. defined in conventional WLAN. For the data frame, the value of the type field (B3 and B2) of the MAC header is set to 10.

[0159] The type of the MAC frame used in the present disclosure can be identified through the type field / information and the subtype field / information included in the frame control field of the header of the MAC frame (i.e., the MAC header). For example, the “trigger frame” of the present disclosure can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 bits in the frame control field are also set to 0010. Various MAC frames described in the present disclosure are inserted / included in the data field of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).

[0160] Figure 15 illustrates a trigger frame format. The trigger frame format may also be referred to as the structure of a trigger frame.

[0161] Referring to FIG. 15, a trigger frame may include a frame control field, a duration / ID field, a receiver address (RA) field, a transmitter address (TA) field, a common info field, a user info list field, a padding field, and / or a frame check sequence (FCS) field. Optionally, the trigger frame may further include a special user info field between the common info field and the user info list field. The user info list field may include one or more user info fields. The frame control field, the duration / ID field, the RA field, and the TA field may constitute a MAC header.

[0162] For example, the common information field may include a trigger type subfield. The trigger type subfield value may indicate a trigger frame variant, as shown in Table 1:

[0163] Trigger type subfield valueTrigger frame variant0Basic1Beamforming Report Poll (BFRP)2MU-BAR3MU-RTS4Buffer Status Report Poll (BSRP)5GCR MU-BAR6Bandwidth Query Report Poll (BQRP)7NDP Feedback Report Poll (NFRP)8Ranging9-15Reserved

[0164] For example, if the value of the trigger type subfield is set to 0, the trigger frame may be a basic trigger frame. For example, if the value of the trigger type subfield is set to 3, the trigger frame may be a MU (multi-user) RTS trigger frame. Meanwhile, according to the EHT (or 802.11be) standard, in order to support peer-to-peer (P2P) transmission to a non-AP STA, an AP may allocate a portion of the time interval within the TXOP acquired by the AP. In order to allocate a portion of the time interval within the TXOP, a TXOP Sharing Mode subfield may be defined within the Common Info Field of the MU-RTS trigger frame. When the value of the TXOP Sharing Mode subfield is non-zero, such an MU-RTS trigger frame may be referred to as an MU-RTS TXOP Sharing (TXS) trigger frame (TF). The values ​​of the TXOP Sharing Mode subfield are described in Table 2 below:

[0165] Triggered TXOP Sharing Mode subfield valueDescription0MU-RTS that does not initiate MU-RTS TXOP sharing procedure.1MU-RTS that initiates MU-RTS TXOP sharing procedure wherein a scheduledSTA can only transmit MPDU(s) addressed to its associated AP.2MU-RTS that initiates MU-RTS TXOP sharing procedure wherein a scheduled STA can transmit MPDU(s) addressed to its associated AP or addressed to another STA.3Reserved.

[0166] For example, if the value of the TXOP shared mode subfield is 1, one or more (non-TB) PPDU transmissions to the AP may be supported. If the value of the TXOP shared mode subfield is 2, not only (non-TB) PPDU transmissions to the AP but also P2P transmissions may be supported. In the present disclosure, the MU-RTS TXS TF may also be briefly referred to as a TXS trigger frame.

[0167] Figure 16 shows an example of the user information field format of MU-RTS TXS TF.

[0168] Referring to FIG. 16, the user information field may include an AID subfield, an RU allocation subfield, an allocation duration subfield, reserved bits, and / or a PS160 subfield.

[0169] The AID subfield may indicate the AID for the corresponding STA. The RU allocation subfield may indicate RU allocation for the corresponding STA.

[0170] The allocation interval subfield can contain 9 bits from B20 to B28 in the MU-RTS TXS TF and can indicate an allocation interval in units of 16us. In this case, the maximum length of the allocation interval that can be indicated by the allocation interval subfield can be 2^9= 8192us.

[0171] The PS160 subfield may indicate the primary 160MHz channel or the second 160MHz channel to which RU or MRU allocation applies.

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

[0173] In this disclosure, multi-AP operation is proposed. Multi-AP operation may be based on a technique for reducing various interferences, such as inter-symbol interference (ISI), through coordination with neighboring APs (e.g., APs located in overlapping BSSs).

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

[0175] In this disclosure, “multi-AP (cooperative) operation” may also be referred to as “multi-AP (cooperative) transmission.” Furthermore, “multi-AP (cooperative) operation / transmission” and “multi-AP cooperative scheme (or cooperative scheme)” may be used interchangeably.

[0176] Figure 17 shows an example of operation when the value of the TXOP shared mode subfield is 2.

[0177] Referring to FIG. 17, an AP may transmit an MU-RTS TXS TF including allocation (time) interval information (e.g., Time allocated in MU-RTS TXS Trigger Frame) to non-AP STA 1. Non-AP STA 1 may transmit a CTS in response to the MU-RTS TXS TF and perform P2P transmission to non-AP STA 2.

[0178] When the triggered TXOP sharing protocol is utilized for multi-AP coordination, transmissions within the BSS of each cooperative AP are divided into time units, so that each cooperative AP can perform frame exchange without affecting other cooperative APs.

[0179] In the present disclosure, "frame exchange (FE)" may include frame transmission and / or reception operations between STAs. The STAs may be APs or non-AP STAs. Here, the frames may include various types of frames (e.g., data frames, control frames, management frames).

[0180] Figure 18 shows an example of a single TXOP-based coordinated time division multiple access (Co-TDMA) operation diagram between cooperating APs.

[0181] For example, Co-TDMA could mean that each cooperating AP exchanges frames without affecting other cooperating APs by separating transmissions within the BSS of each cooperating AP into time units.

[0182] When the triggered TXS protocol is applied to a multi-AP cooperative operation, an AP in the triggered TXS protocol may be an AP that shares a TXOP in the multi-AP cooperative operation, and an STA in the triggered TXS protocol may be an AP that shares a TXOP in the multi-AP cooperative operation. In the present disclosure, an AP that shares a TXOP may be referred to as a SAP (sharing AP), and an AP that receives a TXOP from a SAP may be referred to as a DAP (shared AP). Here, the term SAP does not limit that the entity that shares a TXOP is only an AP STA, and a SAP may also include a non-AP STA that shares a TXOP. In addition, the term DAP does not limit that the entity that shares a TXOP is only an AP STA, and a DAP may also include a non-AP STA that shares a TXOP (or performs transmission and reception with an AP STA that shares a TXOP). Additionally, the frame exchange performed by the DAP with a non-AP STA or SAP belonging to the DAP BSS during the allocated time (i.e., the allocated period for DAP / AP2 within the TXOP indicated by the MU-RTS TXS TF transmitted from the SAP, which is the time allocated in the MU-RTS TXS TF in FIG. 16) may be referred to as a BSS frame exchange (FE) of the DAP. For example, the RTS / CTS frame exchange between the DAP and the non-AP STA followed by data frame transmission and block ACK frame response, UL data frame transmission of non-AP STAs by a trigger frame transmitted from the DAP, and / or data frame transmission of the DAP by a trigger frame transmitted from the SAP may be performed.

[0183] In order for multi-AP cooperation to be achieved between two APs, the two APs must be in a connected / bonded state, and / or a negotiation procedure must be performed in advance to exchange capability information / requirement information between them, and then multi-AP transmission (e.g., Co-TDMA (coordinated time division multiple access), C-OFDMA (coordinated orthogonal frequency division multiple access), Co-SR (coordinated spatial reuse), Co-BF (coordinated beamforming), AP selection, or J-TX (joint transmission)) can be performed based on the obtained information. In other words, in order for multi-AP transmission to be performed smoothly, a negotiation procedure for configuring / managing multi-AP cooperation and / or transmitting based on a specific multi-AP cooperation method must be performed in advance between the above-described SAP and DAP. A multi-AP set can be set up / configured through the negotiation procedure. Therefore, the negotiation procedure may also be referred to as a multi-AP set setup / configuration procedure.

[0184] For successful multi-AP cooperation, a multi-AP selection procedure may be performed to select a DAP with which the SAP wishes to share TXOPs within a multi-AP set established / configured through a negotiation procedure and / or to notify that the TXOPs will be shared. Through the multi-AP selection procedure, the SAP can determine whether a DAP requires TXOP sharing within the acquired TXOPs, and if a specific DAP does not require TXOP sharing, it can decide to share the TXOPs with subsequent / other DAPs. Alternatively, the SAP can simply notify the target DAPs that it intends to share TXOPs during the multi-AP selection procedure, thereby enabling multi-AP cooperation while reducing the overhead caused by the multi-AP selection procedure.

[0185] In a multi-AP selection procedure, a SAP can send a request frame (i.e., a request frame for AP selection) to select a DAP with which to share a TXOP from a set of multi-APs established / configured through a negotiation procedure, and a DAP that receives the request frame can send a response frame (i.e., a response frame for AP selection) to the request frame based on whether TXOP sharing is required. If a response frame is received from a DAP indicating that TXOP sharing is not required, or if a response frame is not received from a DAP, the SAP can send a request frame for AP selection to another DAP - i.e., the SAP can perform AP reselection. Alternatively, the SAP can simply inform the target DAPs that it intends to share a TXOP in the multi-AP selection procedure. For example, the SAP can send an AP selection request frame without soliciting a response frame to the target DAPs with which it wishes to share a TXOP, and the DAP that receives such an AP selection request frame can prepare for the intended TXOP sharing.

[0186] The SAP transmits a frame for TXOP sharing (e.g., TXOP sharing frame / MU-RTS TXS trigger frame) to the selected DAP through a multi-AP selection procedure, and the DAP can exchange frames with non-AP STA(s) connected to the DAP in the time interval (e.g., allocation interval) allocated by the TXOP sharing frame.

[0187] Meanwhile, since TXOPs are shared between APs in Co-TDMA operation, the trigger frame that SAP transmits to DAP needs to be newly designed in order to perform the TXOP sharing procedure using the triggered TXS protocol.

[0188] Accordingly, according to various embodiments of the present disclosure, the structure and / or format of a trigger frame transmitted by a SAP to share a TXOP with a DAP in Co-TDMA operation is defined. Using the trigger frame proposed in the present disclosure, a SAP can initiate a TXOP sharing procedure to share a TXOP with a DAP.

[0189] The specific designations / names proposed in this disclosure may be changed and are not limited thereto.

[0190] FIG. 19 illustrates an example of a method performed by a first AP according to an embodiment of the present disclosure. In FIG. 19, the first AP may be a DAP, and the second AP may be a SAP.

[0191] Referring to FIG. 19, in step S1901, the first AP can perform a negotiation procedure for multi-AP cooperation with the second AP.

[0192] In step S1903, the first AP may receive a TXOP sharing frame including information about TXOP sharing in multi-AP cooperation from the second AP.

[0193] In step S1905, the first AP can obtain information related to the allocation interval for the first AP from the TXOP shared frame.

[0194] In step S1907, the first AP can perform frame exchange in the allocated interval.

[0195] According to various embodiments, information about TXOP sharing in multi-AP cooperation may include information indicating that the TXOP sharing is TXOP sharing for multi-AP cooperation between APs. Information about TXOP sharing in multi-AP cooperation may include at least one of a TXOP sharing mode, an ID (identifier) ​​associated with the first AP, or an address of the first AP.

[0196] According to various embodiments, the TXOP shared mode may be included in the common information field of the TXOP shared frame.

[0197] According to various embodiments, the value of the TXOP sharing mode may be set to 2. The TXOP sharing mode with the value set to 2 may indicate that a TXOP sharing procedure is initiated, through which the STA can transmit data to the connected AP or another STA.

[0198] According to various embodiments, the value of the TXOP sharing mode may be set to 1. The TXOP sharing mode with the value set to 1 may indicate that a TXOP sharing procedure is initiated, through which the AP can transmit data to the connected STA.

[0199] According to various embodiments, the value of the TXOP sharing mode may be set to a value greater than or equal to 3 using at least one reserved bit. The TXOP sharing mode set to a value greater than or equal to 3 may indicate that a TXOP sharing procedure is initiated, in which an AP in a multi-AP cooperative relationship can transmit data to an associated STA.

[0200] According to various embodiments, the ID associated with the first AP may be included in the AID (association ID)12 field of the user information field of the TXOP shared frame. The ID associated with the first AP may include at least one of the BSS (basic service set) ID of the first AP, the BSS color of the first AP, the ID of the multi-AP group to which the first AP belongs, or the ID for the first AP assigned by the second AP within the multi-AP group.

[0201] According to various embodiments, the address of the first AP may be included in the RA (receiver address) field of the TXOP shared frame.

[0202] According to various embodiments, the TXOP shared frame may further include at least one of information about a multi-AP cooperation method, information about whether a TXOP return is required, information about whether a medium reservation is required, information about a cooperation priority, information about whether transmission of a response frame to the TXOP shared frame is required, information about whether a clear to send (CTS) frame is transmitted after the TXOP shared frame is transmitted, information about whether NAV reset is disabled when a NAV timeout expires, information about an address of the first AP, or an ID locally assigned to the first AP within the multi-AP group to which the first AP belongs.

[0203] According to various embodiments, the trigger frame may be a multi-user (MU)-request to send (RTS) TXOP sharing (TXS) trigger frame.

[0204] FIG. 20 illustrates an example of signal flow between a first AP and a second AP according to an embodiment of the present disclosure. In FIG. 20, the first AP may be a DAP, and the second AP may be a SAP.

[0205] Referring to FIG. 20, in step S2001, the second AP can perform a negotiation procedure for multi-AP cooperation with the first AP.

[0206] In step S2003, the second AP may transmit a TXOP sharing frame including information about TXOP (transmission opportunity) sharing in multi-AP cooperation to the first AP.

[0207] In step S2005, the first AP can obtain information related to the allocation interval for the first AP from the TXOP shared frame.

[0208] In step S2007, the first AP may perform operations including an operation of performing frame exchange in the allocated interval.

[0209] According to various embodiments, information about TXOP sharing in multi-AP cooperation may include information indicating that the TXOP sharing is TXOP sharing for multi-AP cooperation between APs. Information about TXOP sharing in multi-AP cooperation may include at least one of a TXOP sharing mode, an ID (identifier) ​​associated with the first AP, or an address of the first AP.

[0210] According to various embodiments, the TXOP shared mode may be included in the common information field of the TXOP shared frame.

[0211] According to various embodiments, the ID associated with the first AP may be included in the AID (association ID)12 field of the user information field of the TXOP shared frame. The ID associated with the first AP may include at least one of the BSS (basic service set) ID of the first AP, the BSS color of the first AP, the ID of the multi-AP group to which the first AP belongs, or the ID for the first AP assigned by the second AP within the multi-AP group.

[0212] According to various embodiments, the address of the first AP may be included in the RA (receiver address) field of the TXOP shared frame.

[0213] According to various embodiments, the TXOP shared frame may further include at least one of information about a multi-AP cooperation method, information about whether a TXOP return is required, information about whether a medium reservation is required, information about a cooperation priority, information about whether transmission of a response frame to the TXOP shared frame is required, information about whether a clear to send (CTS) frame is transmitted after the TXOP shared frame is transmitted, information about whether NAV reset is disabled when a NAV timeout expires, information about an address of the first AP, or an ID locally assigned to the first AP within the multi-AP group to which the first AP belongs.

[0214] Below, a detailed implementation of the trigger frame design for TXOP sharing in multi-AP operation is described.

[0215] According to various embodiments of the present disclosure, a trigger frame transmitted by a SAP to a DAP to share a TXOP in transmissions based on multi-AP cooperation (e.g., Co-TDMA) may be defined. The structure and / or format of the trigger frame for multi-AP cooperation and / or Co-TDMA proposed in the present disclosure is described in detail below.

[0216] I. MU-RTS TXS Trigger Frame

[0217] In some implementations, the trigger frame that can be transmitted for multi-AP cooperation and / or TXOP sharing in Co-TDMA can be designed by utilizing the MU-RTS TXS TF used in the triggered TXOP sharing protocol of EHT.

[0218] I-1. MU-RTS TXS trigger frame based on legacy TXS mode

[0219] In some implementations, MU-RTS TXS TF in TXOP sharing for Co-TDMA may be utilized based on existing triggered TXOP sharing modes (i.e., mode = 1 or 2) as shown in . For example, since the existing TXS mode = 2 allows a time-allocated STA to forward MPDU(s) to other STAs, TXS mode = 2 may be applied to allow a DAP to forward MPDU(s) to other STAs.

[0220] MU-RTS TXS TF based on existing TXS mode can be defined and / or designed according to the following options:

[0221] Option 1) The trigger frame for TXOP sharing in Co-TDMA is based on TXS mode = 2, and no (new) fields related to multi-AP cooperation and / or Co-TDMA-based transmission are added separately.

[0222] Option 2) The trigger frame for TXOP sharing in Co-TDMA is based on TXS mode = 2, and (new) fields related to multi-AP cooperation and / or Co-TDMA based transmission may be added separately.

[0223] For example, in option 2), one or more fields (e.g., A to J) below may be added and / or defined within the MU-RTS TXS TF, and the specific designation (name) of one or more of the fields may be changed.

[0224] A. Multi-AP cooperation type: Information about multi-AP cooperation methods such as C-OFDMA, Co-TDMA, J-TX, and Co-SR. For example, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field may be utilized. For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits according to the number of multi-AP cooperation methods) in the EHT reserved bit (7 bits). For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits according to the number of multi-AP cooperation methods) in the reserved bit (4 bits).

[0225] B. Co-TDMA Operation: Indicates that TXOP is shared for Co-TDMA operation. For example, the EHT reserved bit (bit 7) or the reserved bit (bit 4) of the common information field may be utilized. For example, a new field may be defined to indicate that Co-TDMA operation is in progress by utilizing 1 bit in the EHT reserved bit (bit 7). For example, a new field may be defined to indicate that Co-TDMA operation is in progress by utilizing 1 bit in the reserved bit (bit 4) (e.g., B22 of the EHT variant common information field). In the above examples, i) bit 0 may indicate that the corresponding MU-RTS TXS TF is not for Co-TDMA operation, and ii) bit 1 may indicate that the corresponding MU-RTS TXS TF is for Co-TDMA operation.

[0226] C. TXOP Return Required: Indicates whether the TXOP return procedure must be performed within the allocated time. For example, this field may indicate to the DAP that it supports transmitting frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field may indicate that the DAP must transmit frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field may indicate that the DAP must transmit frames containing information about the SAP (e.g., the AID of the SAP, a new AID defined for multi-AP cooperation) within the allocated time.

[0227] In some implementations, the EHT Reserved Bit (7 bits) or Reserved Bit (4 bits) may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the EHT Reserved Bit (7 bits). For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the Reserved Bit (4 bits).

[0228] In some implementations, the reserved bits (10 bits) of the User Information field may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (10 bits).

[0229] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the TXOP return request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (3 bits).

[0230] In the examples described above, i) bit 0 may indicate that the DAP does not have to perform a TXOP return within the allocated time, and ii) bit 1 may indicate that the DAP must perform a TXOP return within the allocated time.

[0231] D. Medium Reservation Requirement: Indicates whether the DAP supports and / or must perform the NAV setup sequence with SAP. For example, this field may indicate whether the DAP can send an MU-RTS TXS TF (i.e., a frame for SAP-side medium reservation and / or NAV setup) to SAP for the NAV setup sequence at the time allocated by SAP.

[0232] In some implementations, the EHT Reserved Bit (7 bits) or Reserved Bit (4 bits) may be utilized for the Media Reservation Request field. For example, a new field may be defined to indicate media reservation support and / or request by utilizing one bit in the EHT Reserved Bit (7 bits). For example, a new field may be defined to indicate media reservation support and / or request by utilizing one bit in the Reserved Bit (4 bits).

[0233] In some implementations, the reserved bits (10 bits) of the user information field may be utilized for the media reservation request field. For example, a new field may be defined to indicate media reservation support and / or request by utilizing 1 bit in the reserved bits (10 bits).

[0234] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the media reservation request field. For example, a new field may be defined to indicate media reservation support and / or request by utilizing 1 bit of the reserved bits (3 bits).

[0235] In the examples described above, i) bit 0 may indicate that the DAP does not need to perform media reservation within the allocated time, and ii) bit 1 may indicate that the DAP must perform media reservation within the allocated time.

[0236] E. Cooperation Priority: It can indicate the priority of the currently used cooperation method among the multi-AP cooperation methods, and / or indicate the priority / protection level for efficiently performing Co-TDMA operation.

[0237] For example, the EHT reserved bit (7 bits) or reserved bit (4 bits) of the common information field can be utilized for the cooperative priority field. For example, two bits of the EHT reserved bit (7 bits) or reserved bit (4 bits) can indicate the priority / protection level of the current Co-TDMA operation. Bit 0 can indicate cooperative transmission with priority / protection level 0. This can mean that no separate protection for TXOP sharing and / or TXOP return is required in Co-TDMA operation. Bit 1 can indicate cooperative transmission with priority / protection level 1-1. This can mean that separate protection for TXOP sharing is required in Co-TDMA operation. Bit 2 can indicate cooperative transmission with priority / protection level 1-2. This can mean that separate protection for TXOP return is required in Co-TDMA operation. Bit 3 may indicate cooperative transmission with priority / protection level 2. This may mean that protection is required for both TXOP sharing and TXOP return in Co-TDMA operation.

[0238] F. CTS Request: Indicates whether a CTS frame should be transmitted in response to a MU-RTS TXS TF (i.e., whether solicited / unsolicited).

[0239] In some implementations, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field may be utilized for the CTS request field. For example, one bit of the EHT reserved bit (7 bits) may indicate whether transmission of a CTS frame is requested. For example, one bit of the reserved bit (4 bits) may indicate whether transmission of a CTS frame is requested.

[0240] In some implementations, the reserved bits (10 bits) of the user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (10 bits) may indicate whether transmission of a CTS frame is requested.

[0241] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (3 bits) may indicate whether transmission of a CTS frame is requested.

[0242] In the examples described above, i) bit 0 may indicate that transmission of a CTS frame is induced for transmission of the corresponding MU-RTS TXS TF (i.e., indicates that a CTS frame must be transmitted), and ii) bit 1 may indicate that transmission of a CTS frame is not induced for transmission of the corresponding MU-RTS TXS TF (i.e., indicates that a CTS frame does not need to be transmitted).

[0243] G. More CTS: It can indicate whether to transmit a CTS frame (or CTS-to-Self frame) within a certain time. For example, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field can be utilized for the More CTS field. For example, one bit of the EHT reserved bit (7 bits) or the reserved bit (4 bits) can indicate whether to transmit a CTS frame (or CTS-to-Self frame). Bit 0 can indicate that a CTS frame (or CTS-to-Self frame) will not be transmitted following the transmission of the corresponding MU-RTS TXS TF. Bit 1 can indicate that a CTS frame (or CTS-to-Self frame) will be transmitted following the transmission of the corresponding MU-RTS TXS TF.

[0244] H. NAVTimeout Disable: It can be instructed not to reset the NAV even if the NAVTimeout period expires. For example, the EHT Reserved bit (bit 7) or Reserved bit (bit 4) of the Common Information field can be utilized for the NAVTimeout Disable field. For example, one bit of the EHT Reserved bit (bit 7) or Reserved bit (bit 4) can indicate whether to reset the NAV even if the NAVTimeout period expires. Bit 0 can indicate to reset the NAV if the NAVTimeout period expires after receiving the corresponding MU-RTS TXS TF (default). Bit 1 can indicate not to reset the NAV even if the NAVTimeout period expires after receiving the corresponding MU-RTS TXS TF.

[0245] I. Address: Address information of potential DAPs that wish to perform multi-AP transmission in a multi-AP set (e.g., BSS color, BSSID for multi-AP, MAC address).

[0246] J. Multi-AP ID or AP ID: An ID (e.g., 0, 1, 2, ...) locally assigned by each AP within a configured multi-AP set / group. For example, the multi-AP ID or AP ID may be included in the AID12 field within the user information field of the trigger frame.

[0247] According to Option 1) and Option 2), the AID12 field in the User Information field may be replaced with an ID related to multi-AP cooperation so that the MU-RTS TXS TF can be transmitted for TXOP sharing between APs. Here, the ID related to multi-AP cooperation may include at least one of the BSSID of the target DAP, the BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that have formed multi-AP cooperation), or a DAP ID (i.e., an ID assigned by the SAP within the formed multi-AP group). Alternatively, when targeting a single DAP, the RA field may include the MAC address of the target DAP.

[0248] An AP receiving an MU-RTS TXS TF based on Option 1) and Option 2) can identify that the received MU-RTS TXS TF is an MU-RTS TXS TF for Co-TDMA and / or multi-AP cooperation between APs, not an EHT TXS protocol (i.e., a TXS protocol between STAs and APs), by decoding the AID12 field within the user information field and if it contains an ID associated with itself, and / or if the RA field is set to its MAC address, and can decode and obtain additional information.

[0249] Therefore, since the AP receiving the MU-RTS TXS TF can identify that the received MU-RTS TXS TF is the MU-RTS TXS TF transmitted to the AP, the following option 3) can be used as an alternative:

[0250] Option 3) Instead of the encoding method for the TXS mode of the MU-RTS TXS TF (i.e., ), a new encoding method for multi-AP cooperation and / or Co-TDMA based transmission can be defined.

[0251] For example, an encoding example of TXS mode for multi-AP cooperation and / or Co-TDMA based transmission may be as shown in below:

[0252] Triggered TXOP Sharing Mode subfield valueDescription0MU-RTS that does not initiate TXS procedure.1 (Co-TDMA target)MU-RTS that initiates triggered TXOP sharing procedure wherein a scheduled AP can transmit MPDU(s) addressed to its associated STA.2-3Reserved

[0253] In addition to the TXS mode according to Option 3) (i.e., TXS mode = 1 for Co-TDMA), specific multi-AP cooperation schemes (e.g., C-OFDMA, Co-TDMA, Co-BF, Co-SR) may be indicated and / or included. In addition, they may be separately defined and / or indicated by utilizing reserved fields such as the above-described A to J fields (i.e., Multi-AP Cooperation Type field, Co-TDMA Operation field, TXOP Return Request field, Medium Reservation Request field, Cooperation Priority field, CTS Request field, More CTS field, NAVTimeout Inactive field, Address field, Multi-AP ID or AP ID). In addition, reserved bits (e.g., TXS mode = 2, 3) may also indicate other multi-AP cooperation schemes, and may be utilized to indicate other procedures in Co-TDMA operation (e.g., Multi-AP selection, TXOP return).

[0254] FIG. 21 illustrates an example of a frame format based on TXS mode 2 according to an embodiment of the present disclosure. For example, the frame format illustrated in FIG. 21 may be a frame format according to option 2) described above.

[0255] Referring to FIG. 21, an MU-RTS TXS TF for multi-AP cooperation can be designed by modifying the common information field and / or the user information field.

[0256] For example, when TXS mode = 2, a field may be defined to indicate a multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits according to the number of multi-AP cooperation methods) in the reserved bits of the common information field of the MU-RTS TXS TF for Co-TDMA.

[0257] For example, when TXS mode = 2, a field can be defined to indicate TXOP return support and / or request by utilizing 1 bit in the EHT reserved bit of the (UHR variant) common information field of the MU-RTS TXS TF for Co-TDMA.

[0258] For example, when TXS mode = 2, a field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the reserved bits of the (UHR variant) User Information field of the MU-RTS TXS TF for Co-TDMA. The AID12 field of the (UHR variant) User Information field may include at least one of the BSSID of the target DAP, a BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that have formed multi-AP cooperation), or a DAP ID (i.e., an ID assigned from a SAP within the formed multi-AP group).

[0259] I-2. MU-RTS TXS trigger frame based on the new TXS mode

[0260] In some implementations, a new TXS mode can be defined by setting the TXOP sharing mode triggered in Table 2 to a reserved value of 3, and can be utilized as MU-RTS TXS TF in TXOP sharing for Co-TDMA.

[0261] A new TXS mode utilizing the reserved bits of the TXS mode can be defined and / or designed based on at least one of the following options:

[0262] Option 1) The reserved value TXS mode = 3 may be newly defined and utilized as a mode for sharing TXOPs between APs. That is, TXS mode = 3 may support allowing a DAP to transmit one or more PPDUs to an STA connected to the DAP. In addition, when a new mode is defined, the fields following the TXS mode field may be reserved, or the above-described A to J fields for Co-TDMA operation (i.e., Multi-AP Cooperation Type field, Co-TDMA Operation field, TXOP Return Request field, Medium Reservation Request field, Cooperation Priority field, CTS Request field, More CTS field, NAVTimeout Inactive field, Address field, Multi-AP ID or AP ID) may be separately defined and / or indicated by utilizing the reserved fields. In this case, a specific description of TXS mode 3 may be as shown in below:

[0263] Triggered TXOP Sharing Mode subfield valueDescription0~2Same as 3MU-RTS that initiates triggered TXOP sharing procedure wherein a scheduled AP can transmit MPDU(s) addressed to its associated STA.

[0264] Option 2) The reserved value TXS Mode = 3 may be (newly) defined and / or utilized as a mode for UHR that can operate based on TXOP sharing. That is, TXS Mode = 3 may be (newly) defined as a special and / or UHR mode to support multi-AP cooperation (e.g., Co-TDMA) and / or relay communication in UHR. In this case, the specific description of TXS Mode 3 may be as shown in below:

[0265] Triggered TXOP Sharing Mode subfield valueDescription0~2Same as 3MU-RTS that initiates triggered TXOP sharing procedure for Multi-AP coordination (or) Relay communication.

[0266] Option 3) Considering forward capability, such as procedures related to multi-AP cooperation (e.g., multi-AP selection procedure) and / or procedures related to TXS (e.g., TXOP return procedure) and / or UHR operation (e.g., multi-AP cooperation, relay communication), the 2-bit triggered TXOP shared mode field may be extended and newly defined and / or utilized. In this case, the reserved and EHT reserved fields in the common information field of the MU-RTS TXS TF may be utilized. For example, B20-B22 (3 bits), including the reserved field B22, may be extended and newly defined for the triggered TXOP shared mode field. An example of the encoding of the extended TXS mode may be as shown in below:

[0267] Triggered TXOP Sharing Mode subfield value Description 0~2 3 (Multi-AP cooperation) MU-RTS that initiates a triggered TXOP sharing procedure wherein a scheduled AP can transmit MPDU(s) addressed to its associated STA. 4 (Relay communication) MU-RTS that initiates a triggered TXOP sharing procedure for relay communication. 5-7 Reserved

[0268] The new TXS mode in Option 3) may indicate and / or include a multi-AP cooperation scheme (e.g., C-OFDMA, Co-TDMA, Co-BF, Co-SR), and may be separately defined and / or indicated by utilizing reserved fields such as the above-described A to J fields (i.e., Multi-AP Cooperation Type field, Co-TDMA Operation field, TXOP Return Request field, Medium Reservation Request field, Cooperation Priority field, CTS Request field, More CTS field, NAVTimeout Disable field, Address field, Multi-AP ID or AP ID). In the MU-RTS TXS TF according to Option 1), Option 2), and Option 3), the above-described A to J fields (i.e., Multi-AP Cooperation Type field, Co-TDMA Operation field, TXOP Return Request field, Medium Reservation Request field, Cooperation Priority field, CTS Request field, More CTS field, NAVTimeout Disable field, Address field, Multi-AP ID or AP ID) may be added and / or defined, and the specific fields The designation (name) may be changed.

[0269] The SAP may replace the AID12 field within the User Information field with an ID associated with multi-AP cooperation to indicate the target DAP for TXOP sharing. For example, the ID associated with multi-AP cooperation may include at least one of the BSSID of the target DAP, the BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that constitute multi-AP cooperation), or a DAP ID (i.e., an ID assigned by the SAP within the configured multi-AP group). Alternatively, if targeting a single DAP, the RA field may contain the MAC address of the target DAP.

[0270] Therefore, an AP receiving an MU-RTS TXS TF based on the new TXS mode can identify the TXS mode by performing decoding according to Option 1), Option 2), and Option 3). In addition, if the AP receives an MU-RTS TXS TF in which the AID12 field in the user information field includes an ID related to the AP or an MU-RTS TXS TF in which the RA field is set to the AP's MAC address, the AP can identify that the MU-RTS TXS TF is an MU-RTS TXS TF for Co-TDMA and / or multi-AP cooperation between APs, not an EHT TXS protocol between the AP and STA, and can decode and / or obtain additional information according to the indicated TXS mode.

[0271] FIG. 22 illustrates an example of a frame format based on a novel TXS mode according to an embodiment of the present disclosure. For example, the frame format illustrated in FIG. 22 may be a frame format according to Option 3) described above.

[0272] Referring to FIG. 22, an MU-RTS TXS TF for multi-AP cooperation can be designed by modifying the common information field and / or the user information field.

[0273] For example, a triggered TXOP sharing mode for multi-AP cooperation (e.g. TXS mode = 3, or a newly defined value) can be defined by additionally utilizing one bit in the reserved bits of the common information field of the MU-RTS TXS TF for Co-TDMA.

[0274] For example, a field can be defined to indicate TXOP return support and / or request by utilizing 1 bit in the EHT reserved bit of the (UHR variant) common information field of the MU-RTS TXS TF for Co-TDMA.

[0275] For example, a field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the reserved bits of the User Information field of the (UHR variant) MU-RTS TXS TF for Co-TDMA. The AID12 field of the (UHR variant) User Information field may include at least one of the BSSID of the target DAP, a BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that have formed multi-AP cooperation), or a DAP ID (i.e., an ID assigned by the SAP within the formed multi-AP group).

[0276] II. New Type of Trigger Frame

[0277] A new type of trigger frame can be designed for TXOP sharing in multi-AP cooperation or Co-TDMA-based transmission. For example, a new type of trigger frame that can be utilized in multi-AP cooperation or Co-TDMA-based transmission can be implemented by utilizing the reserved values ​​(9 to 15) among the trigger frame types shown in Table 1.

[0278] II-1. Multi-AP (MAP) trigger frame

[0279] A MAP trigger frame may be implemented and / or defined for the purpose of supporting multi-AP cooperation or Co-TDMA-based transmission. The notation of the MAP trigger frame is exemplary, and the specific name (name) may be changed. The MAP TF may allocate and / or request resources for transmission of one or more TB PPDUs between APs, and may also carry information required for a DAP to transmit a TB PPDU.

[0280] FIG. 23 illustrates an example of a MAP trigger frame format according to an embodiment of the present disclosure.

[0281] Referring to FIG. 23, a MAP trigger frame may be a trigger frame in which the trigger type of the trigger frame is set to a newly defined value to indicate the MAP trigger frame.

[0282] The (UHR variant) common information field of the MAP trigger frame may include at least one of a multi-AP cooperation type field (3 bits), an AP type field (1 bit), a TXOP return request field (1 bit), or coordination dependent common information.

[0283] The multi-AP cooperation type field can indicate a multi-AP cooperation method such as C-OFDMA, Co-TDMA, J-TX, or Co-SR.

[0284] In some implementations, the EHT reserved bits (7 bits) or the reserved bits (4 bits) of the common information field may be utilized for the multi-AP cooperation type field. For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits depending on the number of multi-AP cooperation methods) in the EHT reserved bits (7 bits). For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits depending on the number of multi-AP cooperation methods) in the reserved bits (4 bits).

[0285] In some implementations, the triggered TXOP shared mode field (2 bits) and the reserved bit (1 bit) may be combined to extend the triggered TXOP shared mode field to 3 bits, and a multi-AP cooperation type field (3 bits) may be configured as shown in FIG. 23. For example, the combined and / or extended 3 bits may be used to indicate a currently operating multi-AP cooperation scheme such as C-OFDMA, Co-TDMA, Co-SR, or J-TX.

[0286] The AP Type field may indicate the AP's operating type (e.g., SAP or DAP) within the current TXOP. In some implementations, the EHT reserved bit (bit 7) or the reserved bit (bit 4) of the common information field may be utilized for the AP Type field. For example, a new field may be defined to indicate the AP type within the current TXOP by utilizing bit 1 of the EHT reserved bit (bit 7) or the reserved bit (bit 4). Bit 0 may indicate that the AP transmitting the corresponding MAP TF is not acting as a SAP, and bit 1 may indicate that the AP transmitting the corresponding MAP TF is acting as a SAP. The AP Type field may be utilized to indicate the AP's operating type and / or to distinguish between operations that can be performed individually using the corresponding MAP TF in a SAP or a DAP (e.g., a TXOP sharing operation by a SAP and a TXOP return operation by a DAP).

[0287] The TXOP Return Required field can indicate whether the TXOP return procedure must be performed within the allocated time. For example, this field can indicate to the DAP that it supports transmitting frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field can indicate that the DAP must transmit frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field can indicate that the DAP must transmit frames containing information about the SAP (e.g., the AID of the SAP, a new AID defined for multi-AP cooperation) within the allocated time.

[0288] In some implementations, the EHT Reserved Bit (7 bits) or Reserved Bit (4 bits) may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the EHT Reserved Bit (7 bits). For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the Reserved Bit (4 bits).

[0289] In some implementations, the reserved bits (10 bits) of the User Information field may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (10 bits).

[0290] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the TXOP return request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (3 bits).

[0291] In the examples described above, i) bit 0 may indicate that the DAP does not have to perform a TXOP return within the allocated time, and ii) bit 1 may indicate that the DAP must perform a TXOP return within the allocated time.

[0292] The cooperation-based common information field may optionally be present based on the values ​​of the multi-AP cooperation type field and / or the AP type field. For example, the cooperation-based common information field may include and / or indicate user-specific information and / or common information required for Co-TDMA operation. For example, a value indicating an allocation interval field included in the user information field of the MAP TF may be included in the cooperation-based common information field of the common information field. If an allocation interval value is included in the common information field / cooperation-based common information field, the value may indicate a maximum allocation interval value that the SAP can allocate to the DAP. As another example, the cooperation-based common information field may include a nominal TXOP duration (e.g., a TXOP duration scheduled by the SAP for Co-TDMA operation), which is a period of time during which APs participating in Co-TDMA operation cooperate with each other and perform individual FE, TXOP sharing, and / or TXOP return.

[0293] Additionally, the (UHR variant) common information field / user information field of the MAP trigger frame may further include at least one of a cooperation priority field, a More CTS field, a NAVTimeout inactive field, a CTS request field, an address field, or multiple AP IDs / AP IDs.

[0294] The cooperation priority field may indicate the priority of the currently used cooperation method among the multi-AP cooperation methods, and / or may indicate the priority / protection level for efficiently performing Co-TDMA operation.

[0295] For example, the EHT reserved bit (7 bits) or reserved bit (4 bits) of the common information field can be utilized for the cooperative priority field. For example, two bits of the EHT reserved bit (7 bits) or reserved bit (4 bits) can indicate the priority / protection level of the current Co-TDMA operation. Bit 0 can indicate cooperative transmission with priority / protection level 0. This can mean that no separate protection for TXOP sharing and / or TXOP return is required in Co-TDMA operation. Bit 1 can indicate cooperative transmission with priority / protection level 1-1. This can mean that separate protection for TXOP sharing is required in Co-TDMA operation. Bit 2 can indicate cooperative transmission with priority / protection level 1-2. This can mean that separate protection for TXOP return is required in Co-TDMA operation. Bit 3 may indicate cooperative transmission with priority / protection level 2. This may mean that protection is required for both TXOP sharing and TXOP return in Co-TDMA operation.

[0296] The CTS Request field can indicate whether a CTS frame should be transmitted in response to a MAP TF (i.e., whether solicited / unsolicited).

[0297] In some implementations, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field may be utilized for the CTS request field. For example, one bit of the EHT reserved bit (7 bits) may indicate whether transmission of a CTS frame is requested. For example, one bit of the reserved bit (4 bits) may indicate whether transmission of a CTS frame is requested.

[0298] In some implementations, the reserved bits (10 bits) of the user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (10 bits) may indicate whether transmission of a CTS frame is requested.

[0299] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (3 bits) may indicate whether transmission of a CTS frame is requested.

[0300] In the examples described above, i) bit 0 may indicate that transmission of a CTS frame is induced for transmission of the corresponding MAP TF (i.e., indicates that a CTS frame must be transmitted), and ii) bit 1 may indicate that transmission of a CTS frame is not induced for transmission of the corresponding MAP TF (i.e., indicates that a CTS frame does not need to be transmitted).

[0301] The More CTS field can indicate whether a CTS frame (or a CTS-to-Self frame) will be transmitted within a certain period of time. For example, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field can be utilized for the More CTS field. For example, one bit of the EHT reserved bit (7 bits) or the reserved bit (4 bits) can indicate whether a CTS frame (or a CTS-to-Self frame) will be transmitted. Bit 0 can indicate that a CTS frame (or a CTS-to-Self frame) will not be transmitted following the transmission of the corresponding MAP TF. Bit 1 can indicate that a CTS frame (or a CTS-to-Self frame) will be transmitted following the transmission of the corresponding MAP TF.

[0302] The NAVTimeout disable field can indicate that the NAV will not be reset even if the NAVTimeout period expires. For example, the EHT reserved bit (bit 7) or reserved bit (bit 4) of the common information field can be utilized for the NAVTimeout disable field. For example, one bit of the EHT reserved bit (bit 7) or reserved bit (bit 4) can indicate whether to reset the NAV even if the NAVTimeout period expires. Bit 0 can indicate that the NAV will be reset if the NAVTimeout period expires after receiving the corresponding MAP TF (default). Bit 1 can indicate that the NAV will not be reset even if the NAVTimeout period expires after receiving the corresponding MAP TF.

[0303] The address field contains address information of potential DAPs that wish to perform multi-AP transmissions in a multi-AP set (e.g., BSS color, BSSID for multi-AP, MAC address).

[0304] The Multi-AP ID or AP ID field is an ID (e.g., 0, 1, 2, ...) locally assigned by each AP within the configured Multi-AP Set / Group. For example, the Multi-AP ID or AP ID may be included in the AID12 field within the User Information field of the trigger frame.

[0305] The SAP may replace the AID12 field within the User Information field with an ID associated with multi-AP cooperation to indicate the target DAP for TXOP sharing. For example, the ID associated with multi-AP cooperation may include at least one of the BSSID of the target DAP, the BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that constitute multi-AP cooperation), or a DAP ID (i.e., an ID assigned by the SAP within the configured multi-AP group). Alternatively, if targeting a single DAP, the RA field may contain the MAC address of the target DAP.

[0306] Therefore, an AP receiving a MAP TF can identify the multi-AP cooperation type through decoding. In addition, when the AP receives a MAP TF in which the AID12 field in the user information field contains an ID related to the AP or a MAP TF in which the RA field is set to the AP's MAC address, the AP can identify that the MAP TF is a MAP TF for Co-TDMA and / or multi-AP cooperation between APs, and can decode and / or obtain additional information according to the multi-AP cooperation type. Thereafter, the DAP can transmit a CTS frame (or a CTS-to-self frame) to the SAP based on the information obtained from the TF.

[0307] II-2. Multi-AP (MAP)-RTS Trigger Frame

[0308] In some implementations, a MAP-RTS trigger frame may be implemented and / or defined to support multi-AP cooperation and / or Co-TDMA-based transmission. The notation of the MAP-RTS trigger frame is exemplary, and the specific name (designation) may be changed. The MAP-RTS TF may be designed based on the structure and / or format of the MU-RTS TF or the MU-RTS TXS TF.

[0309] FIG. 24 illustrates an example of a MAP-RTS trigger frame format according to an embodiment of the present disclosure. The names and / or number of bits of the fields illustrated in FIG. 24 may be changed and are not limited thereto.

[0310] Referring to FIG. 24, a MAP-RTS trigger frame may be a trigger frame in which the trigger type of the trigger frame is set to a newly defined value to indicate a MAP-RTS trigger frame.

[0311] The (UHR variant) common information field of the MAP-RTS trigger frame may include at least one of a multi-AP cooperation type field (3 bits), an AP type field (1 bit), a TXOP return request field (1 bit), or coordination dependent common information.

[0312] The multi-AP cooperation type field can indicate a multi-AP cooperation method such as C-OFDMA, Co-TDMA, J-TX, or Co-SR.

[0313] In some implementations, the EHT reserved bits (7 bits) or the reserved bits (4 bits) of the common information field may be utilized for the multi-AP cooperation type field. For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits depending on the number of multi-AP cooperation methods) in the EHT reserved bits (7 bits). For example, a new field may be defined to indicate the multi-AP cooperation type by utilizing one or more bits (e.g., 1 to n bits depending on the number of multi-AP cooperation methods) in the reserved bits (4 bits).

[0314] In some implementations, the triggered TXOP shared mode field (2 bits) and the reserved bit (1 bit) may be combined to extend the triggered TXOP shared mode field to 3 bits, and a multi-AP cooperation type field (3 bits) may be configured as shown in FIG. 24. For example, the combined and / or extended 3 bits may be used to indicate a currently operating multi-AP cooperation scheme such as C-OFDMA, Co-TDMA, Co-SR, or J-TX.

[0315] The AP Type field may indicate the AP's operating type (e.g., SAP or DAP) within the current TXOP. In some implementations, the EHT reserved bit (bit 7) or the reserved bit (bit 4) of the common information field may be utilized for the AP Type field. For example, a new field may be defined to indicate the AP type within the current TXOP by utilizing bit 1 of the EHT reserved bit (bit 7) or the reserved bit (bit 4). Bit 0 may indicate that the AP transmitting the corresponding MAP-RTS TF is not acting as a SAP, and bit 1 may indicate that the AP transmitting the corresponding MAP-RTS TF is acting as a SAP. The AP Type field may be utilized to indicate the AP's operating type and / or to distinguish between operations that can be performed individually using the corresponding MAP-RTS TF in a SAP or a DAP (e.g., a TXOP sharing operation by a SAP and a TXOP return operation by a DAP).

[0316] The TXOP Return Required field can indicate whether the TXOP return procedure must be performed within the allocated time. For example, this field can indicate to the DAP that it supports transmitting frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field can indicate that the DAP must transmit frames whose RA field specifies the address of the SAP within the allocated time. Alternatively, this field can indicate that the DAP must transmit frames containing information about the SAP (e.g., the AID of the SAP, a new AID defined for multi-AP cooperation) within the allocated time.

[0317] In some implementations, the EHT Reserved Bit (7 bits) or Reserved Bit (4 bits) may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the EHT Reserved Bit (7 bits). For example, a new field may be defined to indicate TXOP return support and / or request by utilizing 1 bit in the Reserved Bit (4 bits).

[0318] In some implementations, the reserved bits (10 bits) of the User Information field may be utilized for the TXOP Return Request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (10 bits).

[0319] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the TXOP return request field. For example, a new field may be defined to indicate support and / or request for TXOP return by utilizing 1 bit in the reserved bits (3 bits).

[0320] In the examples described above, i) bit 0 may indicate that the DAP does not have to perform a TXOP return within the allocated time, and ii) bit 1 may indicate that the DAP must perform a TXOP return within the allocated time.

[0321] The cooperation-based common information field may optionally be present based on the values ​​of the multi-AP cooperation type field and / or the AP type field. For example, the cooperation-based common information field may include and / or indicate common information required for Co-TDMA operation. For example, a value indicating an allocation interval field included in the user information field of the MAP-RTS TF may be included in the cooperation-based common information field of the common information field. When an allocation interval value is included in the common information field / cooperation-based common information field, the value may indicate a maximum allocation interval value that the SAP can allocate to a DAP. Alternatively, the allocation interval value included in the common information field / cooperation-based common information field may indicate an additional maximum allocation interval value that the SAP can allocate when it wishes to perform additional TXOP sharing within the remaining TXOP period. As another example, the cooperation-based common information field may include a Nominal TXOP Duration (e.g., a TXOP duration scheduled by a SAP for Co-TDMA operation), which is the period during which APs participating in Co-TDMA operation cooperate with each other and perform individual FE, TXOP sharing, and / or TXOP return.

[0322] The (UHR variant) User Information field of the MAP-RTS trigger frame may include a Cooperation-Based User Information field (10 bits). The Cooperation-Based User Information field may be optionally present based on the values ​​of the Multi-AP Cooperation Type field and / or the AP Type field. For example, the Cooperation-Based User Information field may include and / or indicate user-specific information required for Co-TDMA operation. For example, the Cooperation-Based User Information field may include a signaling bit indicating that the SAP may perform additional TXOP sharing within the remaining TXOP period when the SAP may perform additional TXOP sharing within the remaining TXOP period. Alternatively, the Cooperation-Based User Information field may indicate an additional allocation interval value that can be allocated when the SAP wishes to perform additional TXOP sharing within the remaining TXOP period. The Cooperation-Based User Information field may include BSS operating channel width and / or primary / secondary channel index information recommended by the SAP to the DAP wishing to share TXOPs to improve efficiency in Co-TDMA-based transmission.

[0323] Additionally, the (UHR variant) common information field / user information field of the MAP-RTS trigger frame may further include at least one of a cooperation priority field, a More CTS field, a NAVTimeout inactive field, a CTS request field, an address field, or multiple AP IDs / AP IDs.

[0324] The cooperation priority field may indicate the priority of the currently used cooperation method among the multi-AP cooperation methods, and / or may indicate the priority / protection level for efficiently performing Co-TDMA operation.

[0325] For example, the EHT reserved bit (7 bits) or reserved bit (4 bits) of the common information field can be utilized for the cooperative priority field. For example, two bits of the EHT reserved bit (7 bits) or reserved bit (4 bits) can indicate the priority / protection level of the current Co-TDMA operation. Bit 0 can indicate cooperative transmission with priority / protection level 0. This can mean that no separate protection for TXOP sharing and / or TXOP return is required in Co-TDMA operation. Bit 1 can indicate cooperative transmission with priority / protection level 1-1. This can mean that separate protection for TXOP sharing is required in Co-TDMA operation. Bit 2 can indicate cooperative transmission with priority / protection level 1-2. This can mean that separate protection for TXOP return is required in Co-TDMA operation. Bit 3 may indicate cooperative transmission with priority / protection level 2. This may mean that protection is required for both TXOP sharing and TXOP return in Co-TDMA operation.

[0326] The CTS Request field can indicate whether a CTS frame should be transmitted in response to a MAP-RTS TXS TF (i.e., whether solicited / unsolicited).

[0327] In some implementations, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field may be utilized for the CTS request field. For example, one bit of the EHT reserved bit (7 bits) may indicate whether transmission of a CTS frame is requested. For example, one bit of the reserved bit (4 bits) may indicate whether transmission of a CTS frame is requested.

[0328] In some implementations, the reserved bits (10 bits) of the user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (10 bits) may indicate whether transmission of a CTS frame is requested.

[0329] In some implementations, the reserved bits (3 bits) of the special user information field may be utilized for the CTS request field. For example, one bit of the reserved bits (3 bits) may indicate whether transmission of a CTS frame is requested.

[0330] In the examples described above, i) bit 0 may indicate that transmission of a CTS frame is induced for transmission of the corresponding MAP-RTS TXS TF (i.e., indicating that a CTS frame must be transmitted), and ii) bit 1 may indicate that transmission of a CTS frame is not induced for transmission of the corresponding MAP-RTS TXS TF (i.e., indicating that a CTS frame does not need to be transmitted).

[0331] The More CTS field can indicate whether a CTS frame (or a CTS-to-Self frame) will be transmitted within a certain period of time. For example, the EHT reserved bit (7 bits) or the reserved bit (4 bits) of the common information field can be utilized for the More CTS field. For example, one bit of the EHT reserved bit (7 bits) or the reserved bit (4 bits) can indicate whether a CTS frame (or a CTS-to-Self frame) will be transmitted. Bit 0 can indicate that a CTS frame (or a CTS-to-Self frame) will not be transmitted following the transmission of the corresponding MAP-RTS TXS TF. Bit 1 can indicate that a CTS frame (or a CTS-to-Self frame) will be transmitted following the transmission of the corresponding MAP-RTS TXS TF.

[0332] The NAVTimeout disable field can indicate not to reset the NAV even if the NAVTimeout period expires. For example, the EHT reserved bit (bit 7) or reserved bit (bit 4) of the common information field can be utilized for the NAVTimeout disable field. For example, one bit of the EHT reserved bit (bit 7) or reserved bit (bit 4) can indicate whether to reset the NAV even if the NAVTimeout period expires. Bit 0 can indicate to reset the NAV if the NAVTimeout period expires after receiving the corresponding MAP-RTS TXS TF (default). Bit 1 can indicate not to reset the NAV even if the NAVTimeout period expires after receiving the corresponding MAP-RTS TXS TF.

[0333] The address field contains address information of potential DAPs that wish to perform multi-AP transmissions in a multi-AP set (e.g., BSS color, BSSID for multi-AP, MAC address).

[0334] The Multi-AP ID or AP ID field is an ID (e.g., 0, 1, 2, ...) locally assigned by each AP within the configured Multi-AP Set / Group. For example, the Multi-AP ID or AP ID may be included in the AID12 field within the User Information field of the trigger frame.

[0335] The SAP may replace the AID12 field within the User Information field with an ID associated with multi-AP cooperation to indicate the target DAP for TXOP sharing. For example, the ID associated with multi-AP cooperation may include at least one of the BSSID of the target DAP, the BSS color, a newly defined multi-AP group ID (i.e., an ID for a set / group of APs that constitute multi-AP cooperation), or a DAP ID (i.e., an ID assigned by the SAP within the configured multi-AP group). Alternatively, if targeting a single DAP, the RA field may contain the MAC address of the target DAP.

[0336] Accordingly, an AP receiving a MAP-RTS TF can identify the multi-AP cooperation type through decoding. In addition, when the AP receives a MAP-RTS TXS TF in which the AID12 field in the user information field includes an ID related to the AP or a MAP-RTS TXS TF in which the RA field is set to the AP's MAC address, the AP can identify that the MAP-RTS TXS TF is a MAP-RTS TXS TF for Co-TDMA and / or multi-AP cooperation between APs, and can decode and / or obtain additional information according to the indicated multi-AP cooperation type. Thereafter, the DAP can transmit a CTS frame (or a CTS-to-self frame) to the SAP based on the information obtained from the TF.

[0337] The technical features of the present disclosure described above can be applied to various devices and methods. For example, the technical features of the present disclosure described above can be performed / supported by the devices of FIG. 1 and / or FIG. 5. For example, the technical features of the present disclosure described above can be applied only to a portion of FIG. 1 and / or FIG. 5. For example, the technical features of the present disclosure described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and memory (112, 122) of FIG. 1, or based on the processor (510) and memory (520) of FIG. 5.

[0338] For example, the processor (121) and / or the processing chip (124) of FIG. 1 may be configured to execute instructions stored in the memory (122) to perform operations performed by the first AP in the present disclosure. The operations include: performing a negotiation procedure for multi-AP cooperation with the second AP; receiving, from the second AP, a TXOP (transmission opportunity) sharing frame including information about sharing in the multi-AP cooperation; obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

[0339] For example, the processor (111), the processing chip (114) of FIG. 1, and / or the processor (510) of FIG. 5 may be configured to execute instructions stored in the memory (112, 520) to perform operations performed by the second AP in the present disclosure. The operations include: performing a negotiation procedure for multi-AP cooperation with the first AP; and transmitting, to the first AP, a TXOP (transmission opportunity) shared frame including information about TXOP sharing in the multi-AP cooperation, wherein the first AP is configured to perform operations including: obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

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

[0341] For example, the CRM may be the memory (122) of FIG. 1 and / or a separate external memory / storage medium / disk. The CRM may store commands that perform operations performed by the first AP in the present disclosure based on being executed by a processor (e.g., the processor (121) and / or the processing chip (124) of FIG. 1). The operations include: performing a negotiation procedure for multi-AP cooperation with a second AP; receiving, from the second AP, a TXOP (transmission opportunity) sharing frame including information about sharing of TXOP in the multi-AP cooperation; obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

[0342] For example, the CRM may be the memory (112) of FIG. 1, the memory (520) of FIG. 5, and / or a separate external memory / storage medium / disk. The CRM may store commands that perform operations performed by the second AP in the present disclosure based on being executed by a processor (e.g., the processor (111), the processing chip (114) of FIG. 1, and / or the processor (510) of FIG. 5). The operations include: performing a negotiation procedure for multi-AP cooperation with a first AP; and transmitting, to the first AP, a TXOP (transmission opportunity) shared frame including information about TXOP sharing in the multi-AP cooperation, wherein the first AP is configured to perform operations including: obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0359] The present disclosure may have various advantageous effects.

[0360] For example, according to various embodiments of the present disclosure, the structure and / or format of a trigger frame transmitted by a SAP to share a TXOP with a DAP in a Co-TDMA operation may be defined. Using the trigger frame provided in the present disclosure, the SAP may perform / initiate a TXOP sharing procedure to share a TXOP with the DAP.

[0361] The beneficial effects that can be achieved through specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, various technical effects may be understood and / or derived from the present disclosure by those skilled in the art. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure.

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

Claims

1. A step in which the first AP (access point) performs a negotiation procedure for multi-AP cooperation with the second AP; A step in which the first AP receives a TXOP sharing frame including information about TXOP (transmission opportunity) sharing in the multi-AP cooperation from the second AP; The step of the first AP obtaining information related to the allocation interval for the first AP from the TXOP shared frame; and A method comprising a step of the first AP performing frame exchange in the above allocation interval.

2. In claim 1, the information about TXOP sharing in the multi-AP cooperation includes information indicating that the TXOP sharing is TXOP sharing for the multi-AP cooperation between APs. A method in which information about TXOP sharing in the above multi-AP cooperation includes at least one of a TXOP sharing mode, an ID (identifier) associated with the first AP, or an address of the first AP.

3. In claim 2, the TXOP sharing mode is included in the common information field of the TXOP sharing frame.

4. In claim 3, the value of the TXOP sharing mode is set to 2, The above TXOP sharing mode with the value set to 2 is a method of initiating a TXOP sharing procedure that allows a STA to transmit data to an AP or another STA to which the STA is connected.

5. In claim 3, the value of the TXOP sharing mode is set to 1, The above TXOP sharing mode with the value set to 1 is a method of instructing that a TXOP sharing procedure is initiated, through which the AP can transmit data to the connected STA.

6. In claim 3, the value of the TXOP shared mode is set to a value greater than or equal to 3 using at least one reserved bit, The TXOP sharing mode set to a value greater than or equal to 3 is a method of instructing that a TXOP sharing procedure is initiated, through which the AP can transmit data to the connected STA.

7. In claim 2, the ID associated with the first AP is included in the AID (association ID)12 field of the user information field of the TXOP shared frame, A method wherein the ID associated with the first AP includes at least one of a BSS (basic service set) ID of the first AP, a BSS color of the first AP, an ID of a multi-AP group to which the first AP belongs, or an ID for the first AP assigned by the second AP within the multi-AP group.

8. A method according to claim 2, wherein the address of the first AP is included in the RA (receiver address) field of the TXOP shared frame.

9. A method according to claim 1, wherein the TXOP shared frame further includes at least one of information on a multi-AP cooperation method, information on whether TXOP return is required, information on whether medium reservation is required, information on a cooperation priority, information on whether transmission of a response frame to the TXOP shared frame is required, information on whether a CTS (clear to send) frame is transmitted after the TXOP shared frame is transmitted, information on whether NAV re-establishment is disabled when NAV timeout expires, information on an address of the first AP, or an ID locally assigned to the first AP within the multi-AP group to which the first AP belongs.

10. A method according to claim 1, wherein the trigger frame is a MU (multi-user)-RTS (request to send) TXOP sharing (TXS) trigger frame.

11. At the first AP (access point), Transmitter and receiver; memory; and At least one processor functionally coupled with the transceiver and the memory, The above memory stores instructions for performing operations based on being executed by the at least one processor, the operations being: An action to perform negotiation procedures for secondary AP and multi-AP cooperation; An operation of receiving, from the second AP, a TXOP sharing frame including information about TXOP (transmission opportunity) sharing in the multi-AP cooperation; An operation of obtaining information related to an allocation interval for the first AP from the above TXOP shared frame; and A first AP including an operation for performing frame exchange in the above allocation interval.

12. In the device, at least one processor; and comprising at least one memory functionally coupled with at least one processor; The at least one memory stores instructions that perform operations based on being executed by the at least one processor, the operations comprising: An action to perform negotiation procedures for secondary AP and multi-AP cooperation; An operation of receiving, from the second AP, a TXOP sharing frame including information about TXOP (transmission opportunity) sharing in the multi-AP cooperation; An operation of obtaining information related to an allocation interval for the first AP from the above TXOP shared frame; and A device comprising an operation for performing frame exchange in the above allocation interval.

13. A non-transitory computer readable medium (CRM) storing program code implementing instructions that perform operations based on being executed by at least one processor, said operations comprising: An action to perform negotiation procedures for secondary AP and multi-AP cooperation; An operation of receiving, from the second AP, a TXOP sharing frame including information about TXOP (transmission opportunity) sharing in the multi-AP cooperation; An operation of obtaining information related to an allocation interval for the first AP from the above TXOP shared frame; and CRM including an operation for performing frame exchange in the above allocation section.

14. A step in which the second AP (access point) performs a negotiation procedure for multi-AP cooperation with the first AP; and The step of the second AP transmitting a TXOP sharing frame including information about sharing of TXOP (transmission opportunity) in the multi-AP cooperation to the first AP, A method configured to perform operations including: obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

15. At the second AP (access point), Transmitter and receiver; memory; and At least one processor functionally coupled with the transceiver and the memory, The above memory stores instructions for performing operations based on being executed by the at least one processor, the operations being: An action to perform a negotiation procedure for multi-AP cooperation with the first AP; and An operation of transmitting a TXOP sharing frame including information about sharing of TXOP (transmission opportunity) in the multi-AP cooperation to the first AP, The first AP is configured to perform operations including: obtaining information related to an allocation interval for the first AP from the TXOP shared frame; and performing frame exchange in the allocation interval.

16. In claim 15, the information about TXOP sharing in the multi-AP cooperation includes information indicating that the TXOP sharing is TXOP sharing for the multi-AP cooperation between APs. Information about TXOP sharing in the above multi-AP cooperation, a second AP including at least one of a TXOP sharing mode, an ID (identifier) associated with the first AP, or an address of the first AP.

17. In claim 16, the TXOP sharing mode is a second AP included in the common information field of the TXOP sharing frame.

18. In claim 16, the ID associated with the first AP is included in the AID (association ID)12 field of the user information field of the TXOP shared frame, A second AP, wherein the ID associated with the first AP includes at least one of a BSS (basic service set) ID of the first AP, a BSS color of the first AP, an ID of a multi-AP group to which the first AP belongs, or an ID for the first AP assigned by the second AP within the multi-AP group.

19. In claim 16, the address of the first AP is included in the RA (receiver address) field of the TXOP shared frame.

20. In claim 15, the TXOP shared frame further includes at least one of information on a multi-AP cooperation method, information on whether TXOP return is required, information on whether medium reservation is required, information on a cooperation priority, information on whether transmission of a response frame to the TXOP shared frame is required, information on whether a CTS (clear to send) frame is transmitted after the TXOP shared frame is transmitted, information on whether NAV re-establishment is disabled when NAV timeout expires, information on an address of the first AP, or an ID locally assigned to the first AP within the multi-AP group to which the first AP belongs.

Images