Method and apparatus for request-based low latency communication in wireless local area network system

Abstract

A method and an apparatus for request-based low latency communication in a wireless local area network system are provided. Provided is an operation method of a first device in a wireless local area network system, the method comprising the steps of: receiving downlink data from a second device that is a transmission opportunity (TXOP) holder; transmitting information requesting sharing of the TXOP to a second device; receiving information about the shared TXOP from the second device; and obtaining a shared TXOP, where the shared TXOP is a period during which the first device can transmit uplink data.

Description

Technical Field

[0001] The present invention relates to a wireless local area network (WLAN) system, and more specifically, to a method and apparatus for request-based low-latency communication in a WLAN system. Background Technology

[0002] Recently, with the widespread adoption of mobile devices, wireless LAN technology, which provides fast wireless communication services to mobile devices, has attracted attention. Wireless LAN technology is a technology that uses wireless communication to enable mobile devices (such as smartphones, tablets, laptops, portable multimedia players, embedded devices, etc.) to wirelessly access the internet.

[0003] As applications requiring higher throughput and / or real-time transmission emerge, extended frequency bandwidth and / or efficient retransmission operations can be supported in wireless LANs. Furthermore, simultaneous use of multiple channels or multiple links can be supported.

[0004] On the other hand, the techniques described in the background section are written to improve the understanding of the background of the present invention, and may include content that is not yet known to those skilled in the art to which the present invention pertains. Summary of the Invention

[0005] Technical issues The present invention aims to provide a method and apparatus for rapidly transmitting data stored in a wireless local area network (WLAN) terminal during data reception from another WLAN terminal in a wireless local area network (WLAN) system.

[0006] This invention aims to provide a method and apparatus for rapidly transmitting data stored in a terminal and requiring low latency in a wireless local area network system.

[0007] This invention aims to provide a method and apparatus for requesting scheduling in a wireless local area network system to transmit data during data reception.

[0008] The technical objectives to be achieved in this invention are not limited to those described above, and those skilled in the art who apply the technical configuration of this invention may consider other technical objectives not mentioned herein from the embodiments of the invention described below.

[0009] Technical solution According to an embodiment of the present invention, a method of operating a first device in a wireless local area network system includes: receiving at least one first frame from a second device, sending at least one second frame to the second device including information requesting the sharing of a TXOP, and receiving at least one third frame from the second device including information about the shared TXOP.

[0010] According to another embodiment of the present invention, a method of operating a second device in a wireless local area network system includes: obtaining a TXOP by performing a channel access procedure, sending at least one first frame, receiving at least one second frame from the first device including information requesting the sharing of the TXOP, and sending at least one third frame to the first device including information about the shared TXOP.

[0011] According to another embodiment of the present invention, a first device in a wireless local area network system includes: a transceiver and a processor coupled to the transceiver, wherein the processor can control the transceiver to receive at least one first frame from a second device, send a second frame to the second device including information requesting TXOP sharing, and receive a third frame from the second device including information in response to the request for sharing.

[0012] According to another embodiment of the present invention, a second device in a wireless local area network system includes: a transceiver and a processor coupled to the transceiver, wherein the processor may obtain a TXOP by performing a channel access procedure, control the transceiver to send at least one first frame, control the transceiver to receive at least one second frame including information requesting the sharing of the TXOP from the first device, and control the transceiver to send at least one third frame including information about the shared TXOP to the first device.

[0013] According to another embodiment of the present invention, the first device may send at least one fourth frame to the second device, and the fourth frame may include at least one data frame and a control frame.

[0014] According to another embodiment of the invention, the information requesting the sharing of TXOP may include at least one of information indicating the start time of the sharing and information indicating the size of the resource to be shared.

[0015] According to another embodiment of the invention, the information indicating the start time of sharing may include: information indicating the start time of sharing for at least one of each Access Category (AC) and each Service Indication (TID).

[0016] According to another embodiment of the invention, the size of the resource may include the size of the data or the size in terms of time.

[0017] According to another embodiment of the invention, the third frame may include at least one trigger frame and a data frame.

[0018] According to another embodiment of the invention, the third frame may include information in response to a request for sharing via TXOP.

[0019] According to another embodiment of the invention, the information regarding the shared TXOP may include at least one of the size of the shared TXOP and the transmission mode information of the first device.

[0020] According to another embodiment of the present invention, the transmission mode information may include information related to the transmission target device of the first device.

[0021] The features briefly outlined above are provided as examples to illustrate the detailed description and should not be construed as limiting the scope of the invention.

[0022] Beneficial effects According to the present invention, a wireless local area network (WLAN) terminal and a communication method are provided, which can request to share a TXOP obtained by another WLAN terminal, so as to quickly transmit data requiring low latency during communication in the WLAN system.

[0023] According to the present invention, a wireless local area network (WLAN) terminal and a communication method are provided, which can quickly transmit data that requires low-latency transmission, thereby reducing the data transmission latency in the WLAN system.

[0024] The effects obtained in this invention are not limited to those described above, and those skilled in the art who apply the technical configuration of this invention can clearly deduce and understand other effects not mentioned above from the following description of the embodiments of this invention. Attached Figure Description

[0025] Figure 1 A block diagram of a communication node in a wireless local area network system is shown.

[0026] Figure 2 This illustrates the concept of multiple links set up between multi-link devices (MLDs) in a wireless local area network system.

[0027] Figure 3 A first implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0028] Figure 4 A second implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0029] Figure 5 A third implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0030] Figure 6 A fourth implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0031] Figure 7 A method for operating the first station (STA) according to an embodiment of the present invention is shown.

[0032] Figure 8 A method for operating an access point (AP) according to an embodiment of the present invention is shown. Detailed Implementation

[0033] In the following description, embodiments of the invention will be specifically described with reference to the accompanying drawings to enable those skilled in the art to readily implement the embodiments. However, the invention may be embodied in different forms and is not limited to the embodiments described herein.

[0034] In describing this invention, detailed descriptions of known functions and configurations will be omitted where such descriptions might obscure the subject matter. Additionally, in the accompanying drawings, portions irrelevant to the description of the invention are omitted, and the same reference numerals refer to the same parts.

[0035] In this invention, when a component is "connected," "linked," or "coupled" to another component, it may include not only a direct connection but also an indirect connection between the two components. Furthermore, when a component "comprises" or "has" other components, this means that other components may be further included without excluding them, unless the context clearly indicates otherwise.

[0036] In this invention, terms such as first, second, etc., are used only for the purpose of distinguishing one component from other components, and the order or importance of components is not limited unless otherwise stated. Accordingly, within the scope of this invention, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0037] In this invention, the distinction between components is intended to clearly describe each of their characteristics, and does not necessarily imply that the components are separate from each other. That is, multiple components may be integrated to form a single hardware or software unit, or a single component may be distributed to form multiple hardware or software units. Accordingly, such integrated or distributed implementations are included within the scope of this invention, even if not specifically mentioned.

