Method, architecture, apparatus and system for target wake time work for multi-AP negotiation

By improving the TWT parameter set and control field format, the target wake-up time negotiation mechanism for multi-AP negotiation was optimized, solving the problems of resource waste and low efficiency in the existing technology, and achieving more efficient device wake-up time negotiation and throughput improvement.

CN120917822APending Publication Date: 2025-11-07INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480024498.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-02-23
Filing Date
2024-02-26
Publication Date
2025-11-07

AI Technical Summary

Technical Problem

Existing methods for negotiating target wake-up time (TWT) in multi-access point (AP) systems suffer from inefficiency and resource waste, especially during multi-AP negotiation, where it is difficult to effectively coordinate wake-up times to optimize energy consumption and throughput.

Method used

The improved TWT parameter set field and enhanced control field format enable a negotiation mechanism between APs, optimize the target wake-up time negotiation process, including negotiation of broadcast and individual TWT parameter sets, support overlapping and non-overlapping TWT operation, and enhance the frame exchange mechanism to improve resource utilization.

Benefits of technology

It improves the efficiency of multi-AP negotiation in wireless communication systems, optimizes device wake-up time negotiation, reduces power consumption, and increases system throughput.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120917822A_ABST
    Figure CN120917822A_ABST
Patent Text Reader

Abstract

Multiple access points (APs) may operate within the same coordinated multi-AP (C-MAP) set and may have overlapping service areas and overlapping target wake time (TWT) service cycles (SPs), where the TWT allows the APs to negotiate wake periods during which stations (STAs) and the APs may transmit and receive, otherwise in a power saving mode. In order to minimize access contention for a wireless radio medium between an STA and an AP, and to maximize the availability of the STA and the AP, particularly in an environment where ultra high reliability (UHR) functions, a mechanism is disclosed that enables the negotiation of TWT operating parameters between APs in a C-MAP.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 447,795, filed February 23, 2023, which is incorporated herein by reference. BACKGROUND

[0002] The present disclosure relates generally to the fields of communication, software, and coding, including for example, methods, architectures, apparatuses, and systems related to target wake-up time operation negotiation with multiple APs. SUMMARY

[0003] Methods and apparatuses for multiple access point (AP) negotiation of target wake-up time (TWT) operation are discussed and claimed in accordance with the appended claims. BRIEF DESCRIPTION OF DRAWINGS

[0004] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings. Like reference numerals indicate like elements in the figures, as is common practice. Similarly, the drawings are not necessarily drawn to scale, with emphasis instead being placed upon illustrating the principles of the disclosure. In the drawings: Figure 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments can be implemented; Figure 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A Figure 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system illustrated in Figure 1A Figure 1D is a system diagram illustrating yet another example RAN and yet another example CN that can be used within the communications system illustrated in Figure 1A Figure 2 illustrates an example of individual TWT operation defined in 802.11ax; Figure 3 illustrates an example of broadcast TWT operation defined in 802.11ax; Figure 4 illustrates an example architecture for neighboring APs with overlapping service areas to negotiate TWT; Figure 5a ​​​An example enhanced control field format in an enhanced TWT element is illustrated; Figure 5b An example modified individual TWT parameter set field is illustrated; Figure 5c A modified broadcast TWT parameter set field is illustrated; Figure 6 An example explanation of the negotiation type subfield and target wake-up time, TWT wake-up interval mantissa, and TWT wake-up interval exponent subfields in the inter-AP negotiation subfield in the enhanced control field is illustrated where the inter-AP negotiation subfield is equal to 1; Figure 7 An example of a modified broadcast TWT recommendation field for a broadcast TWT element is illustrated. Figure 8 An example of an enhanced TWT frame exchange for TWT negotiation between APs - overlapping TWT (overlapping operating channels for the overlapping TWT SP and the AP1 TWT and AP2 TWT) is illustrated; Figure 9 An example of an enhanced TWT frame exchange for TWT negotiation between APs - non-overlapping TWT is illustrated; Figure 10 An example of negotiated individual TWT operation at an AP is illustrated; Figure 11 An example of negotiated individual TWT operation at an AP with extended doze duration is illustrated; Figure 12 An example architecture of a MAP for power saving (doze) mode negotiation is illustrated; Figure 13 An example of a modified broadcast TWT parameter set field format is illustrated; Figure 14 An example of an enhanced TWT frame exchange for TWT negotiation between APs - power save time / duration negotiation is illustrated; and Figure 15 is a flow diagram illustrating a method according to one embodiment. DETAILED DESCRIPTION

[0005] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples can be practiced without some or all of these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Also, embodiments and examples not specifically described herein can be implemented in conjunction with the embodiments and other examples specifically described, implied, and / or otherwise provided (collectively, “provided”) herein. Although various embodiments are described and / or claimed herein, it should be understood that any embodiment described and / or claimed herein can be implemented in any combination of hardware, software, firmware, and / or other approaches. Although various embodiments are described and / or claimed herein, it should be understood that any embodiment described and / or claimed herein can be implemented in any combination of hardware, software, firmware, and / or other approaches.

[0006] Abbreviations and Acronyms: AIFS arbitration interframe space AP access point BSS basic service set CDMA code division multiple access C-MAP coordinated multi-access point CSMA / CA carrier sense multiple access with collision avoidance CN core network DIFS distributed interframe space DL downlink DLS direct link setup DS distributed system EHT extremely high throughput HT high throughput ID identifier IBSS independent BSS IFFT inverse fast fourier transform MAC medium access control MLD multi-link device MTC metering type control PS power save (mode) PSR parameterized spatial reuse QoS quality of service RAN radio access network RB resource block RAT radio access technology RF radio frequency RIFS reduced interframe space R-TWT restricted target wake time RX receive / reception SP service period SG study group SIFS short interframe space STA station TBTT target beacon transmission time TDLS tunneled DLS TSF timing synchronization function TVWS TV white space TWT target wake time TX transmit / transmission TXOP transmit opportunity UE user equipment (see also WTRU) UHR ultra high reliability UL uplink VHT very HT WLAN wireless local area network WTRU wireless transmit receive unit (see also UE, STA).

[0007] Figure 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform spread orthogonal frequency division multiplexing (ZT-UW-DFT-S-OFDM), unique-word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0008] As Figure 1AAs shown, the communication system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which can be referred to as a "station" (STA)) can be configured to transmit and / or receive wireless signals and can include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot or other wireless devices operating in an industrial and / or an automated processing chain environments), a consumer electronics, a device operating on a commercial and / or industrial wireless network, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.

[0009] The communication system 100 can also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b can be a base transceiver station (BTS), a Node-B, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation Node-B (such as gNode Bs (gNB)), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b can include any number of interconnected base stations and / or network elements.

[0010] The base stations 114a can be part of the RAN 104, which can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base stations 114a and / or the base stations 114b can be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which can be referred to as a cell (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrums. A cell can provide wireless service to a particular geographic area that can be relatively fixed, or can vary as users in the cell move throughout the network. The cell can further be divided into cell sectors. For example, a cell associated with a base station 114a can be divided into three sectors. Thus, in one embodiment, the base station 114a can include three transceivers, one for each sector of the cell. In one embodiment, the base station 114a can employ multiple-input multiple-output (MIMO) techniques, and can use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in desired spatial directions.

[0011] The base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over the air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 can be established using any suitable radio access technology (RAT).

[0012] More specifically, as noted above, the communications system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c can implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish the air interface 116 using wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

[0013] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-A Pro.

[0014] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement a radio technology such as NR Radio Access, which can establish the air interface 116 using NR.

[0015] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base station 114a and WTRUs 102a, 102b, 102c can implement LTE wireless access and NR wireless access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., a eNB and a gNB).

[0016] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0017] For example, Figure 1AThe base station 114b in the embodiment can be a wireless router, Home Node B, Home eNode B, or access point, for example, and can utilize any suitable RAT for facilitating wireless connectivity access in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. As shown, the base station 114b can be directly connected to the Internet 110. Thus, the base station 114b can not be required to access the Internet 110 via the CN 106. Figure 1A

[0018] The RAN 104 can be in communication with the CN 106, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data can have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 can provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in Figure 1A Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 can be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which can employ NR radio technology, the CN 106 can also be in communication with another RAN (not shown) employing 5G GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0019] ​CN 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 can include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 can include a global system of interconnected computer networks and devices that use the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the internet protocol suite to communicate with one another. The networks 112 can include wired or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 can include another CN that employs a RAT different from that of the RAN 104.

