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

Abstract

Disclosed are a method and a device for operation in a wireless LAN system. A method according to an embodiment of the present disclosure may comprise the steps of: transmitting, in a second band, a request frame including first information related to whether communication based on a first band is available to a second STA, by a first station (STA); receiving, in the second band, a response frame for the request frame from the second STA, by the first STA; and performing, by the first STA, communication based on the first band on the basis of second information included in the response frame and indicating that communication based on the first band is available.

Description

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

[0001] The present disclosure relates to communication operations in a Wireless Local Area Network (WLAN) system, and more specifically, to a method and apparatus for performing a multi-link operation (MLO) in a next-generation wireless LAN system.

[0002] New technologies have been introduced for wireless LANs (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and reduce latency. Among wireless LAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, technologies recently introduced to wireless LANs 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 an improved wireless communication environment, enhanced technologies for Extremely High Throughput (EHT) have been developed and introduced. For example, technologies for Multiple Input Multiple Output (MIMO) supporting increased bandwidth, efficient utilization of multiple bands, and increased spatial streams, as well as technologies for multiple access points (AP) coordination, are being researched. In particular, various technologies are being studied to support traffic with low latency or real-time characteristics. Furthermore, new technologies to support ultra-high reliability (UHR), including improvements or extensions of EHT technology, are being discussed.

[0004] The technical problem of the present disclosure is to provide a method and apparatus for performing MLO operations in a wireless LAN system.

[0005] The technical problem of the present disclosure is to provide a method in which the millimeter band is used as a single link for MLO.

[0006] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below.

[0007] A method according to one embodiment of the present disclosure may include: transmitting a request frame containing first information regarding whether communication based on a first band is available to a second STA by a first station (STA) in a second band; receiving a response frame for the request frame from the second STA by the first STA in the second band; and performing communication based on the first band by the first STA based on the fact that second information indicating that communication based on the first band is available is included in the response frame.

[0008] A method according to another embodiment of the present disclosure may include: receiving a request frame containing first information regarding whether communication based on a first band is available from a first STA by a second station (STA) in a second band; transmitting a response frame for the request frame to the first STA by the second STA in the second band; and performing communication based on the first band by the second STA based on the second information indicating that communication based on the first band is available being included in the response frame.

[0009] By various embodiments of the present disclosure, a method and apparatus for performing MLO operations in a wireless LAN system may be provided.

[0010] By various embodiments of the present disclosure, power consumption and delay issues can be reduced while communication is performed in the mmWave band.

[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

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

[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 drawing showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

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

[0016] FIG. 4 is a drawing illustrating a backoff process to which the present disclosure may be applied.

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

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

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

[0020] FIG. 8 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

[0021] Figure 9 is a diagram illustrating a situation in which a Deafness problem occurs.

[0022] FIG. 10 is a flowchart for explaining a method performed by a first STA according to one embodiment of the present disclosure.

[0023] FIG. 11 is a flowchart illustrating a method performed by a second STA according to one embodiment of the present disclosure.

[0024] FIG. 12 is a diagram illustrating a procedure for exchanging information on whether communication support using mmWave is possible, according to one embodiment of the present disclosure.

[0025] FIG. 13 is a diagram illustrating a procedure for exchanging information on whether communication support using mmWave is possible, according to one embodiment of the present disclosure.

[0026] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

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

[0028] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0029] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0030] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and in the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term "and / or" as used in this disclosure may refer to any one of the related enumerated items, or refers to and includes any and all possible combinations of two or more of them. Additionally, the " / " between words in this disclosure has the same meaning as "and / or" unless otherwise noted.

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

[0032] The following describes the technical features to which the examples of the present disclosure may be applied.

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

[0034] The first device (100) and the second device (200) exemplified in FIG. 1 may be replaced with various terms such as terminal, wireless device, WTRU (Wireless Transmit Receive Unit), UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), MSS (Mobile Subscriber Unit), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), or simply user. Additionally, the first device (100) and the second device (200) may be replaced with various terms such as access point (AP), base station (BS), fixed station, Node B, base transceiver system (BTS), network, artificial intelligence (AI) system, road side unit (RSU), repeater, router, relay, gateway, etc.

[0035] The device (100, 200) exemplified in FIG. 1 may be referred to as a station (STA). For example, the device (100, 200) exemplified in FIG. 1 may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, or a receiving STA. For example, the STA (110, 200) may perform the role of an access point (AP) or a non-AP. That is, in the present disclosure, the STA (110, 200) may perform the functions of an AP and / or a non-AP. If the STA (110, 200) performs the AP function, it may simply be referred to as an AP, and if the STA (110, 200) performs the non-AP function, it may simply be referred to as a STA. Additionally, in the present disclosure, the AP may also be indicated as an AP STA.

[0036] 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) may include interfaces for the medium access control (MAC) layer and the physical layer (PHY) that comply with the specifications of the IEEE 802.11 standard.

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

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

[0039] The second device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this disclosure. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal 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 store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement 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 through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be used in combination with an RF unit. In the present disclosure, the device may refer to a communication modem / circuit / chip.

[0040] Hereinafter, 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 Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this 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 flowcharts of operation disclosed in this disclosure. One or more processors (102, 202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this disclosure and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., a baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this disclosure.

[0041] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or 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 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure may be included in 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 sequences disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0042] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0043] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of the present disclosure to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in the present disclosure from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected 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, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this disclosure through one or more antennas (108, 208). In this disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0044] 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 transceiver (106, 206) of FIG. 1 may perform the operation of transmitting and receiving signals (e.g., packets or PPDU (Physical Layer Protocol Data Unit) according to IEEE 802.11a / b / g / n / ac / ax / be / bn, etc.). Additionally, the operation of generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals by various STAs in the present disclosure may be performed by the processor (102, 202) of FIG. 1. For example, an example of an operation to generate a transmission and reception signal or to perform data processing or operations in advance for a transmission and reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of fields (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 4) power control operations and / or power saving operations applied to the STA; and 5) operations related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding transmission and reception signals in the following example can be stored in the memory (104, 204) of FIG. 1.

[0045] In the following, the 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 the AP STA, and the receiver may be part of the non-AP STA. The 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 the non-AP STA, and the receiver may be part of the AP STA.

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

[0047] The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports STA mobility transparent to the upper layer can be provided. A Basic Service Set (BSS) corresponds to the basic building block of a wireless LAN. Figure 2 exemplarily illustrates 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). In Figure 2, the ellipse representing the BSS can also be understood as representing the coverage area where the STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). If a STA moves outside the BSA, it becomes unable to communicate directly with other STAs within that BSA.

[0048] Excluding the DS illustrated in Fig. 2, the most basic type of BSS in a wireless LAN is the Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For instance, assuming other components are omitted, a BSS1 composed of only STA1 and STA2, or a BSS2 composed of only STA3 and STA4, can each be considered a representative example of an IBSS. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, this type of wireless LAN is not configured through pre-planning but can be configured when a LAN is needed, and this can be referred to as an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. In other words, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and since connections to distributed systems (DS) are not allowed, they form a self-contained network.