[0038] In this invention, the components described in the various embodiments do not necessarily represent essential components, and some of these components may be optional. Accordingly, embodiments comprising a subset of the components described in one embodiment are also included within the scope of this invention. Furthermore, embodiments including other components besides those described in the various embodiments are also included within the scope of this invention.

[0039] In this invention, for ease of description, expressions of positional relationships used herein are provided, such as above, below, left, and right, and the positional relationships described in the specification can be interpreted in reverse when the accompanying drawings shown in the specification are viewed in reverse.

[0040] The following describes a wireless local area network (WLAN) communication system applying embodiments of the present invention. The WLAN communication system applying embodiments of the present invention is not limited to the following description, and the embodiments of the present invention can be applied to various WLAN communication systems. The WLAN communication system may also be referred to as a "wireless local area network" or a "wireless local area network system".

[0041] Figure 1 A block diagram of a communication node in a wireless local area network system is shown.

[0042] refer to Figure 1 Communication node 100 can be an access point (AP), a station (STA), an AP multi-link device (MLD), or a non-AP MLD. STAs can be non-AP STAs. The operating channel width supported by the AP can be 20 MHz, 80 MHz, or 160 MHz, etc. The operating channel width supported by the STA can be 20 MHz or 80 MHz.

[0043] Communication node 100 may include at least one processor 110, memory 120, and at least one transmitting / receiving device 130 connected to a network and performing communication. Transmitting / receiving device 130 may also be referred to as a transceiver, radio frequency (RF) unit, or RF module. Additionally, communication node 100 may further include an input interface device 140, an output interface device 150, and a storage device 160. Components included in communication node 100 can be connected via bus 170 and perform communication between them.

[0044] However, each component included in communication node 100 may be connected not via common bus 170, but via a separate interface or separate bus around processor 110. For example, processor 110 may be connected via a dedicated interface to at least one of memory 120, transmitting / receiving device 130, input interface device 140, output interface device 150, and storage device 160.

[0045] Processor 110 can execute program instructions stored in at least one of memory 120 and storage device 160. Processor 110 can be a central processing unit (CPU), graphics processing unit (GPU), or dedicated processor that performs methods according to embodiments of the present invention. Memory 120 and storage device 160 can each be configured as at least one volatile storage medium and at least one non-volatile storage medium. For example, memory 120 can be configured as at least one read-only memory (ROM) and random access memory (RAM).

[0046] Figure 2 The concept of multiple links set up between multiple link devices (MLDs) in a wireless local area network system is illustrated.

[0047] refer to Figure 2 An MLD can have a medium access control (MAC) address. In an implementation, the MLD can be an AP MLD and / or a non-AP MLD. The MAC address of the MLD can be used in the multi-link establishment process between the non-AP MLD and the AP MLD. The MAC address of the AP MLD can be different from the MAC address of the non-AP MLD. APs associated with an AP MLD can have different MAC addresses, and STAs associated with a non-AP MLD can have different MAC addresses. An AP existing in an AP MLD and having a different MAC address can be responsible for the corresponding link and act as an independent AP.

[0048] A STA residing in a non-AP MLD and having a different MAC address can be responsible for the corresponding link and act as an independent STA. A non-AP MLD can be referred to as a STA MLD. An MLD can support simultaneous transmit and receive (STR) operations. In this case, the MLD can perform transmit operations on link 1 and receive operations on link 2. An MLD supporting STR operations can be referred to as a STR MLD (e.g., a STR AP MLD or a STR non-AP MLD). In implementations, a link can be a channel or a frequency band. A device that does not support STR operations can be referred to as a non-STR (NSTR) AP MLD or an NSTR non-AP MLD (or an NSTR STA MLD).

[0049] MLDs can utilize discontinuous bandwidth extension schemes (e.g., 80 MHz + 80 MHz) to send and receive frames on multiple links. Multi-link operation can include multi-band transmission. An AP MLD can include multiple APs, and these APs can operate on different links. Each AP can perform lower-level MAC layer functions. Each AP can be referred to as a "communication node" or a "lower-level entity." A communication node (i.e., an AP) can be configured according to the upper layer (or...) Figure 1 The processor 110 shown is operated under the control of the processor. A non-AP MLD may include multiple STAs, and these STAs may operate on different links. Each STA may be referred to as a "communication node" or a "lower-level entity." A communication node (e.g., an STA) can operate according to the control of an upper layer (or...). Figure 1 The processor 110 shown is operated under its control.

[0050] MLDs can perform communication across multiple frequency bands. For example, an MLD can perform communication using a 40 MHz bandwidth in the 2.4 GHz band, and a 160 MHz bandwidth in the 5 GHz band, depending on a channel extension scheme (e.g., a bandwidth extension scheme). An MLD can also perform communication using a 160 MHz bandwidth in the 5 GHz band and a 160 MHz bandwidth in the 6 GHz band. A single frequency band (e.g., a single channel) used by an MLD can be defined as a single link. Alternatively, multiple links can be configured within a single frequency band used by an MLD. For example, an MLD can configure one link in the 2.4 GHz band and two links in the 6 GHz band. The links can be referred to as Link 1, Link 2, and Link 3, respectively. Alternatively, the links can be referred to as Link 1, Link 2, and Link 3, respectively. Link numbers can be set by the AP, and an identifier (ID) can be assigned to each link.

[0051] A Multi-Link Ledger (MLD) (e.g., an AP MLD and / or a non-AP MLD) can configure multiple links by executing access and / or negotiation procedures for multi-link operation. In this case, the number of links and / or the links to be used among the multiple links can be configured. A non-AP MLD (e.g., a STA) can identify information about the frequency bands that can communicate with the AP MLD. During the multi-link operation negotiation procedure between the non-AP MLD and the AP MLD, the non-AP MLD can configure one or more links supported by the AP MLD for multi-link operation. A STA that does not support multi-link operation (e.g., a STA according to IEEE 802.11 a / b / g / n / ac / ax) can access one or more links supported by the AP MLD.

[0052] When the frequency band gaps between multiple links (e.g., the frequency band gap between link 1 and link 2 in the frequency domain) are sufficient, the MLD can perform STR operations. For example, the MLD can use link 1 to transmit Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) 1 and can use link 2 to receive PPDU 2. On the other hand, when the frequency band gaps between multiple links are insufficient and the MLD performs STR operations, in-device coexistence (IDC) interference may occur, that is, interference between multiple links. Accordingly, when the frequency band gaps between multiple links are insufficient, the MLD may not be able to perform STR operations. The link pairs in the above interference relationship can be link pairs restricted to non-simultaneous transmit and receive (NSTR). Here, the MLD can be an NSTR AP MLD or an NSTR non-AP MLD.

