Method and device for sharing transmission opportunity in wi-fi communication system

Abstract

The present disclosure proposes a method and device for an access point (AP) to share a transmission opportunity (TXOP) with another access point or station during Wi-Fi communication. The method performed by a first access point in a wireless local access network (WLAN) system according to an embodiment of the present disclosure, comprises the steps of: receiving, from a second access point, a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point; determining whether to receive the shared TXOP on the basis of the first control frame; and when it is determined not to receive the shared TXOP, determining not to transmit a response frame to the second access point.

Description

Method and device for sharing transmission opportunities in a Wi-Fi communication system

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

[0002] Recently, with the advancement of wireless technology, wired networks, which are widely used by many people, are being replaced by wireless networks. In other words, since 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, 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. WiFi communication primarily uses the 2.4 GHz and 5 GHz radio bands. In particular, with the popularization of mobile devices, wireless LANs, which have potential as open wireless networks, are rapidly expanding, and WiFi is being used to provide high-speed data services to entire cities, including schools, airports, hotels, and offices.

[0004] The Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being researched.

[0005] In an IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects, creating new value in human life. IoT, through the convergence and integration of existing IT (information technology) technologies with various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0006] The present disclosure proposes a method and device for an access point to share a transmission opportunity (TXOP) with another access point or station during Wi-Fi communication.

[0007] The present disclosure proposes a method and device that, when an access point shares a TXOP with another access point or station during Wi-Fi communication, allows the TXOP to be shared only when a certain condition for sharing the TXOP with the access point or station to be shared is satisfied.

[0008] According to one embodiment of the present disclosure, a method performed by a first access point (AP) in a wireless local access network (WLAN) system includes: receiving, from a second access point, a first control frame related to sharing a transmission opportunity (TXOP) acquired by the second access point; determining, based on the first control frame, whether to share the TXOP; and determining, if it is determined not to share the TXOP, not to transmit the response frame to the second access point.

[0009] According to one embodiment of the present disclosure, a method of a second access point (AP) in a wireless local access network (WLAN) system includes the steps of: transmitting a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point to at least one first access point; and identifying whether a response frame has been received from the at least one first access point; and, if the response frame has not been received from the at least one first access point, determining whether to share the TXOP with a third access point excluding the at least one first access point.

[0010] According to one embodiment of the present disclosure, in a wireless local area network (WLAN) system, a first access point (AP) includes a transceiver; one or more processors including processing circuitry; and a memory storing instructions, which, when individually or collectively executed by the one or more processors, cause the first access point to: receive, from a second access point, a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point; determine, based on the first control frame, whether to share the TXOP; and, if it is determined not to share the TXOP, determine not to transmit the response frame to the second access point.

[0011] In accordance with one embodiment of the present disclosure, in a wireless local area network (WLAN) system, a second access point (AP) includes a transceiver; one or more processors including processing circuitry; and a memory storing instructions, which, when individually or collectively executed by the one or more processors, cause the second access point to: transmit, to at least one first access point, a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point; identify whether a response frame has been received from the at least one first access point; and, if the response frame has not been received from the at least one first access point, determine whether to share the TXOP with a third access point excluding the at least one first access point.

[0012] According to one embodiment of the present disclosure, an access point (AP) can transfer a transmission opportunity to another access point or station when necessary, as well as to the access point that created the transmission opportunity during Wi-Fi communication, thereby improving data transmission performance.

[0013] According to one embodiment of the present disclosure, an access point can improve the efficiency of data transmission in a Wi-Fi communication system by sharing a TXOP only when certain conditions for sharing the TXOP are satisfied with the access point or station to be shared.

[0014] Figure 1 is a block diagram of an electronic device within a network environment.

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

[0016] FIG. 2b is a diagram for explaining the operation of an access point (AP) and a station (STA) for establishing a Wi-Fi connection according to one embodiment of the present disclosure.

[0017] FIG. 3 is a diagram illustrating an operation when DL traffic arrives during a DL (downlink) TXOP (transmit opportunity) according to one embodiment of the present disclosure.

[0018] FIG. 4 illustrates a wireless communication system including multiple access points and stations according to one embodiment of the present disclosure.

[0019] FIGS. 5A and 5B are diagrams illustrating examples of operation of a multi-access point according to one embodiment of the present disclosure.

[0020] FIG. 6 is a diagram illustrating an operation of sharing TXOP between access points according to one embodiment of the present disclosure.

[0021] FIG. 7 is a diagram illustrating a downlink operation between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0022] FIG. 8 is a diagram illustrating an uplink operation between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram illustrating a random access operation in uplink transmission between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0024] FIG. 10 is a diagram illustrating a case in which a collision occurs in a random access operation in an uplink transmission between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0025] FIG. 11 is a diagram illustrating an operation in which a shared AP rejects sharing of a TXOP using a predetermined control frame when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0026] FIG. 12 is a diagram illustrating an operation in which a shared AP rejects sharing of a TXOP by not transmitting a response frame when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating an operation in which a station refuses to share a TXOP when sharing a TXOP between an access point and a station according to one embodiment of the present disclosure.

[0028] FIGS. 14a, 14b, 14c, 14d, and 14e are diagrams illustrating examples of field and information element formats of a TXS trigger frame used by an access point when sharing the TXOP according to one embodiment of the present disclosure.

[0029] FIG. 15 is a flowchart illustrating the operation of a first access point according to one embodiment of the present disclosure.

[0030] FIG. 16 is a flowchart illustrating the operation of a second access point according to one embodiment of the present disclosure.

[0031] FIG. 17 is a diagram showing an example configuration of a station according to one embodiment of the present disclosure.

[0032] FIG. 18 is a diagram showing an example configuration of an access point 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, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0035] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0036] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments of the present disclosure are provided only 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. Like reference numerals refer to like elements throughout the specification.

[0037] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s).

[0038] Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, so that the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also be able to provide steps for performing the functions described in the flowchart block(s).

[0039] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0040] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, according to some embodiments, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate 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 term 'electronic device', 'terminal' or 'device' used herein may refer to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (UE), subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. Additionally, the terminal may include, but is not limited to, an M2M (Machine to Machine) terminal or an MTC (Machine Type Communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.

[0042] The exemplary embodiments are described below for simplicity only with respect to Wireless Local Area Network (WLAN) systems. It should be understood that the exemplary embodiments are equally applicable to other wireless networks (e.g., cellular networks, pico-networks, femto-networks, satellite networks), as well as systems that utilize signals of one or more wired standards or protocols (e.g., Ethernet and / or HomePlug / PLC standards). As used herein, the terms "WLAN" and "Wi-Fi®" may include communications governed by the IEEE 802.11 family of standards, BLUETOOTH®, HiperLAN (a set of wireless standards primarily used in Europe and comparable to the IEEE 802.11 standards), and other technologies having a relatively short radio propagation range. Accordingly, the terms "WLAN" and "WiFi" may be used interchangeably herein. Additionally, while the following is described with respect to an infrastructure WLAN system including one or more Access Points (APs) and multiple Stations (STAs), the exemplary embodiments are equally applicable to other WLAN systems including, for example, multiple WLANs, peer-to-peer (or independent basic service set) systems, Wi-Fi Direct systems, and / or hotspots.

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

[0044] In the following description, numerous specific details are set forth, such as examples of specific components, circuits, and processes, to provide a thorough understanding of the present disclosure. The term "connected," as used herein, means directly connected or connected via one or more intervening components or circuits. The term "connected access point" refers to an access point with which a given station is currently associated and / or connected (e.g., there is an established communications channel or link between the access point and the given station). Furthermore, in the following description and for purposes of explanation, specific nomenclature is set forth to provide a thorough understanding of the exemplary embodiments. However, it will be apparent to one skilled in the art that such specific details may not be necessary to practice the exemplary embodiments. In other instances, well-known circuits and devices are shown in block diagram form to avoid obscuring the present disclosure.

[0045] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0046] Certain terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0047] "PCF (point coordination function) transmission" refers to a transmission method in which the access point directly asks multiple wireless stations and waits for data transmission.

