Resource sharing method and device for wi-fi communication

Abstract

The present disclosure proposes an operation of an access point (AP) during Wi-Fi communication. A method of a first AP according to one embodiment of the present disclosure may comprise the operations of: transmitting, to a second AP, a first message for triggering a multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP; receiving, from the second AP, a second message including configuration information for the multi-AP operation determined by the second AP on the basis of the first message; and transmitting, to the second AP, a third message indicating scheduling information for the multi-AP operation determined on the basis of the second message.

Description

Resource sharing method and device for Wi-Fi communication

[0001] The present disclosure relates to a method for sharing resources for Wi-Fi communication between devices.

[0002] Recently, due to the development of wireless technology, wired networks used by many people are being replaced by wireless networks. In other words, as wireless technology can solve the mobility limitations of wired networks, many technologies utilizing wireless networks are being actively researched.

[0003] A Wireless Local Area Network (WLAN), also known as Wi-Fi (Wireless Fidelity), allows users to access the internet via mobile devices or laptops within a certain distance from an Access Point (AP). The Wi-Fi Alliance defines Wi-Fi as a Wireless Local Area Network (WLAN) product based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. Wi-Fi communication primarily uses the 2.4 GHz and 5 GHz wireless bands. In particular, with the popularization of mobile devices, wireless LANs, which possess the potential as open wireless networks, are expanding rapidly, and Wi-Fi is being used to provide high-speed data services throughout cities, including in schools, airports, hotels, and offices.

[0004] The Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with big data processing technologies through connections with cloud servers, is also emerging. Implementing IoT requires technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology. Recently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched for connecting objects.

[0005] In an IoT environment, intelligent IT (Internet Technology) services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT (Information Technology) with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0006] The present disclosure proposes a method for multiple devices to share resources during Wi-Fi communication.

[0007] A method of a first AP according to one embodiment of the present disclosure may include: transmitting a first message to a second AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP; receiving a second message from the second AP that includes setting information for the Multi-AP operation determined by the second AP based on the first message; and transmitting a third message to the second AP that indicates scheduling information for the Multi-AP operation determined based on the second message.

[0008] According to one embodiment, the Multi-AP operation may be such that, within the TXOP acquired by the first AP, the first AP and the second AP use at least one transmission scheme among Co-TDMA (coordinated time division multiple access), Co-BF (coordinated beamforming), Co-SR (coordinated spatial reuse), Co-SN (coordinated spatial nulling), and Co-rTWT (coordinated restricted target wake time).

[0009] A method of a second access point (AP) performing Wi-Fi communication according to one embodiment of the present disclosure may include: receiving a first message from the first AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP; transmitting a second message to the first AP that includes setting information for the Multi-AP operation determined by the second AP based on the first message; and receiving a third message from the first AP that indicates scheduling information for the Multi-AP operation determined based on the second message.

[0010] According to one embodiment of the present disclosure, a first AP (access point) performing Wi-Fi communication includes a transceiver; and a control unit. The control unit may control the transmission of a first message to the second AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP, receive a second message from the second AP containing setting information for the Multi-AP operation determined by the second AP based on the first message, and control the transmission of a third message to the second AP indicating scheduling information for the Multi-AP operation determined based on the second message.

[0011] According to one embodiment of the present disclosure, a second AP (access point) performing Wi-Fi communication may include a transceiver; and a control unit. The control unit may include the operation of receiving a first message from the first AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP, controlling the transmission of a second message to the first AP that includes setting information for the Multi-AP operation determined by the second AP based on the first message, and receiving a third message from the first AP that indicates scheduling information for the Multi-AP operation determined based on the second message.

[0012] According to one embodiment of the present disclosure, an access point that has acquired a Transmission Opportunity (TXOP) may share the TXOP with another access point or perform Multi-AP operations with another access point within the acquired TXOP.

[0013] FIG. 1 is a drawing for explaining a short-range communication connection type of an electronic device according to one embodiment of the present disclosure.

[0014] FIG. 2 is a diagram illustrating the operation of an access point and a station for establishing a Wi-Fi connection according to one embodiment of the present disclosure.

[0015] FIG. 3 is a diagram illustrating a Co-TDMA operation that shares TXOPs owned between APs according to one embodiment of the present disclosure.

[0016] FIG. 4 is a diagram illustrating a procedure for Multi-AP operation at the TXOP level according to one embodiment of the present disclosure.

[0017] FIG. 5a is a drawing showing a first type of User Info field according to one embodiment of the present disclosure.

[0018] FIG. 5b is a drawing showing a second type of User Info field according to one embodiment of the present disclosure.

[0019] FIG. 6 is a drawing showing an M-BA (Multi-Block Ack) according to one embodiment of the present disclosure.

[0020] FIG. 7 is a diagram showing Multi-AP operation information (M-AP Operation Info) according to one embodiment of the present disclosure.

[0021] FIG. 8a is a drawing showing a bandwidth information field format according to one embodiment of the present disclosure.

[0022] FIG. 8b is a drawing showing a control subfield format according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram showing Multi-AP operation information (M-AP Operation Info) according to one embodiment of the present disclosure.

[0024] FIG. 10a is a drawing showing a bandwidth information field format according to one embodiment of the present disclosure.

[0025] FIG. 10b is a drawing showing a control subfield format according to one embodiment of the present disclosure.

[0026] FIG. 11 is a drawing showing a user info field included in a MU-RTS TXS trigger frame (TF) according to one embodiment of the present disclosure.

[0027] FIG. 12 is a flowchart for explaining the operation of a first AP (TXOP Sharing AP) according to one embodiment of the present disclosure.

[0028] FIG. 13 is a flowchart for explaining the operation of a second AP (TXOP Shared AP) according to one embodiment of the present disclosure.

[0029] FIG. 14 is a diagram illustrating an example in which ICF and ICR according to one embodiment of the present disclosure are utilized in Co-TDMA.

[0030] FIG. 15 is a drawing illustrating an example in which ICF and ICR according to one embodiment of the present disclosure are utilized in Co-BF / Co-SR.

[0031] FIG. 16 is a diagram showing an example of a configuration of a first AP (TXOP Sharing AP) according to one embodiment of the present disclosure.

[0032] FIG. 17 is a diagram showing an example of a configuration of a second AP (TXOP Shared AP) according to one embodiment of the present disclosure.

[0033] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0034] In describing the embodiments, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0035] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference number.

[0036] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments of the present disclosure are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, like reference numerals refer to like components.

[0037] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction to perform the function described in the flow diagram block(s).

[0038] Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that execute a computer or other programmable data processing equipment by performing a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer may also provide steps for executing the functions described in the flowchart block(s).

[0039] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order depending on the corresponding function.

[0040] In this embodiment, the term "part" used refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, according to some embodiments, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the 'parts' may include one or more processors.

[0041] The terms “electronic device,” “terminal,” or “station” as used herein may be referred to as a mobile station (MS), User Equipment (UE), User Terminal (UT), wireless terminal, access terminal (AT), terminal, Subscriber Unit, Subscriber Station (SS), wireless device, wireless communication device, Wireless Transmit / Receive Unit (WTRU), mobile node, mobile, or other terms. Various embodiments of an “electronic device,” “terminal,” or “station” may include a cellular telephone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, a photographic device such as a digital camera with wireless communication capabilities, a gaming device with wireless communication capabilities, a music storage and playback appliance with wireless communication capabilities, an internet appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such capabilities. Additionally, 'electronic device', 'terminal', or 'station' may include, but are not limited to, M2M (Machine to Machine) terminals and MTC (Machine Type Communication) terminals / devices. In this specification, 'electronic device', 'terminal', or 'station' may also be referred to simply as 'device'.

