Frame for relay operation in wireless LAN system

Abstract

The technical features of the present disclosure may relate to a method or apparatus performed in a wireless local area network (WLAN) system. For example, the method of the present disclosure comprises a step in which a non-access point (non-AP) station (STA) receives a relay beacon frame from a relay STA. For example, the relay beacon frame comprises a medium access control (MAC) header including a frame control field, and a frame body. For example, the frame control field comprises at least one of a type field and a subtype field, which have a pre-set value for identifying the relay beacon frame. For example, the frame body comprises information about a relay beacon interval for the relay beacon frame. For example, the relay beacon interval is set to be shorter than a beacon interval of a beacon frame transmitted from an access point (AP).

Description

Frame for relay operation in wireless LAN systems

[0001] This specification relates to a wireless LAN system, and more specifically, to a method and device related to a frame for relay operation of a wireless LAN system.

[0002] Wireless local area networks (WLANs) have been improved in various ways. For example, the Extreme High Throughput (EHT) standard can utilize newly proposed increased bandwidth, an improved PHY layer protocol data unit (PPDU) structure, improved sequences, and Hybrid Automatic Repeat Request (HARQ) techniques. The EHT standard can also be referred to as the IEEE 802.11be standard.

[0003] The EHT specification supports high throughput and high data rates, which may include wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.

[0004] In the EHT specification, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used to achieve high throughput. Preamble puncturing and multiple RU transmissions can also be used to efficiently utilize bandwidth.

[0005] WLAN systems can be further improved through the Ultra High Reliability (UHR) standard. The UHR system, also known as the IEEE 802.11bn standard, aims to support ultra-high reliability when transmitting signals to STAs. To achieve this, various technologies are being considered for UHR systems, including high throughput, low latency, and extended range support.

[0006] This specification relates to relay operations / procedures / transmission in a wireless LAN system. The technical features of this specification propose a relay station in a next-generation wireless LAN system to ensure reliable transmission and extend coverage / range for various IoT devices, including outdoor use.

[0007] This specification proposes a new frame related to relay operation. The frame proposed in this specification may be a management frame. For example, the management frame may be a beacon frame, or a beacon frame in a newly proposed format for relay operation.

[0008] The new frame proposed in this specification is preferably smaller than the existing beacon frame. Furthermore, the beacon frame is preferably transmitted at a shorter interval than the existing beacon frame. This reduces the overhead associated with relay operation and improves the efficiency of relay operation for STAs located outside the AP's coverage area.

[0009] This specification proposes various technical features. These technical features can be applied to various types of STAs / devices.

[0010] For example, the technical features of the present specification may relate to a method or device performed in a Wireless Local Area Network (WLAN) system. For example, the method of the present specification includes a step of receiving a relay beacon frame from a relay STA by a Non-AP (Non Access Point) STA. For example, the relay beacon frame includes a Medium Access Control (MAC) header including a Frame Control field, and a frame body. For example, the Frame Control field includes a Type field having a preset value for identifying the relay beacon frame. For example, the frame body includes information regarding a relay beacon interval for the relay beacon frame. For example, the relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access Point). For example, the method includes a step of acquiring information included in the relay beacon frame.

[0011] The technical features described in this specification can bring about various advantageous effects. For example, when a relay STA receives a specific frame (e.g., a beacon frame) from an AP and then transmits the information contained in the beacon frame to an end-STA, the new frame / signal / beacon proposed in this specification can accurately transmit the information required for the relay operation. This can achieve the technical effect of increasing the efficiency of the relay operation. In addition, when the size of the specific frame (e.g., a beacon frame) transmitted by the relay STA is smaller than that of a conventional beacon frame, the overhead associated with transmitting the frame can be reduced. The overhead required for the relay operation can be reduced through the new frame / signal / beacon proposed in this specification. In addition, the end-STA can be located outside the coverage of the AP, in which case the technical effect of performing accurate relay operation can be achieved by accurately transmitting information regarding the relay operation through the new frame / signal / beacon proposed in this specification.

[0012] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0013] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0014] Figure 3 is a diagram illustrating a general link setup process.

[0015] Figure 4 illustrates one embodiment of a multi-link (ML).

[0016] Figure 5 illustrates a PPDU transmitted / received by an STA of this specification.

[0017] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.

[0018] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0019] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.

[0020] Figure 9 shows the operation according to UL-MU.

[0021] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0022] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0023] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0024] Figure 13 shows an example of a header of a MAC frame.

[0025] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0026] Figure 15 describes the characteristics of a Relay STA controlled by an AP.

[0027] Figure 16 is a drawing for explaining the concept of range extension related to an example of this specification.

[0028] Figure 17 shows an example of the frame format of a relay beacon frame of this specification.

[0029] Figure 18 shows an example of transmission and reception of a relay beacon frame and a normal beacon frame.

[0030] Figure 19 is a procedure flow chart based on an example of this specification.

[0031] Figure 20 is a procedure flow chart based on an example of this specification.

[0032] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0033] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0034] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0035] In addition, parentheses used in this specification may mean “for example”. Specifically, when it is indicated as “control information (UHR-Signal field)”, the “UHR-Signal field” may be proposed as an example of “control information”. In other words, the “control information” in this specification is not limited to the “UHR-Signal field”, and the “UHR-Signal field” may be proposed as an example of “control information”. In addition, even when it is indicated as “control information (UHR-Signal field)”, the “UHR-Signal field” may be proposed as an example of “control information”.

[0036] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”

[0037] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”

[0038] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0039] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to wireless local area network (WLAN) systems. For example, the present specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification can be applied to the Ultra High Reliability (UHR) standard or the next-generation wireless LAN standard that enhances IEEE 802.11bn. In addition, the examples of this specification can be applied to mobile communication systems. For example, the examples of this specification can be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on the 3rd Generation Partnership Project (3GPP) standard.

[0040] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0041] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0042] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present specification may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present specification may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

[0043] For example, STA (110, 120) may perform the role of an AP (access point) or a non-AP role. That is, STA (110, 120) of the present specification may perform the functions of an AP and / or a non-AP. In the present specification, AP may also be indicated as an AP STA.

[0044] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (Self-Driving, Autonomous-Driving).

[0045] In this specification, STA (110, 120) may include a medium access control (MAC) and a physical layer interface for a wireless medium that follow the provisions of the IEEE 802.11 standard.

[0046] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.

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

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

[0049] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (112) of the AP can store a signal received through the transceiver (113) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

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

[0051] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (122) of the Non-AP STA can store a signal received through the transceiver (123) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

[0052] For example, in the specification below, the operation of a device indicated as AP may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is an AP, the operation of the device indicated as AP may be controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). In addition, control information related to the operation of the AP or a transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110). In addition, when the second STA (110) is an AP, the operation of the device indicated as an AP is controlled by the processor (121) of the second STA (120), and a related signal can be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signal of the AP can be stored in the memory (122) of the second STA (110).

[0053] For example, in the specification below, the operation of a device indicated as a non-AP (or User-STA) may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device indicated as a non-AP may be controlled by the processor (121) of the second STA (120), and a related signal may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of a device indicated as a non-AP is controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110).

[0054] In the following specification, devices called (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. In addition, in the example below, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include 1) an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation for determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.