[0049] The membership of an STA in a BSS can be dynamically changed by the STA being turned on or off, or by the STA entering or leaving the BSS area. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services of the BSS infrastructure, an STA must be associated with the BSS. This association can be configured dynamically and may include the use of a Distribution System Service (DSS).

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

[0051] DS refers to a structure in which BSSs are interconnected. Specifically, as shown in FIG. 2, a BSS may exist as a component in an extended form of a network composed of multiple BSSs. DS is a logical concept and can be specified by the characteristics of the Distributed System Medium (DSM). In this regard, the Wireless Medium (WM) and the DSM can be logically distinguished. Each logical medium is used for a different purpose and is utilized by different components. These media are not limited to being identical or different. The flexibility of the wireless LAN structure (DS structure or other network structure) can be explained by the fact that multiple media are logically distinct in this way. That is, the wireless LAN structure can be implemented in various ways, and the corresponding wireless LAN structure can be specified independently by the physical characteristics of each implementation.

[0052] DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary for handling addresses to destinations. Additionally, DS may include a component called a portal that acts as a bridge for connecting the wireless LAN with another network (e.g., IEEE 802.X).

[0053] An AP refers to an entity that enables access to a DS via a WM for combined non-AP STAs and also possesses the functionality of an STA. Data movement between a BSS and a DS can be performed through the AP. For example, STA2 and STA3 shown in FIG. 2 possess the functionality of an STA and provide the ability for combined non-AP STAs (STA1 and STA4) to access a DS. Furthermore, since all APs fundamentally correspond to STAs, all APs are addressable entities. The address used by the AP for communication on the WM and the address used by the AP for communication on the DSM do not necessarily have to be the same. A BSS composed of an AP and one or more STAs can be referred to as an infrastructure BSS.

[0054] Data transmitted from one of the STA(s) coupled to the AP to the STA address of the AP can always be received at an uncontrolled port and processed by an IEEE 802.1X port access entity. Additionally, if the controlled port is authenticated, the transmitted data (or frame) can be forwarded to the DS.

[0055] In addition to the structure of the aforementioned DS, an Extended Service Set (ESS) may be configured to provide wider coverage.

[0056] An ESS refers to a network of arbitrary size and complexity composed of DSs and BSSs. An ESS can correspond to a set of BSSs connected to a single DS. However, an ESS does not contain a DS. An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs included in 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 included in a single ESS can have the same Service Set Identification (SSID). The SSID is distinct from the BSSID, which is the identifier for the BSS.

[0057] In wireless LAN systems, no assumptions are made regarding the relative physical locations of BSSs, and all of the following forms are possible. BSSs may partially overlap, which is a form commonly used to provide continuous coverage. Additionally, BSSs may not be physically connected, and logically, there is no limit to the distance between BSSs. Furthermore, BSSs may be located in the same physical location, which can be used to provide redundancy. Also, one (or more) IBSS or ESS networks may physically exist in the same space as one (or more) ESS networks. This may apply to ESS network forms such as when an ad-hoc network operates at a location where an ESS network exists, when wireless networks that physically overlap are configured by different organizations, or when two or more different access and security policies are required at the same location.

[0058] FIG. 3 is a diagram illustrating a link setup process to which the present disclosure can be applied.

[0059] In order 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 go through authentication procedures for security. The link setup process can also be referred to as the session initiation process or the session setup process. Additionally, the processes of discovery, authentication, association, and security setup in the link setup process can be collectively referred to as the association process.

[0060] In step S310, the STA may perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks existing in a specific area is called scanning.

[0061] Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels to search for nearby APs, transmits a probe request frame, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame; however, in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (i.e., transmit and receive probe request / response on channel 2).

[0062] Although not illustrated in FIG. 3, the scanning operation may be performed using a passive scanning method. In passive scanning, the STA performing the scanning waits for a beacon frame while switching between channels. A beacon frame is one of the management frames defined in IEEE 802.11, which is periodically transmitted to announce the presence of a wireless network and to allow the scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, and in an IBSS, the STAs within the IBSS take turns transmitting beacon frames. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. The STA that receives the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel, and can perform scanning in the next channel in the same way. When comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

[0063] 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 in step S340 described later.

[0064] The authentication process involves the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

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

[0066] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.

[0067] After the STA is successfully authenticated, the association process can be performed in step S330. The association process includes the STA transmitting an association request frame to the AP, and in response, the AP transmitting an association response frame to the STA.

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

[0069] After the STA is successfully joined to the network, a security setup process can be performed in step S340. The security setup process in step S340 may be described as an authentication process through RSNA (Robust Security Network Association) requests / responses, and the authentication process in step S320 may be referred to as the first authentication process, and the security setup process in step S340 may simply be referred to as the authentication process.

[0070] The security setup process of step S340 may include, for example, a private key setup process through a 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame. Additionally, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.

[0071] FIG. 4 is a drawing illustrating a backoff process to which the present disclosure may be applied.

[0072] In wireless LAN systems, the basic access mechanism for MAC (Medium Access Control) is the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism is also known as the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and it basically employs a "listen before talk" access mechanism. According to this type of access mechanism, the AP and / or STA may perform Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time interval (e.g., DIFS (DCF Inter-Frame Space)) before starting transmission. If the sensing result determines that the medium is in an idle status, it starts transmitting a frame through that 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 wait by setting a delay period for medium access (e.g., a random backoff period) before attempting to transmit a frame. 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.

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

[0074] Referring to FIG. 4, the operation based on the random backoff period is described. When a medium in an occupied / busy state changes to an idle state, multiple STAs may attempt to transmit data (or frames). As a measure to minimize collisions, each STA may select a random backoff count and attempt transmission after waiting for the corresponding slot time. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​in the range from 0 to CW. Here, CW is the Contention Window parameter value. The CW parameter is given an initial value of CWmin, but in the case of transmission failure (e.g., failure to receive an ACK for a transmitted frame), it may take a value twice that amount. When the CW parameter value becomes CWmax, data transmission may be attempted while maintaining the CWmax value until data transmission is successful; if data transmission is successful, it is reset to the CWmin value. The values ​​of CW, CWmin, and CWmax are 2 n It is desirable to set it to -1 (n=0, 1, 2, ...).

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

[0076] In the example of Fig. 4, when a packet to be transmitted arrives at the MAC of STA3, STA3 confirms that the medium is idle for DIFS and can immediately transmit the frame. The remaining STAs monitor whether the medium is occupied or busy and wait. Meanwhile, data to be transmitted may also arise from each of STA1, STA2, and STA5, and each STA can perform a countdown of the backoff slot according to a random backoff count value selected by each after waiting for DIFS when the medium is monitored to be idle. Assume the case where STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. That is, this exemplifies a case where, at the point when STA2 finishes the backoff count and starts transmitting the frame, the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1. STA1 and STA5 pause the countdown briefly and wait while STA2 occupies the medium. When STA2's possession ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the paused backoff count. That is, they can start transmitting a frame after counting down the remaining backoff slots corresponding to the remaining backoff time. Since STA5's remaining backoff time was shorter than STA1's, STA5 starts transmitting the frame. While STA2 is occupying the medium, data to be transmitted may also be generated by STA4. From STA4's perspective, when the medium becomes idle, it waits for DIFS, performs a countdown based on a random backoff count value selected by itself, and can start transmitting a frame. The example in Figure 4 illustrates a case where STA5's remaining backoff time happens to match STA4's random backoff count value; in this case, a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 receives an ACK, resulting in a failure to transmit data.In this case, STA4 and STA5 can double the CW value, select a random backoff count value, and perform a countdown. STA1 waits while the medium is occupied due to transmission by STA4 and STA5, and when the medium becomes idle, it waits for DIFS, and then can start transmitting frames after the remaining backoff time has passed.

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