[0020] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 can include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d can include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in Figure 1 A can be configured to communicate with the base station 114a, which can employ a cellular-based radio technology, and with the base station 114b, which can employ an IEEE 802 radio technology. Figure 1A The WTRU 102c, as shown in Figure 1 B, can be configured to communicate as described herein with the base station 114c, which can employ a radio technology such as IEEE 802.11, and with the base station 114d, which can employ a radio technology such as IEEE 802.15 or ZIGBEE. In one embodiment, the WTRU 102c can include a plurality of transceivers for communicating with a plurality of base stations. For example, WTRU 102c can include a first transceiver configured to communicate as described herein with the base station 114c, and a second transceiver configured to communicate as described herein with the base station 114d.

[0021] Figure 1B Figure 1 C is a system diagram of an example WTRU 102. As shown in Figure 1 C, the WTRU 102 can include a plurality of components configured to carry out various functions (e.g., software components, hardware components, etc.). For example, as shown in Figure 1 C, the WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It should be appreciated that the WTRU 102 can include any sub-combination of the foregoing, in Figure 1B

[0022] ​The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but can be integrated together in an electronic package or chip.

[0023] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 can be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0024] Although the transmit / receive element 122 is depicted in the WTRU 102 Figure 1B In one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) to facilitate increasing the WTRU's 102 capacity.

[0025] The transceiver 120 can be configured to modulate information to be transmitted by the transmit / receive element 122 and to demodulate information received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode capabilities. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0026] The processor 118 of the WTRU 102 can be coupled to, and can receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 can include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 can access information from, and store data in, a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0027] The processor 118 can receive power from the power source 134, and can be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0028] The processor 118 can also be coupled to the GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or

[0029] The processor 118 can further be coupled to other peripherals 138, which can include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 can include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, an electronic game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 can include one or more sensors. The sensors can be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a posture sensor, a biological sensor, a humidity sensor, and the like.

[0030] The WTRU 102 can include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) can be concurrent and / or simultaneous. The full duplex radio can include an interference management unit to reduce and / or eliminate self-interference and / or cross- interference that can occur during concurrent transmission and reception. In one embodiment, the WTRU 102 can include a half duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)) are time divided, e.g., using a single receiver chain.

[0031] Figure 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 can employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 can also be in communication with the CN 106.

[0032] The RAN 104 can include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 can include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c can implement MIMO technology. Thus, the eNode-B 160a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0033] Each of the eNode-Bs 160a, 160b, 160c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown, the eNode-Bs 160a, 160b, 160c can communicate with one another over an X2 interface. Figure 1C

[0034] Figure 1C The CN 106 shown in FIG. 10 can include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0035] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an SI interface and can serve as a control node. For example, the MME 162 can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 can provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0036] ​The SGW 164 can be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0037] The SGW 164 can be connected to the PGW 166, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0038] The CN 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 can include circuit-switched telephone networks that provide infrastructure for the provision of voice, video, and / or data services to users. The CN 106 can include IP gateways, such as an IP Multimedia Subsystem (IMS), that serve as interfaces between the CN 106 and the PSTN 108. The CN 106 can also include serving as gateways to other networks 112, such as networks that are owned and / or operated by other service providers.

[0039] Although WTRUs are described in Figures 1A-1D representative embodiments as wireless terminals, it is contemplated that in certain representative embodiments such terminals can use, for example, wired communication interfaces with communication networks.

[0040] In representative embodiments, the other network 112 can be a WLAN.

[0041] A WLAN in Infrastructure Basic Service Set (BSS) mode can have an Access Point (AP) associated with one or more stations (STAs) that are associated with the AP. The AP can have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS can arrive through the AP and can be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS can be sent to the AP to be delivered to respective destinations depending on the traffic. For example, traffic between STAs within the BSS can be sent through the AP, where a source STA can send traffic to the AP and the AP can deliver the traffic to a destination STA. The traffic between STAs within a BSS can be considered and / or referred to as peer-to-peer (P2P) traffic. P2P traffic can be sent between STAs directly using a direct link, without using or passing through the AP. A direct link can be set up between (or for) source and destination STAs using an exchange of direct link setup (DLS) messages (e.g., a 802.11e DLS or an 802.11z tunneled DLS (TDLS) for example). In certain representative embodiments, the DLS can use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode can not have an AP, and all STAs in the IBSS can communicate directly with each other without using or passing through a central AP.

[0042] When using an 802.11 ac infrastructure mode of operation or similar, an AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can be a fixed width (e.g., a wide bandwidth of 20 MHz) or a dynamically set width. The primary channel can be the operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, such as in 802.11 systems, a carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented. For CSMA / CA, STAs, including the AP (e.g., each STA) can sense the primary channel. If a particular STA senses / detects that the primary channel is busy, the particular STA can back off. Only one STA can transmit at any given time in a given BSS.

[0043] High Throughput (HT) STAs can use 40 MHz wide channels for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0044] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data can be parsed into two streams by a segment parser. The inverse fast Fourier transform (IFFT) and time domain processing can be done on each stream separately. The streams can be mapped on to the two 80 MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described 80+80 configuration operations can be reversed, and the combined data can be sent to the medium access control (MAC).

[0045] 802.11af and 802.11ah support sub-1 GHz modes of operation. The channel operating bandwidths and carriers in 802.11af and 802.11ah are reduced relative to those used in 802.11η and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah can support metering type control / Machine Type Communication (MTC), such as MTC devices in a macro coverage area. MTC devices can have certain capabilities, e.g., limited capabilities, including support (e.g., only support) for certain and / or limited bandwidths. MTC devices can include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0046] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11η, 802.11ac, 802.11af, and 802.11ah include a channel that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by one of the STAs operating in the BSS that supports the smallest bandwidth operating mode. In the example of 802.11ah, for a STA (e.g., a MTC type device) that supports (e.g., only supports) a 1 MHz mode, the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, e.g., due to a STA (which only supports a 1 MHz operating mode) transmitting to the AP, then all available frequency bands can be considered busy, even if most of the available frequency bands remain idle.

[0047] In the United States, the available frequency bands that 802.11ah can use are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available to 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0048] Figure 1D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 can utilize NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 can also be in communication with the CN 106.

[0049] The RAN 104 can include gNBs 180a, 180b, 180c, although the RAN 104 can include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c can implement MIMO technology. For example, gNBs 180a, 108b can utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers can be on unlicensed spectrum while the remaining component carriers can be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c can implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0050] The WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using transmissions associated with the extensible numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of various or extensible lengths (e.g., containing a variable number of OFDM symbols and / or lasting a variable length of absolute time).

[0051] The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, the WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize signal s in the unlicensed frequency band(s) to communicate with gNBs 180a, 180b, 180c. In the non-standalone configuration, the WTRUs 102a, 102b, 102c can communicate / wirelessly couple to gNBs 180a, 180b, 180c while also communicating / wirelessly coupling with another RAN, such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c can implement DC principles to substantially simultaneously communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c can serve as the mobility anchor point for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to serving WTRUs 102a, 102b, 102c.

[0052] Each of the gNBs 180a, 180b, 180c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, DC, interworking with E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b, and the like. As shown, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface. Figure 1D

[0053] Figure 1D ​The illustrated CN 106 can include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0054] The AMF 182a, 182b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and can serve as the control-plane anchor for the WTRUs 102a, 102b, 102c. For example, the AMF 182a, 182b can handle authentication of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different Protocol Data Unit (PDU) sessions with different requirements), selection of a particular SMF 183a, 183b, management of the WTRU 102a, 102b, 102c’ s registration area, termination of Non-Access Stratum (NAS) signaling, mobility management, and the like. The AMF 182a, 182b can utilize network slicing to customize CN support for the WTRUs 102a, 102b, 102c based on the types of services being utilized, the contract that the WTRUs 102a, 102b, 102c have purchased, or the like. For example, different network slices can be established for access to services that rely on ultra-reliable low latency (URLLC) access, access to services that rely on enhanced massive mobile broadband (eMBB) access, access to services for MTC access, and the like. The AMF 182a, 182b can provide control plane functionality such as for switching the RAN 104 to other RANs (not shown) that employ different radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0055] The SMF 183a, 183b can be connected to AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b can also be connected to the UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b can select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b can perform other functions, such as managing and allocating IP address