[0055] The device / STA of the sub-drawing (a) of the above-described Fig. 1 can be modified as in the sub-drawing (b) of Fig. 1. Hereinafter, the STA (110, 120) of the present specification will be described based on the sub-drawing (b) of Fig. 1.

[0056] For example, the transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the transceiver illustrated in sub-drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) illustrated in sub-drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (a) of FIG. 1 described above.

[0057] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, Base Station, Node-B, Access Point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

[0058] For example, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal being received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1 being acquired by a processor (111, 121) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 being acquired by a processing chip (114, 124) illustrated in sub-drawing (b) of FIG.

[0059] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.

[0060] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or an enhanced processor thereof.

[0061] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.

[0062] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0063] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0064] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP) 225 and a station (STA1, 200-1), that have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).

[0065] A BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.

[0066] A distributed system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS) 240. An ESS (240) can be used as a term to indicate a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) can have the same SSID (service set identification).

[0067] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0068] In a BSS such as the upper part of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0069] The bottom of Figure 2 is a conceptual diagram showing IBSS.

[0070] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and access to the distributed system is not permitted, forming a self-contained network.

[0071] Figure 3 is a diagram illustrating a general link setup process.

[0072] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning by the STA. That is, for the STA to access the network, it must find a network it can join. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0073] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist in the vicinity while moving between channels and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits the beacon frame, so the AP becomes the responder. In an IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not constant. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0074] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

[0075] An STA that discovers a network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0076] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group.

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

[0078] A successfully authenticated STA may perform an association process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and the AP transmits an association response frame to the STA in response. For example, the association request frame may include information related to various capabilities, such as a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may contain information related to various capabilities, status codes, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise Indicator (RSNI), mobility domains, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS maps, etc.

[0079] In step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0080] Figure 4 illustrates one embodiment of a multi-link (ML).

[0081] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0082] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the second link may be configured in different bands.

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

[0084] In the example of FIG. 4, AP1 may initiate a multi-link setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In the example of FIG. 4, non-AP STA1 may transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the AP illustrated in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the STA (i.e., user-STA or non-AP STA) illustrated in FIG. 1 and / or FIG. 2.

[0085] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.

[0086] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0087] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.

[0088] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.

[0089] In FIG. 5, L-STF or UHR-LTF may be called a preamble or physical preamble, and may be generated / transmitted / received / acquired / decoded in the physical layer (included in the transmitting / receiving STA).

[0090] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.

[0091] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.

[0092] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0093] The L-SIG field of FIG. 5 may include, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4 bit Rate field, a 1 bit Reserved bit, a 12 bit Length field, a 1 bit Parity bit, and a 6 bit Tail bit. For example, the 12 bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12 bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU or UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

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

[0095] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.

[0096] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be called by various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, the common control field, and the common control signal.

[0097] A U-SIG can contain N bits of information and can include information for identifying the type of EHT PPDU. For example, a U-SIG can be formed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., an OFDM symbol) for a U-SIG can have a duration of 4 microseconds. Each symbol of a U-SIG can be used to transmit 26 bits of information. For example, each symbol of a U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0098] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52 coded bits, and perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols allocated to each U-SIG symbol. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.

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

[0100] The A bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

[0101] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

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

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

[0104] For example, the version-independent bits of U-SIG may contain information about the length of the TXOP and information about the BSS color ID.

[0105] For example, if a UHR PPDU is classified into various types (e.g., a type related to SU transmission (performed based on UL or DL), a type related to DL transmission, a type related to NDP transmission, a type related to DL non-MU-MIMO, a type related to DL MU-MIMO, a type related to Multi-AP operation, a type related to CBF (Coordinated beamforming), SR (Spatial Reuse), a type related to C-OFDMA (Coordinated OFDMA), a type related to C-TDMA (Coordinated TDMA)), information about the type of the EHT PPDU (e.g., 2-bit or 3-bit information) can be included in the version-dependent bits of the U-SIG.

[0106] For example, U-SIG may include 1) a bandwidth field including information about bandwidth, 2) a field including information about a Modulation and Coding Scheme (MCS) technique applied to UHR-SIG, 3) an indication field including information about whether a dual subcarrier modulation (DCM) technique is applied to UHR-SIG, 4) a field including information about the number of symbols used for UHR-SIG, 5) a field including information about whether UHR-SIG is generated over the entire band, 6) a field including information about the type of UHR-LTF / STF, and 7) a field indicating the length of UHR-LTF and the CP length.

[0107] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0108] For example, the pattern of preamble puncturing can be preset. For example, when the first puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing can be applied only to one of the two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, a primary 40 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band) may be present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

[0109] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0110] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).

[0111] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).

[0112] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth can contain different U-SIGs.

[0113] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted via at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0114] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

[0115] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on RUs (resource units) defined by multiple subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.

[0116] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.

[0117] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.

[0118] Meanwhile, the RU arrangement of FIG. 6 is utilized not only in a situation for multiple users (MUs) but also in a situation for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of FIG. 4, in which case three DC tones can be inserted.

[0119] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.

[0120] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0121] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0122] Additionally, as illustrated, 484 RUs may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.

[0123] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.

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

[0125] TB PPDUs (941, 942) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (930). The ACK frame (950) for the TB PPDU can be implemented in various forms. For example, the ACK frame (950) for the TB PPDU can be implemented in the form of a BA (block ACK).

[0126] In FIG. 9, transmission(s) of a Trigger Frame (930), TB PPDU (941, 942) and / or ACK frame (950) can be performed within a TXOP (925).

[0127] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0128] The 2.4 GHz band may be referred to by other names, such as the first band (band). Furthermore, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency between 2.4 and 2.5 GHz) are used / supported / defined.

[0129] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407 + 0.005*N) GHz. The channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of the channel indices and center frequencies may change.

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

[0131] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0132] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 are subject to change.

[0133] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency ranges called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.

[0134] Within the 5 GHz band, multiple channels can be configured, and the bandwidth of each channel can be variously configured, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel through a 160 MHz frequency domain.

[0135] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0136] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.

[0137] For example, the 20 MHz channel of FIG. 12 can be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 can have an index of 1 (or channel index, channel number, etc.), and a center frequency of 5.945 GHz can be assigned. That is, the center frequency of the indexed channel N can be determined as (5.940 + 0.005*N) GHz.

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

[0139] Below, the structure and types / subtypes of MAC frames are described.

[0140] Fig. 13 illustrates an example of a header of a MAC frame. As illustrated, the MAC frame may include a frame control field / information of 2 octets in length, a duration field / information of 2 octets in length, a RA (Receiver Address) field / information of 6 octets in length, and a TA (Transmitter Address) field / information of 6 octets in length. As illustrated in Fig. 13, the four fields may be consecutive to each other. The MAC header of Fig. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.

[0141] The MAC header illustrated in Fig. 13 may be positioned at the very front of a MAC frame. That is, the MAC frame may include a MAC header as illustrated in Fig. 13 and MAC body fields / information subsequent to the MAC header. The MAC frame including the MAC header of Fig. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) illustrated in Fig. 5.

[0142] The MAC frames included in the data field of the PPDU of this specification can be classified into various types. For example, the MAC frames of this specification can be classified into control frames, management frames, and data frames.

[0143] For example, the management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLAN. For the management frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 00. In addition, the values ​​of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).