[0078] A QoS (Quality of Service) STA can transmit a frame after backoff, which is performed after the passage of the arbitration IFS (AIFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC). Here, the frame for which AIFS[i] can be used can be a data frame or a management frame, and can also be a control frame rather than a response frame.

[0079] FIG. 5 is a diagram illustrating a CSMA / CA-based frame transmission operation to which the present disclosure may be applied.

[0080] As previously mentioned, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, where the STA directly senses the medium. Virtual carrier sensing is intended to mitigate problems that may occur in medium access, such as the hidden node problem. For virtual carrier sensing, the STA's MAC can utilize the Network Allocation Vector (NAV). The NAV is a value that indicates to other STAs the time remaining until the medium becomes available, provided that the STA currently using or authorized to use the medium is using it. Therefore, the value set as the NAV corresponds to the period during which the medium is scheduled to be used by the STA transmitting the frame, and the 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 frame's MAC header.

[0081] In the example of FIG. 5, it is assumed that STA1 intends to transmit data to STA2, and STA3 is located in a position where it can overhear part or all of the frames transmitted and received between STA1 and STA2.

[0082] In order to reduce the possibility of collisions between multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism utilizing RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, the medium may be determined to be idle based on the carrier sensing result of STA3. That is, STA1 may be a hidden node to STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, the medium may be determined to be idle based on the carrier sensing result of STA3. That is, STA2 may be a hidden node to STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, it is possible to prevent a STA outside the transmission range of either STA1 or STA2, or a STA outside the carrier sensing range for transmission from STA1 or STA3, from attempting to occupy the channel during data transmission and reception between STA1 and STA2.

[0083] Specifically, STA1 can determine whether the channel is in use through carrier sensing. In terms of physical carrier sensing, STA1 can determine the channel occupancy idle state based on the energy magnitude or signal correlation detected in the channel. Additionally, in terms of virtual carrier sensing, STA1 can determine the channel occupancy state using a NAV (network allocation vector) timer.

[0084] If the channel is idle during DIFS, STA1 can send an RTS frame to STA2 after performing backoff. If STA2 receives the RTS frame, it can send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0085] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can set a NAV timer for the duration of subsequently transmitted frames (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) using the duration information included in the RTS frame. Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can set a NAV timer for the duration of subsequently transmitted frames (e.g., SIFS + data frame + SIFS + ACK frame) using the duration information included in the CTS 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.

[0086] If STA1 receives a CTS frame from STA2, it may transmit a data frame to STA2 after SIFS from the time the reception of the CTS frame is completed. If STA2 successfully receives the data frame, it may transmit an ACK frame to STA1 as an acknowledgment to the data frame after SIFS. STA3 may determine whether the channel is in use through carrier sensing when the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during DIFS from the time the NAV timer expires, it may attempt channel access after a contention window (CW) based on random backoff has passed.

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

[0088] Based on instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare the MPDU (MAC PDU) to be transmitted. For example, upon receiving an instruction from the MAC layer requesting the start of transmission, the PHY layer switches to transmit mode and can construct the information provided by the MAC layer (e.g., data) into a frame for transmission. Additionally, if the PHY layer detects a valid preamble of a received frame, it monitors the preamble header and sends an instruction to the MAC layer indicating the start of reception.

[0089] As such, information transmission and reception in wireless LAN systems are carried out in the form of frames, and for this purpose, the Physical Layer Protocol Data Unit (PPDU) format is defined.

[0090] A basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a Signal (SIGNAL) field, and a Data field. The most basic (e.g., the non-HT (High Throughput)) PPDU format illustrated in FIG. 7 may consist only of Legacy-STF (Legacy-STF), Legacy-LTF (Legacy-LTF), Legacy-SIG (Legacy-SIG) fields and a Data field. In addition, 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 other types of) RL-SIG, U-SIG, non-legacy SIG fields, 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.

[0091] 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 and frequency error estimation. STF and LTF can be considered signals for synchronization and channel estimation in the OFDM physical layer.

[0092] The SIG field may contain various information related to the transmission and reception of the PPDU. For example, the L-SIG field consists 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 contain information regarding the modulation and coding rates of the data. For example, the 12-bit Length field may contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the Length field may be determined as a multiple of 3. For example, for HE PPDUs, the value of the Length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0093] The data field may include a SERVICE field, a PSDU (Physical layer Service Data Unit), and PPDU TAIL bits, and may also include padding bits if necessary. Some bits of the SERVICE field may be used for synchronization of the descrambler at the receiver. The PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated or used by the upper layer. The PPDU TAIL bits may be used to return the encoder to a 0 state. Padding bits may be used to adjust the length of the data field to a predetermined unit.

[0094] A MAC PDU is 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 a MAC PDU and can be transmitted or received through the PSDU of the data portion in the PPDU format.

[0095] The MAC header includes a Frame Control field, a Duration / ID field, an Address field, etc. The Frame Control field may contain control information necessary for transmitting or receiving frames. The Duration / ID field may be set as the time for transmitting the corresponding frame. Address subfields may indicate the frame's receiver address, transmitter address, destination address, and source address, and some address subfields may be omitted. Specific details regarding each subfield of the MAC header, including Sequence Control, QoS Control, and HT Control subfields, can be found in the IEEE 802.11 standard document.

[0096] The Null-Data PPDU (NDP) format refers to a PPDU format that does not include a data field. In other words, NDP is a frame format that includes the PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and additionally, non-legacy SIG, non-legacy STF, and non-legacy LTF if present) from a standard PPDU format, but excludes the remaining parts (i.e., the data field).

[0097] FIG. 7 is a drawing illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure may be applied.

[0098] Various forms of PPDU have been used in standards such as IEEE 802.11a / g / n / ac / ax. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format may also be referred to as the non-HT PPDU format (Fig. 7(a)).

[0099] 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 the HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a Data field, without including L-STF, L-LTF, and L-SIG (not shown).

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

[0101] An example of the HE PPDU format (IEEE 802.11ax) includes the 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 the 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 multiple users (MU), but is not included in the HE PPDU format for single users (SU). Additionally, the HE trigger-based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field may vary to 8 µs. 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 16 µs. For example, RL-SIG can be configured identically to L-SIG. Based on the presence of RL-SIG, the receiving STA can determine that the received PPDU is a HE PPDU or the EHT PPDU described later.

