Multi-link sleep mode for wlan

Abstract

The invention relates to a multi-link sleep mode for WLAN. Some aspects of the present disclosure include apparatuses and methods for implementing a sleep mode for a multi-link wireless communication network, such as a wireless local area network (WLAN). For example, some aspects relate to a multi-link device (MLD) including a first station (STA) associated with a first link of a wireless network and configured to communicate with a second MLD over the first link. The MLD also includes a second STA associated with a second link of the wireless network. The second STA is in a sleep mode. The MLD also includes one or more processors communicatively coupled to the first STA and the second STA and configured to control operation of the first STA and the second STA.

Description

[0001] This application is a divisional application of the invention patent application with application date of June 1, 2021, application number 202110609515.1, and invention name “Multi-link sleep mode for WLAN”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 033,486, filed on June 2, 2020, which is hereby incorporated by reference in its entirety. Background Art Technical Field

[0004] The described aspects relate generally to channel access in wireless communications, including a multi-link sleep mode in a multi-link wireless communication network such as a wireless local area network (WLAN).

[0005] Related fields

[0006] A first multi-link device (MLD) may use multiple links / channels to communicate with a second MLD. For example, the first MLD may use a first radio to communicate with a first radio of a second MLD using a first link. The first MLD may also use a second radio to communicate with a second radio of a second MLD using a second link. The two MLDs may use multiple links to transmit more data and / or transmit data faster. However, when using two radios, the MLDs will use more power. Summary of the invention

[0007] Some aspects of the present disclosure include an apparatus and method for implementing a sleep mode of a multi-link wireless communication network such as a wireless local area network (WLAN). The sleep mode of the multi-link WLAN and the operation for entering and / or exiting the sleep mode described in the present disclosure can help devices (e.g., access points (APs), stations (STAs)) in the WLAN to better utilize channel resources, save power, and / or enable virtual STAs in the multi-link WLAN.

[0008] Some aspects relate to a multi-link device (MLD). The MLD includes a first station (STA) associated with a first link of a wireless network and configured to communicate with a second MLD on the first link. The MLD also includes a second STA associated with a second link of the wireless network. The second STA is in a sleep mode. The MLD also includes one or more processors that are communicatively coupled to the first STA and the second STA and configured to control the operation of the first STA and the second STA.

[0009] In some examples, the one or more processors are further configured to transmit, using the first STA on the first link, a message to the second MLD indicating that the second STA is in sleep mode. In some examples, the message includes an association request transmitted during an association between the MLD and the second MLD, and the message also includes a request to map one or more traffic identifiers (TIDs) at the second MLD to the first link and the second link.

[0010] In some examples, the one or more processors are further configured to transmit a keep-alive message using the first STA within the shorter of a first time period and a second time period. The first time period may be a first idle period associated with the first STA, and the second time period may be a second idle period associated with the second STA.

[0011] In some examples, the one or more processors are further configured to receive, using the first STA, from the second MLD at least one of an updated group temporary key (GTK) or an updated integrity GTK (IGTK) associated with the second STA in sleep mode.

[0012] In some examples, the one or more processors are further configured to transmit, using the second STA, a frame indicating that the second STA has exited the sleep mode to the second MLD in response to the second STA being transitioned to the wake-up mode and controlling the first STA to enter the sleep mode. In some examples, the first STA includes a first transceiver, and the second STA includes a second transceiver different from the first transceiver.

[0013] In some examples, the one or more processors are further configured to transmit, using the first STA, to the second MLD a first frame indicating that the first STA is transitioning to sleep mode and causing the second STA to transition from sleep mode to wake-up mode. The one or more processors are further configured to transmit, using the second STA, to the second MLD a second frame indicating that the second STA has exited sleep mode in response to the second STA transitioning to wake-up mode.

[0014] In some examples, to cause the second STA to transition from the sleep mode to the wake-up mode, the one or more processors are configured to control transceivers of the MLDs associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0015] In some examples, the one or more processors are further configured to determine that the first link is unavailable, and in response to the determination, control the first STA to transition from the wake-up mode to the sleep mode. The one or more processors are further configured to cause the second STA to transition from the sleep mode to the wake-up mode and transmit a frame indicating that the second STA has exited the sleep mode to the second MLD using the second STA.

[0016] In some examples, to cause the second STA to transition from the sleep mode to the wake-up mode, the one or more processors are configured to control transceivers of the MLDs associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0017] In some examples, the one or more processors are further configured to determine that the first link is unavailable, and in response to the determination, transmit a first frame to the second MLD using the first link indicating that a link switch is occurring. The one or more processors are further configured to control the first STA to transition from an awake mode to a sleep mode, cause the second STA to transition from the sleep mode to an awake mode, and transmit a frame to the second MLD using the second STA indicating that the second STA has exited the sleep mode.

[0018] In some examples, to cause the second STA to transition from the sleep mode to the wake-up mode, the one or more processors are configured to control transceivers of the MLDs associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0019] Some aspects relate to a method. The method includes using a first station (STA) of a first multi-link device (MLD) to transmit a first message to a second MLD on a first link of a wireless network. The first message indicates that the second STA of the first MLD associated with a second link of the wireless network is in a sleep mode. The method also includes using the first STA of the first MLD to transmit at least one of a data frame, a management frame, or a control frame with the second MLD on the first link.

[0020] Some aspects relate to a non-transitory computer-readable medium storing instructions. When the instructions are executed by a processor of a multi-link device (MLD), the instructions cause the processor to perform operations, the operations comprising using a first station (STA) of the multi-link device (MLD) to transmit a first message to a second MLD on a first link of a wireless network. The first message indicates that the second STA of the first MLD associated with a second link of the wireless network is in a sleep mode. The operations also include using the first STA of the first MLD to transmit at least one of a data frame, a management frame, or a control frame with the second MLD on the first link.

[0021] The present invention is provided for the purpose of illustrating some aspects only, so as to provide an understanding of the subject matter described herein. Therefore, the above-mentioned features are only examples and should not be understood as narrowing the scope or essence of the subject matter in the present disclosure. Other features, aspects and advantages of the present disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and enable those skilled in the relevant art to make and use the present disclosure.

[0023] Figure 1A An exemplary system implementing a sleep mode in a multi-link communication network according to some aspects of the present disclosure is shown.

[0024] Figure 1B An exemplary multi-link communication between two devices according to some aspects of the present disclosure is shown.

[0025] Figure 2 A block diagram of an exemplary wireless system of an electronic device implementing sleep mode and sleep mode entry and / or exit operations of a multi-link communication network according to some aspects of the present disclosure is shown.

[0026] Figure 3 Exemplary communications between an access point (AP) multi-link device (MLD) and a non-AP MLD are shown in accordance with aspects of the present disclosure.

[0027] Figure 4A and Figure 4B An exemplary traffic identifier (TID) to link mapping is shown in accordance with some aspects of the present disclosure.

[0028] Figure 5 Exemplary communications between an AP of an AP MLD and a STA that is not an AP MLD are shown in accordance with some aspects of the present disclosure.

[0029] Figure 6 Exemplary communications between an AP MLD and a non-AP MLD are shown in accordance with some aspects of the present disclosure.

[0030] Figure 7 Example communications between an AP of an AP MLD and a STA of a non-AP MLD to enter a sleep mode during association are shown in accordance with aspects of the present disclosure.

[0031] Figure 8 Exemplary communications between an AP MLD 802 and a non-AP MLD 804 are shown to communicate keep-alive messages and GTK / IGTK updates in accordance with some aspects of the present disclosure.

[0032] Fig. 9A and Fig. 9B Example communications between an AP MLD and a non-AP MLD to enter and / or exit a sleep mode during a link transition are shown in accordance with some aspects of the present disclosure.

[0033] Fig.10Example communications between an AP MLD and a non-AP MLD to enter and / or exit a sleep mode during a link transition are shown in accordance with some aspects of the present disclosure.

[0034] Fig.11 Example communications between an AP MLD and a non-AP MLD to enter and / or exit a sleep mode during a fast link switch are shown in accordance with aspects of the present disclosure.

[0035] Fig.12 Example communications between an AP MLD and a non-AP MLD to enter and / or exit a sleep mode during a fast link switch are shown in accordance with aspects of the present disclosure.

[0036] Fig.13 An exemplary frame format is shown that may be communicated between an AP MLD and a non-AP MLD to communicate that a STA is entering (or has exited) sleep mode in accordance with some aspects of the present disclosure.

[0037] Fig.14 An exemplary method for a wireless system to support and implement a sleep mode for a multi-link wireless communication network, such as a wireless local area network (WLAN), according to some aspects of the present disclosure is shown.

[0038] Fig.15 An exemplary computer system for implementing some aspects or portions thereof.

[0039] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, the same reference numerals represent the same or functionally similar elements. In addition, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0040] Some aspects of the present disclosure include an apparatus and method for implementing a sleep mode of a multi-link wireless communication network such as a wireless local area network (WLAN). The sleep mode of a multi-link WLAN of various aspects of the present disclosure and operations for entering and / or exiting the sleep mode can help devices (e.g., access points (APs), stations (STAs)) in the WLAN to better utilize channel resources, save power, and / or enable virtual STAs in the multi-link WLAN.

[0041] According to some aspects, sleep mode and sleep mode entry and / or exit operations of a multi-link WLAN may be implemented using communication techniques compatible with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, such as, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, etc. However, aspects of the present disclosure may also extend to operations in other multi-link communication networks.

[0042] Figure 1A An exemplary system 100 for implementing a sleep mode in a multi-link communication network according to some aspects of the present disclosure is shown. The exemplary system 100 is provided for illustration purposes only and is not intended to limit the disclosed aspects. The system 100 may include, but is not limited to, an access point (AP) multi-link device (MLD) 110, a non-AP MLD 120, and a network 130. The non-AP MLDs 120a-120c may include, but are not limited to, wireless local area network (WLAN) stations, such as wireless communication devices, smart phones, laptops, desktop computers, tablet computers, personal assistants, monitors, televisions, wearable devices, etc. The AP MLD 110 may include, but is not limited to, WLAN electronic devices, such as wireless routers, wearable devices (e.g., smart watches), wireless communication devices (e.g., smart phones), or combinations thereof. The network 130 may be the Internet and / or a WLAN. The communication of the non-MLD 120 is shown as wireless communication 140. The communication between the AP MLD 110 and the non-AP MLD 120 may be performed using the wireless communication 140a-140c. Wireless communications 140a-140c may be based on a variety of wireless communication technologies, including but not limited to technologies based on IEEE 802.11 (such as but not limited to IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11bc, IEEE 802.11bd, IEEE 802.11be, IEEE 802.11v, etc.).

[0043] According to some aspects, AP MLD 110 and non-AP MLD 120 are configured to implement multi-link communications. In other words, AP MLD 110 and non-AP MLD 120 are configured to use multiple MAC / PHY links to implement and support simultaneous or substantially simultaneous data transmission. For example, Figure 1B An exemplary multi-link communication between two devices according to some aspects of the present disclosure is shown.