[0144] For example, the control frame includes Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLAN. For the control frame, the value of the type field (B3 and B2) in FIG. 13 is set to 01. Also, the values ​​of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger (0010), Beamforming Report Poll (0100), NDP Announcement (0101), Control Frame Extension (0110), Control Wrapper (0111), BlockAckReq (1000), BlockAck (1001), PS-Poll (1010), RTS (1011), CTS (1100), Ack (1101), CF-End (1110).

[0145] For example, the data frame includes (QoS) Data, (QoS) Null, etc. defined in conventional WLAN. For the management frame, the value of the type field (B3 and B2) of Fig. 13 is set to 10.

[0146] The MAC frame / signal used in this specification can be identified through the type field / information and subtype field / information described above. For example, the “trigger frame” in this specification can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, B4 bits in the frame control field are also set to 0010. Various MAC frames described in this specification are inserted / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).

[0147] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0148] The devices (e.g., AP STA, non-AP STA) illustrated in FIGS. 1 to 4 may be modified as illustrated in FIG. 14. The transceiver (630) of FIG. 14 may be identical to the transceivers (113, 123) of FIG. 1. The transceiver (630) of FIG. 14 may include a receiver and a transmitter.

[0149] The processor (610) of FIG. 14 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 14 may be identical to the processing chip (114, 124) of FIG. 1.

[0150] The memory (150) of FIG. 14 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 14 may be a separate external memory different from the memory (112, 122) of FIG. 1.

[0151] Referring to FIG. 14, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0152] Referring to FIG. 14, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).

[0153] Various technical features of the present specification may operate based on a relay station. A relay STA (station) refers to a device that receives a PPDU (e.g., the above-described HT / VHT / HE / EHT / UHR-PPDU) from a first STA (e.g., an AP STA) and relays the received PPDU to a second STA (e.g., a non-AP STA). The relay function / operation / procedure / transmission performed by the relay STA in the present specification may be implemented in various ways. For example, the relay STA may receive a first PPDU from the first STA and decode a portion of the received first PPDU. For example, the relay STA can decode the PHY preamble (e.g., L-SIG, U-SIG, EHT-SIG, etc.) included in the first PPDU, and decode a part of the MAC frame (e.g., MAC header) included in the data field of the first PPDU. Through this, the relay STA can obtain the frame body of the MAC frame of the first PPDU, and can relay the frame body of the MAC frame to the second STA without performing additional decoding on the frame body of the obtained MAC frame. That is, the relay STA can encode / generate / configure the second PPDU based on the body of the MAC frame, and transmit the second PPDU to the second STA. As a result, the first PPDU and the second PPDU can include the same payload or MAC frame body. For example, the PHY preamble and / or MAC header of the first PPDU received by the Relay STA may be the same as or different from the PHY preamble and / or MAC header of the second PPDU transmitted by the Relay STA.For example, the Relay STA may not decode the remaining MAC frame (i.e., frame body) except for the MAC header of the first PPDU, or may decode only a part of it.

[0154] In this specification, the Relay STA can be implemented in various ways.

[0155] First, the Relay STA of the present specification can be implemented in a manner that includes a Relay-STA and a Relay-AP. That is, the Relay STA can include a Relay STA that communicates with a Root AP, and at the same time, a Relay AP that communicates with a non-AP. In this case, an upper BSS can be defined between the Root AP and the Relay STA, and a lower BSS can be defined between the Relay AP and the non-AP. A relay function can be implemented between the Relay STA and the Relay AP within the Relay STA.

[0156] Second, the Relay STA of the present specification may be a terminal / device that operates as a non-AP STA (i.e., a user STA). That is, the Relay STA of the present specification may belong to a BSS defined / configured by an AP STA without defining / configuring a new lower BSS by itself. The AP STA may assign an ID (e.g., AID) to the Relay STA in the same way as a conventional non-AP STA (i.e., a user STA). That is, the Relay STA may be identified like a typical non-AP STA (i.e., a user STA) and may additionally support the above-described relay function / operation / procedure / transmission. That is, the Relay STA may receive a first DL PPDU from an AP-STA, obtain a MAC frame body of the first DL PPDU, and relay a second DL PPDU including the obtained MAC frame body to a surrounding non-AP STA. Additionally, the relay STA can receive a first UL PPDU from a surrounding non-AP STA, obtain a MAC frame body of the first UL PPDU, and relay a second UL PPDU including the obtained MAC frame body to the AP STA.

[0157] Third, the Relay STA of the present specification can be implemented based on multiple links. For example, the relay function / operation / procedure described above can be performed based on multiple links described in FIG. 4 of the present specification. That is, a specific non-AP MLD can operate as a Relay STA, and in this case, the first PPDU can be received through the first link included in the non-AP MLD. The Relay STA can relay the first PPDU received through the first link to another STA through the second link. For example, the first link can operate as a DL link (or UL link), and the second link can operate as a UL link (or DL ​​link).

[0158] As described above, this specification is based on the IEEE 802.11bn, or UHR (ultra-high reliability) standard, which improves upon IEEE 802.11be. The specific details are as follows.

[0159] Next Wi-Fi (beyond 11be) aims to support ultra-high reliability when transmitting signals to STAs. To this end, various technologies are being considered to support high throughput, low latency, and extended range. To ensure reliable transmission and extend Wi-Fi coverage / range for various IoT devices as well as outdoor environments, APs can use relay operation to transmit signals to and receive signals from STAs. That is, signals are transmitted and received between relay STAs and non-AP STAs through relay operation. In this way, for signal transmission and reception between relay STAs and non-AP STA(s), the AP detects non-AP STA(s) located around the relay STA and determines whether to perform relay transmission. The present invention defines a method for an AP to detect non-AP STA(s) located around the relay STA for signal transmission and reception through relaying.

[0160] In next-generation wireless LAN systems (e.g., UHR systems based on IEEE 802.11bn), the use of the above-described Relay STA is being considered for stable signal transmission (i.e., reliable signal transmission) regardless of the location of the STA within the BSS, and for increasing coverage for signal transmission and eliminating holes where signals cannot reach.

[0161] As described above, Relay STAs perform various functions, operations, and procedures and can be implemented in various ways. To facilitate implementation and reduce operational complexity, this specification considers a Relay STA controlled by an AP. However, the Relay STA and related operations described herein are not limited to AP-controlled relay transmission and can be applied to all relay transmission and reception.

[0162] Figure 15 describes the characteristics of a Relay STA controlled by an AP.

[0163] As illustrated, an example of a Relay STA may be an AP-controlled Relay STA (ACRS). The ACRS performs relay transmission for data received from an AP within a BSS, and the AP controls the ACRS for relaying. That is, the ACRS may transmit a signal received from the AP to an end-user / STA based on control information received from the AP, or a relay STA may receive signals from multiple non-AP STAs and transmit the signals to the AP.

[0164] The above ACRS can operate as an independent relay device that only performs relay transmission or as a non-AP STA that supports relaying.

[0165] Below, the information exchanged within the BSS through the Management frame, etc. in this specification is described in more detail.

[0166] The Relay STA used in this specification may be referred to by various names. For example, it may be referred to by various names such as Relay, ACRS, Relay entity, and Relay device.

