Apparatus, system and method for fast basic service set (BSS) translation (FT)

Abstract

For example, an STA may: send a fast basic service set (BSS) translation (FT) request to an AP via a current AP associated with the STA, where the FT request is configured to: request FT from the current AP to a target AP; processing an FT response from the target AP after the FT request, the FT response being received by the STA via the current AP; after the FT responds, a re-association request is sent to the target AP via the current AP, and the re-association request is used for requesting association between the STA and the target AP; processing a re-association response from the target AP after the re-association request, the re-association response being received by the STA via the current AP; and switching the STA from the current AP to the target AP for communication via an associated session between the STA and the target AP.

Description

Technical Field

[0001] Aspects described herein generally relate to fast basic service set (BSS) transition (FT). Background Art

[0002] In some wireless communication networks, a wireless communication station (STA) may be configured to communicate with an access point (AP).

[0003] For example, when a STA moves out of the range of a first AP, the mobile device may need to switch communications from the first AP to a second AP. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] For simplicity and clarity of illustration, the elements shown in the drawings may not be drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity of presentation. In addition, reference numerals may be repeated between the drawings to indicate corresponding or similar elements. These drawings are listed below.

[0005] Figure 1 is a schematic block diagram illustration of a system according to some exemplary aspects.

[0006] Figure 2 is a schematic illustration of a multi-link communication scheme that can be implemented according to some exemplary aspects.

[0007] Figure 3 is a schematic illustration of a multi-link communication scheme that can be implemented according to some exemplary aspects.

[0008] Figure 4 is a schematic illustration of a multi-link device (MLD) fast basic service set (BSS) transition (FT) scheme that may be implemented according to some exemplary aspects.

[0009] Figure 5 is a schematic illustration of FT utilizing a backhaul connection according to some demonstrative aspects.

[0010] Figure 6 is a schematic illustration of communications and operations according to the FT protocol, according to some exemplary aspects.

[0011] Figure 7 is a schematic flow chart of an FT method according to some exemplary aspects.

[0012] Figure 8 is a schematic flow chart of an FT method according to some exemplary aspects.

[0013] Fig. 9 is a schematic flow chart of an FT method according to some exemplary aspects.

[0014] Fig.10is a schematic illustration of an article of manufacture according to some exemplary aspects. DETAILED DESCRIPTION

[0015] In the following detailed description, many specific details are set forth in order to provide a thorough understanding of some aspects. However, those skilled in the art will appreciate that some aspects may be practiced without these specific details. In other cases, well-known methods, processes, components, units and / or circuits are not described in detail to avoid obscuring the discussion.

[0016] Discussions herein utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “creating,” “analyzing,” “examining,” and the like may refer to operations and / or processes on a computer, computing platform, computing system, or other electronic computing device that manipulate and / or transform data represented as physical (e.g., electronic) quantities within a computer’s registers and / or memories into other data similarly represented as physical quantities within a computer’s registers and / or memories or other information storage media that may store instructions for performing the operations and / or processes.

[0017] As used herein, the terms “plurality” and “plurality” include, for example, “a plurality” or “two or more.” For example, “a plurality of items” includes two or more items.

[0018] References to "one aspect," "an aspect," "exemplary aspects," "various aspects," etc. indicate that the aspects so described may include a particular feature, structure, or characteristic, but not every aspect must include the particular feature, structure, or characteristic. Furthermore, repeated use of the phrase "in one aspect" does not necessarily refer to the same aspect, although it may.

[0019] As used herein, unless otherwise indicated, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects merely indicates that different instances of similar objects are mentioned and is not intended to imply that the objects so described must be in a given order temporally, spatially, hierarchically, or in any other manner.

[0020] Some aspects may be used in conjunction with various devices and systems, such as user equipment (UE), mobile devices (MD), wireless stations (STA), personal computers (PC), desktop computers, mobile computers, laptop computers, notebook computers, tablet computers, server computers, handheld computers, handheld devices, wearable devices, sensor devices, Internet of Things (IoT) devices, personal digital assistant (PDA) devices, handheld PDA devices, on-board devices, off-board devices, hybrid devices, on-board devices, off-board devices, mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (APs), wired or wireless routers, wired or wireless modems, video devices, audio devices, audio video (A / V) devices, wired or wireless networks, wireless area networks, wireless video area networks (WVANs), local area networks (LANs), wireless LANs (WLANs), personal area networks (PANs), wireless PANs (WPANs), etc.