[0042] Exemplary embodiments are described below in relation to Wireless Local Area Network (WLAN) systems solely for the sake of simplicity. It should be understood that the exemplary embodiments are equally applicable to systems using signals of one or more wired standards or protocols (e.g., Ethernet and / or HomePlug / PLC standards), as well as other wireless networks (e.g., cellular networks, pico networks, femto networks, satellite networks). As used herein, the terms “WLAN” and “Wi-Fi®” may include communications controlled by the IEEE 802.11 standard, BLUETOOTH®, HiperLAN (a set of wireless standards comparable to the IEEE 802.11 standard, mainly used in Europe), and other technologies having a relatively short wireless range. The terms “WLAN” and “Wi-Fi” may be used interchangeably herein. Additionally, although the following describes an infrastructure WLAN system comprising one or more access points (APs) and multiple wireless stations (STAs), exemplary embodiments are equally applicable to other WLAN systems, such as multiple WLANs, peer-to-peer (or independent basic service set) systems, Wi-Fi Direct systems and / or hotspots.

[0043] Additionally, while this specification describes the exchange of data frames between wireless devices, exemplary embodiments may be applied to the exchange of any data unit, packet, and / or frame between wireless devices. Accordingly, the term “frame” may include any frame, packet, or data unit such as, for example, protocol data units (PDUs), MAC (media access control) protocol data units (MPDUs), and PLCP (physical layer convergence procedure) protocol data units (PPDUs). The term “A-MPDU” may mean aggregated MPDUs.

[0044] In the following description, many specific details, such as examples of specific components, circuits, and processes, are presented to provide a thorough understanding of the present disclosure. As used herein, the term “connected” means being directly connected or being connected through one or more intervening components or circuits. The term “connected access point” means an access point to which a given wireless station is currently associated and / or connected (e.g., there exists a communication channel or link established between the access point and the given wireless station). Additionally, in the following description and for illustrative purposes, specific nomenclature is presented to provide a thorough understanding of exemplary embodiments. However, it will be apparent to those skilled in the art that these specific details may not be necessary to carry out the exemplary embodiments. In other cases, to avoid obscuring the present disclosure, well-known circuits and devices are illustrated in block diagram form.

[0045] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0046] FIG. 1 is a drawing for explaining a short-range communication connection type of an electronic device according to one embodiment of the present disclosure.

[0047] Referring to FIG. 1, an electronic device (101) can be connected to an access point (AP) (200) based on Wi-Fi communication. The electronic device (101) may include a processor (120) and a communication module (190).

[0048] According to one embodiment, the communication module (190) can receive a signal from the outside or transmit a signal to the outside based on a Wi-Fi communication method (e.g., IEEE 802.11be-based communication). For example, the communication module (190) can operate based on IEEE 802.11ac, 802.11ax, 802.11be, or 802.11bn among Wi-Fi communication methods, and in particular, IEEE 802.11be or 802.11bn can support wider bandwidth, higher data throughput, and shorter latency compared to IEEE 802.11ax.

[0049] The communication module (190) may include a transceiver (191) for transmitting and receiving data with an external device and a communication processor (193) (e.g., a communication processor (not shown), or a short-range wireless communication module (e.g., a Wi-Fi chipset)). According to one embodiment, the communication module (190) may further include memory.

[0050] According to one embodiment, the transceiver (191) can convert a baseband transmission signal into a wireless signal or convert a received wireless signal into a baseband reception signal.

[0051] According to various embodiments, the communication module (190) may further include, in addition to the transceiver (191) and the communication processor (193), components for orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), e.g., a modulator, a digital-analog converter, a frequency converter, an A / D converter, an amplifier, and / or a demodulator.

[0052] Although not illustrated, according to various embodiments, the electronic device (101) may be electrically connected to a communication module of an access point (200) and may include at least one antenna module that supports a communication protocol and / or frequency band supported by the communication module of the access point (200).

[0053] According to one embodiment, a communication processor (193) can control a transceiver (191) to form a communication connection with an access point (200). For example, the communication connection may include a Wi-Fi network. For example, the communication processor (193) can control a transceiver (191) to form a wireless connection with the access point (200) using a wireless local area network (WLAN) standard in the 2.4 GHz, 5 GHz, or 6 GHz band, such as IEEE 802.11ac, 802.11ax, 802.11be, or 802.11bn. Alternatively, the communication processor (193) can control a transceiver (191) to form a wireless connection with the access point (200) using a WLAN standard in the 60 GHz band, such as IEEE 802.11ad or 802.11ay.

[0054] According to one embodiment, a method of communicating between an electronic device (101) and an access point (200) using a wireless local area network (WLAN) standard may be referred to as a communication method based on STA mode.

[0055] According to one embodiment, the processor (120) may include an application processor. The processor (120) may perform a specified operation of the electronic device (101) or control other hardware (e.g., a communication module (190)) to perform a specified operation.

[0056] According to one embodiment, the access point (200) can support the operation of transmitting data to an external network and / or the operation of receiving data from an external network by a plurality of electronic devices (e.g., electronic device (101)) based on a connection between a plurality of electronic devices and an external network (e.g., Internet, external LAN, or cellular network).

[0057] According to one embodiment, the access point (200) may be a wireless router. The access point (200) may be a dedicated wireless router or a general-purpose device that supports a mobile hotspot function, and there are no limitations on its implementation. For example, the access point (200) may include the same components as the electronic device (101).

[0058] According to one embodiment, the access point (200) can transmit and receive data with an external device, such as a server or an electronic device (101). For example, the access point (200) can transmit at least some of the data received from the server to the electronic device (101). According to one embodiment, the access point (200) and the electronic device (101) can transmit and receive UL (uplink) / DL (downlink) data during an operation period. For example, the access point (200) can transmit traffic to the electronic device (101) only during an operation period set based on schedule information received from the electronic device (101).

[0059] FIG. 2 is a diagram illustrating the operation of an access point and a station for establishing a Wi-Fi connection according to one embodiment of the present disclosure.

[0060] Referring to FIG. 2, the access point (210) can be implemented as the access point (200) of FIG. 1 and can communicate with the station (220) based on Wi-Fi. The station (220) can be implemented as the electronic device (101) of FIG. 1. The station (220) may be a terminal (or a terminal having a Wi-Fi interface) that supports Wi-Fi communication according to the IEEE 802.11 standard.

[0061] A station (220) may transmit (or broadcast) a probe request message to an access point (210) (S201). According to one embodiment, the probe request message may be a message for the station (220) to search for nearby access points (210). According to one embodiment, the probe request message may include information regarding at least one communication capability supported by the station (220). According to one embodiment, the station (220) may receive a beacon message from the access point (210) and transmit a probe request message to the access point (210) based on the information contained in the beacon message. The access point (210) may transmit a probe response message in response to the probe request message (S202).

[0062] Upon receiving the probe response message, the station (220) may send an authentication request message to the access point (210) (S203). The access point (210) sends an authentication response message to the station (220) in response to the authentication request message (S204), and the authentication procedure between the access point (210) and the station (220) may be completed. According to one embodiment, the authentication procedure of S203 and S204 may be a process of selecting and authenticating the channel with the strongest reception strength among the messages received during the channel discovery process. According to one embodiment, through the authentication procedure of S203 and S204, the station (220) and the access point (210) may negotiate the encryption method of the authentication procedure.