[0167] Hereinafter, various procedures for negotiating control information regarding the operation of a Relay STA are described. The relay operation / function / procedure performed by the Relay STA in this specification may be referred to as a Relay operation. This expression Relay operation may be changed to various names such as Relay function / procedure / transmission. Meanwhile, various control information / variables related to the Relay operation (e.g., parameters / control bits related to bandwidth, streams, MCS, etc.) may be referred to as relay operation parameter(s). These relay operation parameters may be changed to various names such as relay (control) information / bits / signals.

[0168] In order to indicate that a relay operation that transmits and receives signals through a Relay STA as described above is performed within a BSS, an AP STA may use a management frame (e.g., a beacon frame and / or a probe response frame). Specifically, the AP STA may indicate to STAs within the BSS information on whether the relay operation is supported / performed / activated based on the management frame (e.g., a beacon frame and / or a probe response frame). Specifically, the AP may transmit specific control information / fields / signals (e.g., Relay operation and / or Relay operation support information / fields) included within a management frame (e.g., a beacon frame). The Relay operation information / fields may be expressed in various terms. For example, in addition to the Relay operation information / fields, terms such as Relay operation parameter(s), Relay operation support parameter(s), Relay operation element(s), and Relay operation support element(s) may be used.

[0169] Below, various technical features applied to the Management frame proposed in this specification are described.

[0170] For example, Next Wi-Fi (which can be expressed in various terms such as beyond 11be, IEEE 802.11bn, etc.) aims to support UHR (ultra-high reliability) when transmitting signals to STAs. To this end, various technologies are being considered for high throughput, low latency, and extended range support. For this purpose, the next Wi-Fi can utilize signal transmission and reception using relay. For example, in order to efficiently support not only STAs within AP coverage (e.g., non-AP or end-STA) but also STAs outside AP coverage (e.g., non-AP or end-STA), a method for performing range extension during relay transmission and reception may be required.

[0171] In this way, if a method for transmitting a beacon frame to an STA outside of AP coverage is required to perform range extension using a relay, a relay beacon frame (or a frame with various names described below) can be defined and transmitted for relay transmission to reduce the overhead of the beacon frame through the relay. Therefore, the following describes various examples of a beacon frame configuration for range extension when transmitting and receiving signals using a relay and a method / device for transmitting the same.

[0172] In the above Next Wi-Fi, a relay STA can be used to transmit and receive signals smoothly to STAs existing in the coverage boundary of the AP and to expand the coverage of the AP.

[0173] The above relay STA may be an STA operating as an AP or non-AP STA. Additionally, the relay STA may be referred to by various names. For example, it may be referred to by various names such as Relay, ACRS, Relay entity, and Relay device.

[0174] FIG. 16 is a diagram illustrating the concept of range extension related to an example of the present specification. As illustrated, through signal transmission and reception using a relay STA, signals can be transmitted and received to an STA (e.g., a non-AP STA or end-STA) located outside the coverage of an AP, as in the example of FIG. 16.

[0175] In the case where a relay is used to transmit and receive signals to an STA (e.g., a non-AP STA or end-STA) that exists outside the AP coverage / range as shown in Fig. 16, a frame (e.g., Management frame) transmitted by the AP can be transmitted to the STA through the relay.

[0176] As shown in FIG. 16, STAs (e.g., non-AP STAs or end-STAs) that exist outside the coverage / range may not be able to receive the beacon frame transmitted by the AP. Therefore, the relay STA in FIG. 16 can receive the beacon frame transmitted by the AP and then broadcast it. In this case, the relay STA retransmitting the normal beacon frame (or various names can be changed) transmitted by the AP for range extension incurs a large overhead and may confuse legacy STAs due to repeated reception of the beacon frame.

[0177] Therefore, a new relay beacon frame (or one that can be renamed to various names) for relay operation can be defined. For example, when relay transmission is supported, the AP can transmit the relay beacon frame, and the relay beacon frame can include various technical features described below. The relay beacon frame proposed in this specification can be defined as a short frame with a smaller size than the normal beacon frame.

[0178] Below, examples of various beacon frames that can be transmitted from a relay (STA) are described. The beacon frame proposed in this specification can be called by various names such as relay beacon frame, relay management frame, relay probe response frame, first / second beacon frame, short / compact beacon frame, TX / RX beacon frame, etc.

[0179] The relay beacon frame proposed in this specification may be different from the existing beacon frame transmitted from an AP to a non-AP STA (or end-STA) according to the prior art. The existing beacon frame may be called by various names. For example, various names such as normal beacon frame, legacy beacon frame, long beacon frame, first / second beacon frame, TX / RX beacon frame, etc. may be used. The normal beacon frame may include various information. For example, the normal beacon frame may include various information of technical feature 4 described below.

[0180] For example, the relay beacon frame can be transmitted by various transmitting devices (e.g., relay STA or AP) and received by STA (e.g., non-AP STA or end-STA). For example, the normal beacon frame can be transmitted by AP. In addition, the normal beacon frame can be received by relay (STA) or received by STA (e.g., non-AP STA or end-STA).

[0181] Since the technical features of this specification may be varied in various ways, the technical features of this specification are not limited to FIG. 16. For example, an STA (e.g., a non-AP STA or end-STA) receiving a relay beacon frame may also be located within the coverage of the AP.

[0182] The above relay beacon frame may include indication information for various purposes (e.g., to distinguish it from the normal beacon frame).

[0183] Technical Features 1. For example, a field / information having a preset value for identifying the relay beacon frame may be included in the relay beacon frame. For example, indication information (or a field / information having a preset value for identifying the relay beacon frame) may be included in the type field and / or subtype field of the Frame control field included in the MAC header of the relay beacon frame. For example, the type field and / or subtype field of the Frame control field may be identical to the 2-bit type field and the 4-bit subtype field illustrated in FIG. 13.

[0184] Technical Features 1.1. For example, a 2-bit type field expressed as [B3 B2] may be defined in the Frame control field of the relay beacon frame transmitted by the Relay (STA) (or / and transmitted by the AP). For example, while the type field (i.e., B3 B2 bit) of the normal beacon frame is set to 00, the 2-bit type field expressed as [B3 B2] in the Frame control field of the relay beacon frame may be set to 11. That is, the type field of the Frame control field of the relay beacon frame may include a type description indicating the Extension type.

[0185] Technical Feature 1.2. Additionally or alternatively, for the relay beacon frame, a 4-bit subtype field expressed as [B7 B6 B5 B4] may be defined within the Frame control field. For example, the B7 B6 B5 B4 (i.e., the 4-bit subtype field) may be set to 0010, or may be set to at least one value from 0010 to 1111. For example, for the normal beacon frame, the B7 B6 B5 B4 (i.e., the 4-bit subtype field) may be set to 1000.

[0186] Technical Feature 1.3. Additionally or alternatively, the relay beacon frame may be defined as a management type (rather than an extension type). That is, [B3 B2] of the type field may be set to 00 (rather than 11 as described above). In this case, [B7 B6 B5 B4] of the subtype field of the relay beacon frame may be set to 0111 or 1111.

[0187] The above technical feature 1 may be used together with the technical features 2 / 3 / 4 described below, or may be used independently, regardless of the technical features 2 / 3 / 4 described below.

[0188] Below, more specific technical features of the above relay beacon frame are explained based on technical features 2 / 3 / 4 described below.

[0189] Technical Feature 2. The MAC header of the relay beacon frame may be the same MAC header as that of the Normal beacon frame. In this case, the content included in the (beacon) frame body of the relay beacon frame may be simplified / simplified compared to the (beacon) frame body of the Normal beacon frame.