[0053] For example, multiple links, including Link 1, Link 2, and Link 3, can be set up between the AP MLD and the non-AP MLD 1. When the band gap between Link 1 and Link 3 is sufficient, the AP MLD can perform STR operations using Link 1 and Link 3. That is, the AP MLD can use Link 1 to send frames and use Link 3 to receive frames. When the band gap between Link 1 and Link 2 is insufficient, the AP MLD may not be able to perform STR operations using Link 1 and Link 2. When the band gap between Link 2 and Link 3 is insufficient, the AP MLD may not be able to perform STR operations using Link 2 and Link 3.

[0054] On the other hand, in a wireless LAN system, a negotiation process for multi-link operation can be performed during the access process between the STA and the AP.

[0055] A device that supports multiple links (e.g., an AP or a STA) can be called a multi-link device (MLD). An AP that supports multiple links can be called an AP MLD, and an STA that supports multiple links can be called a non-AP MLD or a STA MLD. An AP MLD can have a physical address (e.g., a MAC address) for each link. An AP MLD can be implemented as if an AP were independently responsible for each link. Multiple APs can be managed within a single AP MLD. Accordingly, coordination can be performed between multiple APs belonging to the same AP MLD. A STA MLD can have a physical address (e.g., a MAC address) for each link. A STA MLD can be implemented as if an STA were independently responsible for each link. Multiple STAs can be managed within a single STA MLD. Accordingly, coordination can be performed between multiple STAs belonging to the same STA MLD.

[0056] For example, AP 1 of the AP MLD and STA 1 of the STA MLD can each be responsible for the first link and perform communication using the first link. AP 2 of the AP MLD and STA 2 of the STA MLD can each be responsible for the second link and perform communication using the second link. STA 2 can receive state change information for the first link on the second link. In this case, STAMLD can collect information received from each link (e.g., state change information) and control the operations performed by STA 1 based on the collected information.

[0057] Next, methods for transmitting and receiving data in a wireless local area network system will be described. When a method (e.g., signal transmission or reception) performed at a first communication node is described, a corresponding second communication node can perform a method (e.g., signal reception or transmission) corresponding to the method performed at the first communication node. That is, when the operation of a STA is described, its corresponding AP can perform an operation corresponding to the STA's operation. On the other hand, when the operation of an AP is described, its corresponding STA can perform an operation corresponding to the AP's operation. In the implementation, the operation of a STA can be interpreted as the operation of a STA MLD, the operation of a STA MLD can be interpreted as the operation of a STA, the operation of an AP can be interpreted as the operation of an AP MLD, and the operation of an AP MLD can be interpreted as the operation of an AP.

[0058] Figure 3 A first implementation of a request-based low-latency transmission method in a wireless local area network system is shown.

[0059] refer to Figure 3AP 1 101 and STA 1 103 can operate in a wireless LAN system. AP 1 101 can perform a channel access procedure. The channel access procedure can be an enhanced distributed channel access (EDCA) backoff operation per access category (AC). AP 1 101 acquires a TXOP when the EDCA backoff counter of the EDCA function (EDCAF) of each AC reaches 0 and the EDCAF of each AC determines to transmit. Here, TXOP is the time interval during which data can be transmitted on the accessed channel without contention. The acquired TXOP can be referred to as the original TXOP. AP 1 101 is the TXOP holder of the original TXOP. Within the original TXOP, AP 1 101 can transmit at least one frame (e.g., physical layer protocol data unit (PPDU), media access control layer protocol data unit (MPDU), and aggregated MPDU (A-MPDU)). STA 1 103 can receive downlink frame 300 from AP 1 101. In response to downlink frame 300, STA 1 103 can send a Block Ack (BA) frame 302 to AP 1 101. STA 1 103 can hold frames (or data) that need to be transmitted quickly. STA 1 103 can include TXOP sharing request information in the BA frame 302. Through the TXOP sharing request information, STA 1 103 can be allocated resources within the original TXOP of AP 1 101. The TXOP sharing request information may include at least one of the following: TXOP request information, delay limit information, information about the size of the requested resource, and information about whether to perform P2P communication. The TXOP sharing request information indicates that the STA (e.g., STA 1 103 transmitting the TXOP sharing request) wishes to share the TXOP of the TXOP holder (e.g., AP 1 101). The delay limit information indicates until the STA (e.g., STA 1 103) wishes to share the TXOP from the TXOP holder. For example, when a STA (e.g., STA 1 103) specifies a delay limit of 1 ms, this indicates that the STA (e.g., STA 1 103) wants to share the TXOP from the TXOP holder within 1 ms. When a STA specifies a delay limit of 1 ms, the STA can hold the data frame that needs to be transmitted within 1 ms.In other words, frames requiring rapid transmission may exist in the STA's queue. Delay limit information may further include per-AC or per-TID time information. For example, the STA may indicate delay limit information for each AC, such as 1 ms for AC_VO and 5 ms for AC_BE. Alternatively, the STA may indicate delay limit information for each TID, such as 1 ms for TID 1 and 3 ms for TID 3. Indications for delay limit information for each AC and for each TID can be used concurrently. Information regarding the size of the requested resource may indicate the size of the resource that the STA (e.g., STA 1 103) wishes to share. For example, the size of the resource may be indicated by time information. In another approach, the size of the resource may be indicated by information about the size of the data to be transmitted. Information regarding whether to perform P2P communication may indicate whether the STA (e.g., STA 1 103) wishes to perform P2P communication. The TXOP sharing request information can be included not only in BA frames 302, but also in every type of frame sent by STA 1 103 to AP 1 101. The TXOP sharing request information can be included in the form of the A-control field within the MAC header of a QoS empty frame in frames sent by STA 1 103 to AP 1 101 (e.g., BA frames). For example, BA frames and QoS empty frames can be formed as an A-MPDU. In another approach, the TXOP sharing request information can be included in frames sent by STA 1 103 to AP 1 101 in the form of indicator bits, subfields, information elements, or other forms.