[0063] When the authentication process is completed, the station (220) may send an association request message to the access point (210) to perform an association setup for the access point (210) (S205). According to one embodiment, the association request message may include information regarding at least one capability to be used for data communication between the station (220) and the access point (210) (e.g., according to the IEEE 802.11 standard). The access point (210) may generate an association ID (AID) for the station (220) and send an association response message to the station (220) (S206).

[0064] FIG. 3 is a diagram illustrating a Co-TDMA operation that shares TXOPs owned between APs according to one embodiment of the present disclosure.

[0065] Co-TDMA (Coordinated Time Division Multiple Access) can refer to the function of sharing transmission opportunities (TXOPs) owned by access points (APs). A TXOP can mean setting a limited fixed period to allow a specific access point (AP) to access a specific channel without competition.

[0066] In the present disclosure, an AP that acquires and shares a TXOP may be referred to as a Sharing AP or TXOP Owner AP, and an AP that receives a shared TXOP may be referred to as a Shared AP or Candidate AP. In FIG. 3, a Sharing AP (310) may form a first Basic Service Set (BSS) with a station (STA) (330), and a Shared AP (320) may form a second BSS different from the first BSS. A BSS may include one AP and at least one STA.

[0067] Referring to FIG. 3, the Sharing AP (310) that has acquired the TXOP transmits a Multi User-Request to Send (MU-RTS), and the station (STA) (330) that has received the MU-RTS can transmit a Clear to Send (CTS) to the Sharing AP (310).

[0068] A Sharing AP (310) that has acquired a TXOP may transfer its TXOP to a Shared AP (320) when it finishes its frame exchange sequence or when transmission through a nearby AP (e.g., transmission through a Shared AP (320)) is required for a specific reason (e.g., a request to process LL (Low latency) traffic).

[0069] The Sharing AP (310) can send a MU-RTS TXS (triggered TXOP sharing) TF (trigger frame) to the Shared AP (320) to trigger the Shared AP (320) to use at least a portion of the TXOP (shared TXOP) acquired by the Sharing AP (310). The Shared AP (320), having received the MU-RTS TXS TF within at least a portion of the TXOP (shared TXOP), can send a CTS to the Sharing AP (310). Afterward, the Shared AP (320) can return the TXOP to the Sharing AP (310) once it has completed its frame exchange sequence.

[0070] FIG. 4 is a diagram illustrating a procedure for Multi-AP operation at the TXOP level according to one embodiment of the present disclosure.

[0071] In FIG. 4, the AP that acquires the TXOP and initiates Multi-AP operation may be referred to as the TXOP Owner AP (410), and the AP that shares the TXOP may be referred to as the Candidate AP (420). In FIG. 4, the TXOP Owner AP (410) may form a first BSS with a station (STA) (430), and the Candidate AP (420) may form a second BSS different from the first BSS.

[0072] The TXOP Owner AP (410) that has acquired the TXOP can transmit an ICF (Initial Control Frame) containing a BSRP (Buffer Status Report Poll). The Candidate AP (420) can receive the ICF and transmit an ICR (initial control response frame) corresponding to the ICF to the TXOP Owner AP (410). According to one embodiment, the station (STA) (430) can receive the ICF and transmit an ICR corresponding to the ICF to the TXOP Owner AP (410). The TXOP Owner AP (410) and the Candidate AP (420) can set up a Multi-AP operation in a section (Acquired TXOP by Sharing AP) that occurs continuously through the exchange of ICF-ICR pairs.

[0073] According to one embodiment, the ICF may include information regarding Multi-AP operations that a Candidate AP (420) can perform within a TXOP interval acquired by a TXOP Owner AP (410). According to one embodiment, the ICF may include a request for information required for the Candidate AP (420) to perform Multi-AP operations within a TXOP interval acquired by a TXOP Owner AP (410). According to one embodiment, the ICR may include information required for the Candidate AP (420) to perform Multi-AP operations within a TXOP interval corresponding to the request.

[0074] The TXOP Owner AP (410) transmits a MU-RTS, and the station (STA) (430) and / or Candidate AP (420) that receives the MU-RTS can transmit a CTS to the TXOP Owner AP (410). The TXOP Owner AP (410) and Candidate AP (420) can determine (or perform) a Multi-AP operation through the exchange of MU-RTS and / or CTS.

[0075] The present disclosure proposes a field format to be added to at least one of ICF, ICR, and MU-RTS to set up Multi-AP operation.

[0076] Multi-AP operation may include multiple phases and / or procedures among multiple APs. Multi-AP operation may include a Multi-AP setup phase and / or a Multi-AP coordination phase.

[0077] In the Multi-AP setup phase, at least one of information exchange between multiple APs and grouping operations for Candidate APs can be performed.

[0078] In the Multi-AP coordination phase, at least one of the following may be performed: information exchange between the TXOP Owner AP (or Sharing AP) and the Candidate AP (or Shared AP), the TXOP Owner AP (or Sharing AP) selecting the Candidate AP (or Shared AP), the Multi-AP channel sounding phase, the Multi-AP data sharing phase, and the Multi-AP transmission scheme.

[0079] In the Multi-AP channel sounding phase, the AP can perform channel sounding together with or independently of the station (STA). In the Multi-AP data sharing phase, the TXOP Owner AP (or Sharing AP) can share data with the Candidate AP (or Shared AP). The Multi-AP transmission scheme may include at least one of Co-TDMA, CSR (coordinated spatial reuse), coordinated OFDMA / TDMA, Co-BF (coordinated beamforming), Co-SR (coordinated spatial reuse), Co-rTWT (coordinated restricted Target Wake Time), and JT / JT (joint transmission / reception).

[0080] According to one embodiment, the TXOP Owner AP (410) can transmit whether it accepts the Multi-AP operation to the Candidate AP (420) via MU-RTS.

[0081] According to one embodiment, if the Multi-AP operation accepted by the TXOP Owner AP (410) via MU-RTS is Co-TDMA, the TXOP Owner AP (410) may perform TXOP level scheduling based on the TXOP request value and / or LL Indication exchanged in the ICF and / or ICR. The TXOP Owner AP (410) may perform TXOP level scheduling related to the Multi-AP operation for its BSS and Candidate AP (420).

[0082] According to one embodiment, if the Multi-AP operation accepted by the TXOP Owner AP (410) via MU-RTS is Co-BF (or Co-SN), the TXOP Owner AP (410) may perform a Sounding procedure and Co-BF (or Co-SN) operation scheduling to perform the Co-BF (or Co-SN) operation.

[0083] According to one embodiment, if the Multi-AP operation accepted by the TXOP Owner AP (410) via MU-RTS is Co-rTWT, the TXOP Owner AP (410) may reflect whether the TXOP has ended prior to the rTWT.

[0084] According to one embodiment, if Candidate APs respond to MU-RTS, the possibility of resolving the hidden node problem may be improved. However, in order to resolve the over-protection problem that occurs when Candidate APs respond to MU-RTS, Candidate APs that have received information about Co-TDMA may not respond to MU-RTS.

[0085] FIG. 5a is a drawing showing a first type of User Info field according to one embodiment of the present disclosure.

[0086] The TXOP Owner AP (or Sharing AP) that has acquired the TXOP may transmit an ICF containing a first type of User Info field to announce its transmission information. The TXOP Owner AP (or Sharing AP) may transmit separate information for each type of Multi-AP operation using the first type of User Info field shown in FIG. 5a. Depending on the Multi-AP operation, multiple User Info fields having a single AID may be transmitted.

