Method and apparatus for performing TWT operation of multi-link device in wireless LAN system

Abstract

Disclosed are a method and an apparatus for performing a TWT operation of a multi-link device in a wireless LAN system. A method performed by a first MLD, according to an embodiment of the present disclosure, may comprise the steps of: receiving, by a first STA belonging to the first MLD, a first frame from a first AP belonging to a second MLD and operating in a first band, wherein the first frame includes information regarding one or more TWT schedules related to a second AP belonging to the second MLD and operating in a second band different from the first band; and on the basis of the information regarding the one or more TWT schedules, performing, by a second STA belonging to the first MLD, transmission and / or reception of a frame with the second AP belonging to the second MLD.

Description

Method and device for performing TWT operation of a multi-link device in a wireless LAN system

[0001] The present disclosure relates to a method and device for performing a target wake time (TWT) operation of a multi-link device (MLD) in a wireless local area network (WLAN) system.

[0002] New technologies have been introduced for wireless local area networks (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and reduce latency. Among WLAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, recently introduced technologies for WLANs include enhancements for Very High Throughput (VHT) in the 802.11ac standard and enhancements for High Efficiency (HE) in the IEEE 802.11ax standard.

[0003] To provide a more advanced wireless communication environment, improved technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for Multiple Input Multiple Output (MIMO), which supports increased bandwidth, efficient utilization of multiple bands, and increased spatial streams, and for coordination of multiple access points (APs), are being studied. In particular, various technologies are being studied to support low latency or real-time traffic. Furthermore, new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions of EHT technology.

[0004] The technical problem of the present disclosure is to provide a method and device for performing a target wake time (TWT) operation of a multi-link device (MLD).

[0005] In addition, an additional technical problem of the present disclosure is to provide a method for transmitting and receiving TWT information for one or more APs (e.g., APs operating in a millimeter wave (mmWave) band) belonging to an access point (AP) station MLD, and a device therefor.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007] A method performed by a first multi-link device (MLD) according to one aspect of the present disclosure may include: receiving, by a first station (STA) belonging to the first MLD, a first frame from a first access point (AP) belonging to a second MLD and operating in a first band, the first frame including information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band; and performing, by a second STA belonging to the first MLD, transmission and / or reception of a frame with the second AP belonging to the second MLD based on the information about the one or more TWT schedules.

[0008] A method performed by a second multi-link device (MLD) according to an additional aspect of the present disclosure may include: transmitting, by a first access point (AP) belonging to the second MLD and operating in a first band, a first frame to a first station (STA) belonging to the first MLD, the first frame including information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band; and performing, by the second AP belonging to the second MLD, transmission and / or reception of a frame with a second STA belonging to the first MLD based on the information about the one or more TWT schedules.

[0009] According to the present disclosure, signaling overhead can be reduced by instead transmitting TWT scheduling information for one or more APs (e.g., APs operating in the millimeter wave (mmWave) band) belonging to an AP STA MLD.

[0010] In addition, according to the present disclosure, linkage (i.e., multi-link setup) and frame exchange between APs and STAs operating in the millimeter wave (mmWave) band within the MLD can be performed, so that wireless transmission and reception efficiency can be improved.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0012] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0013] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0014] FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

[0015] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

[0016] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0017] FIG. 5 is a diagram for explaining a CSMA / CA-based frame transmission operation to which the present disclosure can be applied.

[0018] FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

[0019] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0020] FIG. 8 is a drawing illustrating an example of an individual TWT operation to which the present disclosure can be applied.

[0021] FIG. 9 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.

[0022] FIG. 10 illustrates the format of a TWT element in a wireless communication system to which the present disclosure can be applied.

[0023] Figure 11 exemplarily shows the structure of an ML element to which the present disclosure can be applied.

[0024] FIG. 12 illustrates the format of a TIM element in a wireless communication system to which the present disclosure can be applied.

[0025] FIG. 13 illustrates an AP MLD and a non-AP MLD supporting the mmWave band according to one embodiment of the present disclosure.

[0026] FIG. 14 illustrates a discovery and multi-link setup process for multi-link operation in a wireless communication system to which the present disclosure can be applied.

[0027] FIG. 15 illustrates the format of a per-STA profile subelement within a multi-link element in a wireless communication system to which the present disclosure may be applied.

[0028] FIG. 16 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0029] FIG. 17 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0030] FIG. 18 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0031] FIG. 19 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0032] FIG. 20 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0033] FIG. 21 illustrates a TWT membership negotiation process according to one embodiment of the present disclosure.

[0034] FIG. 22 illustrates the operation of a multi-link device for performing a TWT operation according to one embodiment of the present disclosure.

[0035] FIG. 23 illustrates the operation of a multi-link device for performing a TWT operation according to one embodiment of the present disclosure.

[0036] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0037] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0038] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0039] In this disclosure, terms such as "first," "second," etc. are used only to distinguish one component from another, are not used to limit the components, and do not limit the order or importance of components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0040] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0041] The examples of the present disclosure can be applied to various wireless communication systems. For example, the examples of the present disclosure can be applied to a wireless LAN system. For example, the examples of the present disclosure can be applied to a wireless LAN based on the IEEE 802.11a / g / n / ac / ax / be standards. Furthermore, the examples of the present disclosure can be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard. Additionally, the examples of the present disclosure can be applied to a wireless LAN based on the next-generation standard after IEEE 802.11bn. Furthermore, the examples of the present disclosure can be applied to a cellular wireless communication system. For example, the examples of the present disclosure can be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series of technologies and the 5G NR (New Radio) series of technologies of the 3rd Generation Partnership Project (3GPP) standard.

[0042] Below, technical features to which examples of the present disclosure can be applied are described.

[0043] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0044] The first device (100) and the second device (200) illustrated in FIG. 1 may be replaced with various terms such as a terminal, a wireless device, a WTRU (Wireless Transmit Receive Unit), a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an MSS (Mobile Subscriber Unit), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), or simply a user. In addition, the first device (100) and the second device (200) may be replaced with various terms such as an access point (AP), a BS (Base Station), a fixed station, a Node B, a BTS (Base Transceiver System), a network, an AI (Artificial Intelligence) system, an RSU (road side unit), a repeater, a router, a relay, a gateway, etc.

[0045] The devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs). For example, the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, in the present disclosure, the STAs (110, 200) may perform the functions of an AP and / or a non-AP. When the STAs (110, 200) perform an AP function, they may simply be referred to as APs, and when the STAs (110, 200) perform a non-AP function, they may simply be referred to as STAs. In addition, in the present disclosure, the APs may also be referred to as AP STAs.

[0046] Referring to FIG. 1, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless LAN technologies (e.g., IEEE 802.11 series). The first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.11 standard.

[0047] In addition, the first device (100) and the second device (200) may additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than wireless LAN technology. In addition, the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

[0048] A first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0049] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0050] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0051] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0052] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0053] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0054] For example, one of the STAs (100, 200) may perform the intended operation of an AP, and the other of the STAs (100, 200) may perform the intended operation of a non-AP STA. For example, the transceivers (106, 206) of FIG. 1 may perform transmission and reception operations of signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.11a / b / g / n / ac / ax / be / bn, etc.). In addition, in the present disclosure, operations in which various STAs generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals may be performed in the processors (102, 202) of FIG. 1. For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include 1) an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of a field (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU, 2) an operation for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (104, 204) of FIG. 1.

[0055] Hereinafter, downlink (DL) refers to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. can be transmitted and received through the downlink. In downlink communication, the transmitter may be part of an AP STA, and the receiver may be part of a non-AP STA. Uplink (UL) refers to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. can be transmitted and received through the uplink. In uplink communication, the transmitter may be part of a non-AP STA, and the receiver may be part of an AP STA.

[0056] FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

[0057] The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports transparent STA mobility to the upper layer can be provided. A Basic Service Set (BSS) corresponds to a basic building block of a wireless LAN. FIG. 2 illustrates, by way of example, the existence of two BSSs (BSS1 and BSS2) and the inclusion of two STAs as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). The oval representing a BSS in FIG. 2 can also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). When an STA moves outside of a BSA, it cannot directly communicate with other STAs within the BSA.

[0058] If we do not consider the DS illustrated in Figure 2, the most basic type of BSS in a wireless LAN is an Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For example, assuming other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4, can be representative examples of an IBSS, respectively. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, in this type of WLAN, a LAN can be configured when needed rather than being planned in advance, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems (DS) is not permitted, forming a self-contained network.

[0059] An STA's membership in a BSS can dynamically change, for example, when an STA is turned on or off, or when an STA enters or leaves a BSS area. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services in the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may involve the use of a Distribution System Service (DSS).

[0060] In a wireless LAN, the direct STA-to-STA distance can be limited by PHY performance. While this distance limit may be sufficient in some cases, communication between STAs over longer distances may be required in other cases. To support extended coverage, a distributed system (DS) can be configured.

[0061] DS refers to a structure in which BSSs are interconnected. Specifically, a BSS may exist as an extended component of a network composed of multiple BSSs, as illustrated in Figure 2. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, the Wireless Medium (WM) and DSM can be logically distinguished. Each logical medium is used for a different purpose and by different components. These media are neither limited to being identical nor limited to being different. This logical difference between multiple media explains the flexibility of the WLAN architecture (DS architecture or other network architectures). In other words, the WLAN architecture can be implemented in various ways, and the physical characteristics of each implementation can independently specify the WLAN architecture.

[0062] A DS can support mobile devices by providing seamless integration of multiple BSSs and the logical services necessary to handle addresses to destinations. Additionally, a DS may further include a component called a portal, which acts as a bridge for connecting wireless LANs to other networks (e.g., IEEE 802.X).

[0063] An AP is an entity that enables access to a DS through a WM for associated non-AP STAs and also has the functionality of an STA. Data movement between a BSS and a DS can be performed through an AP. For example, STA2 and STA3 illustrated in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS. In addition, since all APs are basically STAs, all APs are addressable entities. The address used by an AP for communication on a WM and the address used by an AP for communication on a DSM do not necessarily have to be the same. A BSS consisting of an AP and one or more STAs can be referred to as an infrastructure BSS.

[0064] Data transmitted from one of the STA(s) associated with an AP to the STA address of that AP may always be received on an uncontrolled port and processed by an IEEE 802.1X port access entity. In addition, if the controlled port is authenticated, the transmitted data (or frame) may be forwarded to the DS.

[0065] In addition to the structure of the DS described above, an extended service set (ESS) may be established to provide wider coverage.

[0066] An ESS is a network of arbitrary size and complexity, consisting of DSs and BSSs. An ESS may correspond to a set of BSSs connected to a DS. However, an ESS does not include a DS. An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs within an ESS can communicate with each other, and mobile STAs can move from one BSS to another (within the same ESS) transparently to the LLC. APs within an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is the identifier of the BSS.

[0067] In a wireless LAN system, no assumptions are made about the relative physical locations of BSSs, and all of the following configurations are possible: BSSs can be partially overlapping, which is commonly used to provide continuous coverage. BSSs can also be physically disconnected, and there is no logical distance limit between them. BSSs can also be physically co-located, which can be used to provide redundancy. Furthermore, one (or more) IBSS or ESS networks can physically co-exist with one (or more) ESS networks. This can occur in cases where an ad-hoc network operates at the same location as an ESS network, where physically overlapping wireless networks are configured by different organizations, or where two or more different access and security policies are required at the same location.

[0068] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

[0069] For an STA to set up a link and transmit and receive data on a network, it must first discover the network, perform authentication, establish an association, and complete security authentication procedures. The link setup process can also be referred to as the session initiation process or session setup process. Furthermore, the discovery, authentication, association, and security setup processes of the link setup process can be collectively referred to as the association process.

[0070] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning operations by the STA. That is, for the STA to access a network, it must search for available networks. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning.