[0021] Some aspects can be used in conjunction with the following devices and / or networks: according to existing IEEE 802.11 standards (including IEEE 802.11-2020 (IEEE 802.11-2020, IEEE Standard for Information Technology—Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks—Specific Requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, December 2020) and / or IEEE802.11be (IEEE P802.11be / D1.5 Draft Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 8: Enhancements for extremely high Devices and / or networks operating according to existing cellular specifications and / or protocols and / or future versions and / or derivative versions thereof; and / or units and / or devices as part of the above networks; etc.

[0022] Some aspects may be used in conjunction with the following devices: one-way and / or two-way radio communication systems, cellular radio-telephone communication systems, mobile phones, cellular phones, wireless phones, personal communication system (PCS) devices, PDA devices including wireless communication devices, mobile or portable global positioning system (GPS) devices, devices including GPS receivers or transceivers or chips, devices including RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (e.g., smart phones), wireless application protocol (WAP) devices, etc.

[0023] Some aspects may be used in conjunction with one or more types of wireless communication signals and / or systems, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), orthogonal frequency division multiple access (OFDMA), time division multiplexing (TDM), time division multiple access (TDMA), multi-user MIMO (MU-MIMO), space division multiple access (SDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee TM , ultra-wideband (UWB), 4G, fifth generation (5G) or sixth generation (6G) mobile networks, 3GPP, long term evolution (LTE), advanced LTE, enhanced data rates for GSM evolution (EDGE), etc. Other aspects may be used in various other devices, systems and / or networks.

[0024] As used herein, the term "wireless device" includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, etc. In some exemplary aspects, a wireless device may be or may include a peripheral device that may be integrated with a computer, or a peripheral device that may be attached to a computer. In some exemplary aspects, the term "wireless device" may optionally include a wireless service.

[0025] The term "transfer / communication" as used herein with respect to a communication signal includes sending a communication signal and / or receiving a communication signal. For example, a communication unit capable of transmitting a communication signal may include a transmitter for transmitting the communication signal to at least one other communication unit and / or a communication receiver for receiving a communication signal from at least one other communication unit. The verb "transfer" may be used to refer to an action of sending or an action of receiving. In one example, the phrase "transferring a signal" may refer to an action of sending a signal by a first device, and may not necessarily include an action of receiving a signal by a second device. In another example, the phrase "transferring a signal" may refer to an action of receiving a signal by a first device, and may not necessarily include an action of sending a signal by a second device. A communication signal may be sent and / or received, for example, in the form of a radio frequency (RF) communication signal and / or any other type of signal.

[0026] As used herein, the term "circuit" may refer to, be part of, or include an application specific integrated circuit (ASIC), an integrated circuit, an electronic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some aspects, some functions associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, the circuit may include logic that is at least partially operable in hardware.

[0027] The term "logic" may, for example, refer to computing logic embedded in the circuits of a computing device and / or computing logic stored in the memory of a computing device. For example, the logic may be accessed by a processor of a computing device to execute the computing logic, thereby performing computing functions and / or operations. In one example, the logic may be embedded in various types of memory and / or firmware, such as silicon blocks of various chips and / or processors. The logic may be included in various circuits and / or implemented as part of various circuits, such as radio circuits, receiver circuits, control circuits, transmitter circuits, transceiver circuits, processor circuits, etc. In one example, the logic may be embedded in volatile memory and / or non-volatile memory, including random access memory, read-only memory, programmable memory, magnetic memory, flash memory, permanent memory, etc. The logic may be executed by one or more processors using memory (e.g., registers, stacks, buffers, etc.) coupled to the one or more processors, such as as needed to execute the logic.

[0028] Some exemplary aspects may be used in conjunction with a WLAN (e.g., a WiFi network). Other aspects may be used in conjunction with any other suitable wireless communication network, such as a wireless local area network, a "piconet," a WPAN, a WVAN, etc.

[0029] Some exemplary aspects may be used in conjunction with a wireless communication network that communicates on a sub-10 Gigahertz (GHz) frequency band, such as the 2.4 GHz band, the 5 GHz band, the 6 GHz band, and / or any other frequency band below 10 GHz.

[0030] Some exemplary aspects may be used in conjunction with a wireless communication network that communicates in an extremely high frequency (EHF) band (also known as a “millimeter wave (mmWave)” band), such as a band within a band between 20 GHz and 300 GHz, such as a band above 45 GHz, such as the 60 GHz band, and / or any other mmWave band.

[0031] Some exemplary aspects may be used in conjunction with a wireless communication network communicating on a sub-10 GHz band and / or a mmWave band, such as described below. However, other aspects may be implemented using any other suitable wireless communication band, such as a 5G band, a band below 20 GHz, a Sub 1 GHz (S1G) band, a WLAN band, a WPAN band, etc.

[0032] Some exemplary aspects may be implemented by a mmWave STA (mSTA), which may include, for example, a STA having a radio transmitter capable of operating on a channel within the mmWave frequency band. In one example, mmWave communications may involve one or more directional links for communicating at a rate of multiple gigabits per second (e.g., at least 1 gigabit per second, such as at least 7 gigabits per second, at least 30 gigabits per second, or any other rate).

[0033] In some exemplary aspects, the mmWave STA may include a directional multi-gigabit (DMG) STA, and the DMG STA may be configured to communicate via a DMG frequency band. For example, the DMG frequency band may include a frequency band with a channel start frequency higher than 45 GHz.

[0034] In some exemplary aspects, the mmWave STA may include an enhanced DMG (EDMG) STA, which may be configured to implement one or more mechanisms that may be configured to: implement single-user (SU) and / or multi-user (MU) communications for downlink (DL) and / or uplink frames (UL) using a MIMO scheme. For example, the EDMG STA may be configured to implement one or more channel bundling mechanisms that may, for example, support communications over a channel bandwidth (BW) (also referred to as a "wide channel", "EDMG channel" or "bundled channel") comprising two or more channels (e.g., two or more 2.16 GHz channels). For example, the channel bundling mechanism may include, for example, a mechanism and / or operation in which two or more channels (e.g., 2.16 GHz channels) may be combined, for example, for higher packet transmission bandwidth, for example, to enable higher data rates compared to transmissions on a single channel. Some exemplary aspects are described herein with respect to communication over a channel BW comprising two or more 2.16 GHz channels, however, other aspects may be implemented with respect to communication over the following channel bandwidths, such as a "wide" channel comprising or formed by any other number of two or more channels, such as an aggregated channel comprising an aggregation of two or more channels. For example, an EDMG STA may be configured to implement one or more channel bonding mechanisms, which may, for example, support increased channel bandwidths, such as a channel BW of 4.32 GHz, a channel BW of 6.48 GHz, a channel BW of 8.64 GHz, and / or any other additional or alternative channel BW. The EDMG STA may perform other additional or alternative functions.

[0035] In other aspects, the mmWave STA may include any other type of STA, and / or may perform other additional or alternative functions. Other aspects may be implemented by any other apparatus, device, and / or station.

[0036] As used herein, the term "antenna" may include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. In some aspects, an antenna may use separate transmit antenna elements and receive antenna elements to implement transmit and receive functions. In some aspects, an antenna may use common and / or integrated transmit / receive elements to implement transmit and receive functions. Antennas may include, for example, phased array antennas, single element antennas, a set of switched beam antennas, and the like.

[0037] Reference Figure 1 , which schematically illustrates a system 100 according to some exemplary aspects.

[0038] like Figure 1As shown, in some demonstrative aspects, system 100 may include one or more wireless communication devices. For example, system 100 may include wireless communication device 102, wireless communication device 140, wireless communication device 150, and / or one or more other devices.

[0039] In some demonstrative aspects, devices 102, 140, and / or 150 may comprise mobile devices or non-mobile devices (eg, stationary devices).

[0040] For example, the devices 102, 140, and / or 150 may include, for example, UE, MD, STA, AP, PC, desktop computer, mobile computer, laptop computer, Ultrabook, etc. TM computer, notebook computer, tablet computer, server computer, handheld computer, Internet of Things (IoT) device, sensor device, handheld device, wearable device, PDA device, handheld PDA device, on-board device, off-board device, hybrid device (e.g., combining cellular phone functionality with PDA device functionality), consumer device, in-vehicle device, off-vehicle device, mobile or portable device, non-mobile or non-portable device, mobile phone, cellular phone, PCS device, PDA device including wireless communication device, mobile or portable GPS device, DVB device, relatively small computing device, non-desktop computer, "travel light, enjoy life" (CSLL) device, ultra mobile device (UMD), ultra mobile PC (UMPC), mobile Internet device (MID), "Origami" device or computing device, device supporting dynamic composable computing (DCC), context-aware device, video device, audio device, A / V device, set-top box (STB), Blu-ray disc (BD) player, BD recorder, digital video disc (DVD) player, high definition (HD) DVD player, DVD recorder, HD DVD recorder, personal video recorder (PVR), broadcast HD receiver, video source, audio source, video sink, audio sink, stereo tuner, broadcast radio receiver, flat panel display, personal media player (PMP), digital video camera (DVC), digital audio player, speaker, audio receiver, audio amplifier, gaming device, data source, data sink, digital still camera (DSC), media player, smart phone, television, music player, etc.

[0041] In some exemplary aspects, device 102 and / or device 150 may include, for example, one or more of processor 191, input unit 192, output unit 193, memory unit 194, and / or storage unit 195; and / or device 140 may include, for example, one or more of processor 181, input unit 182, output unit 183, memory unit 184, and / or storage unit 185. Devices 102, 140, and / or 150 may optionally include other suitable hardware components and / or software components. In some exemplary aspects, some or all of the components of one or more of devices 102, 140, and / or 150 may be housed in a common housing or package and may be interconnected or operably associated using one or more wired or wireless links. In other aspects, the components of one or more of devices 102, 140, and / or 150 may be distributed over multiple or separate devices.

[0042] In some exemplary aspects, processor 191 and / or processor 181 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multi-core processor, a microprocessor, a main processor, a controller, multiple processors or controllers, a chip, a microchip, one or more circuits, circuits, logic units, integrated circuits (ICs), application specific ICs (ASICs), or any other suitable multi-purpose or specific processor or controller. Processor 191 may execute, for example, instructions of an operating system (OS) of device 102 and / or instructions of one or more suitable applications. Processor 181 may execute, for example, instructions of an operating system (OS) of device 140 and / or instructions of one or more suitable applications.

[0043] In some exemplary aspects, input unit 192 and / or input unit 182 may include, for example, a keyboard, a keypad, a mouse, a touch screen, a touch pad, a trackball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 193 and / or output unit 183 may include, for example, a monitor, a screen, a touch screen, a flat panel display, a light emitting diode (LED) display unit, a liquid crystal display (LCD) display unit, a plasma display unit, one or more audio speakers or headphones, or other suitable output devices.

[0044] In some exemplary aspects, memory unit 194 and / or memory unit 184 include, for example, random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffer, short-term memory unit, long-term memory unit, or other suitable memory unit. Storage unit 195 and / or storage unit 185 may include, for example, a hard disk drive, a floppy disk drive, a compact disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage unit. Memory unit 194 and / or storage unit 195, for example, may store data processed by device 102. Memory unit 184 and / or storage unit 185, for example, may store data processed by device 140.

[0045] In some demonstrative aspects, wireless communication devices 102, 140, and / or 150 may be capable of communicating content, data, information, and / or signals via wireless medium (WM) 103. In some demonstrative aspects, wireless medium 103 may include, for example, a radio channel, an RF channel, a WiFi channel, a cellular channel, a 5G channel, an IR channel, a Bluetooth (BT) channel, a Global Navigation Satellite System (GNSS) channel, and / or the like.

[0046] In some demonstrative aspects, WM 103 may include one or more wireless communication bands and / or channels. For example, WM 103 may include a sub-10 GHz wireless communication band, such as one or more channels in a 2.4 GHz wireless communication band, one or more channels in a 5 GHz wireless communication band, and / or one or more channels in a 6 GHz wireless communication band. For example, WM 103 may additionally or alternatively include one or more channels in a mmWave wireless communication band.

[0047] In other aspects, WM 103 may include any other type of channels on any other frequency bands.

[0048] In some demonstrative aspects, device 102, device 140, and / or device 150 may include one or more radio devices including circuitry and / or logic for performing wireless communications between devices 102, 140, 150, and / or one or more other wireless communication devices. For example, device 102 may include one or more radio devices 114, device 150 may include one or more radio devices 173, and / or device 140 may include one or more radio devices 144.

[0049] In some demonstrative aspects, radios 114, 173, and / or 144 may include one or more wireless receivers (Rx), which include circuits and / or logic for receiving wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and / or data. For example, radio 114 may include at least one receiver 116, and / or radio 144 may include at least one receiver 146.

[0050] In some demonstrative aspects, radios 114, 173, and / or 144 may include one or more wireless transmitters (Tx), which include circuits and / or logic for transmitting wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and / or data. For example, radio 114 may include at least one transmitter 118, and / or radio 144 may include at least one transmitter 148.

[0051] In some demonstrative aspects, radio devices 114, 173 and / or 144, transmitters 118 and / or 148, and / or receivers 116 and / or 146 may include: circuits; logic; radio frequency (RF) elements, circuits and / or logic; baseband elements, circuits and / or logic; modulation elements, circuits and / or logic; demodulation elements, circuits and / or logic; amplifiers; analog-to-digital and / or digital-to-analog converters; filters; etc. For example, radio devices 114, 173 and / or 144 may include a wireless network interface card (NIC) or the like, or may be implemented as part thereof.

[0052] In some exemplary aspects, radio devices 114, 173 and / or 144 can be configured to communicate in a sub-10 GHz band (e.g., a 2.4 GHz band, a 5 GHz band, a 6 GHz band, and / or any other sub-10 GHz band), and / or a mmWave band (e.g., a 45 GHz band, a 60 GHz band, and / or any other mmWave band), and / or any other frequency band (e.g., a 5G band, an S1G band, and / or any other frequency band).

[0053] In some demonstrative aspects, radios 114, 173, and / or 144 may include, or may be associated with, one or more (eg, a plurality of) antennas.

[0054] In some demonstrative aspects, device 102 may include one or more (e.g., plural) antennas 107 , device 150 may include one or more (e.g., plural) antennas 177 , and / or device 140 may include one or more (e.g., plural) antennas 147 .

[0055] Antennas 107, 177, and / or 147 may include any type of antenna suitable for sending and / or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages, and / or data. For example, antennas 107, 177, and / or 147 may include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. In some aspects, antennas 107, 177, and / or 147 may use separate transmit antenna elements and receive antenna elements to implement transmit functions and receive functions. In some aspects, antennas 107, 177, and / or 147 may use common and / or integrated transmit / receive elements to implement transmit functions and receive functions.

[0056] In some demonstrative aspects, device 102 may include controller 124 , device 150 may include controller 174 , and / or device 140 may include controller 154 . Controller 124 may be configured to execute and / or trigger, cause, instruct and / or control device 102 to perform one or more communications, generate and / or communicate one or more messages and / or transmissions, and / or perform one or more functions, operations and / or processes between devices 102, 140, 150 and / or one or more other devices; controller 174 may be configured to execute and / or trigger, cause, instruct and / or control device 150 to perform one or more communications, generate and / or communicate one or more messages and / or transmissions, and / or perform one or more functions, operations and / or processes between devices 102, 140, 150 and / or one or more other devices; and / or controller 154 may be configured to execute and / or trigger, cause, instruct and / or control device 140 to perform one or more communications, generate and / or communicate one or more messages and / or transmissions, and / or perform one or more functions, operations and / or processes between devices 102, 140, 150 and / or one or more other devices, for example as described below.

[0057] In some demonstrative aspects, controllers 124, 174, and / or 154 may include, or may be partially or fully implemented by, circuits and / or logic, such as one or more processors including circuits and / or logic, memory circuits and / or logic, medium access control (MAC) circuits and / or logic, physical layer (PHY) circuits and / or logic, baseband (BB) circuits and / or logic, BB processors, BB memories, application processor (AP) circuits and / or logic, AP processors, AP memories, and / or any other circuits and / or logic that are configured to perform the functions of controllers 124, 174, and / or 154, respectively. Additionally or alternatively, one or more functions of controllers 124, 174, and / or 154 may be implemented by logic that may be executed by a machine and / or one or more processors, such as described below.

[0058] In one example, the controller 124 may include circuits and / or logic, such as one or more processors including circuits and / or logic, to cause, trigger, and / or control a wireless device (e.g., device 102) and / or a wireless station (e.g., a wireless STA implemented by the device 102) to perform one or more operations, communications, and / or functions, such as described herein. In one example, the controller 124 may include, for example, at least one memory coupled to one or more processors, which may be configured, for example, to at least temporarily store at least some information processed by one or more processors and / or circuits, and / or may be configured to store logic to be used by the processors and / or circuits.

[0059] In one example, the controller 174 may include circuits and / or logic, such as one or more processors including circuits and / or logic, to cause, trigger, and / or control a wireless device (e.g., device 150) and / or a wireless station (e.g., a wireless STA implemented by device 150) to perform one or more operations, communications, and / or functions, such as described herein. In one example, the controller 174 may include, for example, at least one memory coupled to one or more processors, which may be configured, for example, to at least temporarily store at least some information processed by one or more processors and / or circuits, and / or may be configured to store logic to be used by the processor and / or circuits.

[0060] In one example, the controller 154 may include circuits and / or logic, such as one or more processors including circuits and / or logic, to cause, trigger, and / or control a wireless device (e.g., device 140) and / or a wireless station (e.g., a wireless STA implemented by device 140) to perform one or more operations, communications, and / or functions, such as described herein. In one example, the controller 154 may include, for example, at least one memory coupled to one or more processors, which may be configured, for example, to at least temporarily store at least some information processed by one or more processors and / or circuits, and / or may be configured to store logic to be used by the processor and / or circuits.

[0061] In some exemplary aspects, at least a portion of the functionality of controller 124 may be implemented as part of one or more elements of radio device 114, at least a portion of the functionality of controller 154 may be implemented as part of one or more elements of radio device 144, and / or at least a portion of the functionality of controller 174 may be implemented as part of one or more elements of radio device 173.

[0062] In other aspects, the functionality of controller 124 may be implemented as part of any other element of device 102 , the functionality of controller 174 may be implemented as part of any other element of device 150 , and / or the functionality of controller 154 may be implemented as part of any other element of device 140 .

[0063] In some demonstrative aspects, device 102 may include a message processor 128 configured to generate, process, and / or access one or more messages communicated by device 102 .

[0064] In one example, the message processor 128 may be configured to generate one or more messages to be sent by the device 102, and / or the message processor 128 may be configured to access and / or process one or more messages received by the device 102, e.g., as described below.

[0065] In one example, the message processor 128 may include: at least one first component configured to generate a message, for example, in the form of a frame, a field, an information element, and / or a protocol data unit (e.g., a MAC protocol data unit (MPDU)); at least one second component configured to convert the message into a PHY protocol data unit (PPDU), for example, by processing the message generated by the at least one first component, for example, by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message; and / or at least one third component configured to cause the message to be transmitted on a wireless communication medium (e.g., a wireless communication channel in a wireless communication band), for example, by applying one or more transmission waveforms to one or more fields of the PPDU. In other aspects, the message processor 128 may be configured to perform any other additional or alternative functions, and / or may include any other additional or alternative components to generate and / or process the message to be transmitted.

[0066] In some demonstrative aspects, device 140 may include a message processor 158 configured to generate, process, and / or access one or more messages communicated by device 140 .

[0067] In one example, message processor 158 may be configured to generate one or more messages to be sent by device 140, and / or message processor 158 may be configured to access and / or process one or more messages received by device 140, eg, as described below.

[0068] In one example, the message processor 158 may include: at least one first component configured to generate a message, for example, in the form of a frame, field, cell, and / or protocol data unit (e.g., MPDU); at least one second component configured to convert the message into a PPDU, for example, by processing the message generated by the at least one first component, for example, by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message; and / or at least one third component configured to cause the message to be transmitted on a wireless communication medium (e.g., a wireless communication channel in a wireless communication band), for example, by applying one or more transmit waveforms to one or more fields of the PPDU. In other aspects, the message processor 158 may be configured to perform any other additional or alternative functions, and / or may include any other additional or alternative components to generate and / or process the message to be transmitted.

[0069] In some demonstrative aspects, device 150 may include a message processor 178 configured to generate, process, and / or access one or more messages communicated by device 150 .

[0070] In one example, message processor 178 may be configured to generate one or more messages to be sent by device 150, and / or message processor 178 may be configured to access and / or process one or more messages received by device 150, e.g., as described below.

[0071] In one example, the message processor 178 may include: at least one first component configured to generate a message, for example, in the form of a frame, a field, an information element, and / or a protocol data unit (e.g., a MAC protocol data unit (MPDU)); at least one second component configured to convert the message into a PHY protocol data unit (PPDU), for example, by processing the message generated by the at least one first component, for example, by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message; and / or at least one third component configured to cause the message to be transmitted on a wireless communication medium (e.g., a wireless communication channel in a wireless communication band), for example, by applying one or more transmission waveforms to one or more fields of the PPDU. In other aspects, the message processor 178 may be configured to perform any other additional or alternative functions, and / or may include any other additional or alternative components to generate and / or process the message to be transmitted.

[0072] In some demonstrative aspects, message processors 128, 178, and / or 158 may include, or may be partially or fully implemented by, circuits and / or logic, such as one or more processors including circuits and / or logic, memory circuits and / or logic, MAC circuits and / or logic, PHY circuits and / or logic, BB circuits and / or logic, BB processors, BB memories, AP circuits and / or logic, AP processors, AP memories, and / or any other circuits and / or logic configured to respectively perform the functions of message processors 128, 178, and / or 158. Additionally or alternatively, one or more functions of message processors 128, 178, and / or 158 may be implemented by logic that may be executed by a machine and / or one or more processors, such as described below.

[0073] In some demonstrative aspects, at least a portion of the functionality of message processor 128 may be implemented as part of radio device 114, at least a portion of the functionality of message processor 178 may be implemented as part of radio device 173, and / or at least a portion of the functionality of message processor 158 may be implemented as part of radio device 144.

[0074] In some exemplary aspects, at least a portion of the functionality of message processor 128 may be implemented as part of controller 124, at least a portion of the functionality of message processor 178 may be implemented as part of controller 174, and / or at least a portion of the functionality of message processor 158 may be implemented as part of controller 154.

[0075] In other aspects, the functionality of message processor 128 may be implemented as part of any other element of device 102, the functionality of message processor 178 may be implemented as part of any other element of device 150, and / or the functionality of message processor 158 may be implemented as part of any other element of device 140.

[0076] In some demonstrative aspects, at least a portion of the functionality of the controller 124 and / or the message processor 128 may be implemented by an integrated circuit, e.g., a chip (e.g., a system on a chip (SoC)). In one example, the chip or SoC may be configured to perform one or more functions of the one or more radios 114. For example, the chip or SoC may include one or more elements of the controller 124, one or more elements of the message processor 128, and / or one or more elements of the one or more radios 114. In one example, the controller 124, the message processor 128, and the one or more radios 114 may be implemented as part of a chip or SoC.

[0077] In other aspects, controller 124 , message processor 128 , and / or one or more radios 114 may be implemented by one or more additional or alternative elements of device 102 .

[0078] In some demonstrative aspects, at least a portion of the functionality of the controller 154 and / or the message processor 158 may be implemented by an integrated circuit, such as a chip (e.g., a SoC). In one example, the chip or SoC may be configured to perform one or more functions of the one or more radio devices 144. For example, the chip or SoC may include one or more elements of the controller 154, one or more elements of the message processor 158, and / or one or more elements of the one or more radio devices 144. In one example, the controller 154, the message processor 158, and the one or more radio devices 144 may be implemented as part of a chip or SoC.

[0079] In other aspects, controller 154 , message processor 158 , and / or one or more radios 144 may be implemented by one or more additional or alternative elements of device 140 .

[0080] In some demonstrative aspects, at least a portion of the functionality of the controller 174 and / or the message processor 178 may be implemented by an integrated circuit, such as a chip (e.g., SoC). In one example, the chip or SoC may be configured to perform one or more functions of the one or more radio devices 173. For example, the chip or SoC may include one or more elements of the controller 174, one or more elements of the message processor 178, and / or one or more elements of the one or more radio devices 173. In one example, the controller 174, the message processor 178, and the one or more radio devices 173 may be implemented as part of a chip or SoC.

[0081] In other aspects, controller 174 , message processor 178 , and / or one or more radios 173 may be implemented by one or more additional or alternative elements of device 150 .

[0082] In some demonstrative aspects, device 102, device 150, and / or device 140 may include one or more STAs as part of their operations, perform their roles, and / or perform their one or more functions. For example, device 102 may include at least one STA, device 150 may include at least one STA, and / or device 140 may include at least one STA.

[0083] In some demonstrative aspects, device 102, device 140, and / or device 150 may include one or more extremely high throughput (EHT) STAs as their operation, to perform their roles, and / or to perform one or more functions thereof. For example, device 102 may include one or more EHT STAs as their operation, to perform their roles, and / or to perform one or more functions thereof, device 150 may include one or more EHT STAs as their operation, to perform their roles, and / or to perform one or more functions thereof, and / or device 140 may include one or more EHT STAs as their operation, to perform their roles, and / or to perform one or more functions thereof.

[0084] In some demonstrative aspects, device 102, device 140, and / or device 150 may include one or more mmWave STAs (e.g., DMG STAs, EDMG STAs, and / or any other mmWave STAs) as their operations, perform their roles, and / or perform one or more functions thereof. For example, device 102 may include one or more mmWave STAs as their operations, perform their roles, and / or perform one or more functions thereof, device 150 may include one or more mmWave STAs as their operations, perform their roles, and / or perform one or more functions thereof, and / or device 140 may include one or more mmWave STAs as their operations, perform their roles, and / or perform one or more functions thereof.

[0085] In other aspects, devices 102, 140, and / or 150 may include any other wireless devices and / or stations (eg, WLAN STA, WiFi STA, etc.) as operating, performing, and / or executing one or more functions thereof.

[0086] In some demonstrative aspects, device 102, device 140, and / or device 150 may be configured to operate as, perform a role of, and / or perform one or more functions of, an access point (AP) (eg, an EHT AP STA).

[0087] In some demonstrative aspects, device 102, device 140, and / or device 150 may be configured to operate as a non-AP STA (eg, an EHT non-AP STA), perform a role thereof, and / or perform one or more functions thereof.

[0088] In other aspects, device 102, device 140, and / or device 150 may operate as any other additional or alternative devices and / or stations, perform the roles thereof, and / or perform one or more functions thereof.

[0089] In one example, a station (STA) may include a logical entity that is a single addressable instance of a medium access control (MAC) and physical layer (PHY) interface to a wireless medium (WM). A STA may perform any other additional or alternative functions.

[0090] In one example, an AP may include an entity that includes a station (STA) and provides access to a distribution service for associated STAs via a wireless medium (WM). The AP may include a STA and a distributed system access function (DSAF). The AP may perform any other additional or alternative functions.

[0091] In some demonstrative aspects, devices 102, 140, and / or 150 may be configured to communicate in an EHT network and / or any other network.

[0092] In some demonstrative aspects, devices 102, 140 and / or 150 may be configured to operate in accordance with one or more specifications, including, for example, one or more IEEE 802.11 specifications, such as the IEEE 802.11-2020 specification, the IEEE 802.11be specification, the IEEE 802.11ay specification, and / or any other specifications and / or protocols.

[0093] In some demonstrative aspects, device 102, device 140, and / or device 150 may include one or more multi-link logical entities as part of their operation, perform their roles, and / or perform their functions, e.g., as described below.

[0094] In other aspects, device 102, device 140 and / or device 150 may include, for example, any other entity that is not a multi-link logical entity, as part of its operation, perform its role and / or perform its function.

[0095] For example, a multi-link logical entity may include a logical entity that includes one or more STAs. The logical entity may have a MAC data service interface and primitives to a logical link control (LLC) and a single address associated with the interface that can be used to communicate on a distributed system medium (DSM). For example, the DSM may include a medium or a set of media used by a distributed system (DS) to communicate between an AP, a mesh door, and a portal of an extended service set (ESS). For example, a DS may include a system for interconnecting a set of basic service sets (BSSs) and an integrated local area network (LAN) to create an extended service set (ESS). In one example, a multi-link logical entity may allow STAs within a multi-link logical entity to have the same MAC address. The multi-link entity may perform any other additional or replacement functions.

[0096] In some demonstrative aspects, device 102, device 140, and / or device 150 may include a multi-link device (MLD) as its operation, to perform its role, and / or to perform its function. For example, device 102 may include at least one MLD as its operation, to perform its role, and / or to perform its function, device 150 may include at least one MLD as its operation, to perform its role, and / or to perform its function, and / or device 140 may include at least one MLD as its operation, to perform its role, and / or to perform its function, e.g., as described below.

[0097] For example, the MLD may include, as a logical entity, a device having more than one attached STA and having a single MAC Service Access Point (SAP) to an LLC that includes one MAC data service. The MLD may perform any other additional or alternative functions.

[0098] In some demonstrative aspects, for example, an infrastructure framework may include, for example, a multi-link AP logical entity (including APs) on one side, and, for example, a multi-link non-AP logical entity (including non-APs) on another side.

[0099] In some demonstrative aspects, device 102, device 140, and / or device 150 may be configured to operate as an AP MLD, perform its role, and / or perform one or more functions thereof.

[0100] In some demonstrative aspects, device 102, device 140, and / or device 150 may be configured to operate as a non-APMLD, perform its role, and / or perform one or more functions thereof.

[0101] In other aspects, device 102, device 140, and / or device 150 may operate as any other additional or alternative devices and / or stations, perform their roles, and / or perform one or more functions thereof.

[0102] For example, the AP MLD may include an MLD, wherein each STA affiliated with the MLD is an AP. In one example, the APMLD may include a multi-link logical entity, wherein each STA within the multi-link logical entity is an EHT AP. The AP MLD may perform any other additional or alternative functions.

[0103] For example, the non-AP MLD may include an MLD, wherein each STA belonging to the MLD is a non-AP STA. In one example, the non-AP MLD may include a multi-link logical entity, wherein each STA within the multi-link logical entity is a non-AP EHT STA. The non-AP MLD may perform any other additional or alternative functions.

[0104] In one example, the multi-link infrastructure framework may be configured as an extension from a single-link operation between two STAs (eg, an AP and a non-AP STA).

[0105] In some exemplary aspects, the controller 124 may be configured to control, execute and / or trigger, cause, instruct and / or control the device 102 to operate as an AP MLD 131 (which includes multiple STAs 133, for example, including AP STA 135, AP STA 137, AP STA 139 and / or mmWave STA 141), perform its role and / or perform one or more operations and / or functions thereof. In some aspects, such as Figure 1 As shown, AP MLD 131 may include four STAs. In other aspects, AP MLD 131 may include any other number of STAs.

[0106] In one example, AP STA 135, AP STA 137, AP STA 139, and / or mmWave STA 141 may operate as an EHT AP STA, perform its role, and / or perform one or more operations and / or functions thereof. In other aspects, AP STA 135, AP STA 137, AP STA 139, and / or mmWave STA 141 may perform any other additional or alternative functions.

[0107] In some exemplary aspects, the mmWave STA 141 may operate as a mmWave AP STA, perform its role and / or perform one or more operations and / or functions thereof. In other aspects, the mmWave STA 141 may operate as a mmWave network controller, perform its role and / or perform one or more operations and / or functions thereof to control communications on the mmWave wireless communication network.

[0108] In some demonstrative aspects, for example, the one or more radios 114 may include a radio for communicating by the APSTA 135 on a first wireless communication frequency channel and / or band (eg, a 2.4 GHz band), for example, as described below.

[0109] In some demonstrative aspects, for example, the one or more radios 114 may include a radio for communicating by the APSTA 137 on a second wireless communication frequency channel and / or band (eg, a 5 GHz band), for example, as described below.

[0110] In some demonstrative aspects, for example, the one or more radios 114 may include a radio for communicating by the APSTA 139 on a third wireless communication frequency channel and / or band (eg, a 6 GHz band), for example, as described below.

[0111] In some demonstrative aspects, for example, one or more radio devices 114 may include, for example, a radio device for communicating by the mmWave STA 141 on a fourth wireless communication frequency channel and / or band (e.g., a mmWave band, such as a wireless communication band above 45 GHz (e.g., a 60 GHz band or any other mmWave band)), as described below.

[0112] In some demonstrative aspects, the radio 114 utilized by the STA 133 can be implemented as a separate radio. In other aspects, the radio 114 utilized by the STA 133 can be implemented by one or more shared and / or common radios and / or radio components.

[0113] In other aspects, the controller 124 can be configured to control, execute and / or trigger, cause, instruct and / or control the device 102 to operate as any other additional or alternative entity and / or STA (e.g., a single STA, multiple STAs and / or non-MLD entity), perform its role and / or perform one or more operations and / or functions thereof.

[0114] In some exemplary aspects, the controller 174 may be configured to control, execute and / or trigger, cause, instruct and / or control the device 150 to operate as an AP MLD 179 (which includes multiple STAs, such as AP STA 171), perform its role and / or perform one or more operations and / or functions thereof.

[0115] In one example, one or more APs of AP MLD 179 may operate as an EHT AP STA, perform its role and / or perform one or more operations and / or functions thereof. In other aspects, one or more APs of AP MLD 179 may perform any other additional or alternative functions.

[0116] In other aspects, the controller 174 can be configured to control, execute and / or trigger, cause, instruct and / or control the device 150 to operate as any other additional or alternative entity and / or STA (e.g., a single STA, multiple STAs and / or non-MLD entity), perform its role and / or perform one or more operations and / or functions thereof.

[0117] In some exemplary aspects, the controller 154 may be configured to control, execute and / or trigger, cause, instruct and / or control the device 140 to operate as an MLD 151 (which includes multiple STAs 153, for example, including STA 155, STA 157, STA 159 and / or STA 161), perform its role and / or perform one or more operations and / or functions thereof. In some aspects, such as Figure 1 As shown, MLD 151 may include four STAs. In other aspects, MLD 151 may include any other number of STAs.

[0118] In one example, STA 155, STA 157, STA 159 and / or STA 161 may operate as an EHT STA, perform its role and / or perform one or more operations and / or functions thereof. In other aspects, STA 155, STA 157, STA 159 and / or STA 161 may perform any other additional or alternative functions.

[0119] In some exemplary aspects, STA 161 may be configured to operate as a mmWave STA, perform its role, and / or perform one or more operations and / or functions thereof, e.g., as described below. For example, mmWave STA 161 may be configured to operate as a non-AP mmWave STA, perform its role, and / or perform one or more operations and / or functions thereof, e.g., as described below.

[0120] In some demonstrative aspects, for example, one or more radios 144 may include a radio for communicating by STA 155 on a first wireless communication frequency channel and / or band (eg, a 2.4 GHz band), for example, as described below.

[0121] In some demonstrative aspects, for example, one or more radios 144 may include a radio for communicating by STA 157 on a second wireless communication frequency channel and / or band (eg, a 5 GHz band), for example, as described below.

[0122] In some demonstrative aspects, for example, one or more radios 144 may include a radio for communicating by STA 159 on a third wireless communication frequency channel and / or band (eg, a 6 GHz band), for example, as described below.

[0123] In some demonstrative aspects, for example, one or more radios 144 may include, for example, a radio for communicating by mmWave STA 161 on a fourth wireless communication frequency channel and / or band (eg, a mmWave band), as described below.

[0124] In some demonstrative aspects, the radio 144 utilized by the STA 153 can be implemented as a separate radio. In other aspects, the radio 144 utilized by the STA 153 can be implemented by one or more shared and / or common radios and / or radio components.

[0125] In some exemplary aspects, the controller 154 may be configured to control, execute and / or trigger, cause, instruct and / or control the MLD 151 to operate as a non-AP MLD, perform its role and / or perform one or more operations and / or functions thereof. For example, the STA 155, the STA 157, the STA 159 and / or the mmWave STA 161 may operate as a non-AP STA (e.g., a non-AP EHT STA), perform its role and / or perform one or more operations and / or functions thereof.

[0126] In some exemplary aspects, the controller 154 may be configured to control, execute and / or trigger, cause, instruct and / or control the MLD 151 to operate as an AP MLD, perform its role and / or perform one or more operations and / or functions thereof. For example, the STA 155, the STA 157, the STA 159 and / or the mmWave STA 161 may operate as an AP EHT STA, perform its role and / or perform one or more operations and / or functions thereof.

[0127] In other aspects, the controller 154 can be configured to control, execute and / or trigger, cause, instruct and / or control the device 140 to operate as any other additional or alternative entity and / or STA (e.g., a single STA, multiple STAs and / or non-MLD entity), perform its role and / or perform one or more operations and / or functions thereof.

[0128] Reference Figure 2 , which schematically illustrates a multi-link communication scheme 200 that can be implemented according to some exemplary aspects.

[0129] like Figure 2 As shown, the first multi-link logical entity 202 ("multi-link logical entity 1"), for example, the first MLD, may include multiple STAs, for example, including STA 212, STA 214, STA 216, and STA 218. In one example, AP MLD 131 ( Figure 1 ) may perform one or more operations, one or more functions, roles, and / or functions of the multi-link logic entity 202. In another example, the AP MLD 179 ( Figure 1 ) can perform one or more operations, one or more functions, roles and / or functions of the multi-link logical entity 202.

[0130] like Figure 2As shown, the second multi-link logical entity 240 ("multi-link logical entity 2"), for example, a second MLD, may include multiple STAs, for example, STA 252, STA 254, STA 256, and STA 258. In one example, MLD 151 ( Figure 1 ) can perform one or more operations, one or more functions, roles and / or functions of the multi-link logical entity 240.

[0131] like Figure 2 As shown, the multi-link logical entity 202 and the multi-link logical entity 240 can be configured to form multiple links, establish multiple links and / or communicate on multiple links, such as link 272 between STA 212 and STA 252, link 274 between STA 214 and STA 254, link 276 between STA216 and STA256, and / or link 278 between STA218 and STA258.

[0132] Reference Figure 3 , which schematically illustrates a multi-link communication scheme 300 that can be implemented according to some exemplary aspects.

[0133] like Figure 3 As shown, the multi-link AP logical entity 302, such as AP MLD, may include multiple AP STAs, such as AP STA 312, AP STA 314, AP STA 316, and mmWave STA 318. In one example, AP MLD 131 ( Figure 1 ) may perform one or more operations, one or more functions, roles, and / or functions of the multi-link AP logical entity 302. In another example, the AP MLD 179 ( Figure 1 ) can perform one or more operations, one or more functions, roles and / or functions of the multi-link AP logical entity 302.

[0134] like Figure 3 As shown, the multi-link non-AP logical entity 340, such as the non-AP MLD, may include multiple non-AP STAs, such as non-AP STA 352, non-AP STA 354, non-AP STA 356, and mmWave STA 358. In one example, MLD 151 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of the multi-link non-AP logical entity 340.

[0135] like Figure 3As shown, the multi-link AP logical entity 302 and the multi-link non-AP logical entity 340 can be configured to form multiple links, establish multiple links and / or communicate on multiple links, for example, including a link 372 between an AP STA 312 and a non-AP STA 352, a link 374 between an AP STA 314 and a non-AP STA 354, a link 376 between an AP STA 316 and a non-AP STA 356, and / or a link 378 between an mmWave STA 318 and an mmWave STA 358.

[0136] For example, Figure 3 As shown, the multi-link AP logical entity 302 may include a multi-band AP MLD, and the multi-band AP MLD may be configured to communicate on multiple wireless communication bands. Figure 3 As shown, AP STA312 can be configured to communicate on the 2.4 GHz band, AP STA314 can be configured to communicate on the 5 GHz band, AP STA 316 can be configured to communicate on the 6 GHz band, and / or mmWave STA318 can be configured to communicate on the mmWave band. In other aspects, AP STA312, AP STA314, AP STA316, and / or mmWave STA 318 can be configured to communicate on any other additional or alternative wireless communication bands.

[0137] Return to reference Figure 1 In some exemplary aspects, devices 102, 140 and / or 150 may be configured to: perform one or more operations of a fast basic service set (BSS) transition (FT) (e.g., allowing a station (e.g., a FT originator (FTO) STA) to move from a first AP STA (also referred to as a “current AP” or “source AP”) to a second AP STA (also referred to as a “target AP”), e.g., as described below).

[0138] In one example, device 140 may be configured to include an FTO, operate as an FTO, perform the role of an FTO, and / or perform the functions of an FTO, device 102 may be configured to include a source AP, operate as a source AP, perform the role of a source AP, and / or perform the functions of a source AP, and / or device 150 may be configured to include a target AP, operate as a target AP, perform the role of a target AP, and / or perform the functions of a target AP, for example, as described below.

[0139] In some demonstrative aspects, FT may allow, for example, reducing the time during which connectivity is lost between a STA and a distribution system (DS) during a BSS transition.

[0140] In some demonstrative aspects, one or more FT protocols may be applied, for example, to STA transitions between APs within the same mobility domain, such as within the same extended service set (ESS).

[0141] In one example, the FT protocol can support, for example, STA mobility from one BSS in an ESS to another BSS within the ESS (e.g., a change of association made by a STA from one BSS in an ESS to another BSS in the same ESS). According to this example, FT can minimize the amount of time that a data connection is lost between a STA and a DS.

[0142] In some exemplary aspects, the DS may include, for example, a system for interconnecting a set of BSSs and an integrated local area network (LAN) to create an ESS. In other aspects, the DS may include any other additional or alternative elements.

[0143] In some demonstrative aspects, a FTO may move from its current AP to a target AP, eg, utilizing one or more FT protocols, eg, by performing one or more message exchanges according to an "over-the-DS" mechanism.

[0144] For example, according to the over-the-DS mechanism, the FTO may communicate with the target AP via the current AP. For example, the communication between the FTO and the target AP may be performed in FT action frames, and the FT action frames may be passed between the FTO and the current AP. For example, the communication between the current AP and the target AP may be via encapsulation of FT action frames (e.g., using remote request or remote response frames). The over-the-DS mechanism may utilize any additional or alternative messages, frames, and / or mechanisms.

[0145] In some demonstrative aspects, one or more FT protocols may include, for example, a FT resource request protocol that may allow, for example, a FTO to request resources, such as prior to reassociation.

[0146] In some exemplary aspects, device 102, device 140 and / or device 150 may be configured to support a technical solution for wireless roaming of a STA (e.g., a STA implemented by device 140) between APs (e.g., between a first AP (e.g., an AP implemented by device 102) and a second AP (e.g., an AP implemented by device 150)).

[0147] In some exemplary aspects, device 102, device 140 and / or device 150 may be configured to support technical solutions for wireless roaming for time-sensitive networking (TSN) and / or real-time applications (RTA) that may require high reliability with low bounds on latency and / or jitter.

[0148] For example, due to the random nature of wireless channels, it may be challenging to support TSN and / or RTA via wireless communications.

[0149] For example, supporting TSN and / or RTA via wireless communications of mobile devices may be even more challenging, for example, because wireless channels may change over time.

[0150] For example, a process for wireless (e.g., WiFi) roaming within a wireless communication network (e.g., ESS) may include multiple stages that may be implementation specific (e.g., periodic channel scanning, decisions about when to roam and which AP to roam to, FT processes, and / or packet forwarding from a source AP to a target AP). Thus, for example, there may be some packet loss and / or delay due to a rerouting process for routing a STA from a source AP to a target AP.

[0151] For example, during a roaming process for wireless roaming of a STA between a source AP and a target AP, for example, from the beginning of the roaming process until the time when the STA associates with the target AP, a routing table may be updated in the DS between the source AP and the destination AP. However, there may be a disconnection period between the STA and the DS, which may result in delays (e.g., even large delays) and / or packet losses. Such resulting delays and / or packet losses may be unacceptable in some implementations (e.g., for ultra-reliability and ultra-low latency applications).

[0152] In some exemplary aspects, the device 102, the device 140, and / or the device 150 may be configured to implement a multi-band operation mechanism, which may be configured, for example, according to a general framework that may capture one or more use cases regarding multi-band operation (e.g., including: STA seamless and / or lossless transition between links / bands, STA operation on multiple links / bands with different traffic identifiers (TIDs) on different links / bands, and / or STA operation on multiple links / bands with aggregation of the same TID for multi-band operation). For example, in implementations where the STA is a single radio device or a multi-radio device, and / or in implementations where the APs have the same or different MAC addresses, and / or the APs are collocated or not collocated, for example, the multi-band operation mechanism may be implemented to support these use cases.

[0153] In some demonstrative aspects, device 102, device 140, and / or device 150 may be configured to implement a FT mechanism for MLD operations, eg, as described below.

[0154] In some exemplary aspects, it may be desirable to provide technical solutions to address one or more issues of FT for MLD.

[0155] For example, a multi-link association may be performed through a single link between the STA MLD and the AP MLS, and / or the STA MLD may be connected to multiple links of the current AP MLD. For example, the MLD STA may follow the FT protocol to roam from the current AP MLD to the target AP MLD. However, for example, once the STA MLD completes the FT protocol with the target AP MLD through one of the links, the STA MLD may be disconnected from the current AP MLD through all links. Therefore, for example, during the roaming period, for example, similar to the single link case, the STA MLD may face technical problems of packet loss and / or delay.

[0156] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, which may be configured to provide a technical solution to support a "zero roaming effect" capability regarding STA mobility, for example, by leveraging multi-AP coordination capabilities, such as described below.

[0157] In some exemplary aspects, for example, in some use cases, implementations, and / or scenarios, there may be one or more disadvantages and / or inefficiencies in implementing a layer 3 dual connectivity mechanism to support FT. For example, the layer 3 dual connectivity mechanism may utilize a virtual NIC mechanism, where a STA may have separate links to a DS, for example, with different MAC addresses. For example, the integration of these multiple links may be performed in a higher layer. However, for example, in terms of traffic scheduling and / or traffic steering, for example, using a higher layer for multiple link integration may be inefficient compared to layer 2 multiple links.

[0158] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, which may be configured to provide a technical solution to support "transient roaming" capability for STA mobility, for example by relying on on-relay-tunneling, as described below.

[0159] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, and the FT mechanism for MLD operation may be configured to: provide a technical solution to support STA MLD (also known as "non-AP MLD") to establish an association with a target AP MLD, for example, through a current AP MLD, as described below.

[0160] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, and the FT mechanism for MLD operation may be configured to: provide a technical solution to support the current AP to forward the association (reassociation) request management frame that may be received from the STA MLD to the target AP MLD, for example as described below.

[0161] In some demonstrative aspects, the current AP may be configured to forward an association (reassociation) request management frame to a target AP MLD (eg, to the target AP MLD over an association link).

[0162] In other aspects, the current AP may be configured to forward the (re)association request management frame to the target AP MLD via any other link or connection (eg, over another link, an air control plane, and / or an Ethernet cable through a backhaul connection).

[0163] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, which may be configured to: support the current AP to provide a copy of the data frame for the STA MLD to the target AP MLD, such as described below.

[0164] In some demonstrative aspects, the current AP may provide a copy of the data frame for the STA MLD to the target AP MLD at a later stage, such as in conjunction with association management or such as based on when the STA MLD decides to switch to the target AP MLD.

[0165] In some demonstrative aspects, the FT mechanism for MLD operation may be configured to support a STA MLD to switch association with a target AP MLD, eg, substantially instantaneously, such as described below.

[0166] In some exemplary aspects, the FT mechanism for MLD operation may be configured to provide a technical solution to avoid packet loss and / or additional delays regarding packets that may still be stored at the current AP, for example, after a STA MLD has switched to a target AP MLD, such as described below.

[0167] In some demonstrative aspects, device 102, device 140 and / or device 150 may be configured to implement an FT mechanism for MLD operation, which may be configured to provide a technical solution to support coordination between multi-connected APs, such as during a FT process, such as described below.

[0168] In some exemplary aspects, device 102, device 140 and / or device 150 may be configured to implement a FT mechanism for MLD operations, which may be configured to: provide a technical solution to support ultra-reliable time-sensitive applications with flexibility and / or mobility, for example, for many time-critical industrial systems (e.g., including mobile robotic systems, automated guided vehicle (AGV) systems, controllers, etc.).

[0169] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (eg, STA 155) implemented by device 140 to send an FT request to a target AP via a current AP associated with the STA, e.g., as described below.

[0170] In some exemplary aspects, the FT request may be configured to request FT from a current AP to a target AP. For example, the current AP may include an AP implemented by device 102, and / or the target AP may include an AP implemented by device 150, e.g., as described below. In other aspects, the current AP may include an AP implemented by device 150 and / or any other AP, and / or the target AP may include an AP implemented by device 102 and / or any other AP.

[0171] In some demonstrative aspects, the FT may include an FT between the current AP and the target AP through the DS, e.g., as described below. In other aspects, the FT may include any other type of FT.

[0172] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (e.g., STA 155) implemented by device 140 to: process an FT response from a target AP, e.g., after an FT request, e.g., as described below.

[0173] In some demonstrative aspects, the FT response may be received by the STA via the current AP, e.g., as described below.

[0174] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by device 140 to send a reassociation request to a target AP via a current AP, e.g., after a FT response, e.g., as described below.

[0175] In some demonstrative aspects, the reassociation request may be configured to request an association between the STA and the target AP, eg, as described below.

[0176] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (e.g., STA 155) implemented by device 140 to: process a reassociation response from a target AP, e.g., after a reassociation request, e.g., as described below.

[0177] In some demonstrative aspects, the reassociation response may be received by the STA via the current AP, eg, as described below.

[0178] In some demonstrative aspects, the reassociation request and / or the reassociation response may include a tunnel message between the STA and the target AP via the current AP according to a tunnel protocol, e.g., as described below.

[0179] In other aspects, the reassociation request and / or the reassociation response may be configured and / or communicated as any other type of message.

[0180] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to: switch the STA from a current AP to a target AP, for example, for communication via an association session between the STA and the target AP, such as described below.

[0181] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by device 140 to process one or more buffered data packets received from a target AP via an association session between the STA and the target AP, e.g., as described below.

[0182] In some demonstrative aspects, the buffered data packets received from the target AP may include, for example, data buffered by the current AP before the STA switches from the current AP to the target AP, e.g., as described below.

[0183] In some demonstrative aspects, the controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to send a message to a current AP including an indication of criteria for sending buffered data packets (e.g., which include buffered data for the STA) to a target AP, such as described below.

[0184] In some demonstrative aspects, the criteria may include an amount of buffered data packets to be sent to the target AP, eg, as described below.

[0185] In other aspects, any other criteria and / or parameters may be implemented for configuring the current AP to send the STA's buffered data packets to the target AP.

[0186] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (eg, STA 155) implemented by device 140 to trigger transmission of a reassociation request to a target AP based on at least one criterion, e.g., as described below.

[0187] In some exemplary aspects, the controller 154 can be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to: for example, based on the channel conditions of the wireless communication channel between the STA and the current AP, trigger the transmission of a reassociation request to the target AP, such as described below.

[0188] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (eg, STA 155) implemented by device 140 to trigger transmission of a reassociation request to a target AP based on any other additional or alternative criteria and / or parameters.

[0189] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (e.g., STA 155) implemented by device 140 to send an AP handoff request to a target AP, e.g., after a reassociation response, e.g., as described below.

[0190] In some demonstrative aspects, the AP switching request may be configured to request that the STA be switched to a target AP for communication via an association session between the STA and the target AP, e.g., as described below.

[0191] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and / or instruct a STA (eg, STA 155) implemented by device 140 to process an AP handoff response from a target AP, eg, as described below.

[0192] In some demonstrative aspects, the AP switch response may be configured to acknowledge a request to switch the STA to the target AP for communication via an association session between the STA and the target AP, e.g., as described below.

[0193] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by device 140 to: identify that the current AP supports the ability to communicate reassociation requests and reassociation responses with the target AP, such as described below.

[0194] In some exemplary aspects, the controller 154 can be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to: for example, based on a capability indication in a message from the current AP, identify that the current AP supports the ability to communicate a reassociation request and a reassociation response with a target AP, such as described below.

[0195] In some demonstrative aspects, the message indicating that the current AP supports the ability to communicate reassociation requests and reassociation responses with the target AP may include, for example, a beacon from the current AP, as described below.

[0196] In some demonstrative aspects, a message indicating that the current AP supports the ability to communicate reassociation requests and reassociation responses with a target AP may include, for example, an association frame received from the current AP during association with the current AP, e.g., as described below.

[0197] In other aspects, any other additional or alternative types of messages may be utilized to indicate that the current AP supports the ability to communicate reassociation requests and reassociation responses with the target AP.

[0198] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to: identify a capability indication in a neighbor report element from a current AP, and the target AP supports the ability to transmit a reassociation request and a reassociation response via the current AP, such as described below.

[0199] In some exemplary aspects, the controller 154 can be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to: for example, based on a capability indication in a neighbor report element from the current AP, identify the ability of the target AP to support the transmission of reassociation requests and reassociation responses via the current AP, as described below.

[0200] In other aspects, any other additional or alternative types of messages may be utilized to indicate that the target AP supports the ability to communicate reassociation requests and reassociation responses via the current AP.

[0201] In some exemplary aspects, the controller 154 may be configured to control, trigger, cause and / or instruct a STA (e.g., STA 155) implemented by the device 140 to, for example, communicate an agreement establishment message with a target AP via a current AP before the STA switches from a current AP to a target AP, for example, as described below.

[0202] In some demonstrative aspects, the agreement establishment message may be configured to establish an agreement for communicating via an association session between the STA and the target AP, eg, as described below.

[0203] In some demonstrative aspects, the agreement establishment message may include an Add Block Acknowledge (ADDBA) message to establish an ADDBA agreement, e.g., as described below.

[0204] In some demonstrative aspects, the agreement establishment message may include a target wake time (TWT) message to establish a TWT agreement, such as described below.

[0205] In other aspects, the agreement establishment message may include any other additional or alternative types of messages to establish any other additional or alternative agreements.

[0206] In some exemplary aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 (e.g., AP 135) to: act as a current AP for FT. For example, FT may be performed to switch a STA implemented by device 140 from a current AP implemented by device 102 to a target AP implemented by device 150, e.g., as described below.

[0207] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to communicate FT requests between STAs associated with a current AP and a target AP via the current AP, e.g., as described below.

[0208] In some demonstrative aspects, an FT request may be communicated from a STA (eg, a STA implemented by device 140) to a target AP (eg, an AP implemented by device 150).

[0209] In some demonstrative aspects, the FT request may be configured to request FT of a STA (eg, a STA implemented by device 140) from a current AP (eg, an AP implemented by device 102) to a target AP (eg, an AP implemented by device 150).

[0210] In some demonstrative aspects, the FT may include an FT between the current AP and the target AP through the DS, e.g., as described below. In other aspects, the FT may include any other type of FT.

[0211] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to communicate an FT response between a target AP and a STA via a current AP, e.g., following an FT request, e.g., as described below.

[0212] In some demonstrative aspects, an FT response may be communicated from a target AP (eg, an AP implemented by device 150) to a STA (eg, a STA implemented by device 140).

[0213] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to communicate a reassociation request between a STA and a target AP via a current AP, e.g., after a FT response, e.g., as described below.

[0214] In some demonstrative aspects, a reassociation request may be communicated from a STA (eg, a STA implemented by device 140) to a target AP (eg, an AP implemented by device 150).

[0215] In some demonstrative aspects, the reassociation request may be configured to request an association between the STA and the target AP, eg, as described below.

[0216] In some demonstrative aspects, the controller 124 may be configured to control, trigger, cause and / or instruct an AP (e.g., AP 135) implemented by the device 102 to communicate a reassociation response between a target AP and a STA via a current AP, e.g., following a reassociation request, e.g., as described below.

[0217] In some demonstrative aspects, a reassociation response may be communicated from a target AP (eg, an AP implemented by device 150) to a STA (eg, a STA implemented by device 140).

[0218] In some demonstrative aspects, the reassociation request and / or the reassociation response may include a tunnel message between the STA and the target AP via the current AP according to a tunnel protocol, e.g., as described below.

[0219] In other aspects, the reassociation request and / or the reassociation response may be configured and / or communicated as any other type of message.

[0220] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (eg, AP 135) implemented by device 102 to send one or more buffered data packets to a target AP, eg, as described below.

[0221] In some demonstrative aspects, the buffered data packets may include data for a STA (eg, a STA implemented by device 140), which may be buffered by a current AP, for example, before the STA switches from the current AP to a target AP, e.g., as described below.

[0222] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to identify criteria for sending buffered data packets to a target AP based on a message from a STA, e.g., as described below.

[0223] In some demonstrative aspects, the criteria may include an amount of buffered data packets to be sent to the target AP, e.g., as described below. In other aspects, the current AP may implement any other additional or alternative criteria and / or parameters to send buffered data packets to the target AP.

[0224] In some exemplary aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to: send a capability indication in a message from a current AP, for example, to indicate that the current AP supports the ability to communicate a reassociation request and a reassociation response with a target AP, for example, as described below.

[0225] In some exemplary aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to: send a beacon from a current AP to indicate that the current AP supports the ability to communicate a reassociation request and a reassociation response with a target AP, e.g., as described below.

[0226] In some exemplary aspects, the controller 124 can be configured to control, trigger, cause and / or instruct an AP (e.g., AP 135) implemented by the device 102 to: for example, send an association frame to the STA during association with the STA, for example, to indicate that the current AP supports the ability to communicate a reassociation request and a reassociation response with a target AP, such as described below.

[0227] In other aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 102 (e.g., AP 135) to send any other type of message including an indication that the current AP supports the ability to communicate reassociation requests and reassociation responses with a target AP.

[0228] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to send a message including an indication that the target AP supports the ability to communicate reassociation requests and reassociation responses via a current AP, e.g., as described below.

[0229] In some exemplary aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to send a neighbor report element corresponding to a target AP. For example, the neighbor report element may include an indication that the target AP supports responding to a reassociation request and a capability to reassociate via a current AP, e.g., as described below.

[0230] In other aspects, controller 124 may be configured to control, trigger, cause, and / or instruct an AP (e.g., AP 135) implemented by device 102 to send any other type of message including an indication of the target AP's ability to support communicating reassociation requests and reassociation responses via the current AP.

[0231] In some exemplary aspects, the controller 124 can be configured to control, trigger, cause and / or instruct an AP (e.g., AP 135) implemented by the device 102: for example, before the STA switches from the current AP to the target AP, an agreement establishment message is transmitted between the STA and the target AP via the current AP, such as described below.

[0232] In some demonstrative aspects, the agreement establishment message may be configured to establish an agreement for communicating via an association session between the STA and the target AP, eg, as described below.

[0233] In some demonstrative aspects, the agreement establishment message may include an ADDBA message to establish an ADDBA agreement, eg, as described below.

[0234] In some demonstrative aspects, the agreement establishment message may include a TWT message to establish a TWT agreement, such as described below.

[0235] In other aspects, the agreement establishment message may include any other additional or alternative types of messages to establish any other additional or alternative agreements.

[0236] In some exemplary aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 150 (e.g., AP 171) to act as a target AP for FT. For example, FT may be performed to switch a STA implemented by device 140 from a current AP implemented by device 102 to a target AP implemented by device 150, e.g., as described below.

[0237] In some demonstrative aspects, the FT may include an FT between the current AP and the target AP through the DS, e.g., as described below. In other aspects, the FT may include any other type of FT.

[0238] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 150 (e.g., AP 171) to process an FT request from a STA (e.g., a STA implemented by device 140) associated with a current AP (e.g., an AP implemented by device 102).

[0239] In some demonstrative aspects, the FT request may be received from a STA (eg, a STA implemented by device 102) via a current AP (eg, an AP implemented by device 140).

[0240] In some demonstrative aspects, the FT request may be configured to request FT from a current AP (eg, an AP implemented by device 102 ) to an AP implemented by device 150 .

[0241] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP (eg, AP 171) implemented by device 150 to send an FT response to a STA via a current AP, eg, following an FT request, eg, as described below.

[0242] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP (eg, AP 171 ) implemented by device 150 to process a reassociation request from a STA, eg, as described below.

[0243] In some demonstrative aspects, a reassociation request may be received from a STA (e.g., a STA implemented by device 140) via a current AP (e.g., an AP implemented by device 102), e.g., after a FT response, e.g., as described below.

[0244] In some demonstrative aspects, the reassociation request may be configured to request an association between a STA (eg, a STA implemented by device 140) and a target AP (eg, an AP implemented by device 150).

[0245] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause and / or instruct an AP (e.g., AP 171) implemented by device 150 to send a reassociation response to a STA via a current AP, e.g., after a reassociation request, e.g., as described below.

[0246] In some demonstrative aspects, the reassociation request and / or the reassociation response may include a tunnel message between the STA and the target AP via the current AP according to a tunnel protocol, e.g., as described below.

[0247] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP (eg, AP 171) implemented by device 150 to communicate with a STA via an association session between the STA and a target AP, eg, as described below.

[0248] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP (eg, AP 171) implemented by device 150 to process one or more buffered data packets received from a current AP, eg, as described below.

[0249] In some demonstrative aspects, buffered data packets may include, for example, data packets buffered by a current AP (eg, an AP implemented by device 102) before a STA switches from the current AP to a target AP, e.g., as described below.

[0250] In some demonstrative aspects, controller 174 may be configured to control, trigger, cause and / or instruct an AP (e.g., AP 171) implemented by device 150 to send buffered data packets to a STA, e.g., via an association session between the STA and a target AP implemented by device 150, e.g., as described below.

[0251] In some exemplary aspects, controller 174 may be configured to control, trigger, cause, and / or instruct an AP implemented by device 150 (e.g., AP 171) to: process an AP switching request from a STA. For example, after a reassociation response is sent from a target AP implemented by device 150 to a STA implemented by device 140 via a current AP implemented by device 102, a switching request from the STA may be received at the target AP, e.g., as described below.

[0252] In some demonstrative aspects, the AP switching request may be configured to request that the STA be switched to a target AP for communication via an association session between the STA and the target AP, e.g., as described below.

[0253] In some exemplary aspects, the controller 174 may be configured to control, trigger, cause and / or instruct an AP implemented by the device 150 (e.g., AP 171) to: send an AP switching response to a STA, for example, to confirm a request to switch the STA to a target AP for communication via an association session between the STA and the target AP, for example, as described below.

[0254] In some exemplary aspects, the controller 174 can be configured to control, trigger, cause and / or instruct an AP (e.g., AP 171) implemented by the device 150: for example, before the STA switches from the current AP to the target AP implemented by the device 150, an agreement establishment message is transmitted via the current AP with the STA, for example, as described below.

[0255] In some demonstrative aspects, the agreement establishment message may be configured to establish an agreement for communicating via an association session between a STA and a target AP implemented by device 150, eg, as described below.

[0256] In some demonstrative aspects, the agreement establishment message may include an ADDBA message to establish an ADDBA agreement, eg, as described below.

[0257] In some demonstrative aspects, the agreement establishment message may include a TWT message to establish a TWT agreement, such as described below.

[0258] In other aspects, the agreement establishment message may include any other additional or alternative types of messages to establish any other additional or alternative agreements.

[0259] Reference Figure 4 , Figure 4 An MLD FT scheme that can be implemented according to some exemplary aspects is schematically illustrated.

[0260] In some exemplary aspects, such as Figure 4 As shown, for example, when STA 440 is at a first position (position A), STA 440 (eg, STA MLD) may be associated with current AP MLD 402. In one example, device 140 ( Figure 1 ) may perform one or more operations, one or more functions, roles, and / or functions of STA 440. In one example, device 102 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of AP MLD 402.

[0261] In some exemplary aspects, such as Figure 4 As shown, STA 440 may have a multi-link connection 421 with current AP MLD 402 (eg, including three links with three corresponding APs of AP MLD 402).

[0262] In some exemplary aspects, such as Figure 4 As shown, STA 440 may move away from AP MLD 402, for example, toward a second location (Location B).

[0263] In some exemplary aspects, such as Figure 4 As shown, STA 440 may execute FT protocol 411 to switch STA 440 from current AP MLD 402 to target AP MLD 450. In one example, device 150 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of AP MLD 450.

[0264] In some demonstrative aspects, FT protocol 411 may include FT between current AP MLD 402 and target AP MLD 450 over DS 490 .

[0265] In some exemplary aspects, such as Figure 4 As shown, for example, when the STA 440 is at the third position (position C), the STA 440 may switch from the current AP MLD 402 to the target AP MLD 450 for communication via an association session between the STA 440 and the target AP MLD 450 .

[0266] In some exemplary aspects, such as Figure 4 As shown, STA 440 may have a multi-link connection 419 with current AP MLD 450 (eg, including three links with three respective APs of AP MLD 450).

[0267] Reference Figure 5 , Figure 5 FT utilizing a backhaul connection according to some exemplary aspects is schematically illustrated.

[0268] In some exemplary aspects, such as Figure 5 As shown, for example, when STA 540 is at a first location, STA 540 (eg, STA MLD) may be associated with current AP MLD 502. In one example, device 140 ( Figure 1 ) can perform one or more operations, one or more functions, roles and / or functions of STA540. In one example, device 102 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of AP MLD 502.

[0269] In some exemplary aspects, such as Figure 5 As shown, STA 540 may have a multi-link connection with target AP MLD 402 (eg, including a first link between a 2.4 GHz STA of STA 540 and a 2.4 GHz AP of AP MLD 502 and a second link between a 5 GHz STA of STA 540 and a 5 GHz AP of AP MLD 502).

[0270] In some exemplary aspects, such as Figure 5 As shown, STA 540 may move away from AP MLD 502 , for example, toward target AP MLD 550 .

[0271] In some exemplary aspects, such as Figure 5 As shown, STA 540 may perform the FT protocol to switch STA 540 from the current AP MLD 502 to the target AP MLD 550. In one example, device 150 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of the AP MLD 550.

[0272] In some demonstrative aspects, the FT protocol may include FT between the current AP MLD 502 and the target AP MLD 550 over the DS.

[0273] In some demonstrative aspects, STA 540, current AP MLD 502, and / or target AP MLD 550 may be configured to support a FT protocol configured to support establishing an association between STA 540 and target AP MLD 550, e.g., via current AP MLD 502, e.g., as described below.

[0274] In some demonstrative aspects, the FT protocol may be configured to provide a technical solution to support a "zero roaming effect" with respect to STA mobility, such as described below.

[0275] In some demonstrative aspects, STA 540 may be configured to establish an association with target AP MLD 550 , eg, through current AP MLD 502 , eg, through backhaul connection 590 between current AP MLD 502 and target AP MLD 550 .

[0276] In some exemplary aspects, such as Figure 5 As shown, the STA MLD 540 may be configured to send a reassociation management frame to the current AP MLD 502 , for example, via any available connection link between the STA 540 and the current AP MLD 502 .

[0277] In some exemplary aspects, such as Figure 5 As shown, the current AP MLD 502 may forward the reassociation frame received from the STA 540 to the target AP MLD 550 , for example, via the backhaul connection 590 .

[0278] In some exemplary aspects, the FT protocol may be defined, for example, as an enhanced FT protocol over DS, for example, wherein the final reassociation request / response frame may be simplified.

[0279] In some demonstrative aspects, the FT protocol may be defined, for example, as a new tunneling mechanism that may tunnel communications between a STA 540 and a target AP MLD 550 using the current AP MLD 502 .

[0280] In some exemplary aspects, such as Figure 5 As shown, the STA 540 may switch from the current AP MLD 502 to the target AP MLD 550 for communication via an association session between the STA 540 and the target AP MLD 550.

[0281] In some exemplary aspects, such as Figure 5 As shown, STA 540 may have a multi-link connection with the current AP MLD 550 (eg, including a first link between a 2.4 GHz STA of STA 540 and a 2.4 GHz AP of AP MLD 550 and a second link between a 5 GHz STA of STA 540 and a 5 GHz AP of AP MLD 550).

[0282] In some exemplary aspects, such as Figure 5 As shown, the current AP MLD 502 may be configured to provide a copy of the buffered data packets for the STA MLD 502 to the target AP MLD 550. For example, configuring the current AP MLD 502 to provide the buffered data packets to the target AP MLD 550 may provide a technical solution to support avoiding packet loss and / or additional delay that may be caused by FT to the target AP MLD 550.

[0283] In some demonstrative aspects, for example, once STA MLD 540 switches to target AP MLD 550 and there is still data left in current AP MLD 502, STA MLD 540 may still be able to receive the data from target AP MLD 550, for example, with low latency.

[0284] In some demonstrative aspects, STA 540, current AP MLD 502, and / or target AP MLD 550 may be configured to support a reassociation trigger mechanism to trigger a reassociation management exchange of reassociation requests and reassociation responses between STA 540 and target AP MLD 550, e.g., as described below.

[0285] In some demonstrative aspects, the STA 540 , the current AP MLD 502 , and / or the target AP MLD 550 may be configured to support a STA-centric trigger mechanism to trigger a reassociation management exchange of a reassociation request and a reassociation response between the STA 540 and the target AP MLD 550 .

[0286] In some demonstrative aspects, STA 540 may be configured to trigger a reassociation management exchange based on one or more criteria.

[0287] In some demonstrative aspects, STA 540 may be configured to trigger a reassociation management exchange, for example based on channel conditions (e.g., channel conditions of a wireless communication channel between STA 540 and current AP MLD 502 and / or channel conditions of a wireless communication channel between STA 540 and target AP MLD 550).

[0288] In other aspects, the STA 540 may be configured to trigger a reassociation management exchange based on any other additional or alternative criteria and / or parameters.

[0289] In some demonstrative aspects, the STA 540 , the current AP MLD 502 , and / or the target AP MLD 550 may be configured to support a network-centric trigger mechanism to trigger a reassociation management exchange of a reassociation request and a reassociation response between the STA 540 and the target AP MLD 550 .

[0290] In some demonstrative aspects, current AP MLD 502 may be configured to trigger a reassociation management exchange based on one or more criteria.

[0291] In some demonstrative aspects, a reassociation management exchange may be triggered, for example, by a central controller or a network controller based on one or more criteria.

[0292] In some demonstrative aspects, a reassociation management exchange may be triggered, for example, based on the location of the STA.

[0293] In some demonstrative aspects, the reassociation management exchange may be triggered, for example, based on channel conditions at the current AP MLD 502 .

[0294] In some demonstrative aspects, the reassociation management exchange may be triggered, for example, based on channel conditions at the target AP MLD 550 .

[0295] In some demonstrative aspects, the reassociation management exchange may be triggered, for example, based on the traffic load at the current AP MLD 502 .

[0296] In some demonstrative aspects, the reassociation management exchange may be triggered, for example, based on traffic load at the target AP MLD 550 .

[0297] In other aspects, the reassociation management exchange may be triggered based on any other additional or alternative criteria and / or parameters corresponding to the STA 540 , the current AP MLD 502 , and / or the target AP MLD 550 .

[0298] In some demonstrative aspects, the STA 540, the current AP MLD 502, and / or the target AP MLD 550 may be configured to support an AP switching trigger mechanism to trigger a switch of the STA 540 from the current AP MLD 502 to the target AP MLD 550, eg, as described below.

[0299] In some demonstrative aspects, STA 540 may be configured to decide to switch from current AP MLD 502 to target AP MLD 550 .

[0300] In some exemplary aspects, STA 540 can be configured to decide to switch from the current AP MLD 502 to the target AP MLD 550, for example, based on channel conditions (e.g., channel conditions of the wireless communication channel between STA 540 and the current AP MLD 502 and / or channel conditions of the wireless communication channel between STA 540 and the target AP MLD 550).

[0301] In some demonstrative aspects, STA 540 may be configured to trigger a switch from current AP MLD 502 to target AP MLD 550 , for example, based on a management frame exchange (eg, a single management frame exchange) with target AP MLD 550 .

[0302] In some demonstrative aspects, STA 540 , current AP MLD 502 , and / or target AP MLD 550 may be configured to support a buffering mechanism to identify how much data buffered in current AP MLD 502 is to be shared with target AP MLD 550 .

[0303] In some exemplary aspects, the buffering mechanism may be implementation specific.

[0304] In some demonstrative aspects, for example, once the STA MLD 540 starts or completes the roaming process, the current AP MLD 502 may be configured to share all data buffered at the current AP MLD 502 for the STA MLD 540 with the target AP MLD 550 .

[0305] In some demonstrative aspects, for example, once the STA MLD 540 starts or completes the roaming process, the current AP MLD 502 may be configured to share with the target AP MLD 550 only some of the data buffered at the current AP MLD 502 for the STA MLD 540 .

[0306] In some demonstrative aspects, STA 540 may be configured to send a message to current AP MLD 502 indicating an amount of buffered data to be sent to target AP MLD 550. For example, current AP MLD 502 may be configured to share the amount of data indicated by STA 540 with target AP MLD 550.

[0307] In some demonstrative aspects, STA 540 , current AP MLD 502 , and / or target AP MLD 550 may be configured to support a duplicate packet elimination mechanism to eliminate duplicate packets received by STA 540 from both current AP MLD 502 and target AP MLD 550 .

[0308] In some demonstrative aspects, duplicate packet elimination mechanisms may be implementation specific.

[0309] In some exemplary aspects, duplicate packet elimination may be handled at a higher layer, for example, where the current AP MLD 502 and the target AP MLD 550 use independent block acknowledgement (BA) protocols.

[0310] In some demonstrative aspects, STA 540 , current AP MLD 502 , and / or target AP MLD 550 may be configured to support a capability indication mechanism to indicate the capability of current AP MLD 502 and / or target AP MLD 550 to support the FT protocol utilizing backhaul connection 590 .

[0311] In some demonstrative aspects, current AP MLD 502 may be configured to indicate to STA 540 the capability of current AP MLD 502 to support the FT protocol utilizing backhaul connection 590 .

[0312] In some demonstrative aspects, current AP MLD 502 may be configured to configure a beacon frame sent by current AP MLD 502 to indicate the capability of current AP MLD 502 to support the FT protocol utilizing backhaul connection 590 .

[0313] In some demonstrative aspects, current AP MLD 502 may be configured to configure frames sent by current AP MLD 502 during an association process to STA MLD 540 to indicate the capability of current AP MLD 502 to support the FT protocol utilizing backhaul connection 590 .

[0314] In some demonstrative aspects, current AP MLD 502 may be configured to indicate to STA 540 the capability of target AP MLD 550 to support the FT protocol utilizing backhaul connection 590 .

[0315] In some demonstrative aspects, current AP MLD 502 may be configured to indicate to STA 540 that current AP MLD 502 may support the FT protocol utilizing a backhaul connection 590 with a particular AP or AP MLD (eg, target AP MLD 550).

[0316] In some exemplary aspects, the current AP MLD 502 can be configured to: establish a capability field, for example, in a neighbor report describing a neighbor AP and / or in a reduced neighbor report element describing a neighbor AP, for example, to indicate that the current AP MLD 502 can support the FT protocol utilizing a backhaul connection 590 with a neighbor AP (e.g., the target AP MLD 550).

[0317] In some demonstrative aspects, the STA 540 , the current AP MLD 502 , and / or the target AP MLD 550 may be configured to support an agreement establishment mechanism to establish an agreement for communication between the STA 540 and the target AP MLD 550 .

[0318] In some exemplary aspects, STA 540 and target AP MLD 550 may be configured to communicate protocol establishment messages via current AP MLD 502, e.g., before STA 540 switches from current AP MLD 502 to target AP MLD 550. For example, current AP MLD 502 and target AP MLD 550 may communicate protocol establishment messages via backhaul connection 590.

[0319] In some demonstrative aspects, the agreement establishment message may include an ADDBA message to establish an ADDBA agreement.

[0320] In some exemplary aspects, the agreement establishment message may include a TWT message to establish a TWT agreement.

[0321] In other aspects, the agreement establishment message may include any other additional or alternative types of messages to establish any other additional or alternative agreements.

[0322] Figure 6 is a schematic illustration of communications and operations according to FT protocol 600 according to some exemplary aspects.

[0323] In some exemplary aspects, one or more operations of the FT protocol 600 may be performed by the FTO STA 640, the current AP 602, and the target AP 650, for example, to move the FTO STA 640 from the current AP 602 to the target AP 650, for example, as described below. In one example, the device 140 ( Figure 1 ) may perform one or more operations, one or more functions, roles, and / or functions of the FTO STA 640. In one example, the device 102 ( Figure 1 ) can perform one or more operations, one or more functions, roles and / or functions of the current AP 602. In one example, device 150 ( Figure 1 ) may perform one or more operations, one or more functions, roles and / or functions of the target AP 650.

[0324] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may associate with the current AP 602 and may establish a session 610 (eg, a secure session) with the current AP 602 , for example, to support data transmission between the FTO STA 640 and the current AP 602 .

[0325] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may determine (612) that the FTO STA is to transition to the target AP 650, for example, based on channel conditions of a wireless communication channel between the FTO STA 640 and the current AP 602 and / or based on any other conditions and / or criteria.

[0326] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may send an FT request 614 to the target AP 650 via the current AP 602 , for example, to request FT of the FTO STA 640 from the current AP 602 to the target AP 650 .

[0327] In some exemplary aspects, such as Figure 6 As shown, the current AP 602 may communicate the FT request 614 between the FT OSTA 640 and the target AP 650, for example, via the current AP 602.

[0328] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may process the FT request 614 received from the FT OSTA 640 via the current AP 602.

[0329] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may send a FT response 616 to the FTO STA via the current AP 602, for example, after the FT request 614.

[0330] In some exemplary aspects, such as Figure 6 As shown, the current AP 602 may communicate the FT response 616 between the target AP 650 and the FTO STA 640 , for example, via the current AP 602 .

[0331] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may process the FT response 616 received by the FTO STA 640 via the current AP 602.

[0332] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may send a reassociation request 618 to the target AP 650 via the current AP 602, for example, after the FT response 616. For example, the reassociation request 618 may be configured to request an association between the FTO STA 640 and the target AP 650.

[0333] In some exemplary aspects, such as Figure 6 As shown, the current AP 602 may communicate a reassociation request 618 between the FTOSTA 640 and the target AP 650, such as via the current AP 602.

[0334] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may process the reassociation request 618 received from the FTOSTA 640 via the current AP 602 .

[0335] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may send a reassociation response 620 to the FTO STA 640 via the current AP 602 , for example, following the reassociation request 618 .

[0336] In some exemplary aspects, such as Figure 6 As shown, the current AP 602 may communicate a reassociation response 620 between the target AP 650 and the FTO STA 640 , for example, via the current AP 602 .

[0337] In some exemplary aspects, such as Figure 6As shown, the FTO STA 640 may process a reassociation response 620 received by the FTO STA 640 via the current AP 602 .

[0338] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may switch from the current AP 602 to the target AP 650 for communication via an association session 628 between the FTO STA 640 and the target AP 650.

[0339] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may communicate with the FTO STA 640 via an association session 628 between the FTO STA 640 and the target AP 650 .

[0340] In some exemplary aspects, such as Figure 6 As shown, the FTO STA 640 may send an AP switching request 624 to the target AP 650, for example, after the reassociation response 620. For example, the AP switching request 624 may be configured to request that the FTO STA 640 be switched to the target AP 650 for communication via an association session 628 between the FTO STA 640 and the target AP 650.

[0341] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may process an AP switch request 624 from the FTO STA 640 , for example, after the reassociation response 620 .

[0342] In some exemplary aspects, such as Figure 6 As shown, the target AP 650 may send an AP switch response 626 to the FTO STA 640 , for example, to confirm the request to switch the FTO STA 640 to the target AP 650 .

[0343] In some exemplary aspects, such as Figure 6 As shown, the current AP 602 may send one or more buffered data packets 622 to the target AP 650. The buffered data packets 622 may include data for the FTO STA 640 buffered by the current AP 602 before the FTO STA 640 switches from the current AP 602 to the target AP 650, for example.

[0344] In some demonstrative aspects, the target AP 650 may send the buffered data packets 622 to the FTO STA 640 , eg, via an association session 628 between the FTO STA 640 and the target AP 650 .

[0345] Figure 7 is a schematic flow chart illustration of a method of FT according to some exemplary aspects. For example, Figure 7 One or more of the operations of the method may be performed by a system (e.g., system 100 ( Figure 1 )) of one or more elements (e.g., one or more wireless devices (e.g., device 102 ( Figure 1 ), device 140( Figure 1 ) and / or device 150( Figure 1 ))、MLD(e.g., MLD 131( Figure 1 ), MLD 179( Figure 1 ) and / or MLD 151( Figure 1 )), a controller (e.g., controller 124 ( Figure 1 )、Controller 174( Figure 1 ) and / or controller 154 ( Figure 1 )), a radio device (e.g., a radio device 114 ( Figure 1 )、Radio Device 173( Figure 1 ) and / or radio device 144 ( Figure 1 )) and / or a message processor (e.g., message processor 128 ( Figure 1 ), message processor 178 ( Figure 1 ) and / or message processor 158 ( Figure 1 )))implement.

[0346] As indicated at block 702, the method may include sending an FT request from the STA to the target AP via the current AP associated with the STA. For example, the FT request may be configured to request FT from the current AP to the target AP. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger and / or control device 140 ( Figure 1 ): via current AP 602 ( Figure 6 ), to target AP 650( Figure 6 ) Send FT request 614 ( Figure 6 ), for example as described above.

[0347] As indicated at block 704, the method may include, for example, processing, at the STA, an FT response from the target AP after the FT request. For example, the STA may receive the FT response via the current AP. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger and / or control device 140 ( Figure 1 ): Processing via current AP 602 ( Figure 6 ) from target AP 650( Figure 6 ) received FT response 616 ( Figure 6 ), for example as described above.

[0348] As indicated at block 706, the method may include, after the FT response, sending a reassociation request from the STA to the target AP via the current AP, for example, to request an association between the STA and the target AP. Figure 1 ) may be configured to cause, trigger and / or control device 140 ( Figure 1 ): via current AP 602 ( Figure 6 ) to target AP 650( Figure 6 ) sends a reassociation request 618 ( Figure 6 ), for example as described above.

[0349] As indicated at block 708, the method may include, for example, processing, at the STA, a reassociation response from the target AP after the reassociation request. For example, the STA may receive the reassociation response via the current AP. For example, the controller 154 ( Figure 1 ) may be configured to cause, trigger and / or control device 140 ( Figure 1 ): Processing via current AP 602 ( Figure 6 ) from target AP 650( Figure 6 ) received reassociation response 620( Figure 6 ), for example as described above.

[0350] As indicated at block 710, the method may include switching the STA from the current AP to the target AP, for example, for communication via an association session between the STA and the target AP. Figure 1 ) may be configured to cause, trigger and / or control device 140 ( Figure 1 ): From the current AP 602 ( Figure 6 )Switch to target AP 650( Figure 6 ), for example, for use via the association session 628 ( Figure 6 ) to communicate, for example as described above.

