Method and apparatus for rescheduling target wakeup time service period in wireless LAN system

By introducing a rescheduling method of the limited target wake-up time (r-TWT) service period in the WLAN system, the problem of delay-sensitive service support in the WLAN system is solved, and efficient transmission of delay-sensitive data is achieved.

CN118891933APending Publication Date: 2024-11-01LG ELECTRONICS INC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202380027988.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-28
Filing Date
2023-03-17
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

In WLAN systems, the prior art is difficult to effectively support delay-sensitive services, especially when multiple STAs compete to occupy media, resulting in an increase in transmission delay and it is difficult to meet the demand for delay-sensitive services.

Method used

By introducing a rescheduling method of the restricted target wake-up time (r-TWT) service period in the WLAN system, the new TWT information field contains r-TWT related subfields, all TWT subfields and the next TWT subfields to STA Send scheduling information to enable support for delay-sensitive services.

Benefits of technology

It realizes effective support for delay-sensitive services in WLAN system, optimizes data transmission of low-latency STAs, and improves the system's transmission efficiency for delay-sensitive data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118891933A_ABST
    Figure CN118891933A_ABST
Patent Text Reader

Abstract

Disclosed are a method and apparatus for rescheduling a target wakeup time (TWT) service period (SP) in a wireless LAN system. According to one embodiment of the present disclosure, a method performed by a station (STA) in a wireless LAN system comprises the steps of: establishing an agreement relating to a restricted target wake-up time (r-TWT); and transmitting at least one frame including the TWT information field to one or more other STAs. Here, the TWT information field may include an r-TWT related subfield, an all TWT subfield, and a next TWT subfield, and rescheduling related information on the r-TWT SP scheduled for the STA may be indicated based on the r-TWT related subfield, the all TWT subfield, and the next TWT subfield.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to target wake time (TWT) operation in a wireless local area network (WLAN) system, and more particularly, to methods and apparatus related to rescheduling of restricted TWT service periods in a next generation WLAN system. Background Art

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

[0003] In order to provide a further improved wireless communication environment, enhanced technologies for EHT (Extremely High Throughput) are being discussed. For example, technologies supporting increased bandwidth, efficient use of multiple frequency bands, and increased spatial streams, multiple input multiple output (MIMO) and multiple access point (AP) coordination are being studied, and specifically, various technologies for supporting low latency or real-time services are being studied. In addition, new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions of EHT technologies. Summary of the invention

[0004] Technical issues

[0005] The technical problem to be solved by the present disclosure is to provide a method and a device for sending delay-sensitive services in a WLAN system.

[0006] An additional technical object of the present disclosure is to provide methods and apparatus related to suspension and / or resumption of a restricted TWT service period (SP) in a wireless LAN system.

[0007] An additional technical objective of the present disclosure is to provide a method and apparatus for requesting or indicating extension of an end point for a restricted TWT SP in a WLAN system.

[0008] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art can clearly understand other technical objectives not described herein through the following description.

[0009] Technical Solution

[0010] According to one aspect of the present disclosure, a method performed by a station (STA) in a wireless LAN system may include the following steps: establishing an agreement related to a restricted target wake-up time (r-TWT); and sending at least one frame including a TWT information field to one or more other STAs. In this article, the TWT information field may include an r-TWT related subfield, a total TWT subfield, and a next TWT subfield, and may indicate rescheduling related information about an r-TWT service period (r-TWT SP) scheduled for the STA based on the r-TWT related subfield, the total TWT subfield, and the next TWT subfield.

[0011] Beneficial Effects

[0012] According to the present disclosure, a method and apparatus for sending delay-sensitive services in a WLAN system can be provided.

[0013] According to the present disclosure, methods and apparatuses related to suspension and / or resumption of a restricted TWT service period (SP) in a wireless LAN system may be provided.

[0014] According to the present disclosure, a method and apparatus for requesting or indicating extension of an end point for a restricted TWT SP in a WLAN system may be provided.

[0015] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the art through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 A configuration block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0018] Figure 2 is a diagram illustrating an exemplary structure of a WLAN system to which the present disclosure can be applied.

[0019] Figure 3 is a diagram for explaining a link establishment process to which the present disclosure can be applied.

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

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

[0022] Figure 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0023] Figure 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0024] Figures 8 to 10 is a diagram for explaining an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0025] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0026] Fig.12 is a diagram for explaining a MU-MIMO method in which multiple users / STAs are assigned to one RU.

[0027] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0028] Fig.14 is a diagram for describing an example of a separate TWT operation to which the present disclosure can be applied.

[0029] Fig.15 is a diagram for describing an example of a broadcast TWT operation to which the present disclosure may be applied.

[0030] Fig.16 is a diagram for describing an example of the TWT information field format.

[0031] Fig.17 is a diagram for describing an example of the TWT information element format.

[0032] Fig.18 is a diagram for describing an example of the format of individual TWT parameter set fields.

[0033] Fig.19 is a diagram used to describe an example of the broadcast TWT parameter set field format.

[0034] Fig. 20 is a diagram for describing an example of restricted TWT operation.

[0035] Fig.21 An example of an r-TWT related information frame according to the present disclosure is illustrated.

[0036] Fig. 22 An example of restricted TWT operation based on r-TWT information frame according to the present disclosure is illustrated.

[0037] Fig.23 Another example of restricted TWT operation based on r-TWT information frame according to the present disclosure is illustrated.

[0038] Fig.24 Another example of an r-TWT related information frame according to the present disclosure is illustrated.

[0039] Fig.25 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0040] Fig.26 Another example of an r-TWT related information frame according to the present disclosure is illustrated.

[0041] Fig. 27 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0042] Fig.28 An example of restricted TWT operation considering extended r-TWT SP according to the present disclosure is illustrated.

[0043] Fig.29 Another example of restricted TWT operation considering extended r-TWT SP according to the present disclosure is illustrated.

[0044] Fig.30 2 is a diagram for explaining the operation of a STA supporting rescheduling of an r-TWT SP according to one embodiment of the present disclosure. DETAILED DESCRIPTION

[0045] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art know that the present disclosure can be implemented without these specific details.

[0046] In some cases, well-known structures and devices may be omitted, or may be shown in the form of a block diagram based on the core functions of each structure and device in order to prevent ambiguity of the concepts of the present disclosure.

[0047] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between another element and a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

[0048] In the present invention, terms such as "first", "second", etc. are only used to distinguish one element from another element and are not used to limit the elements, and unless otherwise specified, they do not limit the order or importance between the elements, etc. Therefore, within the scope of the present disclosure, the first element in an embodiment may be referred to as the second element in another embodiment, and similarly, the second element in an embodiment may be referred to as the first element in another embodiment.

[0049] The terms used in this disclosure are intended to describe specific embodiments, rather than to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form, unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in the present invention has the same meaning as "and / or".

[0050] Examples of the present disclosure can be applied to various wireless communication systems. For example, examples of the present disclosure can be applied to wireless LAN systems. For example, examples of the present disclosure can be applied to wireless LANs based on IEEE 802.11a / g / n / ac / ax standards. In addition, examples of the present disclosure can be applied to wireless LANs based on the newly proposed IEEE 802.11be (or EHT) standard. Examples of the present disclosure can be applied to wireless LANs based on the IEEE802.11be version 2 standard corresponding to the additional enhanced technology of the IEEE 802.11be version 1 standard. In addition, examples of the present disclosure can be applied to wireless LANs based on next-generation standards after IEEE 802.11be. In addition, examples of the present disclosure can be applied to cellular wireless communication systems. For example, it can be applied to cellular wireless communication systems based on long term evolution (LTE) technology and 5G new radio (NR) technology based on the third generation partnership project (3GPP) standard.

[0051] Hereinafter, technical features of examples to which the present disclosure can be applied will be described.

[0052] Figure 1 A block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0053] Figure 1The first device 100 and the second device 200 illustrated in the figure may be replaced with various terms such as terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), mobile subscriber unit (MSU), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT) or simple user, etc. In addition, the first device 100 and the second device 200 include an access point (AP), a base station (BS), a fixed station, a node B, a base transceiver system (BTS), a network. It may be replaced with various terms such as an artificial intelligence (AI) system, a roadside unit (RSU), a repeater, a router, a relay and a gateway.

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

[0055] refer to Figure 1 , the first device 100 and the second device 200 can send and receive radio signals through various wireless LAN technologies (e.g., IEEE802.11 series). The first device 100 and the second device 200 may include interfaces for a media access control (MAC) layer and a physical layer (PHY) that conform to the IEEE802.11 standard.

[0056] In addition, in addition to the wireless LAN technology, the first device 100 and the second device 200 may further support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) technologies. In addition, the device of the present disclosure may be implemented in various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) devices, and virtual reality (VR) devices. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, machine type communications (MTC), machine to machine (M2M), device to device (D2D), IoT (Internet of Things), etc.

[0057] The first device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 102 may send a wireless signal including the first information / signal through the transceiver 106 after generating the first information / signal by processing the information in the memory 104. In addition, the processor 102 may receive a wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by the signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0058] The second device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in the present disclosure. For example, the processor 202 may generate third information / signals by processing the information in the memory 204, and then send a wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained by signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a device may refer to a communication modem / circuit / chip.

[0059] In the following, the hardware elements of the apparatus 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, suggestions, and / or methods disclosed in the present disclosure to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure and obtain a PDU, SDU, message, control information, data, or information.

[0060] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, and the like. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts included in the present disclosure may be implemented using firmware or software in the form of codes, instructions and / or instruction sets.

[0061] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0062] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or operation flow chart, etc. included in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, suggestions, methods and / or operation flow charts, etc. included in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals into baseband signals to process received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals into RF band signals. Thus, one or more of the transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0063] For example, one of the STAs 100 and 200 may perform the expected operation of an AP, and the other of the STAs 100 and 200 may perform the expected operation of a non-AP STA. Figure 1 The transceivers 106 and 206 of the present invention may perform transmission and reception operations of signals (e.g., packets or physical layer protocol data units (PPDUs) compliant with IEEE 802.11a / b / g / n / ac / ax / be). In addition, in the present disclosure, operations of various STAs generating transmission / reception signals or performing data processing or calculations on transmission / reception signals in advance may be performed by Figure 1The processors 102 and 202 are executed. For example, examples of operations of generating a transmission / reception signal or performing data processing or calculation for the transmission / reception signal in advance may include: 1) determining / obtaining / configuring / calculating / decoding / encoding bit information of fields (signal (SIG), short training field (STF), long training field (LTF), data, etc.) included in the PPDU; 2) determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) for fields (SIG, STF, LTF, data, etc.) included in the PPDU; 3) determining / configuring / obtaining a specific sequence (e.g., pilot sequence, STF / LTF sequence, additional sequence applied to SIG) for fields (SIG, STF, LTF, data, etc.) included in the PPDU action; 4) power control operations and / or power saving operations applied to STAs; 5) operations related to ACK signal determination / obtaining / configuring / calculating / decoding / encoding, etc. In addition, in the following example, various information used by various STAs to determine / acquire / configure / calculate / decode / encode transmission signals and reception signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) may be stored in Figure 1 in the memories 104 and 204.

[0064] Hereinafter, a downlink (DL) may mean a link for communication from an AP STA to a non-AP STA, and a DL PPDU / packet / signal may be transmitted and received through the DL. In DL communication, a transmitter may be a part of an AP STA, and a receiver may be a part of a non-AP STA. An uplink (UL) may mean a link for communication from a non-AP STA to an AP STA, and a UL PPDU / packet / signal may be transmitted and received through the UL. In UL communication, a transmitter may be a part of a non-AP STA, and a receiver may be a part of an AP STA.

[0065] Figure 2 is a diagram illustrating an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

[0066] The structure of the wireless LAN system may be composed of a plurality of components. A wireless LAN supporting STA mobility transparent to an upper layer may be provided through the interaction of the plurality of components. A basic service set (BSS) corresponds to a basic building block of a wireless LAN. Figure 2 It is exemplarily shown that two BSSs (BSS1 and BSS2) exist, and two STAs (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2) are included as members of each BSS. Figure 2The ellipse representing the BSS in the figure can also be understood as representing the coverage area in which the STAs included in the corresponding BSS maintain communication. This area can be called a basic service area (BSA). When a STA moves outside the BSA, it cannot communicate directly with other STAs in the BSA.

[0067] If you don't consider Figure 2 , the most basic BSS type in the wireless LAN is an independent BSS (IBSS), if the DS is shown in FIG. 1 . For example, an IBSS may have a minimum form containing only two STAs. For example, assuming that other components are omitted, a BSS1 containing only STA1 and STA2 or a BSS2 containing only STA3 and STA4 may correspond to representative examples of IBSSs, respectively. This configuration is possible when STAs can communicate directly without an AP. In addition, in this type of wireless LAN, it is not pre-configured but can be configured when a LAN is needed, and this may be referred to as an ad-hoc network. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, STAs are managed in a distributed manner. In the IBSS, all STAs may be composed of mobile STAs, and access to the distributed system (DS) is not allowed, thereby forming a self-contained network.

[0068] The membership of a STA in a BSS can be changed dynamically by turning the STA on or off, entering or exiting a BSS region, etc. In order to become a member of a BSS, a STA can join the BSS using a synchronization process. In order to access all services of the BSS infrastructure, a STA should associate with the BSS. This association can be established dynamically and can include the use of a distributed system service (DSS).

[0069] The direct STA-to-STA distance in a wireless LAN may be limited by PHY performance. In some cases, this distance limitation may be sufficient, but in some cases, communication between STAs at longer distances may be required. A distributed system (DS) can be configured to support extended coverage.

[0070] DS refers to the structure of BSS interconnection. Specifically, Figure 2As shown, the BSS can exist as an extended form of a network composed of multiple BSSs. DS is a logical concept and can be specified by the characteristics of the distributed system medium (DSM). At this point, the wireless medium (WM) and the DSM can be logically separated. Each logical medium is used for different purposes and is used by different components. These media are not limited to being the same, nor are they limited to being different. In this way, the flexibility of the wireless LAN structure (DS structure or other network structure) can be interpreted as multiple media being logically different. That is, the wireless LAN structure can be implemented in various ways, and the corresponding wireless LAN structure can be independently specified by the physical characteristics of each implementation.