[0071] Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation including an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover any APs in the vicinity while moving between channels and waits for a response. The responder transmits a probe response frame in response to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, the AP transmits the beacon frame, so the AP becomes the responder. In the IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not fixed. 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 (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0072] Although not shown in Figure 3, the scanning operation can also be performed in a passive scanning manner. In passive scanning, the STA performing the scanning moves between channels and waits for a beacon frame. A beacon frame is one of the management frames defined in IEEE 802.11. It announces the existence of a wireless network and is periodically transmitted so that the STA performing the scanning can find the wireless network and participate in the wireless network. In the BSS, the AP performs the role of periodically transmitting the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the STA performing the scanning receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. The STA receiving the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel to perform scanning on the next channel in the same manner. Comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

[0073] After the STA discovers the network, an authentication process may be performed in 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 below.

[0074] The authentication process involves the STA sending an authentication request frame to the AP, and the AP responding by sending an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0075] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group. These are just some examples of information that may be included in an authentication request / response frame, and may be replaced with other information or include additional information.

[0076] An STA can send an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

[0077] After the STA is successfully authenticated, an association process may be performed in step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA.

[0078] For example, the association request frame may include information about various capabilities, a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, an RSN, a mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, the association response frame may include information about various capabilities, a status code, an Association ID (AID), supported rates, an Enhanced Distributed Channel Access (EDCA) parameter set, a Received Channel Power Indicator (RCPI), a Received Signal to Noise Indicator (RSNI), a mobility domain, a timeout interval (e.g., an association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a Quality of Service (QoS) map, etc. These are just some examples of information that may be included in a combined request / response frame, and may be replaced by other information or include additional information.

[0079] After the STA successfully joins the network, a security setup process may be performed in step S340. The security setup process in step S340 may be referred to as an authentication process through a Robust Security Network Association (RSNA) request / response, the authentication process in step S320 may be referred to as a first authentication process, and the security setup process in step S340 may also be referred to simply as an authentication process.

[0080] The security setup process of step S340 may include, for example, a process of establishing a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame. Furthermore, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.

[0081] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0082] In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). The CSMA / CA mechanism, also known as the Distributed Coordination Function (DCF) of the IEEE 802.11 MAC, essentially employs a "listen before talk" access mechanism. According to this type of access mechanism, the AP and / or STA may perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time period (e.g., a DCF Inter-Frame Space (DIFS)) before starting transmission. If the sensing result determines that the medium is in an idle state, the AP and / or STA may start transmitting frames through the medium. On the other hand, if the medium is detected to be occupied or busy, the AP and / or STA may not start its own transmission, but may wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit frames. By applying a random backoff period, multiple STAs are expected to attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.

[0083] In addition, the IEEE 802.11 MAC protocol provides the Hybrid Coordination Function (HCF). The HCF is based on the DCF and the Point Coordination Function (PCF). The PCF is a polling-based synchronous access method that periodically polls all receiving APs and / or STAs to ensure that they receive data frames. In addition, the HCF has the Enhanced Distributed Channel Access (EDCA) and the HCF Controlled Channel Access (HCCA). The EDCA is a contention-based access method for a provider to provide data frames to multiple users, while the HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, the HCF includes a medium access mechanism to improve the Quality of Service (QoS) of the wireless LAN, and can transmit QoS data in both the Contention Period (CP) and the Contention Free Period (CFP).

[0084] Referring to Fig. 4, an operation based on a random backoff period is described. When a medium that was occupied / busy changes to an idle state, multiple STAs can attempt to transmit data (or frames). To minimize collisions, each STA can select a random backoff count, wait for the corresponding slot time, and then attempt transmission. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​in the range of 0 to CW. Here, CW is a contention window parameter value. The CW parameter is given an initial value of CWmin, but can take a value doubled in case of transmission failure (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, data transmission can be attempted while maintaining the CWmax value until data transmission is successful, and if data transmission is successful, it is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are 2. n It is desirable to set it to -1 (n=0, 1, 2, ...).

[0085] Once the random backoff process begins, the STA continues to monitor the medium while counting down the backoff slots according to the determined backoff count value. If the medium is monitored as occupied, the countdown stops and waits. When the medium becomes idle, the remaining countdown resumes.

[0086] In the example of FIG. 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit a frame if it confirms that the medium is idle for DIFS. The remaining STAs monitor the medium for occupied / busy states and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can count down the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS if the medium is monitored as idle. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. In other words, this example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission. STA1 and STA5 briefly stop counting down and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, they can start transmitting frames after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time is shorter than STA1's, STA5 starts transmitting frames. While STA2 occupies the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS, counts down according to its selected random backoff count value, and then starts transmitting frames. In the example of Figure 4, the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failure in data transmission.In this case, STA4 and STA5 can select a random backoff count value and perform a countdown after doubling the CW value. STA1 waits while the medium is occupied by transmissions from STA4 and STA5, and when the medium becomes idle, it waits for DIFS and can start transmitting frames after the remaining backoff time elapses.

[0087] As in the example of Fig. 4, a data frame is a frame used for transmitting data forwarded to a higher layer, and can be transmitted after a backoff performed after DIFS elapses from when the medium becomes idle. Additionally, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS elapses, such as DIFS or PIFS (Point coordination function IFS). Subtype frames of a management frame include a beacon, an association request / response, a re-association request / response, a probe request / response, and an authentication request / response. A control frame is a frame used to control access to the medium. The subtype frames of the control frame include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), Null Data Packet Announcement (NDP), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after a backoff performed after the DIFS (Direct Inverse Frame Stop) has elapsed, and if it is a response frame to the previous frame, it is transmitted without a backoff performed after the SIFS (short IFS). The type and subtype of the frame can be identified by the type field and subtype field in the Frame Control (FC) field.

[0088] A QoS (Quality of Service) STA can transmit a frame after a backoff performed after the AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed. Here, the frames for which AIFS[i] can be used can be data frames, management frames, and also control frames that are not response frames.

[0089] FIG. 5 is a diagram for explaining a CSMA / CA-based frame transmission operation to which the present disclosure can be applied.

[0090] As mentioned above, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, in which STAs directly sense the medium. Virtual carrier sensing is intended to address potential issues in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of an STA can utilize a Network Allocation Vector (NAV). The NAV is a value that an STA that is currently using or has the right to use the medium indicates to other STAs the remaining time until the medium becomes available. Therefore, the value set as NAV corresponds to the period during which the STA transmitting the frame is scheduled to use the medium, and an STA receiving the NAV value is prohibited from accessing the medium during that period. For example, the NAV can be set based on the value of the "duration" field in the MAC header of the frame.

[0091] In the example of FIG. 5, it is assumed that STA1 wants to transmit data to STA2, and STA3 is in a position to overhear some or all of the frames transmitted and received between STA1 and STA2.

[0092] In order to reduce the possibility of collisions in transmissions of multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA1 may correspond to a hidden node for STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA2 may correspond to a hidden node for STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0093] Specifically, STA1 can determine whether a channel is occupied through carrier sensing. In terms of physical carrier sensing, STA1 can determine channel occupancy idleness based on the energy level or signal correlation detected in the channel. Furthermore, in terms of virtual carrier sensing, STA1 can determine the channel occupancy status using a network allocation vector (NAV) timer.

[0094] STA1 can transmit an RTS frame to STA2 after performing a backoff if the channel is idle during the DIFS. STA2 can transmit a CTS frame, which is a response to the RTS frame, to STA1 after an SIFS if it receives the RTS frame.

[0095] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can use the duration information contained in the RTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can use the duration information contained in the CTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame). That is, if STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0096] If STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the CTS frame is completely received. If STA2 successfully receives the data frame, it can transmit an ACK frame in response to the data frame to STA1 after SIFS. STA3 can determine whether the channel is in use through carrier sensing if the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during the DIFS after the NAV timer expires, it can attempt channel access after a contention window (CW) based on a random backoff has elapsed.

[0097] FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

[0098] The PHY layer can prepare an MPDU (MAC PDU) to be transmitted based on an instruction or primitive (meaning a set of instructions or parameters) from the MAC layer. For example, when a command requesting the start of transmission of the PHY layer is received from the MAC layer, the PHY layer can switch to transmission mode and transmit the information (e.g., data) provided by the MAC layer in the form of a frame. In addition, when the PHY layer detects a valid preamble of the received frame, it monitors the header of the preamble and sends a command to the MAC layer notifying the start of reception of the PHY layer.

[0099] In this way, information transmission / reception in a wireless LAN system is done in the form of frames, and for this purpose, the PHY layer Protocol Data Unit (PPDU) format is defined.

[0100] A basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field. The most basic (e.g., non-HT (High Throughput) as illustrated in FIG. 7) PPDU format may consist of only the Legacy-STF (L-STF), Legacy-LTF (L-LTF), Legacy-SIG (L-SIG) fields, and a Data field. Additionally, depending on the type of PPDU format (e.g., HT-mixed format PPDU, HT-greenfield format PPDU, VHT (Very High Throughput) PPDU, etc.), additional (or different types of) RL-SIG, U-SIG, non-legacy SIG field, non-legacy STF, non-legacy LTF, (i.e., xx-SIG, xx-STF, xx-LTF (e.g., xx is HT, VHT, HE, EHT, etc.)) may be included between the L-SIG field and the data field. More specific details will be described later with reference to FIG. 7.

[0101] STF is a signal for signal detection, AGC (Automatic Gain Control), diversity selection, and precise time synchronization, while LTF is a signal for channel estimation, frequency error estimation, etc. STF and LTF can be said to be signals for synchronization and channel estimation of the OFDM physical layer.

[0102] The SIG field may include various information related to PPDU transmission and reception. For example, the L-SIG field may consist of 24 bits and may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field. The RATE field may include information about the modulation and coding rate of data. For example, the 12-bit Length field may include information about 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, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, for HE PPDU, the value of the Length field can be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0103] The data field may include a SERVICE field, a Physical layer Service Data Unit (PSDU), a PPDU TAIL bit, and, if necessary, padding bits. Some bits of the SERVICE field may be used to synchronize the descrambler at the receiving end. The PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated / used by upper layers. The PPDU TAIL bit may be used to return the encoder to a 0 state. The padding bit may be used to adjust the length of the data field to a predetermined unit.

[0104] MAC PDUs are defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS). A MAC frame is composed of MAC PDUs and can be transmitted / received through the PSDU in the data portion of the PPDU format.

[0105] The MAC header includes a Frame Control field, a Duration / ID field, an Address field, etc. The Frame Control field may include control information required for frame transmission / reception. The Duration / ID field may be set to a time for transmitting the corresponding frame, etc. The Address subfields may indicate the receiver address, transmitter address, destination address, and source address of the frame, and some Address subfields may be omitted. For specific details of each subfield of the MAC header, including the Sequence Control, QoS Control, and HT Control subfields, refer to the IEEE 802.11 standard document.

[0106] The Null-Data PPDU (NDP) format refers to a PPDU format that does not include a data field. In other words, NDP refers to a frame format that includes a PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and, if additionally present, non-legacy SIG, non-legacy STF, and non-legacy LTF) in the general PPDU format, and does not include the remaining part (i.e., data field).

[0107] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0108] Standards such as IEEE 802.11a / g / n / ac / ax use various PPDU formats. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format can also be referred to as the non-HT PPDU format (Fig. 7(a)).

[0109] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format illustrated in Fig. 7(b) may be referred to as an HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format that does not include L-STF, L-LTF, and L-SIG, but consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).

[0110] An example of the VHT PPDU format (IEEE 802.11ac) includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format (Fig. 7(c)).

[0111] An example of a HE PPDU format (IEEE 802.11ax) additionally includes RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in addition to the basic PPDU format (Fig. 7(d)). Depending on specific examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-users (MUs), but the HE PPDU format for single users (SUs) does not include the HE-SIG-B. In addition, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us. For example, RL-SIG can be configured identically to L-SIG. The receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU, described later, based on the presence of RL-SIG.

[0112] The EHT PPDU format may include the EHT MU (multi-user) PPDU of FIG. 7(e) and the EHT TB (trigger-based) PPDU of FIG. 7(f). The EHT PPDU format is similar to the HE PPDU format in that it includes an RL-SIG following an L-SIG, but may include a U (universal)-SIG, an EHT-SIG, an EHT-STF, and an EHT-LTF following the RL-SIG.