[0190] Technical Feature 2.A. Relay beacon frame is configured with a frame body that is different from a normal beacon frame and can be configured to include the following content or elements. That is, below, the contents that can be included in the (beacon) frame body of the relay beacon frame can be based on at least one of the following Technical Feature 2.Ai to Technical Feature 2.A.xii.1.

[0191] Technical Features 2.Ai For example, Timestamp field / information may be included.

[0192] The Timestamp field indicates the value of the TSF (timing synchronization function) timer of the source (or transmitting device / STA) of the frame. The Timestamp field may have a length of 8 octets. For example, if the Relay beacon frame is transmitted by a relay STA, the Timestamp field may indicate the TSF timer (or timer value) of the relay STA.

[0193] Technical Feature 2.A.ii. For example, Relay beacon interval field / information may be included.

[0194] In general, the Beacon Interval field can indicate the number of TUs (time units) between TBTTs (target beacon transmission times). The Beacon Interval field can have a length of 2 octets. The Relay beacon interval information can indicate the number of TUs (time units) between TBTTs of a relay beacon frame other than a normal beacon.

[0195] Technical Features 2.A.iii. For example, the Service Set Identifier (SSID) field / information.

[0196] Technical Features 2.A.iii.1. The SSID field may include information related to SSID, which is string information used to identify the infrastructure of the BSS related to the relay beacon frame. In order to reduce overhead for the SSID, a compressed SSID (rather than a conventional Full SSID) may be used. That is, information related to the compressed SSID may be included in the relay beacon frame. The compressed SSID may include specific LSB bits (e.g., 16 LSBs) of the conventional SSID. When the compressed SSID is included in the relay beacon frame, 1-bit information indicating that the compressed SSID is used may be included in the frame control field / information of the relay beacon frame (or other control field / information in the MAC header).

[0197] Technical Feature 2.A.iv. For example, Traffic Indication Map (TIM) information / fields may be included. This information / field may indicate the TIM within the relay beacon interval.

[0198] Technical Feature 2.Av For example, the BSS Available Admission Capacity information / field may be included. This information / field may include a list of Available Admission Capacity fields according to different User Priorities and Access Categories.

[0199] Technical Features 2.A.vi. For example, the Multiple BSSID field / information may be included. The above field / information may include information regarding Multiple BSSIDs.

[0200] Technical Feature 2.A.vii. For example, the Multiple BSSID Configuration field / information may be included. The field / information may provide configuration information for multiple sets of BBSSIDs.

[0201] Technical Feature 2.A.viii. For example, the Transmit Power Envelope field / information may be included. This field / information may provide information regarding local or regulatory maximum transmit powers for various transmission bandwidths or channels within the BSS bandwidth.

[0202] Technical Features 2.A.ix. For example, Vendor Specific fields / information may be included.

[0203] Technical Features 2.Ax For example, the Relay capabilities field / information may be included. The field / information may provide various information related to relay operation (e.g., information about whether relay operation is supported, information about transmission power related to relay operation, identification information of at least one relay STA, information about the direction of relay operation, etc.).

[0204] Technical Features 2.A.xi. For example, the MLO operation field / information may be included. This field / information may provide various information for multi-link operation (e.g., information regarding whether multi-link is supported, link identifier information for links supported in multi-link, maximum number of links supported, etc.).

[0205] Technical Feature 2.A.xii. For example, a TSF offset field / information may be included.

[0206] Technical Feature 2.A.xii.1. For example, the TSF offset field / information may be set only when the relay beacon frame is transmitted by the relay STA. For example, if the beacon frame is transmitted by the AP, the value may be reserved. When the relay STA retransmits (e.g., forwards / relays) the relay beacon frame it has received, the time offset value identified by the relay STA may be transmitted through the field.

[0207] The above TSF offset field / information may be related to the above-described Timestamp field / information. The Timestamp field / information may indicate the TSF timer value of the source / transmitter (e.g., AP or relay STA) of the corresponding beacon frame.

[0208] For example, the Timestamp field / information included in the relay beacon frame transmitted by the relay STA may store a value (e.g., a timer value) related to the TSF timer of the relay STA. In this case, the STA (i.e., a non-AP STA or an end-STA) that has received the relay beacon frame may adjust / calculate / determine synchronization (e.g., time synchronization) between the STA (i.e., the non-AP STA or the end-STA) and the relay STA based on the Timestamp field / information. In addition, the STA (i.e., the non-AP STA or the end-STA) that has received the relay beacon frame may adjust / calculate / determine synchronization (e.g., time synchronization) between the STA (i.e., the non-AP STA or the end-STA) and the AP based on the TSF offset field / information. For example, the TSF offset field / information may include information (e.g., difference / offset of TSF timer value or time synchronization value) regarding synchronization (e.g., time synchronization) between an AP (e.g., an AP within a BSS to which the relay STA belongs) and the Relay STA.

[0209] Additionally or alternatively, when an AP (e.g., an AP within a BSS to which the relay STA belongs) transmits a beacon frame to a corresponding relay STA, the TSF offset field / information of the beacon frame may be set to reserved or omitted, and a value related to the TSF timer of the AP (e.g., a timer value) may be stored in the Timestamp field / information of the beacon frame.

[0210] Technical Feature 2.B. The fields / information (or elements or content) included in the above relay beacon frame are examples, and the relay beacon frame may be composed of only some of the above content or may include additional information. The content of the above relay beacon frame may be composed in various ways.

[0211] Technical Feature 2.C. Compared to the above-described Normal beacon, the relay beacon frame preferably minimizes the size of the fields / information (or elements or content) included in the frame body, thereby reducing the beacon size. This can achieve the technical effect of reducing the overhead of the beacon frame transmitted via the relay STA.

[0212] Technical Feature 3. The relay beacon frame proposed in this specification can be modified in various ways. While Technical Feature 2 described above is an example of a frame with the same MAC header as a normal beacon frame, this specification is not limited thereto. For example, the relay beacon frame of this specification can be newly defined and configured in a compact size. Specific examples are as follows.

[0213] Technical Feature 3.A. For example, the MAC header of the relay beacon frame may be defined as follows to transmit basic information about the AP and relay-related information. That is, the MAC header of the relay beacon frame may be one in which fields / bits / information included in the MAC header of the normal beacon frame are omitted / modified.

[0214] Technical Feature 3. For AI Beacon frames, the duration field may be set to 0, preventing its value from being used when receiving the beacon frame. Therefore, the relay beacon frame of this specification can be configured without the duration field. This achieves the technical benefit of a smaller relay beacon frame.

[0215] Technical Feature 3.A.ii. For example, since a beacon frame can always be broadcast, a receiver address and destination address may not be required. Accordingly, the relay beacon frame in this specification may only include the Transmitter (TX) address or source address that transmits the beacon frame.

[0216] Technical Features 3.A.ii.1. Additionally or alternatively, the TX address and source address may be set to the AP ID and / or BSS ID.

[0217] Technical Feature 3.A.iii. Additionally or alternatively, it is also possible for the destination STA receiving the Beacon frame to include information / fields related to the TSF for performing synchronization with the AP.

[0218] Technical Feature 3.A.iii.1. For example, information / fields related to the TSF may be set to the TSF of the AP when transmitting a relay beacon frame. For example, information / fields related to the TSF may be included in the MAC header.