[0071] DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary to address the address leading to the destination. In addition, DS can also include a component called a portal, which is used as a bridge for connection between wireless LAN and other networks (e.g., IEEE 802.X).

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

[0073] Data sent from one of the STAs associated with the AP to the STA address of the corresponding AP can always be received at the uncontrolled port and can be processed by the IEEE 802.1X port access entity. In addition, when the controlled port is authenticated, the transmitted data (or frame) can be passed to the DS.

[0074] In addition to the above-mentioned structure of the DS, an extended service set (ESS) may also be configured to provide wide coverage.

[0075] ESS means a network with arbitrary size and complexity consisting of DS and BSS. ESS may correspond to a set of BSSs connected to one DS. However, ESS does not include DS. The ESS network is characterized by being regarded as an IBSS in the logical link control (LLC) layer. The STAs included in the ESS can communicate with each other, and the mobile STA can move from one BSS to another (within the same ESS) transparently for LLC. The APs included in one ESS may have the same service set identifier (SSID). SSID is distinguished from BSSID, which is an identifier of BSS.

[0076] The wireless LAN system does not assume anything about the relative physical location of the BSS, and all of the following forms are possible. The BSS may partially overlap, which is a form commonly used to provide continuous coverage. In addition, the BSS may not be physically connected, and logically, there is no limit on the distance between the BSS. In addition, the BSS may be physically located in the same location, which can be used to provide redundancy. In addition, one (or more than one) IBSS or ESS network may physically exist in the same space as one (or more than one) ESS network. When an ad hoc network operates in a location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location, this may correspond to the form of an ESS network, etc.

[0077] Figure 3 is a diagram for explaining a link establishment process to which the present disclosure can be applied.

[0078] In order for a STA to establish a link with respect to a network and send / receive data, it first discovers the network, performs authentication, establishes association, and needs to perform authentication processing for security. The link establishment processing may also be referred to as a session initiation processing or a session establishment processing. In addition, the discovery, authentication, association, and security establishment processing of the link establishment processing may be collectively referred to as an association processing.

[0079] In step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access a network, it needs to find a network that it can participate in. The STA should identify compatible networks before participating in a wireless network, and the process of identifying networks present in a specific area is called scanning.

[0080] Scanning schemes include active scanning and passive scanning. Figure 3The network discovery operation including active scanning processing is exemplarily illustrated. In active scanning, the STA performing the scan sends a probe request frame to discover which APs exist around it while the channel moves and waits for a response thereto. The responder sends a probe response frame as a response to the probe request frame to the STA that has sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. In the BSS, since the AP sends a beacon frame, the AP becomes the responder, and in the IBSS, the STAs in the IBSS rotate to send beacon frames, so the responder is not constant. For example, a STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 may store the BSS-related information included in the received probe response frame, and may move to the next channel (e.g., channel 2), and perform scanning in the same manner (i.e., sending and receiving probe requests / responses on channel 2).

[0081] Although not in Figure 3 , but the scanning operation can be performed in a passive scanning manner. In passive scanning, the STA performing the scan waits for a beacon frame while the channel moves. The beacon frame is one of the management frames defined in IEEE 802.11, and is periodically sent to notify the existence of a wireless network and allow the STA performing the scan to find the wireless network and participate in the wireless network. In the BSS, the AP is used to periodically send beacon frames, and in the IBSS, the STAs within the IBSS rotate to send beacon frames. When the STA performing the scan receives the beacon frame, the STA stores the information of the BSS included in the beacon frame, and records the beacon frame information in each channel while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner. Comparing active scanning with passive scanning, the advantage of active scanning is that it has less delay and less power consumption than passive scanning.

[0082] After the STA discovers the network, an authentication process may be performed at step S320. In order to clearly distinguish from the security establishment operation of step S340 to be described later, this authentication process may be referred to as a first authentication process.

[0083] The authentication process includes the following process: the STA sends an authentication request frame to the AP, and in response thereto, the AP sends an authentication response frame to the STA. The authentication frame for authentication request / response corresponds to a management frame.

[0084] The authentication frame includes an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), a limited cycle group, etc. This corresponds to some examples of information that can be included in the authentication request / response frame, and can be replaced with other information, or additional information can also be included.

[0085] The STA may send an authentication request frame to the AP. The AP may determine whether to allow authentication of the corresponding STA based on the information included in the received authentication request frame. The AP may provide the result of the authentication process to the STA via an authentication response frame.

[0086] After the STA is successfully authenticated, an association process may be performed at step S330. The association process includes the following processes: the STA sends an association request frame to the AP, and in response, the AP sends an association response frame to the STA.

[0087] For example, the association request frame may include information related to various capabilities, a beacon listening interval, a service set identifier (SSID), supported rates, supported channels, RSN, a mobile domain, supported operation categories, a traffic indication map broadcast request (TIM broadcast request), interworking service capabilities, etc. For example, the association response frame may include information related to various capabilities, a status code, an association ID (AID), supported rates, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise ratio indicator (RSNI), a mobile domain, a timeout interval (e.g., an association recovery time), an overlapping BSS scan parameter, a TIM broadcast response, a quality of service (QoS) map, etc. This corresponds to some examples of information that may be included in an association request / response frame, and may be replaced with other information, or may also include additional information.

[0088] After the STA successfully associates with the network, a security establishment process may be performed at step S340. The security establishment process at step S340 may be referred to as an authentication process through a robust security network association (RSNA) request / response, the authentication process at step S320 may be referred to as a first authentication process, and the security establishment process at step S340 may also be referred to simply as an authentication process.

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

[0090] Figure 4 is a diagram for explaining a rollback process to which the present disclosure can be applied.

[0091] In a wireless LAN system, the basic access mechanism of the medium access control (MAC) is a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism is also known as the distributed coordination function (DCF) of the IEEE 802.11 MAC, and basically adopts a "listen before talk" access mechanism. According to this type of access mechanism, before starting to send, the AP and / or STA may perform a clear channel assessment (CCA) of sensing the radio channel or medium during a predetermined time interval (e.g., DCF interframe space (DIFS)). As a result of the sensing, if it is determined that the medium is in an idle state, frame transmission is started through the corresponding medium. On the other hand, if it is detected that the medium is occupied or busy, the corresponding AP and / or STA does not start its own transmission, and a delay period (e.g., a random backoff period) for medium access may be set and frame transmission may be attempted after waiting. By applying a random backoff period, since multiple STAs are expected to attempt frame transmission after waiting for different time periods, conflicts can be minimized.

[0092] In addition, the IEEE 802.11 MAC protocol provides a hybrid coordination function (HCF). HCF is based on DCF and point coordination function (PCF). PCF is a synchronous access method based on polling, and refers to a method in which all receiving APs and / or STAs periodically poll to receive data frames. In addition, HCF has enhanced distributed channel access (EDCA) and HCF controlled channel access (HCCA). EDCA is a contention-based access method that provides data frames to multiple users in a direction, and HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, HCF includes a medium access mechanism for improving the QoS (quality of service) of a wireless LAN, and QoS data can be sent during a contention period (CP) and a contention-free period (CFP).

[0093] refer to Figure 4, the operation based on the random backoff period will be described. When the occupied / busy medium becomes idle, multiple STAs can attempt to send data (or frames). As a method to minimize conflicts, each of the STAs can select a random backoff count respectively and attempt to send after waiting for the corresponding time slot time. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​ranging from 0 to CW. Here, CW is the contention window parameter value. The CW parameter is assigned CWmin as an initial value, but can take a value twice as large as in the case of a transmission failure (for example, when an ACK for the transmitted frame is not received). When the CW parameter value reaches CWmax, data transmission can be attempted while maintaining the CWmax value until the data transmission is successful, and when the data transmission is successful, the CWmin value is reset. The values ​​of CW, CWmin and CWmax are preferably set to 2n-1 (n=0, 1, 2, ...).

[0094] When the random backoff process starts, the STA continuously monitors the medium in the backoff slot countdown according to the determined backoff count value. When the medium is monitored for occupancy, it stops the countdown and waits, and restarts the remaining part of the countdown when the medium becomes idle.

[0095] exist Figure 4 In the example of , when the packet to be sent arrives at the MAC of STA 3, STA3 can send the frame immediately after confirming that the medium has been idle for up to DIFS. The remaining STAs monitor and wait for the medium to be occupied / busy. At the same time, the data to be sent can also occur in each of STA1, STA2 and STA5, and when the medium is monitored as idle, each STA waits for up to DIFS, and then the countdown of the backoff slot can be performed according to the random backoff count value selected by each STA. Assume that STA2 selects the minimum backoff count value and STA1 selects the maximum backoff count value. That is, the example illustrates a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 completes the backoff count and starts frame transmission. STA1 and STA5 temporarily stop the countdown and wait when STA2 occupies the medium. When STA2's occupancy ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and restart the stopped backoff count. That is, frame transmission can start after counting down the remaining backoff slot for the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. The data to be transmitted may also occur in STA4 while STA2 occupies the medium. From the perspective of STA4, when the medium becomes idle, STA4 can wait for DIFS, and then can perform a countdown according to the random backoff count value selected by STA4, and start sending frames. Figure 4The example shows a case where the remaining backoff time of STA5 accidentally collides with the random backoff count value of STA4. In this case, a conflict may occur between STA4 and STA5. When a conflict occurs, neither STA4 nor STA5 receives an ACK, so data transmission fails. In this case, STA4 and STA5 can double the CW value, select a random backoff count value, and perform a countdown. While the medium is occupied due to the transmission of STA4 and STA5, STA1 waits, and when the medium becomes idle, STA1 waits for DIFS, and then starts frame transmission after the remaining backoff time has passed.

[0096] As in Figure 4 In the example of , a data frame is a frame for sending data forwarded to a higher layer, and may be sent after a backoff performed after DIFS has passed since the medium became idle. In addition, a management frame is a frame for exchanging management information that is not forwarded to a higher layer, and is sent after a backoff is performed after an IFS such as DIFS or a point coordination function IFS (PIFS). As subtype frames of the management frame, there are beacons, association request / responses, reassociation request / responses, probe request / responses, authentication request / responses, and the like. A control frame is a frame for controlling access to a medium. As subtype frames of the control frame, there are request to send (RTS), clear to send (CTS), acknowledgment (ACK), power save poll (PS-Poll), block ACK (BlockAck), block ACK request (BlockACKReq), empty data packet announcement (NDP announcement), and trigger, and the like. If the control frame is not a response frame of the previous frame, it is sent after performing a backoff after DIFS, and if it is a response frame of the previous frame, it is sent without performing a backoff after a short IFS (SIFS). The type and subtype of the frame can be identified by the type field and subtype field in the frame control (FC) field.

[0097] Quality of Service (QoS) STA can perform a backoff performed after arbitration IFS (AIFS) (i.e., AIFS [i] (where i is a value determined by AC)) for the access category (AC) to which the frame belongs, and then can send the frame. Here, the frame that can use AIFS [i] may be a data frame, a management frame, or a control frame instead of a response frame.

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

[0099] As described above, in addition to the physical carrier sensing in which the STA directly senses the medium, the CSMA / CA mechanism also includes virtual carrier sensing. Virtual carrier sensing is intended to compensate for problems such as hidden node problems that may occur in medium access. For virtual carrier sensing, the MAC of the STA can use a network allocation vector (NAV). NAV is a value that indicates to other STAs the remaining time until the medium is available for use by the STA that is currently using or has the right to use the medium. Therefore, the value set to NAV corresponds to the period during which the STA sending the frame plans to use the medium, and during the corresponding period, the STA receiving the NAV value is prohibited from accessing the medium. For example, the NAV can be configured based on the value of the "Duration" field of the MAC header of the frame.

[0100] exist Figure 5 In the example of FIG. 1 , it is assumed that STA1 intends to send data to STA2, and STA3 is in a position to be able to eavesdrop on some or all frames sent and received between STA1 and STA2.

[0101] In order to reduce the possibility of transmission conflicts among multiple STAs in the CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames can be applied. Figure 5 In the example of , when STA1's transmission is being performed, as a result of STA3's carrier sensing, it can be determined that the medium is in an idle state. That is, STA1 may correspond to a hidden node with respect to STA3. Alternatively, in Figure 5 In the example of , it can be determined that the carrier sensing result medium of STA3 is in an idle state while the transmission of STA2 is being performed. That is, STA2 may correspond to a hidden node with respect to STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of one of STA1 or STA2 or STAs outside the carrier sensing range of the transmission from STA1 or STA3 may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0102] Specifically, STA1 can determine whether the channel is being used by carrier sensing. In terms of physical carrier sensing, STA1 can determine the channel occupancy idle state based on the energy level or signal correlation detected in the channel. In addition, in terms of virtual carrier sensing, STA1 can use the network allocation vector (NAV) timer to determine the channel occupancy state.

[0103] When the channel is in an idle state during DIFS, STA1 may send an RTS frame to STA2 after performing backoff. When STA2 receives the RTS frame, STA2 may send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0104] If STA3 cannot eavesdrop on the CTS frame from STA2 but can eavesdrop on the RTS frame from STA1, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the RTS frame. Alternatively, if STA3 can eavesdrop on the CTS frame from STA2, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the CTS frame even though STA3 cannot eavesdrop on the RTS frame from STA1. That is, if STA3 can eavesdrop on one or more of the RTS frame or the CTS frame from one or more of STA1 or STA2, STA3 can set the NAV accordingly. When STA3 receives a new frame before the NAV timer expires, STA3 can update the NAV timer using the duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0105] When STA1 receives a CTS frame from STA2, STA1 may send a data frame to STA2 after SIFS, starting from the time point when reception of the CTS frame is completed. When STA2 successfully receives the data frame, STA2 may send an ACK frame to STA1 after SIFS as a response to the data frame. When the NAV timer expires, STA3 may determine whether the channel is being used by carrier sensing. When STA3 determines that the channel is not being used by other terminals during the DIFS period after the NAV timer expires, STA3 may attempt channel access after the contention window (CW) according to the random backoff has passed.