[0102] The EHT PPDU format may include the EHT MU (multi-user) 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 RL-SIG following L-SIG, but it may include U (universal)-SIG, EHT-SIG, EHT-STF, and EHT-LTF following RL-SIG.

[0103] The EHT MU PPDU of FIG. 7(e) corresponds to a PPDU that carries one or more data (or PSDU) 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.

[0104] The EHT-SIG is omitted in the EHT TB PPDU of FIG. 7(f) compared to the EHT MU PPDU. A STA that receives 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.

[0105] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated so that demodulation and decoding can be attempted even on legacy STAs, and mapped based on a defined 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 so that they can be demodulated and decoded by a STA that has successfully decoded a non-legacy SIG (e.g., U-SIG and / or EHT-SIG) to obtain the information contained in the corresponding fields, and mapped based on a defined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

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

[0107] The U-SIG included in the EHT PPDU format of FIG. 7 can be constructed based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol for the U-SIG (e.g., OFDM symbol) can have a duration of 4 µs, and the U-SIG can have a total duration of 8 µs. 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.

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

[0109] For example, A number of uncoded bits may be transmitted through U-SIG, and the first symbol of U-SIG (e.g., U-SIG-1 symbol) transmits the first X bits of the total A bit information, and the second symbol of U-SIG (e.g., U-SIG-2 symbol) transmits the remaining Y bits of the total A bit information. The A bit information (e.g., 52 uncoded bits) may include a CRC field (e.g., a field of 4 bits) and a tail field (e.g., a field of 6 bits). The tail field may be used to terminate the trellis of the convolution decoder and may be set to, for example, 0.

[0110] A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG may be included in a new PPDU format not shown in FIG. 7 (e.g., UHR PPDU format), 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 may be the same, and some or all of the version-dependent bits may be different.

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

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

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

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

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

[0116] Preamble puncturing may refer to the transmission of a PPDU in which a signal is not present in one or more frequency units within the PPDU bandwidth. For example, the size of the frequency unit (or the resolution of preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth of a predetermined size or larger.

[0117] 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. A non-legacy SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 µs. Information regarding the number of symbols used for EHT-SIG may be included in the previous SIG (e.g., HE-SIG-A, U-SIG, etc.).

[0118] Non-legacy SIGs, such as HE-SIG-B and EHT-SIG, may include common fields and user-specific fields. Common fields and user-specific fields may be coded individually.

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

[0120] 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 may be related to MU-MIMO allocation or non-MU-MIMO allocation.

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

[0122] An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. Additionally, an RU may be defined when transmitting signals to a single STA. Resources may be allocated on an RU basis for non-legacy STF, non-legacy LTF, and Data fields.

[0123] Applicable RU sizes can be defined according to the PPDU bandwidth. RUs 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 80 MHz PPDU, the RU placement for HE PPDU and EHT PPDU may differ. The applicable RU sizes, number of RUs, RU locations, DC (direct current) subcarrier locations and numbers, null subcarrier locations and numbers, and guard subcarrier locations and numbers for each PPDU bandwidth can be referred to as a tone-plan. For example, a tone-plan for a wide bandwidth may be defined as a multiple repetition of a tone-plan for a low bandwidth.

[0124] RUs of various sizes can be defined as 26-ton RUs, 52-ton RUs, 106-ton RUs, 242-ton RUs, 484-ton RUs, 996-ton RUs, 2x996-ton RUs, 3x996-ton RUs, etc. An MRU (multiple RU) is distinguished from multiple individual RUs and corresponds to a group of subcarriers composed 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. In addition, multiple RUs constituting a single MRU may be continuous or non-continuous in the frequency domain.

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

[0126] The names of the respective fields in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by such names. Furthermore, the examples of the present disclosure may be applied not only to the PPDU formats exemplified in FIG. 7, but also to new PPDU formats based on the PPDU formats of FIG. 7 in which some fields are excluded and / or some fields are added.

[0127] Multi-Link Operation (MLO)

[0128] The following describes the multi-link (ML) operations supported by the STA according to the present disclosure.

[0129] The STA (AP STA and / or non-AP STA) described in this disclosure may support multi-link (ML) communication. ML communication may refer to communication that supports multiple links. The links involved in ML communication may include channels (e.g., 20 / 40 / 80 / 160 / 240 / 320 MHz channels) in the frequency band (e.g., 2.4 GHz band, 5 GHz band, 6 GHz 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 by a single STA for ML communication may belong to the same frequency band or to different frequency bands. Additionally, each link may correspond to a frequency unit of a predetermined size (e.g., channel, subchannel, RU, etc.). Furthermore, some or all of the multiple links may be frequency units of the same size or frequency units of different sizes.

[0130] When a single STA supports multiple links, the transmitting and receiving devices supporting each link can operate as a single logical STA. That is, an MLD refers to a device that, as a logical entity, has one or more affiliated STAs and a single MAC Service Access Point (SAP) for a single MAC data service and logical link control (LLC). A non-AP MLD refers to an MLD where 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 the reception or exchange of frames on one or more links at a time. An AP MLD refers to an MLD where each STA affiliated with the MLD is an AP STA.

[0131] Multi-Link Operation (MLO) can enable non-AP MLDs to discover, authenticate, associate, and set up multiple links for AP MLDs. Based on the supported capabilities exchanged during the association process, 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 operation parameters independently of other STA(s) affiliated with the same MLD.

[0132] Through a multi-link setup process, the AP MLD and / or 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 the following: whether simultaneous transmit and receive (STR) operations that allow simultaneous transmission and receive on multiple links supported by the MLD, or non-simultaneous transmit and receive (NSTR) operations that do not allow simultaneous transmission and receive; information regarding the number / upper limit of UL / DL links; information regarding the location / band / resource of UL / DL links; information regarding frame types available or preferred on at least one UL / DL link (e.g., management, control, data, etc.); information regarding ACK policies available or preferred on at least one UL / DL link; or information regarding traffic identifiers (TID) available on at least one UL / DL link.

[0133] An AP MLD (e.g., an NSTR mobile AP MLD) may set one of the multiple links as the primary link. The AP MLD may perform beacon frames, probe response frames, and group-addressed data frames only on the primary link. The remaining other links of the multiple links may be 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. Additionally, a non-AP MLD may perform frame exchange during authentication, (re)association, and 4-way handshake only on the primary link.

[0134] 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 may 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, TIDs are mapped to all setup links, so all setup links can be enabled.

[0135] FIG. 8 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

[0136] A trigger frame may allocate resources for one or more TB PPDU transmissions and request TB PPDU transmissions. The trigger frame may also include other information required by an STA that transmits a TB PPDU in response. The trigger frame may include common info and user info list fields in the frame body.

[0137] The common information field may include information that applies commonly to one or more TB PPDU transmissions requested by a trigger frame, such as trigger type, UL length, whether a subsequent trigger frame exists (e.g., More TF), whether a CS (channel sensing) is required, UL BW (bandwidth), etc. FIG. 8 illustrates an exemplary format for the EHT variant common information field.

[0138] The 4-bit trigger type subfield can have values ​​from 0 to 15. Among these, the values ​​0, 1, 2, 3, 4, 5, 6, and 7 of the trigger type subfield are defined to correspond to basic, BFRP (Beamforming Report Poll), MU-BAR (multi-user-block acknowledgement request), MU-RTS (multi-user-request to send), BSRP (Buffer Status Report Poll), GCR (groupcast with retries) MU-BAR, BQRP (Bandwidth Query Report Poll), and NFRP (NDP Feedback Report Poll), respectively, and the values ​​8 to 15 are defined as reserved.

[0139] Among the common information, the trigger-dependent common info subfield may include information that is optionally included based on the trigger type.

[0140] A special user info field may be included within the trigger frame. The special user info field does not contain user-specific information, but rather contains extended common information not provided in the common information field.

[0141] The user information list contains zero or more user info fields. Figure 8 illustrates an exemplary EHT variant user info field format.

[0142] How to resolve Deafness issues in wireless LAN systems using MLO

[0143] As the number of wireless devices capable of accessing the Internet via wireless connection increases exponentially, communication methods using only currently allocated low-frequency bands are reaching their limits. For example, wireless LAN-based communication methods operate in the sub-7 GHz band, but some frequency bands are already saturated, and the use of newly allocated frequency bands (e.g., 6 GHz) is not yet widespread globally.

[0144] To solve the aforementioned frequency shortage problem, millimeter (mmWave) bands may be considered and / or applied to mobile communication methods and wireless LAN communication methods. For example, the mmWave band being considered for wireless LAN communication methods may be a 45 GHz band to a 71 GHz band, but is not limited thereto.

[0145] In addition, MLO procedures including mmWave bands can be applied in next-generation wireless LAN systems. Since MLO enables the combined use of one or more frequency bands or channels, benefits such as efficient resource utilization, reduced latency, and improved reliability can be provided. However, in the case of communication using mmWave bands, due to the characteristics of mmWave bands, it may cause a significant decrease in signal strength compared to communication using low bands.

[0146] To overcome this, a multi-antenna-based MIMO method may be applied. The use of multiple antennas can increase transmission distance and reduce interference with surrounding devices. To increase transmission distance, each device can concentrate the transmission signal in a specific direction (e.g., a specific azimuth or altitude) (e.g., beamforming). Since beamforming operation spatially restricts the detection range of the transmission signal, other surrounding devices may find it difficult to determine whether a device wishing to communicate via the mmWave band (hereinafter "mmWave communication") is communicating with another device other than itself. This problem can be collectively referred to as the Deafness problem.

[0147] In UHR and future Wi-Fi technology evolution, millimeter band (mmWave band) based operation is being considered for inclusion as a single link in the Multi-Link Operation defined in EHT.

[0148] For example, referring to FIG. 9, assume a case where STA 1 (e.g., AP / PCP or non-AP / PCP) performs mmWave communication with STA 3 (e.g., AP / PCP or non-AP / PCP) through beamforming (910). In this case, STA 2 (e.g., AP / PCP or non-AP / PCP) performing beamforming (920) cannot confirm through channel identification or the like that STA 1 is currently participating in mmWave communication. That is, STA 2 may attempt to establish a communication connection unnecessarily, which may cause unnecessary power consumption and delay. Additionally, the unnecessary attempt to establish a communication connection by STA 2 may act as interference.

[0149] Due to the aforementioned Deafness issue, other devices wishing to connect to a device performing mmWave communication (e.g., AP and / or PCP) may not receive a separate response, which may result in unnecessary power consumption and delay.

[0150] Below, we will describe a method for exchanging information regarding the availability of mmWave communication between device(s) that wish to communicate in mmWave through the transmission and reception of signals in the sub-7 GHz band (e.g., management frames, control frames, and / or the transmission and reception of control frames). This method can resolve the Deafness problem and reduce additional power and latency.

[0151] In describing the present disclosure, the STA may include an AP, a PCP (personal basic service set control point) STA, a non-AP STA and / or a non-PCP STA, and may support MLO operation. When MLO operation is applied / supported, combinations of operating frequency bands may be supported / applied, such as i) 2.4 GHz + mmWave, ii) 2.4 GHz + 5 GHz + mmWave, iii) 2.4 GHz + 6 GHz + mmWave, iv) 5 GHz + mmWave, v) 5 GHz + 6 GHz + mmWave, vi) 6 GHz + mmWave, etc.