[0044] like Figure 1BAs shown, the non-AP MLD 120a and the AP MLD 110 can use multiple links 150a-150c to communicate with each other. In other words, the non-AP MLD 120a and the AP MLD 110 can use multiple MAC / PHY links 150a-150c to transmit data simultaneously or substantially simultaneously. Although three links 150 are shown, aspects of the present disclosure are not limited to this example, and any number of links 150 can be implemented. According to some aspects, the links 150 may include different wireless channels. For example, each wireless channel / link 150 may be defined based on its corresponding frequency that is different from other wireless channels / links. However, aspects of the present disclosure are not limited to wireless channels and other MAC / PHY layer links can be used as links 150 for communication between the non-AP MLD 120a and the AP MLD 110.

[0045] Additionally, although links 150a-150c are illustrated as links between non-AP MLD 120a and AP MLD 110, aspects of the present disclosure are not limited to this example. In some aspects, multi-link communication may be between two AP MLDs. Additionally or alternatively, multi-link communication may be between two non-AP MLDs. For example, communication between two non-AP MLDs (and link 150) may be direct communication (and direct link) between these non-AP MLDs. Additionally or alternatively, communication between two non-AP MLDs (and link 150) is conducted through AP MDL 110. In this example, as Figure 1A The wireless communications 140a and 140b shown may include Figure 1B Links 150a-150c.

[0046] According to some aspects and as discussed in more detail below, the non-AP MLD 120a may include two or more radios that communicate with the AP MLD 110 using the plurality of links 150. According to some aspects and as discussed in more detail below, to save power and / or implement virtual sites, the non-AP MLD 120a may be configured to use only one of its radios to track a Delivery Traffic Indication Map (DTIM) beacon and maintain normal communication with the AP MLD 110. In some aspects, the non-AP MLD 120a may put its other radios or corresponding STAs into sleep mode and activate them only when needed.