[0048] "DCF (distributed coordination function) transmission" refers to a transmission method in which a wireless station detects and waits in advance to avoid collisions before transmitting data in an environment where multiple wireless stations compete to transmit data.

[0049] The above DCF transmission method is a concept for providing services in a contention period, and can handle waiting time by dividing traffic priorities into IFSs (inter-frame spaces) to request channel use. In other words, priority can be determined by the size of the waiting time, and the shorter the waiting time, the higher the priority packet. The IFS can include SIFS (short IFS), PIFS (PCF IFS), and DIFS (DCF IFS).

[0050] The SIFS has the shortest period and has a high priority, and can be used primarily as a waiting time for control information. The PIFS has a medium-length period and has a medium priority. The DIFS has a low priority and can be used primarily as a waiting time for channel checks. That is, during the DIFS period, the channel can be listened for (or waited for) to be available. If the channel is busy during the DIFS period, transmission can be delayed.

[0051] A "TXOP (transmission opportunity)" can refer to a time interval during which a specific AP or station has the right to initiate a frame exchange sequence over the wireless medium. The AP or station that acquires the TXOP is called the TXOP holder, and the other party is called the TXOP responder. TXOPs are typically acquired through contention, and the typical procedure for protecting them is the RTS (request to send) / CTS (clear to send) exchange.

[0052] FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) applicable to the present disclosure. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with an electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with an electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). In one embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).

[0053] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (121). For example, when the electronic device (101) includes the main processor (121) and the auxiliary processor (123), the auxiliary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a given function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0054] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, in the electronic device (101) itself where artificial intelligence is performed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0055] The memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto. The memory (130) can include volatile memory (132) or non-volatile memory (134).

[0056] The program (140) may be stored as software in the memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0057] The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0058] The audio output module (155) can output audio signals to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0059] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0060] The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).

[0061] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0062] The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). In one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0063] The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0064] The haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0065] The camera module (180) can capture still images and videos. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0066] The power management module (188) can manage the power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0067] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0068] The communication module (190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi), or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).When the electronic device communicates with an access point (AP) using short-range wireless LAN communication among the first network (198), the electronic device may be referred to as a station (STA).

[0069] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (192) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC realization.

[0070] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), may be selected from the plurality of antennas, for example, by the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).

[0071] According to various embodiments, the antenna module (197) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

[0072] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0073] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

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

[0075] Referring to FIG. 2A, an electronic device (101) (e.g., the electronic device (101) of FIG. 1) may be connected to an AP (200) based on Wi-Fi communication. The electronic device (101) may include a processor (120) (e.g., the processor (120) of FIG. 1) and a communication module (190) (e.g., the communication module (190) of FIG. 1). The electronic device (101) may be referred to as a station (STA) in a communication system based on Wi-Fi communication.

[0076] According to one embodiment, the communication module (190) may 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) may 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 may support a wider bandwidth, higher data throughput, and shorter delay time compared to IEEE 802.11ax.

[0077] 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 a memory.

[0078] According to one embodiment, the transceiver (191) may convert a baseband transmit signal into a wireless signal or convert a received wireless signal into a baseband receive signal.

[0079] 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), for example, a modulator, a digital-analog converter (D / A converter), a frequency converter, an A / D converter, an amplifier, and / or a demodulator.

[0080] Although not shown, according to various embodiments, the electronic device (101) may be electrically connected to the communication module of the AP (200) and may include at least one antenna module (e.g., the antenna module (197) of FIG. 1) that supports a communication protocol and / or frequency band supported by the communication module of the access point (200).

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

[0082] A wireless local area network (WLAN) system that complies with the IEEE 802.11n standard is called a High Throughput (HT) system, and a system that complies with the IEEE 802.11ac standard is called a Very High Throughput (VHT) system. In comparison, a WLAN system that supports orthogonal frequency division multiple access (OFDMA) is called a High Efficiency WLAN (HEW) system or a High Efficiency (HE) system. The terms HEW or HE are only used to distinguish them from conventional WLANs and are not used to limit the technical scope.

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

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

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

[0086] In one embodiment, the AP (200) may be a wireless router. The access point (200) may be a dedicated wireless router or a general-purpose device supporting mobile hotspot functionality, and there are no limitations on its implementation. For example, the AP (200) may include the same components as the electronic device (101), such as a processor (e.g., the processor (120) of FIG. 1 ) and / or a communication module (e.g., the communication module (190) of FIG. 1 ).

[0087] According to one embodiment, the AP (200) can transmit and receive data with an external device, such as a server (e.g., server (108) of FIG. 1) 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).

[0088] FIG. 2b 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.

[0089] Referring to FIG. 2B, an access point (210) may be implemented as the access point (200) of FIG. 2A and may communicate with a station (220) based on Wi-Fi. The station (220) may be implemented as the electronic device (101) of FIG. 1 or the electronic device (101) of FIG. 2A. 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.

[0090] 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 surrounding 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 information included in the beacon message. The access point (210) may transmit a probe response message (probe response) in response to the probe request message (S202).

[0091] Upon receiving the probe response message, the station (220) may transmit an authentication request message to the access point (210) (S203). The access point (210) may transmit 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. In one embodiment, the authentication procedures of S203 and S204 may be a procedure for selecting and authenticating a channel with the strongest reception strength among messages received during a channel search process. In one embodiment, through the authentication procedures of S203 and S204, the station (220) and the access point (210) may negotiate an encryption method of the authentication procedure.

[0092] Once the authentication procedure is completed, the station (220) may transmit an association request message to the access point (210) to establish a connection to the access point (210) (S205). According to one embodiment, the association request message may include information regarding at least one capability (e.g., according to the IEEE 802.11 standard) to be used for data communication between the station (220) and the access point (210). The access point (210) may generate an association ID (AID) for the station (220) and transmit an association response message to the station (220) (S206).

[0093] FIG. 3 is a diagram illustrating an operation when UL (uplink) traffic arrives at an STA during a DL (downlink) TXOP (transmit opportunity) according to one embodiment of the present disclosure.

[0094] In FIG. 3, the operation between AP (300) and STA (310) is illustrated, and STA (310) may include an associated STA included in the BSS (basic service set) of AP (300) as described above.

[0095] Referring to FIG. 3, even if a new UL packet arrives (370) from a station (310) while the AP (300) acquires and initiates a TXOP (330) and is transmitting a long DL PPDU (320), the station (310) may wait for transmission of the new UL packet until the transmission of the long DL PPDU (320) is completed during the TXOP (330) period (345). The station (310) may transmit an ACK frame (350) for the long DL PPDU (320). After the TXOP (330) ends, the station (310) may participate in the competition, acquire and initiate a TXOP (370) for transmitting a UL PPDU (360), and transmit the UL PPDU (360) corresponding to the packet that was being waited for. AP (300) can transmit an ACK frame (380) for the UL PPDU (360).

[0096] FIG. 4 illustrates a wireless communication system including multiple access points and stations according to one embodiment of the present disclosure.

[0097] Referring to FIG. 4, a wireless communication system (400) includes a first AP (400), a second AP (410), and a third AP (420), and may include STA 1-1 (405), STA 1-2 (407) connected to the first AP (400), STA 2-1 (415), STA 2-2 (417) connected to the second AP (410), and STA 3 (425) connected to the third AP (420). In FIG. 4, the first AP (400), the second AP (410), and the third AP (420) may each form a wireless local area network (WLAN) (403, 413, 423). The circular shape of the WLAN (403, 413, 423) illustrated in FIG. 4 can also be understood as representing a coverage area in which STAs included in the corresponding infrastructure basic service set (BSS) of each AP maintain communication.

[0098] The first AP (400), the second AP (410), and the third AP (420) are assigned unique media access control (MAC) addresses. The WLANs (403, 413, 423) depicted in a circular shape in FIG. 4 are depicted as an infrastructure BSS, which is a basic building block in an IEEE 802.11 system. However, in other exemplary embodiments, the WLANs (403, 413, 423) may include an independent basic service set (IBSS) network. This area may be referred to as a basic service area (BSA). When an STA moves outside of the BSA, it cannot directly communicate with other STAs within the BSA.