[0152] STA(s) may provide and / or exchange information to support mmWave communication using sub-7 GHz. Information to support mmWave communication may be exchanged via sub-7 GHz management frames and / or control frames. The examples described below in this disclosure relate to procedures between an AP / PCP STA and a non-AP / PCP STA, but are not limited thereto. The examples described below in this disclosure may also be valid and applicable between non-AP / PCP STAs.

[0153] Additionally or alternatively, when multiple antennas are used, all beamforming (BF) capabilities may be concentrated in a specific direction, and / or a single BF capability may be distributed or concentrated in one or more directions.

[0154] FIG. 10 is a flowchart for explaining a method performed by a first STA according to one embodiment of the present disclosure.

[0155] In FIGS. 10 and 11, the first STA may include a non-AP STA or a non-PCP (personal basic service set control point) STA, and the second STA may include an AP or a PCP STA. However, this is merely one embodiment, and each of the first STA and the second STA may be one of a non-AP STA, an AP, a PCP STA, or a non-PCP STA. Also, the first band may be a mmWave band and the second band may be a sub-7 GHz band, but is not limited thereto. The sub-7 GHz band may include a 2.4 GHz band, a 5 GHz band, a 6 GHz band, etc.

[0156] The first STA can transmit a request frame containing first information regarding whether communication based on the first band is available to the second STA in the second band (S1010).

[0157] That is, in order to perform communication based on the first band (e.g., mmWave communication), the first STA may transmit a request frame containing first information regarding whether communication based on the first band is possible to the second STA on the second band. At this time, the request frame may include a trigger frame or other control frames.

[0158] In one example of the present disclosure, the first STA may transmit a request frame to the second STA in response to a beacon frame. For example, the beacon frame may include fourth information regarding whether communication based on the first band is supported, which may be transmitted and received through the second band. That is, the first STA can check whether the second STA supports and is currently capable of communication based on the first band through the fourth information. Additionally or alternatively, the first STA can check information regarding a future time of capability (e.g., a future time when communication based on the first band is possible) through the fourth information or separate information.

[0159] For example, based on the fourth information indicating that it supports communication based on the first band, the first STA can transmit a request frame to the second STA in response to a beacon frame. That is, if it is confirmed that the second STA supports communication based on the first band, the first STA can transmit a request frame to the second STA.

[0160] The first STA can receive a response frame for a request frame from the second STA in the second band (S1020).

[0161] Based on the second information indicating that communication based on the first band is possible being included in the response frame, the first STA can perform communication based on the first band (S1030).

[0162] Here, the response frame may include an ACK (acknowledgement) frame, but is not limited thereto. The response frame may also consist of a separate frame.