[0351] Figure 8 is a schematic flow chart illustration of a method of FT according to some exemplary aspects. For example, Figure 8 One or more of the operations of the method may be performed by a system (e.g., system 100 ( Figure 1 )) of one or more elements (e.g., one or more wireless devices (e.g., device 102 ( Figure 1 ), device 140( Figure 1 ) and / or device 150( Figure 1 ))、MLD(e.g., MLD 131( Figure 1), MLD 179( Figure 1 ) and / or MLD 151( Figure 1 )), a controller (e.g., controller 124 ( Figure 1 )、Controller 174( Figure 1 ) and / or controller 154 ( Figure 1 )), a radio device (e.g., a radio device 114 ( Figure 1 )、Radio Device 173( Figure 1 ) and / or radio device 144 ( Figure 1 )) and / or a message processor (e.g., message processor 128 ( Figure 1 ), message processor 178 ( Figure 1 ) and / or message processor 158 ( Figure 1 )))implement.

[0352] As indicated at block 802, the method may include communicating an FT request between a STA associated with the current AP and a target AP via the current AP of the FT. For example, the FT request may be from the STA to the target AP. For example, the FT request may be configured to request an FT from the current AP to the target AP by the STA. For example, the controller 102( Figure 1 ) may be configured to cause, trigger and / or control device 102 ( Figure 1 ): In FTO STA 640( Figure 6 ) and target AP 650( Figure 6 ) between which FT request 614 ( Figure 6 ), for example as described above.

