Method and apparatus for TXOP sharing for multiple users in wireless LAN system

Abstract

The disclosure relates to transmission opportunity (TXOP) sharing for multiple users in a wireless local area network (LAN) system. According to an embodiment of the present disclosure, a method performed by means of a station (STA) in a wireless LAN system comprises the steps of: receiving a TXOP sharing (TXS) trigger frame including a plurality of user information fields, each user information field in the plurality of user information fields indicates a corresponding allocation period in a plurality of allocation periods among TXOP periods related to the TXS trigger frame; identifying one or more allocation periods of the STA based on one or more user information fields for the STA among the plurality of user information fields; determining a start time of a first allocation period among the one or more allocation periods based on order information and / or a basic trigger frame; and transmitting data in the first allocation period after the start time.

Description

Technical Field

[0001] This disclosure relates to the sharing of transmission opportunity (TXOP) for multiple users in a wireless LAN system. Background Technology

[0002] Wireless local area networks (WLANs) have been improved in various ways. For example, the IEEE 802.11 ax standard proposed an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multiple user multiple input multiple output (DLMU MIMO) technologies.

[0003] This disclosure proposes technical features that can be utilized in new communication standards. For example, the new communication standard could be the Extremely High Throughput (EHT) standard currently under discussion. The EHT standard could utilize newly proposed increased bandwidth, improved PHY layer Protocol Data Unit (PPDU) structures, improved sequencing, and Hybrid Automatic Repeat Request (HARQ) techniques. The EHT standard could also be referred to as the IEEE 802.11 be standard.

[0004] In wireless LAN systems, TXOP sharing can be supported. During TXOP sharing, the scheduled STA can i) send to the associated AP, and / or ii) send to another STA. TXOP sharing can be supported for both single users and multiple users. Summary of the Invention

[0005] Technical issues

[0006] One aspect of this disclosure is to provide a method and apparatus for multi-user TXOP sharing in a wireless LAN system.

[0007] Technical solution

[0008] According to embodiments of this disclosure, a method performed by a station (STA) in a wireless local area network (LAN) system includes: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a basic trigger frame; and transmitting data during the first allocated duration after the start time.

[0009] According to embodiments of this disclosure, a station (STA) in a wireless local area network (LAN) system includes: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, wherein the memory stores instructions that perform operations based on execution by the at least one processor, the operations including: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a basic trigger frame; and transmitting data during the first allocated duration after the start time.

[0010] According to embodiments of this disclosure, an apparatus configured to operate in a wireless local area network (LAN) system includes: at least one processor; and at least one memory operatively coupled to the at least one processor, wherein the at least one memory stores instructions that perform operations based on execution by the at least one processor, the operations including: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one user information field of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a basic trigger frame; and transmitting data during the first allocated duration after the start time.

[0011] According to embodiments of the present disclosure, a non-transitory computer-readable medium (CRM) stores program code implementing instructions that perform operations based on execution by at least one processor, the operations including: receiving a Transmission Opportunity (TXOP) Share (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a basic trigger frame; and transmitting data during the first allocated duration after the start time.

[0012] According to embodiments of this disclosure, an access point (AP) in a wireless local area network (LAN) system includes: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, wherein the memory stores instructions that perform operations based on execution by the at least one processor, the operations including: obtaining a transmission opportunity (TXOP); configuring a user information list field of a TXOP sharing (TXS) trigger frame associated with the TXOP, wherein the user information list field includes a plurality of user information list fields, and each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within the duration of the TXOP; and transmitting the TXS trigger frame, wherein the plurality of user information fields includes at least one user information field for the STA indicating at least one allocated duration of the STA, and wherein the start time of a first allocated duration among the at least one allocated duration is determined based on sequence information or at least one of a basic trigger frame.

[0013] According to embodiments of this disclosure, a method performed by an access point (AP) in a wireless local area network (LAN) system includes: obtaining a transmission opportunity (TXOP); configuring a user information list field of a TXOP sharing (TXS) trigger frame associated with the TXOP, wherein the user information list field includes a plurality of user information list fields, and each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within the duration of the TXOP; and transmitting the TXS trigger frame, wherein the plurality of user information fields include at least one user information field for the STA indicating at least one allocated duration of the STA, and wherein a start time of a first allocated duration among the at least one allocated duration is determined based on sequence information or at least one of a basic trigger frame.

[0014] Beneficial effects

[0015] This disclosure can have various beneficial effects.

[0016] For example, the methods for configuring user information fields and for multiple allocation instructions and sequence instructions in this disclosure can be easily designed from a multi-user perspective. Furthermore, in a single-user triggered TXOP sharing protocol / process, if each STA needs a large number of P2P transmissions within a period exceeding the maximum allocation duration that can be allocated from the AP, the AP must obtain a new TXOP duration through media contention. However, the multi-triggered TXOP sharing method of this disclosure allows STAs to perform and complete P2P transmissions for relatively long periods within a single TXOP duration.

[0017] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, various technical effects can exist that can be understood and / or obtained by those skilled in the art from this disclosure. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but can include various effects that can be understood or obtained from the technical features of this disclosure. Attached Figure Description

[0018] Figure 1 Examples of transmitting and / or receiving devices of this disclosure are shown.

[0019] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0020] Figure 3 The diagram illustrates the typical link establishment process.

[0021] Figure 4 An example of multi-link (ML) is shown.

[0022] Figure 5 Examples of Physical Protocol Data Units or Physical Layer (PHY) Protocol Data Units (PPDUs) transmitted / received by the STA of this disclosure are shown.

[0023] Figure 6 The layout of a resource unit (RU) for a 20 MHz PPDU is illustrated.

[0024] Figure 7 The layout of a resource unit (RU) for a 40 MHz PPDU is illustrated.

[0025] Figure 8 The layout of a resource unit (RU) for an 80 MHz PPDU is illustrated.

[0026] Figure 9 The operation related to UL-MU is shown.

[0027] Figure 10 The illustration shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0028] Figure 11 The illustration shows an example of a channel used / supported / defined within the 5 GHz band.

[0029] Figure 12 The illustration shows an example of channels used, supported, and defined within the 6 GHz band.

[0030] Figure 13 Examples of modifications to the transmitting and / or receiving apparatus of this disclosure are shown.

[0031] Figure 14 An example of a process related to RTS / CTS transmission is shown.

[0032] Figure 15 An example of the value of the TXOP shared schema subfield is shown.

[0033] Figure 16 An example of the operation is shown when the TXOP shared schema subfield has a value of 2.

[0034] Figure 17 An example of the user information field format of MU-RTS TXS TF is shown.

[0035] Figure 18 An example of a method for multi-trigger TXOP sharing performed by a STA according to an embodiment of this disclosure is shown.

[0036] Figure 19An example of signal flow between an AP and a STA for multi-trigger TXOP sharing is shown according to an embodiment of this disclosure.

[0037] Figure 20 A first example of the configuration of a user information field according to an embodiment of this disclosure is shown.

[0038] Figure 21 A second example of the configuration of a user information field according to an embodiment of this disclosure is shown.

[0039] Figure 22 A first example of operation of multi-trigger TXOP sharing according to an embodiment of this disclosure is shown.

[0040] Figure 23 A second example of operation of multi-trigger TXOP sharing according to an embodiment of this disclosure is shown.

[0041] Figure 24 A third example of operation of multi-trigger TXOP sharing according to an embodiment of this disclosure is shown.

[0042] Figure 25 An example of a TXOP allocation method according to an embodiment of this disclosure is shown.

[0043] Figure 26 An example of the configuration of a user information field for priority allocation of short TXOP duration according to an embodiment of this disclosure is shown.

[0044] Figure 27 An example of the operation of prioritizing the allocation of short TXOP durations according to an embodiment of this disclosure is shown.

[0045] Figure 28 An example is shown of allocating TXOP durations to STAs with different power sensitivities during a multi-user triggered TXOP sharing process according to an embodiment of the present disclosure.

[0046] Figure 29 An example of a user information field format considering power sensitivity according to an embodiment of this disclosure is shown.

[0047] Figure 30 An example of the operation of prioritizing the allocation of TXOP duration considering power sensitivity according to an embodiment of this disclosure is shown. Detailed Implementation

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

[0049] The forward slash ( / ) or comma used in this disclosure can represent "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0050] In this disclosure, "at least one of A and B" can mean "only A", "only B" or "both A and B". Additionally, in this disclosure, the expression "at least one of A or B" or "at least one of A and / or B" can be interpreted as "at least one of A and B".

[0051] The brackets used in this disclosure may indicate "for example". Specifically, when indicated as "control information (UHR-signal field)", it may indicate that the "UHR-signal field" is cited as an example of "control information". In other words, the "control information" of this disclosure is not limited to the "UHR-signal field", and the "UHR-signal field" may also be cited as an example of "control information". Furthermore, when indicated as "control information (i.e., UHR-signal field)", it may also indicate that the "UHR-signal field" is cited as an example of "control information".

[0052] Furthermore, as used in this disclosure, "a" can mean "at least one" or "one or more". Additionally, terms ending in "(s)" can mean "at least one" or "one or more".

[0053] Furthermore, as used in this disclosure, the expressions “based on”, “on the basis of”, or “according to” mean “at least partially based on”, and not “based on only”.

[0054] The technical features described individually in one of the accompanying drawings of this disclosure may be implemented individually or simultaneously.

[0055] The following examples of this disclosure can be applied to various wireless communication systems. For example, the following examples of this disclosure can be applied to wireless local area network (WLAN) systems. For example, this disclosure can be applied to the IEEE 802.11 a / g / n / ac / ax / be / bn standards. Furthermore, the examples of this disclosure can also be applied to next-generation wireless LAN standards such as enhanced Ultra High Reliability (UHR) standards or IEEE 802.11 bn. Additionally, the examples of this disclosure can be applied to new WLAN standards enhanced from EHT standards or IEEE 802.11be standards. Furthermore, the examples of this disclosure can be applied to mobile communication systems. For example, it can be applied to mobile communication systems based on Long Term Evolution (LTE), which relies on 3GPP standards and is based on LTE evolution. Furthermore, the examples of this disclosure can be applied to communication systems based on the 5G NR standard of 3GPP standards.

[0056] In the following text, for the purpose of describing the technical features of this disclosure, technical features applicable to this disclosure will be described.

[0057] Figure 1 Examples of transmitting and / or receiving devices of this disclosure are shown.

[0058] exist Figure 1 In the example, the various technical features described below can be implemented. Figure 1 At least one station (STA) is involved. For example, STA 110 and 120 of this disclosure may also be referred to by various terms such as mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or simply user. STA 110 and 120 of this disclosure may also be referred to by various terms such as network, base station, Node B, access point (AP), repeater, router, relay, etc. STA 110 and 120 of this disclosure may also be referred to by various names such as receiving device, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

[0059] For example, STA 110 and 120 can be used as AP or non-AP. That is, STA 110 and 120 of this disclosure can be used as AP and / or non-AP. In this disclosure, AP can be indicated as AP STA.

[0060] In addition to the IEEE 802.11 standard, the STAs 110 and 120 of this disclosure can together support various communication standards. For example, they can support communication standards based on 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). Furthermore, the STAs of this disclosure can be implemented in various devices such as mobile phones, vehicles, and personal computers. Additionally, the STAs of this disclosure can support communication for various communication services such as voice calls, video calls, data communication, and autonomous driving.

[0061] The STA 110 and 120 disclosed herein may include media access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for radio media.

[0062] The following will refer to Figure 1 The subgraph (a) is used to describe STA 110 and 120.

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

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

[0065] For example, the first STA 110 can perform the operations expected by the AP. For example, the AP's processor 111 can receive signals via transceiver 113, process receive (RX) signals, generate transmit (TX) signals, and provide control over signal transmission. The AP's memory 112 can store signals received via transceiver 113 (e.g., RX signals) and can store signals to be transmitted via transceiver 113 (e.g., TX signals).

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