[0113] The EHT MU PPDU in FIG. 7(e) corresponds to a PPDU that carries one or more data (or PSDUs) for one or more users. That is, the EHT MU PPDU can be used for both SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0114] The EHT TB PPDU of Fig. 7(f) omits the EHT-SIG compared to the EHT MU PPDU. An STA that has received a trigger for UL MU transmission (e.g., a trigger frame or TRS (triggered response scheduling)) can perform UL transmission based on the EHT TB PPDU format.

[0115] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated to allow legacy STAs to attempt demodulation and decoding, and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated to allow STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in the fields, and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

[0116] Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields may be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, Data, and PE fields may be referred to as HE modulation fields. Additionally, in the VHT PPDU format, the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields may be referred to as pre-VHT modulation fields, and the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields may be referred to as VHT modulation fields.

[0117] The U-SIG included in the EHT PPDU format of FIG. 7 can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG can have a duration of 4 us, and the U-SIG can have a total duration of 8 us. Each symbol of the U-SIG can be used to transmit 26 bits of information. For example, each symbol of the U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0118] U-SIGs can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be duplicated in 20MHz units. That is, four identical U-SIGs can be included in an 80MHz PPDU. When the bandwidth exceeds 80MHz, for example, for a 160MHz PPDU, the U-SIGs in the first 80MHz unit and the U-SIGs in the second 80MHz unit can be different.

[0119] For example, A uncoded bits may be transmitted via U-SIG, and a first symbol of U-SIG (e.g., a U-SIG-1 symbol) may transmit the first X bits of information out of a total A bits of information, and a second symbol of U-SIG (e.g., a U-SIG-2 symbol) may transmit the remaining Y bits of information out of a total A bits of information. The A bits of information (e.g., 52 uncoded bits) may include a CRC field (e.g., a field of 4 bits in length) and a tail field (e.g., a field of 6 bits in length). The tail field may be used to terminate the trellis of the convolutional decoder and may be set to 0, for example.

[0120] The A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in a new PPDU format (e.g., UHR PPDU format) not shown in FIG. 7, and in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-dependent bits can be different.

[0121] For example, the size of the version-independent bits of U-SIG can be fixed or variable. The version-independent bits can be assigned only to U-SIG-1 symbols, or to both U-SIG-1 symbols and U-SIG-2 symbols. The version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

[0122] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier, which may indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted and received PPDUs. The version-independent bits of the U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field relates to UL communication, and the second value of the UL / DL flag field relates to DL communication. The version-independent bits of the U-SIG may include information about the length of a transmission opportunity (TXOP) and information about a BSS color ID.

[0123] For example, the version-dependent bits of the U-SIG may contain information that directly or indirectly indicates the type of PPDU (e.g., SU PPDU, MU PPDU, TB PPDU, etc.).

[0124] Information required for PPDU transmission and reception may be included in the U-SIG. For example, the U-SIG may further include information about bandwidth, information about the MCS technique applied to the non-legacy SIG (e.g., EHT-SIG or UHR-SIG), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique to achieve an effect similar to frequency diversity by reusing the same signal on two subcarriers) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, information about whether the non-legacy SIG is generated across the entire band, etc.

[0125] Some of the information required for transmitting and receiving a PPDU may be included in the U-SIG and / or the non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.). For example, information about the type of the non-legacy LTF / STF (e.g., EHT-LTF / EHT-STF or UHR-LTF / UHR-STF, etc.), information about the length of the non-legacy LTF and the cyclic prefix (CP) length, information about the guard interval (GI) applicable to the non-legacy LTF, information about preamble puncturing applicable to the PPDU, information about resource unit (RU) allocation, etc. may be included only in the U-SIG, may be included only in the non-legacy SIG, or may be indicated by a combination of the information included in the U-SIG and the information included in the non-legacy SIG.

[0126] Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the PPDU's bandwidth. For example, the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth greater than a certain size.

[0127] In the example of FIG. 7, non-legacy SIGs such as HE-SIG-B and EHT-SIG may include control information for the receiving STA. The non-legacy SIG may be transmitted over at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG may be included in a previous SIG (e.g., HE-SIG-A, U-SIG, etc.).

[0128] Non-legacy SIGs, such as HE-SIG-B and EHT-SIG, may contain common fields and user-specific fields. Common and user-specific fields may be coded separately.

[0129] In some cases, common fields may be omitted. For example, in a compressed mode where non-OFDMA (orthogonal frequency multiple access) is applied, common fields may be omitted, and multiple STAs may receive PPDUs (e.g., data fields of PPDUs) over the same frequency band. In a non-compressed mode where OFDMA is applied, multiple users may receive PPDUs (e.g., data fields of PPDUs) over different frequency bands.

[0130] The number of user-specific fields can be determined based on the number of users. A single user block field can contain up to two user fields. Each user field can be associated with either MU-MIMO allocation or non-MU-MIMO allocation.

[0131] The common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, and the length of the Tail bits may be determined as 6 bits and set to 000000. The common field may include RU allocation information. The RU allocation information may include information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.

[0132] An RU can contain multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA techniques. RUs can also be defined when transmitting signals to a single STA. Resources can be allocated on an RU basis for non-legacy STFs, non-legacy LTFs, and data fields.

[0133] Depending on the PPDU bandwidth, an applicable RU size can be defined. The RU may be defined identically or differently for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80MHz PPDU, the RU arrangements of HE PPDU and EHT PPDU may be different. The applicable RU size, RU number, RU position, DC (direct current) subcarrier position and number, null subcarrier position and number, guard subcarrier position and number, etc. for each PPDU bandwidth can be referred to as a tone plan. For example, a tone plan for a wide bandwidth can be defined in the form of multiple repetitions of a low bandwidth tone plan.

[0134] RUs of different sizes can be defined, such as 26-ton RU, 52-ton RU, 106-ton RU, 242-ton RU, 484-ton RU, 996-ton RU, 2X996-ton RU, 3X996-ton RU, etc. A multiple RU (MRU) is distinguished from multiple individual RUs and corresponds to a group of subcarriers consisting of multiple RUs. For example, one MRU can be defined as 52+26-tons, 106+26-tons, 484+242-tons, 996+484-tons, 996+484+242-tons, 2X996+484-tons, 3X996-tons, or 3X996+484-tons. Additionally, multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.

[0135] The specific size of an RU may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. Furthermore, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, etc.) in the present disclosure, the number of RUs may vary depending on the RU size.

[0136] The names of each field in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by those names. Furthermore, the examples of the present disclosure can be applied not only to the PPDU format exemplified in FIG. 7, but also to a new PPDU format in which some fields are excluded and / or some fields are added based on the PPDU formats of FIG. 7.

[0137] Target wake time (TWT)

[0138] TWT is a power saving technology that can improve the energy efficiency of non-AP STAs by defining a service period (SP) between an AP and non-AP STAs and sharing information about the SP to reduce contention of the medium. In the TWT setup phase, an STA that performs requests / suggestions / demands, etc., can be called a TWT requesting STA. In addition, an AP that responds to the request with an acceptance / rejection, etc., can be called a TWT responding STA. The setup phase can include a process of determining / defining a TWT request from an STA to the AP, the type of TWT operation to be performed, and the type of frames to be transmitted and received. TWT operations can be divided into individual TWT and broadcast TWT.

[0139] FIG. 8 is a drawing illustrating an example of an individual TWT operation to which the present disclosure can be applied.

[0140] Individual TWT is a mechanism in which an AP and a non-AP STA negotiate the awake / doze status of a non-AP STA by sending and receiving TWT request / response frames, and then exchange data. In the example of Fig. 8, the AP and STA1 can form a trigger-enabled TWT agreement through a TWT request frame and a TWT response frame. Here, the method used by STA1 is a solicited TWT method, in which STA1 transmits a TWT request frame to the AP, and STA1 receives information for TWT operation from the AP through a TWT response frame. On the other hand, STA2, which performs the unsolicited TWT method, can receive information about the trigger-enabled TWT agreement setup from the AP through the unsolicited TWT response. Specifically, STA2 can calculate the next TWT by adding a specific number to the current TWT value. During the trigger-enabled TWT SP, the AP can transmit a trigger frame to the STAs. The trigger frame can inform the STAs that the AP has buffered data. In response, STA1 can inform the AP of its awake state by transmitting a PS-Poll frame. Additionally, STA2 can inform the AP of its activated state by transmitting a QoS Null frame. Here, the data frames transmitted by STA1 and STA2 can be frames in the TB PPDU format. The AP, which has checked the status of STA1 and STA2, can transmit DL MU PPDU to the activated STAs.When the corresponding TWT SP expires, STA1 and STA2 can enter doze state.

[0141] FIG. 9 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.

[0142] Broadcast TWT is a TWT in which a non-AP STA (or TWT scheduling STA) obtains information such as target beacon transmission time (TBTT) and listen interval by transmitting and receiving TWT request / response frames with the AP (or TWT scheduled STA). Here, a negotiation operation for TBTT may be performed. Based on this, the AP can define a frame to include TWT scheduling information through a beacon frame. In Fig. 9, STA1 performs a requested TWT operation, and STA2 performs an unsolicited TWT operation. The AP can transmit a DL MU PPDU after checking the awake status of the STAs through the trigger it transmitted. This may be the same as the process of an individual TWT. In broadcast TWT, a trigger-enabled TWT SP including a beacon frame may be repeated multiple times at a regular cycle.

[0143] Transmission of TWT information can be accomplished through a TWT information frame and a TWT information element. The TWT information frame is transmitted by an STA to request or transmit information about a TWT agreement, and is transmitted by one of the STAs of an existing TWT agreement. The action frame of the TWT Information frame includes a TWT information field. The TWT Information field can include a 3-bit TWT flow identifier subfield, a 1-bit response requested subfield, a 1-bit next TWT request subfield, a 2-bit next TWT subfield size subfield, a 1-bit all TWT subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0144] FIG. 10 illustrates the format of a TWT element in a wireless communication system to which the present disclosure can be applied.

[0145] Referring to FIG. 10, a TWT element is configured to include an element ID field, a length field, a control field, and a TWT parameter information field.

[0146] The element ID field identifies a TWT element, and the length field indicates the number of octets in the TWT element excluding the element ID field and the length field.

[0147] The control field consists of an NDP paging indicator / unavailability mode subfield, a responder PM mode subfield, a negotiation type subfield, a TWT information frame disabled subfield, a wake duration unit subfield, a link ID bitmap present subfield, and an aligned TWT subfield.

[0148] The NDP paging indicator / unavailability mode subfield is set to 1 to indicate that an NDP paging field is present, otherwise it is set to 0.

[0149] The responder PM mode subfield indicates the power management (PM) mode.

[0150] The negotiation type subfield indicates whether the information contained in the TWT element is for broadcast or for negotiation of parameters of individual TWT(s) or wake TBTT intervals. The most significant bit (MSB) of the negotiation type subfield is the broadcast field.

[0151] The TWT information frame disabled subfield is set to 1 to indicate that reception of TWT information frames is disabled by the STA, otherwise it is set to 0.

[0152] The wake duration unit subfield indicates the unit of the Nominal Minimum TWT Wake Duration field.

[0153] The link ID bitmap present subfield indicates whether the link ID bitmap subfield is present.

[0154] If the TWT element contains an individual TWT parameter set transmitted by the MLD, the aligned TWT subfield indicates whether alignment of individual TWTs on two or more setup links is requested or provided, where the aligned individual TWTs point to aligned start times on those links and have identical TWT parameters. The aligned TWT link bitmap subfield is present if the aligned TWT subfield is 1, otherwise the aligned TWT link bitmap subfield is not present.

[0155] If the broadcast field of the negotiation type subfield is 1, the TWT parameter information field contains one or more broadcast TWT parameter set fields (see Fig. 10). On the other hand, if the broadcast field of the negotiation type subfield is 0, the TWT parameter information field contains one individual TWT parameter set field.

[0156] A TWT element with the broadcast field set to 1 is referred to as a broadcast TWT element.

[0157] The broadcast TWT parameter set field may be composed of a request type subfield, a target wake time subfield, a nominal minimum TWT wake duration subfield, a TWT wake interval mantissa subfield, a broadcast TWT info subfield, and a restricted TWT traffic info subfield.