[0099] STAs (405, 407, 415, 417, 425) are devices that operate according to the Medium Access Control (MAC) / PHY specifications of IEEE 802.11. As long as the function of an STA is not individually distinguished from an AP, an STA may include an AP STA and a non-AP STA. However, when communication is performed between an STA and an AP, an STA may be understood as a non-AP STA. The STAs (405, 407, 415, 417, 425) may be any suitable Wi-Fi-enabled wireless device or electronic device, including, for example, a cell phone, a personal digital assistant (PDA), a tablet device, a laptop computer, etc. The stations (405, 407, 415, 417, 425) may also be referred to as user equipment (UE), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, electronic device, or any other suitable terminology.

[0100] In FIG. 4, the second AP (410) and the third AP (420) may have overlapping basic service sets (overlapping BSS, OBSS) with the first AP (400), in which case the second AP (410) and the third AP (420) may be referred to as OBSS APs. In this case, the second AP (410) and the third AP (OBSS AP) (420) may overhear a signal transmitted (e.g., broadcast) by the first AP (400).

[0101] In one embodiment, the first AP (400) may operate as a sharing AP that shares TXOP with another AP or STA, and the second AP (410) may operate as a shared AP that shares TXOP from the first AP (400).

[0102] FIGS. 5A and 5B are diagrams illustrating examples of operation of a multi-access point according to one embodiment of the present disclosure.

[0103] Referring to FIGS. 5a and 5b, the first AP (500) and the second AP (510) are APs included in a wireless communication system including multiple access points and stations, and can transmit using coordinated beamforming (C-BF).

[0104] The first AP (500) and the second AP (510) illustrated in FIGS. 5A and 5B may operate as a sharing AP and a shared AP, similar to the first AP (400) and the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The first AP (500) and the second AP (510) may form BSS1 and BSS2, respectively, and the STA connected to the first AP (500) may be referred to as the first STA, and the STA connected to the second AP (510) may be referred to as the second STA. Additionally, the second AP (510) may have an overlapping basic service set (overlapping BSS, OBSS) with the first AP (500), in which case the second AP (510) may be referred to as an OBSS AP for the first AP (500), and the second STA connected to the second AP (510) may be referred to as an OBSS STA for the first AP (500).

[0105] Referring to FIG. 5A, the first AP (500) can transmit a MAC control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (520) to the second AP (510) to trigger transmission using C-BF, and initiate a TXOP (530) acquired by the first AP (500). The MAC control frame (520) can include at least one piece of information from among a shared AP ID, an OBSS STA2'S ID, an In-BSS STA'1 ID, and a C-BF PPDU length.

[0106] The second AP (510) can transmit a CTS (clear to send) frame (525) to the first AP (500). In this case, the first AP (500) can transmit a DL PPDU (540) of C-BF PPDU length to the first STA after SIFS after the CTS frame (525) is transmitted. The second AP (510) can transmit a PPDU (545) of C-BF PPDU length to the second STA in the TXOP (530) acquired by the first AP (500). Thereafter, the first AP (500) can receive an acknowledgment frame (e.g., Ack, or BA (block Ack) frame, etc.) (547).

[0107] FIG. 5b is an operation for a case where the MAC control frame that triggers transmission using C-BF transmitted by the first AP (500) does not include a shared AP ID, unlike that illustrated in FIG. 5a above.

[0108] Referring to FIG. 5b, the first AP (500) can transmit a MAC control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (570) to the second AP (510) to trigger transmission using C-BF. The MAC control frame (520) can include at least one piece of information from among OBSS STA2'S ID, In-BSS STA'1 ID, and C-BF PPDU length.

[0109] The second AP (510) does not transmit a CTS (clear to send) frame because the shared AP ID is not indicated in the MAC control frame transmitted by the first AP (500). However, since it operates on the same channel, after listening to the MAC control frame, if it determines that transmission to an STA connected to the second AP (510) is advantageous, it may perform PPDU transmission using C-BF. That is, after the MAC control frame (570) is transmitted, the first AP (500) may transmit a DL PPDU (580) having a C-BF PPDU length to the first STA. The second AP (510) may transmit a PPDU (585) having a C-BF PPDU length to the second STA. Thereafter, the first AP (500) may receive an acknowledgment frame (e.g., an Ack, or a BA (block Ack) frame, etc.) (547). Thereafter, the second AP (510) may transmit a BAR (block Ack request) frame (590) requesting an acknowledgment frame (e.g., a BA (block Ack) frame, etc.) to the second STA. Thereafter, the second AP (510) may receive a BA frame (595) from the second STA.

[0110] FIG. 6 is a diagram illustrating an operation of sharing TXOP between access points according to one embodiment of the present disclosure.

[0111] The sharing AP (600), the shared AP (610) illustrated in FIG. 6 may correspond to the first AP (400) and the second AP (410) included in the wireless communication system including the multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (600) may share TXOP with APs with overlapping BSSs. The first STA (605) may refer to an STA connected to the sharing AP (600), and the second STA (615) may refer to an STA connected to the shared AP (610).

[0112] Referring to FIG. 6, the sharing AP (600) can initiate a TXOP (630) acquired by the sharing AP (600) and transmit a control frame (e.g., a MU-RTS TXS (triggered TXOP sharing) trigger frame) (640) for sharing the TXOP to the shared AP (610). By the control frame (640) for sharing the TXOP, a part of the time interval (645) of the TXOP (630) can be shared with the shared AP (610).

[0113] The shared AP (610) can transmit a response frame (e.g., a CTS frame) (650) to the control frame (640) for sharing the TXOP with the shared AP (600). The shared AP (610) can transmit data (660) to the second STA (615) in the time interval (630) shared from the shared AP (600). The second STA (615) can transmit a BA frame (645) to the shared AP (610). In one embodiment, when the BA frame (665) of the second STA (615) transmitted by the shared AP (610) is transmitted, the sharing AP (600) can resume the frame exchange procedure with the first STA (670).

[0114] In environments with a high concentration of APs and STAs, performance degradation due to competition can occur. Therefore, the TXOP sharing described above can prevent excessive competition by allowing APs to share TXOPs with neighboring APs after long periods of occupancy, thereby improving spectrum efficiency in dense environments.

[0115] The present disclosure can determine and specify conditions for a shared AP to share (transfer) a TXOP for efficient use of a medium by an AP (sharing AP) that occupies a TXOP for TXOP sharing. In one embodiment, the sharing AP can indicate the sharing conditions in a TXOP sharing trigger frame. Accordingly, only APs that satisfy the conditions for sharing the TXOP can share (transfer) the TXOP.

[0116] For example, the conditions for sharing the above TXOP may include at least one of the conditions below.

[0117] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0118] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0119] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0120] In one embodiment, an AP occupying a TXOP (sharing AP) may determine whether uplink OFDMA-based random access (UORA) can be used, which may result in inefficient use of the medium. In one embodiment, the sharing AP may indicate whether the UORA can be used in a TXOP sharing trigger frame.

[0121] In one embodiment, a shared AP that receives a TXOP sharing trigger frame from the shared AP may determine whether to share (transfer) the TXOP based on conditions for sharing the TXOP. In one embodiment, if the shared AP determines not to share (transfer) the TXOP, it may transmit a response frame for rejection or may not transmit a response frame.

[0122] FIG. 7 is a diagram illustrating a downlink operation between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0123] The sharing AP (700) illustrated in FIG. 7 can operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The shared AP (710) illustrated in FIG. 7 can operate as a shared AP, like the shared AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (700) can share a TXOP with the shared AP (710) whose BSS overlaps. The second STA (715) illustrated in FIG. 7 can include an STA associated with the shared AP (710).

[0124] Referring to FIG. 7, the sharing AP (700) can initiate a TXOP (730) acquired by the sharing AP (700) and transmit a DL PPDU (740) to the first STA connected to the sharing AP (700). After transmitting the DL PPDU (740), the sharing AP (700) can receive an ACK frame (or BA frame) (745) from the first STA after SIFS.

[0125] In one embodiment, the sharing AP (700) may transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (760) to the shared AP (710) to share the TXOP (750) of a certain time interval among the TXOPs (730). The sharing AP (700) may transmit the control frame (760) to the shared AP (710) after SIFS after receiving the ACK frame (or BA frame) (745).