[0060] When AP 1 101 receives a TXOP sharing request message from STA 1 103, it can transmit a multi-user request to send (MU-RTS) TXOP sharing (TXS) frame 304 after a short inter-frame space (SIFS) period following the completion time of receiving the frame containing the TXOP sharing request message (e.g., BA frame 302). MU-RTS TXS frame 304 is a trigger frame. MU-RTS TXS frame 304 can be transmitted via broadcast. That is, the receiver address indicated in the MAC header of the MU-RTS TXS frame is the broadcast address. The user information subfield of MU-RTS TXS frame 304 can indicate the association ID (AID) of STA 1 103. The AID of STA 1 103 indicated in the user information subfield indicates that STA 1 103 will share the TXOP. MU-RTS TXS frame 304 can indicate the length of the TXOP shared by AP 1 101 and STA 1 103. MU-RTS TXS frame 304 can indicate TXS mode 1, enabling STA 1 103 to perform communication with AP 1 101, and TXS mode 2, enabling STA 1 103 to perform P2P communication and communication with AP 1 101. The information included in MU-RTS TXS frame 304 can be set based on the TXOP sharing request information sent by STA 1 103 to AP 1 101. AP 1 101 can share the TXOP with STA 1 103 based on the transmission of MU-RTS TXS frame 304. Such a shared TXOP is called a "shared TXOP". A shared TXOP is a time interval within the original TXOP during which a device that is not the TXOP holder can send data without contention. For example, STA 1 103 can send data within the shared TXOP. Within a shared TXOP, STA 1 103 may send data only to AP 1 101 or, according to TXS mode, to AP 1 101 and / or other STAs. When the shared TXOP terminates, AP 1 101 may send frames to STA 1 103 and / or other STAs within the remaining segments of the original TXOP. A shared TXOP may also be referred to as the allocated time or allocated duration in a MU-RTS TXS frame.

[0061] In another method, when STA 1 103 sends a TXOP sharing request message to AP 1 101, AP 1 101 may refrain from transmission for a duration corresponding to the information indicated by STA 1 103 regarding the size of the requested resource, instead of performing a TXOP sharing operation (e.g., a TXOP sharing operation via the transmission of MU-RTS TXS frame 304). STA 1 103 may perform P2P communication within AP 1 101's TXOP. Alternatively, STA 1 103 may perform non-802.11 communication within AP 1 101's TXOP. When the P2P or non-802.11 communication of STA 1 103 ends, AP 1 101 may transmit additional frames within the remaining TXOP.

[0062] Figure 4 A second implementation of a request-based low-latency transmission method in a wireless local area network system is shown.

[0063] refer to Figure 4AP 1 101 and STA 1 103 are operable. AP 1 101 can perform channel access procedures. Channel access procedures can be, for example, per-AC EDCA backoff operations. AP 1 101 acquires a TXOP when the EDCA backoff counter of the per-AC EDCA function (EDCAF) reaches 0 and the per-AC EDCAF determines transmission. The TXOP acquired by AP 1 101 can be referred to as the original TXOP. AP 1 101 is the TXOP holder of the original TXOP. Within the original TXOP, AP 1 101 can transmit multiple frames (e.g., PPDU, MPDU, and A-MPDU). STA 1 103 can receive downlink frame 400 from AP 1 101. In response to downlink frame 400, STA 1 103 can send a Block Ack (BA) frame 402 to AP 1 101. STA 1 103 can hold frames (or data) that require fast transmission. BA frame 402 transmitted by STA 1 103 may include TXOP sharing request information. Through the TXOP sharing request information, STA 1 103 can be allocated resources within the original TXOP of AP 1 101. The TXOP sharing request information may include at least one of the following: TXOP request information, delay limit information, information about the size of the requested resource, and information about whether P2P communication is performed. The TXOP sharing request information indicates that the STA (e.g., STA 1 103 transmitting the TXOP sharing request) wishes to share the TXOP of the TXOP holder (e.g., AP 1 101). The delay limit information indicates until the STA (e.g., STA 1 103) wishes to share the TXOP from the TXOP holder. For example, when the delay limit information is specified as 1 ms, the delay limit information indicates that the STA (e.g., STA 1 103) wishes to share the TXOP from the TXOP holder within 1 ms. The delay limit information may further include per AC or per TID time information. For example, delay limit information can indicate the TXOP sharing time for each AC, such as 1 ms for AC_VO and 5 ms for AC_BE. Alternatively, delay limit information can indicate the TXOP sharing time for each TID, such as 1 ms for TID 1 and 3 ms for TID 3. Indications for delay limit information for each AC and for each TID can be used concurrently. Information about the size of the requested resource can indicate the size of the resource that the STA (e.g., STA 1 103) wishes to share. For example, the size of the resource can indicate the time information that the STA (e.g., STA 1 103) wishes to share. In another approach, the size of the resource can indicate information about the size of the data to be transmitted.Information regarding whether to perform P2P communication can indicate to the STA (e.g., STA 1 103) whether it wishes to perform P2P communication. The TXOP share request information can be included not only in BA frame 402, but also in every type of frame sent by STA 1 103 to AP 1 101. The TXOP share request information can be included in the form of an A-control within the MAC header of a QoS empty frame in a frame sent by STA 1 103 to AP 1 101 (e.g., BA frame 402). For example, BA frames and QoS empty frames can be formed as an A-MPDU. In another approach, the TXOP share request information can be included in the frame sent by STA 1 103 to AP 1 101 in the form of indicator bits, subfields, information elements, or other forms.

[0064] When AP 1 101 receives a TXOP sharing request message from STA 1 103, it may send a data frame 404 to STA 1 103 after the SIFS period following the completion time of receiving the frame containing the TXOP sharing request message (e.g., BA frame 402). Data frame 404 may include, for example, a QoS empty frame. Data frame 404 may include information regarding AP 1 101's response to STA 1 103's TXOP sharing request. This information may include acceptance or rejection of STA 1 103's TXOP sharing request. This information may be included in the form of an A-control statement in the MAC header of data frame 404. In another approach, the information regarding the response to the TXOP sharing request may be included in the frame sent by AP 1 101 to STA 1 103 in the form of indicator bits, subfields, information elements, or other forms. When AP 1 101 accepts STA 1 103's TXOP sharing request, AP 1 101 can indicate acceptance of STA 1 103's request in the information regarding the response to the TXOP sharing request. After AP 1 101 sends data frame 404 to STA 1 103 and receives BA frame 406 from STA 1 103, AP 1 101 can transmit MU-RTS TXS frame 408. MU-RTS TXS frame 408 is a trigger frame. MU-RTS TXS frame 408 can be transmitted via broadcast. That is, the receiver address indicated in the MAC header of the MU-RTS TXS frame is the broadcast address. The user information subfield of MU-RTS TXS frame 408 can indicate the AID of STA 1 103. The AID of STA 1 103 indicated in the user information subfield indicates that STA 1 103 will share the TXOP. MU-RTS TXS frame 408 can indicate the length of the TXOP shared by AP 1 101 and STA 1 103. MU-RTS TXS frame 408 can indicate TXS mode 1, which allows STA 1 103 to perform communication with AP 1 101, and TXS mode 2, which allows STA 1 103 to perform P2P communication and communication with AP 1 101. The information included in MU-RTS TXS frame 408 can be set based on the TXOP sharing request information sent by STA 1 103 to AP 1 101. AP 1 101 can share the TXOP with STA 1 103 based on the transmission of MU-RTS TXS frame 408. Such a shared TXOP is called a "shared TXOP". Within the shared TXOP, STA 1 103 can perform only transmissions to AP 1 101, or, depending on the TXS mode, perform transmissions to AP 1 101 and / or other STAs.When the shared TXOP terminates, AP 1 101 may send frames to STA 1 103 and / or other STAs within the remaining segments of the original TXOP. The shared TXOP may also be referred to as the allocated time or allocated duration in the MU-RTS TXS frame.

