Method and apparatus for multi-access point operation for wi-fi communication

Abstract

Proposed in the present disclosure is an operation of an access point (AP) in Wi-Fi communication. A method by which a first AP carries out Wi-Fi communication, according to an embodiment of the present disclosure, may comprise the steps of: transmitting, to a second AP, a first frame including quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of an access category (AC), a user priority (UP), and a traffic identifier (TID); receiving, from the second AP, a second frame responsive to the QoS information of the first AP; and on the basis of the second frame responsive to the QoS information of the first AP, carrying out a multi-AP operation with the second AP.

Description

Multi-access point operation method and device for Wi-Fi communication

[0001] The present disclosure relates to multi-AP operation in Wi-Fi communication.

[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 processing information for multi-AP operation in Wi-Fi communication.

[0007] A method of a first AP (access point) performing Wi-Fi communication according to one embodiment of the present disclosure may include: transmitting a first frame to a second AP containing quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID); receiving a second frame from the second AP in response to the QoS information of the first AP; and performing a Multi-AP operation with the second AP based on the second frame in response to the QoS information of the first AP.

[0008] A method of a second AP (access point) performing Wi-Fi communication according to one embodiment of the present disclosure may include: receiving from the first AP a first frame containing quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID); transmitting to the first AP a second frame responding to the QoS information of the first AP; and performing a Multi-AP operation with the first AP based on the second frame responding to the QoS information of the first AP.

[0009] According to one embodiment of the present disclosure, a first AP (access point) performing Wi-Fi communication may include a transceiver; and a control unit. The control unit controls the transmission of a first frame to a second AP that includes quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID); receives a second frame from the second AP that responds to the QoS information of the first AP; and performs a Multi-AP operation with the second AP based on the second frame that responds to the QoS information of the first AP.

[0010] 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: receive from the first AP a first frame containing quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID); control the transmission of a second frame responding to the QoS information of the first AP to the first AP; and perform a Multi-AP operation with the first AP based on the second frame responding to the QoS information of the first AP.

[0011] According to one embodiment of the present disclosure, an access point (AP) can improve Wi-Fi communication efficiency by sharing or negotiating quality of service (QoS) information or parameters for Multi-AP (M-AP) operation.

[0012] According to one embodiment of the present disclosure, an AP can improve Wi-Fi communication efficiency by sharing or negotiating enhanced distributed channel access (EDCA) parameters for M-AP operation.

[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 AP 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 diagram illustrating a procedure for Multi-AP operation according to one embodiment of the present disclosure.

[0018] FIG. 5b shows an example of the format of an R-TWT Traffic info field according to one embodiment of the present disclosure.

[0019] Figure 6 shows an example of how the quality of service (QoS) of traffic varies depending on the AP in a multi-AP environment.

[0020] FIG. 7a shows an example of a QoS Characteristics element used to transmit information regarding the QoS characteristics of AC / UP / TID according to one embodiment of the present disclosure.

[0021] FIG. 7b shows an example of a control info field used to transmit information regarding the QoS characteristics of AC / UP / TID according to one embodiment of the present disclosure.

[0022] FIG. 8a shows an example of a QoS and AC / UP / TID Mapping element (QoS to AC / UP / TID Mapping element) according to one embodiment of the present disclosure.

[0023] FIG. 8b shows an example of a Presence Bitmap subfield used to indicate QoS metrics according to one embodiment of the present disclosure.

[0024] FIG. 8c shows an example of a QoS and AC / UP / TID Mapping field (QoS to AC / UP / TID Mapping) according to one embodiment of the present disclosure.

[0025] FIG. 9a shows an example of an EDCA parameter set element according to one embodiment of the present disclosure.

[0026] FIG. 9b shows an example of a QoS information field transmitted by an AP according to one embodiment of the present disclosure.

[0027] FIG. 9c shows an example of an Update EDCA info field according to one embodiment of the present disclosure.

[0028] FIG. 10a shows an example of a MU EDCA parameter set element according to one embodiment of the present disclosure.

[0029] FIG. 10b shows an example of a QoS information field transmitted by an AP according to one embodiment of the present disclosure.

[0030] FIG. 11 is a drawing showing an example of a configuration of a first AP according to one embodiment of the present disclosure.

[0031] FIG. 12 is a drawing showing an example of a configuration of a second AP according to one embodiment of the present disclosure.

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

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

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

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

[0036] 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).

[0037] 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).

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

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

[0040] 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'.

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

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

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

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

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

[0046] 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).

[0047] 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.11-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.

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

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

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

[0051] 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).

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

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

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

[0055] 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).

[0056] 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).

[0057] 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).

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

[0059] 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 communication. 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.

[0060] 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).

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

[0062] 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).

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

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

[0065] In the present disclosure, an AP that acquires and shares a TXOP may be referred to as a Sharing AP or a TXOP Owner AP, an AP capable of receiving a shared TXOP may be referred to as a Candidate AP, and among the Candidate APs, an AP that receives a shared TXOP may be referred to as a Shared 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. According to one embodiment, a BSS may include one AP and at least one STA.

[0066] 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).

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

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

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

[0070] 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 candidate AP that can share 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.

[0071] 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 configure a Multi-AP operation in the acquired TXOP section (Acquired TXOP by Sharing AP) through the exchange of ICF-ICR pairs.

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

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

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

[0075] In the Multi-AP setup phase, at least one of the following may be performed: information exchange among multiple APs, discovery phase among APs, agreement establishment phase and parameter negotiation phase, and grouping operation for candidate APs.

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

[0077] In the above Multi-AP channel sounding phase, the AP can perform channel sounding together with or independently of the station (STA).

[0078] In the above Multi-AP data sharing phase, the TXOP Owner AP (or Sharing AP) can share data with the Candidate AP (or Shared AP). At this time, the Multi-AP operation scheme that can be used may include at least one of Co-TDMA, Co-BF (coordinated beamforming), Co-rTWT (coordinated restricted Target Wake Time), Co-SR (coordinated spatial reuse), coordinated OFDMA, and JT / JR (joint transmission / joint reception).

[0079] FIG. 5a is a diagram illustrating a procedure for Multi-AP operation according to one embodiment of the present disclosure.

[0080] In FIG. 5a, the AP that acquires the TXOP and initiates Multi-AP operation is referred to as the Sharing AP (510), and the APs that can share the TXOP may be referred to as Candidate AP1 (520) and Candidate AP2 (530). In FIG. 5a, the Sharing AP (510) can form a BSS with multiple stations (STAs) (540).