[0219] Technical Features 3.B. For example, the technical features described above can be combined in various ways. Below, an example of the frame format of a relay beacon frame is described.

[0220] Technical Features 3.Bi Figure 17 shows an example of the frame format of the relay beacon frame of this specification.

[0221] Technical Feature 3.C. The frame body of the above frame is composed of basic information about the AP and information for relay operation, and may be composed of, for example, the following information. This is one embodiment, and the above information may be composed in different combinations.

[0222] For example, as illustrated in FIG. 17, the relay beacon frame may include a Frame control field / information. Additionally or alternatively, the Frame control field / information may have the feature of Technical Feature 1 described above. For example, the Frame control field / information of FIG. 17 may include a type and / or subtype field having preset values ​​for identifying the relay beacon frame. For example, the frame control field / information of FIG. 17 may have a length of 2 octets.

[0223] For example, as illustrated in FIG. 17, the relay beacon frame may include a TA / SA field / information that is consecutive to the Frame control field / information. The TA / SA field may include a transmitting address (i.e., TX address) or a source address (i.e., source address). For example, the TA / SA field of FIG. 17 may have a length of 2 octets. The TA / SA field may have various names (e.g., address 1 field / information, control information field, first field / information, etc.).

[0224] For example, as illustrated in FIG. 17, the relay beacon frame may include a sequence control field / information that is continuous with the TA / SA field / information. For example, the sequence control field / information may have a length of 2 octets. For example, the sequence control may indicate a fragment number or sequence number of a related MAC frame to identify the related MAC frame.

[0225] For example, as illustrated in FIG. 17, the relay beacon frame may include TSF information / fields subsequent to the sequence control field / information. As illustrated, the TSF information / fields may be inserted into the MAC header.

[0226] For example, as illustrated in FIG. 17, there may be a MAC header including at least one of frame control information / field, TA / SA information / field, Sequence control information / field, and TSF information / field, and a Frame body continuous to the MAC header.

[0227] For example, as illustrated in FIG. 17, the MAC header for the relay beacon frame may omit the duration field. Additionally or alternatively, as illustrated in FIG. 17, the MAC header for the relay beacon frame may include only one address field.

[0228] The Frame body of FIG. 17 may include detailed information / fields of the above-described Technical Feature 2 (e.g., the above-described timestamp information, TSF offset information, and / or Relay Beacon Interval information, etc.). Additionally or alternatively, the Frame body may include a combination of various fields described in Technical Feature 3.C below.

[0229] Technical Features 3.Ci For example, it may include Service Set-Identifier (SSID) information / field.

[0230] Technical Feature 3.Ci1. For example, a compressed SSID can be used to reduce overhead. For example, an indication of the use of a compressed SSID can be performed through the MAC header. For example, to indicate this, the compressed SSID field can be included in the MAC header of Figure 1.

[0231] For example, the above-described technical feature 3.Ci1. may be identical to the information / fields of the previously described technical feature 2.A.iii.1.

[0232] Technical Feature 3.C.ii. For example, Traffic Indication Map (TIM) information / fields may be included. For example, such information / fields may indicate TIMs within a relay beacon interval. For example, such information / fields may be identical to the information / fields in Technical Feature 2.A.iv.

[0233] Technical Feature 3.C.iii. For example, BSS Available Admission Capacity information / fields may be included. These information / fields may be identical to those in Technical Feature 2.Av.

[0234] Technical Feature 3.C.iv. For example, Multiple BSSID information / fields may be included. This information / fields may be identical to those in Technical Feature 2.A.vi.

[0235] Technical Feature 3.Cv For example, Multiple BSSID Configuration information / fields may be included. The information / fields may be identical to the information / fields in Technical Feature 2.A.vii.

[0236] Technical Feature 3.C.vi. For example, Transmit Power Envelope information / fields may be included. These information / fields may be identical to those in Technical Feature 2.A.viii.

[0237] Technical Feature 3.C.vii. For example, Vendor Specific information / fields may be included. These information / fields may be identical to those in Technical Feature 2.A.ix.

[0238] Technical Feature 3.C.viii. For example, Relay capabilities information / fields may be included. These information / fields may be identical to those in Technical Feature 2.Ax.

[0239] Technical Feature 3.C.ix. For example, MLO operation information / fields may be included. These information / fields may be identical to those in Technical Feature 2.A.xi.

[0240] Technical Feature 3.Cx For example, TSF offset information / field may be included. This information / field may be identical to the information / field in Technical Feature 2.A.xii.

[0241] Technical Feature 3.Cx1. For example, when an AP transmits, the value is reserved. For example, when a relay STA retransmits a relay beacon frame received, the relay STA can transmit the time offset value it has identified through this field.

[0242] Additionally or alternatively, for transmission of a relay beacon frame configured as described above, the AP may include information about the relay beacon frame within the normal beacon frame. Furthermore, the AP may transmit the normal beacon frame within its own BSS.

[0243] Additionally or alternatively, the normal beacon frame may include at least one of the following various fields (e.g., various fields related to the relay beacon frame, relay operation, and / or relay STA). The specific characteristics of the normal beacon frame are described in Technical Characteristic 4 below.

[0244] Technical Feature 4. For example, the above Normal beacon frame may include various combinations of the following fields.

[0245] Technical Features 4.1. For example, the above Normal beacon frame may include Relay operation information / fields.

[0246] Technical Features 4.1.1. For example, the Relay operation information / field may include information / fields related to whether Relay is supported. For example, the information / field may have a length of 1 bit or 2 bits. For example, the information / field may include information regarding whether the AP transmitting the Normal beacon frame (or the BSS related to the AP) supports the Relay (operation).

[0247] Technical Features 4.1.2. Additionally or alternatively, the Relay operation information / field may include information related to the Relay transmission direction.

[0248] Technical Features 4.1.2.1. For example, the information related to the Relay transmission direction may be a DL / UL indication for the Relay transmission. For example, the information / field may indicate downlink or uplink based on 1 bit, or may indicate at least one direction of downlink, uplink, or both based on 2 bits. For example, the information / field may be information about the direction of the Relay transmission supported by the AP (or the BSS related to the AP) transmitting the Normal beacon frame.

[0249] Technical Features 4.1.3. Additionally or alternatively, the Relay operation information / field may include information / fields related to Relay STA information. The Relay STA information is information related to the Relay STA, and may include, for example, identification (ID) information for the Relay STA, (Radio / RF / PHY / MAC) capability information for the Relay STA, etc.

[0250] Technical Feature 4.2. For example, the Normal beacon frame may include Relay beacon support information / field. For example, the information / field may include information regarding whether the AP transmitting the Normal beacon frame (or the BSS associated with the AP) supports the Relay beacon frame.

[0251] Technical Features 4.2.1. Additionally or alternatively, the Normal beacon frame and / or the Relay beacon support information / field may include information regarding the Relay beacon interval.

[0252] Technical Features 4.2.1.1. For example, the information about the relay beacon interval may be information about the cycle at which the relay beacon frame is transmitted.

[0253] Technical Features 4.2.2. Additionally or alternatively, the Normal beacon frame and / or the Relay beacon support information / field may include information regarding the Relay window.

[0254] Technical Features 4.2.2.1. For example, the information about the Relay window may include information about the time duration during which the Relay transmission is performed.