[0126] In one embodiment, a control frame (e.g., a MU-RTS TXS (triggered TXOP sharing) trigger frame) (760) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0127] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0128] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0129] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0130] In one embodiment, the shared AP (710) may determine whether to share the TXOP based on the conditions for sharing the TXOP. In one embodiment, if the shared AP (710) determines to share the TXOP based on the conditions for sharing the TXOP, the shared AP (710) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (765) to the shared AP (700) in response to the control frame (760) after SIFS after receiving the control frame (760).

[0131] For example, if a certain percentage (e.g., 90%) or more of the TXOP to be shared (transferred) is available, which is included in the conditions for sharing the TXOP, the shared AP (710) may transmit a control frame (e.g., a clear-to-send (CTS) frame) to approve sharing (transferring) the TXOP.

[0132] The shared AP (710) can transmit a DL PPDU (770) to the second STA (715) in the TXOP (750) of the shared time interval from the shared AP (700). The shared AP (710) can transmit the DL PPDU (770) to the second STA (715) after SIFS after transmitting the control frame (765). The second STA (715) can transmit an ACK frame (or BA frame) (775) to the shared AP (710) after SIFS after receiving the DL PPDU (770).

[0133] In one embodiment, the shared AP (710) may transmit a control frame (e.g., a CF-End frame) (780) to the shared AP (700) after SIFS after receiving the ACK frame (or, BA frame) (775). In one embodiment, even after receiving the ACK frame (or, BA frame) (775), if the shared TXOP (750) remains, the shared AP (710) may transmit a control frame (e.g., a CF-End frame) (780) to the shared AP (700).

[0134] The sharing AP (700) can transmit a DL PPDU (790) to the first STA connected to the sharing AP (700) after SIFS after receiving the control frame (e.g., CF-End frame) (780).

[0135] In one embodiment, if the shared AP (700) does not transmit the control frame (e.g., CF-End frame) (780), the shared AP (700) may transmit a DL PPDU (790) to the first STA connected to the sharing AP (700) after a certain period of time (e.g., PIFS) after the ACK frame (or, BA frame) (775) is transmitted. The first STA may transmit the ACK frame (or, BA frame) (795) to the sharing AP (700) after an SIFS after receiving the DL PPDU (790).

[0136] The operation when sharing TXOP between the sharing AP and the shared AP illustrated in FIG. 7 can be applied by modifying the operation when sharing TXOP between the AP and the STA. For example, the STA can perform an operation similar to the shared AP, and for example, the STA can determine whether to share the TXOP based on a condition for sharing the TXOP included in the TXS trigger frame received from the AP, and only when the condition for sharing the TXOP is satisfied, the STA can determine to share the TXOP and transmit a control frame (e.g., a clear-to-send (CTS) frame) to the AP. For example, the STA can transmit a UL PPDU or a P2P PPDU within the shared TXOP.

[0137] FIG. 8 is a diagram illustrating an uplink operation between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0138] The sharing AP (800) illustrated in FIG. 8 may operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The shared AP (810) illustrated in FIG. 8 may operate as a shared AP, like the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (800) may share a TXOP with the shared AP (810) whose BSS overlaps. The second STA (815) illustrated in FIG. 8 may include an STA associated with the shared AP (810).

[0139] Referring to FIG. 8, the sharing AP (800) can initiate a TXOP (830) acquired by the sharing AP (800) and transmit a DL PPDU (840) to the first STA connected to the sharing AP (800). After transmitting the DL PPDU (840), the sharing AP (800) can receive an ACK frame (or BA frame) (845) from the first STA after SIFS.

[0140] In one embodiment, the sharing AP (800) may transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (860) to the shared AP (810) to share a TXOP (850) of a certain time interval among the TXOPs (830). The sharing AP (800) may transmit the control frame (860) to the shared AP (810) after SIFS after receiving the ACK frame (or BA frame) (845).

[0141] In one embodiment, a control frame (e.g., a MU-RTS TXS (triggered TXOP sharing) trigger frame) (860) for sharing the TXOP may indicate a condition for sharing the TXOP. The condition for sharing the TXOP may include at least one of the following conditions.

[0142] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0143] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0144] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0145] The shared AP (810) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (865) to the sharing AP (800) in response to the control frame (860) for sharing the TXOP after SIFS after receiving the control frame (860). In one embodiment, the shared AP (810) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the shared AP (810) determines to share the TXOP based on the condition for sharing the TXOP, the shared AP (810) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (865) to the sharing AP (800) in response to the control frame (860).

[0146] For example, if a certain percentage (e.g., 90%) or more of the TXOP to be shared (transferred) is available, which is included in the conditions for sharing the TXOP, the shared AP (810) may transmit a control frame (e.g., a clear-to-send (CTS) frame) to approve sharing (transferring) the TXOP.

[0147] The shared AP (810) can transmit a TRG (trigger) frame (870) to the second STA (815) in the TXOP (850) of the shared time period from the shared AP (800). The shared AP (810) can transmit the TRG (trigger) frame (870) to the second STA (815) after SIFS after transmitting the control frame (865). The second STA (815) can transmit a TB (trigger-based) PPDU (875) to the shared AP (810) after SIFS after receiving the TRG (trigger) frame (870). Thereafter, the shared AP (800) can transmit an ACK frame (or, BA frame) (877) to the second STA (815) after SIFS after receiving the TB PPDU (875).

[0148] In one embodiment, the shared AP (810) may transmit a control frame (e.g., a CF-End frame) (880) to the shared AP (800) after SIFS after transmitting the ACK frame (or BA frame) (877). In one embodiment, even after transmitting the ACK frame (or BA frame) (877), if the shared TXOP (850) remains, the shared AP (810) may transmit a control frame (e.g., a CF-End frame) (880) to the shared AP (800).

[0149] The sharing AP (800) can transmit a DL PPDU (890) to the first STA connected to the sharing AP (800) after SIFS after receiving the control frame (e.g., CF-End frame) (880).

[0150] In one embodiment, if the shared AP (810) does not transmit the control frame (e.g., CF-End frame) (880), the sharing AP (800) may transmit a DL PPDU (890) to the first STA connected to the sharing AP (800) after a certain period of time (e.g., PIFS) after the ACK frame (or, BA frame) (875) is transmitted. The first STA may transmit the ACK frame (or, BA frame) (895) to the sharing AP (800) after an SIFS after receiving the DL PPDU (890).

[0151] FIG. 9 is a diagram illustrating a random access operation in uplink transmission between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0152] The sharing AP (900) illustrated in FIG. 9 can operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The first shared AP (910) and the second shared AP (920) illustrated in FIG. 9 can operate as shared APs, like the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (900) can share TXOP with the first shared AP (910) and the second shared AP (920) whose BSSs overlap. Referring to FIG. 9, the second STA (913) and the third STA (915) are associated with the first shared AP (910), and the fourth STA (925) is associated with the second shared AP (920).

[0153] Referring to FIG. 9, the sharing AP (900) initiates the TXOP acquired by the sharing AP (900), and the sharing AP (900) can transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (940) to the first shared AP (910) to share the TXOP (930) of a certain time interval among the TXOPs.

[0154] In one embodiment, a control frame (e.g., an MU-RTS TXS trigger frame) (940) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0155] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0156] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0157] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0158] The first shared AP (910) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (945) to the sharing AP (900) in response to the control frame (940) for sharing the TXOP after SIFS after receiving the control frame (960). In one embodiment, the first shared AP (910) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the first shared AP (910) determines to share the TXOP based on the condition for sharing the TXOP, the first shared AP (910) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (945) to the sharing AP (900) in response to the control frame (940).

[0159] In one embodiment, the first shared AP (910) may transmit (e.g., broadcast) a UORA TRG (trigger) frame (950) to STAs within the BSS in a TXOP (930) of a time interval shared from the shared AP (900). STAs within the BSS of the first shared AP (910) (e.g., the second STA (913) and the third STA (915)) may not transmit (955) a UORA frame for the UORA TRG frame (950). That is, STAs within the BSS of the first shared AP (910) (e.g., the second STA (913) and the third STA (915)) may not participate in the random access triggered by the UORA TRG frame (950).