[0067] For example, a non-AP STA processor 121 can receive signals via transceiver 123, process RX signals, generate TX signals, and provide control over signal transmission. A non-AP STA memory 122 can store signals received via transceiver 123 (e.g., RX signals) and can store signals to be transmitted via transceiver 123 (e.g., TX signals).

[0068] For example, the operation of a device designated as an AP in the disclosure described below can be performed in either the first STA 110 or the second STA 120. For instance, if the first STA 110 is an AP, the operation of the device designated as an AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 112 of the first STA 110. Similarly, if the second STA 120 is an AP, the operation of the device designated as an AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Furthermore, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 122 of the second STA 120.

[0069] For example, in the disclosure described below, the operation of a device indicated as a non-AP (or user STA) can be performed in either the first STA 110 or the second STA 120. For instance, if the second STA 120 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 122 of the second STA 120. Similarly, if the first STA 110 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 112 of the first STA 110.

[0070] In the disclosure described below, devices referred to as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving apparatus), network, etc., may implicitly refer to Figure 1 STAs 110 and 120. For example, devices indicated as (but without specific labels) (transmitting / receiving) STA, First STA, Second STA, STA1, STA2, AP, First AP, Second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) device, network, etc., can be implied. Figure 1 STAs 110 and 120. For example, in the following example, the operation of various STA transmit / receive signals (e.g., PPDU) can be... Figure 1 The operation is performed in transceivers 113 and 123. Additionally, in the following examples, various STAs can generate TX / RX signals or perform data processing and calculations on TX / RX signals in advance. Figure 1 The operations are executed in processors 111 and 121. Examples of operations for generating TX / RX signals or performing prior data processing and calculations may include: 1) operations to determine / obtain / configure / calculate / decode / encode bit information of subfields (SIG, STF, LTF, data) included in the PPDU; 2) operations to determine / configure / obtain time resources or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, data) included in the PPDU; 3) operations to determine / configure / obtain specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the subfields (SIG, STF, LTF, data) included in the PPDU; 4) power control operations and / or power-saving operations applied to the STA; and 5) operations related to the determination / obtaining / configuration / decoding / encoding of the ACK signal. Additionally, in the following examples, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs to determine / obtain / configure / calculate / decode / decode the TX / RX signal may be stored in the STA's memory. Figure 1 In memory 112 and 122.

[0071] Figure 1 The aforementioned device / STA in subgraph (a) can be as follows Figure 1 The subgraph (b) is modified as shown below. In the following text, the modifications will be based on... Figure 1 The subgraph (b) is used to describe STA 110 and STA 120 of this disclosure.

[0072] For example, Figure 1The transceivers 113 and 123 shown in subgraph (b) can perform operations with Figure 1 The transceiver shown in sub-diagram (a) has the same function as the aforementioned transceiver. For example, Figure 1 The processing chips 114 and 124 shown in sub-figure (b) may include processors 111 and 121 and memories 112 and 122. Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (b) can perform operations related to Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (a) have the same functions.

[0073] The mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, user STA, network, base station, node B, access point (AP), repeater, router, relay, receiving unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving device and / or transmitting device described below may mean Figure 1 The STA 110 and 120 shown in subgraphs (a) / (b) may mean, or Figure 1 The processing chips 114 and 124 are shown in sub-figure (b). That is, the technical features of this disclosure can be... Figure 1 It can be performed in STA 110 and 120 as shown in subgraphs (a) / (b), or it can be performed only in Figure 1 The processing chips 114 and 124 shown in sub-diagram (b) are executed Figure 1 Transceivers 113 and 123 are shown in sub-diagrams (a) and (b). For example, the technical features of transmitting control signals by a STA can be understood as being achieved through... Figure 1 The transceiver 113 shown in sub-diagrams (a) / (b) transmits in Figure 1 The technical features of the control signals generated in processors 111 and 121 are illustrated in sub-figures (a) and (b). Alternatively, the technical features of the STA transmitting control signals can be understood as follows: Figure 1 The technical features of generating control signals to be transmitted to transceivers 113 and 123 in processing chips 114 and 124 are shown in sub-figure (b).

[0074] For example, the technical characteristics of receiving STA control signals can be understood as through... Figure 1 The technical features of transceivers 113 and 123 receiving control signals are shown in sub-figure (a). Alternatively, the technical features of receiving STA control signals can be understood as being achieved through... Figure 1 Processors 111 and 121 shown in subgraph (a) obtain Figure 1The technical features of the control signals received in transceivers 113 and 123 shown in sub-figure (a) are illustrated. Alternatively, the technical features of receiving control signals by the STA can be understood as being achieved through... Figure 1 The processing chips 114 and 124 shown in sub-figure (b) obtain Figure 1 Technical features of the control signals received in transceivers 113 and 123 as shown in sub-figure (b).

[0075] refer to Figure 1 Subgraph (b), software codes 115 and 125 can be included in memories 112 and 122. Software codes 115 and 125 can include instructions for controlling the operation of processors 111 and 121. Software codes 115 and 125 can be included in various programming languages.

[0076] Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include at least one of the following: a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, Figure 1 The processors 111 and 121 or the processor chips 114 and 124 may be SNAPDRAGON™ series processors manufactured by Qualcomm®, EXYNOS™ series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIO™ series processors manufactured by MediaTek®, ATOM™ series processors manufactured by Intel®, or processors enhanced from these processors.

[0077] In this disclosure, an uplink can mean a link used for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc., can be transmitted via the uplink. Similarly, in this disclosure, a downlink can mean a link used for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc., can be transmitted via the downlink.

[0078] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0079] Figure 2 The upper part of the diagram illustrates the structure of the Infrastructure Basic Services Set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0080] refer to Figure 2 The upper part of the wireless LAN system may include one or more infrastructure BSS 200 and 205 (hereinafter referred to as BSS). BSS 200 and 205, as a set of APs and STAs (e.g., access point (AP) 225 and station (STA1) 200-1) that have successfully synchronized to communicate with each other, are not concepts indicating a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that can join an AP 230.

[0081] A BSS may include at least one STA, an AP that provides distributed services, and a distributed system (DS) 210 that connects multiple APs.

[0082] Distributed system 210 can implement an Extended Service Set (ESS) 240 that is expanded by connecting multiple BSSs 200 and 205. ESS 240 can be used as a term to refer to a network configured by connecting one or more APs 225 or 230 via distributed system 210. APs included in an ESS 240 can have the same Service Set Identifier (SSID).

[0083] Portal 220 can be used as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0084] exist Figure 2 The BSS shown at the top allows for networking between APs 225 and 230, as well as between APs 225 and 230 and STAs 200-1, 205-1, and 205-2. However, it also allows for networking between STAs to perform communication even without APs 225 and 230. Networks that enable communication between STAs by configuring networks even without APs 225 and 230 are defined as self-organizing networks or Independent Basic Service Sets (IBSS).

[0085] Figure 2 The lower part of the diagram shows a concept map, illustrating IBSS.

[0086] refer to Figure 2The lower part of the IBSS is a BSS that operates in a self-organizing mode. Since the IBSS does not include access points (APs), there is no centralized management entity performing management functions at the center. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 can be composed of mobile STAs, and access to DS to form a self-contained network is not permitted.

[0087] Figure 3 The diagram illustrates the typical link establishment process.

[0088] In S310, the STA can perform network discovery operations. Network discovery operations can include scanning operations by the STA. That is, in order to access a network, the STA needs to discover participating networks. The process of identifying compatible networks before joining a wireless network and identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0089] Figure 3 The diagram illustrates the network discovery process in active scanning. In active scanning, the STA performing the scan sends a probe request frame and waits for a response to it, in order to identify which APs are nearby while moving to a new channel. The responder sends a probe response frame to the STA that sent the probe request frame as a response. Here, the responder can be the STA in the BSS of the channel being scanned that sent the last beacon frame. In the BSS, the AP is the responder because it sends the beacon frame. In the IBSS, the responder is not fixed because the STAs in the IBSS take turns sending beacon frames. For example, when an STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA can store the BSS-related information included in the received probe response frame, move to the next channel (e.g., channel 2), and perform a scan in the same way (e.g., sending a probe request and receiving a probe response via channel 2).

[0090] Although Figure 3As not shown, scanning can be performed using a passive scanning method. In passive scanning, the STA performing the scan can wait for beacon frames while moving to a channel. Beacon frames are one of the management frames in IEEE 802.11 and are periodically sent to indicate the presence of a wireless network and enable the STA performing the scan to find and join the wireless network. In a BSS, the AP periodically sends beacon frames. In an IBSS, STAs in the IBSS take turns sending beacon frames. Upon receiving a beacon frame, the STA performing the scan stores information about the BSS included in the beacon frame and records the beacon frame information for each channel, while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, can move to the next channel, and can perform a scan on the next channel using the same method.

[0091] After network discovery, the STA can perform authentication processing in S320. This authentication processing can be referred to as the first authentication processing to clearly distinguish it from the subsequent security establishment operation in S340. The authentication processing in S320 may include the STA sending an authentication request frame to the AP and the AP sending an authentication response frame to the STA in response. The authentication frame used for the authentication request / response is a management frame.

[0092] An authentication frame may include information about the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and finite cyclic group.

[0093] The STA can send an authentication request frame to the AP. The AP can determine whether to allow the STA's authentication based on the information included in the received authentication request frame. The AP can then provide the authentication processing result to the STA via an authentication response frame.