[0065] In another method, when STA 1 103 sends a TXOP sharing request message to AP 1 101, AP 1 101 may refrain from transmission for a duration corresponding to the information indicated by STA 1 103 regarding the size of the requested resource, instead of performing a TXOP sharing operation (e.g., a TXOP sharing operation transmitted via MU-RTS TXS frame 408). STA 1 103 may perform P2P communication within AP 1 101's TXOP. Alternatively, STA 1 103 may perform non-802.11 communication within AP 1 101's TXOP. When STA 1 103's P2P communication or non-802.11 communication ends, AP 1 101 may transmit additional frames within the remaining TXOP.

[0066] Figure 5 A third implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0067] refer to Figure 5AP 1 101 and STA 1 103 can operate in a wireless LAN channel. AP 1 101 can perform a channel access procedure. The channel access procedure can be a per-AC EDCA backoff operation. When the EDCA backoff counter of the per-AC EDCA function (EDCAF) reaches 0 and the per-AC EDCAF determines transmission, AP 1 101 acquires a TXOP. The acquired TXOP can be referred to as the original TXOP. AP 1 101 is the TXOP holder of the original TXOP. Within the original TXOP, AP 1 101 can transmit multiple frames (e.g., PPDU, MPDU, and A-MPDU). Multiple frames 500 can be transmitted consecutively using XIFS. XIFS can be shorter than or equal to SIFS. Alternatively, XIFS can be a longer space than SIFS (e.g., PIFS). Between XIFS, STA 1 103 can send frames 500 to AP 1 101. STA 1 103 can receive downlink frame 500 from AP 1 101. STA 1 103 can hold frames (or data) that require fast transmission. STA 1 103 can transmit frame 502, including TXOP sharing request information, between XIFS frames transmitted by AP 1 101. STA 1 103 can be allocated resources within the original TXOP of AP 1 101 by utilizing the TXOP sharing request information. The TXOP sharing request information may include at least one of the following: TXOP request information, delay limit information, information about the size of the requested resource, and information about whether P2P communication is performed. The TXOP sharing request information indicates that the STA (e.g., STA 1 103, which transmits the TXOP sharing request) wishes to share the TXOP of the TXOP holder (e.g., AP 1 101). The delay limit information indicates until the STA (e.g., STA 1 103) needs to share the TXOP from the TXOP holder. For example, when an STA (e.g., STA 1 103) specifies a delay limit of 1 ms, the delay limit indicates that the STA (e.g., STA 1 103) wishes to share the TXOP from the TXOP holder within 1 ms. The delay limit information may further include per-AC or per-TID time information. For example, the STA (e.g., STA 1 103) may indicate delay limit information for each AC, such as 1 ms for AC_VO and 5 ms for AC_BE. Alternatively, the STA may indicate delay limit information for each TID, such as 1 ms for TID 1 and 3 ms for TID 3. Indications for delay limit information for each AC and for each TID can be used concurrently.

[0068] Information about the size of the requested resource can indicate the size of the resource that the STA (e.g., STA 1 103) wishes to share. For example, information about the size of the resource can indicate the time information that the STA (e.g., STA 1 103) wishes to share. In another approach, information about the size of the resource can indicate information about the size of the data to be transmitted. Information about whether to perform P2P communication can indicate whether the STA (e.g., STA 1 103) wishes to perform P2P communication. The TXOP sharing request information can also be included in each type of frame sent by STA 1 103 to AP 1 101. The TXOP sharing request information can be included in the frame sent by STA 1 103 to AP 1 101 in the form of an A-control within the MAC header of a QoS empty frame. For example, BA frames and QoS empty frames can be formed as an A-MPDU. In another approach, the TXOP sharing request information can be included in the frame sent by STA 1 103 to AP 1 101 in the form of an indication bit, subfield, information element, or other forms.

[0069] When AP 1 101 receives a TXOP sharing request message from STA 1 103, it may transmit a MU-RTS TXS frame 504 after the SIFS period following the completion time of receiving the frame 502 containing the TXOP sharing request message. The MU-RTS TXS frame 504 is a trigger frame. The MU-RTS TXS frame 504 can be transmitted via broadcast. That is, the receiver address indicated in the MAC header of the MU-RTS TXS frame is the broadcast address. The user information subfield of the MU-RTS TXS frame 504 may indicate the AID of STA 1 103. The AID of STA 1 103 indicated in the user information subfield indicates that STA 1 103 will share the TXOP. The MU-RTS TXS frame 504 may indicate the length of the TXOP shared by AP 1 101 and STA 1 103. MU-RTS TXS frame 504 can indicate that STA1 103 can perform TXS mode 1 for communication with AP1 101 and TXS mode 2 for P2P communication with AP1 101. The information included in MU-RTS TXS frame 504 can be set based on the TXOP sharing request information sent by STA1 103 to AP1 101. AP1 101 can share a TXOP with STA1 103 based on the transmission of MU-RTS TXS frame 504. This shared TXOP is referred to as a "shared TXOP". Within the shared TXOP, STA1 103 can perform only transmissions to AP1 101, or, depending on the TXS mode, transmissions to AP1 101 and / or other STAs. When the shared TXOP terminates, AP1 101 can send frames to STA1 103 and / or other STAs within the remaining segments of the original TXOP. The shared TXOP can also be referred to as the allocated time or allocated duration in a MU-RTS TXS frame.

[0070] In another method, when STA 1 103 sends a TXOP sharing request message to AP 1 101, AP 1 101 may refrain from transmission for a duration corresponding to the information indicated by STA 1 103 regarding the size of the requested resource, instead of performing a TXOP sharing operation (e.g., a TXOP sharing operation via the transmission of MU-RTS TXS frame 504). STA 1 103 may perform P2P communication within AP 1 101's TXOP. Alternatively, STA 1 103 may perform non-802.11 communication within AP 1 101's TXOP. When the P2P or non-802.11 communication of STA 1 103 ends, AP 1 101 may transmit additional frames within the remaining TXOP.

