Method and electronic devices for r-twt

By negotiating a common R-TWT schedule among adjacent APs, the method addresses interference issues in wireless communication systems, optimizing resource allocation and enhancing performance for latency-sensitive applications.

WO2026240478A1PCT designated stage Publication Date: 2026-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/095507
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-06-25
Filing Date
2026-04-03
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in meeting the quality of service (QoS) requirements for latency-sensitive applications like virtual and augmented reality due to interference from adjacent basic service sets (BSSs) during restricted target wake time (R-TWT) service periods, leading to inefficient resource utilization and reduced performance.

Method used

A method for determining a common R-TWT schedule through negotiation between adjacent access points (APs) to synchronize R-TWT service periods, minimizing interference and optimizing resource allocation across overlapping BSSs.

Benefits of technology

The method enhances R-TWT efficiency by ensuring simultaneous satisfaction of QoS requirements across multiple BSSs, reducing interference and improving performance for latency-sensitive applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026095507_19112026_PF_FP_ABST
    Figure KR2026095507_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed are a method for an R-TWT and an electronic device for performing same. The electronic device according to one embodiment may comprise a wireless communication circuit. The electronic device may comprise at least one processor comprising processing circuitry. The electronic device may comprise a memory storing instructions. The instructions: may cause the electronic device to transmit, through the wireless communication circuit to a first access point (AP) that has formed a second basic service set (BSS) adjacent to a first BSS formed by the electronic device, a first request frame comprising a first target wake time (TWT) element for a restricted target wake time (RTWT) service within the first BSS; and may cause the electronic device to receive, from the first AP through the wireless communication circuit, a first response frame comprising a second TWT element for an R-TWT service within the second BSS. The instructions: may cause the electronic device to determine a common R-TWT schedule within the first BSS and the second BSS via negotiation with the first AP, on the basis of the first TWT element and the second TWT element; and may cause the electronic device to broadcast, within the first BSS, information about the common R-TWT schedule.
Need to check novelty before this filing date? Find Prior Art

Description

Method for R-TWT and electronic device for performing the same

[0001] Various embodiments of the present invention relate to a method for R-TWT and an electronic device for performing the same.

[0002] In a Wi-Fi network, meeting the quality of service (QoS) requirements of an application (or service) can be important for user experience or application performance.

[0003] QoS requirements can be network performance conditions required for an application (or traffic). For example, a virtual reality application or an augmented reality application may have higher QoS requirements than a web browsing application (e.g., Google Chrome).

[0004] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0005] According to one embodiment, an electronic device may include a wireless communication circuit. The electronic device may include at least one processor including a processing circuit. The electronic device may include a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the electronic device may transmit, through the wireless communication circuit, a first request frame containing a first target wake time element for a restricted target wake time (R-TWT) service within the first BSS to a first access point (AP) that forms a second BSS adjacent to a first basic service set (BSS) formed by the electronic device. When the instructions are executed individually or collectively by the at least one processor, the electronic device may receive, through the wireless communication circuit, a first response frame containing a second TWT element for an R-TWT service within the second BSS from the first AP. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may determine a common R-TWT schedule within the first BSS and the second BSS through negotiation with the first AP based on the first TWT element and the second TWT element. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may broadcast information regarding the common R-TWT schedule within the first BSS.

[0006] According to one embodiment, a method of operation of an electronic device may include the operation of transmitting a first request frame containing a first TWT element (target wake time element) for a restricted target wake time (R-TWT) service within the first BSS to a first access point (AP) that forms a second BSS adjacent to a first basic service set (BSS) formed by the electronic device. The method of operation may include the operation of receiving a first response frame containing a second TWT element for an R-TWT service within the second BSS from the first AP. The method of operation may include the operation of determining a common R-TWT schedule within the first BSS and the second BSS through negotiation with the first AP based on the first TWT element and the second TWT element. The method of operation may include the operation of broadcasting information regarding the common R-TWT schedule within the first BSS.

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

[0008] FIGS. 1 and FIGS. 2 are drawings for explaining a wireless LAN system according to one embodiment.

[0009] FIG. 3 is a diagram illustrating a link setup operation according to one embodiment.

[0010] FIG. 4 is a schematic block diagram of an access point (AP) according to one embodiment.

[0011] FIG. 5 is a schematic block diagram of a STA (station) according to one embodiment.

[0012] FIG. 6 is a diagram illustrating an R-TWT protocol according to one embodiment.

[0013] FIG. 7 is a diagram illustrating a multi-AP cooperation method for R-TWT according to one embodiment.

[0014] FIG. 8 is a diagram illustrating an R-TWT negotiation method between APs according to one embodiment.

[0015] FIG. 9 is a diagram illustrating a multi-AP cooperation-based R-TWT negotiation system according to one embodiment.

[0016] FIGS. 10a and FIGS. 10b are drawings for illustrating request and / or response frames used in R-TWT negotiation according to one embodiment.

[0017] FIG. 11 is a drawing for explaining a TWT element according to one embodiment.

[0018] FIG. 12 is a diagram illustrating TWT parameter information according to one embodiment.

[0019] FIG. 13 is a diagram illustrating QoS characteristic elements according to one embodiment.

[0020] FIG. 14 is a diagram illustrating a TWT request frame according to one embodiment.

[0021] FIGS. 15a and FIGS. 15b are drawings for illustrating various examples of a multi-AP cooperation system according to one embodiment.

[0022] FIG. 16 is a diagram illustrating a method for dividing a common R-TWT SP according to one embodiment and allocating service sections to each AP.

[0023] FIGS. 17a and FIGS. 17b are drawings for explaining an R-TWT negotiation method between three or more APs according to one embodiment.

[0024] FIG. 18 is an example of a flowchart of an R-TWT negotiation method according to one embodiment.

[0025] FIG. 19 is a block diagram of an electronic device in a network environment according to one embodiment.

[0026] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are given the same reference numeral regardless of the drawing number, and redundant descriptions thereof will be omitted.

[0027]

[0028] FIGS. 1 and FIGS. 2 are drawings for explaining a wireless LAN system according to one embodiment.

[0029] Referring to FIG. 1, according to one embodiment, a wireless LAN system (10) may represent an infrastructure mode in which an access point (AP) exists in the structure of a wireless LAN (WLAN) of IEEE (Institute of Electrical and Electronic Engineers) 802.11. The wireless LAN system (10) may include one or more basic service sets (BSS) (e.g., BSS1, BSS2). A BSS (BSS1, BSS2) may represent a set of access points (e.g., electronic device (1802), electronic device (1804) of FIG. 18) and stations (e.g., electronic device (1801) of FIG. 18) that can communicate with each other by achieving synchronization. BSS1 may include AP1 and STA1, and BSS2 may include AP2, STA2, and STA3.

[0030] According to one embodiment, a wireless LAN system (10) may include at least one STA (STA1 to STA3), a plurality of APs (AP1, AP2) that provide a distribution service, and a distribution system (100) that connects the plurality of APs (AP1, AP2). The distribution system (100) may implement an extended service set (ESS) by connecting a plurality of BSSs (BSS1, BSS2). An ESS may be used as a term to refer to a single network formed by connecting a plurality of APs (AP1, AP2) through the distribution system (100). A plurality of APs (AP1, AP2) included in a single ESS may have the same service set identification (SSID).

[0031] According to one embodiment, STAs (STA1 to STA3) may be any functional medium including a medium access control (MAC) and a physical layer interface for the wireless medium that comply with the provisions of the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard. STAs (STA1 to STA3) may be used to include both APs and non-AP STAs (Non-AP stations). STAs (STA1 to STA3) may also be referred to by various names such as electronic device, mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or simply user.

[0032] Referring to FIG. 2, according to one embodiment, the wireless LAN system (20), unlike the wireless LAN system (10) of FIG. 1, may represent an ad-hoc mode in which communication is performed by establishing a network between a plurality of STAs (STA1 to STA3) without an AP in the structure of a wireless LAN (WLAN) of IEEE (institute of electrical and electronic engineers) 802.11. The wireless LAN system (20) may include a BSS operating in ad-hoc mode, that is, an independent BSS (independent basic service set (IBSS)).

[0033] According to one embodiment, since the IBSS does not include an AP, there may be no centralized management entity performing management functions. In the IBSS, STAs can be managed in a distributed manner. In the IBSS, all STAs can be mobile STAs, and since access to a distributed system is not allowed, it can form a self-contained network.

[0034]

[0035] FIG. 3 is a diagram illustrating an example of a link setup operation according to one embodiment.

[0036] Referring to FIG. 3, according to one embodiment, a link setup operation may be performed between devices (e.g., STA (301), AP (401)) to communicate with each other. For the link setup, network discovery, authentication, establishment of association, and security setup operations may be performed. The link setup operation may be referred to as a session initiation operation or a session setup operation. Additionally, the discovery, authentication, association, and security setup operations of the link setup operation may be collectively referred to as an association operation.

[0037] According to one embodiment, the network discovery operation may include operation 310 and operation 320. In operation 310, the STA (301) (e.g., electronic device (1801) of FIG. 18) may transmit a probe request frame to search for which AP (e.g., electronic device (1802) or electronic device (1804) of FIG. 18) exists and wait for a response to the probe request frame. The STA (301) may perform a scanning operation to access the network and find a network that can participate. The probe request frame may include information of the STA (301) (e.g., the device name and / or address of the STA (301)). The scanning operation in operation 310 may mean an active scanning operation. In operation 320, the AP (401) may transmit a probe response frame as a response to the probe request frame to the STA (301) that transmitted the probe request frame. The probe response frame may include information of the AP (401) (e.g., the device name and / or network information of the AP (401)). Although the network discovery operation is depicted in FIG. 3 as being performed through active scanning, it is not necessarily limited thereto, and if the STA (301) performs passive scanning, the transmission of the probe request frame may be omitted. The STA (301) performing passive scanning may receive a beacon frame transmitted by the AP (401) and perform the following subsequent procedures.

[0038] According to one embodiment, after the STA (301) discovers a network, an authentication operation including operations 330 and 340 may be performed. In operation 330, the STA (301) may transmit an authentication request frame to the AP (401). In operation 340, the AP (401) may determine whether to allow authentication for the STA (301) based on the information contained in the authentication request frame. The AP (401) may provide the result of the authentication process to the STA (301) via an authentication response frame. The authentication frame used for the authentication request / response may correspond to a management frame.