[0087] Referring to FIG. 5a, the User Info field may include at least one of the AP AID12 field, Control field, Data field, Request bitmap field, and Reserved field.

[0088] The AP AID12 field may indicate the AID of the TXOP Owner AP (or Sharing AP). By assigning a specific AP AID that designates the Sharing AP to the AP AID12 field, it may be indicated that the User Info field contains information about the Sharing AP.

[0089] The Control field is a control field for distinguishing the Data field and can indicate the type of Multi-AP transmission supported by the TXOP Owner AP (or Sharing AP). For example, if the Control field is a first value (e.g., 0), it indicates Co-TDMA; if the Control field is a second value (e.g., 1), it indicates Co-BF; and if the Control field is a third value (e.g., 2), it indicates Co-rTWT.

[0090] The Data field may include data regarding the type of Multi-AP transmission set in the Control field. For example, if the Control field indicates Co-TDMA, the Data field may include Allocation duration, and if the Control field indicates Co-BF, it may include STA AID12, Request Sounding Procedure, etc.

[0091] The Request bitmap field can represent a bitmap of information requested from the shared AP for multi-AP operation.

[0092] FIG. 5b is a drawing showing a second type of User Info field according to one embodiment of the present disclosure.

[0093] A TXOP Owner AP (or Sharing AP) that has acquired a TXOP may transmit an ICF containing a second type of User Info field to indicate its transmission information. The TXOP Owner AP (or Sharing AP) may transmit one second type of User Info field per AID. According to one embodiment, the TXOP Owner AP (or Sharing AP) may compress the information and transmit one User Info field per AID.

[0094] Referring to FIG. 5b, the User Info field may include at least one of the AP AID12 field, Bitmap field, STA AID12 field, Allocation duration field, and Reserved field.

[0095] The AP AID12 field may indicate the AID of the TXOP Owner AP (or Sharing AP). By assigning a specific AP AID that designates the Sharing AP to the AP AID12 field, it may be indicated that the User Info field contains information about the Sharing AP.

[0096] The Bitmap field may indicate a Multi-AP scheme indicated by the type of the corresponding User Info field. The Multi-AP scheme may include at least one of Co-TDMA, CSR (coordinated spatial reuse), coordinated OFDMA / TDMA, Co-BF (coordinated beamforming), Co-rTWT (coordinated restricted Target Wake Tim), and JT / JT (joint transmission / reception).

[0097] The STA AID12 field can indicate the AID of the station (STA) that the Sharing AP will serve.

[0098] The Allocation duration field can specify the duration to be served to the corresponding AP AID12.

[0099] FIG. 6 is a drawing showing an M-BA (Multi-Block Ack) according to one embodiment of the present disclosure.

[0100] The Candidate AP (or Shared AP) receives the ICF and can transmit an ICR corresponding to the ICF to the TXOP Owner AP (or sharing AP). The ICR can be implemented in the M-BA (Multi-Block Ack) format shown in FIG. 6.

[0101] Referring to FIG. 6, the ICR implemented in the M-BA format may include an AID TID Info field, a Block Ack Starting Sequence Control field, and a Block Ack Bitmap field.

[0102] The AID TID Info field may include an AID11 subfield, an Ack Type subfield, and a TID (traffic identifier) ​​subfield. The Block Ack Starting Sequence Control field may include a Fragment number subfield indicating Bitmap Size and a Starting Sequence Number subfield. The Block Ack Bitmap field may include M-AP Operation info. The M-AP Operation info is described in detail in FIG. 7 or FIG. 9.

[0103] FIG. 7 is a diagram showing Multi-AP operation information (M-AP Operation Info) according to one embodiment of the present disclosure.

[0104] A Candidate AP (or Shared AP) receives an ICF and can transmit an ICR corresponding to the ICF to a TXOP Owner AP (or sharing AP). The ICR may include Multi-AP Operation Info (M-AP Operation Info) illustrated in FIG. 7. According to one embodiment, the Multi-AP Operation Info (M-AP Operation Info) may be transmitted by being included in the Block Ack Bitmap field illustrated in FIG. 6.

[0105] Referring to FIG. 7, Multi-AP Operation Info may include at least one of a Control field, an AP AID field, a Present bit field, a Requested Allocation Duration field, an LL Traffic indication field, an Access Category field, and a Reserved field.

[0106] According to one embodiment, the Control field may include information (e.g., 2 to 12 bits) indicating that the ICR includes Multi-AP Operation Information (M-AP Operation Info). According to one embodiment, the information indicating that the ICR includes Multi-AP Operation Information (M-AP Operation Info) may be transmitted through the Ack Type subfield, TID subfield, Ack Type subfield + TID subfield, Starting Sequence Number subfield, or part of the Block Ack Bitmap field included in the M-BA of FIG. 6.

[0107] According to one embodiment, the AP AID field represents information specifying the Sharing AP and may be implemented as an 11-bit AP AID 11 field or a 12-bit AP AID 12 field. According to one embodiment, the information specifying the Sharing AP may be transmitted through a part of the Starting Sequence Number subfield or Block Ack Bitmap field included in the M-BA of FIG. 6.

[0108] The Present bit field may specify information indicated (or contained) by the corresponding Block Ack Bitmap (e.g., 8 bits).

[0109] The Reserved field can be composed of variable bits.

[0110] According to one embodiment, the ICR or Multi-AP Operation Info may include rejection information (bit level (1 bit) or reason code (2 octets)) for Multi-AP operation. The rejection information may indicate at least one rejection reason among Nothing to serve / Buffer is empty, Channel is not good for beamforming / Spatial nulling, Not supported PPDU version in beamforming / Spatial nulling manner, or Not enough time to serve.

[0111] According to one embodiment, the ICR or Multi-AP operation information (M-AP Operation Info) may include Co-TDMA specific information (Specific Info).

[0112] According to one embodiment, the Requested Allocation Duration field included in the ICR or Multi-AP Operation Info (M-AP Operation Info) may indicate the requested Co-TDMA duration (e.g., 0 or 9 bits). According to one embodiment, the requested Co-TDMA duration may be transmitted through a portion of the Block Ack Bitmap field included in the M-BA of FIG. 6.

[0113] According to one embodiment, an LL Traffic indication field (e.g., 0 or 1 bit) included in the ICR or Multi-AP Operation Info (M-AP Operation Info) may be transmitted through a part of the Block Ack Bitmap included in the M-BA of FIG. 6.

[0114] According to one embodiment, the Traffic Deadline Info field included in the ICR or Multi-AP Operation Info (M-AP Operation Info) may indicate the deadline of the current traffic (e.g., 0 or 16 bits). According to one embodiment, the Traffic Deadline Info field may be transmitted through a part of the Block Ack Bitmap included in the M-BA of FIG. 6.

[0115] According to one embodiment, the Access Category field included in the ICR or Multi-AP Operation Info (M-AP Operation Info) may indicate the Access Category of the currently held traffic (e.g., 0 or 4 bits). According to one embodiment, the Access Category field may be transmitted through a part of the Block Ack Bitmap included in the M-BA of FIG. 6.

[0116] FIG. 8a shows a bandwidth information field format according to one embodiment of the present disclosure, and FIG. 8b shows a control subfield format within the bandwidth information field.

