Method and device for receiving management frame including information pertaining to DSO mode in wireless LAN system
The method for receiving a management frame in next-generation Wi-Fi systems clarifies DSO operation mode, addressing inconsistencies and enhancing operational predictability by specifying TXOP or SP frame exchange, thus improving DSO consistency.
Patent Information
- Application Number
- PCT/KR2026/096926
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-10-27
- Filing Date
- 2026-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
There is a need for improved methods to determine whether frame exchange in a DSO subband will be performed during a TXOP or SP in next-generation Wi-Fi systems, such as IEEE 802.11be, to ensure consistency and predictability in DSO operation between non-AP STAs and APs.
A method and apparatus for receiving a management frame containing information regarding a DSO mode, indicating whether frame exchange will be performed during a TXOP or SP, thereby reducing inconsistency in DSO operation interpretation and improving operational consistency.
The proposed method enhances predictability and consistency in DSO operation by clearly indicating the mode of operation through a management frame, reducing potential misinterpretations between non-AP STAs and APs.
Smart Images

Figure KR2026096926_19112026_PF_FP_ABST
Abstract
Description
Method and device for receiving a management frame containing information regarding DSO mode in a wireless LAN system
[0001] The present specification relates to a technique for receiving a management frame containing information regarding a DSO mode in a wireless LAN system, and more specifically, to a method and apparatus for determining whether frame exchange in a DSO subband will be performed during a TXOP or SP based on the management frame.
[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs, and to this end, various technologies are being considered to support high throughput, low latency, and extended range. For example, a procedure for negotiating a DSO can be performed.
[0003] The present specification proposes a method and apparatus for receiving a management frame containing information regarding a DSO mode in a wireless LAN system.
[0004] An example of the present specification proposes a method for receiving a management frame containing information regarding a DSO mode.
[0005] This embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0006] This embodiment proposes a method for indicating whether a DSO operates based on TXOP or SP by transmitting information regarding the DSO mode through a management frame. In addition, this embodiment proposes a method for negotiating DSO subbands in an unsolicited manner through the management frame.
[0007] The first STA (station) receives a management frame from the second STA.
[0008] The first STA performs frame exchange with the second STA in the DSO (Dynamic Subband Operation) subband based on the management frame.
[0009] The above management frame includes information regarding the DSO mode. The information regarding the DSO mode indicates whether the frame exchange will be performed during the TXOP (Transmission Opportunity) or SP (Service Period).
[0010] According to the method proposed in this embodiment, by transmitting information regarding the DSO mode through a management frame, it is possible to clearly indicate whether the DSO operates based on TXOP or based on SP. Through this, the possibility of inconsistency in interpretation regarding the DSO operation method between non-AP STA and AP can be reduced, and the predictability of DSO operation and operational consistency can be improved.
[0011] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.
[0012] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).
[0013] Figure 3 is a diagram illustrating a general link setup process.
[0014] FIG. 4 illustrates an example of a multi-link (ML).
[0015] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.
[0016] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.
[0017] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.
[0018] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.
[0019] Figure 9 shows the operation according to UL-MU.
[0020] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.
[0021] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.
[0022] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.
[0023] Figure 13 shows an example of a MAC frame header.
[0024] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.
[0025] Figure 15 illustrates an example of the basic operation method of the DSO.
[0026] Figure 16 illustrates an example of the DSO Subband Indication Parameters field format.
[0027] Figure 17 illustrates Example 1 of performing DSO Subband Negotiation between DSO STA and AP.
[0028] Figure 18 illustrates Example 2 of performing DSO Subband Negotiation between DSO STA and AP.
[0029] Figure 19 illustrates an example of a Transition Timeout when performing DSO Subband Negotiation between a DSO STA and an AP.
[0030] FIG. 20 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.
[0031] FIG. 21 is a flowchart illustrating the operation of a receiving device according to the present embodiment.
[0032] FIG. 22 is a flowchart illustrating a procedure for transmitting a management frame containing information regarding the DSO mode according to the present embodiment.
[0033] FIG. 23 is a flowchart illustrating a procedure for receiving a management frame containing information regarding a DSO mode according to the present embodiment.
[0034] In this specification, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”
[0035] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B, or C.”
[0036] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as synonymous with “at least one of A and B.”
[0037] Additionally, parentheses used in this specification may mean “for example.” Specifically, when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be proposed as an example of “control information.” In other words, the “control information” of this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be proposed as an example of “control information.” Furthermore, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be proposed as an example of “control information.”
[0038] Additionally, as used herein, “a / an” may mean “at least one” or “one or more.” Also, terms ending in “(s)” may mean “at least one” or “one or more.”
[0039] Additionally, the expressions “based on,” “on the basis of,” or “according to” as used herein mean “based at least in part on,” and do not mean “based only on one.”
[0040] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.
[0041] The following examples of this specification may be applied to various wireless communication systems. For example, the following examples of this specification may be applied to wireless local area network (WLAN) systems. For example, this specification may be applied to IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification may be applied to Ultra High Reliability (UHR) standards or next-generation wireless LAN standards that enhance IEEE 802.11bn. In addition, the examples of this specification may be applied to mobile communication systems. For example, they may be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on 3GPP (3rd Generation Partnership Project) standards.
[0042] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.
[0043] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.
[0044] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.
[0045] For example, the STA (110, 120) can perform the role of an access point (AP) or a non-AP. That is, the STA (110, 120) of this specification can perform the functions of an AP and / or a non-AP. In this specification, an AP may also be indicated as an AP STA.
[0046] The STA (110, 120) of this specification may support various communication standards other than the IEEE 802.11 standard. For example, it may support communication standards according to 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). In addition, the STA of this specification may be implemented in various devices such as mobile phones, vehicles, and personal computers. Furthermore, the STA of this specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving.
[0047] In this specification, the STA (110, 120) may include a medium access control (MAC) that complies with the provisions of the IEEE 802.11 standard and a physical layer interface for the wireless medium.
[0048] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.
[0049] The first STA (110) may include a processor (111), memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.
[0050] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0051] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (i.e., the received signal) and the signal to be transmitted through the transceiver (i.e., the transmitted signal).
[0052] For example, the second STA (120) can perform the intended operation of a Non-AP STA. For example, the non-AP transceiver (123) performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0053] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (122) of the Non-AP STA can store the signal received through the transceiver (123) (i.e., the received signal) and can store the signal to be transmitted through the transceiver (i.e., the transmitted signal).
[0054] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through 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 transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).
[0055] For example, the operation of a device indicated as non-AP (or User-STA) in the following specification may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signals of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of the device marked as non-AP is controlled by the processor (111) of the first STA (110), and the related signal can be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signal of the AP can be stored in the memory (112) of the first STA (110).
[0056] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. Additionally, in the following example, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding, etc. of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.
[0057] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.
[0058] For example, the transceiver (113, 123) shown in side drawing (b) of FIG. 1 can perform the same function as the transceiver shown in side drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) shown in side drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) shown in side drawing (b) of FIG. 1 can perform the same function as the processor (111, 121) and the memory (112, 122) shown in side drawing (a) of FIG. 1 described above.
[0059] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, User STA, network, Base Station, Node-B, AP (Access Point), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).
[0060] For example, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal being received by the transceiver (113, 123) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in side view (a) of FIG. 1 being acquired by the processor (111, 121) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in side view (b) of FIG. 1 being acquired by the processing chip (114, 124) shown in side view (b) of FIG. 1.
[0061] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.
[0062] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or a processor enhanced therefrom.
[0063] In this specification, an uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. Additionally, in this specification, a downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.
[0064] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).
[0065] The top of Figure 2 shows the structure of the basic service set (BSS) infrastructure of IEEE (Institute of Electrical and Electronic Engineers) 802.11.
[0066] The top of Figure 2 shows the structure of the basic service set (BSS) infrastructure of IEEE (Institute of Electrical and Electronic Engineers) 802.11.
[0067] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).
[0068] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.
[0069] A distributed system (210) can implement an extended service set (ESS, 240) by connecting multiple BSSs (200, 205). The term ESS (240) may be used to refer to a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) may have the same service set identification (SSID).
[0070] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) with another network (e.g., 802.X).
[0071] In a BSS like the one at the top of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).
[0072] The bottom of Fig. 2 is a conceptual diagram showing IBSS.
[0073] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity that performs management functions centrally. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and since access to the distributed system is not allowed, they form a self-contained network.
[0074] Figure 3 is a diagram illustrating a general link setup process.
[0075] In the described S310 step, the STA can perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.
[0076] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (i.e., transmit and receive probe request / response on channel 2).
[0077] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.
[0078] The STA that discovered the network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described later. The authentication process of 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 in the authentication request / response corresponds to a management frame.
[0079] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc.
[0080] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.
[0081] A successfully authenticated STA may perform an association process based on step S330. The association process includes the STA sending an association request frame to the AP, and in response, the AP sending an association response frame to the STA. For example, the association request frame may include information regarding various capabilities, beacon listen interval, service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, a connection response frame may include information related to various capabilities, status code, AID (Association ID), support rate, EDCA (Enhanced Distributed Channel Access) parameter set, RCPI (Received Channel Power Indicator), RSNI (Received Signal to Noise Indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS map, etc.
[0082] Subsequently, in step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.
[0083] FIG. 4 illustrates an example of a multi-link (ML).
[0084] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (i.e., AP STAs), and the non-AP MLD may include affiliated STAs (i.e., non-AP STAs, or user-STAs).
[0085] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the link may be configured in different bands.
[0086] The AP MLD of FIG. 4 includes three affiliated APs. In one example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In one example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Additionally, in one example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Additionally, in one example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.
[0087] In one example of FIG. 4, AP1 can initiate a multilink setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In one example of FIG. 4, non-AP STA1 can transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) shown in FIG. 4 may be the same as the AP shown in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) shown in FIG. 4 may be the same as the STA shown in FIG. 1 and / or FIG. 2 (i.e., user-STA or non-AP STA).
[0088] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.
[0089] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.
[0090] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.
[0091] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.
[0092] In FIG. 5, L-STF to UHR-LTF can be called a preamble or physical preamble and can be generated / transmitted / received / acquired / decoded at the physical layer (included in the transmitting / receiving STA).
[0093] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.
[0094] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can be set to 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 displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.
[0095] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).
[0096] The L-SIG field of FIG. 5 may contain, for example, 24 bits of bit information. For example, the 24 bits of information may 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 may contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU, or a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, or EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High-Efficiency) PPDU, the value of the Length field can be determined as "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 satisfying the condition that the remainder is zero when LENGTH is divided by 3.
[0097] For example, a (non-AP and AP) STA can apply BCC encoding based on a code rate of 1 / 2 to 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoding. BPSK modulation can be applied to the 48 bits of encoding to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. Consequently, 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 of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.
[0098] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.
[0099] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be referred to by various names such as the first SIG field, first SIG, first type SIG, control signal, control signal field, first (type) control signal, common control field, and common control signal.
[0100] U-SIG may contain N bits of information and may contain information to identify the type of EHT PPDU. For example, U-SIG may be constructed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol for U-SIG (e.g., OFDM symbol) may have a duration of 4 us. Each symbol of U-SIG may be used to transmit 26 bits of information. For example, each symbol of U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.
[0101] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers), excluding the pilot tones -21, -7, +7, and +21.
[0102] For example, A bit information (e.g., 52 un-coded bits) transmitted by U-SIG may include a CRC field (e.g., a field of 4 bits) and a tail field (e.g., a field of 6 bits). The CRC field and the tail field may be transmitted through a second symbol of U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of U-SIG and the remaining 16 bits within the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. Additionally, the tail field may be used to terminate the trellis of a convolutional decoder and may be set, for example, to "000000".
[0103] A bit information (e.g., 52 un-coded bits) transmitted by U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.
[0104] For example, the version-independent bits of U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value of the 3-bit PHY version identifier (e.g., a value of 000) may indicate that the transmitted and received PPDU is an EHT PPDU. Additionally, a second value of the 3-bit PHY version identifier (e.g., a value of 001) may indicate that the transmitted and received PPDU is a UHR PPDU.
[0105] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is a UHR PPDU based on the PHY version identifier having the second value.
[0106] 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.
[0107] For example, the version-independent bits of U-SIG may include information regarding the length of the TXOP (transmission opportunity) and information regarding the BSS color ID.
[0108] For example, if the UHR PPDU is classified into various types (e.g., type related to SU transmission (performed based on UL or DL), type related to DL transmission, type related to NDP transmission, type related to DL non-MU-MIMO, type related to DL MU-MIMO, type related to Multi-AP operation, type related to CBF (Coordinated beamforming) and SR (Spatial Reuse), type related to C-OFDMA (Coordinated OFDMA), type related to C-TDMA (Coordinated TDMA)), information regarding the type of the EHT PPDU (e.g., 2-bit or 3-bit information) may be included in the version-dependent bits of the U-SIG.
[0109] For example, U-SIG may include: 1) a bandwidth field containing information regarding bandwidth; 2) a field containing information regarding the MCS technique applied to UHR-SIG; 3) an indication field containing information regarding whether the dual subcarrier modulation (DCM) technique is applied to UHR-SIG; 4) a field containing information regarding the number of symbols used for UHR-SIG; 5) a field containing information regarding whether UHR-SIG is generated across the entire band; 6) a field containing information regarding the type of UHR-LTF / STF; and 7) information regarding a field indicating the length of UHR-LTF and CP length.
[0110] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies 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.
[0111] For example, the pattern of preamble puncturing can be pre-set. For example, when a first puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band within an 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied only to one of two secondary 20 MHz bands included in a secondary 40 MHz band within an 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, within the 160 MHz band (or 80+80 MHz band), the primary 40 MHz band included in the primary 80 MHz band is present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.
[0112] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.
[0113] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in 80 MHz units. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding a preamble puncturing pattern).
[0114] Additionally or generally, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).
[0115] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth may contain different U-SIGs.
[0116] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.
[0117] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).
[0118] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on a RU (resource unit) defined by a plurality of subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through a RU (resource unit) defined by a plurality of subcarriers / tones.
[0119] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, UHR-LTF, UHR-STF and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.
[0120] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones are inserted into the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.
[0121] Meanwhile, the RU arrangement of Fig. 6 is utilized not only for situations involving multiple users (MU) but also for situations involving a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of Fig. 4, and in this case, three DC tones can be inserted.
[0122] In the example of FIG. 6, various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., are proposed. Since the specific size of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be indicated as N-tone RU, etc. For example, 26-RU may be indicated as 26-tone RU.
[0123] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.
[0124] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.
[0125] In addition, as described, 484-RU may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.
[0126] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.
[0127] FIG. 9 illustrates the operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can establish a channel connection through contending (i.e., Backoff operation) and transmit a Trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the Trigger frame (930). When the PPDU containing the Trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.
[0128] TB PPDUs (941, 942) may be transmitted at the same time and may be transmitted from multiple STAs (e.g., User STAs) with AIDs indicated within the Trigger frame (930). The ACK frame (950) for the TB PPDU may be implemented in various forms.
[0129] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.
[0130] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency located between 2.4 and 2.5 GHz) are used / supported / defined.
[0131] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values of channel indices and center frequencies may change.
[0132] FIG. 10 illustrates four channels within a 2.4 GHz band as an example. The illustrated first frequency range (1010) to fourth frequency range (1040) may each include one channel. For example, the first frequency range (1010) may include channel 1 (a 20 MHz channel having index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency range (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency range (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency range (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.
[0133] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.
[0134] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or higher and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 may be changed.
[0135] Multiple channels within the 5 GHz band include UNII (Unlicensed National Information Infrastructure)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency regions referred to as UNII Mid and UNII-2 Extended. UNII-3 may be referred to as UNII-Upper.
[0136] Multiple channels may be configured within the 5 GHz band, and the bandwidth of each channel may be varied, such as 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 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency range may be divided into four channels through a 40 MHz frequency range. The 5170 MHz to 5330 MHz frequency range may be divided into two channels through an 80 MHz frequency range. Alternatively, the 5170 MHz to 5330 MHz frequency range may be divided into one channel through a 160 MHz frequency range.
[0137] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.
[0138] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.
[0139] For example, the 20 MHz channel of FIG. 12 can be defined starting from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 may have index 1 (or channel index, channel number, etc.), and the center frequency may be assigned as 5.945 GHz. That is, the center frequency of the index N channel may be determined as (5.940 + 0.005*N) GHz.
[0140] Accordingly, the indices (or channel numbers) of the 20 MHz channel in FIG. 12 are 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, 197, It may be 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule described above, the index of the 40 MHz channel of FIG. 12 may 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.
[0141] The structure and types / subtypes of MAC frames are described below.
[0142] FIG. 13 shows an example of a MAC frame header. As illustrated, the MAC frame may include a frame control field / information of 2 octets, a duration field / information of 2 octets, a Receiver Address (RA) field / information of 6 octets, and a Transmitter Address (TA) field / information of 6 octets. As illustrated in FIG. 13, the four fields may be consecutive. The MAC header of FIG. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.
[0143] The MAC header shown in FIG. 13 may be located at the very beginning of the MAC frame. That is, the MAC frame may include a MAC header such as that in FIG. 13 and a MAC body field / information following the MAC header. The MAC frame containing the MAC header of FIG. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) shown in FIG. 5.
[0144] MAC frames included in the data fields of the PPDU of this specification may be classified into various types. For example, MAC frames of this specification may be classified into control frames, management frames, and data frames.
[0145] For example, a management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLANs. For the management frame, the values of the type fields (B3 and B2) in FIG. 13 are set to 00. Additionally, the values of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).
[0146] For example, the control frame includes the Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLANs. For the control frame, the values of the type fields (B3 and B2) in FIG. 13 are set to 01. Also, the values of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger(0010), Beamforming Report Poll(0100), NDP Announcement(0101), Control Frame Extension(0110), Control Wrapper(0111), BlockAckReq(1000), BlockAck(1001), PS-Poll(1010), RTS(1011), CTS(1100), Ack(1101), CF-End(1110).
[0147] For example, the data frame includes (QoS) Data, (QoS) Null, etc., defined in conventional WLANs. For the management frame, the value of the type field (B3 and B2) in FIG. 13 is set to 10.
[0148] MAC frames / signals used in this specification can be identified through the type field / information and subtype field / information described above. For example, the “frame” in this specification may refer to a MAC frame in which the type bits B3 and B2 within the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 within the frame control field are set to 0010. Various MAC frames described in this specification are inserted into / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDU).
[0149] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.
[0150] The device illustrated in FIGS. 1 to 4 (e.g., AP STA, non-AP STA) can be modified as in FIG. 14. The transceiver (630) in FIG. 14 may be identical to the transceiver (113, 123) in FIG. 1. The transceiver (630) in FIG. 14 may include a receiver and a transmitter.
[0151] The processor (610) of FIG. 14 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (610) of FIG. 14 may be the same as the processing chip (114, 124) of FIG. 1.
[0152] The memory (150) of FIG. 14 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 14 may be a separate external memory different from the memory (112, 122) of FIG. 1.
[0153] Referring to FIG. 14, a power management module (611) manages power for a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.
[0154] Referring to FIG. 14, 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).
[0155] 1. Overview of DSO (Dynamic subband operation)
[0156] The present disclosure relates to Dynamic subband operation (DSO) in a WLAN system.
[0157] DSO is a mechanism that allows a DSO non-AP STA to dynamically receive frequency resources on a per-TXOP basis that are outside its operating bandwidth and within the BSS bandwidth of the DSO AP when the operating bandwidth of the DSO non-AP STA is narrower than the BSS (Basic Service Set) bandwidth of the associated DSO AP.
[0158] A non-AP STA with dot11DSOOptionActivated set to true operates as a DSO non-AP STA and sets the DSO Support field included in the UHR MAC Capabilities Information field of the UHR Capabilities element to 1. An AP with dot11DSOOptionActivated set to true operates as a DSO AP and sets the DSO Support field to 1 in the same way.
[0159] For a DSO non-AP STA, a channel that includes the BSS primary channel and has a bandwidth equal to the operating bandwidth of the STA is defined as the primary subband. Additionally, a channel located outside the primary subband, within the BSS bandwidth, and capable of resource allocation by the DSO AP during DSO frame exchange is defined as the DSO subband.
[0160] The DSO subband is determined by the operating bandwidth and BSS bandwidth of the STA. For example, if an 80 MHz operating non-AP STA operates at a 320 MHz BSS, one of the 80 MHz subbands outside the primary 80 MHz may be assigned as the DSO subband.
[0161] A DSO non-AP STA transmits a UHR OMP (Operation Mode and Parameters) request for DSO enablement, disablement, or parameter update. The UHR OMP request may include the following.
[0162] - DSO Padding Delay field: Indicates the minimum time information required to switch from the primary subband to the DSO subband.
[0163] - DSO Switching Back Delay field: Indicates the time required to return from the DSO subband to the primary subband.
[0164] - Preferred 80 MHz DSO Subband field (for 80 MHz STA in 320 MHz BSS): Indicates the preferred DSO subband.
[0165] After receiving the above UHR OMP request, the DSO AP selects a DSO subband and determines whether to enable it. If the DSO subband selected by the AP is different from the STA's preferred DSO subband, the AP notifies the STA via a UHR OMP response including the Offered 80 MHz DSO Subband field. The STA may accept or reject the subband via a UHR OMP confirm.
[0166] When DSO mode is enabled, the DSO AP transmits a Buffer Status Report Poll (BSRP) Trigger Frame as an Initial Control Frame (DSO ICF) to initiate DSO frame exchange. The DSO ICF contains the Resource Unit (RU) allocation within the DSO subband, and if the DSO non-AP STA finds that the RU is included in its DSO subband, it switches to the DSO subband and transmits an Initial Control Response (ICR).
[0167] During DSO frame exchange, the AP limits RU allocation to within the DSO subband and allocates resources based on the DSO subband in the triggering frame and DL MU PPDU. Additionally, puncturing is performed according to a predefined rule.
[0168] After the DSO frame exchange ends, the DSO non-AP STA returns to the primary subband based on the DSO Switching Back Delay field. This return is performed based on a timeout condition or a condition of not receiving an expected frame.
[0169] If the DSO subband is no longer valid due to a change in the operating bandwidth of a DSO non-AP STA or a change in the BSS bandwidth of a DSO AP, the DSO mode is disabled. On the other hand, if the DSO subband remains valid after the change, the DSO mode is maintained.
[0170] In addition, DSO APs can propose DSO subband reassignment through unsolicited UHR OMP responses, and DSO non-AP STAs can accept or reject such proposals through UHR OMP confirms.
[0171] Through such a DSO, the DSO non-AP STA can efficiently utilize frequency resources that exceed its operating bandwidth, thereby improving resource utilization efficiency and transmission performance.
[0172] 2. Method of indicating the DSO subband
[0173] This specification relates to a method of indicating a DSO subband when performing a DSO operation.
[0174] Figure 15 illustrates an example of the basic operation method of the DSO.
[0175] Currently, 802.11 is considering Dynamic Subband Operation (DSO) to overcome the problem where the AP's bandwidth cannot be fully utilized because the operating bandwidth of non-AP STAs is relatively small (e.g., 80 MHz or 160 MHz) compared to the AP's large BSS bandwidth (e.g., 160 MHz or 320 MHz). Previously, an AP with a 160 MHz BSS operating BW allocated RUs only to 80 MHz, including a primary 20 MHz channel, to two associated 80 MHz operating non-AP STAs to perform UL MU operations or DL MU transmissions. However, in practical environments, the operating BW of non-AP STAs is generally smaller than the AP's BSS operating BW, and as the AP's BSS operating BW increases further (e.g., 320 MHz), a limitation arises in that the AP's BSS operating BW cannot be fully utilized. To this end, 802.11bn proposed a DSO feature, and as shown in Fig. 15, from the perspective of a non-AP STA that supports and enables the DSO feature, a subband that is equal to its own operating bandwidth and includes a Primary 20MHz channel can be designated as the Primary subband, and a subband that is within the AP's BSS operating bandwidth but is not the Primary subband and is outside its own operating bandwidth can be designated as the DSO subband.
[0176] The basic operation method of DSO operation is as follows. When an AP obtains a TXOP and transmits an ICF, it can allocate a RU allocation included in the DSO subband to the RU allocation of the ICF. Non-AP STAs that receive this complete the switch to the DSO subband after a DSO subband switch delay. Within the corresponding TXOP, frame exchange is performed based on the DSO subband between the AP and the non-AP STA that has switched to the DSO subband, thereby having the advantage of fully utilizing the AP's Operating BSS bandwidth.
[0177] 1) DSO Subband Indication
[0178] Basically, as shown in Fig. 15, the ICF includes RU allocation information included in the DSO subband to which the non-AP STA will switch, and the non-AP STAs that receive the information can switch to the DSO subband.
[0179] Method 1) Fixed position for the DSO subband
[0180] A restriction rule regarding which DSO subband non-AP STAs operating with a smaller operating bandwidth within the AP's BSS bandwidth can switch to can be defined as follows.
[0181] 1) A 20MHz operating STA has S20 (secondary 20 MHz) as the DSO subband.
[0182] 2) An 80MHz operating STA has S80 (secondary 80MHz) as its DSO subband.
[0183] 3) A 160MHz operating STA has S160 (secondary 80MHz) as its DSO subband.
[0184] This method has the advantage of being simple in terms of ease of implementation and AP scheduling by having a fixed position for the DSO subband.
[0185] Method 2) DSO subband indication based on the operating bandwidth of the Non-AP STA
[0186] Figure 16 illustrates an example of the DSO Subband Indication Parameters field format.
[0187] On the other hand, STA can announce or indicate DSO Subband Indication Parameters fields including at least the field shown in FIG. 16.
[0188] - Presence bitmap for 20 / 80 / 160MHz STA: This field indicates whether or not the DSO Subband Indication for 20MHz STA, DSO Subband Indication for 80MHz STA, and DSO Subband Indication for 160MHz STA are included. For example, assuming it has a 4-bit value, each bit from the lowest bit to the highest bit indicates whether the DSO Subband Indication for 20 / 80 / 160MHz STA is included, and in the case of 1110, it indicates that the DSO Subband for 20MHz STA, DSO Subband for 80MHz STA, and DSO Subband for 160MHz STA are all included.
[0189] - DSO subband for 20MHz STA: This field indicates the number of a channel (e.g., 20MHz channel) within the BSS bandwidth of the AP that STAs operating at 20MHz switch to in order to perform DSO operations. For example, assuming this field has 8 bits, if you want to use a 20MHz channel with channel number 36 as the DSO subband, it can be represented as 36.
[0190] Additionally or alternatively, the channel number can be set based on Country elements and operating classes as shown in Table 1. For example, to determine the DSO subband among 20 MHz channels, a 20 MHz channel with channel number 36 can be determined.
[0191] OperatingclassGlobaloperatingclassChannelstartingfrequency(GHz)Channelspacing(MHz)LC IFChannelstartingfrequency(MHz)Channel setChannelnumber ofthe centerfrequencyBehavior limits set1115520-15436,40,44,48-Applicable toLC2118520-15452,56,60,64-DFS_50_100_Behavior, Applicable toLC3124520149,153,157,161-NomadicBehavior4121520100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144-DFS_50_100_Behavior, UseEirpForVHTTxPowEnv5125520149, 153, 157, 161, 165-LicenseExemptBehavior61034.937551, 2, 3, 4, 5, 6, 7, 8, 9, 10-71034.937551, 2, 3, 4, 5, 6, 7, 8, 9, 10-81024.891011, 13, 15, 17, 19-91024.891011, 13, 15, 17, 19-101014.852021, 25-111014.852021, 25-12812.407251, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11-LicenseExemptBehavior13943.00020133, 137-CCAOCSEDBehavior14953.00010132, 134, 136, 138-CCAOCSEDBehavior15963.00255131, 132, 133, 134, 135, 136, 137, 138-CCAOCSEDBehavior
[0192] Additionally or alternatively, the field can be represented as a bitmap, and when it has an 8-bit value (it may also be composed of 16 bits), for an AP operating at 160 MHz, it can be represented as 0000 0001, indicating that the last 20 MHz from the lowest to the highest frequency is the DSO subband.
[0193] Additionally or alternatively, if a requirement is defined that the DSO subband is determined within the AP's secondary (BSS operating BW / 2) MHz, an 8-bit bitmap can indicate the DSO subband of a BSS operating BW of up to 320 MHz. For example, if the 8-bit bitmap is 0000 0001, for an AP with a BSS operating BW of 320 MHz, the highest 20 MHz channel from lowest to highest frequency within the secondary 160 MHz can be indicated as the DSO subband.
[0194] - DSO subband for 80MHz STA: This field indicates the number of a channel (e.g., 80MHz channel) within the BSS bandwidth of the AP that STAs operating at 80MHz switch to in order to perform DSO operations. For example, assuming this field has 8 bits, if you want to use an 80MHz channel with channel number 42 as the DSO subband, it can be represented as 42.
[0195] Additionally or alternatively, the channel number can be set based on Country elements and operating classes as shown in Table 1 above. For example, to determine the DSO subband among 80 MHz channels, an 80 MHz channel with channel number 42 can be determined.
[0196] Additionally or alternatively, the field can be represented as a bitmap, and when it has a value of 4 bits (it may be composed of 8 bits), for an AP operating at 160 MHz, it can be represented as 0001 to indicate that the last 80 MHz is the DSO subband based on the lowest to highest frequency.
[0197] Additionally or alternatively, the field can be represented as a bitmap, and when it has a value of 4 bits (it may also be composed of 8 bits), for an AP operating at 320 MHz, when represented as 0100, it can indicate that the secondary 80 MHz is the DSO subband based on the lowest to highest frequency.
[0198] Additionally, the field can exist only when the AP is configured with a BSS operating BW of 160 MHz or higher.
[0199] - DSO subband for 160MHz STA: This field indicates the number of a channel (e.g., 160MHz channel) within the BSS bandwidth of the AP that STAs operating at 160MHz switch to in order to perform DSO operations. For example, if this field has 4 bits, when you want to use a 160MHz channel with channel number 50 as the DSO subband, you can represent it as 50.
[0200] Additionally or alternatively, the channel number can be set based on Country elements and operating classes as shown in Table 1 above. For example, to determine the DSO subband among 160 MHz channels, a 160 MHz channel with channel number 50 can be determined.
[0201] Additionally or alternatively, the field can be represented as a bitmap, and when it has a value of 4 bits (it may also be composed of 8 bits), for an AP operating at 320 MHz, when represented as 0001, it can indicate that the last 160 MHz (secondary 160 MHz) based on the lowest to highest frequency is the DSO subband.
[0202] Additionally, the field may exist only when the AP is configured with a BSS operating BW of 320 MHz or higher.
[0203] Additionally or alternatively, STAs may transmit at least one of the fields described above in the DSO Subband Indication Parameters.
[0204] Additionally or alternatively, the Presence bitmap for 20 / 80 / 160MHz STA field may not be included. For example, a non-AP STA may transmit including one of the aforementioned fields depending on its operating bandwidth. For example, a non-AP STA operating with an 80MHz operating bandwidth may transmit including only the DSO subband for 80MHz STA field, and the receiving AP can determine that the transmitted field is the DSO subband for 80MHz STA field because it knows that the non-AP STA's operating bandwidth is 80MHz.
[0205] Method 3) Integrated DSO subband indication
[0206] As shown in Table 2, there may be an integrated DSO subband indication method.
[0207] Operating Bandwidth of STA (2 bits) Secondary Channel Indication (2 bits) DSO subband indication (4 bits) Description 0000 reserved Indicates that the DSO subband of the 20MHz operating STAs is 20MHz with a higher frequency within the secondary 40MHz 00010001 Indicates that the DSO subband of the 20MHz operating STAs is 20MHz with a lower frequency within the secondary 40MHz 00100001 20MHz operating indicates that the DSO subband of the STAs is 20MHz with the highest frequency within the secondary 80MHz 0010001 20MHz operating indicates that the DSO subband of the STAs is 20MHz with the second highest frequency within the secondary 80MHz 0010010020MHz operating indicates that the DSO subband of the STAs is secondary Indicates that the DSO subband of the 20MHz operating STAs has the third highest frequency within 80MHz. Indicates that the DSO subband of the 80MHz operating STAs has the lowest frequency within 80MHz. Indicates that the DSO subband of the 80MHz operating STAs has the highest frequency within 160MHz. Indicates that the DSO subband of the 80MHz operating STAs has the lowest frequency within 160MHz.Indicates that the DSO subband of the 160MHz operating STAs is secondary 160MHz. Indicates that the secondary (its own operating bandwidth) MHz is the DSO subband according to each operating bandwidth. (Method 1)
[0208] - Operating Bandwidth of STA: This field indicates the operating bandwidth of the STA and can have a value of 2 bits. For example, 00 indicates information for a 20MHz operating STA, 01 indicates information for an 80MHz operating STA, and 10 indicates information for a 160MHz operating STA. If the value is 11, the remaining fields (Secondary Channel Indication and DSO subband Indication fields) may be reserved, in which case it may indicate that the DSO subband position is Secondary (its own operating bandwidth) (Method 1).
[0209] - Secondary Channel Indication: This field indicates which secondary channel contains the DSO subband and can have a value of 2 bits. For example, 00 indicates that the DSO subband is contained within the secondary 20 MHz; 01 indicates that the DSO subband is contained within the secondary 40 MHz; 10 indicates that the DSO subband is contained within the secondary 80 MHz; and 11 indicates that the DSO subband is contained within the secondary 160 MHz.
[0210] Additionally or alternatively, together with the field of the Operating Bandwidth of STA described above, it can be interpreted differently as follows. For example, if the Operating Bandwidth of STA is 01, the case where the Secondary Channel Indication value is 00 or 01 is meaningless; therefore, if the Secondary Channel Indication value is 00, it indicates that the DSO subband is included within the Secondary 80MHz, and if it is 01, it indicates that the DSO subband is included within the Secondary 160MHz. That is, depending on the value of the Operating Bandwidth of STA, the interpretation of the Secondary Channel Indication value from the lowest value to the highest value can indicate that it is included within the Secondary XMHz (where X is greater than or equal to the value of the Operating Bandwidth of STA, starting from the same value and increasing by a factor of two).
[0211] - DSO Subband Indication: This field can indicate the exact location of a DSO subband within the Secondary Channel Indication and can have a value of 4 bits. When it has a value of 4 bits, the unit of one bit can be determined according to the value of the Operating Bandwidth of STA field. For example, if the Operating Bandwidth of STA field is 01 and the Secondary Channel Indication is 11, it indicates that the DSO subband for an 80 MHz operating STA is included within the Secondary 160 MHz channel. Each bit of the DSO Subband Indication field represents an 80 MHz unit (depending on the Operating Bandwidth of STA) within the Secondary 160 MHz channel from the lowest bit to the highest bit, and if it is 0001, it can indicate an 80 MHz unit with a higher frequency within the Secondary 160 MHz channel, and if it is 0010, it can indicate an 80 MHz unit with a lower frequency within the Secondary 160 MHz channel.
[0212] - DSO Mode: This indicates whether the DSO operation operates based on TXOP or SP (Service Period). For example, if the field is 1 bit, a value of 0 indicates TXOP-based operation, meaning the DSO operation runs until the TXOP obtained by the AP based on the ICF ends; a value of 1 indicates SP-based operation, meaning the DSO operation runs beyond the TXOP for a specific service period. In other words, this field determines whether the duration of the DSO operation is set based on TXOP or SP.
[0213] 2) DSO Subband Negotiation
[0214] The negotiation process can be carried out based on the aforementioned DSO Subband Indication. For example, a 20MHz operating STA can negotiate which 20MHz DSO subband to switch to within the 80MHz BSS BW. Based on this, non-AP STAs can perform flexible switching considering their channel conditions. Furthermore, from the AP's perspective, there is the advantage of facilitating scheduling to prevent multiple non-AP STAs from converging on a single channel. The negotiation process may include at least one of the following pieces of information.
[0215] - Preferred DSO Subband: This field indicates which secondary channel is desired to switch to within the BSS BW. This field can have an 8-bit value and can be configured based on Country elements and operating classes as shown in Table 1 above. For example, if an 80MHz operating STA prefers a DSO subband with channel number 42, the value of Preferred DSO Subband can be set to 42.
[0216] Additionally or alternatively, the field can be represented as a bitmap, and its length may vary depending on the operating BW. For example, the field may have a 16-bit value for a 20MHz operating STA and a 4-bit value for an 80MHz operating STA. If an 80MHz operating STA operates at a 320MHz BSS BW, it can transmit a bitmap with a value of 1 for the position corresponding to the 80MHz channel it wishes to switch to. For example, to switch to the secondary 80MHz channel, it can transmit a bitmap set to 0100, and to switch to the lower 80MHz channel of the secondary 160MHz channel, it can transmit a bitmap set to 0010 to convey information about its preferred DSO suband to the AP.
[0217] - Offered DSO Subband: This field indicates the DSO Subband offered by the AP based on the Preferred DSO Subband requested within the BSS BW. This field can have an 8-bit value and can be configured based on Country elements and operating classes as shown in Table 1 above. For example, if an 80MHz operating STA wants to DSO subband with channel number 42, the value of Offered DSO Subband can be set to 42.
[0218] Additionally or alternatively, the field can be represented as a bitmap, and its length may vary depending on the operating BW. For example, the field may have a 16-bit value for a 20MHz operating STA and a 4-bit value for an 80MHz operating STA. When an AP with a 320MHz BSS BW transmits to an 80MHz operating STA, it can transmit the data by setting the bit value to 1 for the position corresponding to the 80MHz channel to which the AP wishes to switch the STA. For example, if the AP wishes to switch to the secondary 80MHz channel, it can transmit a bitmap set to 0100, and if it wishes to switch to the lower 80MHz channel of the secondary 160MHz channel, it can transmit a bitmap set to 0010 to convey information about the DSO subband recommended or preferred by the AP to the STA.
[0219] - DSO Subband Setup Command: Indicates the type of command to negotiate the corresponding DSO Subband. When it has a 3-bit value, it can be set to the value shown in Table 3 below. For example, if an STA requesting a DSO Subband sets the values of Preferred DSO Subband and DSO Subband Setup Command to 0, this means that it is requesting a DSO Subband that has the value of Preferred DSO Subband.
[0220] To negotiate a DSO subband, a negotiation frame (referred to herein as the DSO Subband Negotiation Initiation frame (DIF) and DSO Subband Negotiation Response frame (DRF)) is defined.
[0221] Additionally or alternatively, the Negotiation frame may be transmitted by being included in the OMP (Operating Mode Parameters) Request frame and OMP Response frame used when enabling Mode for various features defined in 802.11bn.
[0222] The interpretation and combination of DSO Subband Setup Commands included in DIF and DRF can be defined based on Table 4 below.
[0223] Additionally or alternatively, if the Preferred DSO Subband and the Offered DSO Subband are identical, the Offered DSO Subband may not be included. For example, if the AP accepts the Preferred DSO Subband included in the DIF as is, the Offered DSO Subband may not be included in the DRF.
[0224] Additionally or alternatively, the Preferred DSO Subband and Offered DSO Subband can be transmitted with the same value.
[0225] DSO Subband Setup Command Command Name Description 0 Request Indicates that the SchedulingSTA requests an Offered DSO Subband without including the Preferred DSO Subband. 1 Suggest Indicates that the SchedulingSTA includes the Preferred DSO Subband and is willing to accept other Preferred DSO Subbands if the Preferred DSO Subband is unavailable. 2 Demand Indicates that the SchedulingSTA includes the Preferred DSO Subband and will not accept other Offered DSO Subbands if the Preferred DSO Subband is unavailable. 3 Accept Indicates that the SchedulingSTA accepts / allows the Preferred DSO Subband, whether included or not. 4 Alternate Indicates that the SchedulingSTA proposes an Offered DSO Subband other than the proposed Preferred DSO Subband. 5 Dictate Indicates that the SchedulingSTA proposes an Offered DSO Subband Info other than the proposed Preferred DSO Subband. 6 Reject Indicates that the SchedulingSTA [is] the proposed Preferred Indicates that the DSO Subband is rejected.
[0226] DSO Subband Negotiation Initiation frame (DIF) DSO Subband Negotiation Response frame (DRF) DSO Subband Negotiation after the completion exchange of DIF and DRF Request, Suggest, or Demand No frame transmitted No new Schedule Setup occurs. Demand Schedule Accept Includes the meaning that the Preferred DSO Subband included in the Schedule DIF is accepted; the Preferred DSO Subband and Offered DSO Subband values transmitted from the DIF may be set identically and included in the DRF. Additionally, if the command of the DRF is Accept, the Offered DSO Subband may not be transmitted. Suggest or Request Schedule Accept Although the Preferred DSO Subband may be included in the Schedule DIF, it indicates that the Offered DSO Subband included in the DRF is accepted as the DSO Subband to be switched. Demand or Suggest Schedule Alternate Proposes the Offered DSO Subband included in the Schedule DRF; a new DSO subband negotiation is not successfully completed. DSO subband negotiation can be performed by transmitting a new DIF based on the Offered DSO Subband included in the DRF. Demand or Suggest Schedule Dictate proposes the Offered DSO Subband included in the Schedule DRF, but the new DSO subband negotiation is not successfully completed.Transmit a new DIF based on the Offered DSO Subband included in the DRF to indicate that DSO Subband Negotiation will not be accepted if the Offered DSO Subband is not included in the DRF. Request, Suggest, or Demand Schedule Reject Schedule No new Schedule Setup occurs.
[0227] 3) DSO Subband Negotiation Process
[0228] Figure 17 illustrates Example 1 of performing DSO Subband Negotiation between DSO STA and AP.
[0229] Figure 17 is an example showing the negotiation process between AP and STA1 regarding a DSO subband. In Figure 17, STA1 transmits a DIF to the AP containing information that DSO Mode is enabled, the DSO subband to be switched, and information regarding the DSO subband setup command. Since the DSO subband setup command is set to 1, signifying a suggestion, and includes information about the desired DSO subband but also implies a willingness to accept other DSO subbands, the AP receiving this performs negotiation regarding the DSO subband by indicating the Offered DSO subband, which is different from the Preferred DSO subband, as 0010 and providing a DSO subband setup command to accept it, in order to schedule without making the corresponding subband too complex by considering its own channel conditions and the Preferred DSO subbands of other DSO STAs. Once negotiation for the DSO subband is complete, the DSO frame exchange is performed by allocating the RUs for the negotiated DSO subband to STA1 via the DSO ICF.
[0230] Additionally or alternatively, in the case where the AP in the DRF rejects the DSO Subband Setup Command by setting it to 6, the negotiation for the DSO Subband is not successful, and the DSO STA can transmit a new DIF by including information about the new DSO Subband in the Preferred DSO Subband.
[0231] Figure 18 illustrates Example 2 of performing DSO Subband Negotiation between DSO STA and AP.
[0232] Figure 18 is an example illustrating the negotiation process between the AP and STA1 regarding the DSO subband. In Figure 18, STA1 transmits a DIF to the AP containing information that it enables DSO Mode, the DSO subband to be switched, and the DSO subband setup command. Since the DSO subband setup command is set to 1, signifying a suggestion, and includes information about the desired DSO subband but also implies a willingness to accept other DSO subbands, the receiving AP performs negotiation on the DSO subband by setting the offered DSO subband, which is different from the preferred DSO subband, to 0010 and the DSO subband setup command, in order to schedule without overcomplicatement in the corresponding subband by considering its own channel conditions and the preferred DSO subbands of other DSO STAs. Based on this, the STA sets the DSO subband offered by the AP as the preferred DSO subband and transmits a new DIF to perform DSO negotiation. The AP that receives the DIF sends a DRF to accept it and completes the DSO Subband Negotiation. At this time, if the Preferred DSO Subband and the Offered DSO Subband are the same, the DSO Subband Setup Command is set to 3 to accept it, and the Offered DSO Subband may not be included.
[0233] Additionally or alternatively, when the STA transmits the second DIF, if it accepts the Offered DSO Subband provided by the AP as Alternate without including the Preferred DSO Subband, it may set only the DSO Subband Setup Command to 3 to mean that it accepts it, thereby enabling negotiation for the DSO subband to be performed in 3-way.
[0234] Additionally or alternatively, when the STA transmits the second DIF, it may reject the Offered DSO Subband indicated by Alternate, in which case negotiation for the DSO Subband is not successful, and the above process may be repeated.
[0235] Figure 19 illustrates an example of a Transition Timeout when performing DSO Subband Negotiation between a DSO STA and an AP.
[0236] As shown in Fig. 19, the Transition Timeout can begin from the time the STA receives an ACK from the AP after transmitting the DIF (or from the time the AP transmits the ACK). If the STA does not receive a DRF for the DIF from the AP within the Transition Timeout, the STA may retransmit the DIF after the Transition Timeout expires. In other words, the DSO operation may not be performed until a successful DRF is received, and the DSO operation may be performed after a successful 2-way negotiation process for DIF / ACK / DRF / ACK is completed. This timeout procedure can compensate for the disadvantage of STA1 wasting the channel by continuously transmitting DIFs unnecessarily, and has the advantage of allowing the DSO operation to be performed by negotiating the DSO Subband even when channel conditions are poor or the AP is unable to transmit the DRF for any reason.
[0237] Additionally or alternatively, if the STA does not receive a DRF from the AP within the Transition Timeout after transmitting the DIF, it may perform a DSO operation based on the information transmitted in the DIF.
[0238] Additionally or alternatively, if the AP fails to transmit the DRF within the Transition Timeout, it can perform a DSO operation based on the DIF information received from the STA.
[0239] STA and AP can perform DSO operations based on the information of the DIF transmitted by STA at the time when the Transition Timeout ends.
[0240] Additionally or alternatively, if the AP transmits the DRF within the Transition Timeout, the STA and the AP can receive / transmit the DRF, and then the AP receives the ACK transmitted by the STA, and the STA can perform a DSO operation based on the time when the ACK was transmitted.
[0241] Additionally or alternatively, if Negotiation is performed in 3-way (in the case of DIF / DRF / DCFM (DSO Subband Confirmation)), Transition Timeout may not be applied.
[0242] When the STA transmits a DIF to the AP, the AP transmits a DRF to the STA, and the STA confirms (e.g., Accept or Reject) based on the information in the DRF transmitted by the AP, the Transition Timeout may not be applied because the information transmitted by the AP may be necessary for the STA. In other words, negotiation for the DSO Subband can only occur when the frame exchange for the 3-way negotiation is successfully completed.
[0243] <STA의 동작과정>
[0244] - STA can be a non-AP STA or AP
[0245] <Transmission Process>
[0246] In the present disclosure, the first STA may transmit a PPDU containing at least one frame containing at least one of the following information to another STA when a Critical Update occurs for the first STA or when a Critical Update occurs for a second STA belonging to the same MLD as the first STA.
[0247] Additionally, a frame can be a Beacon, Probe Response, (Re)Association Response frame, or Action frame.
[0248] The first piece of information can be the CUF (Critical Update Flag).
[0249] => The CUF can be a UCUF (UHR CUF) considering the next generations, and can be 1 for the CU (Critical Update) of the UHR feature. Additionally, the UCUF can be indicated using the Capability Information field or the reserved field of the Extended Capabilities element.
[0250] => Additionally, or alternatively, a CUF can be added for each Generation.
[0251] The second piece of information can be BPCC (BSS Parameters Change Count).
[0252] => The BPCC for the first STA may be included in the Per-STA Profile corresponding to the first STA of the Common Info or Link Info of the Basic ML (Multi-Link) IE (Information Element) for each Generation or integrally.
[0253] => The BPCC for the second STA may be included in the TBTT (Target Beacon Transmission Time) Information field corresponding to the second STA of the RNR (Reduced Neighbor Report) IE, either for each Generation or collectively.
[0254] The third piece of information can be Updated Parameters.
[0255] => Updated Parameters for the first STA may be included in the Per-STA Profile corresponding to the first STA of Common Info or Link Info.
[0256] => Updated Parameters for the second STA may be included in the Per-STA Profile corresponding to the second STA in Link Info. Additionally or alternatively, when Updated Parameters are included, the All Updates Included field of the RNR IE corresponding to the second STA may be reused and set to 1, or the UHR All Updates Included may be additionally included and set to 1.
[0257] => Additionally or alternatively, Updated Parameters may be included up to the point in time based on the next DTIM Beacon of the first STA or the Updated Parameters.
[0258] Additionally, updated parameters can be included in the frame only when updated based on at least one of the conditions presented above. In other words, they may not be included in the frame while the update is complete and the parameter's value is maintained.
[0259] <Reception Process>
[0260] In the present disclosure, an STA that receives Critical Update information from an STA can perform frame detection and obtain information on parameters related to the Critical Update through frame detection.
[0261] FIG. 20 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.
[0262] An example of FIG. 20 can be performed on a transmitting STA or a transmitting device (AP and / or non-AP STA).
[0263] Some of the steps (or detailed sub-steps described later) of the example in FIG. 20 may be omitted or changed.
[0264] Through step S2010, the transmitting device (transmitting STA) can obtain information regarding the above-described Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.
[0265] Through step S2020, the transmitting device can construct / generate a PPDU based on acquired control information. The step of constructing / generating the PPDU may include the step of constructing / generating each field of the PPDU. That is, step S2020 includes the step of constructing a UHR-SIG field containing control information regarding a Tone Plan. That is, step S4520 may include the step of constructing a field containing control information (e.g., N bitmap) indicating the size / location of the RU and / or the step of constructing a field containing an identifier (e.g., AID) of the STA receiving the RU.
[0266] Additionally, step S2020 may include the step of generating an STF / LTF sequence transmitted through a specific RU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence.
[0267] Additionally, the S2020 step may include the step of generating a data field (i.e., MPDU) transmitted through a specific RU.
[0268] The transmitting device can transmit the PPDU configured through step S2020 to the receiving device based on step S2030.
[0269] While performing step S2030, the transmitting device may perform at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, GI insertion, etc.
[0270] A signal / field / sequence configured according to the present specification can be transmitted in the form of FIG. 5.
[0271] FIG. 21 is a flowchart illustrating the operation of a receiving device according to the present embodiment.
[0272] The above-described PPDU can be received according to an example of FIG. 21.
[0273] An example of FIG. 21 can be performed on a receiving STA or a receiving device (AP and / or non-AP STA).
[0274] Some of the steps (or detailed sub-steps described later) of each example in FIG. 21 may be omitted.
[0275] A receiving device (receiving STA) can receive all or part of the PPDU through step S2110. The received signal may be in the form of FIG. 5.
[0276] The sub-step of step S2110 can be determined based on step S2030 of FIG. 20. That is, step S2110 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insert operation applied in step S2030.
[0277] In step S2120, the receiving device can perform decoding of all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.
[0278] More specifically, the receiving device can decode the L-SIG and UHR-SIG of the PPDU based on the Legacy STF / LTF and obtain information contained in the L-SIG and UHR-SIG fields. Information regarding various Tone Plans (i.e., RU) described in this specification may be included in the UHR-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the UHR-SIG.
[0279] In step S2130, the receiving device can decode the remainder of the PPDU based on information regarding the Tone Plan (i.e., RU) obtained through step S2120. For example, the receiving STA can decode the STF / LTF fields of the PPDU based on information regarding the one Plan (i.e., RU). Additionally, the receiving STA can decode the data fields of the PPDU based on information regarding the Tone Plan (i.e., RU) and obtain the MPDU contained in the data fields.
[0280] Additionally, the receiving device can perform a processing operation to transmit the decoded data through step S2130 to an upper layer (e.g., MAC layer). Furthermore, if the generation of a signal is instructed from the upper layer to the PHY layer in response to the data transmitted to the upper layer, a subsequent operation can be performed.
[0281] Hereinafter, the above-described embodiment will be explained with reference to FIGS. 1 to 21.
[0282] FIG. 22 is a flowchart illustrating a procedure for transmitting a management frame containing information regarding the DSO mode according to the present embodiment.
[0283] An example of FIG. 22 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0284] This embodiment proposes a method for indicating whether a DSO operates based on TXOP or SP by transmitting information regarding the DSO mode through a management frame. In addition, this embodiment proposes a method for negotiating DSO subbands in an unsolicited manner through the management frame.
[0285] In step S2210, the second STA (station) transmits a management frame to the first STA.
[0286] In step S2220, the second STA performs frame exchange with the second STA and the DSO (Dynamic Subband Operation) subband based on the management frame.
[0287] The above management frame includes information regarding the DSO mode. The information regarding the DSO mode indicates whether the frame exchange will be performed during the TXOP (Transmission Opportunity) or SP (Service Period).
[0288] The first STA may receive an Initial Control Frame (ICF) from the second STA in the primary subband. The first STA may switch from the primary subband to the DSO subband during the padding duration indicated by the ICF. The first STA may transmit an Initial Control Response (ICR) in the DSO subband to the second STA. (Alternatively, the second STA may transmit an Initial Control Frame (ICF) in the primary subband to the first STA. The second STA may receive an Initial Control Response (ICR) in the DSO subband from the first STA.) In this case, the ICF may be called a DSO ICF and may be transmitted as a Buffer Status Report Poll (BSRP) trigger frame. The ICR may be called a DSO ICR. The above frame exchange may be an exchange of the DSO ICF and the DSO ICR.
[0289] The primary subband may be configured (or defined) as a channel that has the same bandwidth as the operating bandwidth of the first STA and includes a Basic Service Set (BSS) primary channel. The DSO subband may be configured (or defined) as a channel located outside the primary subband and included within the BSS bandwidth of the second STA. The DSO subband may also have the same bandwidth as the operating bandwidth of the first STA, and the first STA may be allocated resources from the second STA during the frame exchange in the DSO subband.
[0290] The first STA above may be called a DSO non-AP (non-access point) STA that supports DSO, and the second STA above may be called a DSO AP that supports DSO.
[0291] Information regarding the above DSO mode may be set or instructed as follows.
[0292] For example, based on the information regarding the DSO mode being set to a first value (e.g., 0), the frame exchange in the DSO subband during the TXOP obtained through the ICF may be performed. Based on the information regarding the DSO mode being set to a second value (e.g., 1), the frame exchange in the DSO subband during the SP may be performed regardless of the TXOP obtained through the ICF.
[0293] According to the present embodiment, by transmitting information regarding the DSO mode through a management frame, it is possible to clearly indicate whether the DSO operates based on TXOP or based on SP. Through this, the possibility of inconsistency in interpretation regarding the DSO operation method between non-AP STA and AP can be reduced, and the predictability of DSO operation and operational consistency can be improved.
[0294] Furthermore, according to the present embodiment, since DSO subbands can be negotiated in an unsolicited manner using the management frame, the AP can adaptively reconfigure DSO subbands for the terminal without a separate request procedure. Accordingly, it is possible to respond quickly to changes in the channel environment, traffic load changes, or interference situations, and there is an effect of reducing resource allocation delays and improving overall system spectrum efficiency.
[0295] Furthermore, the above method enables flexible resource management while reducing control signaling overhead, thereby providing the effect of mitigating performance degradation in multi-link or high-density network environments.
[0296] The above ICF may include information regarding the allocation of a Resource Unit (RU). The above ICR may be transmitted through a RU within the DSO subband indicated in the information regarding the allocation of the RU.
[0297] An example of the case where the above management frame is transmitted in a solicited manner is as follows.
[0298] The first STA can transmit a DIF (DSO Subband Negotiation Initiation Frame) to the second STA. (Additionally, the second STA can receive a DIF (DSO Subband Negotiation Initiation Frame) from the first STA.) At this time, the management frame can be set as a DRF (DSO Subband Negotiation Response Frame) requested by the DIF.
[0299] The above DIF may include at least one of information regarding DSO support, information regarding a preferred DSO subband, and information regarding a command to negotiate the DSO subband. If the first STA is the DSO non-AP STA, the information regarding DSO support may be set to a first value (e.g., 1). If the first STA is not the DSO non-AP STA, the information regarding DSO support may be set to a second value (e.g., 0).
[0300] The above DIR may include at least one of information about the offered DSO subband and information about the command to negotiate the DSO subband.
[0301] Information regarding the preferred DSO subband can be set as a first bitmap indicating the DSO subband preferred by the first STA. The length of the first bitmap can be determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA.
[0302] For example, when the operating bandwidth of the first STA is 80 MHz and the BSS bandwidth of the second STA is 320 MHz, the DSO subband is set to one of a plurality of 80 MHz subbands located outside the primary subband, so the first bitmap can be set to 4 bits. For example, if the first bitmap is 0100, the preferred DSO subband may be a secondary 80 MHz channel; if the first bitmap is 0010, the preferred DSO subband may be an 80 MHz channel with a lower frequency among secondary 160 MHz channels; and if the first bitmap is 0001, the preferred DSO subband may be an 80 MHz channel with a higher frequency among secondary 160 MHz channels.
[0303] The information regarding the DSO subband provided above may be set as a second bitmap indicating the DSO subband provided by the second STA based on the DSO subband preferred by the first STA. The length of the second bitmap may be determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA.
[0304] For example, if the operating bandwidth of the first STA is 20 MHz and the BSS bandwidth of the second STA is 320 MHz, the DSO subband is set to one of a plurality of 20 MHz subbands located outside the primary subband, so the first bitmap can be set to 16 bits. For example, if the first bitmap is 0100 0000 0000 0000, the provided DSO subband may be a secondary 20 MHz channel, if the first bitmap is 0010 0000 0000 0000, the provided DSO subband may be a 20 MHz channel with a lower frequency among secondary 40 MHz channels, and if the first bitmap is 0001 0000 0000 0000, the provided DSO subband may be a 20 MHz channel with a higher frequency among secondary 40 MHz channels.
[0305] Information regarding the command to negotiate the above DSO subband can be specified by Table 3 above.
[0306] For example, based on the fact that information regarding a command to negotiate the DSO subband is set to a first value, the DIF may request information regarding the provided DSO subband without including information regarding the preferred DSO subband (Request Scheduling).
[0307] For example, based on the information regarding the command to negotiate the DSO subband being set to a second value, the DIF may include information regarding the preferred DSO subband and information that other DSO subbands may be accepted if the preferred DSO subband is not possible (Suggest Scheduling).
[0308] For example, based on the information regarding the command to negotiate the DSO subband being set to a third value, the DIF may include information regarding the preferred DSO subband and information that other DSO subbands are not accepted if the preferred DSO subband is not available (Demand Scheduling).
[0309] For example, based on the information regarding the command to negotiate the DSO subband being set to a fourth value, the DIR may include information that it accepts a provided DSO subband different from the preferred DSO subband (Accept Scheduling).
[0310] For example, based on the information regarding the command to negotiate the DSO subband being set to a fifth value, the DIR may include information that it proposes a provided DSO subband different from the preferred DSO subband (Alternate Scheduling or Dictate Scheduling).
[0311] For example, based on the information regarding the command to negotiate the DSO subband being set to the sixth value, the DIR may include information that the preferred DSO subband is rejected (Reject Scheduling).
[0312] The above DIF may be a UHR OMP (operating mode and parameter) request frame, and the above DIF may be a UHR OMP response frame. Additionally, the first STA may transmit a UHR OMP confirm frame based on the UHR OMP response frame to the second STA.
[0313] After the execution of the above frame exchange is completed, the first STA can switch back from the DSO subband to the primary subband.
[0314] As another example, the DSO subband may have a fixed position based on the operating bandwidth of the first STA. For example, if the operating bandwidth of the first STA is 20 MHz, the DSO subband may be a secondary 20 MHz channel. If the operating bandwidth of the first STA is 80 MHz, the DSO subband may be a secondary 80 MHz channel. If the operating bandwidth of the first STA is 160 MHz, the DSO subband may be a secondary 160 MHz channel.
[0315] As another example, the management frame may further include a DSO subband indication parameter field. The DSO subband indication parameter field may include an existence bitmap for the first STA and a DSO subband field for the first STA. The existence bitmap for the first STA may indicate whether a DSO subband field for the first STA exists when the operating bandwidth of the first STA is 20 / 80 / 160 MHz. The DSO subband field for the first STA may indicate the channel number or location of the DSO subband when the operating bandwidth of the first STA is 20 / 80 / 160 MHz.
[0316] FIG. 23 is a flowchart illustrating a procedure for receiving a management frame containing information regarding a DSO mode according to the present embodiment.
[0317] An example of FIG. 23 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0318] This embodiment proposes a method for indicating whether a DSO operates based on TXOP or SP by transmitting information regarding the DSO mode through a management frame. In addition, this embodiment proposes a method for negotiating DSO subbands in an unsolicited manner through the management frame.
[0319] In step S2310, the first STA (station) receives a management frame from the second STA.
[0320] In step S2320, the first STA performs frame exchange with the second STA in the DSO (Dynamic Subband Operation) subband based on the management frame.
[0321] The above management frame includes information regarding the DSO mode. The information regarding the DSO mode indicates whether the frame exchange will be performed during the TXOP (Transmission Opportunity) or SP (Service Period).
[0322] The first STA may receive an Initial Control Frame (ICF) from the second STA in the primary subband. The first STA may switch from the primary subband to the DSO subband during the padding duration indicated by the ICF. The first STA may transmit an Initial Control Response (ICR) in the DSO subband to the second STA. (Alternatively, the second STA may transmit an Initial Control Frame (ICF) in the primary subband to the first STA. The second STA may receive an Initial Control Response (ICR) in the DSO subband from the first STA.) In this case, the ICF may be called a DSO ICF and may be transmitted as a Buffer Status Report Poll (BSRP) trigger frame. The ICR may be called a DSO ICR. The above frame exchange may be an exchange of the DSO ICF and the DSO ICR.
[0323] The primary subband may be configured (or defined) as a channel that has the same bandwidth as the operating bandwidth of the first STA and includes a Basic Service Set (BSS) primary channel. The DSO subband may be configured (or defined) as a channel located outside the primary subband and included within the BSS bandwidth of the second STA. The DSO subband may also have the same bandwidth as the operating bandwidth of the first STA, and the first STA may be allocated resources from the second STA during the frame exchange in the DSO subband.
[0324] The first STA above may be called a DSO non-AP (non-access point) STA that supports DSO, and the second STA above may be called a DSO AP that supports DSO.
[0325] Information regarding the above DSO mode may be set or instructed as follows.
[0326] For example, based on the information regarding the DSO mode being set to a first value (e.g., 0), the frame exchange in the DSO subband during the TXOP obtained through the ICF may be performed. Based on the information regarding the DSO mode being set to a second value (e.g., 1), the frame exchange in the DSO subband during the SP may be performed regardless of the TXOP obtained through the ICF.
[0327] According to the present embodiment, by transmitting information regarding the DSO mode through a management frame, it is possible to clearly indicate whether the DSO operates based on TXOP or based on SP. Through this, the possibility of inconsistency in interpretation regarding the DSO operation method between non-AP STA and AP can be reduced, and the predictability of DSO operation and operational consistency can be improved.
[0328] Furthermore, according to the present embodiment, since DSO subbands can be negotiated in an unsolicited manner using the management frame, the AP can adaptively reconfigure DSO subbands for the terminal without a separate request procedure. Accordingly, it is possible to respond quickly to changes in the channel environment, traffic load changes, or interference situations, and there is an effect of reducing resource allocation delays and improving overall system spectrum efficiency.
[0329] Furthermore, the above method enables flexible resource management while reducing control signaling overhead, thereby providing the effect of mitigating performance degradation in multi-link or high-density network environments.
[0330] The above ICF may include information regarding the allocation of a Resource Unit (RU). The above ICR may be transmitted through a RU within the DSO subband indicated in the information regarding the allocation of the RU.
[0331] An example of the case where the above management frame is transmitted in a solicited manner is as follows.
[0332] The first STA can transmit a DIF (DSO Subband Negotiation Initiation Frame) to the second STA. (Additionally, the second STA can receive a DIF (DSO Subband Negotiation Initiation Frame) from the first STA.) At this time, the management frame can be set as a DRF (DSO Subband Negotiation Response Frame) requested by the DIF.
[0333] The above DIF may include at least one of information regarding DSO support, information regarding a preferred DSO subband, and information regarding a command to negotiate the DSO subband. If the first STA is the DSO non-AP STA, the information regarding DSO support may be set to a first value (e.g., 1). If the first STA is not the DSO non-AP STA, the information regarding DSO support may be set to a second value (e.g., 0).
[0334] The above DIR may include at least one of information about the offered DSO subband and information about the command to negotiate the DSO subband.
[0335] Information regarding the preferred DSO subband can be set as a first bitmap indicating the DSO subband preferred by the first STA. The length of the first bitmap can be determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA.
[0336] For example, when the operating bandwidth of the first STA is 80 MHz and the BSS bandwidth of the second STA is 320 MHz, the DSO subband is set to one of a plurality of 80 MHz subbands located outside the primary subband, so the first bitmap can be set to 4 bits. For example, if the first bitmap is 0100, the preferred DSO subband may be a secondary 80 MHz channel; if the first bitmap is 0010, the preferred DSO subband may be an 80 MHz channel with a lower frequency among secondary 160 MHz channels; and if the first bitmap is 0001, the preferred DSO subband may be an 80 MHz channel with a higher frequency among secondary 160 MHz channels.
[0337] The information regarding the DSO subband provided above may be set as a second bitmap indicating the DSO subband provided by the second STA based on the DSO subband preferred by the first STA. The length of the second bitmap may be determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA.
[0338] For example, if the operating bandwidth of the first STA is 20 MHz and the BSS bandwidth of the second STA is 320 MHz, the DSO subband is set to one of a plurality of 20 MHz subbands located outside the primary subband, so the first bitmap can be set to 16 bits. For example, if the first bitmap is 0100 0000 0000 0000, the provided DSO subband may be a secondary 20 MHz channel, if the first bitmap is 0010 0000 0000 0000, the provided DSO subband may be a 20 MHz channel with a lower frequency among secondary 40 MHz channels, and if the first bitmap is 0001 0000 0000 0000, the provided DSO subband may be a 20 MHz channel with a higher frequency among secondary 40 MHz channels.
[0339] Information regarding the command to negotiate the above DSO subband can be specified by Table 3 above.
[0340] For example, based on the fact that information regarding a command to negotiate the DSO subband is set to a first value, the DIF may request information regarding the provided DSO subband without including information regarding the preferred DSO subband (Request Scheduling).
[0341] For example, based on the information regarding the command to negotiate the DSO subband being set to a second value, the DIF may include information regarding the preferred DSO subband and information that other DSO subbands may be accepted if the preferred DSO subband is not possible (Suggest Scheduling).
[0342] For example, based on the information regarding the command to negotiate the DSO subband being set to a third value, the DIF may include information regarding the preferred DSO subband and information that other DSO subbands are not accepted if the preferred DSO subband is not available (Demand Scheduling).
[0343] For example, based on the information regarding the command to negotiate the DSO subband being set to a fourth value, the DIR may include information that it accepts a provided DSO subband different from the preferred DSO subband (Accept Scheduling).
[0344] For example, based on the information regarding the command to negotiate the DSO subband being set to a fifth value, the DIR may include information that it proposes a provided DSO subband different from the preferred DSO subband (Alternate Scheduling or Dictate Scheduling).
[0345] For example, based on the information regarding the command to negotiate the DSO subband being set to the sixth value, the DIR may include information that the preferred DSO subband is rejected (Reject Scheduling).
[0346] The above DIF may be a UHR OMP (operating mode and parameter) request frame, and the above DIF may be a UHR OMP response frame. Additionally, the first STA may transmit a UHR OMP confirm frame based on the UHR OMP response frame to the second STA.
[0347] After the execution of the above frame exchange is completed, the first STA can switch back from the DSO subband to the primary subband.
[0348] As another example, the DSO subband may have a fixed position based on the operating bandwidth of the first STA. For example, if the operating bandwidth of the first STA is 20 MHz, the DSO subband may be a secondary 20 MHz channel. If the operating bandwidth of the first STA is 80 MHz, the DSO subband may be a secondary 80 MHz channel. If the operating bandwidth of the first STA is 160 MHz, the DSO subband may be a secondary 160 MHz channel.
[0349] As another example, the management frame may further include a DSO subband indication parameter field. The DSO subband indication parameter field may include an existence bitmap for the first STA and a DSO subband field for the first STA. The existence bitmap for the first STA may indicate whether a DSO subband field for the first STA exists when the operating bandwidth of the first STA is 20 / 80 / 160 MHz. The DSO subband field for the first STA may indicate the channel number or location of the DSO subband when the operating bandwidth of the first STA is 20 / 80 / 160 MHz.
[0350] <Device Configuration>
[0351] The technical features of the present specification described above may be applied to various devices and methods. For example, the technical features of the present specification described above may be performed / supported through the device of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above may be applied only to parts of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above may be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and memory (112, 122) of FIG. 1, or based on the processor (610) and memory (620) of FIG. 14. For example, the device of the present specification receives a management frame from a second STA (station); and performs frame exchange with the second STA and the DSO (Dynamic Subband Operation) subband based on the management frame.
[0352] The technical features of this specification may be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable medium comprising instructions based on execution by at least one processor.
[0353] The above CRM may store instructions for performing operations including the step of receiving a management frame from a second STA (station); and the step of performing frame exchange between the second STA and the DSO (Dynamic Subband Operation) subband based on the management frame. Instructions stored in the CRM of this specification may be executed by at least one processor. At least one processor associated with the CRM of this specification may be the processor (111, 121) or processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 14. Meanwhile, the CRM of this specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 14, or a separate external memory / storage medium / disk, etc.
[0354] The technical features of the present specification described above are applicable to various applications or business models. For example, the technical features described above may be applied for wireless communication in devices supporting Artificial Intelligence (AI).
[0355] Artificial intelligence refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems addressed within the field of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.
[0356] An Artificial Neural Network (ANN) is a model used in machine learning that can refer to any model capable of problem-solving, composed of artificial neurons (nodes) that form a network through the connection of synapses. An artificial neural network can be defined by connection patterns between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.
[0357] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer may include one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron may output a function value of an activation function for input signals, weights, and biases input through the synapses.
[0358] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters, on the other hand, refer to parameters that must be set prior to training in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.
[0359] The objective of training an artificial neural network can be viewed as determining model parameters that minimize the loss function. The loss function can be used as an indicator to determine optimal model parameters during the training process of an artificial neural network.
[0360] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.
[0361] Supervised learning refers to a method of training an artificial neural network with labels provided for the training data; a label can refer to the correct answer (or result) that the neural network must infer when the training data is input. Unsupervised learning refers to a method of training an artificial neural network without labels provided for the training data. Reinforcement learning refers to a learning method in which an agent defined within an environment is trained to select an action or sequence of actions that maximizes the cumulative reward in each state.
[0362] Machine learning implemented using a Deep Neural Network (DNN) that includes multiple hidden layers among artificial neural networks is also called Deep Learning, and Deep Learning is a part of Machine Learning. Hereinafter, Machine Learning is used in a sense that includes Deep Learning.
[0363] In addition, the aforementioned technical features can be applied to the wireless communication of robots.
[0364] A robot can refer to a machine that automatically processes or operates a given task based on its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions can be called an intelligent robot.
[0365] Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, and propellers in their drive units, enabling them to drive on the ground or fly in the air.
[0366] In addition, the aforementioned technical features can be applied to devices that support augmented reality.
[0367] Extended Reality is a collective term for Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on real-world images, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.
[0368] MR technology is similar to AR technology in that it displays real-world objects and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual objects and real-world objects are used as equals in MR technology.
[0369] XR technology can be applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.
[0370] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.
Claims
1. In a wireless LAN system, The first STA (station) receives a management frame from the second STA; and The above first STA includes the step of performing frame exchange with the second STA in the DSO (Dynamic Subband Operation) subband based on the management frame, wherein The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). method.
2. In Paragraph 1, The first STA receives an ICF (Initial Control Frame) from the second STA in the primary subband; The first STA switches from the primary subband to the DSO subband during a padding duration indicated by the ICF; and The above first STA further includes the step of transmitting an ICR (Initial Control Response) in the DSO subband to the second STA, wherein The above primary subband has a bandwidth equal to the operating bandwidth of the first STA and is configured as a channel including a BSS (Basic Service Set) primary channel, and The above DSO subband is configured as a channel located outside the above primary subband and included within the BSS bandwidth of the above second STA. method.
3. In Paragraph 2, Based on the information regarding the above DSO mode being set to a first value, the frame exchange is performed in the DSO subband during the TXOP obtained through the ICF, and Based on the information regarding the above DSO mode being set to a second value, the frame exchange is performed in the DSO subband during the SP regardless of the TXOP obtained through the ICF. method.
4. In Paragraph 2, The above ICF includes information regarding RU (Resource Unit) allocation, and The above ICR is transmitted through the RU within the DSO subband indicated in the information regarding the RU allocation. method.
5. In Paragraph 1, The above-mentioned first STA further includes the step of transmitting a DIF (DSO Subband Negotiation Initiation Frame) to the above-mentioned second STA, wherein The above management frame is set as the DRF (DSO Subband Negotiation Response Frame) requested to the above DIF, and The above DIF includes at least one of information regarding DSO support, information regarding a preferred DSO subband, and information regarding a command to negotiate the DSO subband. The above DIR includes at least one of information regarding an offered DSO subband and information regarding a command to negotiate the DSO subband. method.
6. In Paragraph 5, Information regarding the preferred DSO subband is set as a first bitmap indicating the DSO subband preferred by the first STA, and The length of the first bitmap is determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA, and The information regarding the DSO subband provided above is set as a second bitmap indicating the DSO subband provided by the second STA based on the DSO subband preferred by the first STA, and The length of the second bitmap is determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA. method.
7. In Paragraph 5, Based on the fact that information regarding a command to negotiate the above DSO subband is set to a first value, the DIF requests information regarding the provided DSO subband without including information regarding the preferred DSO subband, and Based on the information regarding the command to negotiate the above DSO subband being set to a second value, the DIF includes information regarding the preferred DSO subband and information that if the preferred DSO subband is not possible, other DSO subbands may also be accepted. Based on the information regarding the command to negotiate the above DSO subband being set to a third value, the DIF includes information regarding the preferred DSO subband and information that if the preferred DSO subband is not possible, other DSO subbands are not accepted, and Based on the information regarding the command to negotiate the above DSO subband being set to a fourth value, the DIR includes information that it accepts a provided DSO subband different from the preferred DSO subband, and Based on the fact that information regarding the command to negotiate the above DSO subband is set to a fifth value, the above DIR includes information that it proposes a provided DSO subband different from the above preferred DSO subband, and Based on the information regarding the command to negotiate the DSO subband being set to the sixth value, the DIR includes information that it rejects the preferred DSO subband. method.
8. In Paragraph 1, After the above frame exchange is completed, The above first STA further includes the step of switching from the DSO subband to the primary subband. method.
9. In a wireless LAN system, the first STA (station) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Receive a management frame from the 2nd STA; and Frame exchange is performed in the second STA and the DSO (Dynamic Subband Operation) subband based on the above management frame, The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). 1st STA.
10. In wireless LAN systems, The second STA (station) transmits a management frame to the first STA; and The above second STA includes the step of performing frame exchange with the second STA in the DSO (Dynamic Subband Operation) subband based on the management frame, wherein The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). method.
11. In Paragraph 10, The second STA transmits an Initial Control Frame (ICF) to the first STA in the primary subband; and The above second STA further includes the step of receiving an ICR (Initial Control Response) from the first STA in the DSO subband, wherein The above DSO subband is configured as a channel located outside the above primary subband and included within the BSS bandwidth of the above second STA, and The above primary subband has a bandwidth equal to the operating bandwidth of the first STA and is configured as a channel including a BSS (Basic Service Set) primary channel. method.
12. In Paragraph 11, Based on the information regarding the above DSO mode being set to a first value, the frame exchange is performed in the DSO subband during the TXOP obtained through the ICF, and Based on the information regarding the above DSO mode being set to a second value, the frame exchange is performed in the DSO subband during the SP regardless of the TXOP obtained through the ICF. method.
13. In Paragraph 11, The above ICF includes information regarding RU (Resource Unit) allocation, and The above ICR is received through the RU within the DSO subband indicated in the information regarding the RU allocation. method.
14. In Paragraph 10, The above second STA further includes the step of receiving a DIF (DSO Subband Negotiation Initiation Frame) from the above first STA, wherein The above management frame is set as the DRF (DSO Subband Negotiation Response Frame) requested to the above DIF, and The above DIF includes at least one of information regarding DSO support, information regarding a preferred DSO subband, and information regarding a command to negotiate the DSO subband. The above DIR includes at least one of information regarding an offered DSO subband and information regarding a command to negotiate the DSO subband. method.
15. In Paragraph 14, Information regarding the preferred DSO subband is set as a first bitmap indicating the DSO subband preferred by the first STA, and The length of the first bitmap is determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA, and The information regarding the DSO subband provided above is set as a second bitmap indicating the DSO subband provided by the second STA based on the DSO subband preferred by the first STA, and The length of the second bitmap is determined based on the operating bandwidth of the first STA and the BSS bandwidth of the second STA. method.
16. In Paragraph 14, Based on the fact that information regarding a command to negotiate the above DSO subband is set to a first value, the DIF requests information regarding the provided DSO subband without including information regarding the preferred DSO subband, and Based on the information regarding the command to negotiate the above DSO subband being set to a second value, the DIF includes information regarding the preferred DSO subband and information that if the preferred DSO subband is not possible, other DSO subbands may also be accepted. Based on the information regarding the command to negotiate the above DSO subband being set to a third value, the DIF includes information regarding the preferred DSO subband and information that if the preferred DSO subband is not possible, other DSO subbands are not accepted, and Based on the information regarding the command to negotiate the above DSO subband being set to a fourth value, the DIR includes information that it accepts a provided DSO subband different from the preferred DSO subband, and Based on the fact that information regarding the command to negotiate the above DSO subband is set to a fifth value, the above DIR includes information that it proposes a provided DSO subband different from the above preferred DSO subband, and Based on the information regarding the command to negotiate the DSO subband being set to the sixth value, the DIR includes information that it rejects the preferred DSO subband. method.
17. In a wireless LAN system, the second STA (station) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Transmit a management frame to the 1st STA; and Frame exchange is performed in the second STA and the DSO (Dynamic Subband Operation) subband based on the above management frame, The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). 2nd STA.
18. At least one computer-readable medium comprising an instruction based on execution by at least one processor, The step of receiving a management frame from the second STA (station); and The method includes the step of performing frame exchange in the second STA and the DSO (Dynamic Subband Operation) subband based on the above management frame, wherein The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). Recording media.
19. In a device in a wireless LAN system, Memory; and The processor comprises the above memory and operablely coupled thereto, wherein the processor is: Receive a management frame from the second STA (station); and Frame exchange is performed in the second STA and the DSO (Dynamic Subband Operation) subband based on the above management frame, The above management frame includes information regarding the DSO mode, and The information regarding the above DSO mode indicates whether the frame exchange will be performed during a TXOP (Transmission Opportunity) or SP (Service Period). device.