[0039] According to one embodiment, the authentication frame may include information about an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), or a finite cyclic group.

[0040] According to one embodiment, after the STA (301) is successfully authenticated, an association operation including operations 350 and 360 may be performed. In operation 350, the STA (301) may send an association request frame to the AP (401). In operation 360, the AP (401) may send an association response frame to the STA (301) in response to the association request frame.

[0041] According to one embodiment, association request frames and / or association response frames may include information related to various capabilities. For example, a connection request frame may include information related to various capabilities, beacon listen interval, SSID (service set identifier), supported rates, supported channels, RSN, mobility domain, supported operating classes, traffic indication map broadcast request, and / or information regarding interworking service capabilities. For example, a connection response frame may include information such as information related to various capabilities, status code, association ID (AID), support rate, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal to noise indicator (RSNI), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, and / or QoS map.

[0042] According to one embodiment, after the STA (301) is successfully associated with the network, a security setup operation including operations 370 and 380 may be performed. The security setup operation may be performed via a robust security network association (RSNA) request / response. For example, the security setup operation may include a private key setup operation via a 4-way handshake through an extensible authentication protocol over LAN (EAPOL) frame. The security setup operation may also be performed according to a security method not defined in the IEEE 802.11 standard.

[0043] According to one embodiment, a secure session is established between the STA (301) and the AP (401) according to a security setup operation, and the STA (301) and the AP (401) can conduct secure data communication.

[0044]

[0045] FIG. 4 is a schematic block diagram of an access point (AP) according to one embodiment.

[0046] Referring to FIG. 4, according to one embodiment, the electronic device (400) may be an example of the AP (401) described with reference to FIG. 1 to FIG. 3.

[0047] According to one embodiment, the electronic device (400) may include a processor (410), a memory (420), a transmitter (440), a receiver (450), and an antenna (460). The transmitter (440) and the receiver (450) may be combined into a transceiver (490) (e.g., a wireless communication circuit).

[0048] According to one embodiment, the processor (410) may perform MAC functions, PHY functions, RF functions, or a combination of some or all of these. The processor (410) may include some or all of the transmitter (440) and receiver (450). The processor (410) may be coupled to memory (420). The coupling may be direct or indirect.

[0049] According to one embodiment, the processor (410) may be implemented as a circuitry (e.g., processing circuitry) such as a system on chip (SoC) or an integrated circuit (IC). The processor (410) may include one or more processors. For example, the processor (410) may include a combination of one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a micro processing unit (MPU), an application processor (AP), and a communication processor (CP). The CP may be inside or outside the transceiver (490). Instructions stored in memory (420) may be executed by one processor to enable the electronic device (400) to perform and / or control the operation of the electronic device (e.g., AP (401)) described with reference to FIGS. 1 through 3 and the operation of the electronic device (401) described with reference to FIGS. 6 through 19. Instructions stored in memory (420) can be executed by a plurality of processors to enable the electronic device (400) to perform and / or control the operation of the electronic device (e.g., AP (401)) described with reference to FIGS. 1 to 3 and the operation of the electronic device (401) described with reference to FIGS. 6 to 19.

[0050] According to one embodiment, memory (420) may be a non-transitory recording medium that stores instructions that cause an electronic device (400) to perform an operation, method, or procedure described in the present invention when executed by a processor (410). Memory (420) may store instructions required by one or more of the processor (410), a transmitter (440), a receiver (450), and other components of the electronic device (400). Memory (420) may further store an operating system and an application. Memory (420) may include, be implemented as, or be included in read-and-write memory, read-only memory, volatile memory, non-volatile memory, or a combination of some or all of the foregoing.

[0051] According to one embodiment, the memory (420) may include one or more memories. Instructions stored in the memory (420) may be stored in a single memory. Instructions stored in the memory (420) may be divided and stored in multiple memories. Instructions stored in the memory (420) may be executed by a processor (410) to enable an electronic device (400) to perform and / or control the operation of an electronic device (e.g., AP (401)) described with reference to FIGS. 1 to 3 and the operation of an electronic device (401) described with reference to FIGS. 6 to 19.

[0052] According to one embodiment, the antenna section (460) includes one or more physical antennas. When multiple-input multiple-output (MIMO) or multi-user MIMO (MU-MIMO) is used, the antenna section (460) may include one or more physical antennas.

[0053] According to one embodiment, the transceiver (490) may be configured to transmit and receive wireless signals. The transceiver (490) may be a Wi-Fi chipset. The transceiver (490) may support multiple bands of 2.4 GHz, 5 GHz, and / or 6 GHz. A processor (410) may be operatively connected to the transceiver (490). A memory (420) may be electrically connected to the processor (410) and may store one or more instructions executable by the processor (410). An operation performed by the electronic device (400) may include an operation performed by the transceiver (490) and an operation performed by the processor (410) through the transceiver (490).

[0054]

[0055] FIG. 5 is a schematic block diagram of a STA (station) according to one embodiment.

[0056] Referring to FIG. 5, according to one embodiment, the electronic device (500) may be an example of the STA (301) described with reference to FIG. 1 to FIG. 3.

[0057] According to one embodiment, the electronic device (500) may include a processor (510), a memory (520), a transmitter (540), a receiver (550), and an antenna (560). The transmitter (540) and the receiver (550) may be combined into a transceiver (590) (e.g., a wireless communication circuit).

[0058] According to one embodiment, the processor (510) may perform MAC functions, PHY functions, RF functions, or a combination of some or all of these. The processor (510) may include some or all of the transmitter (540) and receiver (550). The processor (510) may be coupled to memory (520). The coupling may be direct or indirect.

[0059] According to one embodiment, the processor (510) may be implemented as a circuitry (e.g., processing circuitry) such as a system on chip (SoC) or an integrated circuit (IC). The processor (510) may include one or more processors. For example, the processor (510) may include a combination of one or more processors such as a CPU, GPU, MPU, AP, and CP. The CP may be inside or outside the transceiver (590). Instructions stored in memory (520) may be executed by one processor to cause the electronic device (500) to perform and / or control the operation of the electronic device (e.g., STA (301)) described with reference to FIGS. 1 through 3 and the operation of the electronic device (e.g., STA (301)) described with reference to FIGS. 6 through 19. Instructions stored in memory (520) can be executed by a plurality of processors to enable the electronic device (500) to perform and / or control the operation of the electronic device (e.g., STA (301)) described with reference to FIGS. 1 to 3 and the operation of the electronic device (301) described with reference to FIGS. 6 to 19.

[0060] According to one embodiment, memory (520) may be a non-transitory recording medium that stores instructions that cause an electronic device (500) to perform an operation, method, or procedure described in the present invention when executed by a processor (510). Memory (520) may store instructions required by one or more of the processor (510), a transmitter (540), a receiver (550), and other components of the electronic device (500). Memory (520) may further store an operating system and an application. Memory (520) may include, be implemented as, or be included in read-and-write memory, read-only memory, volatile memory, non-volatile memory, or a combination of some or all of the foregoing.

[0061] According to one embodiment, the memory (520) may include one or more memories. Instructions stored in the memory (520) may be stored in a single memory. Instructions stored in the memory (520) may be divided and stored in multiple memories. Instructions stored in the memory (520) may be executed by a processor (510) to cause an electronic device (500) to perform and / or control the operation of an electronic device (e.g., STA (301)) described with reference to FIGS. 1 to 3 and the operation of an electronic device (e.g., STA (301)) described with reference to FIGS. 6 to 19.

[0062] According to one embodiment, the antenna section (560) includes one or more physical antennas. When multiple-input multiple-output (MIMO) or multi-user MIMO (MU-MIMO) is used, the antenna section (560) may include one or more physical antennas.

[0063] According to one embodiment, the transceiver (590) may be configured to transmit and receive wireless signals. The transceiver (590) may be a Wi-Fi chipset. The transceiver (590) may support multiple bands of 2.4 GHz, 5 GHz, and / or 6 GHz. The processor (510) may be operatively connected to the transceiver (590). The electronic device (500) may correspond to the electronic device described in FIG. 19 (e.g., the electronic device (1901) of FIG. 19). Accordingly, descriptions that overlap with the parts described with reference to FIG. 19 are omitted. The memory (520) may be electrically connected to the processor (510) and may store one or more instructions executable by the processor (510). The operation performed by the electronic device (500) may include the operation performed by the transceiver (590) and the operation performed by the processor (510) through the transceiver (590).

[0064]

[0065] FIG. 6 is a diagram illustrating an R-TWT protocol according to one embodiment.

[0066] Referring to FIG. 6, according to one embodiment, in a wireless communication system (e.g., wireless communication system (10) of FIG. 1, wireless communication system (20) of FIG. 2), devices (e.g., STA (301), AP (401)) can perform wireless communication according to the R-TWT (restricted target wake time) protocol. The R-TWT protocol may be a protocol for supporting a latency demanding service that transmits and receives latency-sensitive traffic. The R-TWT protocol may be a technique that prioritizes securing the transmission and reception time of latency-sensitive traffic using broadcast TWT. Latency-sensitive traffic may be traffic included in a predefined access category (AC). Latency-sensitive traffic may be traffic assigned a predefined traffic identifier (TID). Latency may refer to the latency defined in IEEE 802.11ax. Latency may refer to the time interval between when a packet is transmitted from the source and when the packet reaches the destination. Below, we will describe how to negotiate an R-TWT between the AP (401) and the STA (301).

[0067] According to one embodiment, devices (e.g., STA (301), AP (401)) can perform wireless communication based on TWT settings (e.g., TWT parameters). TWT parameters may be operational parameters (e.g., periodic parameters and / or aperiodic parameters) for communication between devices (e.g., STA (301), AP (401)) based on the TWT protocol. TWT parameters may include information regarding the R-TWT service period (SP). For example, TWT parameters may include information on the start time of the R-TWT service period, information on the duration of the R-TWT service period, and / or information on the interval of the R-TWT service period.

[0068] According to one embodiment, devices (e.g., STA (301), AP (401)) can implement an R-TWT protocol through a broadcast TWT (e.g., a TWT element). In the broadcast TWT, the AP (401) can pre-schedule for an R-TWT service interval. In the broadcast TWT, the AP (401) can advertise a beacon signal (650). Member information may be included in the restricted TWT traffic information field of the TWT element.