[0117] According to one embodiment, the ICR or Multi-AP Operation Info may include a bandwidth information field indicating bandwidth information to be used during Co-TDMA operation (e.g., 3 or 5 octets).

[0118] Referring to FIG. 8a, the bandwidth information field may include at least one of the Control subfield, CCFS0 subfield, CCFS1 subfield, and Disable Subchannel Bitmap subfield. The CCFS0 subfield may represent the value of the CCFS (Channel Center Frequency Segment) 0 field, and the CCFS1 subfield may represent the value of the CCFS 1 field.

[0119] Referring to FIGS. 8a and 8b, the Control sub-field within the bandwidth information field may include a Channel Width sub-field, a Disable Subchannel Bitmap Present sub-field, and a Reserved sub-field. The Disable Subchannel Bitmap Present sub-field may indicate the existence of the Disable Subchannel Bitmap sub-field (e.g., 1 bit).

[0120] FIG. 9 is a diagram showing Multi-AP operation information (M-AP Operation Info) according to one embodiment of the present disclosure.

[0121] A Candidate AP (or Shared AP) receives an ICF and can transmit an ICR corresponding to the ICF to a TXOP Owner AP (or sharing AP). The ICR may include Multi-AP Operation Info (M-AP Operation Info) illustrated in FIG. 9. According to one embodiment, the Multi-AP Operation Info (M-AP Operation Info) may be transmitted by being included in the Block Ack Bitmap field illustrated in FIG. 6.

[0122] Referring to FIG. 9, Multi-AP Operation Info may include at least one of a Control field, an AP AID field, a Bitmap field, an STA AID field, a Sounding Requesting field, and a Steering Matrix field.

[0123] According to one embodiment, the Control field may include information (e.g., 2 to 12 bits) indicating that the ICR includes Multi-AP Operation Information (M-AP Operation Info). According to one embodiment, the information indicating that the ICR includes Multi-AP Operation Information (M-AP Operation Info) may be transmitted through the Ack Type subfield, TID subfield, Ack Type subfield + TID subfield, Starting Sequence Number subfield, or part of the Block Ack Bitmap field included in the M-BA of FIG. 6.

[0124] According to one embodiment, the AP AID field represents information specifying the Sharing AP and may be implemented as an 11-bit AP AID 11 field or a 12-bit AP AID 12 field. According to one embodiment, the information specifying the Sharing AP may be transmitted through a part of the Starting Sequence Number subfield or Block Ack Bitmap field included in the M-BA of FIG. 6.

[0125] According to one embodiment, the ICR or Multi-AP Operation Info (M-AP Operation Info) may include Co-BF (Coordinated Beamforming) and / or Co-SN (Coordinated Spatial Nulling) related information.

[0126] According to one embodiment, the STA AID field represents information specifying the STA and may be implemented as a 12-bit STA AID 12 field. According to one embodiment, the STA AID field may indicate the STA AID to be served during Co-BF or Co-SN operation (e.g., 0 or 12 bits).

[0127] According to one embodiment, the Bitmap field may indicate a bit (HT (high throughput) / VHT (very high throughput) / HE (high efficiency) / EHT (extremely high throughput),,) representing the PPDU (physical layer protocol data unit) type required for Co-BF or Co-SN operation (e.g., 0 or 4 bits).

[0128] According to one embodiment, the Sounding Requesting field may indicate Sounding Requesting information required for BF or Co-SN operation (e.g., 0 or 1 bit).

[0129] According to one embodiment, the Steering Matrix field may indicate Steering Matrix information required for Co-BF or Co-SN operation (e.g., 0 or variable bit).

[0130] According to one embodiment, the Reserved field may be composed of a variable bit.

[0131] According to one embodiment, the ICR or Multi-AP Operation Info (M-AP Operation Info) may include an index (0 or 8 bit) designating a predefined Steering Matrix required for Co-BF or Co-SN operation.

[0132] According to one embodiment, the ICR or Multi-AP operation information (M-AP Operation Info) may include a Beamforming Feedback Matrix request required for Co-BF or Co-SN operation (0 or 1 bit).

[0133] According to one embodiment, the ICR or Multi-AP operation information (M-AP Operation Info) may include a Beamforming Feedback Matrix required for Co-BF or Co-SN operation (0 or variable bit).

[0134] According to one embodiment, the ICR or Multi-AP Operation Info may include a set of possible NSS (number of spatial streams) of the STA during Co-BF or Co-SN operation (e.g., 0 or variable bit).

[0135] According to one embodiment, the ICR or Multi-AP Operation Info (M-AP Operation Info) may include information regarding possible NSS of the STA during Co-BF or Co-SN operation (e.g., 0 or variable bit).

[0136] According to one embodiment, the ICR or Multi-AP Operation Info may include MU-MIMO information of the STA during Co-BF or Co-SN operation. The MU-MIMO information of the STA may include at least one of the number of STAs, the identifier of each STA (STA IDs), and the NSS of each STA.

[0137] According to one embodiment, the ICR or Multi-AP operation information (M-AP Operation Info) may include ACK policy information (e.g., 0 or 4 bits). According to one embodiment, if the ACK policy information is a first value (e.g., 0), it may indicate No Limit; if the ACK policy information is a second value (e.g., 1), it may indicate Delayed ACK; and if the ACK policy information is a third value (e.g., 2), it may indicate Ack in other TXOP.

[0138] According to one embodiment, the ICR or Multi-AP operation information (M-AP Operation Info) may include feedback information of the previous Co-BF or Co-SN.

[0139] According to one embodiment, the ICR or Multi-AP Operation Info may include Co-rTWT related information. According to one embodiment, the ICR or Multi-AP Operation Info may include time to the next operation rTWT (TWT) information (e.g., 0 or 16 bits). According to one embodiment, the time to the next operation rTWT (TWT) information may be included in a part of the Block Ack Bitmap and transmitted.

[0140] According to one embodiment, the ICR or Multi-AP Operation Info may include TWT element Broadcast TWT information (e.g., 0 or 12 octets).

[0141] According to one embodiment, the ICR or Multi-AP Operation Info may include restricted TWT Traffic information within the TWT element (e.g., 0 or 3 octets).

[0142] According to one embodiment, the ICR or Multi-AP Operation Info may include BW information to be used during TWT SP (service period) operation (e.g., 3 or 5 octets).

[0143] FIG. 10a shows a bandwidth information field format according to one embodiment of the present disclosure, and FIG. 10b shows a control subfield format within the bandwidth information field.

[0144] According to one embodiment, the ICR or Multi-AP Operation Info may include a bandwidth information field indicating bandwidth information to be used during TWT SP operation (e.g., 3 or 5 octets).

[0145] Referring to FIG. 10a, the bandwidth information field may include at least one of a Control subfield, a CCFS0 subfield, a CCFS1 subfield, and a Disable Subchannel Bitmap subfield. The CCFS0 subfield may represent the value of the CCFS (Channel Center Frequency Segment) 0 field, and the CCFS1 subfield may represent the value of the CCFS 1 field.

[0146] Referring to FIGS. 10a and 10b, the Control sub-field within the bandwidth information field may include a Channel Width sub-field, a Disable Subchannel Bitmap Present sub-field, and a Reserved sub-field. The Disable Subchannel Bitmap Present sub-field may indicate the existence of the Disable Subchannel Bitmap sub-field (e.g., 1 bit).

[0147] FIG. 11 is a drawing showing a User info field included in a MU-RTS TXS (triggered TXOP sharing) trigger frame (TF) according to one embodiment of the present disclosure.