[0163] In one example of the present disclosure, a response frame may include a first field relating to whether communication based on a first band is (currently) available. The first field may include second information indicating that communication based on the first band is currently available or third information indicating that communication based on the first band is currently unavailable. Additionally or alternatively, the first field may include information regarding a future possible time (e.g., a future time when communication based on the first band is available).

[0164] For example, the size of the first field may be 1 bit. If the bit value is set to a first numeric value (e.g., 1 or 0), the bit value may correspond to / be related to second information. If the bit value is set to a second numeric value (e.g., 0 or 1), the bit value may correspond to / be related to third information.

[0165] Additionally or alternatively, the response frame may include a bitmap related to whether communication is possible for each channel of the link in the first band. That is, each bit of the bitmap may correspond to information related to whether communication is possible for each channel of the link in the first band.

[0166] Additionally or alternatively, the response frame may include information for a beamforming operation. The first STA may perform a beamforming procedure (e.g., beamforming configuration and / or frame / data transmission / reception procedure based on beamforming, etc.) based on the information for the beamforming operation. As an example, the information for the beamforming operation may include information about at least one beam sector that the second STA can receive / use. Accordingly, the first STA may perform a beamforming operation for the at least one beam sector.

[0167] Additionally or alternatively, the response frame may include information for allocating a time interval during which communication is possible in the first band. For example, if the response frame includes second information, the response frame may include (allocation) information regarding a time interval (e.g., SP, etc.) during which communication based on the first band can be performed. That is, the first STA can perform communication based on the first band together with the second STA within the time interval allocated according to the response frame.

[0168] The method described in the example of FIG. 10 can 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 can transmit a request frame containing first information regarding whether communication based on the first band is possible to the second STA in the second band through one or more transceivers (106). One or more processors (102) can receive a response frame for the request frame from the second STA in the second band through one or more transceivers (106). Based on the second information indicating that communication based on the first band is possible being included in the response frame, one or more processors (102) can perform communication based on the first band.

[0169] Furthermore, one or more memories (104) of the first device (100) may store instructions for performing the method described in the example of FIG. 10 or the examples described below when executed by one or more processors (102).

[0170] FIG. 11 is a flowchart illustrating a method performed by a second STA according to one embodiment of the present disclosure.

[0171] The second STA can receive a request frame from the first STA in the second band containing first information regarding whether communication based on the first band is available (S1110).

[0172] For example, the second STA may first transmit a beacon frame containing fourth information regarding whether (the second STA) supports communication based on the first band to the first STA. The second STA may receive a request frame from the first STA in response to the beacon frame.

[0173] The second STA can transmit a response frame for a request frame to the first STA in the second band (S1120).

[0174] Specifically, the second STA may transmit a response frame to the first STA containing information regarding whether communication based on the first band is currently possible. Since the configuration of the response frame has been explained with reference to FIG. 10, a redundant explanation will be omitted.

[0175] Based on the second information indicating that communication based on the first band is possible being included in the response frame, the second STA can perform communication based on the first band (S1130).

[0176] For example, if second information indicating that communication is currently possible in the first band is transmitted to the first STA, the second STA can perform a communication establishment procedure for the first band with the first STA. And, the second STA can communicate with the first STA in the first band.

[0177] The method described in the example of FIG. 11 can 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 receive a request frame containing first information regarding whether communication based on the first band is possible from the first STA in the second band through one or more transceivers (206). One or more processors (202) may transmit a response frame for the request frame to the first STA in the second band through one or more transceivers (206). Based on the second information indicating that communication based on the first band is possible being included in the response frame, one or more processors (202) may perform communication based on the first band.

[0178] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 11 or the examples described below when executed by one or more processors (202).

[0179] Below, we will specifically explain a method for exchanging information regarding the possibility of mmWave communication between device(s) that want mmWave communication through signal transmission and reception in the sub-7 GHz band.

[0180] Example 1

[0181] Example 1 relates to a procedure for exchanging information on whether communication using the mmWave band (hereinafter, "mmWave communication") is possible.

[0182] As an example of the present disclosure, an AP / PCP STA that supports mmWave communication based on MLO can transmit / notify information regarding whether current mmWave communication is supported through the transmission of a sub-7 GHz beacon frame.

[0183] Additionally or alternatively, the AP / PCP STA may transmit information regarding the current support for mmWave communication via a trigger frame to the STA(s) among the currently associated non-AP / PCP STA(s) that support mmWave communication. Here, the trigger frame may include not only the trigger frame described with reference to FIG. 8 but also a trigger frame with a trigger frame variant related to mmWave communication set. Additionally, a separate trigger frame related to mmWave communication may be defined and used.

[0184] For example, information regarding whether mmWave communication is currently supported may be set to 1 bit. For example, if the bit value is set to 1 (or 0), it may mean that mmWave communication is supported (e.g., "available"). For another example, if the bit value is set to 0 (or 1), it may mean that mmWave communication is not supported (e.g., "unavailable"). However, this is merely one embodiment, and the size and configuration of the information regarding whether mmWave communication is currently supported may vary.

[0185] As an example of the present disclosure, information regarding the current support for mmWave communication may be set / transmitted / applied for each channel of a mmWave link. In this case, the information regarding the current support for mmWave communication may be provided in the form of a bitmap.

[0186] Additionally or alternatively, information regarding cases where mmWave communication is not supported (e.g., information about the "unavailable" status of mmWave communication) may be additionally transmitted, received, or exchanged between STAs. For example, information regarding cases where mmWave communication is not supported may include information about the time when mmWave communication is unavailable (e.g., the start and end times when mmWave communication is unavailable). For example, a STA that receives information regarding cases where mmWave communication is not supported (e.g., a non-AP / PCP STA) may determine whether mmWave communication is possible through said information.

[0187] As an example of the present disclosure, information regarding cases where mmWave communication is not supported may be transmitted and received periodically. As an example, information regarding cases where mmWave communication is not supported may include information regarding periodic service periods (SPs) of currently ongoing mmWave communication (e.g., information regarding SP timing or duration).

[0188] As an example of the present disclosure, information regarding cases where mmWave communication is not supported may be information regarding a specific direction. For example, information indicating that mmWave communication is not supported may be transmitted in relation to an azimuth of 0-60 degrees, but information indicating that mmWave communication is supported may be transmitted in relation to an azimuth of 180-270 degrees. That is, information regarding whether mmWave communication is supported for each unit direction (e.g., azimuth or / and altitude) may be transmitted and received.

[0189] Information regarding whether the above-described current mmWave communication is supported and / or information regarding cases where mmWave communication is not supported may be conveyed through a separate field, subfield, or element. A non-AP / PCP STA that receives information regarding whether the current mmWave communication is supported and / or information regarding cases where mmWave communication is not supported may hold an attempt at mmWave communication in accordance with the received information.