[0106] Figure 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0107] With the help of instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare a MAC PDU (MPDU) to be transmitted. For example, when a command requesting the PHY layer to start transmitting is received from the MAC layer, the PHY layer switches to a transmission mode, and configures information (e.g., data) provided from the MAC layer in the form of a frame and transmits it. In addition, when the PHY layer detects a valid preamble of a received frame, the PHY layer monitors the header of the preamble and transmits a command notifying the start of reception of the PHY layer to the MAC layer.

[0108] In this manner, information transmission / reception in the wireless LAN system is performed in the form of frames, and for this purpose, a PHY layer protocol data unit (PPDU) frame format is defined.

[0109] The basic PPDU frame may include a short training field (STF), a long training field (LTF), a signal (SIG) field, and a data field. The most basic (e.g., non-high throughput (HT)) PPDU frame format may consist of only L-STF (legacy STF), L-LTF (legacy-LTF), a SIG field, and a data field. In addition, depending on the type of PPDU frame format (e.g., HT mixed format PPDU, HT greenfield format PPDU, VHT (very high throughput) PPDU, etc.), additional (or different types of) STF, LTF, and SIG fields may be included between the SIG field and the data field (reference will be made later). Figure 7 Describe this).

[0110] STF is a signal used for signal detection, automatic gain control (AGC), diversity selection, precise time synchronization, etc., and LTF is a signal used for channel estimation and frequency error estimation. STF and LTF can be called signals for synchronization and channel estimation of the OFDM physical layer.

[0111] The SIG field may include a rate field and a length field, etc. The rate field may include information about the modulation and coding rate of the data. The length field may include information about the length of the data. In addition, the SIG field may include a parity bit, a SIG tail bit, etc.

[0112] The data field may include a service (SERVICE) field, a physical layer service data unit (PSDU) and a PPDU tail bit, and may also include padding bits if necessary. Some bits of the service field may be used for synchronization of the descrambler at the receiving end. The PSDU corresponds to the MAC PDU defined in the MAC layer and may include data generated / used in the upper layer. The PPDU tail bit may be used to return the encoder to the 0 state. The padding bit may be used to adjust the length of the data field in predetermined units.

[0113] MAC PDU is defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a frame check sequence (FCS). A MAC frame may consist of a MAC PDU and be transmitted / received through a PSDU of a data portion of a PPDU frame format.

[0114] The MAC header includes a frame control field, a duration / ID field, an address field, etc. The frame control field may include control information required for frame transmission / reception. The duration / ID field may be set to the time for transmitting the corresponding frame, etc. For details of the sequence control, QoS control, and HT control subfields of the MAC header, refer to the IEEE 802.11 standard document.

[0115] The Null Data Packet (NDP) frame format means a frame format that does not include a data packet. That is, the NDP frame refers to a frame format that includes a physical layer convergence procedure (PLCP) header portion (i.e., STF, LTF, and SIG fields) in a common PPDU frame format and does not include the remaining portion (i.e., data field). The NDP frame may also be referred to as a short frame format.

[0116] Figure 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0117] In standards such as IEEE 802.11a / g / n / ac / ax, various types of PPDUs have been used. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and data fields. The basic PPDU format may also be referred to as a non-HT PPDU format.

[0118] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT fields with respect to the basic PPDU format. Figure 7 The HT PPDU format shown in the figure may be referred to as an HT mixed format. In addition, an HT greenfield format PPDU may be defined, and this corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a data field, excluding L-STF, L-LTF, and L-SIG (not shown).

[0119] An example of a VHT PPDU format (IEEE 802.11ac) additionally includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields for the basic PPDU format.

[0120] Examples of HE PPDU formats (IEEE 802.11ax) additionally include repeated L-SIG (RL-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF, and packet extension (PE) fields with respect to the basic PPDU format. According to the detailed examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), while the HE-SIG-B is not included in the HE PPDU format for single user (SU). In addition, the PPDU format based on HE trigger (TB) does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The extended range (HE ER) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us.

[0121] Figures 8 to 10 is a diagram for explaining an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0122] refer to Figures 8 to 10 , a resource unit (RU) defined in a wireless LAN system will be described. A RU may include multiple subcarriers (or tones). When a signal is transmitted to multiple STAs based on an OFDMA scheme, an RU may be used. In addition, an RU may be defined even when a signal is transmitted to one STA. An RU may be used for a data field, an STF, an LTF, etc. of a PPDU.

[0123] like Figures 8 to 10 As shown in , RUs corresponding to different numbers of tones (i.e., subcarriers) are used to construct some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X is HE, EHT, etc.). For example, resources may be allocated in RU units as shown for the X-STF, X-LTF, and data fields.

[0124] Figure 8 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 20 MHz frequency band.

[0125] like Figure 8As shown at the top of , 26-units (i.e., units corresponding to 26 tones) may be allocated. 6 tones may be used as a guard band in the leftmost band of the 20 MHz band, and 5 tones may be used as a guard band in the rightmost band of the 20 MHz band. In addition, 7 DC tones are inserted into the center band (that is, the DC band), and 26-units corresponding to each of the 13 tones may exist on the left and right sides of the DC band. In addition, 26-units, 52-units, and 106-units may be allocated to other bands. Each unit may be allocated for STA or user.

[0126] Figure 8 The RU allocation is used not only for the multi-user (MU) case but also for the single-user (SU) case, and in this case, a 242-unit can be used, such as Figure 8 In this case, three DC tones can be inserted.

[0127] exist Figure 8 In the examples, various sizes of RUs are illustrated, that is, 26-RU, 52-RU, 106-RU, 242-RU, etc., but the specific sizes of these RUs can be reduced or expanded. Therefore, in the present disclosure, the specific size of each RU (i.e., the number of corresponding tones) is exemplary and not restrictive. In addition, within a predetermined bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, ...) in the present disclosure, the number of RUs can vary according to the size of the RU. In the following description, Fig. 9 and / or Fig.10 The fact that the size and / or number of RUs can vary is related to Figure 8 The same example.

[0128] Fig. 9 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 40 MHz frequency band.

[0129] As in Figure 8 As in the example using various RU sizes, you can also Fig. 9 In the example of , 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. are used. 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.

[0130] Additionally, as shown, when used for a single user, a 484-RU may be used.

[0131] Fig.10 is a diagram illustrating exemplary allocation of resource units (RUs) used on an 80 MHz frequency band.

[0132] As in Figure 8 and Fig. 9 As in the example using various RU sizes, you can also Fig.10 In the example of 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. are used. In addition, in the case of 80MHz PPDU, the RU allocation of HE PPDU and EHT PPDU can be different, and Fig.10 The example of FIG. 4 shows an example of RU allocation for an 80 MHz EHT PPDU. Fig.10 The scheme in which 12 tones in the example are used as a guard band in the leftmost band of the 80 MHz band and 11 tones are used as a guard band in the rightmost band of the 80 MHz band is the same as in the HE PPDU and the EHT PPDU. Unlike the HE PPDU in which 7 DC tones are inserted in the DC band and there is a 26-RU corresponding to each of the 13 tones on the left and right sides of the DC band, in the EHT PPDU, 23 DC tones are inserted in the DC band and there is a 26-RU on the left and right sides of the DC band. Unlike the HE PPDU in which one empty subcarrier exists between the 242-RUs instead of the center band, there are five empty subcarriers in the EHT PPDU. In the HE PPDU, one 484-RU does not include an empty subcarrier, but in the EHT PPDU, one 484-RU includes 5 empty subcarriers.

[0133] Additionally, as shown, when used for a single user, 996-RU may be used, and in this case, 5 DC tones are inserted as with HEPPDU and EHT PPDU.

[0134] exist Fig.10 In the example, the EHT PPDU on 160MHz can be configured with multiple 80MHz sub-blocks. The RU allocation for each 80MHz sub-block can be the same as Fig.10 If the 80 MHz sub-block of a 160 MHz or 320 MHz EHT PPDU is not punctured and the entire 80 MHz sub-block is used as a RU or part of a multiple RU (MRU), the 80 MHz sub-block can be used Fig.10 The 996-RU.

[0135] Here, the MRU corresponds to a group of subcarriers (or tones) consisting of multiple RUs, and the multiple RUs constituting the MRU may be RUs of the same size or RUs of different sizes. For example, a single MRU may be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2×996+484-tones, 3×996-tones, or 3×996+484-tones. Here, the multiple RUs constituting one MRU may correspond to a small size (e.g., 26, 52, or 106) RU or a large size (e.g., 242, 484, or 996) RU. That is, one MRU including a small size RU and a large size RU may not be configured / defined. In addition, the multiple RUs constituting one MRU may be continuous in the frequency domain, or may not be continuous.

[0136] When an 80 MHz sub-block includes RUs less than 996-tones or a portion of the 80 MHz sub-block is punctured, the 80 MHz sub-block may use RU allocations other than the 996-tone RUs.

[0137] The RU of the present disclosure may be used for uplink (UL) and / or downlink (DL) communication. For example, when trigger-based UL-MU communication is performed, the STA (e.g., AP) that sends the trigger may allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA through trigger information (e.g., a trigger frame or a trigger response schedule (TRS)), and allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. Thereafter, the first STA may send a first trigger-based (TB) PPDU based on the first RU, and the second STA may send a second TB PPDU based on the second RU. The first / second TB PPDU may be sent to the AP in the same time period.

[0138] For example, when a DL MU PPDU is configured, the STA (e.g., AP) that transmits the DL MU PPDU may allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA, and allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit the HE-STF, HE-LTF, and data fields for the first STA through the first RU in one MU PPDU, and transmit the HE-STF, HE-LTF, and data fields for the second STA through the second RU.

[0139] Information about the allocation of RUs may be signaled in HE PPDU format through HE-SIG-B.

[0140] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0141] As shown, the HE-SIG-B field may include common fields and user-specific fields. If HE-SIG-B compression is applied (e.g., full bandwidth MU-MIMO transmission), the common fields may not be included in the HE-SIG-B, and the HE-SIG-B content channel may include only user-specific fields. If HE-SIG-B compression is not applied, the common fields may be included in the HE-SIG-B.

[0142] The common field may include information about RU allocation (eg, RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.).

[0143] The common field may include N*8 RU allocation subfields. Here, N is the number of subfields, N=1 in the case of 20 or 40MHz MU PPDU, N=2 in the case of 80MHz MU PPDU, N=4 in the case of 160MHz or 80+80MHz MU PPDU, and so on. An 8-bit RU allocation subfield may indicate the size (26, 52, 106, etc.) and frequency position (or RU index) of the RU included in the 20MHz band.

[0144] For example, if the value of the 8-bit RU Allocation subfield is 00000000, this may indicate that Figure 8 In the example, nine 26-RUs are allocated in sequence from the leftmost side to the rightmost side, if the value is 00000001, this may indicate that seven 26-RUs and one 52-RU are allocated in sequence from the leftmost side to the rightmost side, and if the value is 00000010, this may indicate that five 26-RUs, one 52-RU, and two 26-RUs are allocated in sequence from the leftmost side to the rightmost side.

[0145] As an additional example, if the value of the 8-bit RU Allocation subfield is 01000y2y1y0, this may indicate that Figure 8 In the example, one 106-RU and five 26-RUs are allocated from the leftmost to the rightmost. In this case, in the MU-MIMO scheme, multiple users / STAs can be allocated to the 106-RU. Specifically, up to 8 users / STAs can be allocated to the 106-RU, and the number of users / STAs allocated to the 106-RU is determined based on the 3-bit information (i.e., y2y1y0). For example, when the 3-bit information (y2y1y0) corresponds to a decimal value N, the number of users / STAs allocated to the 106-RU can be N+1.

[0146] Basically, one user / STA can be assigned to each of multiple RUs, and different users / STAs can be assigned to different RUs. For RUs larger than a predetermined size (e.g., 106, 242, 484, 996-tones, ...), multiple users / STAs can be assigned to one RU, and the MU-MIMO scheme can be applied to multiple users / STAs.

[0147] The set of user-specific fields includes information about how all users (STAs) of the corresponding PPDU decode their payloads. The user-specific field may contain zero or more user block fields. The non-end-user block field includes two user fields (ie, information to be used for decoding in two STAs). The end-user block field contains one or two user fields. The number of user fields may be indicated by the RU allocation subfield of the HE-SIG-B, the number of symbols of the HE-SIG-B, or the MU-MIMO user field of the HE-SIG-A. The user-specific field may be encoded separately from the common field or independently of the common field.

[0148] Fig.12 is a diagram for explaining a MU-MIMO method in which multiple users / STAs are assigned to one RU.

[0149] exist Fig.12 In the example, assume that the value of the RU allocation subfield is 01000010. This corresponds to the case where y2y1y0=010 in 01000y2y1y0. 010 corresponds to 2 in decimal (i.e., N=2) and may indicate that 3 (=N+1) users are allocated to one RU. In this case, one 106-RU and five 26-RUs may be allocated sequentially from the leftmost to the rightmost of a specific 20 MHz band / channel. Three users / STAs may be allocated to the 106-RU in MU-MIMO manner. As a result, a total of 8 users / STAs are allocated to the 20 MHz band / channel, and the user-specific field of the HE-SIG-B may include 8 user fields (i.e., 4 user block fields). Eight user fields may be assigned to an RU, such as Fig.12 shown.

[0150] The user field may be constructed based on two formats. The user field for MU-MIMO allocation may be constructed in a first format, and the user field for non-MU-MIMO allocation may be constructed in a second format. Fig.12 For example, user fields 1 to 3 may be based on a first format, and user fields 4 to 8 may be based on a second format. The first format and the second format may contain bit information of the same length (eg, 21 bits).