[0353] As indicated at block 804, the method may include, for example, communicating an FT response between the target AP and the STA via the current AP after the FT request. For example, the FT response may be from the target AP to the STA. For example, the controller 102 ( Figure 1 ) may be configured to cause, trigger and / or control device 102 ( Figure 1 ): At target AP 650( Figure 6 ) and FTO STA 640( Figure 6 ) between which the FT response 616 ( Figure 6 ), for example as described above.

[0354] As indicated at block 806, the method may include, for example, communicating a reassociation request between the STA and the target AP via the current AP after the FT response. For example, the reassociation request may be from the STA to the target AP. For example, the reassociation request may be configured to request association between the STA and the target AP. For example, the controller 102( Figure 1) may be configured to cause, trigger and / or control device 102 ( Figure 1 ): In FTO STA 640( Figure 6 ) and target AP 650( Figure 6 ) between which the reassociation request 618 is transmitted ( Figure 6 ), for example as described above.

[0355] As indicated at block 808, the method may include, for example, communicating a reassociation response between the target AP and the STA via the current AP after the reassociation request. For example, the reassociation response may be from the target AP to the STA. For example, the controller 102 ( Figure 1 ) may be configured to cause, trigger and / or control device 102 ( Figure 1 ): At target AP 650( Figure 6 ) and FTOSTA 640( Figure 6 ) between the re-association response 320 ( Figure 6 ), for example as described above.