[0158] multi-link operation (MLO)

[0159] Below, the multi-link (ML) operation supported by the STA according to the present disclosure is described.

[0160] The STA (AP STA and / or non-AP STA) described in the present disclosure can support multi-link (ML) communication. ML communication may refer to communication that supports multiple links. Links related to ML communication may include channels (e.g., 20 / 40 / 80 / 160 / 240 / 320MHz channels) of a frequency band (e.g., 2.4GHz band, 5GHz band, 6GHz band, etc.) in which the STA operates. The multiple links used for ML communication may be configured in various ways. For example, the multiple links supported for one STA for ML communication may belong to the same frequency band or may belong to different frequency bands. In addition, each link may correspond to a frequency unit of a predetermined size (e.g., a channel, a subchannel, an RU, etc.). In addition, some or all of the multiple links may be frequency units of the same size or may be frequency units of different sizes.

[0161] When one STA supports multiple links, the transmitting and receiving devices supporting each link can operate as one logical STA. That is, a multi-link device (MLD) is a device that has one or more affiliated STAs as a logical entity and a single MAC service access point (SAP) for one MAC data service and logical link control (LLC). A non-AP MLD refers to an MLD in which each STA affiliated with the MLD is a non-AP STA. A multi-radio non-AP MLD refers to a non-AP MLD that supports receiving or exchanging frames on more than one link at a time. An AP MLD refers to an MLD in which each STA affiliated with the MLD is an AP STA.

[0162] Multi-link operation (MLO) can enable a non-AP MLD to discover, authenticate, associate, and set up multiple links with an AP MLD. Based on the supported capabilities exchanged during the association procedure, each link can enable channel access and frame exchange between the non-AP MLD and the AP MLD. An STA affiliated with an MLD can select and manage its capabilities and operating parameters independently from other STA(s) affiliated with the same MLD.

[0163] Through the multi-link setup process, the AP MLD and / or the non-AP MLD can transmit and receive link-related information that the MLD can support. The link-related information may include one or more of information about whether the MLD supports simultaneous transmit and receive (STR) operation or non-simultaneous transmit and receive (NSTR) operation on multiple links, information about the number / upper limit of UL / DL links, information about the location / bandwidth / resource of UL / DL links, information about frame types (e.g., management, control, data, etc.) that are available or preferred on at least one UL / DL link, information about an ACK policy that is available or preferred on at least one UL / DL link, or information about a traffic identifier (TID) that is available on at least one UL / DL link.

[0164] An AP MLD (e.g., NSTR mobile AP MLD) can set one of the multiple links as the primary link. The AP MLD may transmit beacon frames, probe response frames, and group-addressed data frames only on the primary link. The remaining link(s) of the multiple links may be referred to as non-primary links. An AP MLD operating on a non-primary link may operate so as not to transmit beacon frames or probe response frames. In addition, a non-AP MLD may perform frame exchanges during authentication, (re)association, and 4-way handshaking only on the primary link.

[0165] A setup link is defined as enabled if at least one traffic identifier (TID) is mapped to the link through the multi-link setup process, and a setup link can be defined as disabled if no TID is mapped to the link. A TID must always be mapped to at least one setup link unless admission control is used. By default, a TID is mapped to all setup links, so all setup links can be enabled.

[0166] When a link is activated, it can be used for frame exchange, depending on the power state of the non-AP STAs operating on that link. Only MSDUs or A-MSDUs with TIDs mapped to the activated link can be transmitted on that link. Management frames and control frames can only be transmitted on the activated link.

[0167] When a link is disabled, that link may not be used for frame exchange, including management frames for both DL and UL.

[0168] During a multi-link setup, activation / deactivation of individual links can be directed through TID-to-Link mapping. TID-to-Link mapping can be performed in default mapping mode or / and negotiation mapping mode.

[0169] Among the STAs belonging to the MLD, one STA may provide information about one or more links other than the link on which it is located, for multi-link discovery (e.g., obtaining information about multiple links including the corresponding link on one link) or multi-link setup (e.g., simultaneously associating on multiple links by exchanging association request / response frames on one link). A multi-link (ML) element may be defined to provide such information.

[0170] Figure 11 exemplarily shows the structure of an ML element to which the present disclosure can be applied.

[0171] In an ML element, the element ID field and the element ID extension field may have specific values ​​(e.g., 255 and 107) indicating that it is an ML element, and the length field may have a value indicating the length (e.g., in octet units) of the remaining fields excluding the element ID field and the length field.

[0172] The multi-link control field is defined as 2 octets in size and may include a 3-bit type subfield, a 1-bit reserved bit, and a 12-bit presence bitmap subfield. The type subfield may have a value indicating one of the following types: basic, probe request, reconfiguration, tunneled direct-link setup (TDLS), and priority access. The presence bitmap subfield indicates the presence or absence of various subfield(s) within the common info field, and may be defined in different formats depending on the various variants (or types) of the ML element.

[0173] The common info field is defined to be of variable size and may include a 6-octet MLD MAC address subfield, which may have a value specifying the MAC address of the MLD to which the STA transmitting the basic ML element belongs. In addition, a link ID info subfield, a BSS parameter change count subfield, a medium synchronization delay information subfield, an enhanced multi-link (EML) capability subfield, and an MLD capability subfield may or may not be included in the common info field.

[0174] The link info field is defined as having a variable size, can contain link-specific information, and can be optionally present. If the link info field exists, it can contain one or more subelements. The format and order of the subelements can be defined in various ways. As an example of optional subelement IDs for the basic variant ML element, the value 0 of the subelement ID corresponds to the name of the per-STA profile and is extensible, the value 221 corresponds to the name of the vendor-specific name and the extensibility can be determined by the vendor, and the remaining values ​​1-220 and 222-255 can be reserved.

[0175] The STA-per-profile subfield may include a 1-octet subelement ID subfield, a 1-octet length subfield, a 2-octet STA control subfield, a variable-size STA info subfield, and a variable-size STA profile subfield. The STA control subfield may include information such as a link ID, whether a complete profile is included, whether an STA MAC address exists, etc. The STA info subfield may include information such as an STA MAC address. The STA profile subfield may include information included in a probe response or probe request frame body, information included in a (re)association response or (re)association request frame body, etc., depending on whether the reported STA is an AP STA or a non-AP STA.

[0176] The format of the ML elements in FIG. 11 is exemplary, and the order, names, sizes, etc. of the fields / subfields may be changed, additional fields / subfields may be further defined, and some fields / subfields may be excluded. In short, the common information field includes common information between STAs in the MLD, and the link information field may include specific information for each STA / link (e.g., in a per-STA profile subelement including a link ID corresponding to the STA).

[0177] Delivery Traffic Indication Map (DTIM)

[0178] The TIM element is used to signal the timing and availability of data to associated STAs.

[0179] FIG. 12 illustrates the format of a TIM element in a wireless communication system to which the present disclosure can be applied.

[0180] Referring to FIG. 12, a TIM element is configured to include an element ID field, a length field, a DTIM count field, a DTIM period field, a bitmap control field, and a partial virtual bitmap field.

[0181] The element ID field identifies the TIM element, and the length field indicates the number of octets within the TIM element excluding the element ID field and the length field.

[0182] The DTIM count field indicates the number of beacon frames (including the current frame) that appear before the next DTIM beacon (i.e., a special case of a beacon frame). A DTIM count of 0 indicates that the current beacon frame is a DTIM beacon.

[0183] The DTIM Period field indicates the number of beacon intervals between consecutive DTIM beacons. If all beacons are DTIM beacons, the value of the DTIM Period field is 1. A DTIM Period value of 0 is reserved.

[0184] MLD discovery method in the millimeter wave (mmWave) band

[0185] A multi-link device (MLD) defined in 802.11be consists of affiliated APs (or non-AP STAs) that operate on one or more different channels, and has fundamentally achieved significant improvements in terms of (aggregated / average) throughput / latency. In particular, while the existing MLD has primarily targeted the 2.4 to 7.25 GHz (sub-7 GHz) band, recently, with the growing need for millimeter wave (mmWave) that offers relatively limited coverage but powerful throughput / latency improvements, research is being conducted to enable MLD affiliated APs (or non-AP STAs) to operate in the mmWave band (i.e., unlicensed bands between 42 and 71 GHz). Therefore, the issues that arise as affiliated APs (or non-AP STAs) of MLDs operating in the mmWave band are included need to be resolved.

[0186] FIG. 13 illustrates an AP MLD and a non-AP MLD supporting the mmWave band according to one embodiment of the present disclosure.

[0187] Figure 13 illustrates an MLD supporting the mmWave band. AP 1 of the AP MLD operates a channel in the sub-7 GHz band, AP 3 operates a channel in the mmWave band, STA 1 of the non-AP MLD supports the sub-7 GHz band, and STA 2 supports the mmWave band. Therefore, the non-AP MLD can request a multi-link setup from the AP MLD so that STA 1 can associate with AP 1 (link 1) and STA 2 can associate with AP 3 (link 2).

[0188] For this purpose, in multi-link operation (MLO), at least one process may be performed in the process exemplified in Fig. 14.

[0189] FIG. 14 illustrates a discovery and multi-link setup process for multi-link operation in a wireless communication system to which the present disclosure can be applied.

[0190] 1) Legacy discovery: A non-AP MLD can detect the presence of an AP MLD by receiving a beacon frame or transmitting a probe request frame through a scanning process. In particular, an AP belonging to an AP MLD (e.g., AP 1 in FIG. 14) can include a basic multi-link element (Basic ML IE) in a beacon frame or a probe response frame to indicate that it belongs to the AP MLD and provide some information about it.

[0191] 2) Multi-link probing: A Non-AP MLD (i.e., any STA belonging to a Non-AP MLD, STA 1 in FIG. 14) can discover AP 1 and request information about one or more other affiliated APs of the AP MLD to which AP 1 belongs. Here, the Non-AP MLD (i.e., STA 1 belonging to a Non-AP MLD and discovering AP 1) can request information about one or more other affiliated APs using an ML Probe Request frame, which is a Probe Request frame including a Probe Request Multi-link element (ML IE) (or Probe Request IE).

[0192] AP 1 (or AP MLD) that receives the ML probe request frame can transmit an ML probe response frame, which is a probe response frame including a Basic ML IE, to the non-AP MLD (i.e., STA 1 that belongs to the non-AP MLD and transmitted the ML probe request frame). Here, based on the request information of the ML probe request frame, AP 1 can transmit the ML probe response frame including a partial profile or a complete profile for one or more other affiliated APs.

[0193] 3) Multi-link setup: A Non-AP MLD (i.e., any STA belonging to the Non-AP MLD) selects an appropriate AP based on information of one or more affiliated APs of the AP MLD, and requests multi-link setup to the AP MLD (i.e., any AP belonging to the AP MLD). To this end, the Non-AP MLD (i.e., any STA belonging to the Non-AP MLD) can transmit an Association Request frame including a Basic ML IE to the AP MLD (i.e., any AP belonging to the AP MLD). The Basic ML IE includes which AP each affiliated STA of the Non-AP MLD wants to associate with, a complete profile of each requesting affiliated STA, etc.

[0194] An AP MLD (i.e., one AP belonging to the AP MLD) that has received a request for multi-link setup determines whether to accept / reject which STA and AP can be associated based on information about STAs belonging to the Non-AP MLD, and transmits an Association Response frame to the Non-AP MLD (i.e., one STA belonging to the Non-AP MLD). Here, the Association Response frame includes information such as a status code indicating whether to accept / reject, a basic ML IE, and a complete profile for each requested affiliated AP.

[0195] Meanwhile, the millimeter wave (mmWave) band requires directional transmission due to its relatively small range / coverage. This can increase the protocol / implementation complexity for beamforming, control / management, etc. Therefore, if an STA operating in the sub-7 GHz band can perform control / management tasks instead of an STA operating in the mmWave band, as in the process illustrated in Figure 14, the mmWave band can be utilized more efficiently. Furthermore, from a power saving (PS) perspective, it may be easier to apply mechanisms that require extensive information and frame exchange, such as the target wake time (TWT). For example, in the case of a broadcast TWT schedule, periodic announcements are required in the beacon frame, and a negotiation process is also required to establish membership between the AP and the STA for the schedule. Therefore, if an STA (non-AP or AP) operating in sub-7GHz performs all or part of its operations by utilizing MLO instead of an STA (non-AP or AP) operating in the mmWave band, efficient mmWave band operations can be performed.