[0056] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which can provide the wtru 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the wtru 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.

[0057] The CN 106 can facilitate communications with other networks. For example, the CN 106 can include, or can communicate with, an IP gateway for facilitating communications between the CN 106 and the PSTN 108, or other networks. The CN 106 can also provide a connection to the other networks 112, which can include other wired or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c can be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0058] In view of Figures 1A-1D And Figures 1A-1D In view of the respective descriptions of the above one or more of the following one or more or all functions described herein can be performed by one or more emulation devices (not shown): WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. The emulation device can be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation device can be used to test other devices and / or to simulate a network and / or WTRU functionality.

[0059] The simulation devices can be designed to implement one or more tests of one or more other devices in a laboratory environment and / or a carrier network environment. For example, the simulation device(s) can perform the one or more, or all, functions while implemented and / or deployed fully or partially as part of a wired and / or wireless communication network to test other devices within the communication network. The simulation device(s) can perform the one or more, or all, functions while implemented / deployed temporarily as part of a wired and / or wireless communication network. The simulation devices can directly couple to another device and / or perform tests using over-the-air wireless communications for testing purposes.

[0060] The simulation device(s) can perform the one or more, including all, functions while not implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device(s) can be used in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement test scenarios for testing one or more components. The simulation device(s) can be test equipment. The simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communications via RF circuitry (e.g., which can include one or more antennas).

[0061] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in combination with others depending on the particular application. The solutions described herein consider the 802.11 specific protocol, but it is understood that the solutions described herein are not limited to this scenario and are applicable to other wireless systems as well.

[0062] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in combination with others depending on the particular application. The solutions described herein consider the 802.11 specific protocol, but it is understood that the solutions described herein are not limited to this scenario and are applicable to other wireless systems as well.

[0063] In the following, the term network node or device can be used to indicate an access point (AP), and the term WTRU can be used to indicate a station (STA). A WTRU can perform the functions of a network node.

[0064] Overview of WLAN system A WLAN in Infrastructure Basic Service Set (BSS) mode has an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP typically interfaces with a Distribution System (DS) or another type of wired / wireless network that carries traffic to and from the WTRUs. Traffic to the AP from WTRUs that is destined for an external gateway (e.g., a Wide Area Network (WAN) is sent to the AP by way of scheduling requests, requests to send, and / or channel use grants. The AP, in turn, sends the traffic to the external gateway over a wired / wireless connection that is typically designated as the DS. Traffic that originates from the external gateway to WTRUs is delivered to the AP by way of the DS. The AP, in turn, sends the traffic to the appropriate WTRU. That being said, a WTRU can communicate directly with another WTRU by utilizing a direct link. The WTRU can utilize the direct link to communicate data / information to and / or from the other WTRU directly. The direct link can utilize an 802.11 DLS or 802.11z tunneled DLS (TDLS) between the WTRUs.

[0065] In the case of using the 802.11 ac infrastructure mode of operation, the AP can transmit a beacon on a fixed channel, typically the primary channel. This channel can be 20 MHz wide and is the operating channel of the BSS. This channel is also used by STAs to establish a connection with the AP. The basic channel access mechanism in 802.11 systems is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). In this mode of operation, each STA, including the AP, will sense the primary channel. If the channel is sensed to be busy, the STA will back off. Thus, only one STA can transmit at any given time in a given BSS.

[0066] In 802.11η, High Throughput (HT) STAs can also communicate using a 40 MHz wide channel. This is accomplished by combining the primary 20 MHz channel with an adjacent 20 MHz channel to form a 40 MHz wide contiguous channel.

[0067] In 802.11 ac, Very High Throughput (VHT) STAs can support 20MHz, 40 MHz, 80 MHz, and / 160 MHz wide channels. Similar to 802.11 n described above, 40 MHz and 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which can also be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data goes through a segment parser that divides the data into two streams. Each stream is then separately subjected to IFFT processing and time domain processing. The streams are then mapped onto the two channels, and the data is transmitted. At the receiver, the mechanism is reversed, and the combined data is sent to the MAC.

[0068] 802.11 af and 802.11 ah support sub-1 GHz modes of operation. For these specifications, the channel operating bandwidths and carriers are reduced relative to those used in 802.11 n and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. A possible use case for 802.11 ah supports Meter Type Control (MTC) devices in a macro coverage area. MTC devices can have limited capabilities, including support for only a limited bandwidth, but also include a requirement for very long battery life.

[0069] WLAN systems that support multiple channels and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel designated as the primary channel. The primary channel can, but does not necessarily, have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. Thus, the bandwidth of the primary channel is limited by one of the STAs operating in the BSS that supports the smallest bandwidth mode of operation. In the example of 802.11 ah, if there is a STA that supports only a 1 MHz mode (e.g., a MTC type of device), the primary channel can be 1 MHz wide, even though other STAs in the AP and BSS can support 2 MHz, 4 MHz, 8 MHz, 16 MHz, or other channel bandwidth modes of operation. All carrier sensing and NAV settings depend on the status of the primary channel; that is, if the primary channel is busy, for example, due to a STA supporting only a 1 MHz mode of operation transmitting to the AP, the entire available frequency band is considered busy, even though most of the available frequency band sits idle and is available.

[0070] In the United States, the available frequency bands that 802.11ah can use are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz; and in Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available to 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0071] TWT and restricted TWT Target wake time (TWT) operation was originally introduced in 802.11ah. It was designed to allow an AP and its associated STAs to negotiate a wake-up time period during which the STAs can transmit and receive traffic. In other words, the STA and the AP reach a TWT agreement that defines when to wake up the STA to receive and transmit data, so that the STA can wake up only at the TWT session and remain in sleep mode for the rest of the time, thereby saving power and prolonging battery life. 802.11ax extended the use of TWT to allow an AP to manage activities in the BSS in order to minimize contention among STAs and reduce the amount of time that STAs need to be awake with power save mode. A TWT element is defined to carry information for negotiating and announcing TWT-related information. Two types of TWT are defined: broadcast TWT and individual TWT.

[0072] An example of individual TWT operation given in 802.11ax is shown in Figure 2 An example of individual TWT operation given in 802.11ax is shown in

[0073] An example of individual TWT operation given in 802.11ax is shown in Figure 3An example of broadcast TWT operation given in 802.11 ax is shown in Figure 1. A TWT scheduled STA (i.e., STA 1 301) can negotiate a first wake-up target beacon transmission time (TBTT) with a TWT scheduling AP (TWT scheduling AP) 300 to listen to a beacon frame 30003. The AP can announce a broadcast TWT element in the beacon. The AP can then start a TWT service period (SP) 30007 with trigger enabled. In the TWT SP, one or more STAs can wake up and communicate with the AP.

[0074] The IEEE 802.11be Task Group (TG) was approved by the IEEE Standards Board based on the Project Authorization Request (PAR) and Criteria for Standards Development (CSD) developed in the EHT SG. Restricted TWT (R-TWT) was introduced in 802.11be. R-TWT was designed to prioritize latency-sensitive traffic by including a restricted TWT traffic information field in the broadcast TWT element.

[0075] Introduction to Ultra High Reliability (UHR) Study Group The IEEE 802.11 Ultra High Reliability (UHR) Study Group was formed in September 2022. UHR is considered the next major revision to the IEEE 802.11 standard after 802.11be and is currently in the Study Group Letter Ballot phase. UHR was formed to explore the possibility of improving reliability, supporting low-latency traffic, and further increasing peak throughput and improving the efficiency of IEEE 802.11 networks.

[0076] Coordinated Multi-AP (C-MAP) transmission was discussed in 802.11be and UHR SG. C-MAP allows two or more APs to coordinate and transmit to a group of STAs simultaneously. The schemes that have been discussed include co-OFDMA; co-TDMA; co- spatial reuse (CSR); coordinated beamforming / nulling (CBF); joint transmission (JTX).

[0077] In the context of coordinated multi-AP, several terms have been defined.

[0078] - Shared-in-AP: An EHT AP that obtains the TXOP and initiates multi-AP coordination.

[0079] - Shared-AP: An EHT AP that is coordinated by the shared-in-AP for multi-AP transmission.

[0080] - AP candidate set: a set of APs that can initiate or participate in multi-AP coordination.