[0071] Figure 6 A fourth implementation of a request-based low-latency communication method in a wireless local area network system is shown.

[0072] refer to Figure 6AP 1 101 and STA 1 103 are operable. AP 1 101 can perform a channel access procedure. The channel access procedure can be a per-AC EDCA backoff operation. When the EDCA backoff counter of the per-AC EDCA function (EDCAF) reaches 0 and the per-AC EDCAF determines transmission, AP 1 101 acquires a TXOP. The acquired TXOP can be referred to as the original TXOP. AP 1 101 is the TXOP holder of the original TXOP. Within the original TXOP, AP 1 101 can transmit multiple frames (e.g., PPDU, MPDU, and A-MPDU). Multiple frames 600 can be transmitted consecutively using XIFS. XIFS can be shorter than or equal to SIFS. Alternatively, XIFS can be a longer space than SIFS (e.g., PIFS). Between XIFS, STA 1 103 can send frames 600 to AP 1 101. STA 1 103 can receive downlink frames 600 from AP 1 101. STA 1 103 may hold frames (or data) that require rapid transmission. STA 1 103 may transmit frame 602, including TXOP sharing request information, between XIFS frames transmitted by AP 1 101. Through the TXOP sharing request information, STA 1 103 may be allocated resources within the original TXOP of AP 1 101. The TXOP sharing request information may include at least one of the following: TXOP request information, delay limit information, information about the size of the requested resource, and information about whether P2P communication is performed. The TXOP sharing request information indicates that the STA (e.g., STA 1 103 transmitting the TXOP sharing request) wishes to share the TXOP of the TXOP holder (e.g., AP 1 101). The delay limit information indicates until the STA (e.g., STA 1 103) needs to share the TXOP from the TXOP holder. For example, when the delay limit information is 1 ms, the delay limit information indicates that the STA (e.g., STA 1 103) wishes to share the TXOP from the TXOP holder within 1 ms. When a STA specifies a delay limit of 1 ms, the STA can hold data frames that need to be transmitted within 1 ms. That is, frames requiring rapid transmission may exist in the STA's queue. The delay limit information may further include per-AC or per-TID time information. For example, the delay limit information may indicate time information for each AC, such as 1 ms for AC_VO and 5 ms for AC_BE. Alternatively, the delay limit information may indicate time information for each TID, such as 1 ms for TID 1 and 3 ms for TID 3. Indications for delay limit information for each AC and for each TID can be used concurrently.Information regarding the size of the requested resource indicates the size of the resource that the STA (e.g., STA 1 103) wishes to share. For example, the size of the resource can be indicated by time information. In another approach, the size of the resource can be indicated by information about the size of the data to be transmitted. Information regarding whether P2P communication is to be performed can indicate whether the STA (e.g., STA 1 103) wishes to perform P2P communication. The TXOP sharing request information can also be included in each type of frame sent by STA 1 103 to AP 1 101. The TXOP sharing request information can be included in the frame sent by STA 1 103 to AP 1 101 in the form of an A-control within the MAC header of a QoS empty frame. For example, BA frames and QoS empty frames can be formed as an A-MPDU. In another approach, the TXOP sharing request information can be included in the frame sent by STA 1 103 to AP 1 101 in the form of indicator bits, subfields, information elements, or other forms.

[0073] When AP 1 101 receives a TXOP sharing request message from STA 1 103, it may send a data frame 604 to STA 1 103 after the SIFS period following the completion time of receiving the frame 602 containing the TXOP sharing request message. Data frame 604 may include a QoS empty frame. For example, a BA frame and a QoS empty frame may be formed as an A-MPDU. Data frame 604 may include information regarding the response to the TXOP sharing request. This information includes AP 1 101's response to STA 1 103's TXOP sharing request. This information includes information regarding acceptance or rejection of STA 1 103's TXOP sharing request. This information regarding the response to the TXOP sharing request may be included in the form of an A-control in the MAC header of data frame 604. In another approach, the information regarding the response to the TXOP sharing request may be included in the frame sent by AP 1 101 to STA 1 103 in the form of indicator bits, subfields, information elements, or other forms. When AP 1101 accepts STA 1103's TXOP sharing request, AP 1101 may indicate acceptance of STA 1103's request in the information regarding the response to the TXOP sharing request. After AP 1101 sends data frame 604 to STA 1103, AP 1101 may transmit MU-RTS TXS frame 606. MU-RTS TXS frame 606 is a trigger frame. MU-RTS TXS frame 606 may be transmitted via broadcast. The user information subfield of MU-RTS TXS frame 606 may indicate the AID of STA 1103. The AID of STA 1103 indicated in the user information subfield indicates that STA 1103 will share the TXOP. MU-RTS TXS frame 606 may indicate the length of the TXOP shared by AP 1101 and STA 1103. MU-RTS TXS frame 606 may include TXS mode information. The TXS mode information indicates that STA 1 103 can perform TXS mode 1 for communication with AP 1 101, and TXS mode 2 for P2P communication with AP 1 101. Information included in the MU-RTS TXS frame 606 can be set based on the TXOP sharing request information sent by STA 1 103 to AP 1 101. AP 1 101 can share the TXOP with STA 1 103 based on the transmission of MU-RTS TXS frame 606. This shared TXOP is referred to as a "shared TXOP". Within the shared TXOP, STA 1 103 can send data only to AP 1 101 or send data to AP 1 101 and / or other STAs according to the TXS mode.When the shared TXOP terminates, AP 1 101 may send frames to STA 1 103 and / or other STAs within the remaining segments of the original TXOP. The shared TXOP may also be referred to as the allocated time or allocated duration in the MU-RTS TXS frame.

[0074] In another method, when STA 1 103 sends a TXOP sharing request message to AP 1 101, AP 1 101 may refrain from transmission for a duration corresponding to the information indicated by STA 1 103 regarding the size of the requested resource, instead of performing a TXOP sharing operation (e.g., a TXOP sharing operation transmitted via MU-RTS TXS frame 606). STA 1 103 may perform P2P communication within AP 1 101's TXOP. Alternatively, STA 1 103 may perform non-802.11 communication within AP 1 101's TXOP. When STA 1 103's P2P communication or non-802.11 communication ends, AP 1 101 may transmit additional frames within the remaining TXOP.

[0075] Figure 7 A method for operating a first device according to an embodiment of the present invention is illustrated. The first device may be, for example, a STA. The first device may be a STA holding at least one data and frame that needs to be transmitted quickly. Figure 7 An example of operating the first device (e.g., Figure 3 STA 1 103 or Figure 6 The method of STA 1 103).