[0148] The TXOP Owner AP (or sharing AP) can send the MU-RTS TXS TF to the Candidate AP (or Shared AP) to trigger the Candidate AP (or Shared AP) to use at least a portion (shared TXOP) of the TXOP acquired by the TXOP Owner AP (or sharing AP).

[0149] Referring to FIG. 11, the MU-RTS TXS TF may include an AID 12 field, a RU allocation field, an Allocation Duration field, a Reserved field, and a PS 160 field. The AID 12 field is an indicator field to designate the AP or non-AP STA to respond to the corresponding trigger frame, and the RU allocation field designates the RU (Resource Unit) to be used when the AP or non-AP STA responds. The Allocation Duration field is a field to indicate the amount of TXOP to be allocated during the TXS operation, and the PS 160 field indicates that if set to 1, the 320 MHz channel is used, and if set to 0, the primary 20 MHz channel, primary 40 MHz channel, primary 80 MHz channel, and primary 160 MHz channel are used.

[0150] According to one embodiment, when operating a sounding procedure for Co-BF or Co-SN, the User Info Field of the MU-RTS TXS TF may include an indicator indicating that it is a MU-RTS TXS TF for sounding (e.g., 1 bit). According to one embodiment, when operating a sounding procedure for Co-BF or Co-SN, the User Info Field of the MU-RTS TXS TF may include a request requesting transmission of a Beamforming Feedback Matrix after sounding (e.g., 1 bit).

[0151] FIG. 12 is a flowchart for explaining the operation of a first AP (TXOP Sharing AP or TXOP Owner AP) according to one embodiment of the present disclosure.

[0152] Referring to FIG. 12, in operation 1210, a first AP (TXOP Sharing AP) may transmit a first message to a second AP (TXOP Shared AP or Candidate AP) to trigger a Multi-AP operation. According to one embodiment, the first message may be implemented as an ICF. In operation 1220, the first AP (TXOP Sharing AP) may receive a second message from the second AP (TXOP Shared AP) in response to the first message. The second message may include support information and / or capability information of the second AP (TXOP Shared AP) regarding the Multi-AP operation. According to one embodiment, the first message may be implemented as an ICF, and the second message may be implemented as an ICR.

[0153] In operation 1230, the first AP (TXOP Sharing AP) can determine whether to perform a Multi-AP operation and determine configuration information based on the information included in the second message. In operation 1240, the first AP (TXOP Sharing AP) can transmit a third message containing configuration information and / or scheduling information for the Multi-AP operation to the second AP (TXOP Shared AP) to enable the Multi-AP operation to be performed. According to one embodiment, the third message may be a message transmitted by the first AP (TXOP Sharing AP) after an ICF / ICR exchange. According to one embodiment, the third message may be implemented as MU-RTS.

[0154] According to one embodiment, when the third message is implemented as MU-RTS, the third message may include a User Info Field List. The User Info Field List may include a plurality of User Info fields. Each of the plurality of User Info fields may include an AP AID12 field, a Control field, and a Data field. The AP AID12 field may indicate the AID of a specific AP that indicates which AP the corresponding User Info field relates to. The Control field may be an indicator referring to time information. The Data field may indicate an Allocation duration for TXOP usage.

[0155] According to one embodiment, the User Info Field List includes a plurality of user information fields, and the order of each user information field can implicitly indicate scheduling information for each of the plurality of APs.

[0156] For example, the User Info Field List may be listed in the order of the first User Info field (User Info field 1), the second User Info field (User Info field 2), and the third User Info field (User Info field 3). The AP AID 12 field within the first User Info field (User Info field 1) may be set to the TXOP Owner AP, the AP AID 12 field within the second User Info field (User Info field 2) may be set to the Candidate AP 2, and the AP AID 12 field within the third User Info field (User Info field 3) may be set to the Candidate AP 1. At this time, the User Info Field List may implicitly indicate that the TXOP is to be used in the order of TXOP Owner AP -> Candidate AP 2 -> Candidate AP 1. At this time, the TXOP Owner AP will use the TXOP first and perform a transmission for the Allocation duration period, and Candidate AP 2 can use the TXOP next.

[0157] FIG. 13 is a flowchart for explaining the operation of a second AP (TXOP Shared AP) according to one embodiment of the present disclosure.

[0158] Referring to FIG. 13, in operation 1310, the second AP (TXOP Shared AP) can receive a first message from the first AP (TXOP Sharing AP) to trigger a Multi-AP operation. In operation 1320, the second AP (TXOP Shared AP) can verify the Multi-AP operation requested by the first AP (TXOP Sharing AP) based on the information included in the first message. According to one embodiment, the first message can be implemented as an ICF.

[0159] In operation 1330, the second AP (TXOP Shared AP) selects the Multi-AP operation it requires and can transmit a second message containing support information and / or capability information regarding the selected Multi-AP operation to the first AP (TXOP Sharing AP). According to one embodiment, the first message may be implemented as an ICF, and the second message may be implemented as an ICR.

[0160] In operation 1340, the second AP (TXOP Shared AP) may receive a third message from the first AP (TXOP Sharing AP) containing configuration information and / or scheduling information for a Multi-AP operation. In operation 1350, the second AP (TXOP Shared AP) may check and / or perform a Multi-AP operation assigned and / or configured to itself based on the third message. According to one embodiment, the third message may be a message transmitted by the first AP (TXOP Sharing AP) after an ICF / ICR exchange. According to one embodiment, the third message may be implemented as a MU-RTS.

[0161] According to one embodiment, when the third message is implemented as a MU-RTS, the third message may include a User Info Field List. The User Info Field List may include a plurality of user information fields. According to one embodiment, the User Info Field List includes a plurality of user information fields and may implicitly indicate scheduling information for each of the plurality of APs through the order of each user information field.

[0162] The present disclosure proposes a method for APs to exchange information necessary to perform dynamic operations within a TXOP in a multi-AP environment. The information may be for controlling or scheduling at least one operation performed by the APs within the TXOP. FIG. 14 illustrates a method for APs to exchange information regarding multi-AP operations through ICF / ICR exchange during the polling phase in Co-TDMA. FIG. 15 illustrates a method for APs to exchange information regarding multi-AP operations through ICF / ICR exchange during the Invite / Response phase in Co-BF or Co-SR. The methods for exchanging information regarding multi-AP operations illustrated in FIG. 14 and FIG. 15 are examples to explain the technical concept of the present disclosure, and the technical concept of the present disclosure is not limited to the above examples and may be applied to Co-SN, Co-rTWT, or various transmission schemes.

[0163] FIG. 14 is a diagram illustrating an example in which ICF and ICR according to one embodiment of the present disclosure are utilized in Co-TDMA.

[0164] In FIG. 14, the first AP (1410) that shares the TXOP of the Co-TDMA may be referred to as the Co-TDMA Sharing AP or Co-TDMA Coordinating AP. The second AP (1420) or third AP (1413) that can receive the shared TXOP of the Co-TDMA may be referred to as the Co-TDMA Shared AP or Co-TDMA Coordinated AP.

[0165] Referring to FIG. 14, in the polling phase, the first AP (1410) may transmit an ICF containing allocation duration information indicating the sharing duration for the corresponding TXOP. The polling phase may refer to a procedure for a transmission request (or time slot request) in Co-TDMA. In the polling phase, the second AP (1420) and the third AP (1413) receive the ICF and, based on the allocation duration information included in the ICF, decide whether to proceed with a Co-TDMA operation or perform other operations (e.g., NPCA (Non-Primary Channel Access) or DPS (dynamic power saving), etc.).