[0081] The Sharing AP (510) that has acquired the TXOP can transmit an Initial Control Frame (ICF) for polling. Polling can refer to a method in which a specific device in a network checks whether it can transmit data to a neighboring device. The ICF can signal the start of the polling process and may be a frame to check whether another device on the network is ready to start transmitting data.

[0082] Candidate AP1 (520) receives the ICF and can send a response frame (Resp) to the Sharing AP (510) indicating acceptance of polling in response to the ICF. Candidate AP2 (530) receives the ICF and can send a response frame (Resp) to the Sharing AP (510) indicating rejection of polling in response to the ICF. At least one of the plurality of stations (STAs) (540) receives the ICF and can send a response frame (Resp) to the Sharing AP (510) in response to the ICF.

[0083] The station (STA) that transmitted the response frame (Resp) can exchange frames with the Sharing AP (510) using the same channel within the Basic Service Set (BSS) (Intra-BSS frame exchange). Intra-BSS may refer to communication between the Sharing AP (510) and the station (STA) within the same BSS, or communication between multiple stations (STA) within the same BSS. That is, data exchanged between the Sharing AP (510) and the station (STA), or between multiple stations (STA), may be an example of Intra-BSS frame exchange.

[0084] Candidate AP1 (520), which has transmitted a response frame (Resp) instructing acceptance of polling, can perform a Multi-AP (M-AP) operation with the Sharing AP (510). According to one embodiment, the M-AP operation performed by Candidate AP1 (520) and the Sharing AP (510) may include at least one of Co-TDMA, Co-BF, Co-RTWT, Co-SR, coordinated OFDMA, and JT / JR. Co-TDMA, Co-BF, and Co-SR can prioritize traffic for shared TXOPs. In Co-RTWT, a Traffic ID (TID) for the R-TWT may be set.

[0085] A common framework for Multi-AP (M-AP) coordination can be defined for various coordination schemes. For example, a coordination scheme may be any one of Co-SR (Co-Simultaneous Data Transfer in the Same Frequency Band), Co-BF (Co-Beamforming), Co-TDMA (Time Division Multiple Access), or Co-RTWT (Reserved Transmission and Waiting Time Coordination).

[0086] The M-AP coordination framework may include Phase 1 (Discovery), Phase 2 (Agreement establishment and / or Parameter negotiation), and Phase 3 (M-AP operations). In Phase 1 (Discovery), APs may exchange information regarding supported M-AP functions, and no session / agreement establishment is established during Phase 1. In Phase 2 (Agreement establishment and / or Parameter negotiation), an agreement may be concluded through the exchange of individually addressed management frames between APs. If an agreement has already been concluded, Phase 2 may be used to update at least one parameter related to M-AP cooperation. The M-AP coordination framework ensures seamless cooperation among multiple APs and can be designed to improve wireless network performance and efficiently utilize resources.

[0087] In this disclosure, an M-AP operation is proposed that considers at least one of AC (Access Category), UP (User Priority), and TID (Traffic ID) to recommend a specific QoS (quality of service) (or priority) when exchanging information for an M-AP operation.

[0088] QoS can refer to a technology that guarantees the performance required by specific data flows (e.g., latency, bandwidth, loss rate, etc.) by providing priorities for various traffic types in a network.

[0089] Traffic types can be classified based on AC. According to one embodiment, AC can be classified into four categories: AC_VO (Voice), AC_VI (Video), AC_BE (Best Effort), and AC_BK (Background). Each category may have different priority and latency policies to meet various QoS requirements.

[0090] UPs can be defined based on the IEEE 802.1D 8-level priority system (0 to 7), and each UP can be mapped to a specific AC. For example, UPs 6 and 7 are mapped to AC_VO and can have high priority.

[0091] A TID is an identifier assigned to each data frame that enables the differentiation and management of traffic streams. Within a QoS frame, the TID provides management information regarding specific traffic flows, supporting appropriate processing and priority guarantees.

[0092] AC, UP, and TID can be part of a QoS mechanism to define data priority in wireless networks and ensure efficient transmission. This allows for the guarantee of the quality of time-sensitive data, such as voice and video streaming.

[0093] FIG. 5b shows an example of the format of an R-TWT Traffic info field according to one embodiment of the present disclosure.

[0094] The Traffic Info field format of R-TWT (Restricted Target Wake Time) is defined in the IEEE 802.11 standard and can be used to improve the power efficiency of the device and the efficiency of data transmission. R-TWT is primarily designed for low-latency applications (e.g., VR, AR, IoT), and the Traffic Info field can contain information to optimize data flow and scheduling.

[0095] Referring to FIG. 5b, the R-TWT traffic information field may include the Traffic Info Control field, the Restricted TWT DL TID Bitmap field, and the Restricted TWT UL TID Bitmap field. The R-TWT traffic information field may exist in the Restricted TWT Parameter Set field when the Restricted TWT Traffic Info Present sub-field of the Broadcast TWT Info sub-field is set to a set value (e.g., 1).

[0096] The Traffic Info Control field may include the DL TID Bitmap Valid subfield, the UL TID Bitmap Valid subfield, and the Reserved field.

[0097] The DL TID Bitmap Valid subfield can be set to a first value (e.g., 1) to indicate that the Restricted TWT DL TID Bitmap field is valid. If the DL TID Bitmap Valid subfield is set to a second value (e.g., 0), all TIDs among the Downlink (DL) traffic of the link associated with the R-TWT membership set by the TWT element are identified as Latency Sensitive traffic, and the Restricted TWT DL TID Bitmap field can remain in a reserved state.

[0098] The UL TID Bitmap Valid subfield can be set to a first value (e.g., 1) to indicate that the Restricted TWT UL TID Bitmap field is valid. If the UL TID Bitmap Valid subfield is set to a second value (e.g., 0), all TIDs among the UL (Uplink) traffic of the link associated with the R-TWT membership set by the TWT element are identified as latency-sensitive traffic, and the Restricted TWT UL TID Bitmap field can remain in a reserved state.

[0099] The Restricted TWT DL TID Bitmap field and the Restricted TWT UL TID Bitmap field can specify TIDs identified as latency-sensitive traffic streams in the DL and UL directions by an R-TWT scheduling AP (Access Point) or R-TWT scheduling STA (Station), respectively. For example, if a value of 1 is set at position k of each bitmap, TID k may be classified as a latency-sensitive traffic stream for that direction (DL or UL). For example, if a value of 0 is set at position k of each bitmap, TID k may not be classified as a latency-sensitive traffic stream for that direction. The Restricted TWT DL TID Bitmap field and the Restricted TWT UL TID Bitmap field can optimize R-TWT scheduling and transmission by specifically defining the latency sensitivity of DL and UL traffic.