[0356] Fig. 9 is a schematic flow chart illustration of a method of FT according to some exemplary aspects. For example, Fig. 9 One or more of the operations of the method may be performed by a system (e.g., system 100 ( Figure 1 )) of one or more elements (e.g., one or more wireless devices (e.g., device 102 ( Figure 1 ), device 140( Figure 1 ) and / or device 150( Figure 1 ))、MLD(e.g., MLD 131( Figure 1 ), MLD 179( Figure 1 ) and / or MLD 151( Figure 1 )), a controller (e.g., controller 124 ( Figure 1 )、Controller 174( Figure 1 ) and / or controller 154 ( Figure 1 )), a radio device (e.g., a radio device 114 ( Figure 1 )、Radio Device 173( Figure 1 ) and / or radio device 144 ( Figure 1 )) and / or a message processor (e.g., message processor 128 ( Figure 1 ), message processor 178 ( Figure 1 ) and / or message processor 158 ( Figure 1 )))implement.

[0357] As indicated at block 902, the method may include processing, at a target AP for FT, a FT request from a STA associated with a current AP, the FT request being received from the STA via the current AP. For example, the FT request may be configured to request FT from the current AP to the target AP. For example, the controller 174( Figure 1 ) may be configured to cause, trigger and / or control device 150 ( Figure 1 ): Processing via current AP 602 ( Figure 6 )From FTO STA 640( Figure 6 ) received FT request 614 ( Figure 6 ), for example as described above.