[0069] According to one embodiment, the beacon signal (650) may include TWT elements and member information. The TWT elements may determine TWT parameters. The TWT parameters may include information regarding the R-TWT service interval. The member information may include information associated with a device granted membership to perform communication by prioritizing the transmission of frames in the R-TWT service interval. For example, the information associated with the device may be about the device granted membership. The member information may be included in either the TWT elements or the VS IE (vendor specific information element).

[0070] According to one embodiment, in a broadcast TWT, the AP (401) may advertise a beacon signal (650) including information about the R-TWT service period (SP) of the link, information about the TID mapped to the link, information about the direction of the link (e.g., uplink, downlink), and member information. The member information may be included in either the VS IE and TWT elements included in the beacon signal (650).

[0071] According to one embodiment, in a broadcast TWT, the STA (301) may request membership for a scheduled R-TWT service interval. Membership may be for the STA (301) to perform communication by prioritizing the transmission of frames in the R-TWT service interval. For example, the STA (301) may obtain information about the TID (traffic ID) mapped to the link from the TWT element. The STA (301) may transmit a frame requesting membership to the AP (401) to prioritize and transmit (or receive) traffic (e.g., a frame containing data) mapped to the membership link. Since the AP (401) grants membership to the STA (301) based on the priority information of the traffic corresponding to the TID, quality control of communication between the STA (301) and the AP (401) may be easy. For example, AP (401) may grant membership to STA (301) only when STA (301) transmits (or receives) latency-sensitive traffic (e.g., traffic such as games, or audio / video calls) according to the priority information of traffic corresponding to TID. AP (401) may not grant membership to STA (301) when STA (301) transmits (or receives) latency-tolerant traffic (e.g., traffic such as web browsing, video streaming) according to the priority information of traffic corresponding to TID. As described above, AP (401) and STA (301) can determine an R-TWT schedule through R-TWT negotiation and perform wireless communication according to the R-TWT schedule. At this time, the R-TWT schedule described in Fig. 6 is determined within a specific BSS, so devices within adjacent BSSs may not be affected by the R-TWT schedule of the specific BSS.As a result, interference by adjacent BSSs may occur during the R-TWT service period. For example, even if a non-member STA (e.g., non-member STA) within a BSS where the R-TWT schedule has been determined terminates a transmit / receive session before the start of the R-TWT service period, and a member STA (e.g., member STA) attempts to obtain media access opportunities through contention, devices within adjacent BSSs may occupy wireless resources, leading to a situation where the member STA is unable to obtain transmission / reception opportunities for real-time services during the R-TWT service period. To resolve this, it may be necessary for adjacent APs to cooperate regarding R-TWT.

[0072]

[0073] FIG. 7 is a diagram illustrating a multi-AP cooperation method for R-TWT according to one embodiment.

[0074] Referring to FIG. 7, according to one embodiment, when a plurality of APs (e.g., AP (701) and / or AP (702)) are adjacent, it may be necessary for the plurality of APs to cooperate with each other regarding R-TWT. Being adjacent to a plurality of APs may mean that the BSS formed by the plurality of APs is placed in an environment where they coexist adjacent to each other (e.g., OBSS (overlapped basic service sets)). Hereinafter, it is assumed that AP (701) and AP (702) are in an OBSS environment.

[0075] According to one embodiment, AP (701) can perform R-TWT negotiations with STA1s included in BSS1 within BSS1 formed by AP (701). AP (702) can also perform R-TWT negotiations with STA2s included in BSS2 within BSS2 formed by AP (702). For convenience of explanation, the R-TWT schedule determined in BSS1 is referred to as the first R-TWT schedule, and the R-TWT schedule determined in BSS2 is referred to as the second R-TWT schedule. As the method of R-TWT negotiation between AP and STA has been described in detail with reference to FIG. 6, redundant descriptions below will be omitted.

[0076] According to one embodiment, AP (701) and AP (702) may share their respective R-TWT schedules. AP (701) may transmit information regarding the first R-TWT schedule to AP (702), and AP (702) may transmit information regarding the second R-TWT schedule to AP (701). Based on the information regarding the second R-TWT schedule, AP (701) may terminate the transmission and reception sessions of devices within BSS1 before the start of the second R-TWT service period. Similarly, based on the information regarding the first R-TWT schedule, AP (702) may terminate the transmission and reception sessions of devices within BSS2 before the start of the first R-TWT service period. In this way, by exchanging information regarding R-TWT schedules independently set according to the BSS among APs and terminating the transmission and reception sessions of adjacent BSSs before the start of the R-TWT service period, interference by adjacent BSSs during the R-TWT service period can be minimized. However, as the R-TWT schedule is set independently according to the BSS, as illustrated in FIG. 7, a problem may arise where the R-TWT service intervals overlap over time. If one or more of the duration and interval of the first R-TWT service interval and the second R-TWT service interval are different, the first R-TWT service interval and the second R-TWT service interval may overlap over time. If the intervals of the first R-TWT service interval and the second R-TWT service interval are not the same, overlap may occur at the time when the least common multiple of each interval is reached. For example, if the first R-TWT service interval is set to 3ms and the second R-TWT service interval is set to 5ms, even if the start time is adjusted to terminate the transmission and reception session of the adjacent BSS at the start of the R-TWT service interval, the two service intervals may overlap at the time when the least common multiple (e.g., 15ms) is reached.

[0077] An R-TWT negotiation method according to one embodiment can resolve the problem of overlapping within each service segment caused by adjacent BSSs independently setting R-TWT service segments among themselves by determining a common R-TWT schedule within adjacent BSSs. Hereinafter, a method for determining a common R-TWT schedule within adjacent BSSs will be described with reference to FIGS. 8 to 18.

[0078]

[0079] FIG. 8 is a diagram illustrating an R-TWT negotiation method between APs according to one embodiment.

[0080] Referring to FIG. 8, according to one embodiment, a first AP (801) (e.g., AP (401) of FIG. 3) and a second AP (802) (e.g., AP (401) of FIG. 3) can form an environment adjacent to each other (e.g., overlapped basic service sets (OBSS)). The first AP (801) can form a first BSS, and the second AP (802) can form a second BSS. The first AP (801) and the second AP (802) share wireless resources, such as frequency resources, with each other and may cause interference between them.

[0081] For convenience of explanation below, it is assumed that the first BSS and the second BSS are adjacent to each other, the STAs included in the first BSS are referred to as the first STAs, and the STAs included in the second BSS are referred to as the second STAs.

[0082] According to one embodiment, the first AP (801) and the second AP (802) can determine a common R-TWT schedule through R-TWT negotiation. According to the common R-TWT schedule, non-member STAs in the first BSS and the second BSS all terminate their transmission and reception sessions before the same R-TWT service interval, and member STAs can attempt to access the medium through competition.

[0083] According to one embodiment, the first AP (801) may transmit a request frame (810) requesting the second AP (802) to negotiate a common R-TWT service period. The request frame (810) may include a first TWT element (target wake time element) for an R-TWT service within the first BSS. For example, the first TWT element may include the duration and interval of a first R-TWT service period that satisfies the quality of service (QOS) requirement of one or more first STAs.

[0084] According to one embodiment, a second AP (802) may receive a request frame (810) from a first AP (801). In response to the request frame (810), the second AP (802) may transmit a response frame (820) to the AP (801). The response frame (820) may include a second TWT element for an R-TWT service within the second BSS. For example, the second TWT element may include the duration and interval of a second R-TWT service segment that satisfies the QoS requirements of one or more second STAs included in the second BSS.

[0085] According to one embodiment, the first AP (801) may receive a response frame (820) from the second AP (802). The first AP (801) and the second AP (802) may negotiate a common R-TWT schedule by transmitting and receiving their respective TWT elements. The first AP (801) and the second AP (802) may determine an R-TWT schedule in which the QoS requirements of the first STA and the second STA are both satisfied, based on the first TWT element and the second TWT element. For example, the first AP (801) and the second AP (802) may negotiate the interval and duration of an R-TWT service interval in which the QoS requirements of the first STA and the second STA are both satisfied. In FIG. 8, the R-TWT negotiation is depicted as being completed via a single request and a single response, but this is merely an example for convenience of explanation, and multiple requests and multiple responses may be required to complete the R-TWT negotiation. For example, if the first AP (801) modifies the first TWT element to satisfy the QoS requirements of the second STAs according to the second TWT element included in the response frame of the second AP (802), and transmits a request frame containing the modified first TWT element to the second AP (802), but the second AP (802) does not accept the modified first TWT element, additional requests and additional responses may be required.

[0086] According to one embodiment, when negotiations regarding a common R-TWT schedule between the first AP (801) and the second AP (802) are completed, the first AP (801) and the second AP (802) may broadcast information regarding the common R-TWT schedule within their respective BSSs. Non-member STAs among the first STAs and the second STAs may terminate their transmission and reception sessions before the start of the common R-TWT service period. Member STAs among the first STAs and the second STAs may attempt to access the medium through competition during the common R-TWT service period. In this way, by determining a common R-TWT schedule between adjacent BSSs, R-TWT efficiency can be improved without causing the problem of overlapping independent R-TWT service periods between adjacent BSSs described through FIG. 7.

[0087]

[0088] FIG. 9 is a diagram illustrating a multi-AP cooperation-based R-TWT negotiation system according to one embodiment.

[0089] Referring to FIG. 9, according to one embodiment, a first AP (801) may form a first BSS containing first STAs (e.g., STA (910-1) and / or STA (910-3)) (e.g., STA (301) of FIG. 3 and / or electronic device (500) of FIG. 5). A second AP (802) may form a second BSS containing second STAs (e.g., STA (920-1) and / or STA (920-3)) (e.g., STA (301) of FIG. 3 and / or electronic device (500) of FIG. 5).