[0047] Figure 2A block diagram of an exemplary wireless system 200 of an electronic device implementing a sleep mode and sleep mode entry and / or exit operation of a multi-link communication network according to some aspects of the present disclosure is shown. The system 200 may be any electronic device in the electronic devices of the system 100 (e.g., AP MLD 110, non-AP MLD 120). The system 200 includes a processor 210, one or more transceivers 220a-220n, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The system shown is provided as an exemplary portion of the wireless system 200, and the system 200 may include other circuits and subsystems. In addition, although the systems of the wireless system 200 are shown as separate components, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0048] The memory 250 may include random access memory (RAM) and / or cache, and may include control logic components (e.g., computer software) and / or data. The memory 250 may include other storage devices or memories, such as, but not limited to, a hard drive and / or a removable storage device / unit. According to some examples, an operating system 252 may be stored in the memory 250. The operating system 252 may manage data transmission from the memory 250 and / or one or more application programs 254 to the processor 210 and / or one or more transceivers 220a-220n. In some examples, the operating system 252 maintains one or more network protocol stacks (e.g., an Internet protocol stack, a cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, the operating system 252 includes a control mechanism and a data structure to perform functions associated with the layer.

[0049] According to some examples, applications 254 may be stored in memory 250. Applications 254 may include applications (e.g., user applications) used by wireless system 200 and / or a user of wireless system 200. Applications in applications 254 may include applications such as, but not limited to, the following: Radio streaming, video streaming, remote control and / or other user applications.

[0050] The system 200 may also include a communication infrastructure 240. The communication infrastructure 240 provides, for example, communication between the processor 210, one or more transceivers 220a-220n, and the memory 250. In some specific implementations, the communication infrastructure 240 may be a bus. The processor 210, together with instructions stored in the memory 250, executes operations that enable the wireless system 200 of the system 100 to implement the sleep mode and sleep mode entry and / or exit operations in the multi-link communication network as described herein. In addition, or alternatively, the one or more transceivers 220a-220n perform operations that enable the wireless system 200 of the system 100 to implement the sleep mode and sleep mode entry and / or exit operations in the multi-link communication network operation as described herein.

[0051] One or more transceivers 220a-220n transmit and receive communication signals supporting multi-link sleep mode according to some aspects, and may be coupled to antenna 260. (In this article, transceivers may also be referred to as radio components). Antenna 260 may include one or more antennas that may be the same or different types. One or more transceivers 220a-220n allow system 200 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 220a-220n may include processors, controllers, radio components, sockets, plugs, buffers, and similar circuits / devices for connecting to a network and communicating on the network. According to some examples, one or more transceivers 220a-220n may include one or more circuits for connecting to a wired network and / or a wireless network and communicating on a wired network and / or a wireless network.

[0052] According to some aspects of the present disclosure, one or more transceivers 220a-220n may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TM Subsystems, each including its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, one or more of the transceivers 220a-220n may include more or fewer systems for communicating with other devices.

[0053] In some examples, one or more transceivers 220a-220n may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network. Cellular networks may include, but are not limited to, 3G / 4G / 5G networks such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc.

[0054] Additionally, or alternatively, one or more transceivers 220a-220n may include a device for implementing a Bluetooth-based TMProtocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low energy long range protocols (including Bluetooth TM For example, the transceiver 220n may include a Bluetooth TM Transceiver.

[0055] In addition, one or more transceivers 220a-220n may include one or more circuits (including WLAN transceivers) to enable connection and communication over a WLAN network (such as, but not limited to, a network based on a standard described in IEEE 802.11 (such as, but not limited to, IEEE 802.11ac, IEEE 802.11ax, IEEE802.11bc, IEEE 802.11bd, IEEE 802.11be, etc.). For example, transceiver 220a may enable connection and communication over a multi-link WLAN network having a first link (e.g., link 150a) associated with a 2.4 GHz wireless communication channel. For example, transceiver 220b may enable connection and communication over a multi-link WLAN network having a second link (e.g., link 150b) associated with a 5 GHz wireless communication channel. For example, transceiver 220c may enable connection and communication over a multi-link WLAN network having a third link (e.g., link 150c) associated with a 6 GHz wireless communication channel. However, aspects of the present disclosure are not limited to these wireless channels, and other PHY layer links and / or other wireless channels may be used.

[0056] In addition, or alternatively, the wireless system 200 may include a WLAN transceiver configured to operate at two or more links. According to some examples, the processor 210 may be configured to control a WLAN transceiver to switch between different links. For example, the transceiver 220a may implement a connection and communication on a multi-link WLAN network having a first link (e.g., link 150a) associated with a 2.4GHz wireless communication channel. And the transceiver 220b may implement a connection and communication on a multi-link WLAN network having a second link (e.g., link 150b) associated with a 5GHz wireless communication channel, and may implement a connection and communication on a multi-link WLAN network having a third link (e.g., link 150c) associated with a 6GHz wireless communication channel. According to some aspects of the present disclosure, switching from a first link to a second link may include using a transceiver associated with the second link (e.g., transceiver 220b) instead of a transceiver associated with the first link (e.g., transceiver 220a). Additionally, or alternatively, switching from the first link to the second link may include controlling a single transceiver (eg, transceiver 220) to operate at a frequency of the second link instead of operating at a frequency of the first link.

[0057] According to some aspects of the present disclosure, the processor 210 alone or in combination with computer instructions stored in the memory 250 and / or one or more transceivers 220a-220n implements sleep mode and sleep mode entry and / or exit operations in a multi-link communication network as discussed herein. Figures 3 to 14 Discussed in more detail, processor 210 may implement Figure 1A , Figure 1B and Figure 2 A sleep mode and sleep mode entry and / or exit operation in a multi-link communication network.

[0058] According to some aspects, the non-AP MLD 120 may operate in different power management modes. In one example, a power management mode may include a power saving mode. According to some examples, the power saving mode may include a lossless power saving mode or a lossy power saving mode. According to some aspects, in the lossless power saving mode, for DTIM tracking, the non-AP MLD 120 may wake up before the DTIM beacon (e.g., before each DTIM beacon) and may receive a group addressed frame. According to some aspects, in the lossless power saving mode, the non-AP MLD 120 may request an individually addressed frame from the AP MLD by transmitting a Power Save Poll (PS-Poll) frame or an Unscheduled Automatic Power Save Delivery (U-APSD) trigger frame.

[0059] According to some aspects, in a lossy power save mode, for basic service set (BSS) maximum idle, AP MLD 110 may advertise a BSS maximum idle period and the AP may maintain the association of non-AP MLD 120 until non-AP MLD 120 sends a keep-alive message within the BSS maximum idle period (e.g., about 1 s to about 18 hours).

[0060] In one example, another power management mode may include a wireless network management (WNM) sleep mode. In some examples, the non-AP MLD 120 may request to enter a WNM sleep mode with a specified WNM sleep interval (e.g., less than the BSS maximum idle period). According to some aspects, after entering the WNM sleep mode, the non-AP MLD 120 may skip DTIM beacon and group temporary key (GTK) / integrity GTK (IGTK) updates. When exiting the WNM sleep mode, the non-AP MLD 120 may obtain an updated GTK / IGTK from, for example, the AP MLD 110.

[0061] In one example, another power management mode may include a multi-link sleep mode. According to some aspects, in the multi-link sleep mode, the non-AP MLD 120 does not track DTIM beacons. Additionally, or alternatively, in the multi-link sleep mode, the non-AP MLD 120 does not receive group addressed frames. Additionally, or alternatively, in the multi-link sleep mode, the non-AP MLD 120 does not request individually addressed frames. Additionally, or alternatively, in the multi-link sleep mode, the non-AP MLD 120 does not send keep-alive messages. Additionally, or alternatively, in the multi-link sleep mode, the non-AP MLD 120 does not perform management handshakes to enter and exit the multi-link sleep mode.

[0062] Figure 3 306a-306c. In some examples, link 306 may be and / or include: Figure 1B Link 150.

[0063] According to some aspects, AP MLD 302 has a multi-link (ML) address 308 associated with AP MLD 304. In addition, AP MLD 302 may include three radio components / transceivers 310a-310c. For example, AP MLD 302 may include transceiver 310a, which is configured to enable connection and communication on a multi-link WLAN network having a first link (e.g., link 306a) associated with a 2.4GHz wireless communication channel. For example, AP MLD 302 may include transceiver 310b, which is configured to enable connection and communication on a multi-link WLAN network having a second link (e.g., link 306b) associated with a 5GHz wireless communication channel. For example, AP MLD 302 may include transceiver 310c, which is configured to enable connection and communication on a multi-link WLAN network having a third link (e.g., link 306c) associated with a 6GHz wireless communication channel. In other words, AP MLD 302 may include three APs operating on a 2.4 GHz channel, a 5 GHz channel, and a 6 GHz channel, respectively. However, aspects of the present disclosure are not limited to these wireless channels, and other PHY layer links and / or other wireless channels may be used. In addition, AP MLD 302 may include fewer or more radio components / transceivers.

[0064] According to some examples, each transceiver 310 may include a medium access control (MAC) layer 312 and a physical (PHY) layer 314. In some examples, each transceiver 310 (e.g., each AP) may have an associated basic service set identifier (BSSID) 316. In these examples, each transceiver 310 (e.g., each AP) may operate independently (e.g., transmit (TX) and receive (RX) (STR) simultaneously) and each transceiver 310 (e.g., each AP) may initiate at least one BSS with a different BSSID. However, aspects of the present disclosure are not limited to these examples and the radio component / transceiver 310 may include other structures and / or components.

[0065] According to some aspects, the non-AP MLD 304 has a multi-link (ML) address 318 associated with the non-AP MLD 304. In addition, the non-AP MLD 304 may include two radio components / transceivers 320a-320b. For example, the non-AP MLD 304 may include a transceiver 320a that is configured to enable connection and communication on a multi-link WLAN network having a first link (e.g., link 306a) associated with a 2.4GHz wireless communication channel. For example, the non-AP MLD 304 may include a transceiver 320b that is configured to enable connection and communication on a multi-link WLAN network having a second link (e.g., link 306b) associated with a 5GHz wireless communication channel, or configured to enable connection and communication on a multi-link WLAN network having a third link (e.g., link 306c) associated with a 6GHz wireless communication channel. However, aspects of the present disclosure are not limited to these wireless channels, and other PHY layer links and / or other wireless channels may be used. In addition, the non-AP MLD 304 may include fewer or more radio components / transceivers.

[0066] According to some examples, each transceiver 320 may include a lower medium access control (MAC) layer 322 and a physical (PHY) layer 324. In addition, each transceiver 320 may have an associated address. However, aspects of the present disclosure are not limited to these examples and the radio component / transceiver 320 may include other structures and / or components. Each transceiver / radio component 320 may also be referred to as a station (STA) in this article. In addition, or alternatively, a station (STA) is associated with a specific communication link / channel. For example, a first STA is associated with a first link, and the first link is associated with a 2.4 GHz wireless communication channel. A second STA is associated with a second link, and the second link is associated with a 5 GHz wireless communication channel. And, a third STA is associated with a third link, and the third link is associated with a 6 GHz wireless communication channel.

[0067] According to some aspects, when the non-AP MLD 304 establishes a multi-link association with the AP MLD 302, the non-AP MLD 304 may create up to three STAs 326a-326c, each associated with one of the APs within the AP MLD 302 and each STA 326 having its associated MAC address (different from the other STAs). In some examples, the non-AP MLD 304 may initially assign the 5 / 6GHz transceiver 320b to one of the STAs associated with the 5GHz and 6GHz APs, while the other STA 326c does not have an assigned radio, which may be referred to as a virtual STA. The virtual STA may have its own MAC address.

[0068] For example, the transceiver 320a of the STA 326a of the non-AP MLD 304 may be associated with the transceiver 310a of the AP MLD 302 (e.g., one AP) and communicate with the transceiver 310a on the link 306a associated with the 2.4 GHz wireless communication channel. In this example, the transceiver 320b of the STA 326b of the non-AP MLD 304 may be associated with the transceiver 310b of the AP MLD 302 (e.g., another AP) and communicate with the transceiver 310b on the link 306b associated with the 5 GHz wireless communication channel. In this example, the STA 326c of the non-AP MLD 304 may be a virtual STA. The virtual STA 326c may be associated with the transceiver 310c of the AP MLD 302 (e.g., a third AP) and communicate with the transceiver 310c on the link 306c associated with the 6 GHz wireless communication channel. In some examples, virtual STA 326c can use transceiver 320b to communicate with transceiver 310c of AP MLD 302 on link 306c associated with a 6 GHz wireless communication channel. In this example, non-AP MLD 304 (using, for example, one or more processors) can control transceiver 320b to operate at the frequency of link 306c instead of operating at the frequency of link 306b. Additionally, or alternatively, STA 326c can have its own and separate transceiver (e.g., transceiver 320c).

[0069] Figure 4A and Figure 4B An exemplary traffic identifier (TID) to link mapping is shown in accordance with some aspects of the present disclosure.

[0070] Figure 4AAn exemplary TID to link mapping 401 is shown, where one or more TIDs are mapped to all links. In this example, AP MLD 402 communicates with non-AP MLD 404. As a non-limiting example, AP MLD 402 may include a higher MAC layer 405 and two APs. Each AP of AP MLD 402 may include a lower MAC layer 412 and a PHY layer 414. In this example, non-AP MLD 404 may include a higher MAC layer 403 and two STAs. Each STA of non-AP MLD 404 may include a lower MAC layer 422 and a PHY layer 424. In this example, each STA of non-AP MLD 404 may be associated with one AP of AP MLD 402. For example, a first STA of non-AP MLD 404 having a lower MAC layer 422a and a PHY layer 424a may use link 406a to communicate with a first AP of non-AP MLD 402 having a lower MAC layer 412a and a PHY layer 414a. Additionally, a second STA of the non-AP MLD 404 having a lower MAC layer 422b and a PHY layer 424b may use the link 406b to communicate with a second AP of the non-AP MLD 402 having a lower MAC layer 412b and a PHY layer 414b.

[0071] according to Figure 4A 4. In the exemplary TID-to-link mapping 401 of FIG. 4, the AP MLD 402 may include a first buffer 411a for a first service with a first TID and a second buffer 411b for a second service with a second TID. In this example, the first buffer 411a and the second buffer 411b are mapped to the two links 406a and 406b. In this example, the AP MLD 402 may use the two links 406a and 406b (and the two APs) to transmit data and / or information in the first buffer 411a and the second buffer 411b.

[0072] In this example, block acknowledgements (BAs) associated with the first TID and the second TID may also be sent from the non-AP MLD 404 to the AP MLD 402 using the two links 406a and 406b. For example, a first STA of the non-AP MLD 404 may send a BA 413a associated with the first TID and the second TID to the AP MLD 402 using the link 406a. Additionally, a second STA of the non-AP MLD 404 may send a BA 413b associated with the first TID and the second TID to the AP MLD 402 using the link 406b. According to some examples, a higher MAC layer 415 of the non-AP MLD 404 may include reorder buffers 415a and 415b. In this example, the reorder buffer 415a may be associated with the first TID, and the reorder buffer 415b may be associated with the second TID. According to some aspects, the reorder buffer 415 may be used to store and / or reorder traffic received from the AP MLD 402 before sending the traffic to a higher layer.

[0073] Figure 4B An exemplary TID to link mapping 441 is shown, where different TIDs are mapped to different links. In this example, AP MLD 442 communicates with non-AP MLD 444. As a non-limiting example, AP MLD 442 may include a higher MAC layer 445 and two APs. Each AP of AP MLD 442 may include a lower MAC layer 452 and a PHY layer 454. In this example, non-AP MLD 444 may include a higher MAC layer 443 and two STAs. Each STA of non-AP MLD 444 may include a lower MAC layer 462 and a PHY layer 464. In this example, each STA of non-AP MLD 444 may be associated with one AP of AP MLD 442. For example, a first STA of non-AP MLD 444 having a lower MAC layer 462a and a PHY layer 464a may use link 446a to communicate with a first AP of non-AP MLD 402 having a lower MAC layer 452a and a PHY layer 454a. Additionally, a second STA of non-AP MLD 444 having a lower MAC layer 462b and a PHY layer 464b may use link 446b to communicate with a second AP of non-AP MLD 442 having a lower MAC layer 452b and a PHY layer 454b.

[0074] according to Figure 4B446a (and its associated AP) to transmit data and / or information in the first buffer 451a. The APMLD 442 may use the link 446b (and its associated AP) to transmit data and / or information in the second buffer 451b.

[0075] In this example, block acknowledgements (BAs) associated with the first TID and the second TID may also be sent from the non-AP MLD 444 to the AP MLD 442 using their associated links 446a and 446b, respectively. For example, a first STA of the non-AP MLD 404 may send a BA 453a associated with the first TID to the AP MLD 442 using link 446a. Additionally, a second STA of the non-AP MLD 404 may send a BA 453b associated with the second TID to the AP MLD 442 using link 446b. According to some examples, a higher MAC layer 455 of the non-AP MLD 444 may include reorder buffers 455a and 455b. In this example, the reorder buffer 455a may be associated with the first TID, and the reorder buffer 455b may be associated with the second TID. According to some aspects, the reorder buffer 455 may be used to store and / or reorder traffic received from the AP MLD 442 before sending the traffic to a higher layer.

[0076] Figure 5 FIG. 1 shows exemplary communications between an AP of an AP MLD and a STA of a non-AP MLD according to some aspects of the present disclosure. It should be understood that it may not be necessary to Figure 5 All operations in the Figure 5 The same sequence is used as shown. Figure 5As shown, an AP MLD (e.g., AP MLD 110, 302, 402, and / or 442) may include three APs. A first AP 510a may operate with a 2.4 GHz wireless communication channel. A second AP 510b may operate with a 5 GHz wireless communication channel. A third AP 510c may operate with a 6 GHz wireless communication channel. A non-AP MLD (e.g., non-AP MLD 120, 304, 404, and / or 444) may include two STAs and one virtual STA. For example, a first STA 526a may operate with a 2.4 GHz wireless communication channel. A second STA 526b may operate with a 5 GHz wireless communication channel. A virtual STA 526c may operate with a 6 GHz wireless communication channel.

[0077] According to some examples, a STA 526a of a non-AP MLD may communicate with an AP 510a of an AP MLD to associate with the AP 510a. For example, the STA 526a may send a probe request 511 to the AP 510a. The probe request 511 may include a probe request frame to announce information about the STA 526a and / or query one or more parameters associated with the AP 510a. In response, the AP 510a may send a probe response 513 to the STA 526a. The probe response 513 may include one or more probe response frames, including, for example, the BSSID of the AP 510a, supported data rates, and other relevant information. In addition, or alternatively, the AP 510a may send a beacon 515 to the STA 526a. According to some examples, at 516, a simultaneous authentication of peer entities (SAE) handshake may be performed between the STA 526a and the AP 510a and the STA 526a may be associated with the AP 510a.

[0078] Similarly, STA 526b and AP 510b may transmit messages so that STA 526b may be associated with AP 510b. For example, STA 526b may send a probe request 517 to AP 510b. The probe request 517 may include a probe request frame to announce information about STA 526b and / or query one or more parameters associated with AP 510b. In response, AP 510b may send a probe response 519 to STA 526b. The probe response 519 may include one or more probe response frames, including, for example, the BSSID of AP 510b, supported data rates, and other relevant information. In addition, or alternatively, AP 510b may send a beacon 521. According to some examples, STA 526b may send an association request 525 to AP 510b. According to some examples, the association request 525 may also be referred to as a multi-link association request or a multi-link setup because it is used to establish an association across all links. In one exemplary aspect, the association request 525 may include information and / or a request to the AP 510b (and corresponding AP MLD) to map all TIDs to all links (including virtual links), such as, for example Figure 4A In some examples, mapping all TIDs to all links may result in more flexible operation without remapping overhead. Alternatively, association request 525 may include information and / or a request to AP 510b (and corresponding APMLD) to map different TIDs to different links, such as, for example Figure 4B In some examples, association request 525 may include information and / or a request to AP 510b (and corresponding AP MLD) for a different mapping between TIDs and links.

[0079] In response to the association request 525 and in response to elements of the association request 525 matching the capabilities of the AP 510b, the AP 510b and the STA 526b may be associated and the AP 510b may send an association response 529 to the STA 526b. In some examples, a 4-way handshake 531 may be performed between the AP 510b and the STA 526b.

[0080] According to some examples, AP 510c may transmit beacon 523 in addition to beacon 521. In some examples, beacons 521 and / or 523 may be transmitted in a broadcast manner.

[0081] In some examples, after associating STA 526a with AP 510a and / or associating STA 526b with AP 510b, data ports 533a-533c may be opened for data communication between STA and AP. For example, AP 510b may send data 535 to STA 526b. In addition, or alternatively, AP 510a may send data 537 to STA 526a. In this example, AP 510c cannot send data 539 to virtual STA 526c because STA 526b is using a radio component to communicate with AP 510b. In other words, virtual STA 526c does not receive data because STA 526b is using a radio component. In some examples, the AP MLD may initiate downlink transmission to the non-AP MLD on all links after the association (e.g., immediately after the association). However, the non-AP MLD may not support reception on all links.

[0082] Figure 6 606a-606c. In some examples, link 606 may be and / or may include Figure 1B Link 150.

[0083] According to some aspects, AP MLD 602 ​​has a multi-link (ML) address associated with AP MLD 604. In addition, AP MLD 602 ​​may include three radio components / transceivers 610a-610c (e.g., three APs). For example, AP MLD 602 ​​may include transceiver 610a (e.g., a first AP) configured to enable connection and communication on a multi-link WLAN network having a first link (e.g., link 606a) associated with a 2.4 GHz wireless communication channel. For example, AP MLD 602 ​​may include transceiver 610b (e.g., a second AP) configured to enable connection and communication on a multi-link WLAN network having a second link (e.g., link 606b) associated with a 5 GHz wireless communication channel. For example, AP MLD 602 ​​may include transceiver 610c (e.g., a third AP) configured to enable connection and communication on a multi-link WLAN network having a third link (e.g., link 606c) associated with a 6 GHz wireless communication channel. In other words, AP MLD 602 ​​may include three APs operating on a 2.4 GHz channel, a 5 GHz channel, and a 6 GHz channel, respectively. However, aspects of the present disclosure are not limited to these wireless channels, and other PHY layer links and / or other wireless channels may be used. In addition, AP MLD 602 ​​may include fewer or more radio components / transceivers / APs.

[0084] According to some examples, each transceiver 610 may include a medium access control (MAC) layer 612 and a physical (PHY) layer 614. In some examples, each transceiver 610 (e.g., each AP) may have an associated basic service set identifier (BSSID). In these examples, each transceiver 610 (e.g., each AP) may operate independently (e.g., transmit (TX) and receive (RX) (STR) simultaneously) and each transceiver 610 (e.g., each AP) may initiate at least one BSS with a different BSSID. However, aspects of the present disclosure are not limited to these examples and the radio component / transceiver 610 may include other structures and / or components.

[0085] In addition, if Figure 6As shown, the AP MLD 602 ​​may include a higher MAC layer 605. According to some aspects, the higher MAC layer 605 may be common to all three transceivers 610 (e.g., APs). In some examples, the higher MAC layer 605 may include a buffer 611 for storing data (e.g., packets, frames, etc.) to be transmitted to the non-AP MLD 604. In addition, each lower MAC layer 612 of each transceiver 610 may include a buffer 613 for transmitting data to an associated STA of the non-AP MLD 604. For example, the lower MAC layer 612a of the transceiver 610a may include a buffer 613a. The lower MAC layer 612b of the transceiver 610b may include a buffer 613b. The lower MAC layer 612c of the transceiver 610c may include a buffer 613c.

[0086] According to some aspects, the non-AP MLD 604 has a multi-link (ML) address associated with the non-AP MLD 604. In addition, the non-AP MLD 604 may include two radio components / transceivers. For example, the non-AP MLD 604 may include a first transceiver associated with the STA 626a, the first transceiver being configured to implement a connection and communication on a multi-link WLAN network having a first link (e.g., link 606a) associated with a 2.4GHz wireless communication channel. For example, the non-AP MLD 604 may include a second transceiver associated with the STA 626b, the second transceiver being configured to implement a connection and communication on a multi-link WLAN network having a second link (e.g., link 606b) associated with a 5GHz wireless communication channel, or the second transceiver associated with the STA 626b is configured to implement a connection and communication on a multi-link WLAN network having a third link (e.g., link 606c) associated with a 6GHz wireless communication channel. However, aspects of the present disclosure are not limited to these wireless channels, and other PHY layer links and / or other wireless channels may be used. Additionally, non-AP MLD 604 may include fewer or more radios / transceivers.

[0087] According to some examples, each transceiver may include a lower medium access control (MAC) layer 622 and a physical (PHY) layer 624. In addition, each transceiver may have an associated address. However, aspects of the present disclosure are not limited to these examples and the radio component / transceiver may include other structures and / or components. Each transceiver / radio component may also be referred to as a station (STA) in this article. In addition, or alternatively, a station (STA) is associated with a specific communication link / channel. For example, a first STA is associated with a first link, and the first link is associated with a 2.4 GHz wireless communication channel. A second STA is associated with a second link, and the second link is associated with a 5 GHz wireless communication channel. And, a third STA is associated with a third link, and the third link is associated with a 6 GHz wireless communication channel.

[0088] According to some aspects, when the non-AP MLD 604 establishes a multi-link association with the AP MLD 602, the non-AP MLD 604 may create up to three STAs 626a-626c, each associated with one of the APs within the AP MLD 602 ​​and each STA 626 having its associated MAC address (different from the other STAs). In some examples, the non-AP MLD 602 ​​may initially assign a 5 / 6GHz transceiver to one of the STAs associated with the 5GHz and 6GHz APs, while the other STA 626c does not have an assigned radio, which may be referred to as a virtual STA. The virtual STA may have its own MAC address.

[0089] For example, the transceiver of STA 626a of non-AP MLD 604 may be associated with transceiver 610a of AP MLD 602 ​​(e.g., one AP) and communicate with transceiver 610a on link 606a associated with 2.4 GHz wireless communication channel. In this example, the transceiver of STA 626b of non-AP MLD 604 may be associated with transceiver 610b of AP MLD 602 ​​(e.g., another AP) and communicate with transceiver 610b on link 606b associated with 5 GHz wireless communication channel. In this example, the transceiver of STA 626c of non-AP MLD 604 may be a virtual STA. Virtual STA 626c may be associated with transceiver 610c of AP MLD 302 (e.g., a third AP) and communicate with transceiver 610c on link 606c associated with 6 GHz wireless communication channel.

[0090] According to some aspects, the non-AP MLD 604 may request that all TIDs (both downlink (DL) and uplink (UL)) be mapped to all links. According to some examples, to save power and / or enable virtual STAs, the non-AP MLD 604 may use only one of the STAs 626a-626c to track the DTIM beacon and maintain normal communication with the AP MLD 602. According to some aspects, the non-AP MLD 604 may put other STAs into sleep mode and activate them when needed. For example, as Figure 6 As shown, the non-AP MLD 604 can put STA 626a and virtual STA 626c into sleep mode. In this example, the non-AP MLD 604 can use STA 626b to track the DTIM beacon and maintain normal communication with the AP MLD 602. In this example, STA 626b can become the master STA of the non-AP MLD 604.

[0091] As discussed above, the sleep mode may be different from the power saving mode and / or the WNM sleep mode. According to some aspects, in the sleep mode (also referred to as the multi-link sleep mode), the non-AP MLD 604 does not track the DTIM beacon. Additionally or alternatively, in the multi-link sleep mode, the non-AP MLD 604 does not receive group addressed frames. Additionally or alternatively, in the multi-link sleep mode, the non-AP MLD 604 does not request individually addressed frames. Additionally or alternatively, in the multi-link sleep mode, the non-AP MLD 604 does not send keep-alive messages. Additionally or alternatively, in the multi-link sleep mode, the non-AP MLD 604 does not perform management handshakes to enter and exit the multi-link sleep mode. According to some aspects, the STA does not need to be awakened in the sleep mode to track the DTIM beacon, send keep-alive messages, and / or receive updated GTK / IGTK. Additionally, the STA may be able to quickly enter and exit the sleep mode in the sleep mode without being affected by management handshakes and / or processing delays.

[0092] According to some aspects, in response to the non-AP MLD 604 placing the STA 626a and the virtual STA 626c into sleep mode, the AP MLD 602 ​​does not buffer data (e.g., packets, frames, etc.) for the STAs in sleep mode. Figure 6 As shown, the buffer 613a of the lower MAC layer 612a and the buffer 613c of the lower MAC layer 612c have no data. In this example, the data from the buffer 611 is moved to the buffer 612b of the lower MAC layer 612b for transmission to the STA 626b that is not in sleep mode.

[0093] Figure 7FIG. 1 shows exemplary communications between an AP of an AP MLD and a STA of a non-AP MLD to enter sleep mode during association in accordance with some aspects of the present disclosure. It should be understood that it may not be necessary Figure 7 All operations in the Figure 7 The same sequence is used as shown. Figure 7 As shown, an AP MLD (e.g., AP MLD 110, 302, 402, 442, and / or 602) may include three APs. A first AP 610a may operate with a 2.4 GHz wireless communication channel. A second AP 610b may operate with a 5 GHz wireless communication channel. A third AP 610c may operate with a 6 GHz wireless communication channel. A non-AP MLD (e.g., non-AP MLD 120, 304, 404, 444, and / or 604) may include two STAs and one virtual STA. For example, a first STA 726a may operate with a 2.4 GHz wireless communication channel. A second STA 726b may operate with a 5 GHz wireless communication channel. A virtual STA 726c may operate with a 6 GHz wireless communication channel.

[0094] According to some examples, the STA 726a of the non-AP MLD may communicate with the AP 710a of the AP MLD to associate with the AP 710a. For example, the STA 726a may send a probe request 711 to the AP 710a. The probe request 711 may include a probe request frame to announce information about the STA 726a and / or query one or more parameters associated with the AP 710a. In response, the AP 710a may send a probe response 713 to the STA 726a. The probe response 713 may include one or more probe response frames, including, for example, the BSSID of the AP 710a, the supported data rate, and other relevant information. In addition, or alternatively, the AP 710a may send a beacon 715 to the STA 726a. According to some examples, at 716, a simultaneous authentication of peer entities (SAE) handshake may be performed between the STA 726a and the AP 710a and the STA 726a may be associated with the AP 710a.

[0095] Similarly, STA 726b and AP 710b may transmit messages so that STA 726b may be associated with AP 710b. For example, STA 726b may send a probe request 717 to AP 710b. The probe request 717 may include a probe request frame to announce information about STA 726b and / or query one or more parameters associated with AP 710b. In response, AP 710b may send a probe response 719 to STA 726b. The probe response 719 may include one or more probe response frames, including, for example, the BSSID of AP 710b, supported data rates, and other relevant information. In addition, or alternatively, AP 710b may send a beacon 721. According to some examples, STA 726b may send an association request 725 to AP 710b. According to some examples, the association request 725 may also be referred to as a multi-link association request or a multi-link setup because it is used to establish an association across all links. In one exemplary aspect, the association request 725 may include information and / or a request to the AP 710b (and corresponding AP MLD) to map all TIDs to all links (including virtual links), such as, e.g. Figure 4A and / or Figure 6 In some examples, mapping all TIDs to all links may result in more flexible operation without remapping overhead. Alternatively, association request 725 may include information and / or a request to AP 710b (and corresponding AP MLD) to map different TIDs to different links, such as, for example Figure 4B In some examples, association request 725 may include information and / or a request to AP 710b (and corresponding AP MLD) for a different mapping between TIDs and links.

[0096] Additionally, or alternatively, the association request 725 may also include information indicating to the AP 710b (and the AP MLD) that the STAs 726a and 726c have entered or will enter a sleep mode. At 727, the STAs 726a and 726c enter a sleep mode. In some examples, operation 727 may be performed before the association request 725. Alternatively, operation 727 may be performed after the association request 725. In some examples, operation 727 may be performed simultaneously or substantially simultaneously with the association request 725. According to some examples, information about TID / link mapping and / or information about the association mode may also be included in a protected association message, such as, but not limited to, a 4-way handshake message 731 in addition to or in lieu of the association request 725. In some examples, having this information in the protected association message may prevent a denial of service attack.

[0097] In response to the association request 725 and in response to the elements of the association request 725 matching the capabilities of the AP 710b, the AP 710b and the STA 726b may be associated and the AP 710b may send an association response 729 to the STA 726b. In some examples, a 4-way handshake 731 may be performed between the AP 710b and the STA 726b. In some examples, the handshake 731 may also include transmitting the GTK / IGTK of all APs 710a-710c (and / or all links associated with STAs in awake mode and sleep mode) to the STA 726b. According to some aspects, the STA may use a group temporary key (GTK) to decrypt multicast and / or broadcast traffic from, for example, an AP. The integrity GTK (IGTK) may also be used to check the integrity of multicast and / or broadcast traffic from, for example, an AP.

[0098] According to some examples, AP 710c may transmit beacon 723 in addition to beacon 721. In some examples, beacons 721 and / or 723 may be transmitted in a broadcast manner.

[0099] In some examples, after associating STA 726b and AP 710b and notifying AP MLD that STA 726a and 726c have entered sleep mode, AP 710a and AP 710c do not buffer any downlink data at 733a and 733c. In addition, AP 710a and 710c do not transmit data to STA 726a and 726c. In some examples, AP 710a may transmit a DTIM beacon (743) and / or broadcast / multicast data (745), but STA 726a and / or 726c do not receive these transmissions. In addition, according to some examples, AP 710c may transmit a DTIM beacon (747) and / or broadcast / multicast data (749), but STA 726a and / or 726c do not receive these transmissions.

[0100] According to some examples, STA 726b and AP 710b may negotiate block acknowledgement (BA) operations and / or parameters during BA scheme setup. BA scheme setup may include messages 735-741. For example, STA 726b may send an add block acknowledgement (ADDBA) request 735 (including an ADDBA frame) to AP 710b and receive an ADDBA response 737 (including an ADDBA frame). ADDBA signaling 735 and 737 may set a block acknowledgement transmission scheme. Additionally or alternatively, STA 726b may send a frame 739 with a power management (PM) value set to 1 (PM=1) to AP 710b and receive an acknowledgement (ACK) 741 from AP 710b. For example, STA 726b may enter a normal power saving mode (e.g., a lossless power saving mode) by transmitting a frame 739 with a PM field set to 1. When AP 710b correctly receives frame 739 (and sends back ACK 741), AP 710b may suspend unicast transmission to STA 726b until STA 726b sends a PS-Poll frame or a U-APSD trigger frame (step 755) to AP 710b to request unicast transmission.

[0101] According to some examples, AP 710b may transmit a DTIM beacon 751 and / or broadcast / multicast data 753 to STA 726b. Additionally or alternatively, STA 726b may transmit a power save poll (PS-Poll) / trigger 755 to AP 710b. According to some examples, AP 710b may transmit unicast data 757 to AP 710b.

[0102] Figure 8 8 shows exemplary communications between an AP MLD 802 and a non-AP MLD 804 to transmit keep-alive messages and GTK / IGTK updates in accordance with some aspects of the present disclosure. Figure 6 compared to, Figure 8 Two APs 810b and 810c of the AP MLD 802 and two STAs 826b and 826c (virtual STAs) of the non-AP MLD 804 are shown. However, the AP MLD 802 may include one or more other APs (e.g., Figure 6 ) and the non-AP MLD 804 may include one or more other STAs (e.g., Figure 6 shown), and relative to Figure 8 The various aspects of the present disclosure discussed may be applicable to all APs of the AP MLD 802 and / or all STAs of the non-AP MLD 804. Figure 8In the example of , STA 826b is in awake mode, wherein STA 826b is configured to track DTIM beacons, send keep-alive messages, and / or receive updated GTK / IGTK. In this example, virtual STA 826c is in sleep mode. According to some examples, all TIDs (e.g., DL TIDs) are mapped to all links in AP MLD 802, and / or all TIDs (e.g., UL TIDs) are mapped to all links in non-AP MLD 804.

[0103] According to some aspects, the AP MLD 802 may specify different idle periods for different links, STAs, APs, and / or BSSs, such as, but not limited to, a BSS maximum idle period. In some examples, the BSS maximum idle period is the maximum time that a STA can be idle (e.g., the AP does not receive any frames from the STA) before the AP disassociates from the STA. For example, the AM MLD 802 may identify a first BSS maximum idle period for AP 810b, link 806b, and STA 826b, and may identify a second BSS maximum idle period for AP 810c, link 806c, and STA 826c. In some examples, the first BSS maximum idle period and the second BSS maximum idle period are different from each other. However, aspects of the present disclosure are not limited to this example, and the first BSS maximum idle period and the second BSS maximum idle period may be the same.

[0104] The non-AP MLD 804 may send a keep-alive message 801 to the AP MLD 802 to satisfy the BSS maximum idle period. In some examples, the association between the AP MLD 802 and the non-AP MLD 804 is at a device level, and the non-AP MLD 804 will satisfy the keep-alive transmission requirements for at least one of the links in order to maintain the association of the ML with the AP MLD 802. According to some aspects, since the STA 826c is in a sleep mode, the STA 826b is configured to transmit the keep-alive message 801 on the link 806b. In some examples, the STA 826b sends the keep-alive message 801 on the link 806b within the minimum (e.g., the shorter) of the first BSS maximum idle period and the second BSS maximum idle period identified by the AP MLD 802 to maintain the association. Alternatively, STA 826b sends a keep alive message 801 on link 806b within the maximum of the first BSS maximum idle period and the second BSS maximum idle period identified by AP MLD 802 to maintain the association.

[0105] According to some aspects, a STA may use a group temporary key (GTK) to decrypt multicast and / or broadcast traffic from, for example, an AP. An integrity GTK (IGTK) may also be used to check the integrity of multicast and / or broadcast traffic from, for example, an AP. In some examples, the STA may use a group temporary key (GTK) to decrypt multicast and / or broadcast traffic from, for example, an AP. Figure 7 GTK and / or IGTK are provided to STAs during handshake 716 and / or handshake 731 of AP MLD 802. In some examples, the GTK and / or IGTK may need to be updated due to, for example, the expiration of one or more timers or when one STA or multiple STAs have been disassociated from the AP. According to some examples, each AP 810b and 810c may have its GTK / IGTK and / or its updated GTK / IGTK different from other APs. Alternatively, two or more APs of AP MLD 802 may share GTK / IGTK and / or updated GTK / IGTK.

[0106] According to some aspects, when one AP of the AP MLD 802 is to update its GTK / IGTK, the AP MLD 802 may deliver the new / updated GTK / IGTK to any available STA of the associated non-AP MLD 804, which may be operating on a different link from the AP that is updating its GTK / IGTK. For example, when the AP 810c updates its GTK / IGTK, since the STA 826c is in sleep mode, the AP 810c does not directly transmit the updated GTK / IGTK over the link 806c. In this example, the AP 810c delivers its updated GTK / IGTK 803 to the AP 810b. The AP 810b may send the updated GTK / IGTK 803 to the STA 826b over the link 806b. After receiving the updated GTK / IGTK, the non-AP MLD 806 may update the GTK / IGTK of the STA 826c.

[0107] Although some examples are discussed with respect to updated GTK / IGTK, aspects of the present disclosure are not limited to these examples. The cross-link updates discussed with respect to updated GTK / IGTK may also be applied to other BSS operating parameter updates that are unicasted from the AP to each associated STA.

[0108] Fig. 9A and Fig. 9B 9 shows exemplary communications between an AP MLD 902 and a non-AP MLD 904 to enter and / or exit sleep mode during a link transition in accordance with some aspects of the present disclosure. Figure 69 shows two APs 910a and 910b of the AP MLD 902 and two STAs 926a and 926b of the non-AP MLD 904. However, the AP MLD 902 may include one or more APs (e.g., Figure 6 ) and the non-AP MLD 904 may include one or more STAs (e.g., Figure 6 9 ), and the various aspects of the present disclosure discussed with respect to FIG. 9 may be applied to all APs of the AP MLD 902 and / or all STAs of the non-AP MLD 904. Fig. 9A In the example of , STA 926a is in awake mode, wherein STA 926a is configured to track DTIM beacons, send keep-alive messages, and / or receive updated GTK / IGTK. In this example, STA 926b is in sleep mode. According to some examples, all TIDs (e.g., DL TIDs) are mapped to all links in AP MLD 902, and / or all TIDs (e.g., UL TIDs) are mapped to all links in non-AP MLD 904.

[0109] According to some examples, the non-AP MLD 904 may change the link the non-AP MLD 904 applies to communicate with the AP MLD 902. As a non-limiting example, Fig. 9A and Fig. 9B As shown, the non-AP MLD 904 may first use link 906a (e.g., a 2.4 GHz link) to communicate with the AP MLD 902 because, for example, link 906a has a longer range. In this non-limiting example, as the non-AP MLD 904 gets closer to the AP MLD 902, the non-AP MLD 904 may decide to transition to link 906b (e.g., a 5 GHz link) because, for example, link 906b has a better quality. In this example, the non-AP MLD 904 (using, for example, one or more processors) may control its STAs to transition STA 926a from an awake mode to a sleep mode and STA 926b from a sleep mode to an awake mode. In this example, STA 926a has its associated transceiver / radio components (e.g., Figure 2 220a), and STA 926b has a different associated transceiver / radio than STA 926a (e.g., Figure 2 transceiver 220b).

[0110] Fig. 9A and Fig. 9B An exemplary operation is shown in which STA 926a transitions from an awake mode to a sleep mode and STA 926b transitions from a sleep mode to an awake mode. Fig. 9AAs shown, AP 910a is using link 906a to communicate with STA 926a. In this example, buffer 913a (e.g., in the lower MAC layer of AP 910a) includes data (e.g., packets, frames, etc.) to be sent to STA 926a. In this example, buffer 913b (e.g., in the lower MAC layer of AP 910b) does not include any data because STA 926b is in sleep mode.

[0111] According to some examples, as an exemplary step in a link transition (e.g., the first step in a link transition and / or before a link transition), STA 926b may transition from a sleep mode to a wake-up mode and transmit a frame 901 (such as, but not limited to, a PS-Poll frame and / or a U-APSD trigger frame) to AP 910b to indicate that STA 926b has exited the sleep mode.

[0112] According to some examples, as another exemplary step in the link transition, and after receiving frame 901, AP MLD 902 may stop buffering new data in, for example, buffer 913a, such as Fig. 9B In this example, AP MLD 902 may stop moving new packets from buffer 911 to buffer 913a. As another exemplary step, AP MLD 902 may use AP 910a to clear buffered data in buffer 913a, such as Fig. 9B For example, AP 910a may complete transmission of buffered data using AP 910a and link 906a until there is no more data in buffer 913a (eg, More Data=0).

[0113] like Fig. 9B As shown, STA 926b has transitioned to awake mode, and as another exemplary step in the link transition, STA 926a is transitioning to sleep mode. In some examples, before transitioning to sleep mode, STA 926a may send a message and / or frame 903 to AP 910a to indicate that STA 926a is transitioning to sleep mode. In some examples, STA 926a may use the A-control field in the MAC header of frame 903 to indicate that STA 926a is transitioning to sleep mode. However, aspects of the present disclosure are not limited to this example, and frame 903 may include other information to indicate that the STA is transitioning to sleep mode. According to some examples, as another exemplary step in the link transition, and after receiving frame 903, AP MLD 902 may stop buffering new data in, for example, buffer 913a, such as Fig. 9BIn this example, AP MLD 902 may stop moving new packets from buffer 911 to buffer 913a. As another exemplary step, AP MLD 902 may use AP 910a to clear buffered data in buffer 913a, such as Fig. 9B For example, AP 910a may complete transmission of buffered data using AP 910a and link 906a until there is no more data in buffer 913a (eg, More Data=0).

[0114] Fig.10 1 shows exemplary communications between an AP MLD 1002 and a non-AP MLD 1004 to enter and / or exit a sleep mode during a link transition in accordance with some aspects of the present disclosure. Figure 6 compared to, Fig.10 Two APs 1010b and 1010c of the AP MLD 1002 and two STAs 1026b and 1026c (virtual STAs) of the non-AP MLD 1004 are shown. However, the APMLD 1002 may include one or more APs (e.g., Figure 6 ) and the non-AP MLD 1004 may include one or more STAs (e.g., Figure 6 shown), and relative to Fig.10 The various aspects of the present disclosure discussed may be applicable to all APs of the AP MLD 1002 and / or all STAs of the non-AP MLD 1004. Fig.10 In the example of , STA 1026b is in awake mode, wherein STA 1026b is configured to track DTIM beacons, send keep-alive messages, and / or receive updated GTK / IGTK. In this example, virtual STA 1026c is in sleep mode. According to some examples, all TIDs (e.g., DL TIDs) are mapped to all links in AP MLD 1002, and / or all TIDs (e.g., UL TIDs) are mapped to all links in non-AP MLD 1004.

[0115] According to some examples, the non-AP MLD 1004 may change the link that the non-AP MLD 1004 applies to communicate with the AP MLD 1002. As a non-limiting example, Fig.10As shown, the non-AP MLD 1004 may first use link 1006b (e.g., a 5 GHz link) to communicate with the AP MLD 1002. In this non-limiting example, the non-AP MLD 1004 may decide to transition to link 1006c (e.g., a 6 GHz link) because, for example, link 1006c has a better quality. In this example, the non-AP MLD 1004 (using, for example, one or more processors) may control its STAs to transition STA 1026b from an awake mode to a sleep mode and to transition virtual STA 1026c from a sleep mode to an awake mode. In this example, STAs 1026b and 1026c may share the same transceiver / radio components (e.g., Figure 2 The non-AP MLD 1004 (using, for example, one or more processors) may control the shared transceiver to operate at the frequency of the second link (e.g., link 1006c) rather than the frequency of the first link (e.g., link 1006b).

[0116] Fig.10 An exemplary operation is shown in which STA 1026b transitions from awake mode to sleep mode and virtual STA 1026c transitions from sleep mode to awake mode. Fig.10 As shown, AP 1010b is communicating with STA 1026b using link 1006b. In this example, buffer 1013b (eg, in a lower MAC layer of AP 1010b) includes data (eg, packets, frames, etc.) to be sent to STA 1026b.

[0117] According to some examples, as an exemplary step in the link transition (e.g., as the first step in the link transition and / or before the link transition), STA 1026b is transitioning from the wake-up mode to the sleep mode. In some examples, before transitioning to the sleep mode, STA 1026b may send a message and / or frame 1003 to AP 1010b to indicate that STA 1026b is transitioning and / or has transitioned to the sleep mode. In some examples, STA 1026b may use the A-control field in the MAC header of frame 1003 to indicate that STA 1026b is transitioning to the sleep mode. However, aspects of the present disclosure are not limited to this example, and frame 1003 may include other information to indicate that the STA is transitioning to the sleep mode.

[0118] According to some examples, as another exemplary step in the link transition, and after receiving frame 1003, AP MLD 1002 may stop buffering new data in, for example, buffer 1013b. In this example, AP MLD 1002 may stop moving new packets from buffer 1011 to buffer 1013b. As another exemplary step, AP MLD 1002 may use AP 1010b to clear buffered data in buffer 1013b. For example, AP 1010b may complete transmission of buffered data using AP 1010a and link 1006b until there is no more data in buffer 1013b (e.g., more data=0).

[0119] According to some examples, as another exemplary step in the link transition (e.g., a second step in the link transition), the non-AP MLD 1004 may switch the transceiver / radio component from the STA 1026b to the STA 1026c. According to some aspects of the present disclosure, switching from the STA 1026b to the STA 1026c may include using the transceiver associated with the link 1006c (e.g., Figure 2 220c) rather than the transceiver associated with link 1006b (e.g., Figure 2 Additionally, or alternatively, switching from STA 1026b to STA 1026c may include controlling a single transceiver (e.g., transceiver 220) to operate at a frequency of link 1006c rather than at a frequency of link 1006b.

[0120] According to some examples, as another exemplary step in the link transition (e.g., the third step in the link transition), the STA 1026c may transition from the sleep mode to the wake-up mode and transmit a frame 1001 (such as, but not limited to, a PS-Poll frame and / or a U-APSD trigger frame) to the AP 1010c to indicate that the STA 1026c has exited the sleep mode. In some examples, the APMLD 1002 may move the new packet from the buffer 1011 to the buffer 1013c of the AP 1010c (e.g., in the lower MAC layer of the AP 1010c) after receiving the frame 1001. Alternatively, the AP MLD 1002 may move the new packet from the buffer 1011 to the buffer 1013c of the AP 1010c after receiving the frame 1003 but before receiving the frame 1001.

[0121] Fig.11 1 shows exemplary communications between an AP MLD 1102 and a non-AP MLD 1104 to enter and / or exit a sleep mode during a fast link switch according to some aspects of the present disclosure. Figure 6 compared to, Fig.11Two APs 1110b and 1110c of the AP MLD 1102 and two STAs 1126b and 1126c (virtual STAs) of the non-AP MLD 1104 are shown. However, the AP MLD 1102 may include one or more APs (e.g., Figure 6 ) and the non-AP MLD 1104 may include one or more STAs (e.g., Figure 6 shown), and relative to Fig.11 The various aspects of the present disclosure discussed may be applicable to all APs of the AP MLD 1102 and / or all STAs of the non-AP MLD 1104. Fig.11 In the example of , STA 1126b is in awake mode, wherein STA 1126b is configured to track DTIM beacons, send keep-alive messages, and / or receive updated GTK / IGTK. In this example, virtual STA 1126c is in sleep mode. According to some examples, all TIDs (e.g., DL TIDs) are mapped to all links in AP MLD 1102, and / or all TIDs (e.g., UL TIDs) are mapped to all links in non-AP MLD 1104.

[0122] Fig.11 An exemplary operation is shown in which STA 1126b transitions from an awake mode to a sleep mode and STA 1126c transitions from a sleep mode to an awake mode. In this exemplary aspect, the transition between links 1106b and 1106c is a fast link switch. According to some examples, in the above with respect to Fig. 9A , Fig. 9B and Fig.10 In the link transition discussed, the old link (the link to which the transition occurs) can still be used to transport the remaining data (e.g., data that has been buffered for transmission or retransmission from the old link). Fig.11 and Fig.12 In the fast link switching discussed, the old link (the link to which the transition occurs) may become immediately unavailable. For example, the connection on the old link is disconnected, errors and / or interference on the old link become above an acceptable threshold, etc. In some examples, the unavailability of the old link may last for a long period (e.g., longer than a threshold period), which may cause unacceptable delays for low-latency services. As described below with respect to Fig.11 and Fig.12Discussed in more detail, when the old link becomes unavailable, the non-AP MLD 1104 may quickly notify the AP MLD 1102 to stop buffering new data for the old link, stop transmission on the old link, move remaining data (e.g., buffered data for transmission or retransmission on the old link) from the old link to the new link or rebuffer remaining data from the host or higher MAC to the new link, and / or start transmission from the new link.

[0123] like Fig.11 106b. As shown, AP 1110b is using link 1106b to communicate with STA 1126b. In this example, buffer 1113b (e.g., in a lower MAC layer of AP 1110b) includes data (e.g., packets, frames, etc.) to be sent to STA 1126b. According to some examples, link 1106b becomes immediately unavailable at 1103 (e.g., the connection on link 1106b is disconnected, errors and / or interference on link 1106b become above an acceptable threshold, etc.). In some examples, STA 1126b may transition from an awake mode to a sleep mode.

[0124] According to some examples, as an exemplary step in the fast link switch, the non-AP MLD 1104 may switch the transceiver / radio component from the STA 1126b to the STA 1126c. According to some aspects of the present disclosure, switching from the STA 1126b to the STA 1126c may include using the transceiver associated with the link 1106c (e.g., Figure 2 220c) rather than the transceiver associated with link 1106b (e.g., Figure 2 Additionally, or alternatively, switching from STA 1126b to STA 1126c may include controlling a single transceiver (e.g., transceiver 220) to operate at a frequency of link 1106c rather than at a frequency of link 1106b.

[0125] According to some examples, as another exemplary step in the fast link switch, STA 1126c may transition from sleep mode to wake mode and transmit frame 1101 to AP 1110c to indicate that STA 1126c has exited sleep mode. In some examples, frame 1101 may include, but is not limited to, a PS-Poll frame and / or a U-APSD trigger frame. In some examples, STA 1126b may use the A-Control field in the MAC header of frame 1101 to indicate that STA 1126b is transitioning and / or has transitioned to wake mode.

[0126] According to some aspects, after receiving frame 1101, AP MLD 1102 may stop buffering new data in, for example, buffer 1113b. In this example, AP MLD 1102 may stop moving new packets from buffer 1111 to buffer 1113b. Additionally or alternatively, AP MLD 1102 may stop using AP 1110b to transmit data on link 1106b. Additionally or alternatively, AP MLD 1102 may move remaining data (e.g., buffered data in buffer 1113b for transmission or retransmission) from buffer 1113b to buffer 1113c (and / or other buffers of other new links). AP MLD 1102 may also rebuffer remaining data from buffer 1113b to buffer 1113c. AP MLD 1102 may begin transmitting remaining data and / or new data to STA 1126c of non-AP MLD 1104 using AP 1110c and link 1106c.

[0127] Fig.12 1 shows exemplary communications between an AP MLD 1202 and a non-AP MLD 1204 to enter and / or exit a sleep mode during a fast link switch according to some aspects of the present disclosure. Figure 6 compared to, Fig.12 Two APs 1210b and 1210c of the AP MLD 1202 and two STAs 1226b and 1226c (virtual STAs) of the non-AP MLD 1204 are shown. However, the AP MLD 1202 may include one or more other APs (e.g., Figure 6 ) and the non-AP MLD 1204 may include one or more other STAs (e.g., Figure 6 shown), and relative to Fig.12 The various aspects of the present disclosure discussed may be applicable to all APs of the AP MLD 1202 and / or all STAs of the non-AP MLD 1204. Fig.12 In the example of , STA 1226b is in awake mode, wherein STA 1226b is configured to track DTIM beacons, send keep-alive messages, and / or receive updated GTK / IGTK. In this example, virtual STA 1226c is in sleep mode. According to some examples, all TIDs (e.g., DLTIDs) are mapped to all links in AP MLD 1202, and / or all TIDs (e.g., UL TIDs) are mapped to all links in non-AP MLD 1204.

[0128] Fig.12An exemplary operation is shown in which STA 1226b transitions from an awake mode to a sleep mode and STA 1226c transitions from a sleep mode to an awake mode. In this exemplary aspect, the transition between links 1206b and 1206c is a fast link switch.

[0129] like Fig.12 12, AP 1210b is using link 1206b to communicate with STA 1226b. In this example, buffer 1213b (e.g., in a lower MAC layer of AP 1210b) includes data (e.g., packets, frames, etc.) to be sent to STA 1226b. According to some examples, link 1206b becomes unavailable (e.g., the connection on link 1106b is disconnected, errors and / or interference on link 1206b become above an acceptable threshold, etc.), but link 1206b remains available for a short period of time. In some examples, the short period of time may include the time to transmit a short frame. Fig.12 In an exemplary aspect, before STA 1226b transitions from awake mode to sleep mode and before link 1206b becomes unavailable, STA 1226b transmits frame 1203 to AP 1210b. In some examples, STA 1226b may use the A-control field in the MAC header of frame 1203 to indicate that STA 1226b is transitioning to awake mode and / or a fast link switch is occurring. For example, STA 1226b may use the A-control field in the MAC header of frame 1203 to indicate to AP 1210b that a fast link switch between links 1206b and 1206c is occurring. However, aspects of the present disclosure are not limited to this example, and frame 1203 may include other information to indicate that the STA is transitioning to sleep mode.

[0130] According to some aspects, after receiving frame 1203, AP MLD 1202 may stop buffering new data, for example, in buffer 1213b. In this example, AP MLD 1202 may stop moving new packets from buffer 1211 to buffer 1213b. Additionally or alternatively, AP MLD 1202 may stop transmitting data on link 1206b using AP 1210b. Additionally or alternatively, AP MLD 1202 may move remaining data (e.g., buffered data in buffer 1213b for transmission or retransmission) from buffer 1213b to buffer 1213c (and / or other buffers of other new links). AP MLD 1202 may also re-buffer remaining data from buffer 1213b to buffer 1213c.

[0131] According to some examples, as an exemplary step in the fast link switch, the non-AP MLD 1204 may switch the transceiver / radio component from the STA 1226b to the STA 1226c. According to some aspects of the present disclosure, switching from the STA 1226b to the STA 1226c may include using the transceiver associated with the link 1206c (e.g., Figure 2 220c) rather than the transceiver associated with link 1206b (e.g., Figure 2 Additionally, or alternatively, switching from STA 1226b to STA 1226c may include controlling a single transceiver (e.g., transceiver 220) to operate at a frequency of link 1206c rather than at a frequency of link 1206b.

[0132] According to some examples, as another exemplary step in the fast link switch, STA 1226c may transition from sleep mode to wake-up mode and transmit frame 1201 to AP 1210c to indicate that STA 1226c has exited sleep mode. In some examples, frame 1201 may include, but is not limited to, a PS-Poll frame and / or a U-APSD trigger frame to indicate that STA 1226b is transitioning and / or has transitioned to wake-up mode.

[0133] According to some aspects, after receiving frame 1201, AP MLD 1202 may begin transmitting remaining data and / or new data to STA 1226c of non-AP MLD 1204 using AP 1210c and link 1206c.

[0134] Fig.13 An exemplary frame format according to some aspects of the present disclosure is shown, which can be transmitted between an AP MLD and a non-AP MLD to transmit that a STA is entering (or has exited) sleep mode. For example, Fig.13 An exemplary format of frame 1301 is shown. The exemplary format of frame 1301 may be an exemplary format of one or more of frames 903, 1003, 1101, and / or 1203. According to some aspects, frame 1301 may include a MAC header 1303, a frame body (e.g., a MAC service data unit (MSDU) and / or an aggregated MSDU (A-MDSU)) 1306, and a frame check sequence (FCS—used for example for error detection and / or additional padding) 1308. Note that the length information provided for each field and / or subfield of frame 1301 is exemplary length information and aspects of the present disclosure are not limited to these examples.

[0135] In some examples, the MAC header 1303 may include fields such as, but not limited to, frame control, a duration field, addresses (e.g., one or more source addresses, one or more destination addresses, etc.), sequence control, quality of service (QoS) control, and HT control 1305, as understood by one of ordinary skill in the art. In various aspects of the present disclosure, one or more fields of the MAC header 1303 (such as, but not limited to, the HT control field 1305) may be used to communicate to the AP MLD that a STA other than the AP MLD is entering (or has exited) sleep mode.

[0136] In some examples, the MAC header 1303 may also include a QoS control field 1310. The QoS control field 1310 may include a field indicating a traffic identifier (TID). In a non-limiting example, the TID field of the QoS control field 1310 may include four bits. The TID may indicate the frame flow to which the frame 1301 (and / or the frame body 1306) belongs.

[0137] An exemplary format of the HT control field 1305 may include two bits, namely, VHT (very high throughput) 1312 and HE (high efficiency) 1314. Based on the values ​​of these two bits, a receiver device (e.g., an AP MLD) receiving the HT control field 1305 may determine the purpose and format of the HT control field 1305 and decode the HT control field 1305 accordingly. For example, if the value of the VHT 1312 bit is "0", the HT control field 1305 is a HT (high throughput) variant. If the value of the VHT 1312 bit is "1" and the value of the HE 1314 bit is "0", the HT control field 1305 is a VHT (very high throughput) variant. If the value of the VHT 1312 bit is "1" and the value of the HE 1314 bit is "1", the HT control field 1305 is a HE (high efficiency) variant.

[0138] According to some aspects, when a receiver device (e.g., an AP MLD) receives a frame 1301 with a MAC header 1303 including an HT control field 1305 with a value of "1" for the VHT 1312 bit and a value of "1" for the HE 1314 bit, the receiver device knows that the remainder of the HT control field 1305 is an A-control field 1307. Therefore, the receiver device can decode the A-control field 1307 accordingly. In some examples, the A-control field 1307 can include 30 bits. However, aspects of the present disclosure are not limited to this example.

[0139] In some aspects, the A-control field 1307 may include different control subfields 1309a-1309n and a padding field. In some examples, the control subfields 1309a-1309n may each have a variable size. The padding subfield may have 0 or more bits. According to some aspects, the non-AP MLD may be configured to use one or more control subfields 1309 to convey that the STA of the non-AP MLD is entering (or has exited) sleep mode.

[0140] For example, the control subfield 1309a of the A-control field 1307 may include one or more of a control identifier (ID) 1311 and control information 1313. According to some aspects, the control ID 1311 is set to a value not used for other purposes to convey that the non-AP MLD STA is entering (or has exited) sleep mode. In some examples, a value of "1" for the control ID 1311 may signal the operating mode of the non-AP MLD STA. In some examples, values ​​7-14 of the control ID 1311 are reserved. In some aspects, one or more of these values ​​may be used to convey to the AP-MLD that the non-AP MLD STA is entering (or has exited) sleep mode.

[0141] Fig.14 An exemplary method 1400 for a wireless system to support and implement a sleep mode for a multi-link wireless communication network such as a wireless local area network (WLAN) according to some aspects of the present disclosure is shown. For convenience and not limitation, the sleep mode may be described with respect to FIG. Fig.13 elements to describe Fig.14 Method 1400 may represent operation of an electronic device (eg, an AP MLD and / or a non-AP MLD as discussed in the present disclosure) to implement a sleep mode of a multi-link wireless communication network. Method 1400 may also be performed by Figure 2 System 200 and / or Fig.15 The method 1400 is performed by a computer system 1500. However, the method 1400 is not limited to the specific aspects depicted in those figures, and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and these operations may not be performed in the same manner as described above. Fig.14 The same sequence as shown is performed.

[0142] At 1402, a first station (STA) using a first multi-link device (MLD) may transmit a first message to a second MLD on a first link of a wireless network. According to some examples, the first message may indicate that a second STA of the first MLD associated with a second link of the wireless network is in a sleep mode. For example, the first MLD may include a non-AP MLD that transmits the non-AP MLD to an AP MLD during, for example, an association operation, that the second STA is in a sleep mode. According to some examples, the non-AP MLD may include one or more processors that are communicatively coupled to the first STA and the second STA and are configured to control operations of the first STA and the second STA. In some examples, the one or more processors are configured to transmit the message to the second MLD using the first STA.

[0143] In some examples, the message may include an association request transmitted during an association of the first MLD and the second MLD. Additionally, the message may also include a request to map one or more traffic identifiers (TIDs) at the second MLD to the first link and the second link.

[0144] After associating the first MLD and the second MLD, the first MLD and the second MLD may transmit at least one of a data frame, a management frame, or a control frame. For example, at 1404, the first MLD transmits at least one of a data frame, a management frame, or a control frame with the second MLD on the first link using the first STA.

[0145] According to some examples, the first MLD may be configured to transmit a keep-alive message to the second MLD, as described above with respect to, for example Figure 8 As discussed. For example, at 1406, a keep-alive message is transmitted within a minimum (e.g., the shorter) of a first time period and a second time period (e.g., using one or more processors and using a first STA). In some examples, the first time period is a first idle period (e.g., a first maximum idle period) associated with the first STA and / or the first link, and the second time period is a second idle period (e.g., a second maximum idle period) associated with the second STA and / or the second link.

[0146] According to some examples, the first MLD may be configured to receive at least one of an updated group transient key (GTK) or an updated integrity GTK (IGTK) from the second MLD, as described above with respect to, for example Figure 8 For example, at 1408, at least one of an updated group temporary key (GTK) or an updated integrity GTK (IGTK) associated with a second STA in sleep mode is received from a second MLD using, for example, one or more processors and using the first STA.

[0147] At 1410, one or more operations associated with entering and / or exiting a sleep mode during a link transition may be performed, such as with respect to Fig. 9A , Fig. 9B and Fig.10 discussed.

[0148] In one example, 1410 may include, in response to the second STA being transitioned to an awake mode, using the second STA to transmit a frame to the second MLD indicating that the second STA has exited a sleep mode and controlling the first STA to enter a sleep mode. In some examples, the first STA includes a first transceiver, and the second STA includes a second transceiver different from the first transceiver.

[0149] In one example, 1410 may include transmitting, using the first STA, to the second MLD a first frame indicating that the first STA is transitioning to a sleep mode and causing the second STA to transition from the sleep mode to a wake-up mode. 1410 may also include transmitting, using the second STA, to the second MLD a second frame indicating that the second STA has exited the sleep mode in response to the second STA transitioning to a wake-up mode. In some examples, causing the second STA to transition from the sleep mode to the wake-up mode may include controlling a transceiver of the first MLD associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0150] At 1412, one or more operations associated with entering and / or exiting a sleep mode during a fast link switch may be performed, such as with respect to Fig.11 and Fig.12 discussed.

[0151] In one example, 1412 may include determining that the first link is unavailable (e.g., a connection on the first link is disconnected, errors and / or interference on the first link become above an acceptable threshold, etc.). In response to the determination, 1412 may also include controlling the first STA to transition from an awake mode to a sleep mode and causing the second STA to transition from the sleep mode to an awake mode. 1412 may also include, using the second STA, transmitting a frame to the second MLD indicating that the second STA has exited the sleep mode. In some examples, causing the second STA to transition from the sleep mode to the awake mode may include controlling a transceiver of the first MLD associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0152] In one example, 1412 may include determining that the first link is unavailable, and in response to the determination, transmitting a first frame to the second MLD using the first link indicating that a link switch is occurring. 1412 may also include controlling the first STA to transition from an awake mode to a sleep mode and causing the second STA to transition from the sleep mode to an awake mode. 1412 may also include using the second STA to transmit a frame to the second MLD indicating that the second STA has exited the sleep mode. In some examples, causing the second STA to transition from the sleep mode to the awake mode may include controlling a transceiver of the first MLD associated with the first STA and the second STA to operate at a frequency associated with the second link.

[0153] For example, one or more computer systems such as Fig.15 The computer system 1500 shown in the figure implements various aspects. The computer system 1500 can be any well-known computer capable of performing the functions described herein, such as Figure 1A and Figure 1B Device 110, 120 or Figure 2 Device 200. Computer system 1500 includes one or more processors (also referred to as central processing units or CPUs), such as processor 1504. Processor 1504 is connected to a communication infrastructure 1506 (e.g., a bus). Computer system 1500 also includes user input / output devices 1503, such as a monitor, keyboard, pointing device, etc., that communicate with communication infrastructure 1506 through user input / output interface 1502. Computer system 1500 also includes main memory or internal memory 1508, such as random access memory (RAM). Main memory 1508 may include one or more levels of cache. Control logic components (e.g., computer software) and / or data are stored in main memory 1508.

[0154] The computer system 1500 may also include one or more secondary storage devices or memories 1510. The secondary storage 1510 may include, for example, a hard disk drive 1512 and / or a removable storage device or drive 1514. The removable storage drive 1514 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0155] The removable storage drive 1514 can interact with a removable storage unit 1518. The removable storage unit 1518 includes a computer usable or readable storage device on which computer software (control logic components) and / or data are stored. The removable storage unit 1518 can be a floppy disk, a magnetic tape, an optical disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 1514 reads and / or writes to the removable storage unit 1518 in a well-known manner.

[0156] According to some aspects, secondary storage 1510 may include other devices, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 1500. Such devices, tools, or other methods may include, for example, a removable storage unit 1522 and an interface 1520. Examples of removable storage unit 1522 and interface 1520 may include a program cartridge and cartridge interface (such as found in a video game device), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0157] The computer system 1500 may also include a communication or network interface 1524. The communication interface 1524 enables the computer system 1500 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 1528). For example, the communication interface 1524 may allow the computer system 1500 to communicate with a remote device 1528 via a communication path 1526, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic and / or data may be transmitted to and from the computer system 1500 via the communication path 1526.

[0158] The operations in the foregoing aspects can be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or in both hardware and software. In some aspects, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 1500, main memory 1508, auxiliary memory 1510, and removable storage units 1518 and 1522, as well as tangible articles embodying any combination of the foregoing. When executed by one or more data processing devices (such as computer system 1500), such control logic causes such data processing devices to operate as described herein.

[0159] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use the Fig.15 The various aspects of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the various aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0160] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary aspects of the present disclosure as contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0161] Although the present disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the various aspects are not limited to the software, hardware, firmware and / or entities shown in the figures and / or described herein. In addition, the various aspects (whether or not explicitly described herein) have significant practicality for fields and applications outside the examples described herein.