[0255] Technical Features 4.3. For example, the above Normal beacon frame may include Relay communication capabilities information / field.

[0256] Technical Features 4.3.1. For example, the Normal beacon frame and / or Relay communication capabilities information / field may include BW information / field.

[0257] Technical Features 4.3.1.1. For example, the BW information / field may include information on 20 / 40 / 80 / 160 / 320MHz as information on the Bandwidth used for Relay transmission.

[0258] Technical Features 4.3.2. For example, the Normal beacon frame and / or Relay communication capabilities information / field may include MCS information / field.

[0259] Technical Features 4.3.2.1. For example, the MCS information / field may include an indication of the max MCS allowed during relay transmission.

[0260] Technical Features 4.3.3. For example, the Normal beacon frame and / or Relay communication capabilities information / field may include NSS information / field.

[0261] Technical Features 4.3.3.1. For example, the NSS information / field may indicate information about the max Number of SS to be considered when transmitting relays.

[0262] Technical Features 4.3.4. For example, the Normal beacon frame and / or Relay communication capabilities information / field may include Ack policy information / field.

[0263] Technical Features 4.3.4.1. For example, the Ack policy information / field may indicate that the immediate ACK policy and / or delayed ACK policy are used as the ack policy for data received during relay transmission.

[0264] Technical Features 4.3.5. For example, the Normal beacon frame and / or Relay communication capabilities information / field may include SU / MU relay indication information / field.

[0265] Technical Features 4.3.5.1. For example, the SU / MU relay indication information / field may indicate whether SU / MU transmission is supported when transmitting and receiving relays.

[0266] Technical Features 4.3.6. For example, information related to the capabilities defined above (e.g., BW / MCS / NSS / ACK-policy / SU-MU-relay-indication, etc.) can be transmitted in a relay beacon frame.

[0267] The relay beacon frame defined as above is transmitted within the normal beacon interval, and one or more relay beacon frames can be transmitted within the normal beacon interval. At this time, the relay beacon frame can be transmitted a certain time after the normal beacon frame is transmitted. The time at which the relay beacon frame is transmitted can be defined as, for example, SIFS or PIFS or XIFS, or a point in time corresponding to 1 / 2 (i.e., half) or 1 / 3 (i.e., one-third) of the beacon frame period.

[0268] Fig. 18 shows an example of transmission and reception of a relay beacon frame and a normal beacon frame. As illustrated, the transmission period of normal beacon frames (1810, 1850) is determined according to the Beacon Interval. In addition, the transmission period of relay beacon frames (1820, 1830, 1840) is determined according to the Relay Beacon Interval. As illustrated, the Relay Beacon Interval of the present specification is preferably shorter than the Beacon Interval. In addition, as described above, the transmission time of the relay beacon frame (1820) may be after a time corresponding to 1 / 2 (i.e., half) or 1 / 3 (i.e., one-third) of the SIFS or PIFS or XIFS or the beacon frame period has elapsed from the transmission time of the normal beacon frame (1810).

[0269] The operations of this specification may be performed by various devices.

[0270] For example, the AP can transmit a beacon frame according to the method illustrated in FIG. 18. For example, the AP of the present specification can include information about the relay beacon frame in the normal beacon frame to transmit the relay beacon frame configured as described above. In addition, the AP can transmit the normal beacon frame within its own BSS. The specific features of the above-described technical feature 4 can be applied to the normal beacon frame.

[0271] The above normal beacon frame can be transmitted to various devices within the BSS. For example, the above normal beacon frame can be transmitted to a relay STA. For example, if a non-AP STA is not located within the coverage of the AP, the above normal beacon frame can be transmitted only to the relay STA and not to the end STA (or non-AP STA).

[0272] The above relay STA can receive a normal beacon frame (e.g., based on the above technical feature 4) from the AP and generate a relay beacon frame based on the received normal beacon frame. The technical features applied to the above relay beacon frame may be identical to the specific contents of the above technical features 1 / 2 / 3. The above relay beacon frame can also be transmitted to an end-STA (or non-AP STA) located outside the coverage of the AP / BSS. In addition, the relay beacon frame can also be transmitted to an end-STA (or non-AP STA) located within the coverage of the AP / BSS.

[0273] Figure 19 is a procedure flow chart based on an example of this specification.

[0274] For example, the operation of FIG. 19 can be performed in a non-AP STA.

[0275] As shown in step S1910, a Non-AP (Non Access Point) STA (Station) can receive a relay beacon frame from a relay STA. The relay beacon frame can be called by various names such as a relay beacon frame, a relay management frame, a relay probe response frame, a first / second beacon frame, a short / compact beacon frame, a TX / RX beacon frame, etc.

[0276] The relay beacon frame may include various technical features described in Technical Features 1 to 3 described above. Additionally or alternatively, the relay beacon frame may include a MAC (Medium Access Control) header including a Frame Control field, and a frame body. Additionally or alternatively, the Frame Control field may include a type field having a preset value for identifying the relay beacon frame. For example, the type field having the preset value may be a 2-bit type field or a 4-bit subtype field described in Technical Features 1.1 to 1.3 described above. Additionally or alternatively, the type field of the present specification may be at least one of the 2-bit type field and / or the 4-bit subtype field described above, or may include at least one of the 2-bit type field and / or the 4-bit subtype field described above. Additionally or alternatively, the frame body may include information regarding a relay beacon interval for the relay beacon frame. The frame body may include various information / fields described in Technical Features 2 to 3 described above. For example, the frame body may include a plurality of information / fields described in the subsections of Technical Feature 2.A.

[0277] Additionally or alternatively, the relay beacon interval may be set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point).

[0278] As shown in step S1920, the Non-AP (Non Access Point) STA can obtain information included in the relay beacon frame. For example, the non-AP STA can obtain at least one field / information of the frame body included in the relay beacon frame. For example, it can obtain at least one of the plurality of information / fields described in the detailed items of the technical feature 2.A (for example, information related to timestamp / relay-beacon-interval / SSID / TSF-offset, etc. described above).

[0279] Additionally or alternatively, the type field may have a length of 2 or 4 bits. For example, the type field having the preset value may have at least one of the technical features described in Technical Features 1.1 to 1.3.

[0280] Additionally or alternatively, the frame body may include a time stamp field containing information related to a timing synchronization function (TSF) timer of the relay STA and a TSF offset field set by the relay STA. Detailed characteristics regarding the time stamp field are described in Technical Feature 2.Ai.

[0281] The TSF offset field may include information regarding a synchronization offset between the access point (AP) of the relay STA and the relay STA. Detailed characteristics regarding the TSF offset field are described in Technical Feature 2.A.xii.1.

[0282] Additionally or alternatively, the MAC header may include a TSF field that includes information related to a TSF timer of the relay STA. For example, the TSF field may be the TSF field illustrated in FIG. 17. For example, as illustrated in FIG. 17, the TSF field may be continuous with the frame body.

[0283] Additionally or alternatively, the beacon frame received from the AP (Access Point) may further include information regarding relay operations related to the relay STA. The information regarding relay operations related to the relay STA may be identical to the fields / information described in Technical Feature 4.1 and / or Technical Feature 4.2 described above.

[0284] Figure 20 is a procedure flow chart based on an example of this specification.

[0285] For example, the operation of FIG. 20 can be performed in a relay STA.