[0151] The user field of the first format (i.e., the format allocated for MU-MIMO) may be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B14 include spatial configuration information such as the number of spatial streams of the corresponding user, B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 is defined as a reserved field, and B20 may include information about the coding type (e.g., binary convolutional coding (BCC) or low-density parity check (LDPC)) applied to the data field of the corresponding PPDU.

[0152] The user field of the second format (i.e., the format for non-MU-MIMO allocation) can be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B13 include information about the number of spatial streams (NSTS) applied to the corresponding RU, B14 includes information indicating whether beamforming is performed (or whether a beamforming control matrix is ​​applied), B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 includes information indicating whether DCM (dual carrier modulation) is applied, and B20 may include information about the coding type (e.g., BCC or LDPC) applied to the data field of the corresponding PPDU.

[0153] The MCS, MCS information, MCS index, MCS field, etc. used in the present disclosure may be indicated by a specific index value. For example, the MCS information may be indicated as index 0 to index 11. The MCS information includes information about the constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). Information about the channel coding type (e.g., BCC or LDPC) may be excluded from the MCS information.

[0154] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0155] Fig.13The PPDU of the present disclosure may be referred to as various names such as EHT PPDU, transmitted PPDU, received PPDU, first type or Nth type PPDU. For example, the PPDU or EHT PPDU of the present disclosure may be referred to as various names such as transmitted PPDU, received PPDU, first type or Nth type PPDU. In addition, the EHT PPU may be used in an EHT system and / or a new wireless LAN system in which the EHT system is improved.

[0156] Fig.13 The EHT MU PPDU corresponds to a PPDU carrying one or more data (or PSDU) for one or more users. That is, the EHT MU PPDU can be used for SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0157] exist Fig.13 In the EHT TB PPDU, the EHT-SIG is omitted compared to the EHT MU PPDU. Upon receiving a trigger for ULMU transmission (eg, a trigger frame or TRS), the STA may perform UL transmission based on the EHT TB PPDU format.

[0158] exist Fig.13 In the example of the EHT PPDU format, L-STF to EHT-LTF correspond to a preamble or a physical preamble and can be generated / transmitted / received / acquired / decoded in a physical layer.

[0159] The subcarrier frequency spacing of the L-STF, L-LTF, L-SIG, RL-SIG, Universal Signal (U-SIG), EHT-SIG fields (these are called pre-EHT modulation fields) can be set to 312.5kHz. The subcarrier frequency spacing of the EHT-STF, EHT-LTF, data and PE fields (these are called EHT modulation fields) can be set to 78.125kHz. That is, the tone / subcarrier index of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG and EHT-SIG fields can be indicated in units of 312.5kHz, and the tone / subcarrier index of the EHT-STF, EHT-LTF, data and PE fields can be indicated in units of 78.125kHz.

[0160] Fig.13 The L-LTF and L-STF can be used with Figure 6 to Figure 7 The corresponding fields of the PPDU described in are constructed identically.

[0161] Fig.13The L-SIG field may consist of 24 bits and may be used to transmit rate and length information. For example, the L-SIG field includes a 4-bit rate field, a 1-bit reserved bit, a 12-bit length field, a 1-bit parity field, and a 6-bit tail field. For example, the 12-bit length field may include information about the duration or length of the PPDU. For example, the value of the 12-bit length field may be determined based on the type of the PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the length field may be determined as a multiple of 3. For example, for HE PPDUs, the value of the length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0162] For example, the transmitting STA may apply BCC encoding based on the coding rate of 1 / 2 to 24 bits of information of the L-SIG field. Thereafter, the transmitting STA may obtain 48 BCC coded bits. BPSK modulation may be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to any position except the pilot subcarrier (e.g., {subcarrier index -21, -7, +7, +21}) and the DC subcarrier (e.g., {subcarrier index 0}). As a result, the 48 BPSK symbols may be mapped to subcarrier indexes -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

[0163] The transmitting STA can construct the RL-SIG with the same structure as the L-SIG. BPSK modulation is applied to the RL-SIG. Based on the existence of the RL-SIG, the receiving STA can identify whether the received PPDU is a HE PPDU or an EHT PPDU.

[0164] exist Fig.13 After the RL-SIG, a universal SIG (U-SIG) may be inserted. The U-SIG may be referred to by various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, and a first (type) control signal.

[0165] The U-SIG may include N bits of information and may include information for identifying the EHT PPDU type. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol of the U-SIG (e.g., OFDM symbol) may have a duration of 4us, and the U-SIG may have a total duration of 8us. Each symbol of the U-SIG may be used to send 26 bits of information. For example, each symbol of the U-SIG may be sent and received based on 52 data tones and 4 pilot tones.

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

[0167] For example, the A-bit information (e.g., 52 uncoded bits) sent by the U-SIG includes a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit length field). The CRC field and the tail field may be sent through the second symbol of the U-SIG. The CRC field may be constructed based on the 26 bits of the first symbol allocated to the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be constructed based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder, and, for example, the tail field may be set to 0.

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

[0169] For example, the version-independent bit of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier). For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted / received PPDU. For example, the first value of the 3-bit PHY version identifier may indicate that the transmitted / received PPDU is an EHT PPDU. In other words, when transmitting an EHT PPDU, the transmitting STA may set the 3-bit PHY version identifier to a first value. In other words, the receiving STA may determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value.

[0170] For example, the version-independent bits of the U-SIG may include a 1-bit UL / DL flag field. A first value of the 1-bit UL / DL flag field is associated with UL communication, and a second value of the UL / DL flag field is associated with DL communication.

[0171] For example, the version-independent bits of the U-SIG may include information about a transmit opportunity length (TXOP) and information about a BSS color ID.

[0172] For example, if the EHT PPDU is classified into various types (e.g., EHT PPDU associated with SU mode, EHT PPDU associated with MU mode, EHT PPDU associated with TB mode, EHT PPDU associated with extended range transmission, etc.), information about the EHT PPDU type may be included in the version-related bit of the U-SIG.

[0173] For example, U-SIG may include information about the following items: 1) a bandwidth field containing information about the bandwidth, 2) a field containing information about the MCS scheme applied to the EHT-SIG, 3) an indication field containing information related to whether the DCM technology is applied to the EHT-SIG, 4) a field containing information about the number of symbols used for the EHT-SIG, 5) a field containing information about whether the EHT-SIG is constructed on all frequency bands, 6) a field containing information about the type of EHT-LTF / STF, and 7) a field indicating the EHT-LTF length and the CP length.

[0174] Can Fig.13 Preamble puncturing is applied to the PPDU of the primary 20MHz band. Preamble puncturing refers to applying puncturing to some frequency bands (e.g., the secondary 20MHz band) among all frequency bands of the PPDU. For example, when sending an 80MHz PPDU, the STA can apply puncturing to the secondary 20MHz band of the 80MHz band and send the PPDU only through the primary 20MHz band and the secondary 40MHz band.

[0175] For example, a pattern of preamble puncturing may be preconfigured. For example, when the first puncturing pattern is applied, puncturing may be applied only to an auxiliary 20 MHz band within the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing may be applied only to either of the two auxiliary 20 MHz bands in the auxiliary 40 MHz band included in the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing may be applied only to an auxiliary 20 MHz band in the main 80 MHz band included in the 160 MHz band (or the 80 MHz + 80 MHz band). For example, when the fourth puncturing pattern is applied, there is a main 40 MHz band in the main 80 MHz band included in the 160 MHz band (or the 80 MHz + 80 MHz band), and puncturing may be applied to at least one 20 MHz channel that does not belong to the main 40 MHz band.

[0176] Information about the preamble puncturing applied to the PPDU may be included in the U-SIG and / or the EHT-SIG. For example, the first field of the U-SIG may include information about the continuous bandwidth of the PPDU, and the second field of the U-SIG may include information about the preamble puncturing applied to the PPDU.

[0177] For example, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be independently constructed 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 a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG includes information about the 160 MHz bandwidth, and the second field of the first U-SIG includes information about the preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). In addition, the first field of the second U-SIG includes information about the 160 MHz bandwidth, and the second field of the second U-SIG includes information about the preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). The EHT-SIG after the first U-SIG may include information about preamble puncturing applied to the second 80 MHz frequency band (i.e., information about the preamble puncturing pattern), and the EHT-SIG after the second U-SIG may include information about preamble puncturing applied to the first 80 MHz frequency band (i.e., information about the preamble puncturing pattern).

[0178] Additionally or alternatively, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. The U-SIG may include information about preamble puncturing of all bands (ie, information about a preamble puncturing pattern). That is, the EHT-SIG does not include information about preamble puncturing, and only the U-SIG may include information about preamble puncturing (ie, information about a preamble puncturing pattern).

[0179] The U-SIG can be constructed in units of 20MHz. For example, if an 80MHz PPDU is constructed, the U-SIG can be duplicated. That is, the same 4 U-SIGs can be included in the 80MHz PPDU. PPDUs with bandwidths exceeding 80MHz can include different U-SIGs.

[0180] Fig.13 The EHT-SIG may include control information for the receiving STA. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4us. Information on the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0181] The EHT-SIG may include Fig.11 and Fig.12 The technical features of HE-SIG-B are described. For example, Figure 8As in the example of , the EHT-SIG may include a common field and a user-specific field. The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0182] As in Fig.11 As in the example of , the common field of EHT-SIG and the user-specific field of EHT-SIG can be encoded separately. One user block field included in the user-specific field can contain information for two user fields, but the last user block field included in the user-specific field can contain one or two user fields. That is, one user block field of EHT-SIG can contain up to two user fields. As in Fig.12 As in the example of , each user field may be associated with a MU-MIMO allocation or a non-MU-MIMO allocation.

[0183] With Fig.11 In the same manner as in the example of , the common field of the EHT-SIG may include a CRC bit and a tail bit. The length of the CRC bit may be determined as 4 bits, and the length of the tail bit may be determined as 6 bits and may be set to 000000.

[0184] As in Fig.11 As in the example of , the common field of EHT-SIG may include RU allocation information. The RU allocation information may be information about the locations of RUs to which multiple users (ie, multiple receiving STAs) are allocated. The RU allocation information may be configured in units of 8 bits (or N bits).

[0185] A mode in which the common field of the EHT-SIG is omitted may be supported. A mode in which the common field of the EHT-SIG is omitted may be referred to as a compressed mode. When the compressed mode is used, multiple users of the EHT PPDU (ie, multiple receiving STAs) may decode the PPDU (eg, the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) received via the same frequency band. When the non-compressed mode is used, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU may receive the PPDU (eg, the data field of the PPDU) via different frequency bands.

[0186] The EHT-SIG may be constructed based on various MCS schemes. As described above, information related to the MCS scheme applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be constructed based on the DCM scheme. For example, a first modulation technique may be applied to a continuous half tone (e.g., the 1st to 26th tones) of N data tones (e.g., 52 data tones) allocated for the EHT-SIG, and a second modulation technique may be applied to the remaining continuous half tones. In other words, the transmitting STA may modulate specific control information into a first symbol based on a first modulation technique and assign it to continuous half tones, and may modulate the same control information into a second symbol based on a second modulation technique and assign it to the remaining continuous half tones. As described above, information related to whether the DCM scheme is applied to the EHT-SIG (e.g., a 1-bit field) may be included in the U-SIG. Fig.13 The EHT-STF can be used to enhance automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment. Fig.13 The EHT-LTF can be used to estimate channels in a MIMO environment or an OFDMA environment.

[0187] Information about the type of STF and / or LTF (including information about a guard interval (GI) applied to LTF) may be included in Fig.13 The U-SIG field and / or EHT-SIG field of the RFID tag may be used.

[0188] Can be based on Figures 8 to 10 Example construction of RU allocation Fig.13 PPDU (ie, EHT PPDU).

[0189] For example, based on Figure 8 The RU constructs an EHT PPDU to be sent on the 20 MHz band, that is, a 20 MHz EHT PPDU. Figure 8 As shown in , the RU positions of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU can be determined. Fig. 9 The RU constructs an EHT PPDU to be sent on the 40 MHz band, that is, a 40 MHz EHT PPDU. Fig. 9 As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined.

[0190] Can be based on Fig.10 The RU constructs an EHT PPDU to be sent on the 80 MHz band, that is, an 80 MHz EHT PPDU. Fig.10As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined. Fig.10 The tone plan for 80 MHz in may correspond to Fig. 9 Two repetitions of the tone plan for 40 MHz.

[0191] The tone plan for 160 / 240 / 320MHz can be repeated multiple times Fig. 9 or Fig.10 The mode is configured in the form of.

[0192] Fig.13 A PPDU can be identified as an EHT PPDU based on the following method.

[0193] The receiving STA may determine the type of the received PPDU as an EHT PPDU based on the following. For example, when 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) the RL-SIG that repeats the L-SIG of the received PPDU is detected, and 3) the result of applying the modulo 3 calculation to the value of the length field of the L-SIG of the received PPDU (i.e., the remainder after division by 3) is detected as 0, the received PPDU may be determined to be an EHT PPDU. When the received PPDU is determined to be an EHT PPDU, the receiving STA may determine the type of the received PPDU as an EHT PPDU based on Fig.13 In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol (BSPK) after the L-LTF signal, 2) the RL-SIG that is adjacent to the L-SIG field and is the same as the L-SIG, and 3) the L-SIG including the length field in which the result of applying modulo 3 is set to 0.

[0194] For example, the receiving STA may determine the type of the received PPDU as the HE PPDU based on the following: For example, when 1) the first symbol after the L-LTF signal is BPSK, 2) the RL-SIG repeating the L-SIG is detected, and 3) the result of applying modulo 3 to the length value of the L-SIG is detected as 1 or 2, the received PPDU may be determined as the HE PPDU.

[0195] For example, the receiving STA may determine the type of the received PPDU as non-HT, HT, and VHT PPDU based on the following. For example, when 1) the first symbol after the L-LTF signal is BPSK and 2) the RL-SIG that repeats the L-SIG is not detected, the received PPDU may be determined as non-HT, HT, and VHT PPDU. In addition, although the receiving STA detects the repetition of the RL-SIG, when it is detected that the result of applying modulo 3 to the length value of the L-SIG is 0, the received PPDU may be determined as non-HT, HT, and VHT PPDU.