[0094] When a STA is successfully authenticated, it can perform association processing in S330. Association processing includes the STA sending an association request frame to the AP, and the AP responding by sending an association response frame to the STA. For example, the association request frame may include information about various capabilities, beacon listening interval, service set identifier (SSID), supported rates, supported channels, RSN, mobile domain, supported operation classes, service indication map (TIM) broadcast request, and interoperability service capabilities. Similarly, the association response frame may include information about various capabilities, status codes, association ID (AID), supported rates, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal-to-noise ratio indicator (RSNI), mobile domain, timeout interval (association recovery time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

[0095] In the S340, the STA can perform security establishment processes. The security establishment processes in the S340 may include the process of establishing a private key via a four-way handshake (e.g., via Extensible Authentication Protocol (EAPOL) frames over the LAN).

[0096] Figure 4 An example of multi-link (ML) is shown.

[0097] like Figure 4 As illustrated, multiple multi-link devices (MLDs) can communicate via a remote link. MLDs can be classified as AP MLDs, which include multiple AP STAs, and non-AP MLDs, which include multiple non-AP STAs. That is, an AP MLD may include affiliated APs (i.e., AP STAs), and a non-AP MLD may include affiliated STAs (i.e., non-AP STAs or user STAs).

[0098] A multi-link system may include a first link and a second link, and different channel / subchannel / frequency resources may be allocated to the first link and the second link. The first and second multi-link systems can be identified by a 4-bit (or other n-bit) link ID. The first and second links can be configured in the same 2.4 GHz, 5 GHz, or 6 GHz frequency band. Alternatively, the first and second links can be configured in different frequency bands.

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

[0100] exist Figure 4 In the example, AP1 can initiate the multi-link establishment process (ML establishment process) by sending an association request frame to a non-AP STA1. Figure 4 In the example, a non-AP STA1 can send an association response frame in response to an association request frame. Figure 4 The individual APs shown (e.g., AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The APs shown are the same, and Figure 4 The various non-APs shown (e.g., non-AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The STAs shown are the same (i.e., user STAs or non-AP STAs).

[0101] The specific features of this disclosure are not limited to Figure 4 The specific characteristics are as follows. That is, the number of links can be defined in various ways, and multiple links can be defined in at least one frequency band in various ways.

[0102] Figure 5 Examples of Physical Protocol Data Units or Physical Layer (PHY) Protocol Data Units (PPDUs) transmitted / received by the STA of this disclosure are shown.

[0103] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) disclosed herein can send and / or receive. Figure 5 The PPDU described in this disclosure may have, for example... Figure 5 The structure is as follows. Furthermore, the PPDU described in this disclosure may be referred to by various names, such as transmit PPDU, receive PPDU, type 1 or type N PPDU, etc. The PPDU described in this disclosure can be used in WLAN systems defined according to IEEE 802.11bn and / or in next-generation WLAN systems that improve upon IEEE 802.11bn.

[0104] Figure 5 The PPDU can encompass various PPDU types used in UHR systems. For example, Figure 5 Examples can be used for at least one of the following modes related to channel detection: single-user (SU) mode / type / transmission, multi-user (MU) mode / type / transmission, and null packet (NDP) mode / type / transmission. For example, if Figure 5 If the example involves NDP, the data fields shown can be omitted. Figure 5 The PPDU is used in trigger-based (TB) mode and can be omitted. Figure 6 The UHR-SIG. In other words, a STA that has received a trigger frame for uplink-MU (UL-MU) communication can send a UHR-SIG. Figure 5 The UHR-SIG PPDU is omitted in the example.

[0105] exist Figure 5In this context, L-STF or UHR-LTF can be referred to as a preamble or physical preamble, and can be generated / transmitted / received / acquired / decoded at the physical layer (including in the transmit / receive STA).

[0106] Figure 5 The blocks shown in the diagram can be referred to as fields / subfields / signals, etc. These fields / subfields / signals can be named as Traditional Short Training Field (L-STF), Traditional Long Training Field (L-LTF), Traditional Signal (L-SIG), Repeated L-SIG (RL-SIG), Universal Signal (U-SIG), UHR Signal (UHR-SIG), etc. Figure 5 As shown in the diagram.

[0107] Figure 5 The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be determined to be 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be represented in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be represented in units of 78.125 kHz.

[0108] exist Figure 5 In the PPDU, the L-LTF and L-STF can be the same as those in the conventional domain (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0109] Figure 5The L-SIG field can include, for example, 24 bits of bit information. For instance, the 24 bits could include a 4-bit rate field, a 1-bit reserved bit, a 12-bit length field, a 1-bit parity bit, and a 6-bit tail bit. For example, the 12-bit length field could include information related to the length or duration of the PPDU. For example, the 12-bit length field can be determined based on the type of PPDU. For example, when the PPDU is a Non-High Throughput (HT), High Throughput (HT), Very High Throughput (VHT) PPDU, Extremely High Throughput (EHT) PPDU, or UHR PPDU, the value of the length field can be determined to be a multiple of 3. For example, when the PPDU is an HE PPDU, the length field can be determined to be a multiple of 3 + 1 or a multiple of 3 + 2. In other words, for non-HT, HT, VHT, EHT, or UHR PPDUs, the length field value can be set to a multiple of 3, and for high-efficiency (HE) PPDUs, the length field value can be set to either a multiple of 3 + 1 or a multiple of 3 + 2. In other words, the LENGTH field in a UHR PPDU is set to a value that satisfies the condition that LENGTH divided by 3 leaves a remainder of 0.

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

[0111] For example, a (non-AP and AP) STA can generate an RL-SIG in the same way as the L-SIG. BPSK modulation can be applied to the RL-SIG. Based on the presence of the RL-SIG, the (non-AP and AP) STA can know that the RX PPDU is an HE PPDU, EHT PPDU, or UHR PPDU. In other words, if the RL-SIG is present, the receiving (non-AP and AP) STA can know that the received PPDU is one of an HE PPDU, EHT PPDU, or UHR PPDU. In other words, if the RL-SIG is not present, the receiving (non-AP and AP) STA can know that the received PPDU is one of a non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repetition of the L-SIG field and is used to distinguish UHR PPDUs from non-HT PPDUs, HT PPDUs, and VHT PPDUs.

[0112] Universal SIG (U-SIG) can be inserted in Figure 6 Following RL-SIG, U-SIG can be referred to by various terms such as First SIG Field, First SIG, First Type SIG, Control Signal, Control Signal Field, First (Type) Control Signal, Common Control Field, Common Control Field, etc.

[0113] U-SIG can include N bits of information and may include information to identify the type of EHT PPDU. For example, U-SIG can be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol used for U-SIG (e.g., an OFDM symbol) can have a duration of 4 μs. Each symbol of U-SIG can be used to transmit 26 bits of information. For example, each symbol of U-SIG can be transmitted / received based on 52 data tones and 4 pilot tones.

[0114] Through U-SIG, for example, A bits of information (e.g., 52 uncoded bits) can be transmitted. The first symbol of U-SIG can transmit the first X bits of the A bits of information (e.g., 26 uncoded bits), and the second symbol of U-SIG can transmit the remaining Y bits of the A bits of information (e.g., 26 uncoded bits). For example, the transmitting STA can obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional coding (i.e., BCC coding) based on a rate of R=1 / 2 to generate 52 coded bits, and can perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols to be assigned to each U-SIG symbol. A U-SIG symbol can be transmitted based on 65 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, except for DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) other than the pilot tone, namely tones -21, -7, +7, and +21.

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

[0116] The A-bit information (e.g., 52 uncoded bits) sent by U-SIG (or the U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, version-independent bits can have a fixed or variable size. For example, version-independent bits can be assigned only to the first symbol of U-SIG, or version-independent bits can be assigned to both the first and second symbols of U-SIG. For example, version-independent bits and version-dependent bits can be referred to using various terms such as first control bit, second control bit, etc.

[0117] For example, the version-independent bits of the U-SIG can include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier can include information related to the PHY version of the TX / RX PPDU. For example, the first value of the 3-bit PHY version identifier (e.g., a value of 000) can indicate that the TX / RX PPDU is an EHT PPDU. Furthermore, the second value of the 3-bit PHY version identifier (e.g., a value of 001) can indicate that the TX / RX PPDU is a UHR PPDU.

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

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

[0120] For example, the version-independent bits of U-SIG can include information related to the transmission opportunity (TXOP) length and information related to the BSS color ID.

[0121] For example, if the UHR PPDU is classified into various types (e.g., types related to SU transmission (based on UL or DL), types related to DL transmission, types related to NDP transmission, types related to DL non-MU-MIMO, types related to DL MU-MIMO, types related to multi-AP operation, types related to Co-BF beamforming (Co-BF), spatial reuse (SR), types related to Co-OFDMA (C-OFDMA), and types related to Co-TDMA (Co-TDMA), then information about the type of UHR PPDU (e.g., 2-bit or 3-bit information) can be included in the version-related bits of the U-SIG.

[0122] For example, U-SIG may include: 1) a bandwidth field including information related to bandwidth; 2) a field including information related to the modulation and demodulation scheme (MCS) applied to UHR-SIG; 3) an indication field including information related to whether a dual subcarrier modulation (DCM) scheme is applied to UHR-SIG; 4) a field including information related to the number of symbols used for UHR-SIG; 5) a field including information related to whether UHR-SIG is generated across the entire frequency band; 6) a field including information related to the type of UHR-LTF / STF; and 7) information related to fields indicating the length of UHR-LTF and the length of CP.

[0123] Can be Figure 5 The PPDU uses preamble puncturing. Preamble puncturing means that a puncture is applied to a portion of the full frequency band (e.g., the secondary 20 MHz band). For example, when transmitting an 80 MHz PPDU, the STA can apply puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0124] For example, the pattern for the preamble punch can be pre-configured. For example, when applying the first punch pattern, punching can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when applying the second punch pattern, punching can be applied only to any one of the two secondary 20 MHz bands within the secondary 40 MHz band included in the 80 MHz band. For example, when applying the third punch pattern, punching can be applied only to the secondary 20 MHz band within the primary 80 MHz band included in the 160 MHz band (or 80+80 MHz band). For example, when applying the fourth punch pattern, punching can be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band, provided that the primary 40 MHz band within the 80 MHz band included in the 160 MHz band (or 80+80 MHz band) is present.

[0125] Information related to the prelead puncturing applied to the PPDU can be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information related to continuous bandwidth, and the second field of the U-SIG may include information related to the prelead puncturing applied to the PPDU.

[0126] For example, based on the following method, U-SIG and UHR-SIG can include information related to pre-lead puncture. When the bandwidth of the PPDU exceeds 80 MHz, U-SIG can be configured individually in 80 MHz units. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU can include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG can include information related to the 160 MHz bandwidth, and the second field of the first U-SIG can include information related to the pre-lead puncture applied to the first 80 MHz band (i.e., information related to the pre-lead puncture pattern). Additionally, the first field of the second U-SIG can include information related to the 160 MHz bandwidth, and the second field of the second U-SIG can include information related to the pre-lead puncture applied to the second 80 MHz band (i.e., information related to the pre-lead puncture pattern). Meanwhile, the UHR-SIG consecutive with the first U-SIG may include information related to the preleading hole applied to the second 80 MHz band (i.e., information related to the preleading hole pattern), and the UHR-SIG consecutive with the second U-SIG may include information related to the preleading hole applied to the first 80 MHz band (i.e., information related to the preleading hole pattern).

[0127] Additionally or alternatively, U-SIG and UHR-SIG may include information related to the pre-drilled hole, based on the following method: U-SIG may include information related to the pre-drilled hole for all frequency bands (i.e., information related to the pre-drilled hole pattern). That is, UHR-SIG may not include information related to the pre-drilled hole, while only U-SIG may include information related to the pre-drilled hole (i.e., information related to the pre-drilled hole pattern).

[0128] U-SIGs can be configured in 20 MHz units. For example, when an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included in an 80 MHz PPDU. PPDUs with bandwidths exceeding 80 MHz can include different U-SIGs.

[0129] Figure 5 The UHR-SIG can include control information for receiving STAs. The UHR-SIG can be transmitted using at least one symbol, and a symbol can have a length of 4 μs. Information related to the number of symbols used for the UHR-SIG can be included in the U-SIG.

[0130] UHR-SIG provides additional signals to the U-SIG field to enable the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that are typically applied to all users. In addition, the UHR-SIG field includes resource allocation information, allowing the STA to locate resources used in fields including the data field / UHR-STF / UHR-LTF (i.e., the UHR modulation field of the UHR PPDU).

[0131] It can be determined based on the RU (Resource Unit) defined by multiple subcarriers / tones. Figure 5 The diagram illustrates the frequency resources of the UHR-LTF, UHR-STF, and data fields. In other words, the UHR-LTF, UHR-STF, and data fields of this disclosure can be transmitted / received via RUs (Resource Units) defined by multiple subcarriers / tones.

[0132] Figure 6 The diagram illustrates the layout of a resource unit (RU) for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be accessed via... Figure 6 At least one of the various RUs defined in the code is used to send / receive.

[0133] like Figure 6 The topmost diagram shows a configuration that can accommodate 26 units (i.e., units corresponding to 26 tones). Six tones can be used for the leftmost guard band of the 20 MHz band, and five tones can be used for the rightmost guard band of the 20 MHz band. Additionally, seven DC tones can be inserted in the center band (i.e., the DC band), and 26 units corresponding to 13 tones on each of the left and right sides of the DC band can be arranged. Units of 26, 52, and 106 can be allocated to other bands. Individual units can be assigned to receiving STAs (i.e., users).

[0134] Figure 6 The RU layout in the diagram can be used not only for multi-user (MU) but also for single-user (SU). In the single-user case, a 242 unit can be used and three DC tones can be inserted, such as... Figure 6 The bottom part is shown in the diagram.

[0135] Although Figure 6Various sizes of RUs have been proposed, namely 26-RU, 52-RU, 106-RU, and 242-RU, but RUs of a specific size can be expanded or increased. Therefore, this embodiment is not limited to individual RUs of a specific size (i.e., the number of corresponding tones). In this specification, an N-RU can be represented as an N-tone RU, etc. For example, a 26-RU can be represented as a 26-tone RU.