[0100] Figure 6 shows an example of how the quality of service (QoS) of traffic varies depending on the AP in a multi-AP environment.

[0101] In wireless communication systems, various Access Categories (AC), User Priorities (UP), and / or Traffic Identifiers (TID) can be defined to classify and process traffic in order to ensure Quality of Service (QoS). However, even if traffic uses the same AC, UP, or TID, QoS characteristics may differ depending on the AP.

[0102] FIG. 6 illustrates an example of a wireless communication environment in which a first AP (AP1) and a second AP (AP2) handle traffic with different delay bound characteristics. The AC_VI traffic of the first AP (AP1) (when the Access Category is Video) has a delay bound of 20ms, but the AC_VI traffic of the second AP (AP2) may have a delay bound of 100ms. That is, even for traffic managed by the same AC_VI, the management value for QoS guarantee may differ for each AP. In the example of FIG. 6, the first AP (AP1) can manage traffic that is more sensitive to delay time than the second AP (AP2) through AC_VI and guarantee Quality of Service (QoS).

[0103] Referring to FIG. 6, the first AP (AP1) can negotiate a cooperative transmission setup with the second AP (AP2) by performing polling through an Initial Control Frame (ICF). At this time, the first AP (AP1) can inform the second AP (AP2) that it can only process AC_VI. The second AP (AP2) can agree to the negotiation by sending a response frame (Resp) indicating acceptance of the polling to the first AP (AP1).

[0104] In the frame exchange phase (Intra-BSS frame exchange), the first AP (AP1) can perform Intra-BSS frame exchange to satisfy a 20ms delay limit for AC_VI traffic. In this phase, delay-sensitive traffic may be processed first.

[0105] The first AP (AP1) can transmit request and transmission frames for multi-user transmission through MU-RTS (Multi-User Request to Send) frames and TXS TF (Trigger Frame). The second AP (AP2) can approve cooperative transmission by transmitting a CTS (Clear to Send) frame in response.

[0106] In the additional frame exchange stage (Intra-BSS frame exchange), the second AP (AP2) can perform Intra-BSS frame exchange to meet the 100ms delay limit of AC_VI traffic.

[0107] In the Co-TDMA method, the first AP (AP1) may want to restrict the QoS characteristics of traffic during a TXOP. For example, the first AP (AP1) may want to maintain the traffic delay limit at 20ms or less by limiting the AC of the traffic that can be transmitted within a Shared TXOP to AC_VI. However, if the AC_VI traffic of the second AP (AP2) has a delay limit of 100ms, the first AP (AP1) may fail to apply the same QoS constraint to the traffic of the second AP (AP2), which indicates a limitation of the Co-TDMA method.

[0108] In the Co-RTWT method, the first AP (AP1) can terminate its TXOP to protect less latency-sensitive traffic of the second AP (AP2). This allows the first AP (AP1) to optimize the QoS performance of the entire network while taking into account the QoS requirements of the second AP (AP2).

[0109] Meanwhile, wireless LAN (WLAN) systems operate based on the IEEE 802.11 standard and may adopt the Enhanced Distributed Channel Access (EDCA) mechanism to ensure quality of service (QoS). EDCA can adjust the probability of winning the channel by distinguishing traffic according to AC and assigning a differentiated priority to each traffic.

[0110] At this time, the channel access probability of EDCA can be determined by the parameters AIFSN (Arbitration Inter-Frame Space Number), CWmin (Contention Window minimum value), and CWmax (Contention Window maximum value). The AIFSN parameter represents the waiting time before frame transmission, the CWmin parameter represents the minimum window size used for backoff time calculation, and the CWmax parameter represents the maximum window size used for backoff time calculation.

[0111] However, even for traffic using the same AC, the AIFSN, CWmin, and CWmax values ​​may be set differently depending on the AP. Consequently, the priority of the traffic may change, and the probability of channel access may also vary.

[0112] Table 1 shows an example where two APs use different ACs and priorities.

[0113] [Table 1]

[0114]

[0115] In Table 1, the AC_VI of the first AP (AP1) has a priority similar to the AC_VO of the second AP (AP2). This demonstrates that even within the same traffic class, channel access probability and priority can vary depending on the AP. Even when the first AP (AP1) and the second AP (AP2) use the same AC, traffic from the first AP (AP1) may have a higher priority than traffic from the second AP (AP2), meaning that equitable channel access is not guaranteed. Consequently, STAs scheduled by the second AP (AP2) may experience higher latency and lower quality of service compared to STAs scheduled by the first AP (AP1). In the Co-TDMA method, the first AP (AP1) may wish to constrain the priority characteristics of traffic during a TXOP. For example, the first AP (AP1) may wish to maintain the priority or channel access probability of traffic by limiting the AC of traffic transmitted within a Shared TXOP to AC_VI. However, if the channel access probability of the AC_VI traffic of the second AP (AP2) is lower than that of the AC_VI traffic of the first AP (AP1), the first AP (AP1) may fail to apply the same channel access probability and priority constraints to the traffic of the second AP (AP2), which represents a limitation of the Co-TDMA method.

[0116] The present disclosure proposes an efficient method for providing and coordinating QoS based on AC, UP, and / or TID in a multi-AP environment. Unlike QoS management in a single AP environment, in a multi-AP environment, different APs must handle traffic with various QoS requirements, so a method is needed to dynamically advertise and negotiate QoS characteristics between APs.

[0117] <1-1 Example>

[0118] In a multi-AP environment, during the Discovery Phase, each AP can advertise the QoS characteristics of its traffic and adjust the characteristics of the traffic flow based on this.

[0119] The AP can advertise QoS characteristics for its traffic during the Discovery Phase. According to one embodiment, advertising for QoS characteristics may be performed in the form of a Representative Value of Existing Streams and / or Requirements for AC / UP / TID.

[0120] According to one embodiment, the AP analyzes the QoS characteristics of a currently active traffic flow, determines a Representative Value of Existing Streams for the corresponding AC / UP / TID based on the analysis results, and can advertise the Representative Value of the corresponding AC / UP / TID during the Discovery Phase. According to one embodiment, the AP can extract QoS characteristics from a Stream Classification Service (SCS) and set at least one value. The at least one value may include the Most Loose Requirement of the SCS stream in the AC / UP / TID and the Average Requirement of the SCS stream in the AC / UP / TID.