[0196] Therefore, the present disclosure proposes a TWT mechanism utilizing MLO including mmWave band.

[0197] In the description of the present disclosure, for convenience of explanation, a case in which a configuration includes an AP / non-AP STA operating in a sub-7 GHz band within an MLD and an AP / non-STA operating in a mmWave band is mainly described. Here, for convenience of explanation, an STA or AP operating in a mmWave band within the same MLD is referred to as an mSTA or mAP, and an STA or AP operating in a sub-7 GHz band is referred to as an sSTA or sAP, respectively.

[0198] In addition, the names referred to in this disclosure are for convenience of explanation and may be replaced with other equivalent names. In addition, unless otherwise stated in this disclosure, an STA may include an AP STA or a non-AP STA. In addition, an MLD may include an AP MLD or a non-AP MLD.

[0199] FIG. 15 illustrates the format of a per-STA profile subelement within a multi-link element in a wireless communication system to which the present disclosure may be applied.

[0200] Referring to FIG. 15, a format within a multi-link element is illustrated, and may be configured to include an element ID field, a length field, an element ID extension field, a multi-link control field, a common info field, and a link info field.

[0201] Depending on the variant of this element, certain field(s) or subfield(s) within a field may not be included, and the type subfield within the multi-link control field is used to distinguish variants of the multi-link element.

[0202] Table 1 illustrates the encoding of values ​​of the type subfield.

[0203] Type Subfield Value Multi-Link Element Variant Name 0 Basic 1 Probe Request 2 Reconfiguration 3 TDLS 4 Priority Access 5-7 Reserved

[0204] The link info field conveys specific information about one or more links and may be optionally present. If present, the link info field may contain one or more per-STA profile subelements.

[0205] A per-STA profile subelement may be composed of a subelement identifier (subelement ID) subfield, a length subfield, a STA control subfield, a STA info subfield, and a STA profile subfield.

[0206] The STA control subfield may be configured to include a link identifier (link ID) subfield, a complete profile subfield, an STA MAC address present subfield, a beacond interval present subfield, a timing synchronization function (TSF) offset present subfield, a delivery traffic indication map (DTIM) information present subfield, an NSTR link pair present subfield, an NSTR bitmap size subfield, a BSS parameters change count present subfield, and reserved bits.

[0207] The link identifier (link ID) subfield specifies a value that uniquely identifies the link on which the reporting / target STA is operating.

[0208] The TSF offset present subfield is set to 1 if the TSF offset subfield is present in the STA Info field, otherwise it is set to 0. Non-AP STAs set the TSF offset present subfield to 0 in the transmitted basic multi-link element.

[0209] Hereinafter, in the description of the present disclosure, for the convenience of explanation, a broadcast TWT schedule will be mainly described, but the present disclosure is not limited thereto, and the same method can be applied to individual TWT schedules.

[0210] Example 1: TWT announcement method

[0211] One or more Broadcast TWT Schedules may be announced in a beacon frame or probe response frame, and may be announced by an sAP on behalf of an mAP belonging to the same MLD. At least one of the following announcement methods may be used.

[0212] For example, it can be announced in the ML element (ML IE: multi-link element) of the beacon frame or probe response frame of SAP (e.g., Basic ML IE) (see Fig. 15) or in a new field / IE.

[0213] Additionally, the ML IE may basically be composed of common information (Common Info) that is commonly applied to the entire MLD and link information (Link Info) that is individually applied to each AP (see FIG. 15). If the link info field exists, it may include one or more per-STA profile subelements. Here, the per-STA profile subelement of the link information corresponding to each mAP in the ML IE transmitted by the sAP may include a broadcast TWT element that includes one or more broadcast TWT schedules (e.g., a broadcast parameter set field) of the corresponding mAP.

[0214] Here, each mAP can be distinguished based on the link ID (i.e., the link ID subfield in the STA control subfield) included in the Per-STA Profile subelement of the link information (Link Info).

[0215] Additionally or alternatively, the Per-STA Profile subelement may correspond to a per-STA profile using the existing subelement ID 0, but may be replaced with a per-STA profile dedicated to Integrated mmWave (IMMW). For example, a reserved value other than subelement ID 0 (any of 1-220 and 222-255, e.g., 1) may be used for the per-STA profile dedicated to IMMW.

[0216] Additionally or alternatively, the value of the TWT of the mAP may be indicated based on the timing synchronization function (TSF) of the mAP. Alternatively, the value of the TWT of the mAP may be indicated based on the TSF of the sAP that announces the broadcast TWT schedule of the mAP, and a TSF offset (i.e., the offset between the TSF of the sAP and the TSF of the mAP) may be announced. This is to enable the STA to understand the exact TWT schedule of the mAP.

[0217] Additionally or alternatively, at least one of the following methods may be used to avoid transmitting all broadcast TWT schedules in periodic beacons:

[0218] Method A) Broadcast TWT schedules can be announced based on specific cycles corresponding to each mAP.

[0219] Information about a specific period during which a broadcast TWT schedule is announced may include at least one of the following pieces of information: The information about the specific period may include a period during which the broadcast TWT schedule is indicated in periodically transmitted management frames (e.g., beacons) (e.g., the number of management frame intervals between consecutive frames indicating a broadcast TWT schedule) and the number of management frames to be transmitted / appearing before the next management frame indicating a broadcast TWT schedule (i.e., counted including the management frame indicating this information). Here, each piece of information may be composed of bits based on the maximum possible value (e.g., 2 or 8 bits).

[0220] The sAP may announce information about the specific period at which the mAP's TWT schedule is announced in a management frame (e.g., a beacon frame).

[0221] FIG. 16 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0222] Figure 16 illustrates a method in which sAP and mAP 1 belong to the same AP MLD, and sAP announces a broadcast TWT schedule for mAP 1 belonging to the same AP MLD in its own beacon frame ("B"). Figure 16 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), but this is only an example, and other management frames may be used.

[0223] Referring to FIG. 16, when the period (i.e., schedule period) at which the broadcast TWT schedule for mAP 1 is announced is 2, a method of indicating a broadcast TWT schedule according to the remaining number of frames to be transmitted (i.e., schedule count) before the next frame (e.g., beacon frame) for which the broadcast TWT schedule is indicated is illustrated.

[0224] In the first beacon frame of sAP, a broadcast TWT schedule for mAP 1 is indicated, and therefore, the schedule count in the first beacon frame of sAP is indicated as 0.

[0225] Since the period for the broadcast TWT schedule is 2 (i.e., the interval between beacon frames * 2), the broadcast TWT schedule for mAP 1 is not indicated in the second beacon frame of sAP. Since the broadcast TWT schedule for mAP 1 will be indicated in the next beacon frame of sAP, the number of beacon frames of sAP to be transmitted before and including the second beacon frame of sAP is 1, and therefore the schedule count is indicated as 1 in the second beacon frame of sAP. Therefore, the broadcast TWT schedule for mAP 1 is indicated in the third beacon frame following sAP.

[0226] Additionally or alternatively, for broadcast TWT, given the duration of the broadcast TWT persistence for each TWT schedule, which is the period during which the corresponding TWT schedule is maintained, if the broadcast TWT schedule is terminated between the time points at which the broadcast TWT schedule is announced, the broadcast TWT schedule may be announced in every frame of the sAP (until the broadcast TWT schedule is terminated) at least until the schedule count becomes 0. For example, if the period of the broadcast TWT schedule of the mAP is 4 (i.e., the interval between beacon frames * 4), and the broadcast TWT schedule of the mAP is scheduled to end in the next beacon frame of the sAP, the sAP may announce the broadcast TWT schedule in every beacon frame until the next beacon frame.

[0227] Additionally or alternatively, if the broadcast TWT schedule is updated between the time points at which the broadcast TWT schedule is announced, the broadcast TWT schedule may be announced in every frame of the sAP (until the broadcast TWT schedule ends) at least until the schedule count becomes 0. For example, if the period of the broadcast TWT schedule of the mAP is 4 (i.e., the interval between beacon frames * 4), and the broadcast TWT schedule of the mAP is to be updated in the next beacon frame, the sAP may announce the broadcast TWT schedule in every beacon frame until the next beacon frame.

[0228] Additionally or alternatively, for a specific identifier (ID: identifier) ​​(e.g., 0) for a broadcast TWT schedule, no specific period may be set so that all STAs are always aware of it, and it may be announced in every frame of the sAP.

[0229] Additionally or alternatively, the presence of a TWT schedule (e.g., 1 bit) or the number of TWT schedules may be announced to allow the Non-AP MLD to be aware of the presence of a TWT schedule even between the time points when the TWT schedule is announced. For example, this may be indicated in the neighbor AP information field corresponding to each mAP in the reduced neighbor report (RNR) element or in the Per-STA Profile subelement corresponding to each mAP in the Link Info field of the ML IE (e.g., the Per-STA Profile subelement with subelement ID 0 or the Per-STA Profile subelement dedicated to IMMW).

[0230] Additionally, the notification cycle for the TWT schedule can be determined and announced by the sAP. For example, it can be indicated in the neighbor AP information field corresponding to each mAP in the RNR IE or in the Per-STA Profile subelement corresponding to each mAP in the Link Info field of the ML IE (e.g., the Per-STA Profile subelement with subelement ID 0 or the Per-STA Profile subelement dedicated to IMMW).

[0231] Additionally or alternatively, a particular period may be determined by at least one of the following methods:

[0232] Method A-1) A specific period can be determined by considering the delivery traffic indication map (DTIM) of each mAP.

[0233] DTIM Period refers to the number of beacon frame intervals between consecutive DTIM beacons (i.e., beacon frames containing a DTIM). DTIM Count refers to the number of beacon frames (including the current beacon frame) that will appear / be transmitted before the next DTIM beacon (i.e., beacon frame containing a DTIM).

[0234] The specific period at which the broadcast TWT schedule for each mAP is announced can be determined by the DTIM count and DTIM period for that mAP. The DTIM count and DTIM period can be conveyed from the sAP in a multi-link probe / association request / response frame, etc., through which the STA can obtain the DTIM count and DTIM period.

[0235] Additionally or alternatively, the sAP may determine a specific periodicity at which the broadcast TWT schedule for each mAP is announced, and the DTIM count for the mAP may be set from the specific periodicity at which the broadcast TWT schedule is announced. For example, the DTIM period may be set to a multiple of the specific periodicity at which the broadcast TWT schedule for the mAP is announced. In this case, the broadcast TWT schedule for the mAP may not be directed to align with the transmission period of the DTIM (although the DTIM period may be set to be the same as the specific periodicity at which the broadcast TWT schedule for the mAP is announced).

[0236] FIG. 17 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0237] Figure 17 illustrates a method in which sAP and mAP 1 belong to the same AP MLD, and sAP announces a broadcast TWT schedule for mAP 1 belonging to the same AP MLD in its own beacon frame ("B"). Figure 17 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), but this is an example, and other management frames may be used.

[0238] Figure 17(a) illustrates a case where the period at which the broadcast TWT schedule of an mAP is announced is determined based on the DTIM of the mAP. That is, the period at which the broadcast TWT schedule of each mAP is announced can be determined based on the DTIM period and DTIM count of the mAP.

[0239] Referring to Fig. 17(a), an example is provided where the DTIM cycle for mAP 1 is 2, which may correspond to the cycle in which the broadcast TWT schedule for mAP 1 is announced.

[0240] In the first beacon frame of sAP, the DTIM for mAP 1 is indicated (i.e., the broadcast TWT schedule is also indicated), and therefore, in the first beacon frame of sAP, the DTIM count is indicated as 0 (i.e., the schedule count is also 0).