[0286] Although not illustrated in FIG. 20, the Relay STA may perform an operation of receiving the normal beacon frame from the AP. The normal beacon frame may include various fields / information of the technical feature 4 described above.

[0287] As illustrated in S2010, a relay beacon frame can be generated by a relay STA. The relay beacon frame can be generated based on the normal beacon frame previously received by the relay STA.

[0288] Other various features applicable to the above step S2010 may be identical to the technical features described in the above step S1910.

[0289] As illustrated in S2020, the relay STA can transmit the generated relay beacon frame to a non-AP STA.

[0290] The technical features of the present disclosure may be implemented by various devices. The devices of the present disclosure may be the devices described in FIG. 1 / FIG. 14. The devices of the present disclosure may include at least one processor; and at least one computer memory operably connectable to the at least one processor, the computer memory storing instructions for performing operations based on execution by the at least one processor.

[0291] For example, the processor may be a processor described in FIG. 1 and / or FIG. 14. That is, as described above, the processor of the present specification may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). The processor may include not only computers having various architectures such as single / multiprocessor architecture, sequential (Von Neumann) / parallel architecture, but also specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices. For example, the processor of the present specification may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or a processor that enhances the same.

[0292] For example, the instructions may refer to computer program instructions executed by the at least one processor. The (computer program) instructions provide logic and / or routines that enable the technical features of the present specification to be performed by the processor. The at least one processor can load and execute a computer program by reading the at least one memory.

[0293] The computer program(s) defined by the above instructions may be delivered to the device (e.g., STA) of the present specification via an appropriate delivery mechanism. The delivery mechanism may be, for example, a computer-readable storage medium, a computer program product, a memory device, a recording medium such as a CD-ROM or DVD, or a product tangibly embodying the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.

[0294] The above (computer program) instructions may include software or firmware for a programmable processor (e.g., programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device, etc.).

[0295] For example, the memory may be the memory described in FIG. 1 and / or FIG. 14. That is, as described above, the memory of the present specification may store control information related to the operation of the STA of the present specification or information about signals transmitted and received by the STA (e.g., PPDU including management / control / data frames).

[0296] The technical features of this specification may be implemented in at least one computer-readable recording medium (CRM). The CRM includes instructions that are executed by at least one processor as described above. The instructions stored in the CRM may be computer program instructions as described above.

[0297] The device of the present disclosure may further include a transceiver. The transceiver may be operably connectable to the memory / processor, etc. The transceiver may be the transceiver illustrated in FIG. 1 and / or FIG. 14.

[0298] The technical features of this specification described above are applicable to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).

[0299] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0300] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0301] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.

[0302] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0303] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.

[0304] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.

[0305] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.

[0306] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.

[0307] Additionally, the above-described technical features can be applied to wireless communication of robots.

[0308] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.

[0309] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.

[0310] Additionally, the above-described technical features can be applied to devices that support extended reality.

[0311] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0312] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0313] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

Claims

1. A Non-AP (Non Access Point) STA (Station) receives a relay beacon frame from a relay STA. The above relay beacon frame includes a MAC (Medium Access Control) header including a frame control field, and a frame body, The above frame control field includes at least one of a type field and a subtype field having a preset value for identifying the relay beacon frame, The above frame body includes information about a relay beacon interval for the above relay beacon frame, The above relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point); and A step of obtaining information included in the above relay beacon frame How to include.

2. In the first paragraph, the type field has a length of 2 bits, and the subtype field has a length of 4 bits. method.

3. In the first paragraph, the frame body includes a time stamp field including information related to a TSF (timing synchronization function) timer of the relay STA and a TSF offset field set by the relay STA, The TSF offset field includes information about the synchronization offset between the AP and the relay STA. method.

4. In the first paragraph, the MAC header includes a TSF field including information related to the TSF timer of the relay STA. method.

5. In the fourth paragraph, the TSF field is continuous to the frame body. method.

6. In the first paragraph, the beacon frame received from the AP further includes information regarding relay operation related to the relay STA, The information about the relay operation includes at least one of information about whether the relay operation is supported by the AP, information about the direction of the relay operation, information about whether the relay beacon frame is supported by the AP, and information about the relay beacon interval. method.

7. In the first paragraph, the beacon frame received from the AP further includes information regarding relay operation related to the relay STA, The information about the relay operation includes at least one of information about a bandwidth supported by the relay operation, information about an MCS (Modulation and Coding Scheme) supported by the relay operation, information about the number of spatial streams supported by the relay operation, information about an ACK policy supported by the relay operation, and information about whether SU (single user) or MU (multi user) communication is supported by the relay operation. method.

8. At least one processor included in a Non-AP (Non Access Point) STA (Station); and At least one computer memory operable to said at least one processor, said memory storing instructions for performing operations based on being executed by said at least one processor, The instructions of at least one computer memory are: By the above Non-AP STA, a relay beacon frame is received from a relay STA, The above relay beacon frame includes a MAC (Medium Access Control) header including a frame control field, and a frame body, The above frame control field includes at least one of a type field and a subtype field having a preset value for identifying the relay beacon frame, The above frame body includes information about a relay beacon interval for the above relay beacon frame, The above relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point); and A step of obtaining information included in the above relay beacon frame Performing the operation of Non-AP STA.

9. In the 8th paragraph, the command of at least one computer memory performs an operation related to any one of the 2nd to 7th paragraphs. Non-AP STA.

10. A relay beacon frame is generated by a relay STA (Station). The above relay beacon frame includes a MAC (Medium Access Control) header including a frame control field, and a frame body, The above frame control field includes at least one of a type field and a subtype field having a preset value for identifying the relay beacon frame, The above frame body includes information about a relay beacon interval for the above relay beacon frame, The above relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point); and A step of transmitting the relay beacon frame to a Non-AP (Non Access Point) STA by the relay STA. How to include.

11. In the 10th paragraph, the relay STA performs an operation related to any one of the 2nd to 7th paragraphs. method.

12. At least one processor included in a relay STA (Station); and At least one computer memory operable to said at least one processor, said memory storing instructions for performing operations based on being executed by said at least one processor, The instructions of at least one computer memory are: By the above relay STA (Station), a relay beacon frame is generated, The above relay beacon frame includes a MAC (Medium Access Control) header including a frame control field, and a frame body, The above frame control field includes at least one of a type field and a subtype field having a preset value for identifying the relay beacon frame, The above frame body includes information about a relay beacon interval for the above relay beacon frame, The above relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point); and A step of transmitting the relay beacon frame to a Non-AP (Non Access Point) STA by the relay STA. Performing the operation of Relay STA.

13. In the 12th paragraph, the command of at least one computer memory performs an operation related to any one of the 2nd to 7th paragraphs. Relay STA.

14. In a wireless local area network (WLAN) system, at least one computer-readable recording medium including instructions based on being executed by at least one processor, The above relay beacon frame includes a MAC (Medium Access Control) header including a frame control field, and a frame body, The above frame control field includes at least one of a type field and a subtype field having a preset value for identifying the relay beacon frame, The above frame body includes information about a relay beacon interval for the above relay beacon frame, The above relay beacon interval is set shorter than the beacon interval of a beacon frame transmitted from an AP (Access point); and A step of obtaining information included in the above relay beacon frame Performing an operation that includes A computer-readable recording medium.

Images