[0090] According to one embodiment, the first AP (801) can obtain (e.g., receive) information regarding the QoS requirements of the first STAs from the first STAs (e.g., STAs requesting membership regarding TWT). The information regarding the QoS requirements may be transmitted via a TWT request frame, which will be described in detail with reference to FIG. 13. Based on the information regarding the QoS requirements of the first STAs, the first AP (801) can calculate an R-TWT service interval that can satisfy the QoS requirements of the first STAs. The first AP (801) can generate a first TWT element according to the R-TWT service interval that can satisfy the QoS requirements of the first STAs. The first TWT element may include the duration and interval of the first R-TWT service interval that satisfies the QoS requirements of the first STAs.

[0091] According to one embodiment, the second AP (802) can obtain (e.g., receive) information regarding the QoS requirements of the second STAs from the second STAs (e.g., a STA requesting membership regarding TWT). Based on the information regarding the QoS requirements of the second STAs, the second AP (802) can calculate an R-TWT service interval that can satisfy the QoS requirements of the second STAs. The second AP (802) can generate a second TWT element according to the R-TWT service interval that can satisfy the QoS requirements of the second STAs. The second TWT element may include the duration and interval of the second R-TWT service interval that satisfies the QoS requirements of the second STAs.

[0092] According to one embodiment, the first AP (801) can perform TWT negotiations with the first STAs based on the first TWT elements. Through TWT negotiations with the first STAs, the first AP (801) can determine an R-TWT schedule (e.g., a schedule independently set within a BSS without considering interference by adjacent BSSs). The first AP (801) and / or the first STAs can perform wireless communication according to the R-TWT schedule.

[0093] According to one embodiment, the first AP (801) may trigger the transmission of a first request frame (e.g., the request frame (810) of FIG. 8) if it detects interference by the second BSS during an R-TWT schedule set at a previous time within the first BSS (e.g., a schedule set independently within the BSS without considering interference by an adjacent BSS). As devices within the adjacent second BSS (e.g., the second AP (802) and / or the second STAs) access the medium during an R-TWT service interval set at a previous time (e.g., the first R-TWT service interval), the member STA included in the first BSS may lose the opportunity to access the medium. The first AP (801) may thus detect whether interference by the second AP (802) and / or the second STAs occurred during the R-TWT service interval set at a previous time. If interference by the second AP (802) and / or the second STAs is detected, the first AP (801) may transmit a request frame (810) for R-TWT negotiation with the second AP (802). The request frame (810) may include a first TWT element.

[0094] According to one embodiment, the second AP (802) can transmit a response frame (820) to the first AP (801) in response to a request frame (810). The second AP (802) can generate a second TWT element by setting a second R-TWT service interval that satisfies the QoS requirements of the second STAs. The second AP (802) can transmit the second TWT element to the first AP (801) by including it in the response frame (820).

[0095] According to one embodiment, the first AP (801) can determine a common R-TWT schedule within the first BSS and the second BSS based on the first TWT element and the second TWT element. The first AP (801) can determine a common R-TWT service interval that simultaneously satisfies the QoS requirements of one or more first STAs included in the first BSS and the QoS requirements of one or more second STAs included in the second BSS based on at least one of the first TWT element and the second TWT element. The first AP (801) can determine a service interval that simultaneously satisfies the QoS requirements of the first STAs and the second STAs as a common R-TWT service interval by considering not only the first R-TWT service interval but also the second R-TWT service interval. For example, if the second R-TWT service interval included in the response frame (820) satisfies the QoS requirements of the first STAs, the first AP (801) may determine the second R-TWT service interval as a common R-TWT service interval. In this case, the first AP (801) may transmit a frame to the second AP (802) to indicate acceptance of the common R-TWT service interval. On the other hand, if the second R-TWT service interval included in the response frame (820) does not satisfy the QoS requirements of the first STAs, the first AP (801) may retransmit to the second AP (802) a request frame containing TWT elements regarding a new R-TWT service interval that satisfies the QoS requirements of the first STAs and the second STAs. If the second AP (802) satisfies the QoS requirements of the second STAs for a new R-TWT service interval, it can send a frame to the first AP (801) to notify it of approval for the common R-TWT service interval.The process of transmitting and receiving the above request frame (810) and / or response frame (820) can be repeated, and an R-TWT schedule to be commonly used within the first BSS and the second BSS can be set.

[0096] According to one embodiment, the request frame (810) and / or the response frame (820) may include a request type field. The request type field may include a TWT setup command field that can set various contexts such as request, suggest, reject, accept, and / or alternate. The first AP (801) and / or the second AP (802) may accept a request regarding TWT elements or propose a new TWT element in response to a request during R-TWT negotiation through the TWT setup command field. The first AP (801) and / or the second AP (802) may reach a final agreement by coordinating TWT elements by sending and receiving the request frame (810) and / or the response frame (820) one or more times with the TWT setup command field set to various contexts. For example, if the interval of the first R-TWT service interval in the request frame (810) does not satisfy the QoS requirements of the second STAs, the second AP (802) may propose a modified second R-TWT service interval. For example, if the duration of the first R-TWT service interval in the request frame (810) does not satisfy the traffic requirements of the second STAs, the second AP (802) may propose to the first AP (801) a duration that can satisfy the traffic requirements of the second STAs.

[0097]

[0098] FIGS. 10a and FIGS. 10b are drawings for illustrating request and / or response frames used in R-TWT negotiation according to one embodiment.

[0099] Specifically, the frame (1000) illustrated in FIG. 10a may be a request frame (e.g., the request frame (810) of FIG. 8) and / or a response frame (e.g., the response frame (820) of FIG. 8) used for R-TWT negotiation between APs (e.g., the first AP (801) and / or the second AP (802) of FIG. 8). The frame (1050) illustrated in FIG. 10b may be a request frame and / or a response frame used for R-TWT negotiation between an AP (e.g., the first AP (801) of FIG. 8) and a STA (e.g., the first STAs (910-1 to 910-3) of FIG. 9).

[0100] Referring to FIG. 10a, according to one embodiment, when interference by the second AP (801) is detected (e.g., interference occurring during the R-TWT service period), the first AP (801) can transmit a frame (1000) to the second AP (802) to negotiate a common R-TWT schedule within the first BSS and the second BSS.

[0101] According to one embodiment, the request frame (1000) may include a TWT element (1010). The TWT element (1010) will be described in detail with reference to FIG. 11 and FIG. 12.

[0102] Referring to FIG. 10b, according to one embodiment, a STA (e.g., first STAs (910-1 to 910-3) and / or second STAs (920-1 to 920-3) of FIG. 9) may transmit a request frame (1050) to an AP (e.g., first AP (801) and second AP (802) of FIG. 8) for TWT negotiation.

[0103] According to one embodiment, the request frame (1050) may include a TWT element (1010) and a QoS characteristic element (1020). If necessary, the TWT element (1010) or the QoS characteristic element (1020) may be excluded from the request frame (1050). For example, if the first AP (801) has obtained the QoS characteristic element (1020) of the first STAs (910-1 to 910-3) through a previous TWT request frame, the next request frame transmitted from the first STAs (910-1 to 910-3) to the first AP (801) may not include the QoS characteristic element (1020). The QoS characteristic element (1020) will be described in detail with reference to FIG. 13.

[0104]

[0105] FIG. 11 is a drawing for explaining a TWT element according to one embodiment.

[0106] Referring to FIG. 11, according to one embodiment, a TWT element (1010) may include an Element ID (1011), Length (1013), Control (1015), and TWT parameter information (1017). FIG. 11 is merely an example of a TWT element (1010), and the TWT element (1010) may include only some of the plurality of fields (1011 to 1017) or include at least one additional field.

[0107] According to one embodiment, the Element ID (1011) may be a field containing information for identifying the TWT element (1010).

[0108] According to one embodiment, Length (1013) may be a field containing information about the total length of the TWT element (1010).

[0109] According to one embodiment, Control (1015) may be a field containing information for controlling TWT operations or TWT schedules. Control (1015) may indicate the purpose of frames transmitted and received during the R-TWT negotiation process (e.g., request, suggest, reject, accept, and / or alternate).

[0110] According to one embodiment, TWT parameter information (1017) may include information about TWT parameters. For example, TWT parameter information (1017) may include a TWT wake time, an interval of the TWT service interval, and / or a duration of the TWT service interval.

[0111]

[0112] FIG. 12 is a diagram illustrating TWT parameter information according to one embodiment.

[0113] Referring to FIG. 12, according to one embodiment, TWT parameter information (1017) may be a broadcast TWT parameter set field format according to IEEE 802.11 (e.g., IEEE 802.11be). TWT parameter information (1017) may include a request type field (1210), a target wake time field, a nominal minimum TWT wake duration field, a TWT wake interval mantissa field, and a broadcast TWT information field (1220). TWT parameter information (1017) may further include a restricted TWT traffic information field (1230). At this time, the request type field (1210) may include a plurality of sub-fields, for example, a TWT request field, a TWT setup command field, a trigger field, a last broadcast parameter set field, a flow type field, a broadcast TWT recommendation field, a TWT wake interval exponent field, and a reserved field.

[0114] According to one embodiment, TWT parameter information (1017) can determine TWT parameters. TWT parameters may include information regarding the R-TWT service interval. The information regarding the R-TWT service interval may include information on the start time of the R-TWT service interval, wake duration information of the R-TWT service interval, and / or interval information of the R-TWT service interval. TWT parameters may be determined by setting the value of one or more fields among a plurality of fields included in the TWT parameter information (1017). The target wake time field of the TWT parameter information (1017) may be set to the time at which the TWT service interval begins, and the nominal minimum TWT wake duration field of the TWT parameter information (1017) may be set to the TWT duration during which the TWT service interval continues (or is maintained). The TWT interval (e.g., the value of the interval) of the TWT service period can be determined by the values ​​set in the TWT wake interval mantissa field and the TWT wake interval exponent field of the TWT parameter information (1017). The TWT wake interval mantissa field may be set with information for the mantissa to determine the TWT interval, and the TWT wake interval exponent field may be set with information for the exponent value to determine the TWT interval with a base of 2. The size of the TWT interval can be determined based on TWT wake interval mantissa x 2 (TWT wake interval exponent).