[0160] In one embodiment, the first shared AP (910) may transmit a control frame (e.g., a CF-End frame) (960) to the sharing AP (900) if it does not receive a UORA frame from STAs for a certain period of time (e.g., PIFS) after the UORA TRG frame (950) is transmitted.

[0161] After receiving the control frame (e.g., CF-End frame) (960), the sharing AP (900) can transmit a control frame (e.g., MU-RTS TXS (triggered TXOP sharing) trigger frame) (970) to the second shared AP (920) after SIFS to share a TXOP (930) of a certain time interval among the TXOPs.

[0162] The second shared AP (920) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (975) to the sharing AP (900) in response to the control frame (970) for sharing the TXOP after SIFS after receiving the control frame (970). In one embodiment, the second shared AP (920) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the second shared AP (920) determines to share the TXOP based on the condition for sharing the TXOP, the second shared AP (920) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (975) to the sharing AP (900) in response to the control frame (970).

[0163] For example, if a certain percentage or more of the TXOP to be shared (transferred) is available (e.g., 90%) included in the conditions for sharing the TXOP, the second shared AP (920) may approve sharing (transferring) the TXOP by transmitting the control frame (e.g., CTS (clear-to-send) frame).

[0164] The second shared AP (920) can transmit a DL PPDU (980) to the fourth STA (925) in a TXOP (930) of a time interval shared from the shared AP (900). The second shared AP (920) can transmit the DL PPDU (980) to the fourth STA (925) after SIFS after transmitting the control frame (975). The fourth STA (925) can transmit an ACK frame (or BA frame) (985) to the second shared AP (920) after SIFS after receiving the DL PPDU (980).

[0165] As illustrated in Fig. 9, when a shared AP that has shared a TXOP triggers random access, the TXOP may not be properly utilized because STAs do not transmit UORA. Therefore, the sharing AP can instruct the shared AP to prohibit the allocation of only UORA from the shared (transferred) TXOP.

[0166] FIG. 10 is a diagram illustrating a case in which a collision occurs in a random access operation in an uplink transmission between a shared AP and an STA when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0167] The sharing AP (1000) illustrated in FIG. 10 can operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The first shared AP (1010) and the second shared AP (1020) illustrated in FIG. 10 can operate as shared APs, like the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (1000) can share a TXOP with the first shared AP (1010) and the second shared AP (1020) whose BSSs overlap. Referring to FIG. 10, the second STA (1013) and the third STA (1015) are associated with the first shared AP (1010), and the fourth STA (1025) is associated with the second shared AP (1020).

[0168] Referring to FIG. 10, the sharing AP (1000) initiates the TXOP acquired by the sharing AP (1000), and the sharing AP (1000) can transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (1040) to the first shared AP (1010) to share the TXOP (1030) of a certain time interval among the TXOPs.

[0169] In one embodiment, a control frame (e.g., an MU-RTS TXS trigger frame) (1040) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0170] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0171] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0172] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0173] The first shared AP (1010) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1045) to the sharing AP (1000) in response to the control frame (1040) for sharing the TXOP after SIFS after receiving the control frame (1060). In one embodiment, the first shared AP (1010) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the first shared AP (1010) determines to share the TXOP based on the condition for sharing the TXOP, the first shared AP (1010) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1045) to the sharing AP (1000) in response to the control frame (1040).

[0174] In one embodiment, the first shared AP (1010) may transmit (e.g., broadcast) a UORA TRG (trigger) frame (1050) to STAs within a BSS in a TXOP (1030) of a time interval shared from the shared AP (1000). STAs within the BSS of the first shared AP (1010) (e.g., the second STA (1013) and the third STA (1015)) may transmit UORA frames (1053, 1055) for the UORA TRG frame (1050) SIFS after receiving the UORA TRG frame (1050). In one embodiment, the second STA (1013) and the third STA (1015) may transmit UORA frames (1053, 1055) for the UORA TRG frame (1050) in the same RU (resource unit) 1, which may cause a collision. In this case, the first shared AP (1010) may transmit a control frame (e.g., a CF-End frame) (1060) to the sharing AP (1000) after SIFS after the UORA frames (1053, 1055) are transmitted.

[0175] After receiving the control frame (e.g., CF-End frame) (1060), the sharing AP (1000) may transmit a control frame (e.g., MU-RTS TXS (triggered TXOP sharing) trigger frame) (1070) to the second shared AP (1020) after SIFS to share a TXOP (1030) of a certain time interval among the TXOPs.

[0176] The second shared AP (1020) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1075) to the sharing AP (1000) in response to the control frame (1070) for sharing the TXOP after SIFS after receiving the control frame (e.g., an MU-RTS TXS trigger frame) (1070). In one embodiment, the second shared AP (1020) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the second shared AP (1020) determines to share the TXOP based on the condition for sharing the TXOP, the second shared AP (1020) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1080) to the sharing AP (1000) in response to the control frame (1070).

[0177] For example, if a certain percentage or more of the TXOP to be shared (transferred) is available (e.g., 90%) included in the conditions for sharing the TXOP, the second shared AP (1020) may approve sharing (transferring) the TXOP by transmitting the control frame (e.g., CTS (clear-to-send) frame) (1080).

[0178] The second shared AP (1020) can transmit a DL PPDU (1090) to the fourth STA (1025) in a TXOP (1030) of a time interval shared from the shared AP (1000). The second shared AP (1020) can transmit the DL PPDU (1090) to the fourth STA (1025) after SIFS after transmitting the control frame (1080). The fourth STA (1025) can transmit an ACK frame (or BA frame) (1095) to the second shared AP (1020) after SIFS after receiving the DL PPDU (1090).

[0179] As illustrated in Fig. 10, when a shared AP that has shared a TXOP triggers random access, a collision may occur between UORA transmissions transmitted by STAs, which may prevent the TXOP from being properly utilized. Therefore, the sharing AP may instruct the shared AP to prohibit the allocation of only UORAs from the shared (transferred) TXOP.

[0180] FIG. 11 is a diagram illustrating an operation in which a shared AP rejects sharing of a TXOP when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0181] The sharing AP (1100) illustrated in FIG. 11 can operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The first shared AP (1110) and the second shared AP (1120) illustrated in FIG. 11 can operate as shared APs, like the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (1100) can share a TXOP with the first shared AP (1110) and the second shared AP (1120) whose BSSs overlap. Referring to FIG. 11, the fourth STA (1125) illustrates an STA that is associated with the second shared AP (1120).

[0182] Referring to FIG. 11, the sharing AP (1100) initiates the TXOP acquired by the sharing AP (1100), and the sharing AP (1100) can transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (1140) to the first shared AP (1110) to share the TXOP (1130) of a certain time interval among the TXOPs.

[0183] In one embodiment, a control frame (e.g., an MU-RTS TXS trigger frame) (1140) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0184] - If there is buffered downlink traffic (DL traffic), or a buffer report is made and a non-zero STA is identified (e.g., Buffer size, Non-zero buffer STA count).

[0185] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0186] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0187] In one embodiment, the first shared AP (1110) may determine whether to share the TXOP based on the condition for sharing the TXOP. In one embodiment, if the first shared AP (1110) determines not to share the TXOP based on the condition for sharing the TXOP, the first shared AP (1110) may transmit a control frame (e.g., a clear-to-send (CTS)-to-self frame) (1145) in response to the control frame (1140) to the sharing AP (1100) SIFS after receiving the control frame (1160). In one embodiment, if the first shared AP (1110) determines not to share the TXOP based on the condition for sharing the TXOP, the first shared AP (1110) may transmit a control frame other than the CTS-to-self frame as exemplified in FIG. 11.

[0188] After receiving the control frame (e.g., CTS-to-self frame) (1145), the sharing AP (1100) may transmit a control frame (e.g., MU-RTS TXS (triggered TXOP sharing) trigger frame) (1150) to the second shared AP (1120) after SIFS to share a TXOP (1130) of a time interval among the TXOPs.