[0121] According to one embodiment, the AP may advertise requirements for AC / UP / TID during the Discovery Phase. According to one embodiment, the AP may map traffic with specific QoS requirements to specific AC / UP / TID. For example, the AP may assign traffic with a delay bound of 20ms or less to AC_VO. For example, the AP may assign traffic with a higher delay bound to AC_VI or AC_BE (Best Effort).

[0122] According to one embodiment, a multi-AP specific TID (M-AP Specific TID) may be assigned (or configured). The M-AP specific TID may be used to identify and manage traffic with specific QoS characteristics in a multi-AP environment.

[0123] [Table 2]

[0124]

[0125] Table 2 shows an example of a TID subfield. When the access policy is EDCA, TIDs 0 through 7 can be used for general traffic management. According to one embodiment, some or all of the TIDs greater than 7 in Table 2 may be assigned (or configured) as M-AP-only TIDs.

[0126] According to one embodiment, TIDs 12 to 15 of Table 2 may be assigned (or configured) as M-AP-only TIDs to indicate unique QoS characteristics. For example, TID 12 may indicate traffic with a delay bound of 20ms or less, TID 13 may indicate throughput-priority traffic, TID 14 may indicate reliability-priority traffic, and TID 15 may indicate traffic with the loosest QoS requirements.

[0127] <1st-2nd Example>

[0128] In a multi-AP environment, APs can negotiate the Quality of Service (QoS) characteristics of each AC, UP, and / or TID during the Agreement Establishment / Parameter Negotiation phase. The Requesting AP can transmit information regarding the QoS characteristics of each AC / UP / TID to the Responding AP. The Requesting AP can direct the mapping of QoS with AC / UP / TID for each AC / UP / TID, such as a Request or Announce / Suggest / Demand.

[0129] According to one embodiment, in the case of a request or an announcement, the requesting AP does not require the responding AP to change the QoS and AC / UP / TID mappings and may simply transmit information as a reference. According to one embodiment, a field distinguishing between a request or an announcement / suggest / demand may not be used, and the requesting AP may transmit information as a reference by not including a field distinguishing between a request or an announcement / suggest / demand.

[0130] According to one embodiment, in the case of a Suggest, the requesting AP may compromise its QoS and AC / UP / TID mapping and request the responding AP to change the mapping.

[0131] According to one embodiment, in the case of a demand, the requesting AP does not change its QoS and AC / UP / TID mapping and may request the responding AP to change the mapping.

[0132] <Examples 1-3>

[0133] In a multi-AP environment, APs can negotiate the QoS (Quality of Service) characteristics of each AC, UP, and / or TID during the Agreement Establishment / Parameter Negotiation phase. The Responding AP can transmit information regarding the QoS characteristics of each AC / UP / TID in response to a request from the Requesting AP.

[0134] The responding AP can instruct QoS and AC / UP / TID mappings, such as Accept / Alternate / Reject, for each AC / UP / TID.

[0135] According to one embodiment, in the case of Accept, the responding AP may transmit information regarding its QoS and AC / UP / TID mapping for reference in response to the request or announcement of the requesting AP. According to one embodiment, a field distinguishing Accept / Alternate / Reject may not be used, and the responding AP may transmit information for reference by not including a field distinguishing Accept / Alternate / Reject.

[0136] According to one embodiment, in the case of Accept, the responding AP may accept the Suggest or Demand request of the requesting AP.

[0137] According to one embodiment, in the case of an alternative, the responding AP may propose a different QoS and AC / UP / TID mapping to the requesting AP.

[0138] According to one embodiment, in the case of a rejection, the responding AP may disable M-AP (Multi-AP) operation using the corresponding AC / UP / TID.

[0139] FIG. 7a shows an example of a QoS Characteristics element used to transmit information regarding the QoS characteristics of AC / UP / TID according to one embodiment of the present disclosure.

[0140] In Wi-Fi standards, the QoS Characteristics element is a feature defined in IEEE 802.11ax (Wi-Fi 6) and later versions that can be used to define and manage Quality of Service (QoS) requirements for wireless networks.

[0141] A QoS Characteristics element is an element that provides information to enable a wireless device (AP or STA) to describe and negotiate the QoS requirements of traffic, and can be used primarily in at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase. A QoS Characteristics element can be included in at least one frame used in at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase.

[0142] Referring to FIG. 7a, the QoS Characteristics element may include an Element ID field (1 Octet), a Length field (1 Octet), an Element ID Extension field (1 Octet), a Control Info field (4 Octets), a Minimum Service Interval field (4 Octets), a Maximum Service Interval field (4 Octets), a Minimum Data Rate field (3 Octets), and a Delay Bound field (3 Octets).

[0143] The Element ID field (1 Octet) represents the identifier (ID) of the Element, the Length field (1 Octet) indicates the total length of the QoS characteristic element, and the Element ID Extension field (1 Octet) can support additional function configurations as an extension identifier. The Control Info field (4 Octets) contains control information and can encode information such as the negotiation status (Request, Suggest, Demand, Accept, Alternate, Reject). Reserved Bits can be used for signaling during the negotiation process. The Minimum Service Interval field (4 Octets) and the Maximum Service Interval field (4 Octets) can define the minimum and maximum intervals of the service transmission cycle, respectively. The Minimum Data Rate field (3 Octets) can set the required minimum data transmission rate. The Delay Bound field (3 Octets) can define the traffic delay limit (Delay Bound) (e.g., set if a delay limit of 20ms or less is required).

[0144] The QoS Characteristics element may further include at least one of the following as optional fields: Maximum MSDU Size field (0 or 2 Octets), Service Start Time field (0 or 4 Octets), Service Start Time Link ID field (0 or 1 Octet), Mean Data Rate field (0 or 3 Octets), Delay Bounded Burst Size field (0 or 4 Octets), MSDU Lifetime field (0 or 2 Octets), MSDU Delivery Info field (0 or 1 Octet), and Medium Time field (0 or 2 Octets).

[0145] The Maximum MSDU Size field (0 or 2 Octets) indicates the maximum MSDU (MAC Service Data Unit) size, the Service Start Time field (0 or 4 Octets) indicates the service start time, the Service Start Time Link ID field (0 or 1 Octet) indicates the link identifier (Link ID) to be distinguishable in a multi-link environment, and the Mean Data Rate field (0 or 3 Octets) indicates the average data transmission rate. The Delay Bounded Burst Size field (0 or 4 Octets) indicates the burst transmission size with guaranteed delay, and the MSDU Lifetime field (0 or 2 Octets) indicates the valid time (lifetime) of data transmission. The MSDU Delivery Info field (0 or 1 Octet) and the Medium Time field (0 or 2 Octets) can each indicate transmission information and medium usage time.