[0115] According to one embodiment, the broadcast TWT information field (1220) may include a plurality of sub-fields, for example, a restricted TWT traffic info present field, a restricted TWT schedule full field, a reserved field, a broadcast TWT ID field, and a broadcast TWT persistence field. The restricted TWT traffic info present field may be set to 1 when a restricted TWT parameter set exists to indicate that the restricted TWT traffic info field exists. The restricted TWT schedule full field may be set to 1 when there is no possibility that an AP performing R-TWT scheduling will allow new membership in that schedule. The broadcast TWT ID field may include information about the broadcast TWT ID. The broadcast TWT ID field may be used to determine the mapping between the TWT ID and the TWT service interval. The broadcast TWT persistence field may include information about the period during which the broadcast TWT information persists. The broadcast TWT persistence field can contain information about the beacon's period.

[0116] According to one embodiment, the restricted TWT traffic information field (1230) may include a plurality of sub-fields, for example, a traffic information control field, a restricted TWT downlink traffic identifier bitmap field, a restricted TWT uplink traffic identifier bitmap field, and a number of members. The restricted TWT traffic information field (1230) may exist when the value of the restricted TWT traffic information present field is 1. The traffic information control field may include a downlink traffic identifier bitmap valid field, an uplink traffic identifier bitmap valid field, and a reserved field. The downlink traffic identifier bitmap valid field may indicate whether there is valid information in the restricted TWT downlink traffic identifier bitmap field. If the value of the valid field of the downlink traffic ID bitmap is 0, downlink traffic for all traffic IDs is identified as latency-sensitive traffic, and the restricted TWT downlink traffic ID bitmap field may be reserved. The valid field of the uplink traffic ID bitmap may indicate whether there is valid information in the restricted TWT uplink traffic ID bitmap field. If the value of the valid field of the uplink traffic ID bitmap is 0, uplink traffic for all traffic IDs is identified as latency-sensitive traffic, and the restricted TWT uplink traffic ID bitmap field may be reserved.The restricted TWT downlink traffic ID bitmap field and the restricted TWT uplink traffic ID bitmap field can specify which traffic ID (TID) is identified by the TWT scheduling AP or TWT scheduled STA in the downlink and uplink directions, respectively, of a latency-sensitive traffic stream. If the bit position k value of the bitmap is 1, traffic ID k may be classified as a latency-sensitive traffic stream. If the bit position k value of the bitmap is 0, traffic ID k may not be classified as a latency-sensitive traffic stream.

[0117]

[0118] FIG. 13 is a diagram illustrating QoS characteristic elements according to one embodiment.

[0119] Referring to FIG. 13, according to one embodiment, a STA (e.g., STA (910-1 to 910-3) of FIG. 9) can provide a QoS characteristic element (1020) to an AP (e.g., AP (801) of FIG. 8).

[0120] According to one embodiment, the QoS characteristic element (1020) may include a plurality of fields (1301 to 1316). FIG. 13 is merely an example of the QoS characteristic element (1020), and the QoS characteristic element (1020) may include only some of the fields (1301 to 1316) or may include additional new fields (not shown) related to QoS information.

[0121] According to one embodiment, the Element ID (1301) may include information for identifying a QoS characteristic element (1020).

[0122] According to one embodiment, Length (1302) may include information about the total length of the QoS characteristic element (1020).

[0123] According to one embodiment, the Element ID Extension (1303) may include information for identifying a QoS characteristic element (1020) separately from the Element ID (1301).

[0124] According to one embodiment, Control Info (1304) may include information for defining QoS requirements.

[0125] According to one embodiment, the Minimum Service Interval (1305) may include information about the minimum time interval between two service periods.

[0126] According to one embodiment, Maximum Service Interval (1306) may include information about the maximum time interval between two service periods.

[0127] According to one embodiment, the Minimum Data Rate (1307) may include information about the minimum data rate that must be provided for traffic.

[0128] According to one embodiment, the Delay Bound (1308) may include information about the allowable maximum transmission latency for the traffic. Applications that generate high-priority traffic, such as real-time applications (e.g., voice calls), may have a relatively low delay bound value.

[0129] According to one embodiment, the Maximum MSDU (media access control service data unit) size (1309) may include information about the maximum size of a data frame that can be transmitted.

[0130] According to one embodiment, Service Start Time (1310) may include information about the start time of the service.

[0131] According to one embodiment, the Service Start Time LinkID (1311) may include information for managing the services and the start times of the services when there are multiple services within a Wi-Fi network.

[0132] According to one embodiment, the Mean Data Rate (1312) may include information about the average data transmission rate required for traffic.

[0133] According to one embodiment, the Delayed Bound Burst Size (1313) may include information about the maximum size of data that can be transmitted at once when the delay is allowed.

[0134] According to one embodiment, the MSDU Lifetime (1314) may include information about the length of time during which a data packet can be effectively handled within a Wi-Fi network.

[0135] According to one embodiment, MSDU Delivery Info (1315) may include information about specific requirements needed to transmit data.

[0136] According to one embodiment, Medium Time (1316) may include information about the time during which the medium can be occupied for data transmission.

[0137]

[0138] FIG. 14 is a diagram illustrating a TWT request frame according to one embodiment.

[0139] Referring to FIG. 14, according to one embodiment, after the R-TWT negotiation between the first AP (e.g., the first AP (801) of FIG. 8) and the second AP (e.g., the second AP (802) of FIG. 8) is completed, interference may occur from another adjacent BSS (e.g., a third BSS formed by the third AP). The first AP (801) and / or the second AP (802) may perform additional negotiations with the third AP based on the results of the existing R-TWT negotiations. When negotiating with the third AP, the first AP (801) and / or the second AP (802) may transmit a frame (1400) containing the results of the existing R-TWT negotiations to the third AP in order to perform a new R-TWT negotiation based on the results of the existing R-TWT negotiations.

[0140] According to one embodiment, the frame (1400) may be a frame (e.g., the frame (1000) of FIG. 10a) to which an OBSS desired TWT parameter information field (1410) is added. The OBSS desired TWT parameter information field (1410) may include information regarding the results of an existing R-TWT negotiation. The OBSS desired TWT parameter information field (1410) may include the identification numbers of the APs that participated in the R-TWT negotiation and the TWT elements considered during the R-TWT negotiation. For example, if a first AP (801) and a second AP (802) have conducted an R-TWT negotiation, the identification number of the first AP (801) (e.g., BSSID), the identification number of the second AP (802), the first TWT element, and / or the second TWT element may be included in the OBSS desired TWT parameter information field (1410).

[0141] According to one embodiment, the OBSS desired TWT parameter information field (1410) may include a BSSID field (1411), a Time stamp field (1413), a Desired Wake interval field (1415), and a Desired Wake duration (1417). The OBSS desired TWT parameter information field (1410) may include information for each AP separately based on the APs. For example, in FIG. 14, for convenience of explanation, the BSSID field (1411), Time stamp field (1413), Desired Wake interval field (1415), and Desired Wake duration (1417) are each shown as one, but the information for the first AP (801) and the second AP (802) may be stored separately in two fields.

[0142] According to one embodiment, the BSSID field (1411) may include the identification numbers of the APs that participated in the R-TWT negotiation. When additional negotiations occur after the R-TWT negotiation, the identification numbers of the APs that participated in the previous R-TWT negotiation are included in the request frame and transmitted, thereby preventing a situation where a renegotiation is requested against the APs that have already participated in the negotiation. For example, if the first AP (801) and the second AP (802) have conducted an R-TWT negotiation, the BSSID of the first AP (801) and the BSSID of the second AP (802) may be included in the BSSID field (1411).

[0143] According to one embodiment, the time stamp field (1413) may contain time information of the AP. The time stamp field (1413) may be used to synchronize the time of the APs (or BSSs) participating in the R-TWT negotiation. The time information of the AP may be determined based on the time synchronization function (TSF) within the BSS formed by the AP. For example, if the first AP (801) and the second AP (802) have engaged in R-TWT negotiation, the TSF value of the first BSS and the TSF value of the second AP (802) may be included in the time stamp field (1413).

[0144] According to one embodiment, the Desired Wake interval field (1415) may include an interval of an R-TWT service interval that satisfies the QoS requirements of a STA (e.g., member STA) within the BSS according to the TWT element. For example, if the first AP (801) and the second AP (802) have negotiated an R-TWT, the interval of the first R-TWT service interval and the interval of the second R-TWT service interval may be included in the Desired Wake interval field (1415).

[0145] According to one embodiment, the Desired Wake duration (1417) may include the duration of an R-TWT service interval that satisfies the QoS requirements of a STA (e.g., member STA) within the BSS according to the TWT element. For example, if the first AP (801) and the second AP (802) have negotiated an R-TWT, the duration of the first R-TWT service interval and the duration of the second R-TWT service interval may be included in the Desired Wake interval field (1415).

[0146]

[0147] FIGS. 15a and FIGS. 15b are drawings for illustrating various examples of a multi-AP cooperation system according to one embodiment.

[0148] According to one embodiment, in a multi-AP cooperation system, resource utilization efficiency and performance can be improved by adjacent APs exchanging information and / or cooperating. The multi-AP cooperation system may be a system in which APs cooperate 1:1, as illustrated in FIG. 15a.

[0149] Referring to FIG. 15a, according to one embodiment, a multi-AP cooperation system may include a first AP (801) (e.g., AP (401) of FIG. 3) and a second AP (802) (e.g., AP (401) of FIG. 3). The first AP (801) and the second AP (802) may form an OBSS. The first AP (801) and the second AP (802) may perform information exchange and / or cooperation on a 1:1 basis. A specific 1:1 cooperation method will be described below.

[0150] According to one embodiment, the first AP (801) may discover the second AP (802) that has formed an adjacent BSS. The first AP (801) may negotiate with the second AP (802) to establish some form of cooperation (e.g., setting a common R-TWT schedule). For example, if independent R-TWT schedules are determined for the first BSS and the second BSS, interference problems such as those described in FIG. 7 may occur when devices within the BSS attempt to access the media according to each R-TWT schedule. Accordingly, to resolve interference between adjacent BSSs, it may be advantageous to establish a common R-TWT schedule within the adjacent BSS. If the first AP (801) detects interference caused by the second BSS, it may request R-TWT negotiation with the second AP (802).

[0151] According to one embodiment, the first AP (801) may negotiate necessary details with the second AP (802) based on specific cooperation targets. For example, the second AP (802) may participate in R-TWT negotiations in response to a request from the first AP (801). The first AP (801) and the second AP (802) may determine a common R-TWT service interval by exchanging their respective TWT elements necessary to establish a common R-TWT schedule.