[0196] Fig.13 The PPDU can be used to send and receive various types of frames. For example, Fig.13 The PPDU can be used to (simultaneously) send and receive one or more of control frames, management frames, or data frames.

[0197] Hereinafter, a target wake time (TWT) is described.

[0198] TWT is a power saving (PS) technology that can improve the energy efficiency of non-AP STAs by defining the service period (SP) between the AP and the non-AP STA and sharing information about the SP with each other to reduce media contention. The STA that performs a request / suggestion / demand, etc. in the TWT establishment step may be referred to as a TWT requesting STA. In addition, the AP that responds to the corresponding request (e.g., acceptance / rejection, etc.) may be referred to as a TWT responding STA. The establishment step may include a TWT request for the AP of the STA, the type of TWT operation performed, and a process for determining / defining the type of frame sent or received. TWT operations can be divided into separate TWT and broadcast TWT.

[0199] Fig.14 is a diagram for describing an example of a separate TWT operation to which the present disclosure can be applied.

[0200] Separate TWT is a mechanism for the AP and non-AP STA to perform data exchange after performing negotiation for the non-AP STA in the awake / sleep state through the transmission or reception of TWT request / response frames. Fig.14In the example of , AP and STA1 can form a trigger-enabled TWT agreement through a TWT request frame and a TWT response frame. Here, the method used by STA1 is a requested TWT method, which is a method as follows: when STA1 sends a TWT request frame to the AP, STA1 receives information for TWT operation from the AP through a TWT response frame. On the other hand, STA2, which performs an unsolicited TWT method, can receive information about the trigger-enabled TWT agreement configuration from the AP through an unsolicited TWT response. Specifically, STA2 can calculate the next TWT by adding a specific number from the current TWT value. During the triggered-enabled TWT SP, the AP can send a trigger frame to the STA. The trigger frame can notify the STA that the AP has buffered the data. In response to this, STA1 can notify the AP of its wake-up state by sending a PS-poll frame. In addition, STA2 can notify the AP of its wake-up state by sending a QoS empty frame. Here, the data frame sent by STA1 and STA2 can be a frame in the form of a TB PPDU. The AP that confirms the status of STA1 and STA2 can send a DL MU PPDU to wake up the STA. When the corresponding TWT SP expires, STA1 and STA2 may switch to the sleep state.

[0201] Fig.15 is a diagram for describing an example of a broadcast TWT operation to which the present disclosure may be applied.

[0202] Broadcast TWT is a TWT in which a non-AP STA (or TWT scheduling STA) obtains information about the target beacon transmission time (TBTT) and the listening interval by sending or receiving TWT request / response frames using an AP (or a STA scheduled by TWT). Here, a negotiation operation for TBTT can be performed. Based on this, the AP can define a frame that will include the scheduling information of the TWT through a beacon frame. Fig.15 In the broadcast TWT, STA1 performs requested TWT operation and STA2 performs unsolicited TWT operation. The AP can send a DL MU PPDU after confirming the wake-up state of the STA through a trigger sent by the AP. It can be the same as the process of a separate TWT. In a broadcast TWT, the triggered enabled TWT SP including a beacon frame can be repeated multiple times at a specific interval.

[0203] The transmission of TWT information can be performed through TWT information frames and TWT information elements.

[0204] Fig.16 is a diagram for describing an example of the TWT information element format.

[0205] The TWT information frame is sent by a STA to request or transfer information about a TWT appointment, and is sent by one of the STAs in an existing TWT appointment. The action frame of the TWT information frame includes a TWT information field. The TWT information field may include a 3-bit TWT stream identifier subfield, a 1-bit response request subfield, a 1-bit next TWT request subfield, a 2-bit next TWT subfield size subfield, a 1-bit full TWT subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0206] The size of the TWT information field is variable according to the size of the next TWT field. The TWT stream identifier subfield includes an identifier of the TWT stream that requests or provides TWT information. When the value of all TWT subfields is 1, the TWT stream identifier subfield can be reserved.

[0207] The response request subfield may indicate whether the STA sending the frame including the TWT information field requests to send a TWT information frame in response to the corresponding frame. When the response request subfield is configured to 0, the receiving STA may be requested not to send a TWT information frame in response to the corresponding frame. When the response request subfield is configured to 1, the receiving STA may be requested to send a TWT information frame in response to the corresponding frame.

[0208] When the Next TWT Request subfield is configured to 1, it may indicate that the TWT Infoframe is a request for delivering a TWT Infoframe including a Next TWT field of non-zero length. Otherwise, the Next TWT Request subfield may be configured to 0.

[0209] When the value of the Next TWT Subfield Size subfield is 0, 1, 2, and 3, it may indicate that the size of the next TWT subfield is 0, 32, 48, and 64, respectively.

[0210] When all TWT subfields are configured to 1, it may indicate that the TWT information frame reschedules all TWTs. Otherwise, all TWT subfields may be configured to 0.

[0211] The next TWT subfield may have a variable length according to the value of the next TWT subfield size. The value included in the next TWT subfield may have a value corresponding to the least significant portion of the timing synchronization function (TSF) in the next TWT for the TWT specified by the TWT stream identifier subfield.

[0212] Fig.17 is a diagram for describing an example of the TWT information element format.

[0213] The TWT information element may be transmitted or received by being included in a beacon, a probe response, a (re)association response frame, etc. The TWT information element may include an element ID field, a length field, a control field, and a TWT parameter information field.

[0214] Regardless of individual TWTs and broadcast TWTs, the control field of the TWT information element has the same format.

[0215] The NDP Paging Indication subfield may have a value of 1 when the NDP Paging field is present, and may have a value of 0 when the NDP Paging field is not present.

[0216] The responder PM mode subfield may indicate a power management (PM) mode.

[0217] The negotiation type subfield may indicate whether the information included in the TWT element is about the negotiation of a broadcast TWT or a separate TWT or about a wake-up TBTT interval.

[0218] For example, when the value of the negotiation type subfield is 0, the TWT subfield is about a future separate TWT SP start time, and the TWT element includes a separate TWT parameter set. This can correspond to a separate TWT negotiation between a TWT requesting STA and a TWT responding STA, or it can correspond to a separate TWT announcement by a TWT responder.

[0219] For example, when the value of the negotiation type subfield is 1, the TWT subfield is about the next TBTT time, and the TWT element includes a separate TWT parameter set. This can correspond to waking up the TBTT and the wake-up interval negotiation between the TWT-scheduled STA and the TWT-scheduled AP.

[0220] For example, when the value of the negotiation type subfield is 2, the TWT subfield is about the future broadcast TWT SP start time, and the TWT element includes at least one broadcast TWT parameter set. This can correspond to providing a broadcast TWT schedule to a TWT-scheduled STA by including the TWT element in a broadcast management frame sent by the TWT scheduling AP.

[0221] For example, when the value of the negotiation type subfield is 3, the TWT subfield is about the future broadcast TWT SP start time, and the TWT element includes at least one broadcast TWT parameter set. This can correspond to managing the membership of the broadcast TWT schedule by including the TWT element in a separately addressed management frame sent by either a TWT-scheduled STA or a TWT-scheduled AP.

[0222] When the TWT information frame disable subfield is configured to 1, this means that the STA's reception of the TWT information frame is disabled, otherwise, it can be configured to 0.

[0223] The wakeup duration unit subfield indicates the unit of the nominal minimum TWT wakeup duration field. When the unit is 256us, the wakeup duration unit subfield may be configured to 0, and when the unit is TU, the wakeup duration unit subfield may be configured to 1. When it is not a HE / EHT STA, the wakeup duration unit subfield may be configured to 0.

[0224] The most significant bit (MSB) of the negotiation type field may correspond to the broadcast field. When the broadcast field is 1, at least one broadcast TWT parameter set may be included in the TWT element. When the broadcast field is 0, only a single TWT parameter set may be included in the TWT element. A TWT element with the broadcast field configured as 1 may be referred to as a broadcast TWT element.

[0225] Fig.18 is a diagram for describing an example of the format of individual TWT parameter set fields. Fig.19 is a diagram used to describe an example of the broadcast TWT parameter set field format.

[0226] Included in Fig.17 The TWT parameter information field in the TWT element in may have different configurations depending on individual TWT or broadcast TWT.

[0227] For an individual TWT, the TWT parameter information field in the TWT element includes a single individual TWT parameter set field.

[0228] For broadcast TWT, the TWT parameter information field in the TWT element includes at least one broadcast TWT parameter set field. Each broadcast TWT parameter set may include specific information about one broadcast TWT.

[0229] like Fig.18 and Fig.19 As shown, the individual TWT parameter set field and the broadcast TWT parameter set field include common subfields.

[0230] The request type subfield has the same size in the separate TWT parameter set field and the broadcast TWT parameter set field, but may have different detailed configurations. This will be described later.

[0231] The Target Wake-up Time subfield indicates the future expected start time of a single / broadcast TWT SP.

[0232] The Nominal Minimum TWT Wake-up Duration subfield indicates the minimum unit expected to wake up the TWT requesting STA to complete the frame exchange associated with the TWT stream identifier during the TWT wake-up interval duration. Here, the TWT wake-up interval may mean the average time between consecutive TWT SPs expected by the TWT requesting STA.

[0233] The TWT wakeup interval mantissa subfield is a binary value of the TWT wakeup interval value, which can be indicated in microseconds.

[0234] Reference Fig.18 , the TWT group assignment subfield, TWT channel and NDP paging subfield are included only in a separate TWT parameter set field.

[0235] The TWT group assignment subfield is provided to the TWT requesting STA by including information about the TWT group to which the STA is assigned. The TWT value in the TWT group can be calculated by using the corresponding information. The TWT value of the STA can be the same as the value obtained by multiplying the value of the zero offset and the value of the TWT offset by the value of the TWT unit.

[0236] The TWT channel subfield represents a bitmap indicating allowed channels. When sent by a TWT requesting STA, the TWT channel subfield may include a bitmap indicating channels requested by the STA to be used as temporary basic channels during the TWT SP. When sent by a TWT responding STA, the TWT channel subfield may include a bitmap indicating channels for which the TWT request is allowed.

[0237] The NDP paging subfield is optional and may include an identifier of the STA being paged, information related to the maximum number of TWT wake-up intervals between NDP paging frames, and the like.

[0238] Reference Fig.19 , the broadcast TWT info subfield is only included in the broadcast TWT parameter set field. The broadcast TWT info subfield may include 3 reserved bits, a 5-bit broadcast TWT identifier (ID) subfield, and an 8-bit broadcast TWT persistence subfield. The broadcast TWT identifier subfield indicates the broadcast ID of a specific broadcast TWT for which the STA requests to participate or provide TWT parameters according to the value of the TWT establishment command subfield of the TWT element. The broadcast TWT persistence subfield indicates the number of TBTTs planned on the schedule of the broadcast TWT.

[0239] Next, the detailed configuration of the request type subfield is described.

[0240] First, by referring to Fig.18 To describe the format of the request type subfield of a single TWT parameter set field.

[0241] The TWT request subfield may indicate whether it is a requesting STA or a responding STA. When the value is 1, it may indicate that it is a TWT requesting STA or a scheduling STA, and when the value is 0, it may indicate that it is a TWT responding STA or a scheduling AP.

[0242] The TWT establishment command subfield can represent commands such as request, suggestion, demand, accept, replace, instruct, reject, etc.

[0243] The trigger subfield indicates whether a trigger frame will be used in the TWT SP. When the value is 1, the trigger may be used, and when the value is 0, the trigger may not be used.

[0244] The implicit subfield can indicate whether it is an implicit TWT or an explicit TWT. When the value is 1, this can indicate an implicit TWT, and when the value is 0, this can indicate an explicit TWT.

[0245] The Stream Type subfield may indicate the type of interaction between a TWT requesting STA (or a TWT scheduled STA) and a TWT responding STA (or a TWT scheduling AP). When the value is 1, this may mean an announced TWT: the STA sends a wake-up signal to the AP by sending a PS-poll or an automatic power saving delivery (APSD) trigger frame before sending a frame from the AP to the STA instead of a trigger frame. When the value is 0, this may mean an unannounced TWT.

[0246] The TWT stream identifier subfield may include a 3-bit value that uniquely identifies specific information about a corresponding TWT request among other requests performed between the same TWT requesting STA and TWT responding STA pair.

[0247] The TWT wakeup interval index subfield may configure the TWT wakeup interval value in binary microsecond units. For a single TWT, this may mean the interval between single TWT SPs. The TWT wakeup interval of the requesting STA may be defined as [TWT wakeup interval mantissa * 2 * TWT wakeup interval index].

[0248] The TWT protection subfield may indicate whether the TWT protection mechanism is used. When the value is 1, the TXOP in the TWT SP may start with a NAV protection mechanism (e.g., (MU)RTS / CTS or CTS-to-self frame), and when the value is 0, the NAV protection mechanism may not be applied.

[0249] Reference Fig.19 , some subfields of the request type subfield of the broadcast TWT parameter set field are common with the subfields of the request type subfield of the separate TWT parameter set field, so their description is omitted. The following describes only the subfields included in the broadcast TWT parameter set.

[0250] The last broadcast parameter set subfield indicates whether it is the last broadcast TWT parameter set. When the value is 1, it may indicate that it is the last broadcast TWT parameter set, and when the value is 0, it may indicate that there is a next broadcast TWT parameter set.

[0251] The Broadcast TWT Recommendation subfield may represent the recommendation for the frame type sent by the AP during the Broadcast TWT SP as a value of 1-7.

[0252] The last 1 bit of the request type subfield of the broadcast TWT parameter set field can be reserved.

[0253] Method for configuring TWT information related to restricted TWT