[0146] FIG. 7b shows an example of a control info field used to transmit information regarding the QoS characteristics of AC / UP / TID according to one embodiment of the present disclosure.

[0147] The control info field of FIG. 7b is included in the QoS Characteristics element of FIG. 7a. Referring to FIG. 7b, the control info field may include at least one of the following: a Direction (2 bits) subfield, a TID (4 bits) subfield, a User Priority (3 bits) subfield, a Presence Bitmap of Additional Parameters (16 bits) subfield, a LinkID (4 bits) subfield, and a Reserved (3 bits) subfield.

[0148] The Direction (2 bits) subfield can indicate the transmission direction (sending or receiving). The TID (4 bits) subfield is an identifier distinguishing traffic flows and can be associated with QoS priority or latency sensitivity. The User Priority (3 bits) subfield can distinguish QoS classes based on User Priority (UP). The Presence Bitmap of Additional Parameters (16 bits) subfield can indicate the presence of additional QoS parameters in a bitmap format. The LinkID (4 bits) subfield is an ID identifying a specific link and can be used for multi-link management.

[0149] According to one embodiment, the Reserved (3 bits) subfield may be used to indicate a negotiation state (Request, Suggest, Demand, Accept, Alternate, Reject) according to embodiments of the present disclosure.

[0150] According to one embodiment, AC (Access Category) may be implied in the User Priority (3 bits) subfield.

[0151] FIG. 8a shows an example of a QoS and AC / UP / TID Mapping element (QoS to AC / UP / TID Mapping element) according to one embodiment of the present disclosure.

[0152] AP can transmit (or exchange) QoS and AC / UP / TID Mapping elements through at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase. QoS and AC / UP / TID Mapping elements may be included in at least one frame used in at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase.

[0153] Referring to FIG. 8a, the QoS and AC / UP / TID Mapping element (QoS to AC / UP / TID Mapping element) may include at least one of an Element ID field (1 Octet), a Length field (1 Octet), an Element ID Extension field (1 Octet), and a QoS to AC / UP / TID Mapping field (Variable Octets). According to one embodiment, if only the QoS to AC / UP / TID Mapping field is included, it may be included in the form of a field that is not an Element.

[0154] The Element ID field (1 Octet) may indicate a unique ID that identifies the QoS and AC / UP / TID Mapping element. The Length field (1 Octet) may indicate the total length of the QoS and AC / UP / TID Mapping element. The Element ID Extension field (1 Octet) may support future extensions as an extension identifier.

[0155] The QoS to AC / UP / TID Mapping field (Variable Octets) may be included in multiple instances within a single QoS and AC / UP / TID Mapping element, and may indicate the mapping relationship between QoS requirements and AC / UP / TID. According to one embodiment, the QoS to AC / UP / TID Mapping field (Variable Octets) may provide flexibility and detailed configuration for the mapping between QoS requirements and AC / UP / TID.

[0156] FIG. 8b shows an example of a Presence Bitmap subfield used to indicate QoS metrics according to one embodiment of the present disclosure.

[0157] The AP may transmit (or exchange) a Presence Bitmap subfield used to indicate QoS metrics through at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase. The Presence Bitmap subfield used to indicate QoS metrics may be included in at least one frame used in at least one of the Discovery Phase, Agreement Establishment Phase, and Parameter Negotiation Phase.

[0158] Referring to FIG. 8b, the Presence Bitmap subfield used to indicate QoS metrics may include at least one of the Max. Service Interval Present subfield (1 Bit), Minimum Data Rate Present subfield (1 Bit), and Delay Bound Present subfield (1 Bit).

[0159] The Max. Service Interval Present subfield (1 bit) indicates whether a Maximum Service Interval exists, the Minimum Data Rate Present subfield (1 bit) indicates whether a Minimum Data Rate exists, and the Delay Bound Present subfield (1 bit) indicates whether a Delay Bound exists.

[0160] FIG. 8c shows an example of a QoS and AC / UP / TID Mapping field (QoS to AC / UP / TID Mapping) according to one embodiment of the present disclosure.

[0161] The QoS and AC / UP / TID Mapping fields of Fig. 8c (QoS to AC / UP / TID Mapping) are included in the QoS and AC / UP / TID Mapping elements of Fig. 8a (QoS to AC / UP / TID Mapping element).

[0162] Referring to FIG. 8c, the QoS and AC / UP / TID Mapping field (QoS to AC / UP / TID Mapping) may include at least one of a TID subfield (4 bits), an UP subfield (3 bits), a Mapping Setup Command subfield (3 bits), a Maximum Service Interval subfield (32 bits), a Minimum Data Rate subfield (24 bits), and a Delay Bound subfield (24 bits). According to one embodiment, the QoS and AC / UP / TID Mapping field (QoS to AC / UP / TID Mapping) may further include a Presence Bitmap subfield (3 bits) as shown in FIG. 8b.

[0163] The TID subfield (4 bits) indicates a unique ID that identifies traffic and can distinguish between QoS requirements and traffic flows. The UP subfield (3 bits) indicates user priority and can be mapped to EDCA traffic priority classes. The Mapping Setup Command subfield (3 bits) indicates a mapping setup command and can specify, for example, a mapping request, suggestion, demand, etc.

[0164] The Maximum Service Interval subfield (32 bits) specifies the maximum service interval and can define periodic service requirements. The Minimum Data Rate subfield (24 bits) specifies the minimum data transmission rate (e.g., bits per second) and can set the data rate for QoS requirements. The Delay Bound subfield (24 bits) specifies the maximum allowable delay time (e.g., milliseconds) and can set QoS requirements for supporting delay-sensitive traffic.

[0165] Meanwhile, if it is unclear to determine the QoS (Quality of Service) characteristics of each AC, UP, and TID, matching the Multi-User (MU) Enhanced Distributed Channel Access (EDCA) parameters can be effective. If the (MU) EDCA parameters between two APs match, AC traffic from each AP can acquire wireless media (WM) with the same probability as traffic from the other AP. This can guarantee the same Channel Access Probability, even if the QoS characteristics of the two APs differ.

[0166] <2-1 Example>