[0152]

[0153] FIG. 15b is a diagram illustrating an example of a multi-AP cooperation system according to one embodiment.

[0154] A multi-AP cooperation system may be a system in which multiple APs cooperate by one or more controllers, as illustrated in FIG. 15b.

[0155] Referring to FIG. 15b, a multi-AP cooperation system may include a communication device (1500) and a plurality of APs (801, 802, 803). In order for the plurality of APs (e.g., AP (801), AP (802), AP (803)) to exchange information and / or cooperate with each other, a multi-AP cooperation environment must be established to enable coordination of the plurality of APs. For the APs to be coordinated, links must be formed between the APs, and information necessary for multi-AP cooperation, such as information about the STA associated with each AP, must be shared.

[0156] According to one embodiment, a communication device (1500) can manage and control (or coordinate) a plurality of APs. The communication device (1500) can manage information on BSS configured by each of the plurality of APs and / or information on STAs associated with the BSS. For example, the communication device (1500) can receive information regarding service intervals for performing NPCA from each of the plurality of APs, and can determine a target service interval by synthesizing the information regarding the service intervals. The communication device (1500) can transmit information regarding the determined target service interval to the plurality of APs.

[0157] According to one embodiment, the communication device (1500) can initiate and control multi-AP cooperation. For example, the communication device (1500) can group or select APs (e.g., AP (801), AP (802), AP (803)) to perform information exchange and / or cooperation, and manage links with the APs so that information can be shared among the APs.

[0158] According to one embodiment, AP (801), AP (802), and / or AP (803) can perform the same function as an AP capable of forming a BSS in a wireless LAN system (e.g., wireless LAN system (10) of FIG. 1 and / or wireless LAN system (20) of FIG. 2), can be coordinated by a communication device (1500), and can exchange information and cooperate with each other. For example, AP (801), AP (802), and / or AP (803) can form an association with the communication device (1500) and share information (e.g., control information, management information, data traffic) with the communication device (1500).

[0159] According to one embodiment, the communication device (1500) may be referred to as an AP controller, a master AP, or a sharing AP. The communication device (1500) is a device that controls multi-AP cooperation and may be replaced with various expressions. An AP capable of participating in multi-AP cooperation (e.g., AP (801), AP (802), AP (803)) may be referred to as a slave AP or a shared AP. An AP capable of participating in multi-AP cooperation is a device that performs multi-AP cooperation under the control of the communication device (1500) and may be replaced with various expressions.

[0160] According to one embodiment, the multi-AP cooperation system is not limited to the structure shown in FIG. 15a and FIG. 15b and can be implemented in various forms.

[0161]

[0162] FIG. 16 is a diagram illustrating a method for dividing a common R-TWT SP according to one embodiment and allocating service sections to each AP.

[0163] Referring to FIG. 16, according to one embodiment, a common R-TWT service interval (1610) established between a first AP (e.g., the first AP (801) of FIG. 8) and a second AP (e.g., the second AP (802) of FIG. 8) may include a first service interval (1630) and a second service interval (1650). The common R-TWT service interval (1610) may be divided into a first service interval (1630) and a second service interval (1650). The first service interval (1630) may be assigned to a first BSS, and the second service interval (1650) may be assigned to a second BSS.

[0164] According to one embodiment, the first AP (801) may set a common R-TWT schedule such that the first service interval (1630) is assigned to the first BSS and the second service interval (1650) is assigned to the second BSS. The first service interval (1630) and the second service interval (1650) may be divided in a 1:1 ratio, but are not limited thereto. For example, the first service interval (1630) and the second service interval (1650) may be divided according to the ratio of the traffic requirements of the first STAs (e.g., first STAs within the first BSS) and the traffic requirements of the second STAs (e.g., second STAs within the second BSS). For example, the first service section (1630) and the second service section (1650) may be divided according to the ratio of the number of first STAs (e.g., first STAs in the first BSS) and the number of second STAs (e.g., second STAs in the second BSS).

[0165]

[0166] FIGS. 17a and FIGS. 17b are drawings for explaining an R-TWT negotiation method between three or more APs according to one embodiment.

[0167] For the sake of convenience of explanation, it is assumed that an R-TWT negotiation (e.g., Negotiation 1) between the first AP (801) and the second AP (802) was performed, and that after the R-TWT negotiation, interference by the third AP (803) that formed the third BSS adjacent to the first BSS and / or the second BSS was detected.

[0168] FIG. 17a illustrates a case where the first AP (801) detects the third AP (803) and an R-TWT negotiation (e.g., Negotiation 2) is performed between the first AP (801) and the third AP (803), and FIG. 17b illustrates a case where the second AP (801) detects the third AP (803) and an R-TWT negotiation (e.g., Negotiation 2) is performed between the second AP (801) and the third AP (803).

[0169] Referring to FIG. 17a, according to one embodiment, in a multi-AP cooperation system with a 1:1 structure (e.g., the multi-AP cooperation system of FIG. 15a), if negotiation between multiple APs is required, negotiation between each AP can be triggered sequentially. On the other hand, in a system in which multiple APs (e.g., the first AP (801), the second AP (802), and / or the third AP (803)) cooperate by a controller (e.g., the communication device (1500) of FIG. 15b), the communication device (1500) may receive information (e.g., TWT elements) from the multiple APs and determine a common R-TWT schedule for the multiple APs. Below, a method for negotiation between multiple APs based on a multi-AP cooperation system with a 1:1 structure will be described.

[0170] According to one embodiment, the first AP (801) may detect interference by a third BSS adjacent to the first BSS after negotiating an R-TWT with the second AP (802) (e.g., after determining a common R-TWT schedule). When interference by the third BSS is detected, the first AP (801) may transmit a request frame (e.g., frame (1400) of FIG. 14) containing a third TWT element regarding a common R-TWT schedule to the third AP (803). In response to the request frame, the third AP (803) may transmit a response frame to the first AP (801) containing a TWT element regarding an R-TWT service within the third BSS. In this way, by transmitting and receiving request frames and / or response frames between the first AP (801) and the third AP (803), negotiation regarding an R-TWT schedule (e.g., Negotiation 2) may be performed. In Negotiation 2, additional negotiations are conducted based on the existing R-TWT negotiation results included in the request frame (e.g., the results of the R-TWT negotiation between the first AP (801) and the second AP (802), which are information regarding an R-TWT service interval in which the QoS requirements of the first STA and the second STA are simultaneously satisfied), so the QoS requirements of the second STA can be considered even if the second AP (802) does not participate in the negotiation.

[0171] According to one embodiment, when an R-TWT negotiation between the first AP (801) and the third AP (803) is completed, the first AP (801) can transmit the result of the R-TWT negotiation (e.g., information regarding a new R-TWT schedule) to the second AP (802). Thus, wireless communication can be performed between the first BSS, the second BSS, and the third BSS according to a common R-TWT schedule.

[0172] According to one embodiment, even if the second AP (802) and the third AP (803) are in a hidden relationship, negotiations regarding an R-TWT schedule between the first AP (801) and the second AP (802) (e.g., Negotiation 1) and negotiations regarding an R-TWT schedule between the first AP (801) and the third AP (803) (e.g., Negotiation 2) may be performed. For example, after the negotiation regarding an R-TWT schedule between the first AP (801) and the second AP (802) (e.g., Negotiation 1) is completed, negotiations regarding an R-TWT schedule between the first AP (801) and the third AP (803) (e.g., Negotiation 2) may be performed. As another example, after a negotiation regarding an R-TWT schedule between the first AP (801) and the third AP (803) (e.g., Negotiation 2) is completed, a negotiation regarding an R-TWT schedule between the first AP (801) and the second AP (802) (e.g., Negotiation 1) may be performed. Wireless communication may be performed in the first BSS, the second BSS, and the third BSS according to a common R-TWT schedule.

[0173] According to one embodiment, whether the second AP (802) and the third AP (803) are in a hidden relationship or not, when it is necessary to align the R-TWT schedule between the first AP (801) and the second AP (802) and the R-TWT schedule between the first AP (801) and the third AP (803) (e.g., when they need to operate a common R-TWT schedule), negotiations regarding the R-TWT schedule between the first AP (801) and the second AP (802) (e.g., Negotiation 1) and negotiations regarding the R-TWT schedule between the first AP (801) and the third AP (803) (e.g., Negotiation 2) may be performed. Referring to FIG. 17b, according to one embodiment, the second AP (802), rather than the first AP (801), may detect interference by the third AP (803). In this case, an R-TWT negotiation is performed between the second AP (802) and the third AP (803), and the result of the R-TWT negotiation can be transmitted to the first AP (801). That is, if the existing R-TWT negotiation (e.g., Negotiation 1) is completed, a new R-TWT negotiation (e.g., Negotiation 2) can be performed regardless of the entity detecting interference by the new BSS, and since the new R-TWT negotiation is performed based on the result of the existing R-TWT negotiation, the QoS requirements of STAs within the BSS that did not participate in the negotiation in the new R-TWT negotiation can also be satisfied. In particular, in FIG. 17b, even if the third AP (803) corresponds to a hidden BSS from the perspective of the first AP (801), the first AP (801) can receive the result of the new R-TWT negotiation from the second AP (802), so the new R-TWT negotiation can be performed normally even if it is a hidden BSS.

[0174]

[0175] FIG. 18 is an example of a flowchart of an R-TWT negotiation method according to one embodiment.

[0176] Referring to FIG. 18, operations 1810 through 1870 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of each operation (1810 to 1870) may be changed, and at least two operations may be performed in parallel.

[0177] In operation 1810, an electronic device (e.g., the first AP (801) of FIG. 8) may transmit a first request frame (e.g., the request frame (810) of FIG. 8) containing a first TWT element (target wake time element) for a restricted target wake time (R-TWT) service within the first BSS to an AP (e.g., the second AP (802) of FIG. 8) that has formed a second BSS adjacent to the first BSS (basic service set) formed by the electronic device (e.g., the first AP (801)). The electronic device (e.g., the first AP (801)) may trigger the transmission of the first request frame (e.g., the request frame (810) of FIG. 8) if it detects interference by the second BSS during an R-TWT schedule set at a previous time within the first BSS (e.g., a schedule set independently within the BSS without considering interference by an adjacent BSS). The first TWT element may be generated based on information regarding the QoS requirements of the first STAs. The first TWT element may include information regarding the first R-TWT service interval (e.g., duration and / or interval) that satisfies the QoS requirements of the first STAs.