[0076] refer to Figure 7 In step S701, the first device receives from the second device (e.g., Figure 3 AP 1 101 or Figure 6 AP 1101 receives downlink data. The downlink data may, for example, be included in the first frame (e.g., ...). Figure 3 downlink frame 300 or Figure 6 In the downlink frame 300, the second device is the TXOP holder. The first frame is a frame sent from the second device to the first device. Downlink data can be received at each predetermined time interval (i.e., XIFS). The predetermined time interval can be shorter than or equal to the SIFS time interval. As another example, the predetermined time interval can be shorter than or equal to the SIFS time interval. As yet another example, the predetermined time interval can be equal to the PIFS time interval.

[0077] In step S703, the first device sends a TXOP sharing request message to the second device. The TXOP sharing request message is information transmitted by the first device to share the TXOP from the second device. The TXOP sharing request message may be included in the second frame (e.g., Figure 3 BA frame 302 or Figure 6 The second frame is a frame sent from the first device to the second device. The second frame may include one of a data frame (e.g., PPDU, MPDU, or A-MPDU) and a control frame (e.g., BA frame).

[0078] The TXOP sharing request information can be transmitted after downlink data is received from the second device. For example, TXOP sharing information can be transmitted in response to downlink data received from the second device. Alternatively, the TXOP sharing information can be transmitted before a predetermined time interval has elapsed after downlink data transmission. In other words, the TXOP sharing information can be transmitted after downlink data reception is complete, before a duration equal to XIFS has elapsed.

[0079] The TXOP sharing request information includes at least one of the following: TXOP request information, delay limit information, information about the size of the requested resource, and information about whether to perform P2P communication. The TXOP request information indicates that the first device wishes to share a TXOP from a TXOP holder. The delay limit information indicates the time at which the first device wishes to share the TXOP from the TXOP holder. In other words, the delay limit information indicates the start time of TXOP sharing. For example, when the delay limit information has a value of 1 ms, it indicates that the STA wishes to share the TXOP before a duration of 1 ms elapses after the STA transmits a frame. The delay limit information may indicate the expected time for TXOP sharing for each AC or each TID. Alternatively, the delay limit information may indicate the expected time for TXOP sharing for both each AC and each TID. The information about the size of the requested resource indicates the size of the resource that the first device wishes to share. Here, the size of the resource may be expressed, for example, as its size in the time domain. Alternatively, the size of the resource may be expressed as the size of the data that the first device wishes to transmit. The information about whether to perform P2P communication indicates whether the first device intends to perform P2P communication.

[0080] TXOP share request information can take various forms and can be included in the second frame. For example, TXOP share request information can be one of the following forms: A-control, indicator bits, subfields, information elements, etc., and can be included in the second frame.

[0081] In step S705, the first device receives from the second device at least one piece of information regarding the response to the TXOP sharing request and information related to the shared TXOP. The information regarding the response to the TXOP sharing request and at least one piece of information related to the shared TXOP may be included, for example, in a third frame (e.g., Figure 3 MU-RTS TXS frame 304 Figure 6 In data frame 604 and / or MU-RTS TXS frame 606. At least one third frame can be at least one of a data frame (e.g., a QoS empty frame) and a trigger frame (e.g., a MU-RTS TXS frame).

[0082] Information regarding the response to a TXOP share request includes information indicating whether the TXOP share request is accepted or rejected. This information can take various forms and can be included in the third frame. For example, the information regarding the response to a TXOP share request can be one of the following forms: A-control, indicator bits, subfields, information elements, or others, and can be included in the third frame.

[0083] Information associated with the shared TXOP may include information indicating the TXS mode and length of the shared TXOP. The first device may perform transmissions based on the TXS mode. For example, when the information associated with the shared TXOP indicates TXS mode 1, the first device may perform transmissions only to the second device. Alternatively, when the information associated with the shared TXOP indicates TXS mode 2, the first device may perform transmissions to both the second device and the STA.

[0084] According to an embodiment of the invention, information regarding the response to a TXOP share request may be included in the data frame (e.g., Figure 6 In data frame 604). According to another embodiment of the invention, information related to the shared TXOP may be included in the trigger frame (e.g., Figure 3 MU-RTS TXS frame 304 or Figure 6 In MU-RTS TXS frame 606).

[0085] In step S707, the first device obtains a shared TXOP and transmits uplink data using the obtained shared TXOP. For example, the first device may transmit uplink data within the shared TXOP time interval. For example, the transmitted uplink data may be in the form of wireless LAN communication (e.g., at least one of data frames and control frames). For example, the uplink data may be included in a fourth frame. Alternatively, the transmitted uplink data may be in the form of data used for non-wireless LAN communication (e.g., P2P communication or Bluetooth).

[0086] Uplink and downlink data can include user information and control information. User information can be included in data frames. Control information can be included in control frames.

[0087] Figure 8 A method for operating a second device according to an embodiment of the present invention is shown. The second device may be, for example, an AP. Figure 8 An example of operating the second device (e.g., Figure 3 AP 1 101 or Figure 6 The method of AP 1 101.

[0088] refer to Figure 8 In step S801, the second device executes a channel access procedure. This channel access procedure can be, for example, an EDCA backoff procedure. When the channel access procedure is successful (e.g., the EDCA backoff counter reaches 0), the second device acquires the TXOP. In other words, when the channel access procedure is successful, the second device operates as the TXOP holder.

[0089] In step S803, the second device sends downlink data to the first device. The downlink data may, for example, be included in the first frame (e.g., Figure 3 downlink frame 300 or Figure 6 The downlink frame 300). The first frame includes a control frame and a data frame. The second device can send data to the first device (e.g., ...). Figure 3 STA 1 103 or Figure 6 STA 1 (103) sends at least one downlink data transmission. The downlink data can be transmitted at XIFS intervals. XIFS can be shorter than or equal to, for example, SIFS intervals. Alternatively, XIFS can be longer than SIFS intervals.

[0090] In step S805, the second device receives TXOP sharing request information from the first device. The TXOP sharing request information may be included, for example, in the second frame (e.g., Figure 3The second frame may include at least one of a data frame (e.g., PPDU, MPDU, or A-MPDU) and a control frame (e.g., a BA frame). The TXOP share request information can take various forms and may be included in the second frame. For example, the TXOP share request information may be one of A-control, indicator bits, subfields, information elements, or other forms, and may be included in the second frame.

[0091] In step S807, the second device sends at least one piece of information to the first device regarding the response to the TXOP sharing request and information related to the shared TXOP. The information regarding the response to the TXOP sharing request and at least one piece of information related to the shared TXOP may be included in a third frame (e.g., Figure 3 MU-RTS TXS frame 304 or Figure 6 In the MU-RTS TXS frame 606. At least one third frame can be at least one of a data frame (e.g., a QoS empty frame) and a trigger frame (e.g., a MU-RTS TXS frame). The second device generates and transmits information about the response to the TXOP sharing request based on the TXOP sharing request information transmitted by the first device.

[0092] Information regarding the response to a TXOP share request includes information indicating acceptance or rejection of the TXOP share request. This information can take various forms and may be included in a third frame. For example, the information regarding the response to a TXOP share request may be one of the following forms: A-control, indicator bits, subfields, information elements, etc., and may be included in a third frame. The second device generates and transmits information regarding the response to the TXOP share request based on the TXOP share request information transmitted by the first device. For example, the second device may generate information regarding the response to the TXOP share request that includes information indicating acceptance of the TXOP share request based on the TXOP share request information transmitted by the first device. Alternatively, the second device may generate information regarding the response to the TXOP share request that includes information indicating rejection of the TXOP share request based on the TXOP share request information transmitted by the first device.

[0093] Information associated with the shared TXOP may include information indicating the TXS mode and length of the shared TXOP. The TXS mode indicates the method by which the first device performs the transmission. For example, the TXS mode indicates the sending target device of the first device. For instance, when the information associated with the shared TXOP indicates TXS mode 1, the first device may perform a transmission only to the second device. Alternatively, when the information associated with the shared TXOP indicates TXS mode 2, the first device may perform a transmission to both the second device and the STA. The length of the shared TXOP indicates the duration of the TXOP shared between the second device and the first device. The length of the shared TXOP is shorter than the length of the TXOP obtained by the second device.

[0094] According to an embodiment of the invention, information regarding the response to a TXOP sharing request may be included in a data frame. According to another embodiment of the invention, information related to the shared TXOP may be included in a trigger frame.

[0095] The second device can transmit, for example, information about the response to the TXOP sharing request and information related to the shared TXOP at intervals of 11FS, starting from the time the TXOP sharing request information is received. When transmitting the TXOP sharing request information and the information related to the shared TXOP, the TXOP sharing request information and the information related to the shared TXOP are transmitted at intervals of 11FS.

[0096] Uplink and downlink data can include user information and control information. User information can be included in data frames. Control information can be included in control frames.

[0097] Although the exemplary method of the present invention is presented as a series of operations for clarity of description, it is not intended to limit the order of the steps to be performed, and the steps may be performed simultaneously or in different orders if desired. To implement the method according to the invention, other steps may be included in addition to those shown, or some steps may be excluded while including the remaining steps, or additional steps may be included while excluding some steps.

[0098] The various embodiments of the present invention do not list all possible combinations, but are intended to describe representative aspects of the invention, and the matters described in the various embodiments may be applied independently or in combination of two or more.

[0099] Furthermore, various embodiments of the present invention can be implemented by hardware, firmware, software, or a combination thereof. In the case of hardware implementation, it can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, etc.

[0100] The scope of the invention also includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause the operation of methods according to various embodiments to be performed on an apparatus or computer, and non-volatile computer-readable media that store such software or instructions and make them executable on an apparatus or computer.

[0101] Industrial availability This disclosure can be used in devices and recording media in wireless local area network systems.

Claims

1. A method for operating a first device in a wireless local area network system, the method comprising: Downlink data is received from a second device holding a transmission opportunity (TXOP), the transmission opportunity (TXOP) comprising a time interval allocated for transmitting data in the absence of contention; Send the first message requesting the sharing of TXOP to the second device; Receive second information from the second device regarding a shared TXOP, including a portion of the time interval within the TXOP; as well as Uplink data is sent using the shared TXOP.

2. The method according to claim 1, wherein, The uplink data includes at least one of control information and user information.

3. The method according to claim 1, wherein, The first information includes at least one of information indicating the start time of the sharing and information indicating the size of the shared resource.

4. The method according to claim 3, wherein, The information indicating the start time of sharing includes: information indicating the start time of sharing for at least one of each Access Category (AC) and each Service Indicator (TID).

5. The method according to claim 3, wherein, The size of the shared resources includes the size of the data or the duration of the data.

6. The method according to claim 1, wherein, Receiving the second information includes receiving a trigger frame that includes the second information.

7. The method of claim 1, further comprising: Receive third information in response to the first information from the second device.

8. The method according to claim 1, wherein, The second information includes at least one of the size of the shared TXOP and the transmission mode information of the first device.

9. The method according to claim 8, wherein, The transmission mode information includes information related to the transmission target device of the first device.

10. A method for operating a second device in a wireless local area network system, the method comprising: Execute the channel access procedure; Based on the success of the channel access procedure, a transmission opportunity (TXOP) is obtained, including a time interval allocated for transmitting data without contention. Send downlink data; Receive first information requesting TXOP sharing from the first device; as well as Send second information to the first device about a shared TXOP that includes a portion of the time interval within the TXOP.

11. The method of claim 10, further comprising: Uplink data is received from the first device by utilizing the shared TXOP. The uplink data includes at least one of control information and user information.

12. The method according to claim 10, wherein, The first information includes at least one of information indicating the start time of the sharing and information indicating the size of the shared resource.

13. The method according to claim 12, wherein, The information indicating the start time of sharing includes: information indicating the start time of sharing for at least one of each Access Category (AC) and each Service Indicator (TID).

14. The method according to claim 12, wherein, The size of the resource includes the size of the data or the duration of the time.

15. The method according to claim 10, wherein, Sending the second message includes: Send a trigger frame that includes the second information.

16. The method of claim 10, further comprising: Receive third information in response to the first information from the second device.

17. The method according to claim 10, wherein, The second information includes at least one of the transmission mode information of the first device.

18. The method according to claim 17, wherein, The transmission mode information includes information related to the transmission target device of the first device.

19. A first device in a wireless local area network system, the first device comprising: transceiver; and The processor, which is connected to the transceiver, The processor controls the transceiver to: Downlink data is received from a second device holding a transmission opportunity (TXOP), the TXOP comprising a time interval for transmitting data in the absence of contention. Send the first message requesting TXOP sharing to the second device. Receive information from the second device about the shared TXOP, including a portion of the time interval within the TXOP; as well as Uplink data is sent using the shared TXOP.

20. A second device in a wireless local area network system, the second device comprising: transceiver; and The processor, which is connected to the transceiver, The processor is configured as follows: Execute the channel access procedure, and Based on the success of the channel access procedure, a transmission opportunity (TXOP) is obtained, including a time interval for transmitting downlink data in the absence of contention; and Control the transceiver to: Send downlink data, Receive the first information requesting TXOP sharing from the first device, and Send second information to the first device about a shared TXOP that includes a portion of the time interval within the TXOP.

Images