[0190] In one example of the present disclosure, a STA (e.g., a non-AP / PCP STA) may determine whether mmWave communication (or mmWave band usage) is possible upon receiving a frame (e.g., a beacon frame, a trigger frame, etc.) containing the information described above. The non-AP / PCP STA may transmit a request frame to the AP / PCP STA in the sub-7 GHz band. The request frame may be for a request for mmWave communication. For example, the request frame may include information regarding a CBAP (contention-based access protocol) and / or SP allocation available through competition with other non-AP / PCP STAs.

[0191] An AP / PCP STA may assign a CBAP and / or SP to a non-AP / PCP STA in response to a request frame to support mmWave communication of the non-AP / PCP STA. For example, a response frame transmitted by an AP / PCP STA may include CBAP and / or SP assignment information for mmWave communication of the non-AP / PCP STA.

[0192] For example, CBAP and / or SP allocation information may include communication time information in the mmWave band, etc. For example, communication time information in the mmWave band may be allocated based on time information in the sub-7 GHz band or time information in the mmWave band. Additionally, communication time in the mmWave band may be allocated / determined by a TSF value. Additionally, or alternatively, the response frame may be transmitted as an "ACK" frame for the request frame.

[0193] The format of each of the above-described request frame and / or response frame may be a frame format of a basic wireless LAN system or a new frame format. For example, if the information regarding cases where mmWave communication is not supported is long-term information, the above-described request frame and response frame may be a combined request frame and a combined response frame, respectively.

[0194] After receiving a response frame and after a set time, the AP / PCP STA and the non-AP / PCP STA may perform a connection operation using the mmWave band. Here, the set time may be SIFS or PIFS, but is not limited thereto and may be a newly defined time. The progress of the connection operation may include an ICR (initial control response) and an ICF (initial control frame) exchange operation.

[0195] For example, a non-AP / PCP STA (or, AP / PCP STA) may transmit an ICF to an AP / PCP STA (or, non-AP / PCP STA) for mmWave band connection operations. The AP / PCP STA (or, non-AP / PCP STA) may transmit a response (e.g., ICR) to the ICF to the non-AP / PCP STA (or, AP / PCP STA). In this case, the ICF and ICR exchange may be performed based on the (minimum) configuration (e.g., minimum supported bandwidth, number of MCS and / or spatial streams, etc.) of the receiving end (e.g., AP / PCP STA or / and non-AP / PCP STA). That is, the AP / PCP STA or / and non-AP / PCP STA may perform an ICF / ICR exchange operation after performing the operation of exchanging the configuration information described above.

[0196] Additionally or alternatively, BF-related procedures may be performed while performing mmWave band connection operations. BF-related procedures may include the exchange of sector-level information or fine antenna weight vector information.

[0197] FIG. 12 is a diagram illustrating a procedure for exchanging information on whether communication support using mmWave is possible, according to one embodiment of the present disclosure.

[0198] As an example of the present disclosure, an AP / PCP STA may transmit a beacon frame to a non-AP / PCP STA in the sub-7 GHz band. In this case, the beacon frame may include information regarding whether mmWave communication is currently supported and / or information regarding cases where mmWave communication is not supported.

[0199] For example, assume a case where a beacon frame contains information (e.g., unavailable information) indicating that mmWave communication is not supported (at a specific time interval or / and a specific azimuth / altitude). A non-AP / PCP STA can determine that mmWave communication is not possible (at a specific time interval or / and a specific azimuth / altitude) based on the above information.

[0200] For example, assume a case where information indicating that mmWave communication is supported (at a specific time interval or / and a specific azimuth / altitude) is transmitted to a non-AP / PCP STA via a beacon frame. Accordingly, the non-AP / PCP STA can transmit a request frame for mmWave communication (or connection) in the sub-7 GHz band to the AP / PCP STA. The AP / PCP STA can transmit an acknowledgment frame (e.g., an ACK frame) for the request frame in the sub-7 GHz band. Subsequently, the non-AP / PCP STA and the AP / PCP STA can perform a connection establishment operation with each other.

[0201] Example 2

[0202] Example 2 relates to an additional or alternative method for exchanging information on whether support for communication using the mmWave band (hereinafter, "mmWave communication") is possible.

[0203] A non-AP / PCP STA that wishes to communicate with an AP / PCP STA or another non-AP / PCP STA in mmWave may request information in advance regarding whether mmWave communication is possible over the sub-7 GHz band (e.g., information on availability). For example, the non-AP / PCP STA may send a request frame containing information on whether communication using the mmWave band is possible to the AP / PCP STA over the sub-7 GHz band.

[0204] For example, information regarding whether communication using the mmWave band is possible may be set in a specific field, subfield, or element of the request frame. The request frame may be a trigger frame, and the trigger frame may be the trigger frame or trigger variant illustrated in FIG. 8 or a newly defined trigger frame. However, this is merely one embodiment, and the request frame may be implemented as a frame other than a trigger frame.

[0205] An AP / PCP STA or another non-AP / PCP STA can inform the non-AP / PCP STA whether mmWave communication is currently available through a response frame to a request frame. For example, the information regarding whether mmWave communication is currently available included in the response frame can be set to 1 bit.

[0206] For example, if the bit value is set to 1 (or 0), it may mean that mmWave communication is currently possible. For another example, if the bit value is set to 0 (or 1), it may mean that mmWave communication is not possible. However, this is merely one example, and the size and configuration of the information regarding whether mmWave communication is currently possible may vary.

[0207] For example, information regarding the current availability of mmWave communication for each channel of a mmWave link can be transmitted and received. In this case, the information regarding the availability of mmWave communication for each channel of a mmWave link can be provided in the form of a bitmap.

[0208] Additionally or alternatively, information regarding the current availability of mmWave communication may additionally provide / transmit information regarding the "unavailable" of mmWave communication. For example, information regarding the "unavailable" of mmWave communication may include information regarding the time when mmWave communication is unavailable (e.g., the start and end times when mmWave communication is unavailable). For example, a STA that receives information regarding cases where mmWave communication is not supported (e.g., a non-AP / PCP STA) can determine whether mmWave communication is possible through said information.

[0209] As an example of the present disclosure, information regarding the "unavailable" of mmWave communication may be transmitted and received periodically. As an example, the information regarding the "unavailable" of mmWave communication may include information regarding periodic SPs of currently ongoing mmWave communication (e.g., information regarding SP timing or intervals).

[0210] In one example of the present disclosure, information regarding the "unavailable" of mmWave communication may be information regarding a specific direction. For example, information indicating that mmWave communication is not possible with respect to an azimuth of 0-60 degrees may be transmitted, but information indicating that mmWave communication is possible with respect to an azimuth of 180-270 degrees may be transmitted. That is, information regarding whether mmWave communication is currently possible for each unit direction (e.g., azimuth or / and altitude) may be transmitted and received.

[0211] Additionally, information for providing BF efficiency may be transmitted and received along with information regarding the availability of current mmWave communication. For example, information for providing BF efficiency may include information regarding the receivable sector(s) of an AP / PCP STA or another non-AP / PCP STA. Based on the information for providing BF efficiency, the STA (e.g., non-AP / PCP STA) may perform BF on some sector(s) instead of BF on all available sector(s), thereby reducing power consumption and latency.