[0162] Various aspects have been described herein with the aid of functional building blocks that illustrate the implementation of specific functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are properly performed. In addition, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0163] References herein to "one aspect," "aspects," "some aspects," "examples," "some examples," or similar phrases indicate that the described aspects may include a particular feature, structure, or characteristic, but each aspect may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same aspect. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with one aspect, it is within the knowledge of a person skilled in the relevant art to incorporate such feature, structure, or characteristic into other aspects, whether or not explicitly mentioned or described herein.

[0164] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.

[0165] As described above, various aspects of the present technology may include collecting and using data available from various sources, thereby (for example) improving or enhancing functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0166] The present disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for the legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to defend and safeguard access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards that include specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0167] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, the present technology may be configured to allow users to selectively participate in "opt-in" or "opt-out" of collecting personal information data at any time during (for example) registration for a service or thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[0168] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0169] Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A multi-link device MLD, comprising: A first station STA, the first STA is associated with a first link of the wireless network and is configured to communicate with a second MLD on the first link; a second STA, the second STA being associated with a second link of the wireless network; a third STA, the third STA being associated with a third link of the wireless network; One or more processors, the one or more processors are communicatively coupled to the first STA, the second STA, and the third STA and are configured to: using the first STA on the first link to transmit to the second MLD a message indicating that the second STA and the third STA are exiting the first mode; as well as The second STA and the third STA are transitioned from the first mode to a second mode, wherein the second STA and the third STA use less power in the second mode than in the first mode. 2 . The MLD of claim 1 , wherein the one or more processors are configured to transition the second STA and the third STA from the first mode to the second mode before transmitting the message to the second MLD. 3 . The MLD of claim 1 , wherein the one or more processors are configured to transition the second STA and the third STA from the first mode to the second mode after transmitting the message to the second MLD. 4 . The MLD of claim 1 , wherein the one or more processors are configured to transition the second STA and the third STA from the first mode to the second mode substantially simultaneously with transmitting the message to the second MLD. 5 . The MLD of claim 1 , wherein the message indicating that the second STA and the third STA are exiting the first mode comprises a message indicating that the second STA and the third STA are entering the second mode.