[0189] The second shared AP (1120) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1155) to the sharing AP (1100) in response to a control frame (e.g., an MU-RTS TXS trigger frame) (1150) for sharing the TXOP after SIFS after receiving the control frame (1150). In one embodiment, the second shared AP (1120) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, when the second shared AP (1120) determines to share the TXOP based on the condition for sharing the TXOP, the second shared AP (1120) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1155) to the sharing AP (1100) in response to the control frame (1150).

[0190] For example, if a certain percentage or more of the TXOP to be shared (transferred) is available (e.g., 90%) included in the conditions for sharing the TXOP, the second shared AP (1120) may approve sharing (transferring) the TXOP by transmitting the control frame (e.g., CTS (clear-to-send) frame) (1155).

[0191] The second shared AP (1120) can transmit a DL PPDU (1160) to the fourth STA (1125) in a TXOP (1130) of a time interval shared from the shared AP (1100). The second shared AP (1120) can transmit the DL PPDU (1160) to the fourth STA (1125) after SIFS after transmitting the control frame (1155). The fourth STA (1125) can transmit an ACK frame (or BA frame) (1165) to the second shared AP (1120) after SIFS after receiving the DL PPDU (1160).

[0192] FIG. 12 is a diagram illustrating an operation in which a shared AP rejects sharing of a TXOP when sharing a TXOP between access points according to one embodiment of the present disclosure.

[0193] The sharing AP (1200) illustrated in FIG. 12 can operate as a sharing AP, like the first AP (400) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. The first shared AP (1210) and the second shared AP (1220) illustrated in FIG. 12 can operate as shared APs, like the second AP (410) included in the wireless communication system including multiple access points and stations illustrated in FIG. 4. That is, the sharing AP (1200) can share a TXOP with the first shared AP (1210) and the second shared AP (1220) whose BSSs overlap. Referring to FIG. 12, the fourth STA (1225) illustrates an STA that is associated with the second shared AP (1220).

[0194] Referring to FIG. 12, the sharing AP (1200) initiates the TXOP acquired by the sharing AP (1200), and the sharing AP (1200) can transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (1240) to the first shared AP (1210) to share the TXOP (1230) of a certain time interval among the TXOPs.

[0195] In one embodiment, a control frame (e.g., an MU-RTS TXS trigger frame) (1240) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0196] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0197] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0198] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0199] In one embodiment, the first shared AP (1210) may receive a control frame (e.g., an MU-RTS TXS trigger frame) (1240) for sharing the TXOP, and may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, if the first shared AP (1210) determines not to share the TXOP based on the condition for sharing the TXOP, the first shared AP (1210) may not transmit a response frame to the control frame (1240) (1245).

[0200] If the sharing AP (1200) does not receive a response frame for a certain period of time (e.g., PIFS) after transmitting the control frame (e.g., MU-RTS TXS trigger frame) (1240), the sharing AP (1200) may transmit a control frame (e.g., MU-RTS TXS trigger frame) (1250) to the second shared AP (1120) to share a TXOP (1230) of a certain time interval among the TXOPs.

[0201] The second shared AP (1220) may be a sharing AP (1200), and may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1255) in response to a control frame (e.g., an MU-RTS TXS trigger frame) (1250) for sharing the TXOP after SIFS after receiving the control frame (e.g., an MU-RTS TXS trigger frame) (1250). In one embodiment, the second shared AP (1220) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, if the second shared AP (1220) determines to share the TXOP based on the conditions for sharing the TXOP, it may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1255) to the sharing AP (1200) in response to the control frame (1250).

[0202] For example, if a certain percentage or more of the TXOP to be shared (transferred) is available (e.g., 90%) included in the conditions for sharing the TXOP, the second shared AP (1220) may approve sharing (transferring) the TXOP by transmitting the control frame (e.g., CTS (clear-to-send) frame) (1255).

[0203] The second shared AP (1220) can transmit a DL PPDU (1260) to the fourth STA (1225) in a TXOP (1230) of a time interval shared from the shared AP (1200). The second shared AP (1220) can transmit the DL PPDU (1260) to the fourth STA (1225) after SIFS after transmitting the control frame (1255). The fourth STA (1225) can transmit an ACK frame (or BA frame) (1265) to the second shared AP (1220) after SIFS after receiving the DL PPDU (1260).

[0204] The operation when sharing TXOP between the sharing AP and the shared AP illustrated in Fig. 12 can be applied by modifying the operation when sharing TXOP between the AP and the STA. For example, the STA can perform an operation similar to the shared AP, and for example, the STA can determine whether to share the TXOP based on the condition for sharing the TXOP included in the TXS trigger frame received from the AP, and if the condition for sharing the TXOP is not met, the STA can determine not to share the TXOP and not transmit a response frame to the AP.

[0205] FIG. 13 is a diagram illustrating an operation in which a station refuses to share a TXOP when sharing a TXOP between an access point and a station according to one embodiment of the present disclosure.

[0206] In one embodiment, the first STA (1310), the second STA (1320), and the third STA (1325) illustrated in FIG. 13 may be included in the BSS or OBSS of the sharing AP (1300).

[0207] Referring to FIG. 13, the sharing AP (1300) initiates the TXOP acquired by the sharing AP (1300), and the sharing AP (1300) can transmit a control frame (e.g., an MU-RTS TXS (triggered TXOP sharing) trigger frame) (1340) to the first STA (1310) to share the TXOP (1330) of a certain time interval among the TXOPs.

[0208] In one embodiment, a control frame (e.g., an MU-RTS TXS trigger frame) (1340) for sharing the TXOP may indicate conditions for sharing the TXOP. The conditions for sharing the TXOP may include at least one of the following conditions.

[0209] - If there is buffered downlink traffic (DL traffic) or a buffer report is made and a non-zero terminal is identified (e.g., Buffer size, number of non-zero buffer terminals)

[0210] - If a certain percentage of the TXOP to be shared (transferred) is available (e.g. 90%)

[0211] - When there is high priority traffic (specific AC (access category) (e.g. low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.)

[0212] In one embodiment, the first STA (1310) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, if the first STA (1310) determines not to share the TXOP based on the condition for sharing the TXOP, the first STA (1310) may transmit a control frame (e.g., a clear-to-send (CTS)-to-self frame) (1345) in response to the control frame (1340) to the sharing AP (1300) SIFS after receiving the control frame (1160). In one embodiment, if the first shared AP (1110) determines not to share the TXOP based on the condition for sharing the TXOP, the first shared AP (1110) may transmit a control frame other than the CTS-to-self frame as exemplified in FIG. 11.

[0213] After receiving the control frame (e.g., CTS-to-self frame) (1345), the sharing AP (1300) may transmit a control frame (e.g., MU-RTS TXS trigger frame) (1350) to the second STA (1320) after SIFS to share a TXOP (1330) of a certain time interval among the TXOPs.

[0214] The second STA (1320) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1355) to the sharing AP (1300) in response to a control frame (e.g., an MU-RTS TXS trigger frame) (1350) for sharing the TXOP after SIFS after receiving the control frame (1350). In one embodiment, the second STA (1320) may determine whether to share the TXOP based on a condition for sharing the TXOP. In one embodiment, if the second STA (1320) determines to share the TXOP based on the condition for sharing the TXOP, the second STA (1320) may transmit a control frame (e.g., a clear-to-send (CTS) frame) (1355) to the sharing AP (1300) in response to the control frame (1350).

[0215] For example, if a certain percentage or more of the TXOP to be shared (transferred) is available (e.g., 90%) included in the conditions for sharing the TXOP, the second STA (1320) may approve sharing (transferring) the TXOP by transmitting the control frame (e.g., CTS (clear-to-send) frame) (1355).

[0216] The second STA (1320) may transmit a P2P PPDU (1360) to the third STA (1325) in the TXOP (1330) of the shared time interval from the sharing AP (1300). The second STA (1320) may transmit the DL PPDU (1360) to the third STA (1325) after an SIFS after transmitting the control frame (1355). The third STA (1325) may transmit an ACK frame (or BA frame) (1365) to the second STA (1320) after an SIFS after receiving the DL PPDU (1360). In one embodiment, the second STA (1320) may transmit a UL PPDU to the sharing AP (1300) in the TXOP (1330) of the shared time interval from the sharing AP (1300). The sharing AP (1300) can transmit an ACK frame (or BA frame) to the second STA (1320) after SIFS after receiving the UL PPDU.