[0136] Figure 7 The layout of a resource unit (RU) for a 40 MHz PPDU is illustrated.

[0137] With the use of RUs of various sizes Figure 6 Similarly, in Figure 7 Examples of frequencies that can be used include 26-RU, 52-RU, 106-RU, 242-RU, and 484-RU. Additionally, five DC tones can be inserted into the center frequency; 12 tones can be used for the leftmost guard band of the 40 MHz band; and 11 tones can be used for the rightmost guard band of the 40 MHz band.

[0138] like Figure 7 As shown, a 484-RU can be used when the RU layout is for a single user. The specific number of RUs can be similar to... Figure 6 Change.

[0139] Figure 8 The diagram illustrates the layout of a resource element (RU) for an 80 MHz PPDU. The layout of the resource element (RU) used in this disclosure can be varied. For example, the layout of the resource element (RU) used in the 80 MHz band can be varied.

[0140] Figure 9 The operation related to the UL-MU is illustrated. As shown, a transmitting STA (e.g., an AP) can obtain TXOP 925 and transmit trigger frame 930 by performing channel access through contention (i.e., backoff operation). That is, the transmitting STA (e.g., an AP) can transmit a PPDU including trigger frame 930. When the PPDU including the trigger frame is received, a trigger-based (TB) PPDU is transmitted after a delay of SIFS.

[0141] TB PPDUs 941 and 942 can be transmitted simultaneously and from multiple STAs (e.g., user STAs) indicated by their AID in trigger frame 930. The ACK frame 950 for the TB PPDU can be implemented in various forms. For example, the ACK frame 950 for the TB PPDU can be implemented as a block ACK (BA).

[0142] exist Figure 9Within TXOP 925, the transmission of trigger frame 930, TB PPDU 941, 942 and / or ACK frame 950 can be performed.

[0143] Figure 10 The figure shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0144] The 2.4 GHz band can also be referred to by other names, such as "first band". Furthermore, the 2.4 GHz band can refer to the frequency range used / supported / defined by channels having a center frequency adjacent to 2.4 GHz (e.g., channels having a center frequency between 2.4 GHz and 2.5 GHz).

[0145] A 2.4 GHz band can include multiple 20 MHz channels. Each 20 MHz channel within the 2.4 GHz band can have multiple channel indices (e.g., indices 1 to 14). For example, the center frequency of channel index 1 for a 20 MHz channel could be 2.412 GHz, the center frequency of channel index 2 for a 20 MHz channel could be 2.417 GHz, and the center frequency of channel index N for a 20 MHz channel could be (2.407 + 0.005 * N) GHz. Channel indices can be referenced by various names such as channel numbers. Specific values ​​for channel indices and center frequencies can be changed.

[0146] Figure 10 Four channels within a 2.4 GHz frequency band are illustrated exemplarily. The first frequency region 1010 to the fourth frequency region 1040 shown may each include one channel. For example, the first frequency region 1010 may include channel 1 (the 20 MHz channel with index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region 1020 may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region 1030 may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region 1040 may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0147] Figure 11 The figure shows an example of a channel used / supported / defined within the 5 GHz band.

[0148] The 5 GHz band can be referred to by other names, such as second band / band, etc. The 5 GHz band can refer to the frequency range that uses / supports / defines channels with a center frequency greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, the 5 GHz band can include multiple channels between 4.5 GHz and 5.5 GHz. Figure 11 The specific values ​​shown may change.

[0149] Multiple channels within the 5 GHz band include the unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as the lower UNII. UNII-2 may include frequency ranges referred to as the middle UNII and the extended UNII-2. UNII-3 may be referred to as the upper UNII.

[0150] Multiple channels can be configured within the 5 GHz band, and the bandwidth of each channel can vary, for example, 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency range can be divided into four channels using a 40 MHz band. The 5170 MHz to 5330 MHz frequency range can be divided into two channels using an 80 MHz band. Alternatively, the 5170 MHz to 5330 MHz frequency range can be divided into one channel using a 160 MHz band.

[0151] Figure 12 The illustration shows an example of channels used, supported, and defined within the 6 GHz band.

[0152] The 6 GHz band can also be referred to by other names, such as the third band. The 6 GHz band can refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, and defined. Figure 12 The specific values ​​shown may vary.

[0153] For example, it can be defined starting from 5.940 GHz. Figure 12 The 20 MHz channel. Specifically, Figure 12 The leftmost channel in the 20 MHz channel can have an index of 1 (or channel index, channel number, etc.) and can be assigned a center frequency of 5.945 GHz. In other words, the center frequency of the index N channel can be determined as (5.940 + 0.005 * N) GHz.

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

[0155] Figure 13 Examples of modifications to the transmitting and / or receiving apparatus of this disclosure are shown.

[0156] It is possible Figure 13 Modifications shown Figures 1 to 4 The device shown (e.g., AP STA, non-AP STA). Figure 13 The transceiver 630 can be used with Figure 1 The transceivers 113 and 123 are the same. Figure 13 The transceiver 630 may include a receiver and a transmitter.

[0157] Figure 13 The processor 610 can be with Figure 1 The processors 111 and 121 are the same. Alternatively, Figure 13 The processor 610 can be with Figure 1 The processing chips 114 and 124 are the same.

[0158] Figure 13 The memory 160 can be connected with Figure 1 The memory modules 112 and 122 are identical. Alternatively, Figure 13 The memory 160 can be different Figure 1 Separate external memories for memories 112 and 122.

[0159] Reference Figure 13The power management module 611 manages the power of the processor 610 and / or transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs the results processed by the processor 610. The keyboard 614 receives input to be used by the processor 610. The keyboard 614 may be displayed on the display 613. The SIM card 616 may be an integrated circuit for securely storing the International Mobile Subscriber Identity (IMSI) and its associated keys, used for identifying and authenticating users in mobile devices such as mobile phones and computers.

[0160] Reference Figure 13 The speaker 640 can output sound-related results processed by the processor 610. The microphone 641 can receive sound-related inputs to be used by the processor 610.

[0161] Figure 14 An example of a process related to RTS / CTS transmission is shown.

[0162] Reference Figure 14 When a source intending to send data (e.g., an AP STA / non-AP STA) sends a Request to Send (RTS) frame to a destination (e.g., an AP STA / non-AP STA) intending to receive data, the destination can send a Clear to Send (CTS) frame to neighboring stations to notify them that it will receive data. In other words, a destination designated as a receiver via an RTS frame can send a CTS frame. If the source sending the RTS frame receives the CTS frame, then the source can initiate data transmission to the destination.

[0163] Meanwhile, if an STA receives an RTS frame other than the destination designated as the receiver via the RTS frame, or if an STA other than the source sending the RTS frame receives a CTS frame, the STA can configure a Network Allocation Vector (NAV). A STA with an NAV configured can refrain from sending data during the NAV period, allowing the STA to avoid collisions with the source / destination. On the other hand, if an RTS frame is received by the destination designated as the receiver via the RTS frame, or if the source sending the RTS frame receives a CTS frame, the source / destination does not configure an NAV.

[0164] If no CTS frame (e.g., the PHY-RXSTART.indication primitive) is received within a certain period starting from the time the RTS frame is received (e.g., the time the MAC receives the PHY-RXEND.indication primitive corresponding to the RTS frame), then a STA that has set or updated the NAV via the RTS frame can reset the NAV (e.g., reset it to 0). A certain period can be (2*aSIFSTime + CTS_Time + aRxPHYStartDelay + 2*aSlotTime). CTS_Time can be calculated based on the length and data rate of the CTS frame indicated by the RTS frame.

[0165] For ease of description, Figure 14 The diagram illustrates setting or updating the NAV via an RTS or CTS frame. However, NAV setting / resetting / updating can also be performed based on the duration field of various other frames, such as non-HT PPDU, HT PPDU, VHT PPDU, or HE PPDU (e.g., the duration field in the MAC header of a MAC frame). For example, if the RA field in a received MAC frame does not match its own address (e.g., MAC address), the STA can set / reset / update the NAV.

[0166] Furthermore, according to the EHT (i.e., 802.11 be) standard, in order to support peer-to-peer (P2P) transmissions to non-AP STAs, the AP can allocate a portion of the duration within the TXOP obtained by the AP. To allocate a portion of the duration within the TXOP, a TXOP sharing mode subfield can be defined within the common information field of the MU-RTS trigger frame. When the value of the TXOP sharing mode subfield is non-zero, such a MU-RTS trigger frame can be called an MU-RTS TXOP sharing (TXS) trigger frame (TF).

[0167] Figure 15 An example of the value of the TXOP shared schema subfield is shown.

[0168] Reference Figure 15 When the TXOP shared mode subfield is set to 1, it supports one or more (non-TB) PPDU transmissions to the AP. When the TXOP shared mode subfield is set to 2, it supports peer-to-peer transmissions in addition to (non-TB) PPDU transmissions to the AP.

[0169] Figure 16 An example of the operation is shown when the TXOP shared schema subfield has a value of 2.

[0170] Reference Figure 16The AP can send a MU-RTS TXS TF to non-AP STA1, including allocated (time) duration information (e.g., the time allocated in the MU-RTS TXS trigger frame). Non-AP STA1 can respond to the MU-RTS TXS TF by sending a CTS and performing a P2P transmission to non-AP STA2. In this case, the (time) duration allocated from the AP to non-AP STA1 can be determined by... Figure 17 The allocation duration subfield is 16 Instructions for the unit.

[0171] Figure 17 An example of the user information field format of MU-RTS TXS TF is shown.

[0172] Reference Figure 17 The allocation duration subfield can include 9 bits from B20 to B28 in the MU-RTS TXS TF, and can be in 16... The unit indicates the allocated duration. In this case, the maximum length of the allocated duration that can be indicated by the allocated duration subfield can be... .

[0173] Additionally, the EHT AP can use a user information field to assign a TXOP time (or an allocated duration within the TXOP duration) to a STA, such as... Figure 17 As shown. However, multi-user triggered TXOP sharing can be implemented, where multiple STAs can perform P2P transmissions during the TXOP duration provided by the AP (e.g., by modifying an existing protocol), and / or the AP can provide multiple TXOP durations (or multiple allocated durations within a TXOP) to each STA.

[0174] The media access wait time can be set via the duration / ID field (2 octets) in the MAC header, with a maximum of 32,768. On the other hand, the length of the TXOP duration (or the allocation duration within the TXOP duration) allocated to the STA by the AP via the (triggered) TXOP sharing protocol can be determined by the allocation duration subfield (9 bits) in 16... Instructions for the unit, such as Figure 17 As shown.

[0175] During a (triggered) TXOP sharing process executed within a single TXOP duration obtained by the AP, the maximum length of the allocation duration, indicated by the allocation duration subfield in the MU-RTSTXS TF, can be 8,192. If the sharing STA (i.e., the STA participating in the TXOP sharing process and / or the STA that has already received the TXS trigger frame) expects to perform many frame exchanges during P2P operation, and therefore needs to exceed the maximum allocation duration (e.g., 8,192...), then... If the TXOP duration is long (or the allocation duration within the TXOP duration), then the P2P operation can be considered to be completed within a single TXOP duration obtained by the AP. For example, to complete the P2P operation within a single TXOP duration, the unit of the allocation duration indicated by the allocation duration subfield can be set to greater than 16. The value allows P2P operations to be performed beyond the existing maximum length of 8,192. The time. As another example, the TXOP duration (or the allocation duration within the TXOP duration) can be assigned to a single STA multiple times.