[0081] Among other things, this document addresses the negotiation mechanism of AP scheduled TWT in C-MAP and the AP power save mode negotiation in C-MAP.

[0082] Negotiation mechanism of AP scheduled TWT in C-MAP When multiple APs work in the same C-MAP set, they can have overlapping service areas. They can have overlapping TWT SPs, which means their operating channels or service periods can overlap or partially overlap. Therefore, it is beneficial to envision a mechanism to support the negotiation of TWT operating parameters (configuration settings) (e.g., TWT SP start time / duration, transmission power settings, etc.) between APs so that transmissions within each AP's TWT SP do not interfere with each other.

[0083] AP power save mode negotiation in C-MAP To save operating power, an AP can enter a power save mode in which the AP can not perform any transmission or reception. However, when an AP enters a power save mode, its associated STA(s) can therefore stop being served. Therefore, it is desirable to develop a mechanism for power save mode negotiation between APs in a C-MAP so as to guarantee that at least one AP in the vicinity (within the same C-MAP as the AP in power save mode) is awake and can therefore serve the STA(s) associated with the AP in power save mode.

[0084] Representative negotiation mechanism of AP scheduled TWT in C-MAP The embodiments discussed herein address the issues raised above in relation to the negotiation mechanism of AP scheduled TWT in C-MAP.

[0085] Multiple APs in the vicinity of each other can have overlapping service areas, as Figure 4 indicated in Figure 4 An example scenario is depicted in which two APs 401 and 421 share their service areas 400 and 420, e.g., WTRUs 411-414 are in the overlapping service area 410. In order to minimize the interference between transmissions within each AP's coverage or to maintain the desired link quality (especially in the AP scheduled TWT SP), as Figure 4The depicted APs with collocated or overlapping service areas can need to coordinate TWT / R-TWT schedules 415 to achieve multiple goals: 1) minimize interference between STAs transmitting in TWT SPs when TWT SPs in neighboring APs overlap; 2) maximize transmission power when there is no overlapping TWT SP in neighboring APs; 3) maximize use of interference-free channels for TWT SP transmissions.

[0086] Representative negotiation mechanism for AP-scheduled TWT in C- MAP: enhanced TWT element According to one embodiment, neighboring APs with overlapping service areas (e.g., sharing the same AP Group ID) can negotiate TWT operation and can reach a TWT operation agreement. The TWT operation agreement can include configurations such as operating channel(s) allocated to each AP's TWT, potential (or allowed) TWT SP time and duration, transmit power, etc. After a TWT agreement is established between the APs, the APs can use the allocated TWT SPs to serve their associated STA(s) with the agreed parameters (configurations) (e.g., operating channel(s) or subchannel(s), power, and duration, etc.). The negotiated TWT can include a broadcast TWT or an individual TWT.

[0087] Figure 5a An example of an enhanced control field format in an enhanced TWT element 5010 according to one embodiment is depicted. This enhanced TWT element has an enhanced control field; compared to a legacy (non-enhanced) TWT element, the enhanced TWT element includes an "inter-AP negotiation" subfield 5008, which can indicate whether the TWT is a legacy TWT element or the TWT element is an enhanced TWT element. The enhanced control field can be used for negotiation of TWT settings between APs. For example, if the inter-AP negotiation subfield 5008 is set to 1, it means that the TWT element 5010 includes an enhanced control field 5008 showing TWT negotiation between APs; otherwise, for example, if the field 5008 is set to 0, it indicates that this TWT is a TWT element between an AP and non-AP STAs (e.g., a legacy TWT). If the inter-AP negotiation control field 5008 is equal to 1, the TWT Tx requirements field 5018 / 5027 according to one embodiment can be included in the individual TWT parameter set field 5011 or the broadcast TWT parameter set field 5012. In Figure 5b and Figure 5c Examples of the improved individual TWT parameter set field and the improved broadcast TWT parameter set field are described in

[0088] According to one embodiment, when TWT negotiation is exchanged among APs, multiple information can be included in the TWT Tx Request field (e.g., 5018, 5027): 1) AP Group ID: indicates the group that the AP belongs to, e.g., APs served by the same virtual AP can have the same AP Group ID, or APs with overlapping service areas can have the same AP Group ID; 2) Spatial Reuse information (e.g., PSR): can indicate the minimum received interference or minimum received power from transmissions in overlapping TWTs. During overlapping TWT SPs, neighboring APs and their associated STAs can need to follow the power setting rules derived from this parameter on the overlapping channels; 3) STA ID: ID of the STA that will be served in the negotiated TWT SP; 3) TWT Operating Channel or Operating Link.

[0089] According to one embodiment, if TWT negotiation is exchanged among APs, i.e., TWT element with Inter-AP Negotiation subfield 5008 set to 1, this can have a different interpretation than the legacy TWT element, i.e., TWT element with Inter-AP Negotiation subfield 5008 set to 0. Figure 6An example interpretation of the negotiation type subfield 600 and the target wake-up time 601, TWT wake-up interval mantissa and TWT wake-up interval exponent subfields 602 according to one embodiment is given in the case where the inter-AP negotiation subfield 5008 in the enhanced control field is equal to 1. For example, the negotiation type subfield 600 set to a value of 0 can be used for an individual TWT negotiation between two APs. In this case, the target wake-up time subfield can indicate a future individual TWT SP start time. The TWT wake-up interval mantissa and TWT wake-up interval exponent subfields can represent the interval between individual TWT SPs. This case can represent a negotiated TWT time allocated to the requesting AP. The requesting AP can use this time to serve its TWT requesting STAs. For example, when the negotiation type subfield 600 is set to a value of 1, to provide a broadcast TWT schedule to the TWT requesting AP and / or the TWT responding AP, the target wake-up time subfield 601 can indicate a future broadcast TWT SP start time and the TWT wake-up interval mantissa and TWT wake-up interval exponent subfields 602 can indicate the interval between broadcast TWT SPs. For example, if the negotiation type subfield 600 is set to a value of 2, to provide an interval negotiation between power save duration and power save period to the TWT requesting AP and the responding AP (where in this negotiation the TWT requesting AP can negotiate sleep time and duration with the responding AP), the target wake-up time subfield 601 can indicate a future power save time (inactive / sleep time) and the TWT wake-up interval mantissa and TWT wake-up interval exponent subfields 602 can indicate the interval between power save periods.