[0167] During Multi-AP Coordination, (MU) EDCA parameters may be advertised and / or negotiated among APs. According to one embodiment, during the Discovery Phase, each AP may advertise (MU) EDCA parameters. According to one embodiment, during the Agreement Establishment / Parameter Negotiation Phase, each AP may negotiate (MU) EDCA parameters.

[0168] <2-2 Example>

[0169] APs may attempt to match (MU) EDCA parameters. The negotiation process may be performed similarly to the process of mapping QoS to AC / UP / TID. According to one embodiment, the negotiation process for (MU) EDCA parameters may include at least one of Request, Suggest, Demand, Accept, Alternate, and Reject.

[0170] FIG. 9a illustrates an example of an EDCA parameter set element according to one embodiment of the present disclosure. Referring to FIG. 9a, the EDCA parameter set element may include at least one of an Element ID field (1 Octet), a Length field (1 Octet), a QoS Info field (1 Octet), an Update EDCA Info field (1 Octet), an AC_BE Parameter Record field (4 Octets), an AC_BK Parameter Record field (4 Octets), an AC_VI Parameter Record field (4 Octets), and an AC_VO Parameter Record field (4 Octets).

[0171] The Element ID field (1 Octet) indicates a unique identification ID of the EDCA parameter set element, and the Length field (1 Octet) may indicate the total length of the EDCA parameter set element. The QoS Info field (1 Octet) may include QoS information and negotiation status (request, offer, demand, acceptance, rejection, etc.). The Update EDCA Info field (1 Octet) indicates the update status of the EDCA information and may indicate whether a new parameter is set.

[0172] The AC_BE Parameter Record field (4 Octets) can set competition parameter information for Best Effort (AC_BE) traffic. The AC_BK Parameter Record field (4 Octets) can set competition parameter information for Background (AC_BK) traffic. The AC_VI Parameter Record field (4 Octets) can set competition parameter information for Video (AC_VI) traffic. The AC_VO Parameter Record field (4 Octets) can set competition parameter information for Voice (AC_VO) traffic.

[0173] According to one embodiment, in the Discovery Phase, the AP may advertise the current EDCA parameters in the QoS Info field so that the STA and / or other APs can verify them.

[0174] According to one embodiment, APs can negotiate parameters using QoS Info and Update EDCA Info during the Agreement Establishment Phase. According to one embodiment, settings for each traffic type (AC_BE, AC_BK, AC_VI, AC_VO) can be dynamically adjusted. According to one embodiment, the negotiation status can be classified into Request, Suggest, Demand, and Response (Accept, Alternate, Reject).

[0175] According to one embodiment, in the parameter negotiation phase, the AP can perform synchronization by utilizing Update EDCA Info when applying new parameters. QoS characteristics can be guaranteed through parameter synchronization between multiple APs.

[0176] FIG. 9b illustrates an example of a QoS information field transmitted by an AP according to one embodiment of the present disclosure. The QoS information field (QoS Info) of FIG. 9b is included in the EDCA parameter set element (EDCA parameter Set element) of FIG. 9a.

[0177] Referring to FIG. 9b, the QoS Info field may include at least one of the EDCA Parameter Set Update Count subfield (4 bits), Q-Ack (QoS Acknowledgment) subfield (1 bit), Queue Request subfield (1 bit), TXOP Request subfield (1 bit), and More Data Ack subfield (1 bit).

[0178] The EDCA Parameter Set Update Count subfield (4 bits) can indicate the number of updates to the EDCA parameter, which can be used for parameter change status and version management. The Q-Ack (QoS Acknowledgment) subfield (1 bit) can provide CF-Ack (Contention Free Ack) support information. The Queue Request subfield (1 bit) can indicate whether the Queue information of the QoS Control field is available. The TXOP Request subfield (1 bit) can indicate whether the TXOP Duration Request information of the QoS Control field is available. The More Data Ack subfield (1 bit) can indicate whether the Ack can include response information for additional data.

[0179] According to one embodiment, bits (e.g., 3 bits) set within the QoS Info field may be utilized for (MU) EDCA parameter negotiation. According to one embodiment, the More Data Ack subfield may be utilized for EDCA parameter negotiation. According to one embodiment, the negotiation process for (MU) EDCA parameters may include at least one of Request, Suggest, Demand, Accept, Alternate, and Reject.

[0180] FIG. 9c illustrates an example of an Update EDCA info field according to one embodiment of the present disclosure. The Update EDCA info field of FIG. 9c is included in the EDCA parameter Set element of FIG. 9a.

[0181] Referring to FIG. 9c, the Update EDCA info field may include at least one of an Override subfield (1 Bit), a PS-Poll ACI subfield (2 Bits), a RAW ACI subfield (2 Bits), an STA Type subfield (2 Bits), and a Reserved subfield (1 Bit).

[0182] The Override subfield (1 bit) specifies whether to override existing EDCA parameters. The PS-Poll ACI subfield (2 bits) allows setting the Access Category Identifier (ACI) to be applied during a transfer request (PS-Poll). The RAW ACI subfield (2 bits) allows setting the ACI to be used in the Resource Allocation Window (RAW). The STA Type subfield (2 bits) indicates the type of Station (STA) (e.g., classified as a standard STA, high-priority STA, cooperative STA, etc.).

[0183] According to one embodiment, the STA Type subfield (2 bits) and the Reserved subfield (1 bit) can be utilized for (MU) EDCA parameter negotiation. According to one embodiment, the negotiation process for (MU) EDCA parameters may include at least one of Request, Suggest, Demand, Accept, Alternate, and Reject.

[0184] <2-3rd Example>

[0185] APs may attempt to match MU EDCA parameters. MU EDCA parameter set elements may be used for MU EDCA parameter negotiation. According to one embodiment, the negotiation process for MU EDCA parameters may include at least one of a Request, Suggest, Demand, Accept, Alternate, and Reject.

[0186] FIG. 10a shows an example of a MU EDCA parameter set element according to one embodiment of the present disclosure.

[0187] Referring to FIG. 10a, the MU EDCA parameter set element may include at least one of the following: an Element ID field (1 Octet), a Length field (1 Octet), an Element ID Extension field (1 Octet), a QoS Info field (1 Octet), a MU AC_BE Parameter Record field (3 Octets), a MU AC_BK Parameter Record field (3 Octets), a MU AC_VI Parameter Record field (3 Octets), and a MU AC_VO Parameter Record field (3 Octets).