[0176] This disclosure provides a method / apparatus for providing multiple P2P transmission opportunities to STAs participating in a multi-user triggered TXOP sharing protocol / process within a single TXOP duration obtained by an AP. In other words, this disclosure provides a multi-triggered TXOP sharing method and / or an apparatus for implementing the method, which supports multiple P2P transmissions for some STAs participating in a multi-user triggered TXOP sharing process within the same TXOP duration.

[0177] The embodiments disclosed herein can be applied not only to TXOP sharing processes triggered by multiple users, but also to TXOP sharing processes triggered by a single user.

[0178] The embodiments of this disclosure can also be applied to support at least one transmission within the same TXOP duration for some STAs participating in a multi-user triggered TXOP sharing process.

[0179] In this disclosure, at least one STA (e.g., ) is allocated a duration during the TXOP duration used for P2P transmission. Figure 16 A non-AP STA 1) can be referred to as a P2P TX (or P2P TX STA), and a STA that receives frames from a P2P TX (e.g., Figure 16 The non-AP STA 2) can be called P2P RX (or P2P RX STA).

[0180] In this disclosure, the names of terms may be replaced by other terms with equivalent meanings, and STA may include AP STA and / or non-AP STA.

[0181] In this disclosure, the trigger frame may include a basic trigger frame and / or a MU-RTS TXS trigger frame.

[0182] A basic trigger frame can be used to indicate the start time of the allocated duration for a single STA. For example, a STA can perform a transmission (e.g., a non-TB PPDU transmission to an AP and / or a P2P transmission to another STA) immediately following the receipt of a basic trigger frame for that STA. The basic trigger frame can be simply referred to as the trigger frame.

[0183] MU-RTS TXS trigger frames can be used to assign a TXOP duration (or the assigned duration within the TXOP duration) to at least one STA. MU-RTS TXS trigger frames can also be simply referred to as TXS trigger frames.

[0184] In this disclosure, allocating TXOP duration may include allocating the entire TXOP duration and / or allocating the duration of allocation within the entire TXOP duration.

[0185] Figure 18 An example of a method for multi-trigger TXOP sharing performed by a STA according to an embodiment of this disclosure is shown.

[0186] Reference Figure 18 In step S1801, the STA may receive a TXS trigger frame that includes multiple user information fields. Each of the multiple user information fields may indicate a corresponding allocated duration among multiple allocated durations within the TXOP duration associated with the TXS trigger frame.

[0187] In step S1803, the STA can identify at least one allocation duration of the STA based on at least one user information field for the STA among a plurality of user information fields.

[0188] In step S1805, the STA may determine the start time of the first allocation duration in at least one allocation duration based on sequence information (e.g., sequence indicator bits) or at least one of the basic trigger frames.

[0189] In step S1807, the STA may send data within the first allocated duration after the start time.

[0190] According to various implementations, the STA can transmit data during the first allocation duration immediately following the receipt of the TXS trigger frame, based on sequence information including a user information field indicating the first allocation duration that is set to a first value (e.g., 1).

[0191] According to various implementations, the STA can transmit data during the first allocated duration immediately following the receipt of the basic trigger frame for the STA, based on sequence information including a second value (e.g., 0) in a user information field indicating the first allocated duration. The basic trigger frame can be received after the TXS trigger frame is received.

[0192] According to various implementations, at least one user information field for the STA may include a first user information field indicating a first allocation duration and a second user information field indicating a second allocation duration. The first user information field may be located before the second user information field in the user information list field of the TXS trigger frame.

[0193] According to various implementations, the first user information field may include multiple allocation information (e.g., multiple allocation indicator bits) indicating that at least one user information field follows the first user information field in the user information list field. The multiple allocation information may be set to a first value (e.g., 1).

[0194] According to various implementation methods, the first user information field and the second user information field can be positioned discontinuously in the user information list field.

[0195] According to various implementation methods, the first user information field and the second user information field can be continuously positioned in the user information list field.

[0196] According to various implementation methods, after decoding the first user information field, the STA can decode at least one consecutive user information field in the user information list field following the first user information field until no user information field for the STA has been decoded.

[0197] According to various implementations, after transmitting data during the first allocated duration, the STA may transmit data during the second allocated duration. The STA may transmit data during the second allocated duration immediately following the receipt of the basic trigger frame for the STA.

[0198] According to various implementation methods, data can be sent to at least one of the access point (AP) or another STA.

[0199] Figure 19 An example of signal flow between an AP and a STA for a multi-trigger TXOP shared according to an embodiment of this disclosure is shown.

[0200] Reference Figure 19 In step S1901, AP can obtain TXOP.

[0201] In step S1903, the AP can configure the user information list field of the TXOP Share (TXS) trigger frame associated with the TXOP. The user information list field may include multiple user information list fields, and each of the multiple user information fields can indicate the corresponding allocated duration among multiple allocated durations within the duration of the TXOP.

[0202] In step S1905, the AP can send a TXS trigger frame to the STA.

[0203] In step S1907, the STA can identify at least one allocation duration of the STA based on at least one user information field for the STA among a plurality of user information fields.

[0204] In step S1909, the STA may determine the start time of the first allocation duration among at least one allocation duration based on sequence information (e.g., sequence indicator bits) or at least one of the basic trigger frames.

[0205] In step S1911, the STA may send data within the first allocated duration after the start time.

[0206] The detailed implementation of multi-triggered TXOP sharing is described below.

[0207] The multi-trigger TXOP sharing method disclosed herein may include a method for configuring user information fields, a method for decoding multi-user information, and / or an operation method for multi-trigger TXOP sharing based on multi-user use cases.

[0208] I. Methods for configuring user information fields

[0209] 1. When performing P2P considering the order of user information fields

[0210] In this scenario, the order of allocation durations within a TXOP duration can follow the order of the corresponding user information fields within the user information list field. To allocate two or more TXOP durations (or allocation durations within a TXOP duration) to multiple STAs and the same STA, the user information list field of the MU-RTS TXS TF can include multiple user information fields, including two or more user information fields for the same STA. Depending on the scheduling of the AP's TXOP durations (or allocation durations within a TXOP duration), two or more user information fields for the same STA can be arranged contiguously or non-contiguously. Multiple STAs receiving the MU-RTS TXS TF including such user information list fields can decode the user information fields sequentially from first to last to identify / calculate the allocation duration included in each user information field. That is, a STA can identify the start time of the allocation duration for that STA by summing the allocation durations in all user information fields preceding the user information field to which that STA is assigned.

[0211] Figure 20 A first example of the configuration of a user information field according to an embodiment of this disclosure is shown. Figure 20 In this context, two or more user information fields for the same STA can be arranged non-contiguously.

[0212] The EHT AP can allocate / configure the allocation duration within the MU-RTS TXS TF where the value of the (triggered) TXOP shared mode subfield is set to 2, based on the TXOP duration requested by each STA. In this case, as in... Figure 20 In this context, the two user information fields for STA 1 can be arranged non-contiguously according to the AP's scheduling. As with a single user, STA 1 can perform a first P2P transmission during the duration of the allocation duration T_1 identified by the user information field #1-(1) initially allocated to STA 1, which is located first after receiving the MU-RTS TXS TF. STA 2 and STA 3 can identify their respective allocation durations as the duration T_2 after T_1 and the duration T_3 after (T_1+T_2) based on the allocation duration information in the user information fields preceding their own user information fields (i.e., user information field #2 for STA 2 and user information field #3 for STA 3). Finally, STA 1 can perform a second P2P transmission during an additional duration of the allocation duration T_1' identified by the second allocation user information field #4-(2) for STA 1.

[0213] Figure 21 A second example of the configuration of a user information field according to an embodiment of this disclosure is shown. Figure 21 In this context, two or more user information fields for the same STA can be arranged consecutively.

[0214] EHT APs can allocate / configure the allocation duration within the MU-RTS TXS TF when the value of the (triggered) TXOP shared mode subfield is set to 2, based on the TXOP duration requested by each STA. At this time, as in... Figure 21 In this context, two user information fields for STA 3 can be arranged consecutively according to the AP's scheduling. STA 1 can identify the duration T_1 allocated to STA 1 as the allocated duration after receiving the MU-RTS TXS TF, just as in the case of a single user. Subsequently, STA 2 and STA 3 can perform P2P transmissions respectively during the duration T_2 after T_1 and the duration T_3 after (T_1+T_2) based on the allocated duration information in the user information fields located before their own user information fields (i.e., user information field #2 for STA 2 and user information field #3-(1)) of STA 3. Finally, STA 3 can perform additional P2P transmissions during the duration of the allocated duration T_3' identified by the user information field #4-(2) consecutively allocated to STA 3.

[0215] The examples of consecutive / non-consecutive assignments of multiple TXOPs (or multiple assignment durations within a TXOP) as described above are not limited to... Figure 20 and Figure 21 This is a situation where, for example, user information fields with the same AID can be arranged in any user information field location in either a consecutive or non-consecutive order. When the AP configures the user information fields according to the order in which the STAs will perform P2P transmissions, each STA can identify that another STA is performing a P2P transmission for a duration corresponding to the allocation duration of all user information fields arranged before the user information field assigned to it.

[0216] 2. When performing P2P regardless of the order of user information fields.

[0217] In this scenario, the order of allocated durations within the TXOP duration can be independent of the order of the corresponding user information fields in the user information list fields. Performing P2P considering the order of user information fields relies on AP-side scheduling, but performing P2P without considering the order of user information fields may not depend on AP-side scheduling. To perform P2P considering the order of user information fields, the STA can sequentially decode the user information fields, starting with the first user information field and ending with the user information field assigned to that STA, to identify / calculate the allocated duration for that STA. Conversely, when performing P2P without considering the order of user information fields, the STA can perform P2P transmission using only the allocated duration information in the user information field corresponding to (or including) the STA's AID. This may require additional sequencing instructions and / or AP triggering.

[0218] II. Decoding methods for multiple user information fields

[0219] 1. Decoding based on multiple allocation indicators

[0220] When the STA decodes the user information list field after receiving the MU-RTS TXS TF, it must identify that multiple TXOPs (or multiple allocation durations within a TXOP duration) have been allocated to the STA. After identifying that multiple TXOPs (or multiple allocation durations within a TXOP duration) have been allocated, the STA must continue decoding the user information list field to read additional user information fields allocated to the STA.

[0221] For example, to identify that multiple TXOPs have been assigned (or multiple assignment durations within a TXOP duration), a reserved subfield within the user information field can be used, such as Figure 17As shown in the diagram. If a user information field with the same AID as the STA's AID in the current user information field is additionally positioned after the current user information field in the user information list field, then one bit (or reserved bit) of the reserved subfield of the current user information field can be used for the multi-allocation indication. That is, if the multi-allocation indication bit for the STA's user information field (or the user information field including the STA's AID) is 1, then the STA should continue decoding the user information list field until it reaches the user information field including the STA's AID and the multi-allocation indication bit is set to 0. At this time, if the user information field in the MU-RTS TXS TF is configured by taking into account the order of allocation durations within the TXOP duration, then an STA that has allocated multiple TXOPs (or multiple allocation durations within the TXOP duration) can also use the allocation duration information allocated to other STAs to determine the starting point of the subsequent allocation duration.

[0222] 2. Decoding of continuous user information fields

[0223] For example, such as Figure 21 As shown, when multiple TXOPs (or multiple allocation durations within a TXOP duration) are consecutively allocated to a specific STA, the decoding rule can be configured such that after decoding the user information field corresponding to the STA's AID, the STA further decodes at least one subsequent user information field. Given the constraint that the AP sequentially places multiple TXOP durations (or multiple allocation durations within a TXOP duration), this rule has the advantage of not requiring the use of reserved bits, unlike when multiple allocation indicator bits are used.

[0224] III. Operation method for TXOP sharing based on multiple triggers in multi-user use cases

[0225] 1. When performing P2P considering the order of user information fields

[0226] Figure 22 A first example of multi-trigger TXOP sharing operation according to an embodiment of this disclosure is shown. Figure 22 In this context, i) the order of the allocation durations assigned to the three STAs within the TXOP duration follows the order of the corresponding user information fields within the user information list fields, and ii) two or more user information fields for the same STA (e.g., STA 1) are arranged non-contiguously, such as... Figure 20 As shown.