6. The MLD of claim 1 , wherein the message comprises an association request transmitted during an association of the MLD and the second MLD, and wherein the message further comprises a request for the second MLD to map one or more traffic identifiers (TIDs) to the first link, the second link, and the third link.

7. The MLD of claim 1 , wherein the message comprises an association request transmitted during an association of the MLD and the second MLD, and wherein the message further comprises a request for the second MLD to map a first traffic identifier (TID) to the first link, a second TID to a second link, and a third TID to a third link.

8. The MLD of claim 1, wherein: When in the second mode, the second STA and the third STA do not track a transmission traffic indication map DTIM beacon, and When in the first mode, the second STA tracks the DTIM beacon.

9. The MLD of claim 1 , wherein the one or more processors are configured to receive at least one of an updated group temporary key GTK or an updated integrity GTK (IGTK) associated with the first link, the second link, and the third link using the first STA and from the second MLD.

10. A method comprising: A first station STA using a multi-link device MLD on a first link of a wireless network transmits a message to a second MLD indicating that a second STA and a third STA of the MLD are exiting a first mode, wherein the second STA is associated with a second link of the wireless network and the third STA is associated with a third link of the wireless network; as well as The second STA and the third STA are transitioned from the first mode to a second mode, wherein the second STA and the third STA use less power in the second mode than in the first mode. 11 . The method of claim 10 , wherein transitioning the second STA and the third STA from the first mode to the second mode comprises transitioning the second STA and the third STA from the first mode to the second mode before transmitting the message to the second MLD. 12 . The method of claim 10 , wherein transitioning the second STA and the third STA from the first mode to the second mode comprises transitioning the second STA and the third STA from the first mode to the second mode after transmitting the message to the second MLD.