[0178] In operation 1830, an electronic device (e.g., a first AP (801)) may receive a first response frame (e.g., a response frame (820) of FIG. 8) containing a second TWT element for an R-TWT service within the second BSS from an AP (e.g., a second AP (802)). The second TWT element may be generated based on information regarding the QoS requirements of the second STAs. The second TWT element may include information regarding a second R-TWT service interval (e.g., duration and / or interval) that satisfies the QoS requirements of the second STAs.

[0179] In operation 1850, an electronic device (e.g., a first AP (801)) can determine a common R-TWT schedule within the first BSS and the second BSS through negotiation with an AP (e.g., a second AP (802)) based on a first TWT element and a second TWT element. The electronic device (e.g., a first AP (801)) can determine a common R-TWT service interval that simultaneously satisfies the QoS requirements of the first STAs and the QoS requirements of the second STAs based on at least one of the first TWT element and the second TWT element.

[0180] In operation 1870, an electronic device (e.g., the first AP (801)) may broadcast information regarding a common R-TWT schedule within the first BSS. The first STAs may perform wireless communication according to the common R-TWT schedule. For example, non-member STAs among the first STAs may terminate their transmit / receive sessions before the start of the common R-TWT service period. Member STAs among the first STAs may attempt to access the medium through competition during the common R-TWT service period.

[0181]

[0182] FIG. 19 is a block diagram of an electronic device in a network environment according to one embodiment.

[0183] Referring to FIG. 19, in a network environment (1900), an electronic device (1901) (e.g., AP (401) of FIG. 3, electronic device (400) of FIG. 4, and / or the first AP (801) of FIG. 8) may communicate with an electronic device (1902) through a first network (1998) (e.g., a short-range wireless communication network) or may communicate with at least one of an electronic device (1904) or a server (1908) through a second network (1999) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (1901) may communicate with the electronic device (1904) through the server (1908). According to one embodiment, the electronic device (1901) may include a processor (1920), memory (1930), input module (1950), sound output module (1955), display module (1960), audio module (1970), sensor module (1976), interface (1977), connection terminal (1978), haptic module (1979), camera module (1980), power management module (1988), battery (1989), communication module (1990), subscriber identification module (1996), or antenna module (1997). In some embodiments, at least one of these components (e.g., connection terminal (1978)) may be omitted from the electronic device (1901), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (1976), camera module (1980), or antenna module (1997)) may be integrated into a single component (e.g., display module (1960)).

[0184] The processor (1920) can, for example, execute software (e.g., program (1940)) to control at least one other component (e.g., hardware or software component) of the electronic device (1901) connected to the processor (1920) and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (1920) can store commands or data received from other components (e.g., sensor module (1976) or communication module (1990)) in volatile memory (1932), process the commands or data stored in volatile memory (1932), and store the resulting data in non-volatile memory (1934). According to one embodiment, the processor (1920) may include a main processor (1921) (e.g., a central processing unit or an application processor) or an auxiliary processor (1923) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (1901) includes a main processor (1921) and an auxiliary processor (1923), the auxiliary processor (1923) may be configured to use less power than the main processor (1921) or to be specialized for a designated function. The auxiliary processor (1923) may be implemented separately from the main processor (1921) or as part thereof.

[0185] The auxiliary processor (1923) may control at least some of the functions or states associated with at least one component of the electronic device (1901) (e.g., display module (1960), sensor module (1976), or communication module (1990)) on behalf of the main processor (1921) while the main processor (1921) is in an inactive (e.g., sleep) state, or together with the main processor (1921) while the main processor (1921) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (1923) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (1980) or communication module (1990)). According to one embodiment, the auxiliary processor (1923) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (1901) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (1908)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

[0186] The memory (1930) may store various data used by at least one component of the electronic device (1901) (e.g., a processor (1920) or a sensor module (1976)). The data may include, for example, software (e.g., a program (1940)) and input or output data for related commands. The memory (1930) may include volatile memory (1932) or non-volatile memory (1934).

[0187] The program (1940) may be stored as software in memory (1930) and may include, for example, an operating system (1942), middleware (1944), or an application (1946).

[0188] The input module (1950) can receive commands or data to be used for a component of the electronic device (1901) (e.g., processor (1920)) from outside the electronic device (1901) (e.g., user). The input module (1950) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0189] The sound output module (1955) can output a sound signal to the outside of the electronic device (1901). The sound output module (1955) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

[0190] The display module (1960) can visually provide information to an external (e.g., user) of the electronic device (1901). The display module (1960) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (1960) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.

[0191] The audio module (1970) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (1970) can acquire sound through an input module (1950) or output sound through an audio output module (1955) or an external electronic device (e.g., electronic device (1902)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (1901).

[0192] The sensor module (1976) can detect the operating state of the electronic device (1901) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (1976) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0193] The interface (1977) may support one or more specified protocols that can be used for the electronic device (1901) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (1902)). According to one embodiment, the interface (1977) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0194] The connection terminal (1978) may include a connector through which the electronic device (1901) can be physically connected to an external electronic device (e.g., electronic device (1902)). According to one embodiment, the connection terminal (1978) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0195] The haptic module (1979) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (1979) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

[0196] The camera module (1980) can capture still images and video. According to one embodiment, the camera module (1980) may include one or more lenses, image sensors, image signal processors, or flashes.

[0197] The power management module (1988) can manage the power supplied to the electronic device (1901). According to one embodiment, the power management module (1988) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0198] The battery (1989) can supply power to at least one component of the electronic device (1901). According to one embodiment, the battery (1989) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0199] The communication module (1990) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (1901) and an external electronic device (e.g., electronic device (1902), electronic device (1904), or server (1908)), and the performance of communication through the established communication channel. The communication module (1990) may include one or more communication processors that operate independently of the processor (1920) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (1990) may include a wireless communication module (1992) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (1994) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (1904) through a first network (1998) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (1999) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (1992) can identify or authenticate the electronic device (1901) within a communication network such as the first network (1998) or the second network (1999) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (1996).

[0200] The wireless communication module (1992) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. The NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (1992) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (1992) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (1992) can support various requirements specified in the electronic device (1901), external electronic device (e.g., electronic device (1904)), or network system (e.g., second network (1999)). According to one embodiment, the wireless communication module (1992) can support a Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for realizing URLLC.

[0201] An antenna module (1997) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (1997) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (1997) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (1998) or a second network (1999), may be selected from the plurality of antennas, for example, by a communication module (1990). A signal or power may be transmitted or received between the communication module (1990) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (1997).

[0202] According to various embodiments, the antenna module (1997) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

[0203] At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.

[0204] According to one embodiment, commands or data may be transmitted or received between the electronic device (1901) and an external electronic device (1904) through a server (1908) connected to a second network (1999). Each of the external electronic devices (1902, or 1904) may be the same or a different type of device as the electronic device (1901). According to one embodiment, all or part of the operations performed on the electronic device (1901) may be performed on one or more of the external electronic devices (1902, 1904, or 1908). For example, if the electronic device (1901) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (1901) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (1901). The electronic device (1901) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (1901) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (1904) may include an Internet of Things (IoT) device. The server (1908) may be an intelligent server using machine learning and / or neural networks.According to one embodiment, an external electronic device (1904) or server (1908) may be included within the second network (1999). The electronic device (1901) may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0205]

[0206] An electronic device according to one embodiment (e.g., AP (401) of FIG. 3, electronic device (400) of FIG. 4, first AP (801) of FIG. 8, electronic device (1901) of FIG. 19)) may include a wireless communication circuit (e.g., transceiver (490) of FIG. 4, communication module (1990) of FIG. 19). The electronic device (400, 401, 801, 1901) may include at least one processor including a processing circuit (e.g., processor (410) of FIG. 4, processor (1920) of FIG. 19). The electronic device (400, 401, 801, 1901) may include a memory for storing instructions (e.g., memory (420) of FIG. 4, memory (1930) of FIG. 19). When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may be caused to transmit a first request frame containing a first target wake time element for an R-TWT (restricted target wake time) service within the first BSS through the wireless communication circuit (490, 1990) to a first access point (e.g., the second AP (802) of FIG. 8) that forms a second BSS adjacent to the first basic service set (BSS) formed by the electronic device (400, 401, 801, 1901). When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may receive a first response frame containing a second TWT element for an R-TWT service within the second BSS from the first AP (802) through the wireless communication circuit (490, 1990).When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may determine a common R-TWT schedule within the first BSS and the second BSS through negotiation with the first AP (802) based on the first TWT element and the second TWT element. When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may broadcast information regarding the common R-TWT schedule within the first BSS.

[0207] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may generate the first TWT element based on quality of service (QOS) requirement information of one or more first STAs (301, 500, 910) included in the first BSS.

[0208] According to one embodiment, the first TWT element may include the duration and interval of a first R-TWT service period that satisfies the quality of service (QOS) requirement of one or more first STAs (301, 500, 910).

[0209] According to one embodiment, the second TWT element may include a duration and interval of a second R-TWT service interval that satisfies the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS.

[0210] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may trigger the transmission of the first request frame when interference by the second BSS is detected during an R-TWT schedule set at an earlier time within the first BSS.

[0211] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may determine a common R-TWT service interval that simultaneously satisfies the QoS requirements of one or more first STAs (301, 500, 910) included in the first BSS and the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS, based on at least one of the first TWT element and the second TWT element.

[0212] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may be configured to divide the common R-TWT service interval into a first service interval and a second service interval. When the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may be configured to set the common R-TWT schedule such that the first service interval is assigned to the first BSS and the second service interval is assigned to the second BSS.

[0213] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may be configured to transmit a second request frame containing a third TWT element regarding the common R-TWT schedule to a second AP (803) that formed the third BSS, if interference by a third BSS adjacent to at least one of the first BSS and the second BSS is detected after the common R-TWT schedule has been determined. When the instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may be configured to receive a second response frame containing a fourth TWT element regarding the R-TWT service within the third BSS from the second AP (803). When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) may determine a common R-TWT schedule within the first BSS, the second BSS, and the third BSS based on at least one of the third TWT element and the fourth TWT element.