[0227] Reference Figure 22STA 1, having been allocated two non-contiguous TXOP durations (or two allocated durations within a TXOP duration) from the EHT AP, can read the user information field #1-(1) where the multi-allocation indicator bit is set to 1. Since the multi-allocation indicator bit is set to 1, STA 1 can identify the presence of additional user information fields for STA 1 in the user information list field and can continue decoding the user information list field. After identifying all additional allocated user information fields by decoding user information fields #4-(2) until the multi-allocation indicator bit is set to 0, STA 1 can perform a P2P transmission for the duration T_1 immediately following the receipt of the MU-RTS TXS TF. STA 1, having completed the first P2P transmission, can wait until the start time of the additional allocation T_1'. STA 2 can read the allocation duration information of user information fields #1-(1) and #2 after receiving the MU-RTS TXS TF, and identify T_2 as its own allocation duration after T_1. STA 3 can also perform P2P transmission during a duration T_3 starting after (T_1+T_2) after reading the allocated duration information of user information fields #1-(1), #2, and #3. After the time (T_1+T_2+T_3) that is the end of STA 3's P2P transmission, STA 1 can perform additional P2P transmission during a time T_1' that is the second allocated duration of STA 1. Therefore, the AP can allocate multiple TXOP durations (or multiple allocated durations within a TXOP duration) to STAs that need to perform multiple frame exchanges within a single TXOP duration obtained by the AP, thereby enabling STAs to complete P2P transmissions faster.

[0228] Figure 23 A second example of multi-trigger TXOP sharing operation according to an embodiment of this disclosure is shown. Figure 23 In this context, i) the order of the allocation durations assigned to the three STAs within the TXOP duration follows the order of the corresponding user information fields within the user information list fields, and ii) two or more user information fields for the same STA (e.g., STA 2) are arranged consecutively, such as... Figure 21 middle.

[0229] Reference Figure 23After STA 1 performs a P2P transmission during T_1 immediately following the receipt of the MU-RTS TXS TF, STA 2 may perform a first P2P transmission during time T_2, which is the allocation duration of user information field #2-(1) with the multi-allocation indicator bit set to 1. Alternatively, when multiple TXOPs are allocated consecutively (or multiple allocation durations within the TXOP duration), STA may decode the user information field corresponding to STA's AID (e.g., user information field #1) and at least one subsequent user information field corresponding to STA's AID consecutively, according to a decoding rule set, to decode the user information field (e.g., user information field #1) and the subsequent user information field (e.g., user information field #2-(1)) without using a separate multi-allocation indicator bit. In this scenario, for example, STA 2 may not recognize the times T_2 and T_2' allocated by the AP as a single long allocation duration (i.e., T_2 + T_2'), but instead perform P2P transmissions by treating them as separate TXOP durations (or allocation durations within TXOP durations). That is, STA 2 must complete the transmission and reception of all response PPDUs within each individual duration of T_2 and T_2'. Alternatively, STA 2 may treat the durations T_2 and T_2' allocated by the AP as a single long allocation duration (i.e., T_2 + T_2'), and perform P2P transmissions during the entire allocation duration of T_2 + T_2'. That is, STA 2 can complete the transmission and reception of all response PPDUs within the entire allocation duration of T_2 + T_2'.

[0230] STA 2, which performs the first P2P transmission during T_2, can subsequently perform a second P2P transmission during T_2'. This allows STA 2, which requires a large number of frame exchanges during a duration exceeding the maximum allocated duration for a single STA, to complete a P2P transmission within a single TXOP duration of the AP.

[0231] Figure 22 and Figure 23The multi-trigger TXOP sharing method for multiple users shown can have static characteristics because the AP allocates one or more TXOP durations (or one or more allocated durations within a TXOP duration) to the STA based on information previously requested from the STA. Furthermore, when two or more allocated durations are continuously allocated to a particular STA within a TXOP duration, P2P transmissions may become unnecessary after a period of relatively long consecutive TXOP durations (or allocated durations within a TXOP duration) allocated from the AP to the STA. In this case, the STA can return the allocated TXOP duration (or allocated durations within a TXOP duration) to prevent the channel from being wasted for an extended period.

[0232] 2. When performing P2P regardless of the order of user information fields.

[0233] Unlike methods where the AP predetermines the P2P operation order for all STAs to share the TXOP duration with multiple STAs (e.g., performing P2P based on the order of user information fields), the AP can support P2P operations regardless of the order of user information fields configured by the AP within the user information list fields. This requires the AP to trigger the process for each STA at the start of the allocated duration, and an instruction from the STA to perform the P2P operation immediately upon receiving the MU-RTS TXS TF.

[0234] 2-1) Sequence Indication Method

[0235] In a single-user triggered TXOP sharing protocol / process, the STA can begin its allocation duration when the PHY-RXEND.indication primitive of the PPDU including the MU-RTS TXS TF sent from the AP occurs. In other words, the starting point for the allocation duration in a single-user triggered TXOP sharing protocol / process can be the time when the PHY-RXEND.indication primitive of the PPDU including the MU-RTS TXSTF sent from the AP occurs. However, in a multi-user triggered TXOP sharing use case, if the AP does not predetermine the starting point for the STA's allocation duration, all STAs indicated by the user information list field can begin their allocation duration when the PHY-RXEND.indication primitive occurs, potentially leading to conflicts between STAs.

[0236] To indicate which STA will perform the P2P operation first, you can use... Figure 17The reserved subfields in the user information field. For example, one bit in the reserved subfield can be used as a sequence indicator (or sequence information), which includes an indication that the STA must start its allocation duration immediately after receiving the MU-RTS TXS TF, as in the existing single-user case, and / or an indication that the STA does not need to start its allocation duration immediately after receiving the MU-RTS TXS TF. In this case, the STA whose corresponding sequence indicator field in the user information field is set to 1 can start its allocation duration immediately after receiving the MU-RTS TXS TF and perform P2P operations / transmissions during the allocation duration. On the other hand, the remaining STAs whose corresponding sequence indicator field in the user information field is set to 0 can not start their allocation duration immediately after receiving the MU-RTS TXS TF, but can wait until a trigger frame is sent from the AP.

[0237] 2-2) AP Triggering Method

[0238] To enable another STA to initiate a P2P transmission immediately after the STA that first performs the P2P transmission upon receiving the MU-RTS TXS TF, using the sequence indication method, an additional trigger frame (e.g., a basic trigger frame) must be sent from the AP. The trigger frame can include a control frame, a QoS data frame, and / or a QoS empty frame. For example, the MU-RTS TXS TF can be reused as a control frame, similar to the method of allocating duration (e.g., TXOP duration / allocation duration) to a single STA in a single-user triggered TXOP sharing protocol / process. Alternatively, to initiate a P2P transmission, the AP can transmit an RTS frame (to the STA). Since the allocated duration has already been allocated to the STA receiving the RTS frame via the MU-RTS TXS TF, transmission can begin immediately upon receiving the RTS frame. Furthermore, since the frame used to trigger the start of P2P transmission for subsequent STAs can be sent separately to the target STA, QoS data frames and / or QoS empty frames can be used as frames to trigger the start of P2P transmission for subsequent STAs.

[0239] Figure 24 A third example of multi-trigger TXOP sharing operation according to an embodiment of this disclosure is shown. Figure 24 In this context, i) the order of the allocation durations assigned to different STAs within the TXOP duration is independent of the order of the corresponding user information fields in the user information list fields, and ii) there are two user information fields / allocation durations for STA 3.

[0240] Reference Figure 24Since the sequence indicator bit in the second user information field within the MU-RTS TXS TF is set to 1, STA 2 can perform the P2P operation first. The sequence indicator bits in the remaining user information fields can be set to 0. Immediately after receiving the MU-RTS TXS TF, STA 2, associated with a user information field including the sequence indicator bit set to 1, can perform a P2P transmission during its own allocated duration. After STA 2's P2P transmission is complete, the AP can send a trigger frame to the STA (e.g., STA 1) that will subsequently perform a P2P operation. The subsequent STA 1 that receives the trigger frame can perform frame exchange (i.e., P2P operation / transmission) during its own allocated duration T_1, immediately following the receipt of the trigger frame or immediately following the sending of a response frame to the trigger frame. The same process can be repeated for subsequent STAs, and STA 3, which has been allocated multiple TXOP durations (or multiple allocated durations within a TXOP duration), can first perform P2P transmission during the time period immediately following the receipt of the trigger frame, indicated by the allocated duration in a user information field (e.g., user information field #3-(1)) with multiple allocation indication bits set to 1. As another example, STA 3, which has been allocated multiple TXOP durations (or multiple allocated durations within a TXOP duration), can first perform P2P transmission during the time period immediately following the receipt of the trigger frame, indicated by the allocated duration in a user information field (e.g., user information field #3-(1)) which is the first user information field arranged in the user information list field for STA 3. That is, the order of allocated durations allocated to the same STA within a TXOP duration can follow the order of the corresponding user information fields in the user information list field. After STA 3 completes its first P2P operation, if it receives a trigger frame from AP indicating the start of the second allocation duration, STA 3 may perform additional P2P operations / transmissions / frame exchanges.

[0241] Meanwhile, regarding multi-user triggered TXOP sharing, an appropriate TXOP allocation method needs to be applied to the AP for effective operation of multiple STAs.

[0242] Figure 25 An example of a TXOP allocation method according to an embodiment of this disclosure is shown.

[0243] In a multi-user triggered TXOP sharing protocol / process, if each STA requests a different TXOP duration, TXOP allocation can be performed, for example, as... Figure 25As shown. If the EHT AP randomly assigns the TXOP duration to each STA, the duration can be assigned in the order of T_1, T_2, and T_3, as follows. Figure 25 As shown. Information regarding the allocation duration can be sent to all STAs via MU-RTS TXSTF (TXOP sharing mode 2). Since STA 1's allocated TXOP duration (or the allocation duration within the TXOP duration) is allocated first, it can perform P2P transmission within the time period T_1 immediately following the receipt of the TF. On the other hand, STA2, allocated T_2, and STA3, allocated T_3, must remain active in time T_1 and (T_1+T_2) respectively, waiting until their allocation duration begins. At this time, if the P2P operation duration of the initially allocated STA is long, such as... Figure 25 As shown, subsequent STAs requiring only relatively short P2P transmissions must unnecessarily wait for longer periods. This problem is not significant when all STAs request the same TXOP duration. However, as the difference in allocated durations between STAs increases, the final STA requiring only short P2P operations must wait a long time for its turn.

[0244] Therefore, in a multi-user triggered TXOP sharing protocol / process that supports P2P transmission of multiple STAs, an effective TXOP duration allocation is required for requests with different TXOP durations.

[0245] This disclosure proposes a method for configuring user information fields and a method for prioritizing short TXOP duration allocation to enable some STAs participating in a multi-user triggered TXOP sharing protocol / process to perform P2P operations in advance.

[0246] This disclosure presents a method for configuring user information fields and a method for prioritizing short TXOP duration allocation to enable some STAs participating in a multi-user triggered TXOP sharing process to perform P2P operations earlier than other STAs.

[0247] If the MU-RTS TXS TF is extended to a multi-user scenario, the TXOP duration can be provided to multiple STAs by individually allocating corresponding user information fields within the MU-RTS TXS TF based on the MU-RTS / CTS protocol defined in 802.11ax. STAs receiving the MU-RTS TXS TF can simultaneously send a CTS response. In this case, each of the multiple STAs receiving different TXOP durations must be able to accurately determine the duration allocated to them by the AP to successfully perform non-TB PPDU transmissions or P2P transmissions and prevent channel waste. Therefore, each user information field can indicate the timing of the TXOP duration as follows:

[0248] Configure user information fields for prioritizing the allocation of short TXOP durations.

[0249] To allocate TXOP durations to multiple STAs, the user information list field within the MU-RTS TXS TF can include multiple user information fields. STAs communicate their P2P requests to the AP via the Flow Classification Service (SCS) request / response process, and the AP can prioritize user information fields from STAs requesting shorter TXOP durations when configuring user information fields. Therefore, the user information field for the STA requiring the longest TXOP duration can be placed last. Multiple STAs receiving the MU-RTS TXS TF including such a user information list field can sequentially calculate the duration by decoding the user information fields from the first to the last. In other words, an STA can determine the start time of its allocated duration by summing the allocated durations within all user information fields allocated before its assigned user information field.

[0250] Figure 26 An example of the configuration of a user information field for priority allocation based on short TXOP duration is shown according to an embodiment of this disclosure.

[0251] Reference Figure 26The EHT AP can allocate the allocated duration within the MU-RTS TXS TF set to TXOP sharing mode 2 based on the TXOP duration requested by each STA. In this case, the user information list field can be configured sequentially from STA 3, which will be allocated the shortest allocated duration, to STA 2, which will be allocated the longest allocated duration. Since STA 3 has its own user information field very early on, it can perform P2P transmission within the time period T_3 immediately following the receipt of the MU-RTS TXS TF (same as in the single-user case). STA 1, which has already been allocated T_1, can perform P2P transmission within the time period T_1 starting after T_3, where T_3 is STA 3's allocated duration. STA 2 can also identify its allocated duration from the time period T_2 starting from (T_3+T_1) based on the allocation information of STA 3 and STA 1.

[0252] The above user information field configuration can be simply designed from the MU's perspective. Furthermore, according to the above user information field configuration, each STA needs to decode the allocation duration subfield, even if it is not its own user information field, until it reaches the user information field that includes its own AID. That is, the STA whose user information field is last needs to decode the allocation duration subfield within all previous user information fields and use the decoding results (to determine the starting point of its own allocation duration).

[0253] Prioritization of short TXOP duration allocation operations

[0254] Figure 27 An example of the operation of prioritizing the allocation of short TXOP durations according to an embodiment of this disclosure is shown.

[0255] Reference Figure 27 The EHT AP can allocate allocation durations T_1, T_2, and T_3 based on different TXOP durations requested from each STA. In this case, the user information fields can be configured in descending order of the TXOP durations requested from each STA, such as... Figure 26As shown. Since the user information field corresponding to STA 3 is in the first position, STA 3 can perform P2P transmission for a duration T_3 immediately following the receipt of the MU-RTS TXS TF from the EHT AP. STA 2 reads the information in user information fields #1 and #2 after receiving the MU-RTS TXS TF, waits until the previously allocated duration T_3 of STA 3 has elapsed, and then performs P2P transmission for the allocated duration T_2 starting after T_3. STA 1 can also wait (T_3+T_2) based on the information in user information fields #1 and #2, and then identify T_1 of its user information field #3 as the allocated duration. In other words, by prioritizing the allocation of TXOP durations to STAs that only require short-term P2P transmissions, these STAs can avoid unnecessary waiting.

[0256] In order to prioritize the allocation of short TXOP durations, each STA must decode the allocated duration in the user information field before identifying the user information field that includes its own AID when decoding the user information list field, even if it does not include its own AID, and use the decoding result to determine the starting point of its allocated duration.

[0257] The user information field configuration method and the acquisition of duration information based on the order of user information fields disclosed herein have the advantage of being simple to design from a multi-user perspective.

[0258] Meanwhile, regarding multi-user triggered TXOP sharing, a power-efficient TXOP duration allocation method needs to be applied to some power-sensitive STAs.

[0259] In this disclosure, power sensitivity is introduced. Power sensitivity may include the listening interval of the STA and / or the maximum idle time of the BSS. For example, a shorter listening interval of the STA may indicate a higher power sensitivity of the STA. Alternatively, a longer maximum idle time of the STA may indicate a higher power sensitivity of the STA.

[0260] Figure 28 An example is shown of allocating TXOP durations to STAs with different power sensitivities during a multi-user triggered TXOP sharing process according to an embodiment of the present disclosure.

[0261] Reference Figure 28 STAs with different power sensitivities can be assigned TXOP durations in any order through a multi-user triggered TXOP sharing process. When the EHT AP randomly assigns TXOP durations to each STA, the durations can be assigned in the order of T_1, T_2, and T_3, such as... Figure 28As shown, information regarding the allocated duration can be sent to all STAs via MU-RTS TXS TF (TXOP sharing mode 2). Since STA 1 has its allocated TXOP duration set first, it can perform P2P transmission for the duration T_1 immediately following the receipt of MU-RTS TXS TF. On the other hand, STA 2, which has been allocated T_2, and STA 3, which has been allocated T_3, must remain in active mode for the durations T_1 and (T_1+T_2), respectively, or operate with a specific power management scheme and wait until their allocated duration begins. These subsequent STAs (i.e., STA 2 and STA 3) can apply appropriate power management schemes to remain in a doze state until P2P operation is performed, thereby reducing unnecessary power consumption. However, some STAs allocated TXOP durations may experience CTS failure and / or premature termination of the allocated TXOP duration (or the allocated duration within the TXOP duration). In this case, the trigger frame cannot be transmitted to the subsequent STAs remaining in a doze state, resulting in wasted channel space.

[0262] Therefore, in multi-user triggered TXOP sharing protocols / processes that support P2P transmissions for multiple STAs, efficient TXOP duration allocation based on STA power sensitivity is required.

[0263] This disclosure proposes a method for configuring user information fields and a method for prioritizing TXOP duration allocation, which allows some STAs participating in a multi-user triggered TXOP sharing process to perform P2P operations earlier than other STAs, as follows:

[0264] When the MU-RTS TXS TF is applied in a multi-user scenario, the AP can provide the TXOP duration to multiple STAs by allocating a user information field corresponding to each STA within the MU-RTS TXS TF based on the MU-RTS / CTS protocol defined in 802.11ax. STAs receiving the MU-RTS TXS TF can respond by simultaneously sending a CTS. At this point, each STA must know precisely when the AP has allocated its requested TXOP duration to successfully perform non-TB PPDU transmissions or P2P transmissions, and also to prevent channel waste. Therefore, each user information field can indicate the TXOP duration (or the allocated duration within the TXOP duration) (or its start time) to each STA in the following way:

[0265] Configuration of user information fields considering power sensitivity

[0266] To allocate the TXOP duration to multiple STAs, the user information list field within the MU-RTS TXS TF can include multiple user information fields. STAs communicate their P2P operation and / or power sensitivity requirements to the AP via the SCS request / response procedure. When configuring user information fields, the AP can prioritize placing user information fields for STAs with high power sensitivity within the user information list field. Therefore, user information fields for STAs with low power sensitivity can be placed last within the user information list field. STAs receiving the MU-RTS TXS TF including such user information fields sequentially decode the user information fields from the first allocated user information field to the last, and sequentially calculate the allocated duration. In other words, each STA determines the start time of its own allocated duration by summing the allocated durations indicated by all user information fields arranged before the user information field allocated to the STA.

[0267] Figure 29 An example of a user information field format considering power sensitivity according to an embodiment of this disclosure is shown.

[0268] Reference Figure 29 The EHT AP can allocate the allocated duration within the MU-RTS TXS TF set to TXOP sharing mode 2 based on the TXOP duration requested by each STA. In this case, the AP can configure the user information list fields sequentially from the power-sensitive STA 3 to the power-insensitive STA 2. Since the user information field corresponding to STA 3 is first, STA 3 can perform P2P transmissions for a time period T_3 immediately following the receipt of the MU-RTS TXS TF, similar to the single-user case. STA 1, which has already been allocated T_1, can perform P2P transmissions for a time period T_1 starting after T_3, where T_3 is STA 3's allocated duration. STA 2 can also identify the time period T_2, starting from (T_3+T_1), as its own allocated duration based on the allocated duration information of STA 3 and STA 1.

[0269] The user information field format can be simply designed from the MU's perspective. Each STA needs to decode the allocation duration subfield, even if it is not its own user information field, until it reaches the user information field that includes its AID. That is, the STA with the last user information field needs to decode the allocation duration subfield in all previous user information fields and use the decoding results (to determine the start time of its own allocation duration).

[0270] Operation with priority allocation of TXOP duration considering power sensitivity

[0271] Figure 30 An example of the operation of prioritizing the allocation of TXOP duration considering power sensitivity according to an embodiment of this disclosure is shown.

[0272] Reference Figure 30 The EHT AP can allocate the allocation durations of T_1, T_2, and T_3 based on the needs of STAs with different power sensitivities. In this case, as... Figure 29 As shown, the AP can configure the user information fields in order of high power sensitivity for each STA. Since the user information field corresponding to STA 3 is placed before the user information list fields, STA 3 can perform P2P transmission during the time period T_3 immediately following the receipt of the MU-RTS TXS TF from the EHT AP. After receiving the MU-RTS TXS TF, STA 1 reads the information in user information fields #1 and #2, and waits until the allocated duration T_3 of the previous STA 3 has elapsed. Afterward, STA 1 can perform P2P transmission during the allocated duration T_1 starting after T_3. Similarly, STA 2 waits (T_3+T_1) based on the information in user information fields #1 and #2, and then identifies the T_2 corresponding to its allocated user information field #3 for its allocated duration. In other words, by first allocating the TXOP duration to the STA that needs reduced power consumption, the power consumption of the corresponding STA can be minimized.

[0273] When decoding user information list fields, each STA needs to decode the allocation duration of the user information fields, even if these fields do not include their own AID, until the STA identifies a user information field that includes its own AID and uses the decoding result to determine the start time of its own allocation duration.

[0274] The user information field configuration method disclosed herein, as well as the sequential acquisition of allocation duration information based on the user information field, have the advantage of being simple to design from a multi-user perspective.

[0275] The technical features of this disclosure described above can be applied to various apparatuses and methods. For example, the technical features of this disclosure described above can be derived from... Figure 1 and / or Figure 13 The device implementation / support. For example, the technical features of this disclosure described above can be applied only to... Figure 1 and / or Figure 13 Part of it. For example, the technical features of the present disclosure described above can be based on Figure 1 Implemented using processing chips 114 and 124, or based on Figure 1Implemented by processors 111, 121 and memories 112, 122, or based on Figure 13 This is achieved using a processor 610 and a memory 620.

[0276] For example, Figure 1 The processor 111, the processing chip 114 and / or Figure 13 The processor 610 can be configured to execute instructions stored in memories 112, 620 to implement a method performed by the STA of this disclosure. The method includes: receiving a Transmission Opportunity (TXOP) Sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one user information field of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a basic trigger frame; and transmitting data within the first allocated duration after the start time.

[0277] For example, Figure 1 The processor 121 and / or processing chip 124 may be configured to execute instructions stored in memory 122 to implement a method performed by the AP of this disclosure. The method includes: obtaining a transmission opportunity (TXOP); configuring a user information list field of a TXOP sharing (TXS) trigger frame associated with the TXOP, wherein the user information list field includes a plurality of user information list fields, and each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within the duration of the TXOP; and transmitting the TXS trigger frame, wherein the plurality of user information fields includes at least one user information field for the STA indicating at least one allocated duration of the STA, and wherein a start time of a first allocated duration among the at least one allocated duration is determined based on sequence information or at least one of a basic trigger frame.