[0358] As indicated at block 904, the method may include, for example, sending an FT response from the target AP to the STA via the current AP after the FT request. For example, the controller 174 ( Figure 1 ) may be configured to cause, trigger and / or control device 150 ( Figure 1 ): via current AP 602 ( Figure 6 ) to FTO STA 640( Figure 6 ) Send FT response 616 ( Figure 6 ), for example as described above.

[0359] As indicated at block 906, the method may include processing, at the target AP, a reassociation request from the STA. For example, the reassociation request may be received from the STA via the current AP, for example, after the FT response. For example, the reassociation request may be configured to request an association between the STA and the target AP. For example, the controller 174( Figure 1 ) may be configured to cause, trigger and / or control device 150 ( Figure 1 ): Processing via current AP 602 ( Figure 6 )From FTO STA 640( Figure 6 ) received reassociation request 618 ( Figure 6 ), for example as described above.

[0360] As indicated at block 908, the method may include, for example, sending a reassociation response from the target AP to the STA via the current AP after the reassociation request. Figure 1 ) may be configured to cause, trigger and / or control device 150 ( Figure 1 ): via current AP 602 ( Figure 6 ) to FTO STA 640( Figure 6 ) Send reassociation response 620 ( Figure 6 ), for example as described above.

[0361] As indicated at block 910, the method may include communicating with the STA via an association session between the STA and the target AP. For example, the controller 174 ( Figure 1 ) may be configured to cause, trigger and / or control device 150 ( Figure 1 ): via association session 628 ( Figure 6 ) and FTO STA 640( Figure 6 ) to communicate, for example as described above.