[0254] With the recent explosive growth of wired / wireless services, delay-sensitive services have also increased significantly. Delay-sensitive services include real-time audio / video transmission, and with the expansion of multimedia devices, the need to support them in a wireless environment increases. However, compared with a wired environment, many things need to be considered in a wireless environment to support delay-sensitive services. This is because the transmission speed in a wireless environment is lower than that in a wired environment, and interference issues from the surrounding environment should also be considered. Specifically, in a WLAN system, multiple STAs should equally compete to occupy the medium in the Industrial Scientific Medical (ISM) band, so supporting delay-sensitive services is relatively more difficult than in a cellular communication network based on radio resource scheduling of a central base station. The present disclosure describes a new method for supporting delay-sensitive services in a WLAN system.

[0255] In the present disclosure, latency may mean latency defined in the IEEE802.11 series of standards. For example, latency may refer to the time until: after a frame to be sent enters the queue of the MAC layer of the sending STA, the sending of the sending STA ends successfully at the PHY layer, the sending STA receives ACK / block ACK, etc. from the receiving STA, and the corresponding frame is deleted from the queue of the MAC layer of the sending STA. In addition, in the present disclosure, a non-AP STA that supports transmission of latency-sensitive data may be referred to as a low-latency STA. And, data other than latency-sensitive data may be referred to as regular data.

[0256] Fig. 20 is a diagram for describing an example of restricted TWT operation.

[0257] Restricted TWT (r-TWT) can support the priority of ensuring the data transmission possibility of low-latency STAs compared to other STAs by enabling the AP to configure a special broadcast TWT for the low-latency STA that sends latency-sensitive data. The STA can establish at least one r-TWT scheduling membership for the AP. Here, the r-TWT agreement can be established through the same process as the broadcast TWT agreement, and the broadcast TWT element for it can be defined to include an r-TWT parameter set field. For example, the r-TWT parameter set may refer to a specific broadcast TWT parameter set field that is different from other broadcast TWT parameter set fields. In other words, the r-TWT parameter set field may correspond to a special case of the broadcast TWT parameter set field. In addition, the AP can announce the r-TWT SP.

[0258] Basically, when other STAs supporting r-TWT operation are TXOP holders, TXOP should end before the start time of the r-TWT SP announced in the combined AP. Therefore, the STA associated with the corresponding r-TWT (i.e., low-latency STA) can send or receive services preferentially compared to other STAs in the r-TWT SP.

[0259] In the present disclosure, as described above, a low-latency STA associated with a specific r-TWT is referred to as a member r-TWT scheduled STA, and other STAs are referred to as non-member STAs. A non-member STA may be a STA that has the ability to support r-TWT operations but is not a member of any r-TWT or a STA that supports r-TWT operations and is a member of other r-TWTs or does not have the ability to support r-TWT operations.

[0260] A STA (e.g., a low-latency STA) that supports restricted SP (or r-TWT SP) operation of broadcast TWT can notify the AP that latency-sensitive data should be sent based on r-TWT operation. If the AP supports r-TWT operation / mode, the AP can send a frame including scheduling information of the TWT requested by each STA to the low-latency STA and other STAs. For example, in order to perform operations for r-TWT, a non-AP STA can obtain r-TWT related information from the AP through a beacon frame, a probe response frame, a (re)association response frame, or other frames of undefined format (e.g., frames for broadcast, announcement, and notification).

[0261] According to the restricted TWT operation, NAV (e.g., (MU)RTS / CTS or CTS-to-self or silent interval, etc.) can be used to protect individual TXOPs in the r-TWT SP (i.e., access by other STAs is restricted). Before a specific r-TWT SP starts, if there is a TXOP of other STAs (i.e., non-member STAs) other than the STAs with membership in a specific r-TWT schedule, it should be stopped. And, the TXOP of other STAs (i.e., non-member STAs) can be additionally performed after the specific r-TWT SP ends. It can be called a TXOP rule-based operation of the r-TWT SP for non-member STAs.

[0262] exist Fig. 20 In the example of , STA1 may correspond to a low-latency STA, and STA2 may correspond to a STA that sends or receives regular data. The AP may notify the STA of r-TWT related information through a frame such as a beacon. In this case, according to the TXOP rules for r-TWT SP, STA2 (TXOP holder) should terminate the corresponding TXOP before the start time of any r-TWT SP announced by the associated AP.

[0263] The method for configuring / defining new TWT information with respect to restricted TWT is described below.

[0264] As described above, the TWT information frame may be used for operations such as pausing or resuming an assigned TWTSP for a specific period of time in a separate TWT or a broadcast TWT. Fig.16 When the value of all TWT subfields (ie, all TWT fields) in the TWT information field shown is 1, the STA (eg, AP STA / non-AP STA) can identify when to resume by the value of the next TWT subfield (ie, next TWT field).

[0265] However, there is no space in the existing TWT information field to separately indicate information related to the r-TWT SP.

[0266] For example, in the case of the existing TWT information field, since the value of the TWT stream identifier subfield is retained when the value of all TWT subfields is 1, the value of the corresponding subfield can be used to indicate whether the TWT SP corresponds to an r-TWT SP rather than a separate TWT / broadcast TWT SP.

[0267] In the case of the above method, information related to the restricted TWT may not be sufficiently included. In addition, the existing TWT information frame only includes information related to the broadcast TWT, and this may correspond to information unrelated to the restricted TWT.

[0268] With this in mind, a method of signaling a new TWT information frame / TWT information field containing information related to the r-TWT SP may be required. Through this signaling, information transfer between STAs supporting limited TWT and the AP can be made clear.

[0269] Therefore, the present disclosure proposes a method for configuring / defining new TWT information for r-TWT SP.

[0270] Specifically, a method for signaling an r-TWT information field to indicate that the corresponding TWT is an r-TWT SP and a method for indicating whether data is sent and received between an AP and a STA within the r-TWT SP (e.g., UL / DL transmission and reception) or between STAs (e.g., peer-to-peer, P2P transmission and reception) will be proposed.

[0271] The names or configuration order of the fields / subfields described below are examples for the sake of explanation clarity, and the proposal of the present disclosure is not limited thereto. That is, the names or configuration order of the fields / subfields described below may be changed and applied.

[0272] In addition, the STA described below may include an AP STA or a non-AP STA.

[0273] The embodiments described below are divided for clarity of explanation, and each of the embodiments may be applied independently, or a part / the entire configuration of one embodiment may be applied by combining / combining / replacing a part of the entire configuration of another embodiment.

[0274] Implementation Method 1

[0275] This embodiment proposes a method for defining / designing a TWT information frame / field for indicating / sending the above-mentioned r-TWT SP related information.

[0276] Fig.21 An example of an r-TWT related information frame according to the present disclosure is illustrated.

[0277] Reference Fig.21 , the r-TWT related information frame may correspond to a newly designed / defined r-TWT information frame to indicate information related to the r-TWT SP.

[0278] The r-TWT information frame may be sent by a STA to request or transfer information related to the r-TWT SP. The action frame of the r-TWT information frame may include an r-TWT information field.

[0279] For example, the r-TWT information frame (or r-TWT information field) may include a 1-bit restricted TWT subfield, a 5-bit broadcast TWTID subfield, a 1-bit P2P subfield, a 1-bit all TWT subfield, a 2-bit next TWT subfield size subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0280] The Restricted TWT subfield may indicate whether the scheduled TWT SP is a broadcast TWT or a restricted TWT. That is, the Restricted TWT subfield may be used to distinguish whether the scheduled TWT SP corresponds to an r-TWT SP.

[0281] If the value of the Restricted TWT subfield is 1, this may indicate r-TWT SP, and if the value of the Restricted TWT subfield is 0, this may indicate broadcast TWT SP. In this regard, the value of the Restricted TWT subfield may be set opposite to the above case.

[0282] The Broadcast TWT ID subfield may be used to indicate TWT membership of STAs supporting limited TWT. Based on the corresponding subfield, information on which broadcast TWT ID the r-TWT SP announced from the AP is the r-TWT SP allocated to the STA belonging to which broadcast TWT ID may be confirmed.

[0283] The P2P subfield may indicate whether a P2P operation is performed within the scheduled TWT SP.

[0284] If the value of the P2P subfield is 1, it may indicate that a P2P operation between STAs supporting restricted TWT (i.e., STAs scheduled for r-TWT) is performed during r-TWT SP. If the value of the P2P subfield is 0, it may indicate that UL / DL data transmission and reception between the AP and the STA is performed during r-TWT SP rather than during P2P operation. In this regard, the value of the P2P subfield may be set opposite to the above case.

[0285] The All TWT subfield may indicate whether to reschedule all TWT SPs allocated to the STA.

[0286] If all TWT subfields are set to 1, information on the rescheduled TWT SP may be notified / indicated by the value of the Next TWT subfield. If all TWT SPs are not rescheduled, all TWT subfields may be set to 0.

[0287] In this regard, the suspension information of r-TWT / non-r-TWT may be indicated by a combination of the above-mentioned restricted TWT subfield and the all TWT subfield.

[0288] For example, if the All TWT subfield is set to 0 and the Restricted TWT subfield is set to 1, this may indicate that a particular r-TWT schedule is suspended. If the All TWT subfield is set to 1 and the Restricted TWT subfield is set to 1, this may indicate that all r-TWT schedules are suspended. If the All TWT subfield is set to 1 and the Restricted TWT subfield is set to 0, this may indicate that all non-r-TWT schedules are suspended.

[0289] The Next TWT Subfield Size subfield may indicate the size of the next TWT subfield. If the value of the Next TWT Subfield Size subfield is 0, 1, 2, and 3, this may indicate that the size of the next TWT subfield is 0, 32, 48, and 64, respectively.

[0290] The Next TWT subfield may indicate a specific time of the next TWT of the r-TWT SP. The Next TWT subfield may have a variable length depending on the value of the Next TWT subfield Size.

[0291] For example, if all TWT subfields are set to 1 and the Next TWT subfield is set to 0, a pause of the r-TWT SP may be indicated. resume ), this may indicate that the r-TWT will be restored from the first allocated r-TWT SP after the next TWT (i.e., after the indicated time).

[0292] In an example according to the present disclosure, T resume May correspond to the recovery timing reference and may have a value based on the TSF.

[0293] In the following, we will Fig. 22 and Fig.23 Describe the operations between the r-TWT scheduled AP and the r-TWT scheduled STA based on the above-mentioned r-TWT related information frames.

[0294] Fig. 22 An example of restricted TWT operation based on r-TWT information frame according to the present disclosure is illustrated.

[0295] Reference Fig. 22 , shows an example r-TWT information frame for pausing and resuming an r-TWT SP (RSP). Fig. 22 In the figure, AP corresponds to the r-TWT scheduled AP, and RSP STA1 can correspond to the r-TWT scheduled STA.

[0296] In addition, Fig. 22In the TWT information frame format, TWT information can be sent and received. This can correspond to the above-mentioned r-TWT information frame / field, or can include the r-TWT information frame / field.

[0297] First, the AP may notify the STAs (including RSPSTA1) to which the r-TWT SP has been assigned of the r-TWT related information through a management frame such as a beacon frame. Here, the r-TWT related information may include RSP allocation information and the like.

[0298] If RSP STA1 does not utilize (ie, suspends) the allocated r-TWT SP, it may send TWT information to the AP.

[0299] As a specific example, with respect to the r-TWT information frame sent by RSP STA1 to the AP, the value of the restricted TWT subfield may be set to 1, the value of the broadcast TWT ID subfield may be set to 2, the value of the all TWT subfield may be set to 1, and the value of the next TWT subfield may be set to 0 (i.e., pause).