[0166] According to one embodiment, when the second AP (1420) and / or the third AP (1413) decide to proceed with a Co-TDMA operation, the second AP (1420) and / or the third AP (1413) may send an ICR to the first AP (1410) as a response, which includes information that it is participating in the Co-TDMA and other information (e.g., at least one of the required TXOP duration and the delay bound of the traffic to be transmitted).

[0167] According to one embodiment, if the second AP (1420) and / or the third AP (1413) decides not to proceed with the Co-TDMA operation, it may send an ICR containing information that it is not participating in the Co-TDMA to the first AP (1410) as a response.

[0168] The first AP (1410) can exchange frames with stations (STAs) belonging to the same BSS. The first AP (1410) can perform scheduling for Co-TDMA operations after receiving an ICR. For example, the first AP (1410) can adjust the order of Co-TDMA Coordinated APs by considering the delay bound of the traffic to be transmitted. For example, the first AP (1410) can adjust the order of Co-TDMA Coordinated APs by considering the TXOP duration required by the Co-TDMA Coordinated AP and the delay bound of the traffic to be transmitted.

[0169] In the TXOP allocation phase, for example, the first AP (1410) can send a MU-RTS TXS (triggered TXOP sharing) TF (trigger frame) to the third AP (1430) to trigger the third AP (1430) to use at least a portion (shared TXOP) of the TXOP acquired by the first AP (1410). In the TXOP allocation phase, the third AP (1430) that receives the MU-RTS TXS TF can send a CTS to the first AP (1410).

[0170] Afterward, the third AP (1430) can perform a frame exchange sequence with stations (STAs) belonging to the same BSS. In the TXOP return phase, the third AP (1430) can return the TXOP to the first AP (1410).

[0171] FIG. 15 is a drawing illustrating an example in which ICF and ICR according to one embodiment of the present disclosure are utilized in Co-BF / Co-SR.

[0172] In FIG. 15, the first AP (1510) may be referred to as a Co-BF (or Co-SR) Sharing AP, and the second AP (1520) may be referred to as a Co-BF (or Co-SR) Shared AP.

[0173] The first AP (1510) may send an ICF containing information regarding whether sounding is required during the corresponding TXOP as an Invite message. Sounding may be a procedure in which a transmitting device transmits a specific frame to determine the wireless channel state, and a receiving device responds to this to provide feedback on the channel information.

[0174] The second AP (1520) receives the ICF and can determine whether to participate in Co-BF (or Co-SR) based on information regarding whether the sounding included in the ICF is required.

[0175] According to one embodiment, when the second AP (1520) decides to proceed with a Co-BF (or Co-SR) operation, the second AP (1520) may send an ICR to the first AP (1510) as a Response message, which includes information about participating in the Co-BF (or Co-SR) and other information (e.g., whether a sounding procedure is required, STA AID to proceed with the Co-BF (or Co-SR), etc.).

[0176] According to one embodiment, if the second AP (1520) decides not to proceed with the Co-BF (or Co-SR) operation, the second AP (1520) may send an ICR containing information that it does not participate in the Co-BF (or Co-SR) to the first AP (1510) as a Response message.

[0177] The first AP (1510) and the second AP (1520) can exchange information necessary to perform Co-BF (or Co-SR) PPDU (Physical Protocol Data Unit) transmission by exchanging Invite messages and Response messages.

[0178] The first AP (1510) can confirm the Co-BF (or Co-SR) transmission and transmit it to the second AP (1520) including necessary information (Sync).

[0179] After receiving the ICR, the first AP (1510) can proceed with the sounding procedure using the provided STA AID if sounding is required, and then start sending the Co-BF (or Co-SR) PPDU.

[0180] After receiving the ICR, the first AP (1510) can use the provided STA AID to start sending Co-BF (or Co-SR) PPDU if sounding is not required.

[0181] FIG. 16 is a diagram showing an example of a configuration of a first AP (TXOP Sharing AP) according to one embodiment of the present disclosure.

[0182] In FIG. 16, the first AP (TXOP Sharing AP) may include a processor (1601), a transceiver (1602), and a memory (1603). The processor (1601), transceiver (1602), and memory (1603) of the first AP (TXOP Sharing AP) may operate according to the method(s) described in the aforementioned embodiments of FIG. 1 to 15. However, the components of the first AP (TXOP Sharing AP) are not limited to the aforementioned examples. For example, the first AP (TXOP Sharing AP) may include more components or fewer components than the aforementioned components. Furthermore, the processor (1601), transceiver (1602), and memory (1603) may be implemented in the form of at least one chip.

[0183] The transceiver (1602) is a collective term for a receiver and a transmitter, and can transmit and receive signals with a station (STA) or another AP through the transceiver (1602). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1602) may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. This is merely one embodiment of the transceiver (1602), and the components of the transceiver (1602) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1602) may receive a signal and output it to a processor (1601), and transmit the signal output from the processor (1601) to a station (STA) or another AP.

[0184] The memory (1603) can store programs and data necessary for the operation of the first AP (TXOP Sharing AP) according to at least one of the embodiments of FIGS. 1 to 15. Additionally, the memory (1603) can store control information and / or data included in the signal obtained from the first AP (TXOP Sharing AP). The memory (1603) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD.

[0185] The processor (1601) can control a series of processes to enable the first AP (TXOP Sharing AP) to operate according to at least one of the embodiments of FIGS. 1 to 8. The processor (1601) may include at least one processor.

[0186] According to one embodiment, the processor (1601) may control the transmission of a first message to the second AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP. According to one embodiment, the processor (1601) may receive a second message from the second AP containing configuration information for the Multi-AP operation determined by the second AP based on the first message. According to one embodiment, the processor (1601) may control the transmission of a third message to the second AP indicating scheduling information for the Multi-AP operation determined based on the second message.

[0187] According to one embodiment, the Multi-AP operation may be such that, within the TXOP acquired by the first AP, the first AP and the second AP use at least one transmission scheme among Co-TDMA (coordinated time division multiple access), Co-BF (coordinated beamforming), Co-SR (coordinated spatial reuse), Co-SN (coordinated spatial nulling), and Co-rTWT (coordinated restricted target wake time).

[0188] According to one embodiment, the first message may include an association ID (AID) of the first AP, information indicating that the Multi-AP operation is performed using the Co-TDMA, an allocation duration for the Co-TDMA, and an indicator for information to be included in the second message. According to one embodiment, the second message may include at least one of a Co-TDMA duration, an LL traffic indication, a deadline for current traffic, an access category for current traffic, and a bandwidth to be used in the Co-TDMA.

[0189] According to one embodiment, the first message may include an association ID (AID) of the first AP, information indicating that the Multi-AP operation is performed using the Co-BF, an AID of the station to be served during the Co-BF operation, and an indicator for information to be included in the second message. According to one embodiment, the second message may include at least one of a sounding requesting required during the Co-BF operation, a steering matrix required during the Co-BF operation, a physical layer convergence procedure protocol data unit (PPDU) type required during the Co-BF operation, and a beamforming feedback matrix required during the Co-BF operation.

[0190] According to one embodiment, the first message may include an association ID (AID) of the first AP, information indicating that the Multi-AP operation is performed using the Co-rTWT, and an indicator for information to be included in the second message. According to one embodiment, the second message may include at least one of the time until the next operation rTWT, restricted TWT traffic information, and bandwidth information to be used when operating during the TWT service period (SP).