[0090] Figure 7 An example of the value of the improved broadcast TWT recommendation field 700 of the broadcast TWT element according to one embodiment is given. In this example, when the broadcast TWT recommendation field 700 value is equal to 5, it means that the AP is exchanging TWT elements to negotiate settings in broadcast / individual TWT SPs or broadcast R-TWT SPs, for example, the negotiation type subfield in the enhanced control field is set to 0 or 1 (as indicated in Figure 6 Figure 6 ​​

[0091] A representative negotiation mechanism for TWT scheduling in C-MAP: negotiation of broadcast TWT between APs. According to one embodiment, the AP can negotiate the TWT SP by exchanging an enhanced TWT request frame and an enhanced TWT response frame according to the embodiment. Figure 8 An example of enhanced TWT frame exchange for TWT negotiation between APs in the case of overlapping TWTs is depicted. In this example, AP1 800 (the TWT requesting AP) sends an enhanced TWT request 805 to AP2 810 with negotiation type 2 indicating a negotiation for broadcasting a TWT SP. This TWT request 805 can include frames with parameters such as... Figure 5a The TWT element in the enhanced control field indicated in the request frame. The request frame may also include the following information: the interval between broadcast TW SPs, the start time of the future broadcast TW SP, the AP group ID, the ID of the STA served by AP1, and proposed spatial multiplexing information (e.g., PSR1). Upon receiving this enhanced TWT request frame, AP2 810 responds 806 with an enhanced TWT response frame having negotiation type 2 and the inter-AP negotiation subfield set to 1. This enhanced TWT response frame indicates that AP2 810 acknowledges the broadcast TWT information transmitted by AP1 and instructs AP2 to accept the parameters proposed by AP1. Because AP1 and AP2 are nearby, for example, in the same C-MAP set or belonging to the same group (i.e., having the same group ID), their TWT broadcast SPs overlap. For example, their TWT operating channels overlap, and their TWT SPs overlap (both TWT SPs start at time 1, t1 and end at time 2, t2). AP2 also proposes PSR information PSR2, which is included in the enhanced TWT response frame from AP2. STAs performing transmissions within AP1's TWT SP may need to set their transmission power according to the function of PSR2. Similarly, STAs performing transmissions within AP2's TWT SP may need to set their transmission power according to the function of PSR1. Note that AP1 and AP2's TWT operating channels may partially overlap. The transmission power on the overlapping channels within AP1's TWT and AP2's TWT2 may need to follow PSR2 and PSR1 respectively.

[0092] Alternatively, TWT responds to AP (e.g., Figure 8 AP2 in the context can refuse AP requests made by TWT (e.g., Figure 8the parameters suggested by AP1. In this case, the APs negotiating (e.g., AP1 and AP2) do not reach an agreement on TWT operation, and AP1 can not set up a TWT SP during the requested time.

[0093] The above protocol can be applied to the negotiation between two AP MLDs or APs affiliated to the same MLD.

[0094] Figure 9 An example embodiment of enhanced TWT frame exchange for TWT negotiation between APs in the case of non-overlapping TWTs is depicted. In this example, AP1 900 (i.e., the TWT requesting AP) transmits to AP2 910 an enhanced TWT request 905 with negotiation type 2 indicating negotiation of broadcast TWT SPs. This TWT request 905 can include a TWT element with an enhanced control field as indicated in Figure 5a AP1 900. The request frame 905 can also include information on the interval between broadcast TW SPs, the future broadcast TW SP start time, the AP group ID, the IDs of the STAs served by AP1 900, the suggested spatial reuse information (e.g., PSR1). Upon receiving this enhanced TWT request frame 905, AP2 910 responds 906 with an enhanced TWT response frame with negotiation type 2 and the inter-AP negotiation subfield set to 1. AP2 910 determines that the TWT SPs between AP1 and AP2 can not overlap. It accepts all the parameters suggested by AP1 900 and can not set the PSR requirement information (e.g., less restricted requirement of PSR information in the TWT Tx requirement field or higher minimum interference value) in the response frame. It can also indicate its TWT operating channel, TWT SPs and the interval between TWT SPs. As indicated in Figure 9 AP1 900 is from time 1 to time 2, i.e., ti to t2, while the TWT SP of AP2 is from time 3 to time 4, i.e., t3 to t4. Since the TWT SPs of AP1 900 and AP2 910 do not overlap, the transmission power of the STAs served by AP1 900 and the STAs served by AP2 910 can not be limited, e.g., less restricted PSR requirement set in the PSR information of the TWT Tx requirement field of the TWT element.

[0095] For example, if the TWT SPs of AP1 and AP2 overlap (as Figure 8If the TWT SPs of AP1 and AP2 overlap (as shown, AP1 800 and AP2 810), then following the PSR information defined by AP2 and AP1, the transmission power of AP1 and AP2 during the negotiated TWT SP can be set to P11 and P21, respectively. If the TWT SPs of AP1 and AP2 do not overlap (as shown, AP1 820 and AP2 830), then the transmission power of AP1 and AP2 for the same STA as the overlapping TWT case is P12 and P22, respectively. P11 can be less than P12, and P21 can be less than P22. Figure 9

[0096] Representative negotiation mechanism for TWT of AP scheduling in C-MAP: negotiation of separate TWTs between APs In one embodiment, after a non-AP STA sends a request for a TWT SP from its associated AP, APs in the same C-MAP can want to negotiate separate TWTs. Figure 10 ​An example of separate TWT operation following negotiation at the AP is depicted. In this example, STA1 1010 and STA2 1030 are associated with AP1 1000; AP1 1000 and AP2 1020 are in the same C-MAP set. STA1 1010 sends a TWT request 1011 to the TWT responder STA (AP1 1000) to establish a TWT agreement with trigger-enabled. The TWT responder STA (AP1 1000) accepts the TWT agreement with STA1 1010 and confirms the acceptance in a TWT response 1001 sent to STA1 1010. Subsequently, AP1 1000 sends a TWT request 1002 including an enhanced TWT element (e.g., using the format shown in the section "Enhanced TWT element") to AP2 1020. AP2 1020 responds to AP1 1000 with a TWT response 1021 including an enhanced TWT element (e.g., using the format shown in the section "Enhanced TWT element"). Upon receiving the TWT response 1021 from AP2 1020, AP1 1000 sends an unsolicited TWT response 1003 to STA2 1030 to establish a TWT agreement with trigger-enabled with STA2 1030. Both TWT agreements (between AP1 1000 and STA1 1010 and between AP1 1000 and STA2 1030) are established as announced TWTs. During the trigger-enabled TWT SP 1004, the TWT responder STA (AP1 1000) sends a basic trigger frame 1005 to which the TWT request STAs indicate that they wake up during the TWT SP. STA1 1010 indicates that it wakes up by sending a PS-Poll frame 1012 and STA2 1030 indicates that it wakes up by sending a QoS null frame 1031 in response to the basic trigger frame 1005. STA1 1010 and STA2 1030 receive their DL BUs in subsequent exchanges with AP1 1000 and go to sleep 1013 and 1032 outside of this TWT SP. Note that in this example, the TWT negotiation procedure between APs (e.g., AP1 1000 and AP2 1020) can be transparent to the TWT request STAs (e.g., STA1 1010) or the TWT scheduled STAs (e.g., STA2 1030). AP1 1000 can use the trigger frame 1005 to indicate to STA1 1010 and STA2 1030 the transmission requirements obtained from the negotiation between AP1 1000 and AP2 1020.

[0097] Alternatively, after TWT negotiation between APs, the APs can determine to extend the sleep time of the TWT requesting STA by using a pseudo trigger-enabled TWT SP during which the APs, TWT responding STAs can send unsolicited TWT responses to the original TWT requesting STA to indicate the updated (e.g., postponed) TWT SP. Figure 11An example of individual TWT operation with extended sleep duration following negotiation at the AP is depicted. In this example, upon receiving a TWT request 1111 from STA1 1110, TWT negotiation between APs is performed after AP1 1100 sends a TWT response 1101 to the TWT requesting STA (STA1 1110). The TWT negotiation agreement between APs can decide a new TWT SP start time that is different from the one already agreed between AP1 1100 and STA1 1110. Subsequently, AP1 1100 sends an unsolicited TWT response 1102 to its associated STA (STA2 1130) with the updated TWT agreement obtained from the negotiation between AP1 1110 and AP2 1120. During the target wake-up time 1105 of STA1 AP1 1110 indicated in the first TWT agreement between AP1 1100 and STA1 1110, AP1 1100 transmits a trigger frame 1103 to the TWT requesting STA (STA1 1110) and STA1 1110 indicates that it wakes up during this TWT SP. Subsequently, AP1 1100 sends an unsolicited TWT response 1104 to STA1 1110 to indicate that this is a fake TWT SP (this can imply that this TWT SP duration is shorter than the originally agreed duration) and the next TWT SP for STA1 1110. The fake TWT SP 1105 in this example is used to exchange the updated TWT response / request 1104. In other words, the fake TWT SP 1105 can only support the exchange of control or management frames, but not the transmission of data frames. After the fake trigger-enabled TWT SP 1105, STA1 1110 returns to sleep mode 1112 until the updated TWT SP 1104 comes. This sleep mode is an extended sleep duration 1112 for STA1 1110. In the upcoming TWT SP 1106 (which is determined by the negotiation between AP1 1100 and AP2 1120), AP1 1100 sends a basic trigger frame 1107 to the TWT requesting STAs (STA1 1110 and STA2 1130) indicating that they are to wake up during this TWT SP 1106 by responding with a PS-Poll frame 1113 and a QoS null frame 1131, respectively. STA1 1110 and STA2 1130 receive their DL BUs (DL MU PPDU) 1108 in the subsequent exchange with AP1 1100 and go to sleep state outside this TWT SP.

[0098] Representative negotiation of power save time / duration between APs The embodiments described herein address the problem raised in embodiment 2 above: negotiation of power save time / duration between APs.

[0099] Representative negotiation of power save time / duration between APs: improved broadcast TWT parameter set field for negotiation of power save time / duration between APs An AP in power save mode can be in a sleep state, e.g., not transmitting or receiving packets. To guarantee that a STA can be served by at least one AP (i.e., it is not in a sleep state), nearby or collocated APs (e.g., APs with the same group ID) can need to coordinate the interval between the power save start time / duration and / or the power save period. Figure 12 An example architecture when multiple APs are negotiating power save mode is depicted according to one embodiment. In this example, STA1 1220 is associated with AP1 1200 and STA2 1230 is associated with AP2 1210. AP1 1200 and AP2 1210 are in the same coordinated multi-AP set (C- MAP set). To guarantee that the associated STAs 1220 and 1230 can be served by at least one AP, AP1 1200 and AP2 1210 are negotiating their respective sleep mode start time / duration / period. When AP1 1200 is in sleep mode, its associated STA1 1220 will be served by AP2 1210. Similarly, when AP2 1210 is in sleep time, its associated STA2 1230 will be served by AP1 1200.

[0100] In one embodiment, if an AP is negotiating power save / duration, e.g., the inter-AP negotiation subfield is set to 1 and the negotiation type subfield is set to 2, the requesting AP can need to transmit an enhanced TWT element with an improved broadcast TWT parameter set field. Figure 13 An example of the improved broadcast TWT parameter set field 1300 in case an AP is negotiating power save / duration is depicted. The target sleep time field 1301 can contain a positive integer corresponding to a TSF time at which the TWT requesting AP intends to be in power save mode or the TWT responding AP agrees to be in power save mode. Alternatively, the target sleep time field 1301 can contain a positive integer corresponding to a TSF time at which the TWT requesting AP requests the TWT responding AP to be in power save mode. The nominal maximum sleep duration field 1302 can contain a positive integer corresponding to the maximum duration of the sleep period in units of wake-up duration subfield (e.g., 100 μβ). The sleep period start time field 1303 can contain a positive integer corresponding to a TSF time at which the TWT requesting AP intends to be in power save mode or the TWT responding AP agrees to be in power save mode. Alternatively, the sleep period start time field 1303 can contain a positive integer corresponding to a TSF time at which the TWT requesting AP requests the TWT responding AP to be in power save mode. Figure 5aThe maximum amount of time that the TWT Requesting AP or TWT Responding AP is expected to be in power save mode can be indicated in units indicated by the units subfield 1302 (e.g., as indicated in the TWT element 5006). The sleep mode can be periodic, with the sleep interval indicated in the sleep wake-up interval exponent field 1303. For example, according to one embodiment, the sleep wake-up interval exponent subfield can be set to a value of the exponent of the TWT sleep interval value in microseconds, with base 2.

[0101] Representative negotiation of power save time / duration between APs: Procedure for negotiation of power save time / duration between APs In one embodiment, if the AP is negotiating power save time / duration, the Requesting AP can need to transmit an enhanced TWT element to the Responding AP and reach agreement on the power save time / duration. Figure 14 An example of an enhanced TWT frame exchange for power save time / duration negotiation between APs is depicted. In this example, AP1 1400 (TWT Requesting AP) transmits an enhanced TWT Request 1405 of negotiation type 1, indicating negotiation of power save start time / duration. By setting the inter-AP negotiation subfield to 1, this TWT Request can include a TWT Parameter field with a Power Save Start Time / Duration element as described in the TWT element 5006. Figure 5aThe TWT element indicates the enhanced control field. The request frame 1405 can also include the following information: future sleep time start / duration, interval between sleep periods, sleep channel (which indicates the channel ID or link ID that the AP will perform sleep mode), AP group ID, ID of STAs served by AP1 1400. Upon receiving this enhanced TWT request frame, AP2 1410 responds with an enhanced TWT response frame 1406 with negotiation type 1 and AP inter negotiation subfield set to 1. AP2 1410 accepts the parameters proposed by AP1 1400 in the enhanced TWT request frame 1405 and indicates its sleep start time / duration, sleep channel, AP group ID, and ID of STAs served by AP2 1410 in its response 1406. Note that AP1 1400 and AP2 1410 can have some overlapping coverage areas. In other words, when AP2 1410 (or AP1 1400) is in sleep mode (i.e., hibernation state), AP1 1400 (or AP2 1410) can be able to serve the STAs associated with AP2 1410 (or AP1 1400). After the sleep agreement is established, AP1 1400 starts the sleep period from time 1 to time 2, i.e., tl to t2 on channel 1; meanwhile, AP2 1410 stays in awake mode and serves the STAs associated with AP1 1400 on channel 1. When time 3 is reached, AP2 1410 starts the sleep period until time 4, i.e., AP2 1410 is in sleep mode from t3 to t4 on channel 1; meanwhile, AP1 1400 stays in awake mode and serves the STAs associated with AP2 1410 on channel 1.

[0102] Alternatively, AP2 can not accept the proposed sleep parameters from AP1, or AP1 can not accept the proposed sleep parameters from AP2. Then, from tl to t2, AP1 can not turn on sleep mode, and from t3 to t4, AP2 can not turn on sleep mode.

[0103] Note that the negotiation can be between two AP MLDs or APs attached to the same MLD. The channel that the AP is in hibernation mode (sleep mode) can be fully / partially overlapped with the other AP it negotiates with, or the two APs can not have a shared channel.

[0104] Figure 15 FIG. 1 1 is a flow diagram illustrating a method performed by a first network node (e.g., a device performing the functions of a network node or AP or a WTRU) according to one embodiment.

[0105] In 1500, the first network node transmits a target wake time (TWT) request frame to a second network node (or a second WTRU performing the functions of a network node) located in a service area overlapping with the service area of the first network node, the request frame indicating a request for negotiating at least one TWT service period (SP) between the first network node and the second network node and / or including information indicating the request for negotiating at least one TWT service period (SP) between the first network node and the second network node. The TWT request includes (proposed) first configuration parameters related to the first network node and a first wireless transmit-receive unit (WTRU) associated with the first network node and / or includes information indicating (proposed) first configuration parameters related to the first network node and a first wireless transmit-receive unit (WTRU) associated with the first network node.

[0106] In 1501, the first network node receives a TWT response frame from the second network node, the TWT response frame acknowledging that the second network node received the TWT request frame sent by the first network node and enabling the first network node to serve a first WTRU associated with the first network node using at least one TWT service period according to information included in the TWT response frame.

[0107] In 1502, the first network node configures itself and the first WTRU associated with the first network node according to information included in the TWT response frame received from the second network node. If the information included in the TWT response frame indicates that the second network node accepts the first configuration parameters, the first network node can configure itself and its associated WTRU according to the first configuration parameters if the first network node and the WTRU associated therewith have not been so configured (i.e., if the first network node and the WTRU associated with the first network node have not been configured according to the first configuration parameters). If the information included in the TWT response frame indicates that some or all of the first configuration parameters are not accepted by the second network node, the first network node can configure itself and the WTRU associated therewith according to other configuration parameter values suggested by the second network node and included in the TWT response frame, or the first network node can choose not to do so and then possibly iterate the method in order to re-negotiate different first configuration parameter value settings as needed until an agreement is reached or not reached with the second network node. This negotiation can include TWT parameter settings for TWT operation of the second network node and the WTRU associated therewith.

[0108] According to one embodiment, the TWT response frame includes second PSR information PSR2 different from the proposed first PSR (PSR1) included in the TWT request frame; and wherein the first network node configures transmission power configuration parameters of the first WTRU associated with the first network node according to the PSR2 included in the TWT response frame.

[0109] According to one embodiment, the overlapping service area is characterized in that the first device and the second device share a same device group identifier.

[0110] According to one embodiment, the TWT request frame includes and / or includes information indicating at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node: power save start time; power save duration; interval between power save periods; TWT operating channel or TWT operating link; operating subchannel; network node group identifier; proposed first parameterized spatial reuse (PSR) information PSR1; transmission power; identifier of the first WTRU associated with the first network node.

[0111] According to one embodiment, the TWT response frame includes and / or includes information indicating second PSR information PSR2 different from the proposed PSR1 included in the TWT request frame. The first network node then configures transmission power configuration parameters of the first WTRU associated with the first network node according to the PSR2 included in the TWT response frame.

[0112] According to one embodiment, the at least one TWT service period is a broadcast TWT service period, and wherein the TWT request frame includes a negotiation type indicating negotiation of the at least one broadcast TWT service period.

[0113] According to one embodiment, the TWT request frame includes and / or includes information indicating at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node: interval between broadcast TWT service periods; future broadcast TWT service period start time; network node group identifier; identifier of the first WTRU associated with the first network node; proposed first spatial reuse (PSR) information PSR1.

[0114] According to one embodiment, the TWT response frame includes second PSR information PSR2 and / or includes information indicating the second PSR information PSR2, the second PSR information PSR2 being different from the suggested PSR1 included in the TWT request frame. The first network node then configures the transmission power configuration parameters of the first WTRU associated with the first network node according to the PSR2 included in the TWT response frame.

[0115] The application also relates to embodiments of a first device (e.g., a network node or a WTRU performing the functions of a network node) comprising at least one processor configured to transmit a target wake time (TWT) request frame to a second device (e.g., a network node or a WTRU performing the functions of a network node) located in a service area overlapping a service area of the first device, the request frame indicating a request to negotiate at least one TWT service period (SP) between the first device and the second device and / or including information indicating the request to negotiate at least one TWT service period (SP) between the first device and the second device, the TWT request including first configuration parameters related to the first device and a first wireless transmit-receive unit (WTRU) associated with the first device and / or including information indicating the first configuration parameters related to the first device and the first WTRU associated with the first device.

[0116] The at least one processor of the first device is further configured to receive a TWT response frame from the second device, the TWT response frame acknowledging the reception by the second device of the TWT request frame transmitted by the first device and enabling the first device to serve the first WTRU associated with the first device using the at least one TWT service period according to information included in the TWT response frame.

[0117] The at least one processor of the first device is further configured to configure the first device and the first WTRU associated with the first device according to information included in the TWT response frame.

[0118] According to one embodiment, the TWT response frame includes second PSR information PSR2 and / or includes information indicating the second PSR information PSR2, the second PSR information PSR2 being different from the suggested PSR1 included in the TWT request frame. The first network node then configures the transmission power configuration parameters of the first WTRU associated with the first network node according to the PSR2 included in the TWT response frame.

[0119] According to embodiments of the first device, the overlapping service areas are characterized in that the first device and the second device share a same device group identifier.

[0120] According to embodiments of the first device, the TWT request frame includes and / or includes information indicating at least one of the following configuration parameters related to the first device and a first WTRU associated with the first device: power save start time; power save duration; interval between power save periods; TWT operating channel or TWT operating link; operating subchannel; device group identifier; suggested first parameterized spatial reuse (PSR) information PSR1; transmission power; identifier of the first WTRU associated with the first device.

[0121] According to embodiments of the first device, the TWT response frame includes and / or includes information indicating second PSR information PSR2, the second PSR information PSR2 being different from the suggested PSR1 included in the TWT request frame; and wherein the at least one processor is configured to configure a transmission power configuration parameter of the first WTRU associated with the first device in accordance with the PSR2 included in the TWT response frame.

[0122] According to embodiments of the first device, the at least one TWT service period is a broadcast TWT service period, and wherein the TWT request frame includes a negotiation type indicating negotiation of the at least one broadcast TWT service period and / or includes information indicating the negotiation type indicating negotiation of the at least one broadcast TWT service period.

[0123] According to embodiments of the first device, the TWT request frame includes and / or includes information indicating at least one of the following configuration parameters related to the first device and a first WTRU associated with the first device: interval between broadcast TWT service periods; future broadcast TWT service period start time; device group identifier; identifier of the first WTRU associated with the first device; suggested first spatial reuse (PSR) information PSR1.

[0124] According to embodiments of the first device, the TWT response frame includes and / or includes information indicating second PSR information PSR2, the second PSR information PSR2 being different from the suggested PSR1 included in the TWT request frame; and wherein the at least one processor is configured to configure a transmission power configuration parameter of the first WTRU associated with the first device in accordance with the PSR2 included in the TWT response frame.

[0125] CONCLUSION Although features and elements are described herein in particular combinations, each combination can be used independently or in combination with other combinations.

[0126] Although the solutions described herein consider the 802.11 specific protocol, it is understood that the solutions described herein are not limited to this scenario and are applicable to other wireless systems as well.

[0127] Although SIFS is used in the examples of design and procedures to indicate various interframe spacings, all other interframe spacings such as RIFS, AIFS, DIFS, or other agreed time intervals can be applied to the same solutions.

[0128] Although four RBs per triggered TXOP are shown as an example in some figures, the actual number of RBs / channels / bandwidth utilized can be different.

[0129] Although features and elements are provided in particular combinations in the above, a person of ordinary skill in the art will understand that each feature or element can be used alone or in combination with other features and elements. The disclosure is not limited to the specific embodiments described in this application, which are intended to illustrate the various aspects. Many modifications and variations will be apparent to those of ordinary skill in the art from the description and illustrations herein, as will be apparent to practitioners of the art. No element, act, or instruction used in the description of the application should be construed as critical or essential to the application unless explicitly so described. According to the description above, methods and apparatuses within the scope of the disclosure in addition to those enumerated herein will be readily apparent to those of ordinary skill in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The disclosure is limited only as would be the following claims and the full scope of equivalents to which such claims are entitled. It is to be understood that the disclosure is not limited to particular methods or systems.

[0130] For simplicity, the foregoing embodiments are discussed in terms of the terminology and structure of devices having wireless communication capabilities (e.g., radio wave transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0131] It should also be understood that the terms used herein are for the purpose of describing particular embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" can refer to any one of a snapshot, a single image, and / or a plurality of images displayed on a time basis. As another example, the term "user equipment" and its acronym "UE," the term "remote," and / or the term "head-mounted display" and its acronym "HMD" can mean or include, when referred to herein, (i) a wireless transmit and / or receive unit (WTRU); (ii) any one of a plurality of embodiments of a WTRU; (iii) a device with wireless capability and / or wired capability (e.g., tetherable) that is configured with some or all of the structure and functionality of a WTRU; (iii) a device with wireless capability and / or wired capability that is configured with less than all of the structure and functionality of a WTRU; or (iv) the like. Reference is made herein to Figures 1A-1D Details of an example WTRU that can represent any WTRU described herein are provided. As another example, various embodiments disclosed above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display can be utilized, and some or all of the present disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other devices can include a drone or other device configured to stream information to provide an adaptive reality experience.

[0132] Furthermore, the methods provided herein can be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable medium for execution by a computer or processor. Examples of computer- readable media include electronic signals (optical, electrical or the like) transmittable over a wire or wireless connection and a computer-readable storage medium. Examples of computer- readable storage media include, but are not limited to, RAM, ROM, register storage, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0133] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present disclosure. In view of the various embodiments that can be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered limiting on the scope of the attached claims. For example, embodiments provided herein include handheld devices, which can include or be used with any suitable voltage source, such as a battery or the like, that provides any suitable voltage.

[0134] Further, in the embodiments provided above, reference has been made to processing platforms, computing systems, controllers, and other devices that include processors. These devices can include at least one central processing unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions can be performed by the various CPUs and memories. Such acts and operations or instructions can be referred to as being "executed," "computer executed" or "CPU executed."

[0135] Those skilled in the art will appreciate that the acts and symbolic representations of operations or instructions include the manipulation of electrical signals by the CPU. The electrical system representations, such as a motherboard or other circuitry, include electronic hardware that can be purchased off-the-shelf or specifically manufactured or designed according to practices of those skilled in the trade and its maintenance requires the manipulation of electrical signals. An apparatus can be specially constructed for the required purposes, or it can comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in any

[0136] Data bits can also be maintained on computer readable media including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium can include cooperating or interconnected computer readable media, which exist exclusively within a processing system, or are distributed among multiple interconnected processing systems that can be local or remote to the processing system. It is understood that the embodiments are not limited to the above-mentioned memory, and that other platforms and memory can support the provided methods.

[0137] In illustrative embodiments, any of the operations, processes, etc. described herein can be implemented as computer readable instructions stored on a computer readable medium. The computer readable instructions can be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0138] There is little distinction between the implementation of various aspects of the system in terms of hardware and software in that either can be used to implement the functionality associated with the various aspects. The choice of whether to implement various aspects using hardware or software depends on factors such as the particular applications for the various aspects, the design choices made during development of the system, and so on. In one embodiment, the various aspects of the system are implemented using hardware that includes one or more of application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other integrated circuits, and / or state machines designed to perform the functions described herein and / or other processing units.

[0139] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples contain one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, and / or examples can be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein can be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented by circuits, combined circuits, and / or other functional paradigms; the preferred embodiments of the subject matter described herein are not limited to being solely of the hardware illustrated for depending on the implementation requirements.

[0140] Those skilled in the art will recognize that the description of apparatus and / or process herein described is typically made in the context of the apparatus and / or process being integrated into a data processing system, in the manner described herein. That is, at least a portion of the apparatus and / or process described herein can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system can include one or more of the following: a system unit housing, a video display device, memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices such as a touch pad or screen, and / or a control system including feedback loop(s) and control motors (e.g., motors for sensing position and / or velocity; control motors to move and / or adjust components and / or quantities). A typical data processing system can be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0141] The subject matter described herein sometimes illustrates different components included in, or connected with, different other components. It is to be understood that the depicted architectures are merely examples, and that in fact many other architectures can implement the same functions. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable", to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0142] With respect to the use of substantially any plural and / or singular term herein, those having skill in the art can translate the plural and / or singular term to a singular and / or plural term, depending on the context in which it is used. For example, where a singular term is used, such as "a" or "an", it is intended to mean "one or more" in the context of this disclosure. Where a plural term is used, such as "a plurality of", it is intended to mean "two or more" in the context of this disclosure.

[0143] Those skilled in the art will appreciate that, in general, terminology used herein, and especially in the appended claims (e.g., in the body of the appended claims), is intended to be interpreted in an "open" and "inclusive" manner (e.g., the term "comprising" should be interpreted as "including, but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including, but not limited to," etc.). Those skilled in the art will further appreciate that if it is intended that a particular number be recited in a claim, such intent will be expressly recited in the claim, and if not so recited, no such intent exists. For example, in the case of only one item being intended, the term "single" or similar language can be used. To aid in understanding, the claims and / or description herein that follow below can include the use of introductory phrases such as "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases is not to be construed as implying any specific limitation to the scope of the claim recitations that follow such introductory phrases. For example, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly, when introduced by "at least one" or "one or more" of a recited list of items, the phrase "at least one" or "one or more" should be interpreted as indicating that at least one, and possibly more than one, of the recited items can be present. Similarly,Furthermore, as used herein, the term "any" followed by a list of multiple items and / or multiple item categories is intended to include, individually or in combination with other items and / or other item categories, "any one," "any combination," "any multiple," and / or "any combination of multiples." Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "quantity" is intended to include any number, including zero. And the term "many" as used herein is intended to be synonymous with "multiple."

[0144] Furthermore, in cases where features or aspects of this disclosure are described in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is also described in accordance with any single member or subgroup of the Markush Group.

[0145] As those skilled in the art will understand, for any and all purposes, such as for providing a written description, all scopes disclosed herein also include any and all possible subscopes and combinations thereof. Any listed scope can be readily considered adequately descriptive and capable of dividing the same scope into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, a middle third, and an upper third, etc. Those skilled in the art will also understand that all language, such as “up to,” “at least,” “greater than,” “less than,” etc., including the stated numbers, refers to a scope that can subsequently be decomposed into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1-3 cells means a group having 1, 2, or 3 cells. Similarly, a group having 1-5 cells means a group having 1, 2, 3, 4, or 5 cells, and so on.

[0146] Furthermore, the claims should not be construed as being limited to the provided order or elements unless otherwise stated. Additionally, the use of the term "means for..." in any claim is intended to refer to... The claim format is either device plus function, and any claim without the term "device for..." is not so.

Claims

1. A method performed by a first network node, the method comprising: transmitting a target wake time (TWT) request frame to a second network node located in a service area that overlaps a service area of the first network node, the target wake time (TWT) request frame indicating a request to negotiate at least one TWT service period between the first network node and the second network node, the TWT request including first configuration parameters related to the first network node and related to a first wireless transmit-receive unit (WTRU) associated with the first network node; receiving a TWT response frame from the second network node, the TWT response frame acknowledging that the second network node received the TWT request frame sent by the first network node and enabling the first network node to serve the first WTRU associated with the first network node using the at least one TWT service period according to information included in the TWT response frame; and configuring the first network node and the first WTRU associated with the first network node according to the information included in the TWT response frame received from the second network node. the TWT response frame includes second parameterized spatial reuse (PSR) information that is different from suggested first PSR information included in the TWT request frame; and wherein the first network node configures a transmission power configuration parameter of the first WTRU associated with the first network node according to the second PSR information included in the TWT response frame.

2. The method of claim 1, wherein, the overlapping service areas are characterized in that the first network node and the second network node share a same network node group identifier.

3. The method of claim 1, wherein, the TWT request frame includes at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node and / or includes information indicating at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node:

4. The method of claim 1, wherein, a power save start time; a power save duration; an interval between power save periods; a TWT operating channel; a TWT operating link; an operating subchannel; a network node group identifier; suggested first parameterized spatial reuse (PSR) information; a transmission power; and an identifier of the first WTRU associated with the first network node. the at least one TWT service period is a broadcast TWT service period, and wherein the TWT request frame includes a negotiation type indicating negotiation of the at least one broadcast TWT service period.

5. The method of claim 1, wherein, the TWT request frame includes at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node and / or includes information indicating at least one of the following configuration parameters related to the first network node and the first WTRU associated with the first network node:

6. The method of claim 1, wherein, an interval between broadcast TWT service periods; a future broadcast TWT service period start time; a network node group identifier; ​ an identifier of a first WTRU associated with the first network node; and suggested first parameterized spatial reuse (PSR) information.

7. The method of claim 6, wherein, the TWT response frame includes second PSR information that is different from the suggested first PSR information included in the TWT request frame; and wherein the first network node configures transmission power configuration parameters of the first WTRU associated with the first network node according to the second PSR information included in the TWT response frame.

8. The method of at least one of claims 1-7, wherein, either of the first network node and the second network node is an access point.

9. The method of at least one of claims 1-8, wherein, either one or more of the first WTRUs is a station.

10. A first device comprising at least one processor configured to: transmit a target wake time (TWT) request frame to a second device located in a service area that overlaps a service area of the first device, the target wake time (TWT) request frame indicating a request to negotiate at least one TWT service period between the first device and the second device, the TWT request including first configuration parameters related to the first device and a first wireless transmit-receive unit (WTRU) associated with the first device; receive a TWT response frame from the second device, the TWT response frame acknowledging receipt of the TWT request frame sent by the first device and enabling the first device to serve the first WTRU associated with the first device using the at least one TWT service period according to information included in the TWT response frame; and configure the first device and the first WTRU associated with the first device according to the information included in the TWT response frame.

11. The first device of claim 10, wherein, the TWT response frame includes second parameterized spatial reuse (PSR) information that is different from the suggested first PSR information included in the TWT request frame; and wherein the at least one processor is configured to configure transmission power configuration parameters of the first WTRU associated with the first device according to the second PSR information included in the TWT response frame.

12. The first device of claim 10, wherein, the overlapping service areas are characterized in that the first device and the second device share a same device group identifier.

13. The first device of claim 10, wherein, the TWT request frame includes at least one of the following configuration parameters related to the first device and a first WTRU associated with the first device: a power save start time; a power save duration; an interval between power save periods; a TWT operating channel; a TWT operating link; an operating subchannel; a device group identifier; suggested first parameterized spatial reuse (PSR) information; a transmission power; and an identifier of a first WTRU associated with the first device.

14. The first device of claim 10, wherein, the at least one TWT service period is a broadcast TWT service period, and wherein the TWT request frame includes a negotiation type indicating negotiation of at least one broadcast TWT service period.

15. The first device of claim 10, wherein, the TWT request frame includes at least one of the following configuration parameters related to the first device and a first WTRU associated with the first device: an interval between broadcast TWT service periods; a future broadcast TWT service period start time; a device group identifier; an identifier of a first WTRU associated with the first device; and suggested first spatial reuse (PSR) information.

16. The first device of claim 15, wherein, the TWT response frame includes second parameterized spatial reuse (PSR) information and / or includes information indicating second parameterized spatial reuse (PSR) information, the second parameterized spatial reuse (PSR) information being different from the suggested first PSR information included in the TWT request frame; and wherein the at least one processor is configured to configure a transmission power configuration parameter of the first WTRU associated with the first device in accordance with the second PSR information included in the TWT response frame.

17. The first device of at least one of claims 10-16, wherein, either of the first device and the second device is an access point.

18. The first device of at least one of claims 10-17, wherein, any one or more of the first WTRUs is a station.