[0300] In response to the corresponding TWT information, RSP STA1 may receive ACK from AP. RSP STA1 having received ACK does not send or receive data from r-TWT SP (eg, RSP#1, RSP#2) until r-TWT SP resumes. That is, RSP may be suspended or temporarily suspended.

[0301] To instruct RSP STA1 to resume the corresponding r-TWT SP, RSP STA1 may set the value of the Next TWT subfield to the desired resumption time (eg, T resume ) to send TWT information to AP.

[0302] As a specific example, with respect to the r-TWT information frame sent by RSP STA1 to the AP, the value of the Restricted TWT subfield may be set to 1, the value of the Broadcast TWT ID subfield may be set to 2, the value of the All TWT subfield may be set to 1, and the value of the Next TWT subfield may be set to T resume (eg, RSP#3 start time).

[0303] In response to the corresponding TWT information, RSP STA 1 may receive ACK from the AP. RSP STA 1 having received the corresponding ACK may start data transmission and reception from RSP#3 which is at time T resume The r-TWT SP allocated later (ie, the next r-TWT SP) can be restored. resumeTransmission and reception of UL / DL data within the r-TWT SP between the AP and RSPSTA 1 are resumed in the allocated r-TWT SP.

[0304] Fig.23 Another example of restricted TWT operation based on r-TWT information frame according to the present disclosure is illustrated.

[0305] Reference Fig.23 , shows an example of an r-TWT information frame for suspending and resuming r-TWT SP (RSP) / sharing P2P operation information between r-TWT SP (RSP). Fig.23 In the figure, AP corresponds to the r-TWT scheduled AP, and RSP STA 1 and RSPSTA 2 can correspond to the r-TWT scheduled STA.

[0306] In addition, Fig.23 In the TWT information frame format, TWT information can be sent and received. This can correspond to the above-mentioned r-TWT information frame / field, or can include the r-TWT information frame / field.

[0307] First, the AP may notify the STA (including RSP STA1) to which the r-TWT SP has been assigned of r-TWT related information through a management frame such as a beacon frame. Here, the r-TWT related information may include RSP allocation information, etc. Additionally or alternatively, the r-TWT SP may be configured for P2P transmission and reception, or P2P transmission and reception may be performed within a designated TXOP through separate signaling for P2P transmission and reception within the r-TWT SP (e.g., a P2P support mode of a triggered TXOP sharing process).

[0308] In order to obtain the same membership as the RSP included in a management frame such as a beacon frame, RSP STA 2 may send a TWT request to the AP by specifying the same broadcast TWT ID value and setting the negotiation type value to 3.

[0309] In response to the TWT request, the AP may set up a TWT setup command to accept the TWT and send a TWT response to RSP STA 2.

[0310] Thereafter, if RSP STA 1 does not utilize (ie, suspends) the allocated r-TWT SP, it may send TWT information to the AP.

[0311] As a specific example, with respect to the r-TWT information frame sent by RSP STA 1 to the AP, the value of the restricted TWT subfield may be set to 1, the value of the broadcast TWT ID subfield may be set to 3, the value of the P2P subfield may be set to 1, the value of the all TWT subfields may be set to 1, and the value of the next TWT subfield may be set to 0 (i.e., pause).

[0312] In response to the corresponding TWT information, RSP STA 1 may receive ACK from the AP. RSP STA 1 having received ACK does not transmit or receive data in the r-TWT SP until it resumes the r-TWT SP. In other words, the RSP related to the P2P operation may be suspended or temporarily suspended.

[0313] The AP that has received the above-mentioned TWT information can notify the RSP STA with the same broadcast TWT ID that the RSP is suspended or suspended. For example, the AP can notify the RSP STA (including RSP STA 2) assigned with the r-TWT SP as RSP STA 1 (i.e., with the same broadcast TWTID) through a management frame such as a beacon frame that the P2P operation within the r-TWT SP to be performed by RSP STA 1 is suspended or delayed until resumed.

[0314] RSP STA 2 having received the information does not perform data transmission and reception (particularly P2P transmission and reception) in r-TWT SP (eg, RSP#1, RSP#2) until the corresponding r-TWT SP is restored. That is, the RSP related to the P2P operation may be suspended or temporarily suspended.

[0315] Additionally or alternatively, since the P2P operation is performed by a trigger from the AP, the AP may not notify other STAs that the RSP related to the P2P operation is suspended.

[0316] Then, when RSP STA 1 wishes to transmit and receive data with RSP STA 2 through the r-TWT SP (i.e., when it wishes to resume the r-TWT SP related to the P2P operation), RSP STA 1 may resume the next TWT subfield by setting the value of the next TWT subfield to the desired time (i.e., T resume ) and set the value of the P2P subfield to 1 to send TWT information to the AP.

[0317] As a specific example, with respect to an r-TWT information frame sent by RSP STA 1 to the AP, the value of the Restricted TWT subfield may be set to 1, the value of the Broadcast TWT ID subfield may be set to 2, the value of the All TWT subfield may be set to 1, and the value of the Next TWT subfield may be set to Tresume (eg, RSP#3 start time).

[0318] In response to the corresponding TWT information, RSP STA 1 may receive ACK from the AP. RSP STA 1 having received ACK may start transmitting and receiving data between RSP STA 1 and RSP STA 2 from RSP#3, which is at time T resume The r-TWT SP allocated later (ie, the next r-TWT SP). That is, it can be based on the time T resume The P2P operation between RSP STA 1 and RSP STA 2 is resumed in the assigned r-TWT SP. In this case, frame transmission and reception, etc. can be performed between RSP STA 1 and RSP STA 2 in the corresponding r-TWT SP. For example, in RSP#3, RSP STA 1 can send MU-RTS to RSP STA 2, and RSP STA 2 can send CTS to RSP STA 1.

[0319] The AP that has received the above-mentioned TWT information can notify the RSP STA with the same broadcast TWT ID that the RSP is restored. For example, the AP can notify the RSP STA (including RSP STA 2) assigned with the r-TWT SP as RSP STA 1 (i.e., having the same broadcast TWT ID) of the restoration of the P2P operation within the r-TWT SP to be performed by RSP STA 1 through a management frame such as a beacon frame.

[0320] RSP STA 2, which has received the information, can resume Data transmission and reception (specifically, P2P transmission and reception) is performed at the first RSP thereafter.

[0321] Additionally or alternatively, the AP may provide the RSP STA 2 with information for triggering the P2P operation without notifying other STAs that the RSP related to the P2P operation is restored.

[0322] Regarding the above Fig.21 In the r-TWT information frame / field, the restricted TWT subfield and the P2P subfield can be expressed as one subfield.

[0323] Fig.24 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0324] Reference Fig.24 , Fig.21The restricted TWT subfield and P2P subfield in can be expressed (integrated) as a TWT identifier subfield.

[0325] For example, the r-TWT information frame (or r-TWT information field) may include a 2-bit TWT identifier subfield, a 5-bit broadcast TWT ID subfield, a 1-bit all TWT subfield, a 2-bit next TWT subfield size subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0326] The TWT identifier subfield may indicate / distinguish information about whether the scheduled TWT SP is for a broadcast TWT, a restricted TWT, or a P2P operation within a restricted TWT.

[0327] For example, setting the value of the TWT identifier subfield to 0 may indicate that the scheduled TWT SP is used for broadcast TWT. Setting the value of the TWT identifier subfield to 1 may indicate that the scheduled TWT SP is used for transmission and reception of UL / DL data within a restricted TWT. Setting the value of the TWT identifier subfield to 2 may indicate that the scheduled TWT SP is used for transmission and reception of data based on P2P operations within a restricted TWT. Setting the value of the TWT identifier subfield to 3 may be reserved.

[0328] Additionally or alternatively, with respect to the above Fig.21 The r-TWT information frame / field in the example may also consider the case where the restricted TWT subfield is not included.

[0329] Fig.25 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0330] Reference Fig.25 , can be excluded from the r-TWT information frame / field Fig.21 The restricted TWT subfield in .

[0331] For example, the r-TWT information frame (or r-TWT information field) may include a 5-bit broadcast TWT ID subfield, a 1-bit P2P subfield, a 1-bit all TWT subfield, a 2-bit next TWT subfield size subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0332] In this case, since the r-TWT information frame does not indicate whether the TWT SP is used for the restricted TWT, only the information of the TWT SP corresponding to the r-TWT SP may be transmitted.

[0333] That is to say, Fig.21 The r-TWT information frame / field in the may contain / send information about the broadcast TWT SP, and Fig.25The r-TWT information frame / field in may be designed / defined to only contain / carry information about the r-TWT SP.

[0334] Additionally or alternatively, with respect to the above Fig.21 In the r-TWT information frame / field, a response request subfield and a next TWT request subfield can be added.

[0335] Fig.26 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0336] Reference Fig.26 , the response request subfield and the next TWT request subfield may be included in Fig.21 In the r-TWT information frame / field.

[0337] For example, the r-TWT information frame (or r-TWT information field) may include a 1-bit restricted TWT subfield, a 5-bit broadcast TWT ID subfield, a 1-bit response request subfield, a 1-bit next TWT request subfield, a 1-bit P2P subfield, a 1-bit all TWT subfield, a 2-bit next TWT subfield size subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0338] The Response Request subfield can be set to 1 or 0 to indicate the presence or absence of a response when the TWT information frame is received.

[0339] That is, the response request subfield may indicate whether the transmitter of the frame including the TWT information field requests to send a TWT information frame in response to the frame. The response request subfield may be set to 0 to request the receiving end not to send a TWT information frame in response to the frame. The response request subfield may be set to 1 to request the receiving end to send a TWT information frame in response to the frame.

[0340] By setting the Next TWT Request subfield to 1 or 0, it can be indicated that there is or is not a request for receiving a TWT information frame including a Next TWT subfield set to a value greater than 0. That is, the Next TWT Request subfield can be set to 1 to indicate that the TWT information frame is a request for transmitting a TWT information frame including a Next TWT field having a length other than 0. Otherwise, the Next TWT Request subfield can be set to 0.

[0341] Implementation Method 2

[0342] In the above-mentioned Embodiment 1, the r-TWT related information frame / field for indicating the suspension / resumption of the r-TWT SP and P2P operations is described.

[0343] In this regard, a method of defining / designing a TWT information frame / field by additionally considering information on expansion / extension of the r-TWT SP is proposed in this embodiment.

[0344] For example, subfields related to the expansion / extension of the r-TWT SP may be designed / defined to be included in the above Fig.21 , Fig.24 , Fig.25 and / or Fig.26 In the r-TWT information frame / field.

[0345] Fig. 27 Another example of the r-TWT related information frame according to the present disclosure is illustrated.

[0346] Reference Fig. 27 ,against Fig.21 The r-TWT information frame / field in the may also include subfields related to the extension of the r-TWT SP, i.e., the restricted TWT SP extension subfield.

[0347] For example, the r-TWT information frame (or r-TWT information field) may include a 1-bit restricted TWT subfield, a 5-bit broadcast TWT ID subfield, a 1-bit P2P subfield, a 1-bit restricted TWT SP extension subfield, a 1-bit all TWT subfield, a 2-bit next TWT subfield size subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0348] The Restricted TWT SP Extension subfield may include information about the expansion / extension of the end time of the initially configured r-TWT SP.

[0349] For example, when the STA sends an r-TWT infoframe with the value of the restricted TWT SP extension subfield set to 1 to the AP, this may mean that the STA sends a request to the AP to extend the end time of the currently ongoing r-TWT SP. At this time, the value of the next TWT in the corresponding r-TWT infoframe is set to a value greater than 0 (e.g., T end ) can be used to indicate a specific end timing.

[0350] In an example according to the present disclosure, T end May correspond to the extended end timing, and may have a value based on the TSF.

[0351] For another example, when the AP sends an r-TWT information frame with the value of the Restricted TWT SP Extension subfield set to 1 to the STA, this may mean that the AP announces that the end timing of the currently ongoing r-TWT SP has been extended to the value of the Next TWT subfield.

[0352] In the examples of the above two cases, the duration from the delayed r-TWT SP start timing to the extended r-TWT SP end point may not exceed the duration of the r-TWT SP initially scheduled by the AP. Additionally or alternatively, when the r-TWTSP is extended, it may not overlap (i.e., overlap) with the subsequently scheduled TWT SP.

[0353] Taking this into consideration, the AP should reject the STA's r-TWT SP extension request if at least one of the following two situations matches.

[0354] - Case 1. A case where the STA requests extension of the r-TWT SP end timing to have a longer duration than the duration of the r-TWT SP initially scheduled by the AP.

[0355] - Case 2. The case where the STA's extension request for the r-TWT SP is repeated with (ie, overlaps with) the TWT SP scheduled after the current r-TWT SP.

[0356] In this regard, in order to confirm / convey that the STA's extension request for the r-TWT SP is valid, the AP may need to send an ACK for the extension request to the STA. Through the ACK, the STA can confirm that the extension request for the r-TWT SP has been accepted / approved by the AP and that the end timing of the r-TWT SP has been extended.

[0357] Regarding the value of a specific restricted TWT SP extension subfield, the following information may be indicated based on the above-mentioned all TWT subfields, the next TWT subfield, and the restricted TWT SP extension subfield.

[0358] For example, if the value of the All TWT subfield is set to 1, the value of the Next TWT subfield is set to 0, and the value of the Limited TWT SP Extension subfield is set to 0, it may indicate / represent the suspension of the r-TWT SP. resume ), and the value of the restricted TWTSP extension subfield is set to 0, it may indicate / mean that the r-TWT SP is from the value of the next TWT subfield (ie, T resume ) is restored after the first r-TWT SP is allocated. If the values ​​of all TWT subfields are set to 1, the value of the next TWT subfield is set to a value greater than 0 (e.g., T end ), and the value of the restricted TWT SP extension subfield is set to 1, then the value of the next TWT subfield (i.e., T end) may indicate / mean the end timing of the extended r-TWT SP. If the values ​​of all TWT subfields are set to 0, the value of the next TWT subfield is set to a value greater than 0 (e.g., T end ), and the value of the restricted TWT SP extension subfield is set to 1, then the value of the next TWT subfield (i.e., T end ) may indicate / mean the end timing (from STA to AP) for the extended r-TWT SP request.

[0359] In the following, consider the above Fig.28 and 29 The extended r-TWT SP described describes the operations between the r-TWT scheduled AP and the r-TWT scheduled STA based on the r-TWT related information frame.

[0360] exist Fig.28 and Fig.29 In the TWT information, the TWT information can be sent and received in the TWT information frame format. This can correspond to the above-mentioned r-TWT information frame / field, or can include the r-TWT information frame / field.

[0361] Fig.28 An example of restricted TWT operation considering extended r-TWT SP according to the present disclosure is illustrated.

[0362] Reference Fig.28 , which illustrates a signaling method of TWT information in the case where an extended r-TWT SP is generated by a STA that does not support r-TWT (ie, does not belong to the r-TWT SP).

[0363] First, the AP may notify the STA assigned to the r-TWT SP of r-TWT related information through a management frame such as a beacon frame. Here, the r-TWT related information may include RSP allocation information, etc.

[0364] As described above, the TXOP of a STA that does not belong to an r-TWT SP should be suspended before any r-TWT SP starts. For example, non-RSP STA 2 does not belong to the RSP, so the TXOP should be suspended. However, in cases where the r-TWT SP may not be prioritized, such as when the TXOP of non-RSP STA 2 is used for delay-sensitive services, the start timing of the r-TWT SP is postponed, and therefore, the end timing of the r-TWT SP may also be postponed. This may be referred to as an extended r-TWT SP.

[0365] exist Fig.28In the example of , the extended RSP appears due to the TXOP of non-RSP STA 2, and the initial allocated RSP can be extended by TWT information sent by the AP. At this time, the length of the initially allocated RSP should be greater than or equal to the extended RSP.

[0366] As a specific example, with respect to the r-TWT information frame transmitted by the AP, the value of the Restricted TWT subfield may be set to 1, the value of the Restricted TWT SP Extension subfield may be set to 1, the value of the All TWT subfield may be set to 1, and the value of the Next TWT subfield may be set to T end (ie, the end timing of the extended RSP). In other words, the AP may set the value of the Restricted TWTSP Extension subfield to 1 to indicate that the current r-TWT SP is extended, and end (which is the value of the Next TWT subfield) to indicate the pause timing of the extended r-TWT SP.