13. The method of claim 10, wherein transitioning the second STA and the third STA from the first mode to the second mode comprises transitioning the second STA and the third STA from the first mode to the second mode substantially simultaneously with transmitting the message to the second MLD. 14 . The method of claim 10 , wherein the message indicating that the second STA and the third STA are exiting the first mode comprises a message indicating that the second STA and the third STA are entering the second mode.

15. The method of claim 10, wherein the message comprises an association request transmitted during an association of the MLD and the second MLD, and wherein the message further comprises a request for the second MLD to map one or more traffic identifiers (TIDs) to the first link, the second link, and the third link.

16. The method of claim 10, wherein the message comprises an association request transmitted during an association of the MLD and the second MLD, and wherein the message further comprises a request for the second MLD to map a first traffic identifier (TID) to the first link, a second TID to a second link, and a third TID to a third link.

17. The method of claim 10, wherein: When in the second mode, the second STA and the third STA do not track a transmission traffic indication map DTIM beacon, and When in the first mode, the second STA tracks the DTIM beacon.

18. The method according to claim 10, further comprising: At least one of an updated group temporary key GTK or an updated integrity GTK (IGTK) associated with the first link, the second link, and the third link is received using the first STA and from the second MLD.

19. A multi-link device MLD, comprising: a first access point AP, the first AP being associated with a first link of a wireless network and being configured to communicate with a second MLD on the first link; a second AP, the second AP being associated with a second link of the wireless network; a third AP, the third AP being associated with a third link of the wireless network; one or more processors, the one or more processors being communicatively coupled to the first AP, the second AP, and the third AP and configured to: receiving, using the first AP on the first link, a message from a first station STA of a second MLD, the message indicating that a second STA and a third STA of the second MLD are exiting a first mode; as well as The second AP and the third AP are prevented from buffering downlink (DL) data of the second STA and the third STA of the second MLD transitioned to a second mode in which the second STA and the third STA use less power than in the first mode.

20. The MLD of claim 19, wherein the one or more processors are configured to use the first AP and transmit to the second MLD at least one of an updated group temporary key GTK or an updated integrity GTK (IGTK) associated with the first link, the second link, and the third link.

Images