[0214] According to one embodiment, the second request frame may include an identification number of the electronic device (400, 401, 801, 1901), the first TWT element, the identification number of the first AP (802), and the second TWT element.

[0215] According to one embodiment, the fourth TWT element may include the duration and interval of a third R-TWT service interval that satisfies the QoS requirements of one or more third STAs included in the third BSS.

[0216] A method of operation of an electronic device according to one embodiment (e.g., AP (401) of FIG. 3, electronic device (400) of FIG. 4, first AP (801) of FIG. 8, electronic device (1901) of FIG. 19) may include the operation of transmitting a first request frame containing a first TWT element (target wake time element) for an R-TWT (restricted target wake time) service within the first BSS to a first AP (access point) (e.g., second AP (802) of FIG. 8) that forms a second BSS adjacent to a first BSS (basic service set) formed by the electronic device (400, 401, 801, 1901). The method of operation may include the operation of receiving a first response frame containing a second TWT element for an R-TWT service within the second BSS from the first AP (802). The above operation method may include an operation of determining a common R-TWT schedule within the first BSS and the second BSS through negotiation with the first AP (802) based on the first TWT element and the second TWT element. The above operation method may include an operation of broadcasting information regarding the common R-TWT schedule within the first BSS.

[0217] According to one embodiment, the operation of transmitting the first request frame may include the operation of generating the first TWT element based on quality of service (QOS) requirement information of one or more first STAs (301, 500, 910) included in the first BSS.

[0218] According to one embodiment, the first TWT element may include the duration and interval of a first R-TWT service period that satisfies the quality of service (QOS) requirement of one or more first STAs (301, 500, 910).

[0219] According to one embodiment, the second TWT element may include a duration and interval of a second R-TWT service interval that satisfies the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS.

[0220] According to one embodiment, the operation of transmitting the first request frame may include an operation of triggering the transmission of the first request frame when interference by the second BSS is detected during an R-TWT schedule set at a previous time point within the first BSS.

[0221] According to one embodiment, the operation of determining the common R-TWT schedule may include the operation of determining a common R-TWT service interval that simultaneously satisfies the QoS requirements of one or more first STAs (301, 500, 910) included in the first BSS and the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS, based on at least one of the first TWT element and the second TWT element.

[0222] According to one embodiment, the operation of determining the common R-TWT service interval may include the operation of dividing the common R-TWT service interval into a first service interval and a second service interval. The operation of determining the common R-TWT service interval may include the operation of setting the common R-TWT schedule such that the first service interval is assigned to the first BSS and the second service interval is assigned to the second BSS.

[0223] According to one embodiment, the operation method may include, after determining the common R-TWT schedule, when interference by a third BSS adjacent to at least one of the first BSS and the second BSS is detected, transmitting a second request frame containing a third TWT element regarding the common R-TWT schedule to a second AP (803) that formed the third BSS. The operation method may include receiving a second response frame containing a fourth TWT element regarding the R-TWT service within the third BSS from the second AP (803). The operation method may include determining a common R-TWT schedule within the first BSS, the second BSS, and the third BSS based on at least one of the third TWT element and the fourth TWT element.

[0224] According to one embodiment, the second request frame may include an identification number of the electronic device (400, 401, 801, 1901), the first TWT element, the identification number of the first AP (802), and the second TWT element.

[0225] According to one embodiment, the fourth TWT element may include the duration and interval of a third R-TWT service interval that satisfies the QoS requirements of one or more third STAs included in the third BSS.

[0226] An electronic device according to one embodiment (e.g., a communication device (1500) of FIG. 15b) may include a wireless communication circuit. The electronic device may include at least one processor including a processing circuit. The electronic device may include a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the electronic device (1500) may be able to receive a first TWT element for an R-TWT service within the first BSS from a first AP (e.g., AP (401) of FIG. 3, the electronic device (400) of FIG. 4, the first AP (801) of FIG. 8, the electronic device (1901) of FIG. 19) that forms a first BSS (basic service set). When the above instructions are executed individually or collectively by the at least one processor, the electronic device (1500) may receive a second TWT element for an R-TWT service within the second BSS from a second AP (e.g., the second AP (802) of FIG. 8) that forms a second BSS adjacent to the first BSS. When the above instructions are executed individually or collectively by the at least one processor, the electronic device (1500) may determine a common R-TWT schedule within the first BSS and the second BSS based on the first TWT element and the second TWT element. When the above instructions are executed individually or collectively by the at least one processor, the electronic device (1500) may transmit information regarding the common R-TWT schedule to the first AP and the second AP.

[0227]

[0228] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0229] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0230] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0231] Various embodiments of the present document may be implemented as software (e.g., program (1740)) comprising one or more instructions stored in a storage medium (e.g., internal memory (1736) or external memory (1738)) readable by a machine (e.g., electronic device (1701)). For example, a processor (e.g., processor (1720)) of the machine (e.g., electronic device (1701)) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0232] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0233] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0234]

[0235] - Explanation of the symbols

[0236] 400, 401, 701, 702, 801, 802: AP

[0237] 301, 500, 910-1, 910-3, 920-1, 920-3: STA

[0238] 1000: Frame

[0239] 1010: TWT element

Claims

1. In an electronic device (400, 401, 801, 1901), Wireless communication circuit (490, 1990); At least one processor (410, 1920) including a processing circuit; and Memory for storing instructions (420, 1930) Includes, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, A first request frame including a first TWT element (target wake time element) for an R-TWT (restricted target wake time) service within the first BSS is transmitted through the wireless communication circuit to a first AP (access point) (802) that forms a second BSS adjacent to a first BSS (basic service set) formed by the electronic device (400, 401, 801, 1901), and From the first AP (802), a first response frame containing a second TWT element for the R-TWT service within the second BSS is received through the wireless communication circuit (490, 1990), and Based on the first TWT element and the second TWT element, a common R-TWT schedule within the first BSS and the second BSS is determined through negotiation with the first AP (802), and An electronic device (400, 401, 801, 1901) that broadcasts information regarding the above common R-TWT schedule into the above first BSS.

2. In Paragraph 1, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, An electronic device (400, 401, 801, 1901) that generates the first TWT element based on quality of service (QOS) requirement information of one or more first STAs (301, 500, 910) included in the first BSS.

3. In either Paragraph 1 or Paragraph 2, The above first TWT element is, The duration and interval of a first R-TWT service period that satisfies the quality of service (QoS) requirement of one or more of the first STAs (301, 500, 910) above Electronic device (400, 401, 801, 1901) including 4. In any one of paragraphs 1 through 3, The above second TWT element is, Duration and interval of the second R-TWT service interval that satisfies the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS above. Electronic device (400, 401, 801, 1901) including 5. In any one of paragraphs 1 through 4, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, An electronic device (400, 401, 801, 1901) that triggers the transmission of the first request frame when interference by the second BSS is detected during an R-TWT schedule set at a previous time point within the first BSS.

6. In any one of paragraphs 1 through 5, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, An electronic device (400, 401, 801, 1901) for determining a common R-TWT service interval that simultaneously satisfies the QoS requirements of one or more first STAs (301, 500, 910) included in the first BSS and the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS, based on at least one of the first TWT element and the second TWT element.

7. In any one of paragraphs 1 through 6, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, The above common R-TWT service section is divided into a first service section and a second service section, and An electronic device (400, 401, 801, 1901) for setting the common R-TWT schedule such that the first service interval is assigned to the first BSS and the second service interval is assigned to the second BSS.

8. In any one of paragraphs 1 through 7, When the above instructions are executed individually or collectively by the at least one processor (410, 1920), the electronic device (400, 401, 801, 1901) causes, After determining the common R-TWT schedule, if interference by a third BSS adjacent to at least one of the first BSS and the second BSS is detected, a second request frame containing a third TWT element regarding the common R-TWT schedule is transmitted to the second AP (803) that formed the third BSS, and Receive a second response frame containing a fourth TWT element for the R-TWT service in the third BSS from the second AP (803), and An electronic device (400, 401, 801, 1901) for determining a common R-TWT schedule within the first BSS, the second BSS, and the third BSS based on at least one of the third TWT element and the fourth TWT element.

9. In any one of paragraphs 1 through 8, The above second request frame is, The identification number of the electronic device (400, 401, 801, 1901), the first TWT element, the identification number of the first AP (802), and the second TWT element Electronic device (400, 401, 801, 1901) including 10. In any one of paragraphs 1 through 9, The above-mentioned fourth TWT element is, Duration and interval of the third R-TWT service interval that satisfies the QoS requirements of one or more third STAs included in the above third BSS. Electronic device (400, 401, 801, 1901) including 11. In a method of operating an electronic device (400, 401, 801, 1901), The operation of transmitting a first request frame including a first TWT element (target wake time element) for an R-TWT (restricted target wake time) service within the first BSS to a first AP (access point) (802) that forms a second BSS adjacent to a first BSS (basic service set) formed by the electronic devices (400, 401, 801, 1901); The operation of receiving a first response frame containing a second TWT element for an R-TWT service within the second BSS from the first AP (802); An operation to determine a common R-TWT schedule within the first BSS and the second BSS through negotiation with the first AP (802) based on the first TWT element and the second TWT element; and The operation of broadcasting information regarding the above common R-TWT schedule into the above first BSS. A method of operation including 12. In Paragraph 11, The operation of transmitting the above first request frame is, An operation to generate the first TWT element based on quality of service (QoS) requirement information of one or more first STAs (301, 500, 910) included in the first BSS. A method of operation including 13. In either of Paragraphs 11 and 12, The above first TWT element is, The duration and interval of a first R-TWT service period that satisfies the quality of service (QoS) requirement of one or more of the first STAs (301, 500, 910) above A method of operation including 14. In any one of paragraphs 11 through 13, The above second TWT element is, Duration and interval of the second R-TWT service interval that satisfies the QoS requirements of one or more second STAs (301, 500, 920) included in the second BSS above. A method of operation including 15. In any one of paragraphs 11 through 14, The operation of transmitting the above first request frame is, An operation to trigger the transmission of the first request frame when interference by the second BSS is detected during the R-TWT schedule set at a previous time point within the first BSS. A method of operation including