[0241] Since the DTIM period is 2 (i.e., the interval between beacon frames * 2), the DTIM for mAP 1 is not indicated in the second beacon frame of sAP (i.e., the broadcast TWT schedule is not indicated either). Since the DTIM for mAP 1 will be indicated in the next beacon frame of sAP, the number of beacon frames to be transmitted before and including the second beacon frame of sAP is 1, and therefore the DTIM count is indicated as 1 in the second beacon frame (i.e., the schedule count is also 1). Therefore, the DTIM for mAP 1 is indicated in the next third beacon frame of sAP (i.e., the broadcast TWT schedule is also indicated).

[0242] Figure 17(b) illustrates a case where the DTIM of a mAP is determined from the period in which the broadcast TWT schedule of the mAP is announced. That is, the sAP can determine the period in which the broadcast TWT schedule of each mAP is announced, and the DTIM count of the mAP can be set / determined based on this period. For example, the DTIM period can be set as a multiple of a specific period in which the broadcast TWT schedule is announced.

[0243] Referring to Fig. 17(b), an example is provided in which the period (i.e., schedule period) in which the broadcast TWT schedule for mAP 1 is announced is 2, and the DTIM period for mAP 1 is 4. That is, Fig. 17(b) exemplifies a case in which the DTIM period for mAP 1 is twice the period in which the broadcast TWT schedule is announced.

[0244] In the first beacon frame of sAP, a broadcast TWT schedule for mAP 1 is indicated, and therefore, the schedule count in the first beacon frame of sAP is indicated as 0.

[0245] Since the period for the broadcast TWT schedule is 2 (i.e., the interval between beacon frames * 2), the broadcast TWT schedule for mAP 1 is not indicated in the second beacon frame of sAP. Since the broadcast TWT schedule for mAP 1 will be indicated in the next beacon frame of sAP, the number of beacon frames to be transmitted before and including the second beacon frame of sAP is 1, and therefore the schedule count is indicated as 1 in the second beacon frame of sAP. Therefore, the broadcast TWT schedule for mAP 1 is indicated in the third beacon frame following sAP.

[0246] Method A-2) A specific period can be determined by considering a broadcast TWT ID or a similar ID (i.e., identification information that can identify a broadcast TWT schedule, which can be referred to as a (TWT) schedule ID).

[0247] A specific period can be set by grouping broadcast TWT IDs or similar IDs (i.e., identification information that can identify a broadcast TWT schedule). That is, each broadcast TWT ID (or identification information that can identify a broadcast TWT schedule) can have a specific period, and the broadcast TWT schedule indicated in each frame of the sAP can be different for each ID. In other words, the period at which the broadcast TWT schedule is announced is determined / set for each broadcast TWT ID (or identification information that can identify a broadcast TWT schedule), and in each frame of the sAP, the broadcast TWT schedule of the broadcast TWT ID (or identification information that can identify a broadcast TWT schedule) corresponding to the timing at which the broadcast TWT schedule is announced can be announced.

[0248] FIG. 18 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0249] FIG. 18 illustrates a method in which sAP and mAP 1 belong to the same AP MLD, and sAP announces a broadcast TWT schedule for mAP 1 belonging to the same AP MLD in its own beacon frame ("B"). Although FIG. 18 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), this is an example, and other management frames may be used.

[0250] Figure 18 illustrates an example of indicating a broadcast TWT schedule according to a specific period, taking into account a (TWT) schedule ID (e.g., a broadcast TWT ID). Figure 18 illustrates a case where the total number of broadcast TWT IDs is defined as 32 and the schedule period is 4.

[0251] In this case, a broadcast TWT schedule of eight broadcast TWT IDs is indicated in each beacon frame of the sAP. That is, a broadcast TWT schedule of broadcast TWT IDs 0 to 7 may be indicated in the first beacon frame of the sAP (if a schedule exists), a broadcast TWT schedule of broadcast TWT IDs 8 to 15 may be indicated in the second beacon frame of the sAP (if a schedule exists), a broadcast TWT schedule of broadcast TWT IDs 16 to 23 may be indicated in the third beacon frame of the sAP (if a schedule exists), and although not illustrated in FIG. 18, a broadcast TWT schedule of broadcast TWT IDs 24 to 31 may be indicated in the fourth beacon frame of the sAP (if a schedule exists).

[0252] Meanwhile, although FIG. 18 illustrates a case of grouping in ascending order of broadcast TWT ID, the present disclosure is not limited thereto. For example, in the first beacon frame of the sAP, a broadcast TWT schedule with broadcast TWT ID mod 4 = 0 may be indicated (if a schedule exists), in the second beacon frame of the sAP, a broadcast TWT schedule with broadcast TWT ID mod 4 = 1 may be indicated (if a schedule exists), in the third beacon frame of the sAP, a broadcast TWT schedule with broadcast TWT ID mod 4 = 2 may be indicated (if a schedule exists), and in the fourth beacon frame of the sAP, a broadcast TWT schedule with broadcast TWT ID mod 4 = 3 may be indicated (if a schedule exists).

[0253] Also, in Fig. 18, it is assumed that there are only current broadcast TWT schedules with ID = 1 and ID = 16. Therefore, in the first beacon frame of sAP, the broadcast TWT schedule corresponding to broadcast TWT ID 1 is indicated, in the second beacon frame of sAP, no schedule is indicated, and in the third beacon frame of sAP, the broadcast TWT schedule corresponding to broadcast TWT ID 16 is indicated.

[0254] Method A-3) A specific period can be determined / set considering the number of mAPs of AP MLD.

[0255] Depending on the schedule period (i.e., the specific period at which the broadcast TWT schedule is announced), the number of mAPs for which the broadcast schedule is indicated in each frame of the sAP may vary. For example, in each frame of the sAP, as many broadcast TWT schedules for mAPs as the number of mAPs / schedule period may be indicated. For example, if the schedule period is 2 and there are 2 mAPs, a broadcast TWT schedule for one mAP may be indicated in each frame of the sAP. As another example, if the schedule period is 2 and there are 4 mAPs, a broadcast TWT schedule for two mAPs may be indicated in each frame of the sAP. As yet another example, if the schedule period is 2 and there are 3 mAPs, a frame of the sAP with a schedule count of 0 may indicate a broadcast TWT schedule for two mAPs, and a frame of the sAP with a schedule count of 1 may indicate a broadcast TWT schedule for one mAP. Also, conversely, if the schedule period is 2 and the mAPs are 3, a broadcast TWT schedule for 1 mAP may be indicated in the frame of the sAP when the schedule count is 0, and a broadcast TWT schedule for 2 mAPs may be indicated in the frame of the sAP when the schedule count is 1.

[0256] Additionally or alternatively, for each mAP, the above-described method A-1 and / or method A-2, etc. may be additionally applied.

[0257] FIG. 19 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0258] FIG. 19 illustrates a method in which sAP, mAP 1, and mAP 2 belong to the same AP MLD, and sAP announces a broadcast TWT schedule for mAP 1 and mAP 2 belonging to the same AP MLD in its own beacon frame ("B"). Although FIG. 19 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), this is an example, and other management frames may be used.

[0259] Figure 19 illustrates an example of a broadcast TWT schedule indication according to a specific period, taking into account the number of mAPs. Figure 19 illustrates a case where the total number of mAPs belonging to the AP MLD is 2, and the schedule period is 2. In this case, a schedule for one mAP can be indicated in each beacon frame of the sAP.

[0260] FIG. 19 illustrates an example where broadcast TWT schedule 1 for mAP 1 is indicated in the first beacon frame of sAP, and broadcast TWT schedules 2 and 3 for mAP 2 are indicated in the second beacon frame of sAP. In the subsequent beacon frames of sAPs, broadcast TWT schedule 1 for mAP 1 and broadcast TWT schedules 2 and 3 for mAP 2 may also be indicated alternately.

[0261] Additionally or alternatively, the method of grouping mAPs may be a method of grouping in ascending order based on a link ID assigned to the mAP, such as the method A-2 described above, or an ID that can be similarly assigned to each mAP (see example in FIG. 18), or a method of grouping by interval, but the present disclosure is not limited thereto.

[0262] For example, multiples of the broadcast TWT ID can be used. For example, grouping by interval (i.e. using multiples, grouping by broadcast TWT ID mod X) can be applied, such as group 1 = {0, 3, 6, ...}, group 2 = {1, 4, 7, ...}.

[0263] Another example is that the groups can be grouped in ascending order from the smallest ID value. For example, group 1 = {0, ..., 50}, group 2 = {51, ...., 100}.

[0264] Additionally or alternatively, a specific broadcast TWT ID (e.g., ID = 0) can be announced in every frame of the sAP without grouping (i.e., without belonging to any group) so that all STAs can participate.

[0265] Additionally or alternatively, the presence of a TWT schedule (e.g., 1 bit) or the number of TWT schedules may be announced to allow the Non-AP MLD to be aware of the presence of a TWT schedule even between the time points when the TWT schedule is announced. For example, this may be indicated in the neighbor AP information field corresponding to each mAP in the reduced neighbor report (RNR) element or in the Per-STA Profile subelement corresponding to each mAP in the Link Info field of the ML IE (e.g., the Per-STA Profile subelement with subelement ID 0 or the Per-STA Profile subelement dedicated to IMMW).

[0266] FIG. 20 illustrates a method for announcing a broadcast TWT schedule to other APs belonging to the same MLD according to one embodiment of the present disclosure.

[0267] FIG. 20 illustrates a method in which sAP, mAP 1, and mAP 2 belong to the same AP MLD, and sAP announces a broadcast TWT schedule for mAP 1 and mAP 2 belonging to the same AP MLD in its own beacon frame ("B"). Although FIG. 20 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), this is an example, and other management frames may be used.

[0268] In FIG. 20, the broadcast TWT schedule of mAP 1 is announced for every beacon frame of sAP, and the broadcast TWT schedule of mAP 2 is announced with a specific cycle, and two broadcast TWT schedules (i.e., broadcast TWT schedules 2 and 3) are exemplified.

[0269] For example, if the period at which the broadcast TWT schedule is announced is applied to the DTIM, the first beacon frame of sAP in FIG. 20 may correspond to the DTIM of mAP 2, and DTIM period = 2.

[0270] Additionally, for example, FIG. 20 illustrates a case where broadcast TWT schedules 2 and 3 for mAP 2 are announced according to schedule period 2, but the schedule of mAP 2 may be announced alternately in each beacon frame of sAP, such that broadcast TWT 2 and broadcast TWT 3 are announced.

[0271] Meanwhile, additionally or alternatively, a partial list of TWT schedules (i.e., information indicating that some TWT schedules can be announced) may be announced in a management frame (e.g., a beacon frame, a probe response frame, or a new action frame) as in at least one of the above-described methods. For example, the partial list of TWT schedules may be indicated in an Extended Capabilities field, a Capability Information And Status Indication field, or an ML IE. Additionally or alternatively, for example, if applicable for each mAP, a partial list of the TWT schedule may be indicated in the Neighbor AP Information field of the RNR IE corresponding to each mAP or in the Per-STA Profile subelement corresponding to each mAP in the Link Info field of the ML IE (e.g., the Per-STA Profile subelement of subelement ID 0 or the Per-STA Profile subelement dedicated to IMMW).

[0272] Method B) To announce the broadcast TWT schedule of mAP, the aligned schedule of the broadcast TWT of sAP can be utilized.

[0273] Currently, Broadcast TWT can utilize aligned TWT. That is, while one of the affiliated APs in the AP MLD announces Broadcast TWT Schedule 1 in its beacon frame, one or more other affiliated APs can announce that their Broadcast TWT schedules are aligned with the announced Broadcast TWT Schedule 1 (i.e., have the same TWT start time and the same Broadcast TWT parameters).

[0274] However, even if an aligned TWT is announced, the actual existence of the TWT can only be determined by receiving the beacon frame of the corresponding AP. Therefore, if a beacon frame is not transmitted from the mAP, the sAP needs to announce the TWT of the mAP. Therefore, when the sAP announces the aligned TWT schedule, it needs to indicate which TWT schedule of which mAP is aligned with the sAP's TWT schedule in the management frame (e.g., beacon frame, probe response frame, new action frame). To reduce signaling overhead, at least one of the following pieces of information may be included to indicate which mAP is aligned.