[0188] The Element ID field (1 Octet) indicates a unique identification ID of the EDCA parameter set element, and the Length field (1 Octet) may indicate the total length of the EDCA parameter set element. The Element ID Extension field (1 Octet) may support future extensions as an extension identifier. The QoS Info field (1 Octet) may include QoS information and negotiation status (request, offer, demand, acceptance, rejection, etc.). The MU AC_BE Parameter Record field (3 Octets) may set competition parameter information for Best Effort (AC_BE) traffic. The MU AC_BK Parameter Record field (3 Octets) may set competition parameter information for Background (AC_BK) traffic. The MU AC_VI Parameter Record field (3 Octets) may set competition parameter information for Video (AC_VI) traffic. The MU AC_VO Parameter Record field (3 Octets) can set competition parameter information for Voice (AC_VO) traffic.

[0189] FIG. 10b illustrates an example of a QoS information field transmitted by an AP according to one embodiment of the present disclosure. The QoS information field (QoS Info) of FIG. 10b is included in the MU EDCA parameter set element (MU EDCA parameter Set element) of FIG. 10a.

[0190] Referring to FIG. 10b, the QoS Info field may include at least one of the EDCA Parameter Set Update Count subfield (4 bits), Q-Ack (QoS Acknowledgment) subfield (1 bit), Queue Request subfield (1 bit), TXOP Request subfield (1 bit), and More Data Ack subfield (1 bit).

[0191] The EDCA Parameter Set Update Count subfield (4 bits) can indicate the number of updates to the EDCA parameter, which can be used for parameter change status and version management. The Q-Ack (QoS Acknowledgment) subfield (1 bit) can provide CF-Ack (Contention Free Ack) support information. The Queue Request subfield (1 bit) can indicate whether the Queue information of the QoS Control field is available. The TXOP Request subfield (1 bit) can indicate whether the TXOP Duration Request information of the QoS Control field is available. The More Data Ack subfield (1 bit) can indicate whether the Ack can include response information for additional data.

[0192] According to one embodiment, bits (e.g., 3 bits) set within the QoS Info field may be utilized for (MU) EDCA parameter negotiation. According to one embodiment, the More Data Ack subfield may be utilized for EDCA parameter negotiation. According to one embodiment, the negotiation process for (MU) EDCA parameters may include at least one of Request, Suggest, Demand, Accept, Alternate, and Reject.

[0193] FIG. 11 is a drawing showing an example of a configuration of a first AP according to one embodiment of the present disclosure.

[0194] The first AP of FIG. 11 can be implemented as any one of the electronic device (101) of FIG. 1, the access point (210) of FIG. 2, the Sharing AP (310) of FIG. 3, the TXOP Owner AP (410) of FIG. 4, the Sharing AP of FIG. 5a, or the Requesting AP.

[0195] In FIG. 11, the first AP may include a processor (1101), a transceiver (1102), and a memory (1103). The processor (1101), transceiver (1102), and memory (1103) of the first AP may operate according to the method(s) described in the aforementioned embodiments of FIG. 1 to FIG. 10b. However, the components of the first AP are not limited to the aforementioned examples. For example, the first AP may include more components or fewer components than the aforementioned components. Furthermore, the processor (1101), transceiver (1102), and memory (1103) may be implemented in the form of at least one chip.

[0196] The transceiver (1102) 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 (1102). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1102) 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 (1102), and the components of the transceiver (1102) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1102) may receive a signal and output it to a processor (1101), and transmit the signal output from the processor (1101) to a station (STA) or another AP.

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

[0198] The processor (1101) can control a series of processes so that the first AP can operate according to at least one of the embodiments of FIGS. 1 to 10b. The processor (1101) may include at least one processor.

[0199] According to one embodiment, the processor (1101) may control the transmission of a first frame to a second AP containing quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID). According to one embodiment, the processor (1101) may receive a second frame from the second AP in response to the QoS information of the first AP. According to one embodiment, the processor (1101) may perform a Multi-AP operation with the second AP based on the second frame in response to the QoS information of the first AP.

[0200] According to one embodiment, the Multi-AP operation may be such that 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), Co-SR (coordinated spatial reuse), and Co-RTWT (coordinated restricted target wake time).

[0201] According to one embodiment, the processor (1101) can control the transmission of the first frame to the second AP in the discovery phase for the Multi-AP operation, the first frame including at least one of the QoS information of the first AP, the EDCA parameter information, and the capability information of the first AP for the Multi-AP operation.

[0202] According to one embodiment, the processor (1101) can control the transmission of the first frame to the second AP in the agreement establishment phase or parameter negotiation phase for the Multi-AP operation, the first frame including at least one of the QoS information of the first AP, the EDCA parameter information, and the parameters for the Multi-AP operation.

[0203] According to one embodiment, the QoS information of the first AP may be a representative value of existing streams; or requirements for AC / UP / TID for at least one of the AC, the UP, or the TID.

[0204] According to one embodiment, the QoS information of the first AP or the EDCA parameter information may include information regarding mapping between at least one of the AC, the UP, or the TID and the QoS. The type of information regarding mapping may be set as a request to transmit the QoS information of the first AP or the EDCA parameter information as a reference; a suggestion requesting to compromise the QoS information of the first AP or the EDCA parameter information and change the QoS information of the second AP or the EDCA parameter information of the second AP; or a demand requesting to change the QoS information of the second AP or the EDCA parameter information of the second AP without changing the QoS information of the first AP or the EDCA parameter information.

[0205] According to one embodiment, the second frame may include QoS information of the second AP or EDCA parameter information of the second AP in response to the request among the types of information regarding the mapping of the first AP, or include information accepting the proposal or the request in response to the proposal or the request among the types of information regarding the mapping of the first AP, or include information rejecting the proposal or the request in response to the proposal or the request among the types of information regarding the mapping of the first AP, or include alternative mapping information in response to the proposal or the request among the types of information regarding the mapping of the first AP.

[0206] According to one embodiment, the at least EDCA parameter information may include at least one of the competition parameter information of BE (best effort) traffic (AC_BE), the competition parameter information of background traffic (AC_BK), the competition parameter information of video traffic (AC_VI), and the competition parameter information of voice traffic (AC_VO).

[0207] FIG. 12 is a drawing showing an example of a configuration of a second AP according to one embodiment of the present disclosure.

[0208] The second AP of FIG. 12 can be implemented as any one of the electronic device (101) of FIG. 1, the access point (210) of FIG. 2, the Shared AP (310) of FIG. 3, the Candidate AP (410) of FIG. 4, the Candidate AP of FIG. 5a, or the Responding AP.