[0191] According to one embodiment, the third message may include a User Info Field List containing user information fields for each of the plurality of APs. Each of the user information fields may include an Association ID (AID) of a specific AP, an indicator indicating time information of the specific AP, and an allocation duration for the use of TXOPs of the specific AP. According to one embodiment, scheduling information of the plurality of APs may be implicitly determined according to the order of the user information fields included in the list.

[0192] FIG. 17 is a diagram showing an example of a configuration of a second AP (TXOP Shared AP) according to one embodiment of the present disclosure.

[0193] In FIG. 17, the second AP (TXOP Shared AP) may include a processor (1701), a transceiver (1702), and a memory (1703). The processor (1701), transceiver (1702), and memory (1703) of the second AP (TXOP Shared AP) may operate according to the method(s) described in the aforementioned embodiments of FIG. 1 to 15. However, the components of the second AP (TXOP Shared AP) are not limited to the aforementioned examples. For example, the second AP (TXOP Shared AP) may include more components or fewer components than the aforementioned components. Furthermore, the processor (1701), transceiver (1702), and memory (1703) may be implemented in the form of at least one chip.

[0194] The transceiver (1702) is a collective term for a receiver and a transmitter, and can transmit and receive signals with a station (STA) or another AP through the transceiver (1702). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1702) may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. This is merely one embodiment of the transceiver (1702), and the components of the transceiver (1702) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1702) may receive a signal and output it to a processor (1701), and transmit the signal output from the processor (1701) to a station (STA) or another AP.

[0195] The memory (1703) can store programs and data necessary for the operation of the second AP (TXOP Shared AP) according to at least one of the embodiments of FIGS. 1 to 15. Additionally, the memory (1703) can store control information and / or data included in the signal obtained from the second AP (TXOP Shared AP). The memory (1703) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD.

[0196] The processor (1701) can control a series of processes to enable the second AP (TXOP Shared AP) to operate according to at least one of the embodiments of FIGS. 1 to 15. The processor (1701) may include at least one processor.

[0197] According to one embodiment, the processor (1701) may receive a first message from the first AP to trigger a Multi-AP operation performed by the first AP and the second AP within a transmission opportunity (TXOP) acquired by the first AP. According to one embodiment, the processor (1701) may control the transmission of a second message to the first AP, which includes configuration information for the Multi-AP operation determined by the second AP based on the first message. According to one embodiment, the processor (1701) may receive a third message from the first AP indicating scheduling information for the Multi-AP operation determined based on the second message. In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in the singular or plural according to the specific embodiments presented. However, singular or plural expressions are selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular component, or even if a component is expressed in the singular, it may be composed of a plural component.

[0198] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method of a first AP (access point) performing Wi-Fi communication, An operation of transmitting a first message to the second AP to trigger a Multi-AP operation performed by the first AP and the second AP within a TXOP (transmission opportunity) acquired by the first AP; The operation of receiving a second message from the second AP containing setting information for the Multi-AP operation determined by the second AP based on the first message; and A method comprising the operation of transmitting a third message to the second AP, which directs scheduling information for the Multi-AP operation determined based on the second message.

2. In paragraph 1, the Multi-AP operation is, A method in which, within the TXOP acquired by the first AP, the first AP and the second AP use at least one transmission scheme among Co-TDMA (coordinated time division multiple access), Co-BF (coordinated beamforming), Co-SR (coordinated spatial reuse), Co-SN (coordinated spatial nulling), and Co-rTWT (coordinated restricted target wake time).

3. In paragraph 2, the first message is, A method comprising an association ID (AID) of the first AP, information indicating to perform the Multi-AP operation using the Co-TDMA, an allocation duration for the Co-TDMA, and an indicator for information to be included in the second message.

4. In paragraph 3, the second message is, A method comprising at least one of a Co-TDMA duration, an LL traffic indication, a deadline for current traffic, an access category for said current traffic, and a bandwidth to be used in said Co-TDMA.

5. In paragraph 2, the first message is, A method comprising the AID (association ID) of the first AP, information indicating to perform the Multi-AP operation using the Co-BF, the AID of the station to serve during the Co-BF operation, and an indicator for information to be included in the second message.

6. In paragraph 5, the above second message is, A method comprising at least one of a sounding requesting required for the Co-BF operation, a steering matrix required for the Co-BF operation, a PPDU (physical layer convergence procedure protocol data unit) type required for the Co-BF operation, and a beamforming feedback matrix required for the Co-BF operation.

7. In paragraph 2, the first message is, A method comprising an AID (association ID) of the first AP, information indicating to perform the Multi-AP operation using the Co-rTWT, and an indicator for information to be included in the second message.

8. In paragraph 7, the above second message is, A method comprising at least one of the time until the next operation rTWT, restricted TWT traffic info, and bandwidth information to be used during operation in the TWT SP (service period).

9. In Paragraph 1, The above third message includes a list (User Info Field List) containing user information fields for each of the plurality of APs, and A method in which each of the above user information fields includes an AID (association ID) of a specific AP, an indicator indicating time information of the specific AP, and an allocation duration for the use of the specific AP's TXOP.

10. In Paragraph 9, A method in which scheduling information of the plurality of APs is implicitly determined according to the order of the user information fields included in the above list.

11. A method of a second AP (access point) performing Wi-Fi communication, An operation of receiving a first message from the first AP to trigger a Multi-AP operation performed by the first AP and the second AP within a TXOP (transmission opportunity) acquired by the first AP; The operation of transmitting a second message to the first AP, the second message including setting information for the Multi-AP operation determined by the second AP based on the first message; and A method comprising receiving a third message from the first AP that indicates scheduling information for the Multi-AP operation determined based on the second message.

12. In Clause 11, the above Multi-AP operation is, A method in which, within the TXOP acquired by the first AP, the first AP and the second AP use at least one transmission scheme among Co-TDMA (coordinated time division multiple access), Co-BF (coordinated beamforming), Co-SN (coordinated spatial nulling), and Co-rTWT (coordinated restricted target wake time).

13. In Paragraph 12, The first message includes the association ID (AID) of the first AP, information indicating that the Multi-AP operation is performed using the Co-TDMA, the allocation duration for the Co-TDMA, and an indicator for information to be included in the second message. The above second message comprises at least one of a Co-TDMA duration, an LL traffic indication, a deadline of the current traffic, an access category of the current traffic, and a bandwidth to be used in the Co-TDMA.

14. In a first AP (access point) that performs Wi-Fi communication, Transmitter / receiver; and It includes a control unit, and the control unit is: Controlling the transmission of a first message to the second AP to trigger a Multi-AP operation performed by the first AP and the second AP within a TXOP (transmission opportunity) acquired by the first AP, and A second message containing setting information for the Multi-AP operation determined by the second AP based on the first message is received from the second AP, and A first AP that controls the transmission of a third message to the second AP, which directs scheduling information for the Multi-AP operation determined based on the second message.

15. In a second AP (access point) that performs Wi-Fi communication, Transmitter / receiver; and It includes a control unit, and the control unit is: Receiving a first message from the first AP to trigger a Multi-AP operation performed by the first AP and the second AP within a TXOP (transmission opportunity) acquired by the first AP, and Control to transmit a second message containing setting information for the Multi-AP operation determined by the second AP based on the first message to the first AP, and A second AP receiving from the first AP a third message instructing scheduling information for the Multi-AP operation determined based on the second message.

Images