[0217] FIGS. 14a, 14b, 14c, 14d, and 14e are diagrams illustrating examples of field and information element formats of a TXS trigger frame used by an access point when sharing the TXOP according to one embodiment of the present disclosure.

[0218] FIG. 14a is a diagram showing an example of a trigger frame format, which is a control frame in an IEEE 802.11 system applicable to the present disclosure.

[0219] FIG. 14b is a diagram showing an example of a subfield or IE (information element) included in the common info field (1410) in the trigger frame illustrated in FIG. 14a that can be applied to the present disclosure.

[0220] FIG. 14c is a diagram showing an example of the value of the Trigger type subfield (1420) among the subfields included in the common info field in the trigger frame illustrated in FIG. 14b, which can be applied to the present disclosure.

[0221] In the IEEE 802.11 system, the type of trigger frame can be indicated in the Trigger type subfield (1420) included in the common info field of the trigger frame. For example, if the value of the Trigger type subfield (1420) is '0', it can indicate that it is a basic general trigger frame. For example, if the value of the Trigger type subfield is '3', it can indicate that it is an MU-RTS trigger frame.

[0222] The format of the common info field in the trigger frame illustrated in FIG. 14b may indicate a HE or EHT variant common info field, and when the Trigger type subfield indicates that it is an MU-RTS trigger frame, the B20-B21 subfield (1425) of the HE or EHT variant common info field of the trigger frame illustrated in FIG. 14b may be used as a triggered TXOP sharing mode subfield.

[0223] FIG. 14d is a diagram illustrating an example of a value of a triggered TXOP sharing mode subfield that may be included in a TXS (triggered TXOP sharing) trigger frame applicable to the present disclosure.

[0224] As an example, FIG. 14d is a diagram showing an example of values ​​that may be included in the triggered TXOP sharing mode subfield (1425) among the subfields included in the common info field in the trigger frame illustrated in FIG. 14b.

[0225] In an IEEE 802.11 system, if the Trigger type subfield of a trigger frame indicates that it is an MU-RTS trigger frame, and the value of the triggered TXOP sharing mode subfield (1425) among the subfields included in the common info field in the trigger frame is not '0', the trigger frame may be referred to as an MU-RTS TXS trigger frame.

[0226] In one embodiment, the MU-RTS TXS trigger frame illustrated in FIGS. 7 to 13 may indicate a trigger frame in which the Trigger type subfield of the trigger frame indicates that it is an MU-RTS trigger frame, and the value of the triggered TXOP sharing mode subfield (1425) among the subfields included in the common info field in the trigger frame is not '0'.

[0227] Referring to FIG. 14d, when the value of the triggered TXOP sharing mode subfield of the trigger frame is '1' or '2', the trigger frame may be an MU-RTS trigger frame that initiates a TXS procedure for sharing TXOP with the corresponding STA.

[0228] In one embodiment, when the value of the triggered TXOP sharing mode subfield of the trigger frame is '3', the trigger frame may indicate that the shared AP can use the shared TXOP without any conditions. In one embodiment, when the value of the triggered TXOP sharing mode subfield of the trigger frame is '4', the trigger frame may indicate that the shared AP can use the shared TXOP under a first condition. The first condition may include, for example, a condition for a Buffered BU (e.g., a buffer size) or a condition for a STA connected to the shared AP that reported the buffer status (e.g., the number of the corresponding STAs).

[0229] In one embodiment, when the value of the triggered TXOP sharing mode subfield of the trigger frame is '5', the trigger frame may indicate that the shared AP can use the shared TXOP under a second condition. The second condition may include, for example, a condition on the usage ratio of the TXOP to be shared (transferred) (e.g., 90% or 100%).

[0230] In one embodiment, when the value of the triggered TXOP sharing mode subfield of the trigger frame is '6', the trigger frame may indicate that the shared AP can use shared TXOP under a third condition. The third condition may include, for example, a condition for specific traffic to be transmitted (e.g., a specific access category (AC) (e.g., low-latency traffic) / traffic identifier (TID) / traffic requirement, etc.).

[0231] FIG. 14e is a diagram illustrating an example of a subfield or IE including TXOP sharing related information that may be included in a trigger frame, applicable to the present disclosure.

[0232] As an example, FIG. 14e is a diagram showing an example of a subfield or IE (information element) included in the user info field (1410) illustrated in FIG. 14a in the case of an MU-RTS TXS trigger frame.

[0233] Referring to FIG. 14e, the user info field of the MU-RTS TXS trigger frame may include at least one of the AP Address subfield (1450), the RU allocation subfield (1453), the allocation duration subfield (1455), and the TXS condition subfield (1457).

[0234] In one embodiment, the AP Address subfield (1450) may include information for indicating an AP that wishes to share a TXOP in the MU-RTS TXS trigger frame. For example, the AP Address subfield (1450) may include BSS MAC Address or BSS Color information. In one embodiment, when the MU-RTS TXS trigger frame is transmitted to an STA, the user info field of the MU-RTS TXS trigger frame may additionally include an AID subfield.

[0235] In one embodiment, the RU allocation subfield (1453) and / or allocation duration subfield (1455) may indicate information such as resource allocation information and / or allocation duration of a shared TXOP.

[0236] In one embodiment, the TXS condition subfield (1457) may include information on conditions under which a shared TXOP can be used. For example, the TXS condition subfield (1457) may include at least one of minimum buffer size information, number of STAs reporting buffer status, minimum usage rate information of the shared TXOP, information on a specific AC (access category) (e.g., low-latency traffic) / TID (traffic identifier) / traffic requirement, etc.), or information on whether UORA is allowed.

[0237] The frame names, subfield names, and / or values ​​including the information described in FIGS. 14d and 14e are examples for convenience of explanation, and the information described above may be included in a frame for sharing a TXOP acquired by a sharing AP with a shared AP and / or a sharing AP with an STA.

[0238] The size (e.g., bit size) and / or position (e.g., bit position) of each field included in the IE (or information) illustrated in FIGS. 14a, 14b, 14c, 14d, and 14e are merely examples for convenience of explanation and may be implemented in various ways depending on design specifications.

[0239] FIG. 15 is a flowchart illustrating the operation of a first access point according to one embodiment of the present disclosure.

[0240] At step 1500, the first access point may obtain a transmission opportunity (TXOP).

[0241] In step 1510, the first access point may transmit a first trigger frame to the second access point, triggering sharing of the TXOP. In one embodiment, the first trigger frame may include sharing condition information of the TXOP for the access point.

[0242] In step 1520, the first access point may transmit a second trigger frame to trigger sharing of the TXOP to the third access point based on whether a response frame has been received from the second access point. In one embodiment, the response frame may be based on the sharing condition information.

[0243] In one embodiment, the first trigger frame and the second trigger frame that trigger sharing for the TXOP may instruct that some time interval included in the TXOP be used.

[0244] In one embodiment, transmitting the second trigger frame triggering sharing of the TXOP to the third access point based on whether the first access point has received the response frame from the second access point may include transmitting the second trigger frame triggering sharing of the TXOP to the third access point if the response frame has not been received from the second access point for a predetermined time interval. In one embodiment, the predetermined time interval may include a time corresponding to a PIFS (point coordination function (PCF) inter frame space (IFS)).

[0245] In one embodiment, transmitting the second trigger frame triggering sharing of the TXOP to the third access point based on whether the first access point has received the response frame from the second access point may include receiving a response frame from the second access point and, if the response frame is a predetermined control frame, transmitting the second trigger frame triggering sharing of the TXOP to the third access point.

[0246] In one embodiment, the predetermined control frame may include a clear to send (CTS)-to-self frame.

[0247] In one embodiment, the sharing condition information of the TXOP may indicate at least one of: condition information related to a buffer to be transmitted using the shared TXOP; condition information related to a usage ratio of the shared TXOP; and condition information related to traffic to be transmitted using the shared TXOP.

[0248] In one embodiment, the first trigger frame may include information indicating whether an uplink OFDMA-based random access (UORA) trigger is possible in a shared TXOP.