[0212] In one example of the present disclosure, a non-AP / PCP STA may transmit a request frame to an AP / PCP STA in the sub-7 GHz band. The request frame may be for a request for mmWave communication. For example, the request frame may include information about a CBAP (contention-based access protocol) and / or SP allocation available through competition with other non-AP / PCP STAs.

[0213] An AP / PCP STA may assign a CBAP and / or SP to a non-AP / PCP STA in response to a request frame to support mmWave communication of the non-AP / PCP STA. For example, a response frame transmitted by an AP / PCP STA may include CBAP and / or SP assignment information for mmWave communication of the non-AP / PCP STA.

[0214] For example, CBAP and / or SP allocation information may include communication time information in the mmWave band, etc. For example, communication time information in the mmWave band may be allocated based on time information in the sub-7 GHz band or time information in the mmWave band. Additionally, communication time in the mmWave band may be allocated / determined by a TSF value. Additionally, or alternatively, the response frame may be transmitted as an "ACK" frame for the request frame.

[0215] The format of each of the above-described request frame and / or response frame may be a frame format of a basic wireless LAN system or a new frame format. For example, if the information regarding cases where mmWave communication is not supported is long-term information, the above-described request frame and response frame may be a combined request frame and a combined response frame, respectively.

[0216] After receiving a response frame (e.g., a response frame containing information indicating that mmWave communication is possible), the AP / PCP STA and the non-AP / PCP STA may perform a connection operation using the mmWave band after a certain period of time. Here, the certain period of time may be SIFS or PIFS, but is not limited thereto and may be a newly defined period of time. The progress of the connection operation may include an ICR (initial control response) and an ICF (initial control frame) exchange operation.

[0217] For example, a non-AP / PCP STA (or, AP / PCP STA) may transmit an ICF to an AP / PCP STA (or, non-AP / PCP STA) for mmWave band connection operations. The AP / PCP STA (or, non-AP / PCP STA) may transmit a response (e.g., ICR) to the ICF to the non-AP / PCP STA (or, AP / PCP STA). In this case, the ICF and ICR exchange may be performed based on the (minimum) configuration (e.g., minimum supported bandwidth, number of MCS and / or spatial streams, etc.) of the receiving end (e.g., AP / PCP STA or / and non-AP / PCP STA). That is, the AP / PCP STA or / and non-AP / PCP STA may perform an ICF / ICR exchange operation after performing the operation of exchanging the configuration information described above.

[0218] Additionally or alternatively, BF-related procedures may be performed while performing mmWave band connection operations. BF-related procedures may include the exchange of sector-level information or fine antenna weight vector information.

[0219] FIG. 13 is a diagram illustrating a procedure for exchanging information on whether communication support using mmWave is possible, according to one embodiment of the present disclosure.

[0220] A non-AP / PCP STA can send a request frame for a mmWave connection in the sub-7 GHz band to an AP / PCP STA. The AP / PCP STA illustrated in FIG. 13 may be replaced by another non-AP / PCP STA. In this case, if the non-AP / PCP STA receives a response frame from the AP / PCP STA containing information indicating that a mmWave connection is currently unavailable, the non-AP / PCP STA may resend the request frame after a certain period of time.

[0221] For example, if a non-AP / PCP STA receives a response frame (e.g., an ACK frame, etc.) containing information indicating that a mmWave connection is currently available from an AP / PCP STA (in the sub-7 GHz band), the non-AP / PCP STA can perform a connection establishment operation for mmWave communication.

[0222] By the various embodiments described above, power consumption and delay in the high-frequency band caused by the occurrence of Deafness can be reduced, and accordingly, resource usage efficiency can be increased.

[0223] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct 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 obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0224] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0225] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may 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 may 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 may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0226] Although the method proposed in this disclosure has been described with an example applied to an IEEE 802.11-based system, it can be applied to various wireless LANs or wireless communication systems in addition to IEEE 802.11-based systems.

Claims

1. A step of transmitting a request frame containing first information regarding whether communication based on the first band is available to the second STA by the first station (STA) in the second band; A step of receiving a response frame for the above request frame from the second STA by the first STA in the above second band; and A method comprising the step of performing communication based on the first band by the first STA, based on second information indicating that communication based on the first band is possible being included in the response frame.

2. In Paragraph 1, A method in which the first band is a mmWave band and the second band is a sub-7 GHz band.

3. In Paragraph 1, The above response frame includes a first field related to whether communication based on the first band is possible, and A method in which the first field comprises third information indicating that communication based on the second information or the first band is unavailable.

4. In Paragraph 1, A method in which the above response frame includes a bitmap related to whether communication is possible for each channel of the link of the first band.

5. In Paragraph 1, The above response frame includes information for beamforming operation, and A method in which information for the beamforming operation includes information for at least one beam sector available to the second STA.

6. In Paragraph 5, A method in which a beamforming operation for at least one beam sector is performed by the first STA.

7. In Paragraph 1, The above response frame includes information for allocating a time interval during which communication is possible in the first band, and A method in which communication based on the first band within the above time interval is performed by the first STA.

8. In Paragraph 1, A method in which a beacon frame containing fourth information regarding whether communication based on the first band is supported is received from the second STA on the second band.

9. In Paragraph 8, A method in which the request frame is transmitted from the first STA to the second STA in correspondence with the beacon frame, based on the fact that the fourth information indicates that communication based on the first band is supported.

10. In Paragraph 1, The above request frame includes a trigger frame or other control frame, and The above response frame is a method including an ACK (acknowledgement) frame.

11. In Paragraph 1, The above first STA includes a non-access point (AP) STA or a non-PCP (personal basic service set control point) STA, and The above second STA is a method comprising an AP or PCP STA.

12. In the first station (STA), the first STA is: One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Transmitting a request frame containing first information regarding whether communication based on the first band is available to the second STA in the second band through the one or more transceivers; Receiving a response frame for the above request frame from the second STA in the above second band through the one or more transceivers; and A first STA configured to perform communication based on the first band, based on second information indicating that communication based on the first band is possible being included in the response frame.

13. A step of receiving a request frame containing first information regarding whether communication based on the first band is available from the first STA by the second station (STA) in the second band; A step of transmitting a response frame for the above request frame to the first STA by the second STA in the above second band; and A method comprising the step of performing communication based on the first band by the second STA, based on second information indicating that communication based on the first band is possible being included in the response frame.

14. In the second station (STA), the second STA is: One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Receiving a request frame containing first information regarding whether communication based on the first band is available from the first STA in the second band through the one or more transceivers; Transmitting a response frame for the above request frame from the above second band to the above first STA through the one or more transceivers; and A second STA configured to perform communication based on the first band, based on the inclusion of second information indicating that communication based on the first band is possible in the response frame.

15. A processing device configured to control a station (STA) in a wireless local area network (WLAN) system, wherein the processing device: One or more processors; and A processing device comprising one or more computer memories that are operably connected to one or more processors and store instructions for performing a method according to any one of claims 1 to 11 based on execution by one or more processors.

16. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium in which one or more of the above 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 11.

Images