[0278] The technical features of this disclosure can be implemented based on a computer-readable medium (CRM) (e.g., a non-transitory CRM). For example, the CRM in this disclosure may include at least one CRM having program code stored thereon that implements instructions executable by at least one processor.

[0279] For example, CRM can be Figure 1 memory 112, Figure 13The memory 620 and / or separate external memory / storage medium / disk. The CRM can store data based on a processor (e.g., ...). Figure 1 The processor 111, the processing chip 114 and / or Figure 13 The processor 610 executes instructions to implement the method performed by the STA in this disclosure. The method includes: receiving a Transmission Opportunity (TXOP) Sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within a TXOP duration associated with the TXS trigger frame; identifying at least one allocated duration of the STA based on at least one user information field of the plurality of user information fields for the STA; determining a start time of a first allocated duration among the at least one allocated duration based on sequence information or at least one of a base trigger frame; and transmitting data within the first allocated duration after the start time.

[0280] For example, CRM can be Figure 1 The memory 122 and / or separate external memory / storage medium / disk. The CRM can store data based on a processor (e.g., ...). Figure 1 The processor 121 and / or processing chip 124 executes instructions to implement the method performed by the AP in this disclosure. The method includes: obtaining a transmission opportunity (TXOP); configuring a user information list field of a TXOP sharing (TXS) trigger frame associated with the TXOP, wherein the user information list field includes a plurality of user information list fields, and each of the plurality of user information fields indicates a corresponding allocated duration among a plurality of allocated durations within the duration of the TXOP; and sending the TXS trigger frame, wherein the plurality of user information fields includes at least one user information field for the STA indicating at least one allocated duration of the STA, and wherein a start time of a first allocated duration among the at least one allocated duration is determined based on sequence information or at least one of a basic trigger frame.

[0281] The aforementioned technical features of this disclosure are applicable to various applications or business models. For example, the aforementioned technical features can be applied to wireless communication in devices that support artificial intelligence (AI).

[0282] Artificial intelligence (AI) refers to the field of research concerning artificial intelligence or the methods used to create it, while machine learning refers to the field of research concerning methods for defining and solving various problems within the field of AI. Machine learning is also defined as an algorithm that improves operational performance through stable operational experience.

[0283] Artificial neural networks (ANNs) are models used in machine learning, and can refer to models that solve problems in general, including artificial neurons (nodes) that form a network by combining synapses. An artificial neural network can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates the output value.

[0284] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron can output the function value of an activation function of the input signal input through synapses, weights, and biases.

[0285] Model parameters refer to the parameters determined through learning, and include the weights of synaptic connections and the biases of neurons. Hyperparameters refer to the parameters that are set before learning in a machine learning algorithm, and include the learning rate, number of iterations, minimum batch size, and initialization function.

[0286] Learning artificial neural networks may aim to determine model parameters used to minimize a loss function. The loss function can be used as a metric for determining the optimal model parameters during the learning process of an artificial neural network.

[0287] Machine learning can be divided into supervised learning, unsupervised learning, and reinforcement learning.

[0288] Supervised learning refers to the method of training an artificial neural network using labels provided for the training data. When the training data is input into the artificial neural network, the labels indicate the correct answer (or result value) that the network should infer. Unsupervised learning refers to the method of training an artificial neural network without providing labels for the training data. Reinforcement learning can be a training method used to train an agent defined in an environment to select actions or sequences of actions to maximize the cumulative reward in each state.

[0289] Machine learning implemented using deep neural networks (DNNs) with multiple hidden layers is called deep learning, and deep learning is a part of machine learning. In the following text, machine learning is interpreted as including deep learning.

[0290] The aforementioned technical features can be applied to wireless communication for robots.

[0291] A robot can be defined as a machine that automatically processes or operates a given task using its own capabilities. In particular, a robot that has the ability to recognize its environment and make autonomous judgments to perform operations can be called an intelligent robot.

[0292] Depending on their application or field, robots can be categorized into industrial, medical, household, and military robots, among others. Robots can include actuators or drives that include motors to perform various physical operations, such as moving robot joints. Additionally, mobile robots can include wheels, brakes, propellers, etc., in their drives to move on the ground or fly in the air.

[0293] The aforementioned technical features can be applied to devices that support extended reality.

[0294] Extended reality is collectively referred to as virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that provides real-world objects and backgrounds only in CG images; AR technology is a computer graphics technology that provides virtual CG images on top of real object images; and MR technology is a computer graphics technology that provides virtual objects that are mixed and combined with the real world.

[0295] MR technology is similar to AR technology in that it can display real and virtual objects together. However, in AR technology, virtual objects are used as a supplement to real objects, while in MR technology, virtual and real objects are used as equals.

[0296] XR technology can be applied to head-mounted displays (HMDs), head-up displays (HUDs), mobile phones, tablets, laptops, desktop computers, televisions, digital signage, and more. Devices that utilize XR technology can be referred to as XR devices.

[0297] This disclosure can have various beneficial effects.

[0298] For example, the methods for configuring user information fields and for multiple allocation instructions and sequence instructions in this disclosure can be easily designed from a multi-user perspective. Furthermore, in a single-user triggered TXOP sharing protocol / process, if each STA needs a large number of P2P transmissions within a period exceeding the maximum allocation duration that can be allocated from the AP, the AP must obtain a new TXOP duration through media contention. However, the multi-triggered TXOP sharing method of this disclosure allows STAs to perform and complete P2P transmissions for relatively long periods within a single TXOP duration.

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

[0300] The claims in this disclosure can be combined in various ways. For example, the technical features in the method claims of this disclosure can be combined to be implemented or performed in an apparatus, and the technical features in the apparatus claims can be combined to be implemented or performed in a method. Furthermore, the technical features in the method claims and apparatus claims can be combined to be implemented or performed in an apparatus, and the technical features in the method claims and apparatus claims can be combined to be implemented or performed in a method.

Claims

1. A method performed by a station (STA) in a wireless local area network (LAN) system, the method comprising: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocation duration among a plurality of allocation durations within a TXOP duration related to the TXS trigger frame; identifying at least one allocation duration for the STA based on at least one user information field for the STA among the plurality of user information fields; determining a start time of a first allocation duration among the at least one allocation duration based on at least one of an order information or a basic trigger frame; and transmitting data in the first allocation duration after the start time.

2. The method of claim 1, wherein, the transmitting the data includes transmitting the data in the first allocation duration immediately after receiving the TXS trigger frame based on the order information being set to a first value for a user information field indicating the first allocation duration.

3. The method of claim 1, wherein, the transmitting the data includes transmitting the data in the first allocation duration immediately after receiving the basic trigger frame for the STA based on the order information being set to a second value for a user information field indicating the first allocation duration, and wherein the basic trigger frame is received after receiving the TXS trigger frame.

4. The method of claim 1, wherein, the at least one user information field for the STA includes a first user information field indicating the first allocation duration and a second user information field indicating a second allocation duration, and wherein the first user information field precedes the second user information field in a user information list field of the TXS trigger frame.

5. The method of claim 4, wherein, the first user information field includes multi-allocation information indicating at least one user information field following the first user information field in the user information list field, and wherein the multi-allocation information is set to a first value.

6. The method of claim 4, wherein, the first user information field and the second user information field are positioned discontinuously in the user information list field.

7. The method of claim 4, wherein, the first user information field and the second user information field are positioned continuously in the user information list field.

8. The method of claim 7, further comprising: decoding at least one user information field following the first user information field in the user information list field after decoding the first user information field until no user information field for the STA is decoded.

9. The method of claim 4, the method further comprising transmitting data in the second allocation duration after transmitting the data in the first allocation duration, wherein the transmitting the data in the second allocation duration includes transmitting the data in the second allocation duration immediately after receiving the basic trigger frame for the STA.

10. The method of claim 1, wherein, the data is transmitted to at least one of an access point (AP) or another STA.

11. A station (STA) in a wireless local area network (LAN) system, the STA comprising: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, wherein the memory stores instructions that, based on execution by the at least one processor, perform operations comprising: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocation duration among a plurality of allocation durations within a TXOP duration related to the TXS trigger frame; identifying at least one allocation duration for the STA based on at least one user information field among the plurality of user information fields for the STA; determining a start time of a first allocation duration among the at least one allocation duration based on at least one of sequence information or a basic trigger frame; and transmitting data in the first allocation duration after the start time.

12. A device configured to operate in a wireless local area network (LAN) system, the device comprising: at least one processor; and at least one memory operatively coupled to the at least one processor, wherein the at least one memory stores instructions that, based on execution by the at least one processor, perform operations comprising: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocation duration among a plurality of allocation durations within a TXOP duration related to the TXS trigger frame; identifying at least one allocation duration for the STA based on at least one user information field among the plurality of user information fields for the STA; determining a start time of a first allocation duration among the at least one allocation duration based on at least one of sequence information or a basic trigger frame; and transmitting data in the first allocation duration after the start time.

13. A non-transitory computer readable medium (CRM) having stored thereon program code implementing instructions that, based on execution by at least one processor, perform operations comprising: receiving a transmission opportunity (TXOP) sharing (TXS) trigger frame including a plurality of user information fields, wherein each of the plurality of user information fields indicates a corresponding allocation duration among a plurality of allocation durations within a TXOP duration related to the TXS trigger frame; identifying at least one allocation duration for the STA based on at least one user information field among the plurality of user information fields for the STA; determining a start time of a first allocation duration among the at least one allocation duration based on at least one of sequence information or a basic trigger frame; and transmitting data in the first allocation duration after the start time. ​ 14. An access point (AP) in a wireless local area network (WLAN) system, the AP comprising: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, wherein the memory stores instructions that, based on execution by the at least one processor, perform operations comprising: obtaining a transmission opportunity (TXOP); configuring a user info list field of a TXOP share (TXS) trigger frame related to the TXOP, wherein the user info list field includes a plurality of user info fields, and each of the plurality of user info fields indicates a corresponding allocation duration among a plurality of allocation durations within a duration of the TXOP; and transmitting the TXS trigger frame, wherein the plurality of user info fields includes at least one user info field for a STA indicating at least one allocation duration of the STA, and wherein a start time of a first allocation duration of the at least one allocation duration is determined based on at least one of sequence information or a basic trigger frame. the start time of the first allocation duration is determined to be immediately after transmitting the TXS trigger frame based on the user info field indicating the first allocation duration including the sequence information set to a first value.

15. The AP of claim 14, wherein, the start time of the first allocation duration is determined to be immediately after transmitting the basic trigger frame for the STA based on the user info field indicating the first allocation duration including the sequence information set to a second value, and 16. The AP of claim 14, wherein, wherein the basic trigger frame is transmitted after transmitting the TXS trigger frame. the at least one user info field for the STA includes a first user info field indicating the first allocation duration and a second user info field indicating a second allocation duration, and 17. The AP of claim 14, wherein, wherein the first user info field precedes the second user info field in the user info list field of the TXS trigger frame. the first user info field includes multi-allocation information indicating that at least one user info field follows the first user info field in the user info list field, and 18. The AP of claim 17, wherein, wherein the multi-allocation information is set to a first value. the first user info field and the second user info field are positioned contiguously or non-contiguously in the user info list field.

19. The AP of claim 17, wherein, 20. A method performed by an access point (AP) in a wireless local area network (WLAN) system, the method comprising: obtaining a transmission opportunity (TXOP); configuring a user info list field of a TXOP share (TXS) trigger frame related to the TXOP, wherein the user info list field includes a plurality of user info fields, and each of the plurality of user info fields indicates a corresponding allocation duration among a plurality of allocation durations within a duration of the TXOP; and transmitting the TXS trigger frame, ​ wherein the plurality of user info fields includes at least one user info field for a STA indicating at least one allocation duration for the STA, and wherein a start time of a first allocation duration of the at least one allocation duration is determined based on at least one of the order information or the basic trigger frame.

Images