[0249] In one embodiment, the first trigger frame may include one of a BSS (basic service set) MAC (media access control) address or BSS color information related to the second access point, and resource-related information for a shared TXOP.

[0250]

[0251] FIG. 16 is a flowchart illustrating the operation of a second access point according to one embodiment of the present disclosure.

[0252] In step 1600, the second access point may receive a trigger frame from the first access point that triggers sharing of a transmission opportunity (TXOP) acquired by the first access point. In one embodiment, the trigger frame may include sharing condition information for the TXOP for the access point.

[0253] At step 1610, the second access point may determine whether to share the TXOP based on the shared condition information.

[0254] At step 1620, the second access point may decide to transmit a response frame to the first access point based on whether it has determined whether to share the TXOP.

[0255] In one embodiment, the second access point may instruct the trigger frame that triggers sharing for the TXOP to use some time interval included in the TXOP.

[0256] In one embodiment, determining whether to transmit the response frame to the first access point based on whether the second access point has determined to share the TXOP may include determining not to transmit the response frame to the first access point if the second access point has determined not to share the TXOP.

[0257] In one embodiment, determining whether to transmit a response frame to the first access point based on whether the second access point has determined to share the TXOP may include determining to transmit a predetermined control frame to the first access point if the second access point has determined not to share the TXOP.

[0258] In one embodiment, the predetermined control frame may include a clear to send (CTS)-to-self frame.

[0259] In one embodiment, the sharing condition information of the TXOP may indicate at least one of: condition information related to a buffer to be transmitted using the shared TXOP; condition information related to a usage ratio of the shared TXOP; and condition information related to traffic to be transmitted using the shared TXOP.

[0260] In one embodiment, the first trigger frame may include information indicating whether an uplink OFDMA-based random access (UORA) trigger is possible in a shared TXOP.

[0261] In one embodiment, the first trigger frame may include one of a BSS (basic service set) MAC (media access control) address or BSS color information related to the second access point, and resource-related information for a shared TXOP.

[0262] FIG. 17 is a diagram showing an example configuration of a station according to one embodiment of the present disclosure.

[0263] In FIG. 17, the station may include a processor (1701), a transceiver (1702), and a memory (1703). The processor (1701), the transceiver (1702), and the memory (1703) of the station may operate according to the method(s) described in the above-described embodiments of FIGS. 1 to 16 . However, the components of the station are not limited to the examples described above. For example, the station may include more or fewer components than the components described above. In addition, the processor (1701), the transceiver (1702), and the memory (1703) may be implemented in the form of at least one chip.

[0264] The transceiver (1702) is a general term for a receiver and a transmitter, and can transmit and receive signals with a station or other network entity through the transceiver (1702). At this time, the transmitted and received signal 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 a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. This is only one embodiment of the transceiver (1702), and the components of the transceiver (1702) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1702) can receive a signal and output it to the processor (1701), and transmit the signal output from the processor (1701) to another network entity through the network.

[0265] The memory (1703) can store programs and data required for the operation of the station according to at least one of the embodiments of FIGS. 1 to 16. In addition, the memory (1703) can store control information and / or data included in a signal acquired from the station. The memory (1703) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0266] The processor (1701) may control a series of processes so that the station can operate according to at least one of the embodiments of FIGS. 1 to 16. The processor (1701) may include at least one processor.

[0267] FIG. 18 is a diagram showing an example configuration of an access point according to one embodiment of the present disclosure.

[0268] In FIG. 18, the access point may include a processor (1801), a transceiver (1802), and a memory (1803). The processor (1801), the transceiver (1802), and the memory (1803) of the access point may operate according to the method(s) described in the above-described embodiments of FIGS. 1 to 16 . However, the components of the access point are not limited to the examples described above. For example, the access point may include more or fewer components than the above-described components. In addition, the processor (1801), the transceiver (1802), and the memory (1803) may be implemented in the form of at least one chip.

[0269] The transceiver (1802) is a general term for a receiver and a transmitter, and can transmit and receive signals with a station or other network entity through the transceiver (1802). At this time, the transmitted and received signal may include at least one of control information and data. To this end, the transceiver (1802) may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts the received signal. This is only one embodiment of the transceiver (1802), and the components of the transceiver (1802) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1802) can receive a signal and output it to the processor (1801), and transmit the signal output from the processor (1801) to another network entity through the network.

[0270] The memory (1803) can store programs and data necessary for the operation of the access point according to at least one of the embodiments of FIGS. 1 to 16. In addition, the memory (1803) can store control information and / or data included in a signal acquired from the access point. The memory (1803) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0271] The processor (1801) may control a series of processes so that the access point can operate according to at least one of the embodiments of FIGS. 1 to 16. The processor (1801) may include at least one processor.

[0272] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0273] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

In a method performed by a first access point (AP) in a wireless local access network (WLAN) system, An operation of receiving, from a second access point, a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point; An operation for determining whether to share the TXOP based on the first control frame; and A method characterized by comprising: an operation of determining not to transmit the response frame to the second access point when it is determined not to share the TXOP; In the first paragraph, the first control frame includes sharing condition information of the TXOP for the access point, A method characterized in that the operation of determining whether to share the TXOP includes an operation of determining whether to share the TXOP based on the sharing condition information. In the first paragraph, the first control frame, A method characterized by indicating that some time interval included in the above TXOP should be used. In the first paragraph, A method characterized by comprising: an operation of determining to transmit a second control frame to the first access point when it is determined not to share the TXOP; In paragraph 4, A method characterized in that the second control frame includes a CTS (clear to send)-to-self frame. In a method of a second access point (AP) in a wireless local access network (WLAN) system, An operation of transmitting a first control frame related to sharing of a transmission opportunity (TXOP) acquired by at least one first access point; An operation for identifying whether a response frame has been received from at least one first access point; and A method characterized by comprising: an operation of determining whether to share a TXOP with a third access point excluding the at least one first access point, if the response frame is not received from the at least one first access point. In the sixth paragraph, the first control frame includes sharing condition information of the TXOP for the access point, and A method characterized in that the above response frame is based on the above shared condition information. In paragraph 6, A method characterized in that the first control frame includes a first trigger frame for triggering a TXOP. In paragraph 6, A method characterized by comprising: an operation of transmitting a first trigger frame that triggers sharing of the TXOP to the third access point when the response frame is not received from the at least one first access point. In the sixth paragraph, if the response frame is not received from the at least one first access point, the operation of determining whether to share the TXOP with the third access point excluding the at least one first access point; A method characterized by comprising: an operation of transmitting the second trigger frame, which triggers sharing of the TXOP to the third access point, when the response frame is not received from the at least one first access point for a predetermined time interval; In the 10th paragraph, the predetermined time interval is: A method characterized in that the time corresponding to PIFS (PCF (point coordination function) IFS (inter frame space)) is. In the sixth paragraph, the first control frame, A method characterized by including information indicating whether an uplink OFDMA-based random access (UORA) trigger is possible in a shared TXOP. In the sixth paragraph, the first control frame, Information of one of the BSS (basic service set) MAC (media access control) address or BSS color information related to the first access point, and A method characterized by including resource-related information for a shared TXOP. In a wireless local area network (WLAN) system, at the first access point (AP), Transmitter and receiver; and One or more processors including processing circuitry; and A memory for storing instructions, wherein when the instructions are individually or collectively executed by the one or more processors, the first access point: Receive a first control frame related to sharing of a transmission opportunity (TXOP) acquired by the second access point from the second access point, Based on the first control frame, determine whether to share the TXOP, and A first access point characterized in that, if it is determined not to share the TXOP, it causes the second access point to decide not to transmit the response frame. In a wireless local area network (WLAN) system, at a second access point (AP), Transmitter and receiver; and One or more processors including processing circuitry; and A memory for storing instructions, wherein when the instructions are individually or collectively executed by the one or more processors, the second access point: Transmitting a first control frame related to sharing of a transmission opportunity (TXOP) acquired by at least one first access point, Identifying whether a response frame has been received from at least one first access point, and A second access point characterized in that it causes a determination to be made as to whether to share a TXOP with a third access point excluding the at least one first access point if the response frame is not received from the at least one first access point.

Images