[0362] Reference Fig.10 , which schematically illustrates an article of manufacture 1000 according to some exemplary aspects. Article 1000 may include one or more tangible computer-readable ("machine-readable") non-transitory storage media 1002, which may include computer-executable instructions (e.g., implemented by logic 1004), which, when executed by at least one computer processor, enable at least one computer processor to perform a process in a device 102 ( Figure 1 )、device 140( Figure 1 )、device 150( Figure 1 )、MLD131( Figure 1 )、MDL 179( Figure 1 )、MLD 151( Figure 1 )、Radio device 114( Figure 1 )、Radio Device 173( Figure 1 )、Radio Device 144( Figure 1 )、Transmitter 118( Figure 1 )、Transmitter 148( Figure 1 )、Receiver 116( Figure 1 )、Receiver 146( Figure 1 )、Message processor 128( Figure 1 ), message processor 178 ( Figure 1 )、Message processor 158( Figure 1 )、Controller 124( Figure 1 )、Controller 174( Figure 1 ) and / or controller 154 ( Figure 1 ) to implement one or more operations, thereby enabling device 102 ( Figure 1 )、device 140( Figure 1 )、device 150( Figure 1 )、MLD 131( Figure 1 )、MLD 179( Figure 1 )、MLD 151( Figure 1 )、Radio device 114( Figure 1 )、Radio Device 173( Figure 1 )、Radio Device 144( Figure 1 )、Transmitter 118( Figure 1 )、Transmitter 148( Figure 1 )、Receiver 116( Figure 1 )、Receiver 146( Figure 1 )、Message processor 128( Figure 1 ), message processor 178 ( Figure 1 )、Message processor 158( Figure 1 )、Controller 124( Figure 1 ), controller 174 and / or controller 154 ( Figure 1 ) execute, trigger and / or implement one or more operations and / or functions, and / or execute, trigger and / or implement reference Figure 1 , 2 , 3, 4, 5, 6, 7, 8 and / or 9, and / or one or more operations described herein. The phrases "non-transitory machine-readable medium" and "computer-readable non-transitory storage medium" may be directed to include all machine and / or computer-readable media, with the only exception being transient propagating signals.

[0363] In some exemplary aspects, the product 1000 and / or the machine-readable storage medium 1002 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. For example, the machine-readable storage medium 1002 may include RAM, DRAM, double data rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, disk, hard drive, etc. The computer-readable storage medium may include any suitable medium involved in downloading or transferring a computer program from a remote computer to a requesting computer via a communication link (e.g., a modem, a radio device, or a network connection), the computer program being carried by a data signal embodied in a carrier wave or other propagation medium.

[0364] In some exemplary aspects, logic 1004 may include instructions, data, and / or code that, if executed by a machine, may cause the machine to perform methods, processes, and / or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware, software, firmware, etc.

[0365] In some exemplary aspects, logic 1004 may include or may be implemented as software, a software module, an application, a program, a subroutine, an instruction, an instruction set, a computing code, a word, a value, a symbol, etc. Instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Instructions may be implemented according to a predefined computer language, manner, or syntax for instructing a processor to perform a specific function. Instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language, machine code, etc.

[0366] Example

[0367] The following examples pertain to further aspects.

[0368] Example 1 includes: an apparatus including logic and circuitry, configured to cause a wireless communication station (STA): to send a fast basic service set (BSS) transition (FT) request to a target access point (AP) via a current AP associated with the STA, wherein the FT request is configured to: request FT from the current AP to the target AP; after the FT request, process an FT response from the target AP, the FT response being received by the STA via the current AP; after the FT response, send a reassociation request to the target AP via the current AP, the reassociation request being used to request association between the STA and the target AP; after the reassociation request, process a reassociation response from the target AP, the reassociation response being received by the STA via the current AP; and switch the STA from the current AP to the target AP for communication via an association session between the STA and the target AP.

[0369] Example 2 includes: the subject matter as described in Example 1, and optionally, wherein the device is configured to cause the STA to: process one or more buffered data packets received from the target AP via an association session between the STA and the target AP, wherein the buffered data packets include data buffered by the current AP before the STA switches from the current AP to the target AP.

[0370] Example 3 includes: the subject matter as described in Example 2, and optionally, wherein the apparatus is configured to cause the STA to: send a message to the current AP including an indication of criteria for sending buffered data packets to the target AP.

[0371] Example 4 includes the subject matter of Example 3, and optionally, wherein the criterion comprises an amount of buffered data packets to be sent to the target AP.

[0372] Example 5 includes: a subject matter as described in any one of Examples 1-4, and optionally, wherein the apparatus is configured to cause the STA to: trigger transmission of the reassociation request to the target AP based on a channel condition of a wireless communication channel between the STA and the current AP.

[0373] Example 6 includes: a subject matter as described in any one of Examples 1-5, and optionally, wherein the device is configured to cause the STA to: after the reassociation response, send an AP switching request to the target AP, wherein the AP switching request is used to request that the STA be switched to the target AP for communication via an association session between the STA and the target AP.

[0374] Example 7 includes: the subject matter as described in Example 6, and optionally, wherein the device is configured to cause the STA to: process an AP switching response from the target AP, wherein the AP switching response is used to confirm a request to switch the STA to the target AP for communication via an association session between the STA and the target AP.

[0375] Example 8 includes: a subject matter as described in any one of Examples 1-7, and optionally, wherein the device is configured to enable the STA to: identify, based on a capability indication in a message from the current AP, the ability of the current AP to support communicating the reassociation request and the reassociation response with the target AP.

[0376] Example 9 includes the subject matter of Example 8, and optionally, wherein the message from the current AP comprises a beacon from the current AP, or an association frame received from the current AP during association with the current AP.

[0377] Example 10 includes: a subject matter as described in any one of Examples 1-9, and optionally, wherein the device is configured to enable the STA to: identify, based on a capability indication in a neighbor report element from the current AP, the ability of the target AP to support transmission of the reassociation request and the reassociation response via the current AP.

[0378] Example 11 includes: the subject matter of any one of Examples 1-10, and optionally, wherein the reassociation request and the reassociation response include tunnel messages according to a tunnel protocol between the STA and the target AP via the current AP.

[0379] Example 12 includes: a subject matter as described in any one of Examples 1-11, and optionally, wherein the device is configured to cause the STA to: transmit an agreement establishment message with the target AP via the current AP before the STA switches from the current AP to the target AP, wherein the agreement establishment message is configured to: establish an agreement for communication via an association session between the STA and the target AP.

[0380] Example 13 includes: the subject matter as described in Example 12, and optionally, wherein the agreement establishment message includes at least one of: an add block acknowledgment (ADDBA) message for establishing an ADDBA agreement; or a target wake time (TWT) message for establishing a TWT agreement.

[0381] Example 14 includes the subject matter of any of Examples 1-13, and optionally, wherein the FT includes a FT between the current AP and the target AP through a distribution system (DS).