[0275] Method B-1) An aligned TWT link ID field can be defined.

[0276] As described above, the sAP may announce one or more TWT schedules of mAPs in the sAP's frame instead of mAPs belonging to the same MLD. In this case, a field (e.g., an aligned TWT link ID field) may be defined in the sAP's frame, indicating a TWT schedule of the sAP that is aligned with one or more TWT schedules of mAPs announced in the sAP's frame.

[0277] For example, the Link ID can be used to distinguish which mAP's TWT schedule is aligned with the sAP's TWT schedule.

[0278] Additionally or alternatively, if one or more broadcast TWT IDs associated with the sAP or similarly identifying TWTs are not present (i.e., not indicated) in the sAP's frame, it may mean that the sAP's overall TWT schedule is aligned with the mAP's TWT schedule indicated by the sAP's frame.

[0279] Additionally or alternatively, if the frame of the sAP contains one or more broadcast TWT IDs associated with the sAP or similarly identifies a TWT schedule (e.g., indicates) (e.g., a 2-tuple <link ID, broadcast TWT ID>), this may mean that the TWT schedule of the sAP corresponding to the corresponding ID of the sAP is aligned with the TWT schedule of the mAP indicated by the frame of the sAP.

[0280] Additionally or alternatively, an Aligned field (e.g., 1 bit) may be added to the Neighbor AP Information field of the RNR IE corresponding to each mAP or to the Per-STA Profile subelement (e.g., the per-STA Profile subelement with subelement ID 0 or the per-STA Profile subelement dedicated to IMMW) in the link info field of the ML IE corresponding to each mAP that already contains a Link ID. Additionally or alternatively, if a broadcast TWT ID or an ID similarly distinguishing a TWT schedule associated with the sAP is added (e.g., a 2-tuple <link ID, broadcast TWT ID>), it may mean that the schedule corresponding to that ID of the sAP is aligned.

[0281] Method B-2) The Aligned TWT Link ID Bitmap can be used to identify which mAP's TWT schedule is aligned with the sAP's TWT schedule. For example, a bit for the mAP can be indicated in the Link ID Bitmap, which is constructed / generated based on the Link ID for the mAP obtained in the Discovery / Multi-link Setup process (see Fig. 14), thereby distinguishing which mAP's TWT schedule is aligned with the sAP's TWT schedule.

[0282] Additionally or alternatively, the Aligned TWT Link ID Bitmap may be included in the Common Info field of the ML IE.

[0283] Additionally or alternatively, if one or more broadcast TWT IDs associated with the sAP or similarly identifying TWTs are not present (i.e., not indicated) in the sAP's frame, it may mean that the sAP's overall TWT schedule is aligned with the mAP's TWT schedule indicated by the sAP's frame.

[0284] Additionally or alternatively, if there is (i.e., indicates) one or more broadcast TWT IDs associated with the sAP in the frame of the sAP or similarly an ID that distinguishes the TWT schedule (e.g., a 2-tuple <aligned TWT link ID bitmap, broadcast TWT ID>), it may mean that the TWT schedule of the sAP corresponding to the corresponding ID of the sAP is aligned with the TWT schedule of the mAP indicated by the bitmap in the frame of the sAP.

[0285] Additionally or alternatively, an Aligned field (e.g., 1 bit) may be added to the Neighbor AP Information field of the RNR IE corresponding to each mAP or to the Per-STA Profile subelement (e.g., the per-STA Profile subelement with subelement ID 0 or the per-STA Profile subelement dedicated to IMMW) in the link info field of the ML IE corresponding to each mAP that already contains a Link ID. Additionally or alternatively, if a broadcast ID or similar ID that distinguishes a TWT schedule associated with the sAP is added (e.g., a 2-tuple <link ID, broadcast TWT ID>), it may mean that the schedule corresponding to that ID of the sAP is aligned.

[0286] B-3 Method) An aligned schedule list can be defined.

[0287] sAP can be instructed to list which schedules of the sAP's TWT schedule align with the mAP's TWT schedule. To this end, a list of broadcast TWT IDs or similar IDs that distinguish the TWT schedules can be instructed, and at least one of the following methods can be used.

[0288] - Bitmap for TWT schedule related IDs: A bitmap of X bits may be constructed based on the maximum possible number of IDs (X). For example, if there are at most 32 broadcast TWT IDs, a bitmap of 32 bits may be constructed. Additionally or alternatively, if some broadcast TWT IDs are excluded or the number of IDs for which TWT schedules can be aligned is limited, the bitmap may be reduced by that number of bits.

[0289] - ID list: At least one TWT schedule-related ID for the sorted TWT schedule may be indicated. Additionally, this may be indicated in ascending order of the ID. Additionally or alternatively, the number of IDs may be indicated. The number of IDs may be indicated with X bits based on the maximum possible number of IDs (e.g., X = 3, 5). For example, if IDs = 2 and 4 among the TWT schedules of sAP are sorted, it is indicated that there are 2 IDs, and IDs 2 and 4 may be sequentially indicated.

[0290] Additionally or alternatively, this information may be indicated in the Per-STA Profile sub-element corresponding to each mAP in the link info field of the ML IE presented above (e.g., the Per-STA Profile sub-element with subelement ID 0 or the Per-STA Profile sub-element dedicated to IMMW). For example, in the Per-STA Profile, which mAP is targeted may be distinguished by its link ID, and an Aligned Schedule List may be added to it.

[0291] Example 2: TWT Information Probing and Membership Negotiation Method

[0292] As described above, when a partial list of TWT schedules of an mAP is announced by an sAP, a non-AP MLD may utilize an sSTA to obtain information about the entire TWT schedule of the mAP or to establish / acquire membership in the announced mAP's TWT schedule. Essentially, this requires a method for an sSTA to indicate which mAP's TWT schedule it is requesting, and at least one of the following methods may be used.

[0293] Method A) A link ID field can be defined.

[0294] An sSTA can instruct an sAP to request information about a TWT schedule for a given mAP or to request membership in a TWT scheduling for a given mAP via a link ID. For example, an sSTA can instruct an sAP on a link ID obtained during the discovery / multi-link setup process (see Figure 14), and additionally, can instruct an sAP on a broadcast TWT ID to indicate which TWT schedule is being requested for that mAP.

[0295] Additionally, the Link ID field may be included in the TWT setup frame or a new action frame. Additionally, the new action frame may include broadcast TWT elements. For example, the Link ID field may be included in the Broadcast TWT Parameter Set field or in the frame body.

[0296] B. A Link ID Bitmap can be defined.

[0297] An sSTA can instruct an sAP to request information about a TWT schedule for a given mAP or to request membership in a TWT scheduling for a given mAP via a link ID bitmap. For example, an sSTA can indicate a bit for a given mAP in the link ID bitmap based on the link ID for the mAP obtained during the discovery / multi-link setup process (see FIG. 14) (e.g., by setting the bit value corresponding to the mAP in the bitmap to 1), and additionally indicate a broadcast TWT ID to indicate a TWT schedule for the given mAP.

[0298] Additionally, the Link ID Bitmap field may be included in the TWT Setup frame or a new action frame. Additionally, the new action frame may include a Broadcast TWT element. For example, the Link ID Bitmap field may be included in the Broadcast TWT Parameter Set field or in the frame body.

[0299] FIG. 21 illustrates a TWT membership negotiation process according to one embodiment of the present disclosure.

[0300] Figure 21 illustrates an example of the TWT membership negotiation process between an AP MLD and a non-AP MLD that has established a multi-link setup. In Figure 21, sAP and mAP belong to the same AP MLD, and sAP announces Schedule 1 (B-TWT ID = 10), which is a broadcast TWT schedule for mAPs belonging to the same AP MLD, in its beacon frame ("B"). Although Figure 21 assumes that the frame indicating the broadcast TWT schedule is a beacon frame ("B"), this is an example, and other management frames may be used.

[0301] Based on the information in the received beacon frame, the non-AP MLD requests TWT membership between the mSTA and the mAP to the sAP through the sSTA (TWT request). Here, the sSTA can indicate which mAP the TWT membership is requested for by indicating the link ID (e.g., link ID = 1) or link ID bitmap (e.g., link ID bitmap = 010000000000000000000). In addition, the sSTA can indicate which broadcast TWT schedule for the corresponding mAP the TWT membership is requested for by indicating the ID of the broadcast TWT schedule (e.g., B-TWT ID = 10).

[0302] If the sAP that received the request from the sSTA accepts it, the mSTA can wake up before Schedule 1 and perform TWT operation.

[0303] Meanwhile, when using multi-link probing, when a partial list of TWT schedules of the mAP's TWT schedule is announced by the sAP, the Non-AP MLD may use the following method to obtain information about the entire TWT schedule for the mAP or to request information about some (broadcast) TWT IDs.

[0304] Referring back to FIG. 14, when transmitting a Multi-link Probe Request frame, the sSTA requests a Per-STA Profile subelement (e.g., a Per-STA Profile subelement with subelement ID 0 or a Per-STA Profile subelement dedicated to IMMW) for each mAP in the Probe Request ML IE in the form of a Partial Profile (Complete Profile = 0), which may include an element ID of a Broadcast TWT IE. Additionally or alternatively, at least one Broadcast TWT ID or a similar schedule-distinguishing ID may be included to indicate a specific TWT schedule.

[0305] Additionally or alternatively, a TWT setup frame or a new action frame may be used to request TWT schedule information. Additionally, a link ID or link ID bitmap indicating the mAP being requested may be included. Furthermore, a broadcast TWT ID or similar TWT schedule ID may be included to indicate the requested TWT schedule. Additionally or alternatively, when requesting TWT schedule information, if a broadcast TWT parameter set is included in the TWT setup frame or the new action frame, information (fields) that the sSTA does not yet know may be reserved (e.g., 0 or 1).

[0306] FIG. 22 illustrates the operation of a multi-link device for performing a TWT operation according to one embodiment of the present disclosure.

[0307] Figure 22 illustrates the operation of a multi-link device based on the previously proposed methods. The example in Figure 22 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 22 may be omitted depending on the circumstances and / or settings.

[0308] Here, a multi-link device may refer to a device capable of multi-link operation. In addition, the multi-link device may be a non-AP MLD (hereinafter, a first MLD) in which each STA belonging to the multi-link device is a non-AP STA, or an AP MLD (hereinafter, a second MLD) in which each STA belonging to the multi-link device is an AP.

[0309] In addition, it is assumed that a first non-AP STA and a second non-AP STA belong to a first MLD, and a first AP and a second AP belong to a second MLD. Here, the first non-AP STA and the first AP may operate on a sub-7 GHz band (e.g., 2.4 to 7.25 GHz), and the second non-AP STA and the second AP may operate on a millimeter wave (mmWave) band (e.g., 42 to 71 GHz).

[0310] Referring to FIG. 22, the first MLD receives a first frame from a first AP belonging to a second MLD and operating in a first band, by a first STA belonging to the first MLD (S2201).

[0311] Here, the first frame may include information about one or more TWT schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band. For example, information about the one or more TWT schedules may be transmitted in a Per-STA Profile sub-element of an ML IE (e.g., a basic ML IE) or a Per-STA Profile dedicated to IMMW.

[0312] Here, information regarding one or more TWT schedules may be transmitted based on a specific period. Furthermore, the specific period may be determined by the first AP.

[0313] For example, the specific period may be determined based on the transmission period of the first frame. In this case, the specific period and count for the one or more TWT schedules may be indicated by the first frame, the specific period may be indicated by the number of intervals between consecutive first frames, and the count may be indicated by the number of first frames to be transmitted before the next first frame indicating information for the one or more TWT schedules.

[0314] Additionally, for example, the specific period may be determined based on the period of a delivery traffic indication map (DTIM) of the second AP belonging to the second MLD. For example, based on the specific period being individually determined for the one or more TWT schedules, it may be determined which TWT schedule information is transmitted among the information on the one or more TWT schedules at each time point when the first frame is transmitted. For example, the specific period may be determined based on the total number of APs belonging to the second MLD, including the second AP.