[0209] In FIG. 12, the second AP may include a processor (1201), a transceiver (1202), and a memory (1203). The processor (1201), transceiver (1202), and memory (1203) of the second AP may operate according to the method(s) described in the aforementioned embodiments of FIG. 1 to FIG. 10b. However, the components of the second AP are not limited to the aforementioned examples. For example, the second AP may include more components or fewer components than the aforementioned components. Furthermore, the processor (1201), transceiver (1202), and memory (1203) may be implemented in the form of at least one chip.

[0210] The transceiver (1202) 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 (1202). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1202) 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 (1202), and the components of the transceiver (1202) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1202) may receive a signal and output it to a processor (1201), and transmit the signal output from the processor (1201) to a station (STA) or another AP.

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

[0212] The processor (1201) can control a series of processes so that the second AP can operate according to at least one of the embodiments of FIGS. 1 to 10b. The processor (1201) may include at least one processor.

[0213] According to one embodiment, a processor (1201) may receive from the first AP a first frame containing quality of service (QoS) information or enhanced distributed channel access (EDCA) parameter information of the first AP for at least one of access category (AC), user priority (UP), or traffic identifier (TID). According to one embodiment, the processor (1201) may transmit a second frame to the first AP in response to the QoS information of the first AP. According to one embodiment, the processor (1201) may perform a Multi-AP operation with the first AP based on the second frame in response to the QoS information of the first AP.

[0214] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is 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 form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0215] 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, comprising the step of transmitting a first frame to a second AP, the first frame including QoS (quality of service) information or EDCA (enhanced distributed channel access) parameter information of the first AP regarding at least one of AC (access category), UP (user priority), or TID (traffic identifier); A step of receiving a second frame from the second AP that responds to the QoS information of the first AP; and A method comprising the step of performing a Multi-AP operation with the second AP based on the second frame responding to the QoS information of the first AP.

2. In paragraph 1, the Multi-AP operation is, A method in which 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), Co-SR (coordinated spatial reuse), Co-OFDMA / TDMA (coordinated OFDMA / TDMA), JT / JR (joint transmission / reception), and Co-RTWT (coordinated restricted target wake time).

3. In paragraph 1, the step of transmitting the first frame is, A method comprising the step of transmitting the first frame to the second AP in the discovery phase for the Multi-AP operation, the first frame comprising at least one of the QoS information of the first AP, the EDCA parameter information, and the capability information of the first AP for the Multi-AP operation.

4. In paragraph 1, the step of transmitting the first frame is, A method comprising the step of transmitting the first frame to the second AP, wherein the first frame includes at least one of the QoS information of the first AP, the EDCA parameter information, and the parameters for the Multi-AP operation, in the agreement establishment phase or parameter negotiation phase for the Multi-AP operation.

5. In paragraph 3, the QoS information of the first AP is, Representative value of existing streams; or A method that is a requirement for at least one of the above AC, the above UP, or the above TID.

6. In paragraph 4, the QoS information of the first AP or the EDCA parameter information includes information regarding the mapping between QoS and at least one of the AC, the UP, or the TID, and The type of information regarding the above mapping is, A request to transmit the QoS information of the first AP or the EDCA parameter information as a reference; A suggestion requesting to compromise the QoS information of the first AP or the EDCA parameter information, and to change the QoS information of the second AP or the EDCA parameter information of the second AP; or A method configured as a demand to change the QoS information of the second AP or the EDCA parameter information of the second AP without changing the QoS information of the first AP or the EDCA parameter information.

7. In paragraph 6, the second frame is, Among the types of information regarding the mapping of the first AP, in response to the request, including QoS information of the second AP or EDCA parameter information of the second AP, Among the types of information regarding the mapping of the first AP, the information includes information that accepts the proposal or the request in response to the proposal or the request, or Among the types of information regarding the mapping of the first AP, the information includes information rejecting the proposal or the request in response to the proposal or the request, or A method comprising alternative mapping information in response to the proposal or request among the types of information regarding the mapping of the first AP.

8. In Paragraph 1, A method comprising at least one of the above EDCA parameter information, which includes competition parameter information of BE (best effort) traffic (AC_BE), competition parameter information of background traffic (AC_BK), competition parameter information of video traffic (AC_VI), and competition parameter information of voice traffic (AC_VO).

9. A method of a second AP (access point) performing Wi-Fi communication, A step of receiving a first frame from the first AP containing QoS (quality of service) information or EDCA (enhanced distributed channel access) parameter information of the first AP for at least one of AC (access category), UP (user priority), or TID (traffic identifier); A step of transmitting a second frame to the first AP in response to the QoS information of the first AP; and A method comprising the step of performing a Multi-AP operation with the first AP based on the second frame responding to the QoS information of the first AP.

10. In Clause 9, the Multi-AP operation is, A method in which 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), Co-SR (coordinated spatial reuse), Co-OFDMA / TDMA (coordinated OFDMA / TDMA), JT / JR (joint transmission / reception), and Co-RTWT (coordinated restricted target wake time).

11. In paragraph 9, the step of receiving the first frame is, A method comprising the step of receiving from the first AP a first frame comprising at least one of QoS information of the first AP, EDCA parameter information, and capability information of the first AP for the Multi-AP operation in the discovery phase for the Multi-AP operation.

12. In paragraph 9, the step of receiving the first frame is, A method comprising the step of receiving from the first AP a first frame comprising at least one of the QoS information of the first AP, the EDCA parameter information, and the parameters for the Multi-AP operation in an agreement establishment phase or a parameter negotiation phase for the Multi-AP operation.

13. In Clause 11, the QoS information of the first AP above is, Representative value of existing streams; or A method that is a requirement for at least one of the above AC, the above UP, or the above TID.

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 to transmit to the second AP a first frame containing QoS (quality of service) information or EDCA (enhanced distributed channel access) parameter information of the first AP for at least one of AC (access category), UP (user priority), or TID (traffic identifier), and A second frame responding to the QoS information of the first AP is received from the second AP, and A first AP that performs a Multi-AP operation with the second AP based on the second frame responding to the QoS information of the first AP.

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 frame from the first AP that includes QoS (quality of service) information or EDCA (enhanced distributed channel access) parameter information of the first AP for at least one of AC (access category), UP (user priority), or TID (traffic identifier), and Control to transmit a second frame to the first AP in response to the QoS information of the first AP, and A second AP that performs a Multi-AP operation with the first AP based on the second frame responding to the QoS information of the first AP.

Images