[0367] If the r-TWT SP is allocated to a plurality of STAs based on a broadcast TWT, a receiver address (RA) field of the corresponding TWT information may be set to a broadcast address and transmitted in a broadcast method.

[0368] The RSP STA (eg, RSP STA 1) that receives ACK for the above TWT information may be extended to T based on the end timing of the r-TWT SP. end Data is sent and received regularly within the RSP.

[0369] Fig.29 Another example of restricted TWT operation considering extended r-TWT SP according to the present disclosure is illustrated.

[0370] Reference Fig.29 , which illustrates a signaling method of TWT information in a case where an extended r-TWT SP is generated by a STA that does not support r-TWT (ie, does not belong to the r-TWT SP) and a P2P operation between RSP STAs is considered.

[0371] First, the AP may notify the STA assigned to the r-TWT SP of r-TWT related information through a management frame such as a beacon frame. Here, the r-TWT related information may include RSP allocation information, etc. Additionally or alternatively, the r-TWT SP may be configured for P2P transmission and reception, or P2P transmission and reception may be performed within a designated TXOP through separate signaling for P2P transmission and reception within the r-TWT SP (e.g., a P2P support mode of a triggered TXOP sharing process).

[0372] In order to obtain the same membership as the RSP included in a management frame (such as a beacon frame), RSP STA 2 can send a TWT request to the AP by specifying the same broadcast TWT ID value and setting the negotiation type value to 3.

[0373] In response to the TWT request, the AP may set up a TWT setup command to accept the TWT and send a TWT response to RSP STA 2.

[0374] As described above, the TXOP of a STA that does not belong to the r-TWT SP should be suspended before any r-TWT SP starts. For example, non-RSP STA 3 does not belong to the RSP, so the TXOP should be suspended. However, in the case where the TXOP of non-RSP STA 3 is used for delay-sensitive services, in the case where the r-TWT SP may not be prioritized, the start timing of the r-TWT SP can be postponed, and the end timing of the r-TWT SP can also be postponed accordingly.

[0375] exist Fig.29 In the example of , the extended RSP appears due to the TXOP of non-RSP STA 3, and the TWT information sent by the AP may indicate that the initially allocated RSP is extended. At this time, the length of the initially allocated RSP must be greater than or equal to the extended RSP.

[0376] As a specific example, with respect to the r-TWT information frame transmitted by the AP, the value of the Restricted TWT subfield may be set to 1, the value of the Broadcast TWT ID subfield may be set to 3, the value of the P2P subfield may be set to 1, the value of the Restricted TWT SP Extension subfield may be set to 1, the value of the All TWT subfield may be set to 1, and the value of the Next TWT subfield may be set to T end (ie, the end timing of the extended RSP). In other words, the AP may set the value of the Restricted TWT SP Extension subfield to 1 to indicate that the current r-TWTSP through which data transmission and reception between RSP STA 1 and RSP STA 2 is performed is extended and can be extended through T end (which is the value of the Next TWT subfield) to indicate the pause timing of the extended r-TWT SP.

[0377] If the r-TWT SP is allocated to a plurality of STAs based on a broadcast TWT, a receiver address (RA) field of the TWT information may be set to a broadcast address and transmitted in a broadcast method.

[0378] The RSP STA (eg, RSP STA 1) that receives ACK for the above TWT information may be extended to T based on the end timing of the r-TWT SP. endThe transmission and reception are performed according to the P2P operation in the RSP at a certain timing.

[0379] Fig.30 2 is a diagram for explaining an operation of a STA supporting rescheduling of an r-TWT SP according to one embodiment of the present disclosure.

[0380] exist Fig.30 In the embodiment, the operation of the STA based on the previously proposed method (for example, any one of the above-mentioned Embodiment 1, Embodiment 2 and their specific embodiments, or a combination of one or more (detailed) embodiments) is illustrated.

[0381] In step S3010, the STA may establish r-TWT related agreements.

[0382] Here, an r-TWT related agreement may be established between an AP STA and a non-AP STA. As an example, as described above, an r-TWT related agreement may be established based on the exchange of a TWT request and a TWT response.

[0383] Regarding r-TWT related conventions, if the STA is a non-AP STA, the STA can receive r-TWT SP related allocation information from the AP STA through a management frame such as a beacon frame. Alternatively, if the STA is an AP STA, the STA can send r-TWT SP related allocation information to the non-AP STA through a management frame such as a beacon frame.

[0384] In step S3020, the STA may send at least one frame including a TWT information field to one or more other STAs.

[0385] If the STA is a non-AP STA, one or more other STAs may be AP STAs.

[0386] If the STA is an AP STA, the one or more other STAs may be one or more non-AP STAs.

[0387] Here, the frame including the TWT information field may be a TWT information frame. For example, at least one frame may include a separate TWT information frame defined for r-TWT and may include an existing TWT information frame.

[0388] As in an embodiment of the present disclosure, the TWT information field may include an r-TWT related subfield, an all TWT subfield, and a next TWT subfield.

[0389] Rescheduling related information for the r-TWT SP (or currently existing r-TWT SP) scheduled for the STA may be indicated based on the r-TWT related subfield, the all TWT subfield, and the next TWT subfield within the TWT information field sent by the STA.

[0390] Here, the rescheduling related information may include one or more of whether the r-TWT SP is suspended, information on the resume timing of the r-TWT SP, and information on the end timing of the extended r-TWT SP.

[0391] Based on the combination of the r-TWT related subfield and the all TWT subfield, the target of rescheduling can be indicated / confirmed. For example, a specific combination between the value of the r-TWT related subfield and the value of the all TWT subfield can indicate the suspension of all r-TWT SPs scheduled for STA.

[0392] For example, the r-TWT related subfield may indicate whether the rescheduled TWT SP corresponds to the r-TWT SP. As a specific example, the r-TWT related subfield may indicate whether the currently existing or rescheduled TWT SP corresponds to the r-TWT SP or the broadcast TWT SP.

[0393] For example, the TWT Information field may further include a Broadcast TWT ID subfield. If the rescheduled TWT SP corresponds to an r-TWT SP, the Broadcast TWT ID subfield may indicate TWT membership of one or more STAs supporting the corresponding r-TWT SP.

[0394] Additionally or alternatively, for the same value of all TWT subfields (e.g., set to 1), the value of the Next TWT subfield may indicate whether the r-TWT SP suspends or resumes timing information (e.g., resumes the timing reference). For example, for all TWT subfields set to a value of 1, a Next TWT subfield set to a value of 0 may indicate a suspension, and a Next TWT subfield set to a value greater than 0 may indicate a resumption of timing information. Here, the resumption timing information may correspond to the first r-TWT SP after the Next TWT field value.

[0395] Additionally or alternatively, the TWT information field may also include a subfield indicating the type of the r-TWT SP (e.g., a P2P subfield). Here, the type of the r-TWT SP may include a first type for UL / DL transmission and reception between an AP STA and a non-AP STA and a second type for P2P transmission and reception between non-AP STAs.

[0396] Additionally or alternatively, the TWT information field may also include an extension-related subfield (eg, a restricted TWT SP extension subfield) indicating whether the end timing of the r-TWT SP scheduled for the STA is extended.

[0397] In this regard, information related to the extension / restoration of the r-TWT SP may be indicated based on the value of the corresponding subfield and the value of the next TWT subfield (as well as the values ​​of all TWT subfields).

[0398] For example, if all TWT subfields are set to 1 and the Next TWT subfield is set to a value greater than 0, the extension-related subfield set to a first value (e.g., a value of 0) may indicate resumption in the first r-TWT SP after the value of the Next TWT subfield. On the other hand, if all TWT subfields are set to 1 and the Next TWT subfield is set to a value greater than 0, the extension-related subfield set to a second value (e.g., a value of 1) may indicate / announce that the end timing is extended to the value of the Next TWT subfield. This may be the case where an AP STA sends a corresponding TWT information field to a non-AP STA.

[0399] For another example, if all TWT subfields are set to 0 and the next TWT subfield is set to a value greater than 0, the extension-related subfield set to a specific value (e.g., value 1) may indicate / represent a request to extend the end timing of the r-TWT SP to the value of the next TWT subfield. This may be the case when a non-AP STA sends a corresponding TWT information field to an AP STA. In this regard, if certain conditions are not met, the request will be rejected by the AP STA. As an example, if the duration length of the extended r-TWT SP exceeds the duration length of the r-TWT SP initially scheduled for the STA, or if at least one of the following situations in which the extended r-TWT SP overlaps with a subsequently existing TWT SP applies, the request may be rejected and the AP STA may send information about the rejection to the non-AP STA.

[0400] In the present disclosure described above, as new TWT information for r-TWT SP, the definition / design of a TWT information frame / field containing information related to the r-TWT SP and a signaling method based thereon are explained.

[0401] In this regard, the r-TWT information frame in the proposal of the present disclosure may be applied / utilized by defining a new TWT information frame, and additionally or alternatively, it may also be applied / utilized based on an existing TWT information frame.

[0402] For example, in order to indicate / deliver the above-mentioned r-TWT SP related information, a new TWT information frame for restricted TWT may be transmitted and received separately from the existing TWT information frame.

[0403] For another example, the new TWT information for the r-TWT SP may be based on an existing TWT information frame, but may be configured / defined in the format of a new TWT information field. As a specific example, within an existing TWT information frame, a new TWT information field (i.e., an additional / extended TWT information field) may be included after the existing TWT information field. That is, in contrast to the existing TWT information field (e.g., Fig.16 Separately from the TWT information field format in the new TWT information field, the new TWT information field may include subfields related to the r-TWT SP described above in the present disclosure. In this case, information related to the r-TWT SP may be indicated based on the new TWT information field or a combination of the existing TWT information field and the new TWT information field.

[0404] The above-mentioned embodiments are elements and features of the present disclosure combined in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be considered as optional. Each element or feature can be implemented in a form not combined with other elements or features. In addition, the embodiments of the present disclosure may include combined partial elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

[0405] It is clear to those skilled in the relevant art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0406] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that enable software or commands, etc. to be stored and executable in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product including such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, but is not limited thereto, and it may include a non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory, or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0407] Industrial Applicability

[0408] The method proposed in the present disclosure is mainly described based on an example applied to a system based on IEEE 802.11 (5G system), but can be applied to various WLAN or wireless communication systems other than the system based on IEEE 802.11.

Claims

1. A method performed by a station STA in a wireless LAN system, the method comprising the following steps: Establishing agreements related to the restricted target wake time r-TWT; as well as Sending at least one frame including a TWT information field to one or more other STAs, The TWT information field includes an r-TWT related subfield, a total TWT subfield, and a next TWT subfield, and Wherein, based on the r-TWT related subfield, the all TWT subfield and the next TWT subfield, rescheduling related information about the r-TWT service period r-TWT SP scheduled for the STA is indicated.

2. The method according to claim 1, in, A specific combination of the value of the r-TWT related subfield and the value of the all TWT subfield indicates suspension of all r-TWT SPs scheduled for the STA.

3. The method according to claim 1, in, The r-TWT related subfield indicates whether the rescheduled TWT SP corresponds to the r-TWT SP.

4. The method according to claim 3, in, The TWT Information field also includes a Broadcast TWT ID subfield, and Wherein, based on that the rescheduled TWT SP corresponds to the r-TWT SP, the broadcast TWT ID subfield indicates the TWT membership of one or more STAs supporting the r-TWT SP.

5. The method according to claim 1, in, For the same value of all TWT subfields, The Next TWT subfield being set to a value of 0 indicates a pause, and The Next TWT subfield, which is set to a value greater than 0, indicates resumption timing information.

6. The method according to claim 5, in, The resumption timing information corresponds to the first r-TWT SP after the next TWT subfield value.

7. The method according to claim 1, in, The TWT information field also includes a subfield indicating the type of r-TWT SP, and The types of r-TWT SP include a first type for uplink or downlink transmission and reception between an access point AP STA and a non-AP STA, and a second type for P2P transmission and reception between non-AP STAs.

8. The method according to claim 1, in, The TWT information field also includes an extension-related subfield, and the extension-related subfield indicates whether to extend the end timing of the r-TWT SP scheduled for the STA.

9. The method according to claim 8, in, Based on the Next TWT subfield being set to a value greater than 0, The extension-related subfield being set to a first value indicates resumption in the first r-TWT SP after the value of the next TWT subfield, and The extension-related subfield being set to a second value indicates that the end timing is extended to the value of the next TWT subfield.

10. The method according to claim 8, in, Based on the STA being a non-AP STA scheduled for r-TWT, and the one or more other STAs being AP STAs, The extension-related subfield set to a specific value and the next TWT subfield set to a value greater than 0 indicate a request to extend the end timing to the value of the next TWT subfield.

11. The method according to claim 10, in, Whether the AP STA rejects the request is determined based on at least one of the first condition or the second condition, The first condition corresponds to whether the duration of the extended r-TWT SP exceeds the duration of the r-TWT SP initially scheduled for the STA, and The second condition corresponds to whether the extended r-TWT SP overlaps with the subsequently located TWT SP.

12. A station STA in a wireless local area network WLAN system, the STA comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: Establishing agreements related to restricted target wake time r-TWT; and Sending at least one frame including a TWT information field to one or more other STAs, The TWT information field includes an r-TWT related subfield, a total TWT subfield, and a next TWT subfield, and Wherein, based on the r-TWT related subfield, the all TWT subfield and the next TWT subfield, rescheduling related information about the r-TWT service period r-TWT SP scheduled for the STA is indicated.

13. A processing device configured to control a station STA in a wireless local area network WLAN system, the processing device comprising: at least one processor; as well as At least one computer memory operatively coupled to the at least one processor and storing instructions which, when executed by the at least one processor, perform the method according to any one of claims 1 to 11.

14. At least one non-transitory computer-readable medium storing at least one instruction, wherein: The at least one instruction executed by at least one processor controls a device to perform the method according to any one of claims 1 to 11 in a wireless communication system.

Citation Information

Cited By

  • Wireless communication method, non-AP STA, and AP

    US12777523B2