[0315] Additionally, the information about the one or more TWT schedules may include information (e.g., an indication by a link ID or bitmap) indicating a link corresponding to the second AP that is aligned with the TWT schedule of the first AP. Additionally, the information about the one or more TWT schedules may include information (e.g., an indication by a TWT ID or bitmap) for identifying the one or more TWT schedules.

[0316] Additionally, the first frame may be either a beacon frame or a probe response frame. Here, information about the one or more TWT schedules may be transmitted in a multi-link element.

[0317] Additionally, the one or more TWT schedules may be broadcast TWT schedules.

[0318] Based on information about one or more TWT schedules, the first MLD performs transmission and / or reception of frames with the second AP belonging to the second MLD by the second STA belonging to the first MLD (S2202).

[0319] Here, the second STA can receive a downlink data frame from the second AP.

[0320] In addition, although not illustrated in FIG. 22, the first MLD may transmit, by the first STA belonging to the first MLD, to the first AP belonging to the second MLD a request frame for participation in a specific TWT schedule among the one or more TWT schedules associated with the second AP belonging to the second MLD. In addition, the first MLD may receive, by the first STA belonging to the first MLD, a response frame indicating whether to accept participation in the specific TWT schedule from the first AP belonging to the second MLD.

[0321] Additionally, the request frame may be a TWT setup frame or a new action frame (e.g., an action frame defined for the purpose of participating in a TWT schedule for an AP operating in mmWave).

[0322] Here, the request frame may include information indicating a link corresponding to the second AP (e.g., a link ID or an indication by a bitmap). In addition, the request frame may include information for identifying the specific TWT schedule (e.g., a TWT ID or an indication by a bitmap). For example, a TWT ID (e.g., a broadcast TWT ID) may be added to the broadcast TWT parameter set field or included in the frame body.

[0323] In steps S2201 and S2202, exchanging frames between the first MLD and the second MLD means exchanging PPDUs containing the corresponding frames.

[0324] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0325] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0326] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0327] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0328] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0329] The above-described STF-part (e.g., the U-STF field) may contain an STF sequence.

[0330] The above-described LTF-part (e.g., U-LTF field) may include a training field (i.e., LTF sequence) for channel estimation.

[0331] The data-part described above may include user data and may include packets (e.g., MPDUs) (i.e., frames) for upper layers.

[0332] The method described in the example of FIG. 22 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may be configured to transmit a frame (or a PPDU including a frame) via the transceiver(s) (106). Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 22 or the examples described above when executed by one or more processors (102).

[0333] FIG. 23 illustrates the operation of a multi-link device for performing a TWT operation according to one embodiment of the present disclosure.

[0334] Figure 23 illustrates the operation of a multi-link device based on the previously proposed methods. The example in Figure 23 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 23 may be omitted depending on the circumstances and / or settings.

[0335] Here, a multi-link device may refer to a device capable of multi-link operation. In addition, the multi-link device may be a non-AP MLD (hereinafter, a first MLD) in which each STA belonging to the multi-link device is a non-AP STA, or an AP MLD (hereinafter, a second MLD) in which each STA belonging to the multi-link device is an AP.

[0336] In addition, it is assumed that a first non-AP STA and a second non-AP STA belong to a first MLD, and a first AP and a second AP belong to a second MLD. Here, the first non-AP STA and the first AP may operate on a sub-7 GHz band (e.g., 2.4 to 7.25 GHz), and the second non-AP STA and the second AP may operate on a millimeter wave (mmWave) band (e.g., 42 to 71 GHz).

[0337] Referring to FIG. 23, the second MLD transmits a first frame to the first STA belonging to the first MLD by the first AP belonging to the second MLD and operating in the first band (S2301).

[0338] Here, the first frame may include information about one or more TWT schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band. For example, information about the one or more TWT schedules may be transmitted in a Per-STA Profile sub-element of an ML IE (e.g., a basic ML IE) or a Per-STA Profile dedicated to IMMW.

[0339] Here, information regarding one or more TWT schedules may be transmitted based on a specific period. Furthermore, the specific period may be determined by the first AP.

[0340] For example, the specific period may be determined based on the transmission period of the first frame. In this case, the specific period and count for the one or more TWT schedules may be indicated by the first frame, the specific period may be indicated by the number of intervals between consecutive first frames, and the count may be indicated by the number of first frames to be transmitted before the next first frame indicating information for the one or more TWT schedules.

[0341] Additionally, for example, the specific period may be determined based on the period of a delivery traffic indication map (DTIM) of the second AP belonging to the second MLD. For example, based on the specific period being individually determined for the one or more TWT schedules, it may be determined which TWT schedule information is transmitted among the information on the one or more TWT schedules at each time point when the first frame is transmitted. For example, the specific period may be determined based on the total number of APs belonging to the second MLD, including the second AP.

[0342] Additionally, the information about the one or more TWT schedules may include information (e.g., an indication by a link ID or bitmap) indicating a link corresponding to the second AP that is aligned with the TWT schedule of the first AP. Additionally, the information about the one or more TWT schedules may include information (e.g., an indication by a TWT ID or bitmap) for identifying the one or more TWT schedules.

[0343] Additionally, the first frame may be either a beacon frame or a probe response frame. Here, information about the one or more TWT schedules may be transmitted in a multi-link element.

[0344] Additionally, the one or more TWT schedules may be broadcast TWT schedules.

[0345] Based on information about one or more TWT schedules, the second MLD performs transmission and / or reception of frames with the second STA belonging to the first MLD by the second AP belonging to the second MLD (S2302).

[0346] Here, the second AP can transmit a downlink data frame to the second STA.

[0347] In addition, although not illustrated in FIG. 23, the second MLD may receive, by the first AP belonging to the second MLD, a request frame for participation in a specific TWT schedule among the one or more TWT schedules associated with the second AP belonging to the second MLD from the first STA belonging to the first MLD. In addition, the second MLD may transmit, by the first AP belonging to the second MLD, a response frame indicating whether to accept participation in the specific TWT schedule to the first STA belonging to the first MLD.

[0348] Additionally, the request frame may be a TWT setup frame or a new action frame (e.g., an action frame defined for the purpose of participating in a TWT schedule for an AP operating in mmWave).

[0349] Here, the request frame may include information indicating a link corresponding to the second AP (e.g., a link ID or an indication by a bitmap). In addition, the request frame may include information for identifying the specific TWT schedule (e.g., a TWT ID or an indication by a bitmap). For example, a TWT ID (e.g., a broadcast TWT ID) may be added to the broadcast TWT parameter set field or included in the frame body.

[0350] In steps S2201 and S2202, exchanging frames between the first MLD and the second MLD means exchanging PPDUs containing the corresponding frames.

[0351] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0352] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0353] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0354] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0355] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0356] The above-described STF-part (e.g., the U-STF field) may contain an STF sequence.

[0357] The above-described LTF-part (e.g., U-LTF field) may include a training field (i.e., LTF sequence) for channel estimation.

[0358] The data-part described above may include user data and may include packets (e.g., MPDUs) (i.e., frames) for upper layers.

[0359] The method described in the example of FIG. 23 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may be configured to receive a frame (or a PPDU including a frame) via a transceiver(s) (206). Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 23 or the examples described above when executed by one or more processors (202).

[0360] In conventional wireless LAN systems, MLD operation only supports operation in the sub-7 GHz band, but unlike this, according to the MLD operation according to the examples of the present disclosure, it is possible to discover APs or non-AP STAs operating in the mmWave band. In addition, since association (i.e., multi-link setup) and frame exchange can be performed with APs or non-AP STAs operating in the mmWave band, wireless transmission and reception efficiency can be improved. In addition, since the affiliated AP operating in the sub-7 GHz of the AP MLD announces the TWT schedule to the affiliated AP operating in the mmWave band instead, the affiliated STAs operating in the mmWave band of the non-AP MLD can perform frame exchange based on the TWT schedule, thereby reducing power consumption.

[0361] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0362] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0363] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0364] The method proposed in this disclosure is described with a focus on examples applied to IEEE 802.11-based systems, but can be applied to various wireless LANs or wireless communication systems in addition to IEEE 802.11-based systems.

Claims

1. A method performed by a first multi-link device (MLD), the method comprising: A step of receiving a first frame from a first access point (AP) belonging to a second MLD and operating in a first band by a first station (STA) belonging to the first MLD, wherein the first frame includes information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band; and A method comprising, based on information about the one or more TWT schedules, performing transmission and / or reception of a frame with the second AP belonging to the second MLD by the second STA belonging to the first MLD.

2. In paragraph 1, A method wherein information about one or more TWT schedules is transmitted based on a specific period.

3. In paragraph 2, A method wherein the specific period is determined based on the transmission period of the first frame.

4. In paragraph 3, The specific period and count for the one or more TWT schedules are indicated by the first frame, A method wherein the specific period is indicated by the number of intervals between consecutive first frames, and the count is indicated by the number of first frames to be transmitted before the next first frame indicating information about the one or more TWT schedules.

5. In paragraph 2, A method in which the specific period is determined based on the period of a delivery traffic indication map (DTIM) of the second AP belonging to the second MLD.

6. In paragraph 2, A method in which information about a TWT schedule among the information about the one or more TWT schedules is determined to be transmitted based on the specific period being individually determined for the one or more TWT schedules at each time point when the first frame is transmitted.

7. In paragraph 2, A method wherein the specific period is determined based on the total number of APs belonging to the second MLD, including the second AP.

8. In paragraph 1, A method wherein the information about the one or more TWT schedules includes information indicating a link corresponding to the second AP that is aligned with the TWT schedule of the first AP.

9. In paragraph 8, A method wherein the information about the one or more TWT schedules includes information for identifying the one or more TWT schedules.

10. In paragraph 1, A step of transmitting, by a first STA belonging to the first MLD, a request frame to the first AP belonging to the second MLD to participate in a specific TWT schedule among the one or more TWT schedules associated with the second AP belonging to the second MLD; and A method further comprising the step of receiving, by the first STA belonging to the first MLD, a response frame indicating whether to accept participation in the specific TWT schedule from the first AP belonging to the second MLD.

11. In paragraph 10, A method wherein the request frame includes information indicating a link corresponding to the second AP.

12. In paragraph 11, A method wherein the request frame includes information for identifying the specific TWT schedule.

13. In paragraph 1, A method wherein the first frame is either a beacon frame or a probe response frame.

14. In paragraph 1, A method wherein information about one or more TWT schedules is transmitted in a multi-link element.

15. In paragraph 1, A method wherein the one or more TWT schedules are broadcast TWT schedules.

16. In paragraph 1, A method wherein the first band is a sub-7 GHz band and the second band is a millimeter wave (mmWave) band.

17. The first multi-link device (MLD) is: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: A first frame is received by a first station (STA: station) belonging to the first MLD from a first access point (AP: access point) belonging to the second MLD and operating in a first band, wherein the first frame includes information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band, and A device configured to perform transmission and / or reception of frames with the second AP belonging to the second MLD by the second STA belonging to the first MLD based on information about the one or more TWT schedules.

18. A method performed by a second multi-link device (MLD), the method comprising: A step of transmitting a first frame to a first station (STA) belonging to the first MLD by a first access point (AP) belonging to the second MLD and operating in a first band, wherein the first frame includes information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band; and A method comprising, based on information about the one or more TWT schedules, performing transmission and / or reception of a frame with the second STA belonging to the first MLD by the second AP belonging to the second MLD.

19. The second multi-link device (MLD) is: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: A first frame is transmitted to a first station (STA) belonging to the first MLD by a first access point (AP) belonging to the second MLD and operating in a first band, wherein the first frame includes information about one or more target wake time (TWT) schedules associated with a second AP belonging to the second MLD and operating in a second band different from the first band, and A device configured to perform transmission and / or reception of frames with a second STA belonging to the first MLD by the second AP belonging to the first MLD based on information about the one or more TWT schedules.

20. In a processing device configured to control a multi-link device (MLD) in a wireless LAN system, the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions that, when executed by said one or more processors, perform a method according to any one of claims 1 to 14.

21. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a device in a wireless LAN system to perform a method according to any one of claims 1 to 14.

Images