[0382] Example 15 includes: the subject matter of any of claims 1-14, and optionally, wherein the STA comprises a non-AP multi-link device (MLD) including a plurality of non-AP STAs.

[0383] Example 16 includes: the subject matter of any of Examples 1-15, and optionally, includes at least one radio device for communicating the FT request, the FT response, the reassociation request, and the reassociation response.

[0384] Example 17 includes the subject matter of Example 16, and optionally, includes: one or more antennas connected to the radio; and a processor for executing instructions of an operating system of the STA.

[0385] Example 18 includes: a device including logic and circuits, configured to: cause a target access point (AP) of a fast basic service set (BSS) transition (FT): to: process an FT request from a wireless communication station (STA) associated with a current AP, the FT request being received from the STA via the current AP, wherein the FT request is configured to: request FT from the current AP to the target AP; after the FT request, send a FT response to the STA via the current AP; process a reassociation request from the STA, the reassociation request being received from the STA via the current AP after the FT response, the reassociation request being used to request association between the STA and the target AP; after the reassociation request, send a reassociation response to the STA via the current AP; and communicate with the STA via an association session between the STA and the target AP.

[0386] Example 19 includes: the subject matter as described in Example 18, and optionally, wherein the device is configured to cause the target AP to: process one or more buffered data packets received from the current AP, and send the buffered data packets to the STA via an association session between the STA and the target AP, wherein the buffered data packets include data packets buffered by the current AP before the STA switches from the current AP to the target AP.

[0387] Example 20 includes: the subject matter as described in Example 18 or 19, and optionally, wherein the device is configured to cause the target AP to: after the reassociation response, process an AP switching request from the STA, wherein the AP switching request is used to request that the STA be switched to the target AP for communication via an association session between the STA and the target AP.

[0388] Example 21 includes: the subject matter as described in Example 20, and optionally, wherein the device is configured to cause the target AP to: send an AP switching response to the STA, wherein the AP switching response is used to confirm a request to switch the STA to the target AP for communication via an association session between the STA and the target AP.

[0389] Example 22 includes: a subject matter as described in any one of Examples 18-21, and optionally, wherein the device is configured to cause the target AP to: transmit an agreement establishment message with the STA via the current AP before the STA switches from the current AP to the target AP, wherein the agreement establishment message is configured to: establish an agreement for communication via an association session between the STA and the target AP.

[0390] Example 23 includes: the subject matter as described in Example 22, and optionally, wherein the agreement establishment message includes at least one of: an add block acknowledgment (ADDBA) message for establishing an ADDBA agreement; or a target wake time (TWT) message for establishing a TWT agreement.

[0391] Example 24 includes the subject matter of any of Examples 18-23, and optionally, wherein the FT includes a FT between the current AP and the target AP through a distribution system (DS).

[0392] Example 25 includes the subject matter of any of Examples 18-24, and optionally, wherein the target AP comprises an AP multi-link device (MLD) including a plurality of AP STAs.

[0393] Example 26 includes the subject matter of any of Examples 18-25, and optionally, includes at least one radio device for communicating with the STA via an association session between the STA and the target AP.

[0394] Example 27 includes the subject matter of Example 26, and optionally, includes: one or more antennas connected to the radio; and a processor for executing instructions of an operating system of the target AP.

[0395] Example 28 includes: a device including logic and circuits, configured to: cause an access point (AP) to act as a current AP for a fast basic service set (BSS) transition (FT) to: transmit an FT request between a wireless communication station (STA) associated with the current AP and a target AP via the current AP, the FT request being from the STA to the target AP, the FT request being used to request FT of the STA from the current AP to the target AP; after the FT request, transmit an FT response between the target AP and the STA via the current AP, the FT response being from the target AP to the STA; after the FT response, transmit a reassociation request between the STA and the target AP via the current AP, the reassociation request being from the STA to the target AP, the reassociation request being used to request association between the STA and the target AP; and after the reassociation request, transmit a reassociation response between the target AP and the STA via the current AP, the reassociation response being from the target AP to the STA.

[0396] Example 29 includes: the subject matter as described in Example 28, and optionally, wherein the device is configured to cause the current AP to: send one or more buffered data packets to the target AP, wherein the buffered data packets include data for the STA buffered by the current AP before the STA switches from the current AP to the target AP.

[0397] Example 30 includes the subject matter of Example 29, and optionally, wherein the apparatus is configured to cause the current AP to: identify criteria for sending buffered data packets to the target AP based on a message from the STA.

[0398] Example 31 includes the subject matter of Example 30, and optionally, wherein the criterion comprises an amount of buffered data packets to be sent to the target AP.

[0399] Example 32 includes: a subject matter as described in any of Examples 28-31, and optionally, wherein the apparatus is configured to cause the current AP to: send a capability indication in a message from the current AP to indicate that the current AP supports the ability to communicate the reassociation request and the reassociation response with the target AP.

[0400] Example 33 includes: the subject matter of Example 32, and optionally, wherein the message from the current AP comprises a beacon from the current AP, or an association frame sent to the STA during association with the STA.

[0401] Example 34 includes: a subject matter as described in any of Examples 28-33, and optionally, wherein the apparatus is configured to cause the current AP to: send a neighbor report element corresponding to the target AP, the neighbor report element including an indication of the target AP's ability to support transmission of the reassociation request and the reassociation response via the current AP.

[0402] Example 35 includes: the subject matter of any of Examples 28-34, and optionally, wherein the reassociation request and the reassociation response include tunnel messages according to a tunnel protocol between the STA and the target AP via the current AP.

[0403] Example 36 includes: a subject matter as described in any one of Examples 28-35, and optionally, wherein the device is configured to cause the current AP to: transmit an agreement establishment message between the STA and the target AP via the current AP before the STA switches from the current AP to the target AP, wherein the agreement establishment message is configured to: establish an agreement for communicating via an association session between the STA and the target AP.

[0404] Example 37 includes: the subject matter as described in Example 36, and optionally, wherein the agreement establishment message includes at least one of: an add block acknowledgment (ADDBA) message for establishing an ADDBA agreement; or a target wake time (TWT) message for establishing a TWT agreement.

[0405] Example 38 includes the subject matter of any of Examples 28-37, and optionally, wherein the FT includes a FT between the current AP and the target AP through a distribution system (DS).

[0406] Example 39 includes the subject matter of any of Examples 28-38, and optionally, wherein the AP comprises an AP multi-link device (MLD) comprising a plurality of AP STAs.

[0407] Example 40 includes: the subject matter of any of Examples 28-39, and optionally, includes at least one radio device for communicating the FT request, the FT response, the reassociation request, and the reassociation response with the STA.

[0408] Example 41 includes the subject matter of Example 40, and optionally, includes: one or more antennas connected to the radio; and a processor for executing instructions of an operating system of the AP.

[0409] Example 42 includes a wireless communication device comprising the apparatus of any of Examples 1-41.

[0410] Example 43 includes an apparatus comprising means for performing any of the operations described in any of Examples 1-41.

[0411] Example 44 includes a product comprising one or more tangible computer-readable non-transitory storage media, the storage media including computer-executable instructions that are operable, when executed by at least one processor, to enable the at least one processor to cause a wireless communication device to perform any of the operations described in any of Examples 1-41.

[0412] Example 45 includes an apparatus comprising: a memory interface; and a processing circuit configured to perform any of the operations described in any of Examples 1-41.

[0413] Example 46 includes a method comprising any of the described operations of any of Examples 1-41.

[0414] The functions, operations, components, and / or features described herein with reference to one or more aspects may be combined with, or utilized in combination with, one or more other functions, operations, components, and / or features described herein with reference to one or more other aspects, and vice versa.

[0415] While certain features have been shown and described herein, numerous modifications, substitutions, changes, and equivalents will occur to those skilled in the art. It is therefore to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Claims

1. An apparatus comprising logic and circuitry configured to enable a wireless communication station (STA): Sending a fast basic service set (BSS) transition (FT) request to a target AP via a current access point (AP) associated with the STA, wherein: The FT request is configured to: request FT from the current AP to the target AP; processing an FT response from the target AP after the FT request, the FT response being received by the STA via the current AP; After the FT response, sending a reassociation request to the target AP via the current AP, the reassociation request being used to request association between the STA and the target AP; processing a reassociation response from the target AP after the reassociation request, the reassociation response being received by the STA via the current AP; as well as The STA is switched from the current AP to the target AP for communication via an association session between the STA and the target AP.

2. The apparatus according to claim 1, configured to cause the STA to: processing one or more buffered data packets received from the target AP via an association session between the STA and the target AP, in, The buffered data packets include data buffered by the current AP before the STA switches from the current AP to the target AP.

3. The apparatus according to claim 2, configured to cause the STA to: A message is sent to the current AP including an indication of criteria for sending buffered data packets to the target AP.

4. The device as claimed in claim 3, wherein: The criteria include an amount of buffered data packets to be sent to the target AP.

5. The apparatus according to any one of claims 1 to 4, configured to enable the STA to: The transmission of the reassociation request to the target AP is triggered based on a channel condition of a wireless communication channel between the STA and the current AP.

6. The apparatus according to any one of claims 1 to 5, configured to enable the STA to: After the re-association response, an AP switching request is sent to the target AP, where the AP switching request is used to request that the STA be switched to the target AP for communication via an association session between the STA and the target AP.

7. The apparatus of claim 6, configured to cause the STA to: An AP handoff response from the target AP is processed, the AP handoff response confirming a request to handoff the STA to the target AP for communication via an association session between the STA and the target AP.

8. The apparatus according to any one of claims 1 to 7, configured to enable the STA to: Based on the capability indication in the message from the current AP, it is identified that the current AP supports a capability of communicating the reassociation request and the reassociation response with the target AP.

9. The device of claim 8, wherein: The message from the current AP includes a beacon from the current AP, or an association frame received from the current AP during association with the current AP.

10. The apparatus according to any one of claims 1 to 9, configured to enable the STA to: Based on a capability indication in a neighbor report element from the current AP, a capability of the target AP to support communication of the reassociation request and the reassociation response via the current AP is identified.

11. The device according to any one of claims 1 to 10, wherein: The reassociation request and the reassociation response include tunnel messages according to a tunneling protocol between the STA and the target AP via the current AP.

12. The apparatus according to any one of claims 1 to 11, configured to enable the STA to: Before the STA switches from the current AP to the target AP, a protocol establishment message is transmitted via the current AP to the target AP. in, The agreement establishment message is configured to establish an agreement for communicating via an association session between the STA and the target AP.

13. The device of claim 12, wherein: The agreement establishment message includes at least one of the following: an add block acknowledgement (ADDBA) message for establishing an ADDBA agreement; or a target wake time (TWT) message for establishing a TWT agreement.

14. The device according to any one of claims 1 to 13, wherein: The FT includes a FT between the current AP and the target AP through a distribution system (DS).

15. The device according to any one of claims 1 to 14, wherein: The STA includes a non-AP multi-link device (MLD) including a plurality of non-AP STAs.

16. The apparatus of any one of claims 1-15, comprising at least one radio device for communicating the FT request, the FT response, the reassociation request, and the reassociation response.

17. The apparatus of claim 16, comprising: one or more antennas connected to the radio; and A processor is used to execute instructions of an operating system of the STA.

18. An apparatus comprising logic and circuitry configured to cause a target access point (AP) of a fast basic service set (BSS) transition (FT): processing an FT request from a wireless communication station (STA) associated with a current AP, the FT request being received from the STA via the current AP, wherein: The FT request is configured to: request FT from the current AP to the target AP; After the FT request, sending an FT response to the STA via the current AP; processing a reassociation request from the STA, the reassociation request being received from the STA via the current AP after the FT response, the reassociation request being used to request association between the STA and the target AP; After the reassociation request, sending a reassociation response to the STA via the current AP; as well as Communicating with the STA via an association session between the STA and the target AP.

19. The apparatus of claim 18, configured to cause the target AP to: processing one or more buffered data packets received from the current AP; and sending buffered data packets to the STA via an association session between the STA and the target AP, in, The buffered data packets include data packets buffered by the current AP before the STA switches from the current AP to the target AP.

20. The apparatus according to claim 18 or 19, configured to cause the target AP to: After the reassociation response, an AP switching request from the STA is processed, the AP switching request being used to request that the STA be switched to the target AP for communication via an association session between the STA and the target AP.

21. The apparatus of claim 20, configured to cause the target AP to: An AP switching response is sent to the STA, the AP switching response being used to confirm a request to switch the STA to the target AP for communication via an association session between the STA and the target AP.

22. An apparatus comprising logic and circuitry configured to: cause an access point (AP) to act as a current AP for a fast basic service set (BSS) transition (FT) to: transmitting, via the current AP, an FT request between a wireless communication station (STA) associated with the current AP and a target AP, the FT request being from the STA to the target AP, the FT request being used to request the STA to perform FT from the current AP to the target AP; After the FT request, an FT response is communicated between the target AP and the STA via the current AP, the FT response being from the target AP to the STA; After the FT response, transmitting a reassociation request between the STA and the target AP via the current AP, the reassociation request being from the STA to the target AP, the reassociation request being used to request association between the STA and the target AP; as well as After the reassociation request, a reassociation response is communicated between the target AP and the STA via the current AP, the reassociation response being from the target AP to the STA.

23. The apparatus of claim 22, configured to cause the current AP to: sending one or more buffered data packets to the target AP, in, The buffered data packets include data for the STA buffered by the current AP before the STA switches from the current AP to the target AP.

24. An article of manufacture comprising one or more tangible computer-readable non-transitory storage media, the one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, cause the at least one processor to cause a wireless communication station (STA): Sending a fast basic service set (BSS) transition (FT) request to a target AP via a current access point (AP) associated with the STA, wherein: The FT request is configured to: request FT from the current AP to the target AP; processing an FT response from the target AP after the FT request, the FT response being received by the STA via the current AP; After the FT response, sending a reassociation request to the target AP via the current AP, the reassociation request being used to request association between the STA and the target AP; processing a reassociation response from the target AP after the reassociation request, the reassociation response being received by the STA via the current AP; as well as The STA is switched from the current AP to the target AP for communication via an association session between the STA and the target AP.

25. The product of claim 24, wherein: When executed, the instruction causes the STA to: After the re-association response, an AP switching request is sent to the target AP, where the AP switching request is used to request that the STA be switched to the target AP for communication via an association session between the STA and the target AP.

Images