Seamless roaming of network recommendations

Abstract

The present disclosure provides techniques that enable a network entity to indicate to a wireless station (STA) a recommendation for seamless roaming. For example, a single mobile domain (SMD) entity with knowledge of various access points (APs) (e.g., regarding load and capabilities) can be able to recommend a set of one or more APs that can be the most suitable as a target for the STA to transition to.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Patent Application No. 18 / 506,831, filed November 10, 2023, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety, as fully set forth below and for all applicable purposes. Technical Field

[0002] This disclosure relates in general to wireless communications, and more specifically to techniques that enable network entities to instruct wireless stations on recommendations for seamless roaming. Background Technology

[0003] A Wireless Local Area Network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices (also known as wireless stations (STAs)). The basic building block of a WLAN conforming to the IEEE 802.11 standard family is the Basic Service Set (BSS) managed by the AP. Each BSS is identified by a Basic Service Set Identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STA within the AP's wireless range to establish or maintain a communication link with the WLAN.

[0004] In wireless systems (such as IEEE 802.11 compliant networks), wireless stations (STAs) often roam between the coverage areas of different access points (APs). In a typical system, when a STA roams, it hands over its service from the source AP (currently serving the STA) to the target AP. As part of this handover process, the STA typically needs to re-associate with the target AP. This re-association usually occurs before the network can switch the data path from the source AP to the target AP. Unfortunately, the re-association process can be relatively time-consuming and interrupt data flow, which can negatively impact the user experience. Summary of the Invention

[0005] The systems, methods, and apparatus disclosed herein each have several innovative aspects, and no single aspect is solely responsible for the desired properties disclosed herein.

[0006] An innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at a first wireless node. The method includes: establishing an association with a single mobile domain (SMD) entity; communicating with a first set of one or more serving access point (AP) devices attached to the SMD entity; obtaining at least a first frame indicating the one or more AP devices attached to the SMD entity; after obtaining the at least first frame, selecting a second set of one or more target AP devices; and transitioning from the first set to the second set.

[0007] On the other hand, a method for wireless communication at a second wireless node is provided. The method includes: generating at least a first frame indicating one or more serving AP devices attached to a single mobile domain (SMD) entity, wherein the second wireless node is also attached to the SMD entity; outputting the at least the first frame to a first wireless node attached to the SMD entity; and, after outputting the first frame, participating in a process of transferring the first wireless node from a first set of one or more serving AP devices to a second set of one or more serving AP devices.

[0008] Other aspects provide: an apparatus (e.g., a wireless node / wireless station / wireless access point / wireless communication device) capable of operating to, being configured to, or otherwise adapted to perform one or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of the apparatus (e.g., directly, indirectly, after preprocessing, or without preprocessing), cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0009] Details of one or more specific embodiments of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0010] Figure 1 A schematic diagram of an example wireless communication network is shown.

[0011] Figure 2 A block diagram depicts an example multi-link device (MLD) deployment.

[0012] Figure 3 An example multi-link operation (MLO) architecture is described.

[0013] Figure 4 A sample call flowchart for a handover initiated by an example station is depicted.

[0014] Figure 5 A sample call flowchart illustrating a network-initiated handover is depicted.

[0015] Figure 6 An example single mobile domain (SMD) MLD deployment hierarchy is described.

[0016] Figure 7 A sample call flowchart illustrating seamless roaming via network recommendation is depicted.

[0017] Figure 8 A flowchart illustrating an example method for wireless communication is shown.

[0018] Figure 9 A flowchart illustrating an example method for wireless communication is shown.

[0019] Figure 10 A block diagram of an example wireless communication device is depicted.

[0020] The same reference numerals and names in the various figures indicate the same elements. Detailed Implementation

[0021] The following description refers to certain specific examples in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some or all of the examples described can be applied in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or Bluetooth as defined by the Bluetooth Special Interest Group (SIG). ® This can be implemented in any device, system, or network that transmits and receives radio frequency (RF) signals according to one or more of the standards or those published by the 3rd Generation Partnership Project (3GPP), such as Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)). The described examples can be implemented in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiplexing (OFDM), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Space Division Multiple Access (SDMA), Rate Split Multiple Access (RSMA), Multi-User Shared Access (MUSA), Single-User (SU) Multiple-Input Multiple-Output (MIMO), and Multi-User (MU) MIMO (MU-MIMO). The described examples can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of the following networks: Wireless Personal Area Network (WPAN), Wireless Local Area Network (WLAN), Wireless Wide Area Network (WWAN), Wireless Metropolitan Area Network (WMAN), or Internet of Things (IoT).

[0022] This disclosure provides apparatus, methods, processing systems, and computer-readable media for seamless roaming via network recommendations.

[0023] In conventional wireless communication systems, when a radio station (STA) roams between multiple access points (APs), the STA needs to re-associate with the new (target) AP and perform an association process (e.g., including a four-way handshake). The four-way handshake typically refers to the exchange of four messages between the AP MLD and non-AP MLDs to generate and exchange various encryption keys used to encrypt data transmitted between the AP and the STA. This four-message exchange can cause undue delays when the STA roams between APs, but it needs to be performed before the network can switch data paths. Therefore, this type of roaming or handover between APs is called a disconnect-before-establish handover because the connection to the serving AP is disconnected before the connection to the target AP is established, causing data interruption and additional delays during the handover process.

[0024] To address this issue, the techniques disclosed herein utilize features of a multi-link operation (MLO) architecture, which enables STAs to roam seamlessly between APs without requiring reassociation. MLO typically refers to features in advanced wireless systems, such as those defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11be Extremely High Throughput (EHT) and the 802.11 revision associated with Wi-Fi 8, that enable transmission and reception between devices using multiple links employing various frequency channels. MLO allows APs, clients, or both to concurrently utilize multiple radio links on different frequency channels / bands. Devices capable of MLO are typically referred to as multi-link devices (MLDs).

[0025] In some cases, APs (e.g., non-coordinated APs located in different physical locations) can be connected as auxiliary APs to a single AP MLD. Therefore, when a STA (e.g., a non-AP MLD) moves between these APs, the STA can bypass the MLO (re)association and four-way handshake process. These techniques, often referred to as seamless roaming or establish-before-disconnect handover processes, avoid data interruptions and reduce latency during handover.

[0026] Seamless roaming can be considered a useful feature in ultra-high reliability (UHR) networks, enabling client devices to move from one serving AP to another without re-associating. Seamless roaming may involve the UHR AP providing information related to a single mobility domain (SMD) entity (e.g., an SMD AP MLD), advertising candidate APs for clients to choose from for roaming, and possibly transferring context between APs. Such a handover can be initiated by a non-AP MLD (STA), or the network can recommend to a non-AP MLD different sets of serving APs to move to (e.g., co-located or non-co-located).

[0027] Various aspects of this disclosure provide techniques for network entities to recommend a set of suitable candidate APs as handover targets to non-AP MLDs. This disclosure provides mechanisms (e.g., container / signaling frameworks) for providing such recommendations. In some aspects, such recommendations may be based on an Extended Basic Services Set (BSS) Transformation Management (BTM) framework or a Multi-Link (ML) Reconfiguration framework, or a combination of both. In some aspects, such recommendations may be based on a request from a non-AP MLD or may be unsolicited. In some cases, such frames (e.g., requests, BTM, or ML reconfigurations) may be protected frames (e.g., encrypted).

[0028] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential benefits. In some examples, the described techniques can be used to help ensure that non-AP MLD devices are transitioned to a suitable AP (or AP set) via seamless roaming. Therefore, the techniques proposed herein can help ensure a successful handover, improve post-handover performance, and enhance the overall user experience.

[0029] Figure 1A schematic diagram of an example wireless communication network 100 is shown. Depending on some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) (such as a Wi-Fi network). For example, the wireless communication network 100 may be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as those defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and 802.11bn). In some other examples, the wireless communication network 100 may be an example of a cellular radio access network (RAN), such as a 5G RAN or 6G RAN implementing one or more cellular protocols (such as those specified in one or more 3GPP standards). In some other examples, the wireless communication network 100 may include a WLAN that operates in an interoperable or converged manner with one or more cellular RANs to provide greater or enhanced network coverage to wireless communication devices within the wireless communication network 100, or to enable these devices to connect to the core of the cellular network, such as to access network management capabilities and functionality provided by the cellular network core.

[0030] The wireless communication network 100 may include numerous wireless communication devices, including at least one wireless access point (AP) 102 and any number of wireless stations (STA) 104. Although Figure 1 Only one AP 102 is shown, but the wireless communication network 100 may include multiple APs 102. AP 102 may be or represent various different types of network entities, including but not limited to home networking APs, enterprise APs, single-band APs, dual-band synchronous (DBS) APs, tri-band synchronous (TBS) APs, standalone APs, non-standalone APs, software-enabled APs (software APs), and multi-link APs (also known as AP multi-link devices (MLDs)), as well as cellular (such as 3GPP, 4G LTE, 5G, or 6G) base stations or other cellular network nodes (such as Node B, evolved Node B (eNB), gNB, Transmit Receive Point (TRP)) or another type of equipment or apparatus included in the radio access network (RAN), including open RAN (O-RAN) network entities such as central units (CUs), distributed units (DUs), or radio units (RUs).

[0031] Each STA 104 may also be referred to as a mobile station (MS), mobile device, mobile phone, wireless phone, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, etc. STA 104 can represent a variety of devices such as mobile phones, other handheld or wearable communication devices, netbooks, laptops, tablets, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR), or extended reality (XR) wireless headsets or other peripherals, wireless earbuds, other wearable devices, display devices (e.g., televisions, computer monitors, or video game consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators) or other home appliances, remote keys (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, vehicles, etc.

[0032] A single AP 102 and its associated set of STA 104s may be referred to as a Basic Service Set (BSS), which is managed by the respective AP 102. Figure 1 Additionally, an example coverage area 108 of AP 102 is shown, which may represent the Basic Service Area (BSA) of wireless communication network 100. The BSA can be identified by STA 104 and other devices via a Service Set Identifier (SSID) and a Basic Service Set Identifier (BSSID), which may be the Media Access Control (MAC) address of AP 102. AP 102 may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STA 104 within the wireless range of AP 102 to “associate” or reassociate with AP 102 to establish or maintain a corresponding communication link 106 (also referred to hereinafter as a “Wi-Fi link”) with AP 102. For example, the beacon may include an identifier or indication of the primary channel used by the corresponding AP 102, and a Timing Synchronization Function (TSF) for establishing or maintaining timing synchronization with AP 102. AP 102 can provide access to external networks to each STA 104 in the wireless communication network 100 via the corresponding communication link 106.

[0033] To establish a communication link 106 with AP 102, each STA 104 is configured to perform a passive or active scanning operation (“scan”) on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform a passive scan, STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (referred to as the Target Beacon Transmission Time (TBTT)). To perform an active scan, STA 104 generates probe requests and transmits these requests sequentially on each channel to be scanned, and listens for probe responses from AP 102. Each STA 104 can identify, determine, detect, or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and performs authentication and association operations to establish a communication link 106 with the selected AP 102. The selected AP 102 assigns an association identifier (AID) to STA 104 at the end of the association operation, and AP 102 uses the association identifier (AID) to track STA 104.

[0034] As wireless networks become increasingly prevalent, STA 104 may have the opportunity to choose from one of many BSSs within its range or from multiple APs 102 that together form an Extended Service Set (ESS) (comprising multiple connected BSSs). For example, wireless communication network 100 may be connected to a wired or wireless distribution system capable of connecting multiple APs 102 in such an ESS. Therefore, STA 104 may be covered by more than one AP 102 and may be associated with different APs 102 at different times for different transmissions. Additionally, after associating with an AP 102, STA 104 may periodically scan its surroundings to find a more suitable AP 102 to associate with. For example, STA 104 moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 with more desirable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0035] In some cases, STA 104 can form a network without AP 102 or other equipment besides STA 104 itself. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may also be referred to as mesh networks or peer-to-peer (P2P) networks. In some cases, ad hoc networks can be implemented within a larger network, such as wireless communication network 100. In such examples, while STA 104 may be able to communicate with each other via communication link 106 through AP 102, STA 104 may also communicate directly with each other via direct wireless communication link 110. Additionally, two STA 104 may communicate via direct communication link 110, regardless of whether the two STA 104 are associated with and served by the same AP 102. In such ad hoc systems, one or more STAs among STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as the group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi direct connections, connections established by using Wi-Fi Tunneling Direct Link Establishment (TDLS) links, and other P2P group connections.

[0036] In some networks, AP 102 or STA 104, or both, can support applications associated with high throughput or low latency requirements, or provide lossless audio to one or more other devices. For example, AP 102 or STA 104 can support applications and use cases associated with ultra-low latency (ULL), such as ULL gaming, or streaming lossless audio and video to one or more personal audio devices (such as peripherals) or AR / VR / MR / XR headsets. In scenarios where a user uses two or more peripherals, AP 102 or STA 104 can support extended personal audio networks that enable communication with these two or more peripherals. Additionally, AP 102 and STA 104 can support additional ULL applications with ULL and high throughput requirements, such as cloud-based applications (such as VR cloud gaming).

[0037] As indicated above, in some implementations, AP 102 and STA 104 may operate and communicate according to one or more of the IEEE 802.11 series of wireless communication protocol standards (via the corresponding communication link 106). These standards define WLAN radio and baseband protocols for the physical (PHY) layer and MAC layer. AP 102 and STA 104 transmit and receive wireless communications to and from each other in the form of PHY Protocol Data Units (PPDUs) (also referred to below as "Wi-Fi communication" or "wireless packets").

[0038] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In instances where the PPDU is transmitted on a bound channel or a wideband channel, the preamble field may be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble can be used for other purposes such as packet detection, automatic gain control, and channel estimation. The legacy preamble is also typically used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-legacy portion of the preamble are associated with the specific IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0039] AP 102 and STA 104 in WLAN 100 can transmit PPDUs on unlicensed spectrum, which can be a portion of the spectrum including bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and 60 GHz band. Some examples of AP 102 and STA 104 described herein can also communicate in other bands that can support both licensed and unlicensed communication. For example, AP 102 or STA 104, or both, may also be able to communicate on licensed operating bands, where multiple operators may have corresponding licenses to operate in the same or overlapping frequency ranges. Such licensed operating frequency bands may be specified or associated with frequency ranges mapped to or associated with FR1 (410MHz to 7.125GHz), FR2 (24.25GHz to 52.6GHz), FR3 (7.125GHz to 24.25GHz), FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz), and FR5 (114.25GHz to 300GHz).

[0040] Each of these frequency bands can include multiple subbands and frequency channels (also referred to as subchannels). For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn standards can be transmitted on one or more of the 2.4 GHz, 5 GHz, or 6 GHz frequency bands, each of which is divided into multiple 20 MHz channels. Therefore, these PPDUs are transmitted on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs can be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, 240 MHz, 320 MHz, 480 MHz, or 640 MHz by bonding multiple 20 MHz channels together.

[0041] Overview of multi-link devices A multi-link device (MLD) generally refers to a single device or apparatus comprising two or more station (STA) instances or entities implemented in the physical (PHY) / media access control (MAC) layer and configured to communicate over a separate radio link. In some examples, each MLD may include a single higher-layer entity, such as a MAC service access point (SAP) that can assign MAC protocol data units (MPDUs) for transmission by individual STA instances.

[0042] Figure 2 A block diagram depicts an example multi-link device (MLD) deployment.

[0043] like Figure 2 As shown, Access Point (AP) MLD 202 can communicate with non-AP MLD 204. Each of the AP MLD and non-AP MLD may include at least two STA entities 214 (hereinafter also referred to as "STAs") that can communicate with an associated STA of another MLD. In the AP MLD, the STA may be an AP STA 212 (a STA acting as an AP or simply "AP"). In the non-AP MLD, the STA may be a non-AP STA (a STA not acting as an AP). Also as described above, the MLD may utilize Multi-Link Aggregation (MLA) (which includes packet-level aggregation), thereby enabling the transmission of MPDUs from the same Traffic ID (TID) via two or more radio links.

[0044] Various communication modes can be employed in the implementation of MLD. For example, MLD can communicate in asynchronous or synchronous modes. Asynchronous mode provides flexibility to adapt to channel load, allowing MLD to perform channel access, transmission, and reception of data asynchronously via multiple links. However, if RF leakage exists between channels, synchronous mode may be preferred because synchronous transmission on all links is unaffected by RF leakage.

[0045] In asynchronous mode, the STA / AP can count down on both radio links (e.g., via Random Backoff (RBO)). The start / end of the Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) can occur independently on each radio link. As a result, asynchronous mode can potentially provide latency and aggregation gain. In some cases, relatively complex (and expensive) filters may be required (e.g., in the case of 5GHz+6GHz aggregation).

[0046] In synchronous mode, the STA / AP can also perform backoff countdowns on multiple radio links as part of the channel access procedure. If the first link gains access to the medium through the channel access procedure, multiple links can transmit PPDUs simultaneously. Therefore, this mode may require some limitations to minimize interference within the device.

[0047] Synchronous mode can operate in 5GHz+6GHz aggregation and may require relatively low filter performance while still providing latency and aggregation gain. However, due to the tiling architecture of STA, this latency and aggregation gain may be difficult to achieve.

[0048] Although not shown, the third communication mode may include a basic (e.g., multi-master channel single-link transmission) mode. In basic mode, the STA / AP may also count down on two wireless links. However, transmission may only occur on the wireless link that has gained access to the medium. The other wireless link may be blocked by in-device interference greater than -62 dBm. In this mode, aggregation gain may not be achievable.

[0049] Figure 3 An example multi-link operation (MLO) architecture is depicted. As mentioned above, conventional wireless communication systems typically only support a disconnect-then-establish handover process, requiring the STA to perform the association process while roaming between multiple APs. This approach causes data interruptions and additional latency during the handover process.

[0050] However, aspects of this disclosure support seamless roaming (e.g., establish-then-disconnect handover processes), which avoid data interruption and reduce delays during handover.

[0051] Various aspects of this disclosure may be, for example, in Figure 3 Implemented in the Multi-Link Operation (MLO) architecture illustrated in the figure. Figure 3 The MLO architecture allows non-co-located APs to be attached to a single AP MLD 302. In this way, the AP MLD can be considered as a logical entity that is physically co-located with any of the non-co-located APs in the set 312 attached to the AP MLD.

[0052] Figure 4 A sample call flowchart for a handover initiated by an example station is depicted. This example assumes that a client station (STA) 420 initiates a handover from a source AP (AP1 410-1) to a destination AP (AP2 410-2), both of which are attached to the SMDMLD.

[0053] As illustrated at 402, the STA can initially communicate with AP1 via the first link (link 1). As illustrated at 404, the STA can initiate a handover (HO) and can transmit an HO indication to AP1. As will be described below, the HO indication can be transmitted in a message called a Roaming Advertisement Initiation (RAI) message. Some other type of message (other than the RAI message) referred to by different names may also transmit HO indications or similar signaling that announces the handover or the initiation of seamless roaming.

[0054] Upon receiving a HO instruction, AP1 may transmit a context to AP2 so that AP2 is ready to provide services to the STA. As mentioned above, the context may include administrative and data context. In some cases, AP1 may, for example, use a response to the HO instruction to indicate that a context transmission has been performed, which may also indicate that a second link (Link 2) is enabled. As illustrated at 406, after receiving the response, the STA may communicate with AP2 via Link 2. As illustrated at 408, the STA may disable Link 1 with AP1.

[0055] Figure 5 A sample call flowchart illustrating a network-initiated handover is depicted. This example assumes a handover initiated by STA 520 from a source AP1 510-1 to a destination AP2 510-2, where both source AP1 and destination AP2 are attached to the SMD MLD. Signaling is similar to... Figure 4 The signaling shown differs in that the source AP1 acts as the HO initiator. In other words, AP1 sends the HO instruction to the STA, and the STA sends the corresponding response. Network-initiated handover can be beneficial, for example, because the AP may have considered information that the STA may not have, such as the overall network load and / or the relative load of one or more potential target APs.

[0056] As illustrated at 502, similar to Figure 4In the scenario illustrated, the STA can initially communicate with AP1 via link 1. As illustrated at 504, AP1 can then initiate a HO (House of Interest) and can send an HO instruction to the STA (e.g., via a RAI message). After sending the HO instruction, AP1 can transmit context to AP2 so that AP2 is ready to service the STA. In this case, when the STA is ready to enable link 2 (e.g., after delegating UL packets to AP1), the STA can signal to AP1 (e.g., via a RAR message). As illustrated at 506, after sending a response, the STA can communicate with AP2 via link 2. As illustrated at 508, the STA can disable link 1 with AP1.

[0057] All aspects related to seamless roaming recommended by the network The various aspects of this disclosure provide mechanisms that enable network entities to instruct wireless stations on recommendations for seamless roaming.

[0058] In the handover scenario described herein, both the source AP and the destination AP can be attached to a Single Mobile Domain (SMD) entity (such as an SMD AP MLD). In this context, an SMD entity typically refers to a logical entity comprising more than one non-coordinated AP device, enabling non-AP devices associated with the SMD entity to roam seamlessly between AP devices attached to the SMD entity (e.g., without re-associating). In this context, an AP device (attached to an SMD entity) can be an AP MLD comprising one or more attached APs or a single-link AP. A non-AP device can be a non-AP MLD comprising one or more attached non-AP STAs or a single-link non-AP STA.

[0059] The source AP and the target AP can be attached to different (normal or non-SMD) AP MLDs. An SMD AP MLD can be similar to a normal AP MLD because it can control multiple APs attached to it. However, one difference is that APs attached to an SMD AP MLD can be located in different positions (non-coordinated), while APs attached to the same normal AP MLD are usually located in the same position (coordinated).

[0060] An example of an SMD entity is an SMD MLD, which can refer to a logical entity that may reside on a serving AP MLD, such as a network controller or a specific client. In the latter case, the physical AP providing (activation / operation) SMD MLD functionality may differ for different clients, and therefore the physical location of the SMD MLD may also differ for different clients. Furthermore, some operations or functionalities may be split between the AP MLD and the SMD MLD. For example, functionalities related to association context, block acknowledgment (BA), and / or security may reside on a specific client's SMD MLD, while other functionalities related to link ID may be based on the serving AP MLD. This contrasts with a typical station (e.g., a legacy client) such as an 802.11 be-compliant non-AP MLD, where such functionalities may all reside on the physical AP MLD serving that non-AP MLD. While this disclosure refers to the entity providing the functionality described above as an SMD MLD, entities providing the same or similar functionalities may be referred to by other names.

[0061] Figure 6 An example SMD MLD hierarchy 600 is depicted. As illustrated, an SMD MLD may have a collection of affiliated AP devices 610 and 620. For example, each affiliated AP device may be a non-MLD AP (e.g., a standalone single AP 620), or it may be an AP MLD 610 with its own affiliated AP. An AP affiliated to an AP MLD may be considered (e.g., indirectly) affiliated to an SMD MLD, which in turn is affiliated to the SMD MLD.

[0062] As mentioned above, seamless roaming is a potentially useful feature in ultra-high reliability (UHR) networks, enabling client devices to move seamlessly from one serving AP to another without re-associating. Seamless roaming may involve the UHR AP providing information related to a single mobility domain (SMD) entity (e.g., an SMD AP MLD), advertising candidate APs for clients to choose from for roaming, and possibly transferring context between APs. Such roaming / handover / transition can be initiated by a non-AP MLD, or the network can recommend to a non-AP MLD different sets of serving APs to move to (e.g., co-located or non-co-located).

[0063] A set of APs can be identified as suitable candidates for handover because the SMD AP MLD has a global view of the Extended Service Set (ESS). For example, the SMD AP MLD can know the load at each affiliated AP MLD, the number of associated clients, etc., which helps identify the set of one or more AP MLDs that are best suited for non-AP MLDs to roam to. Therefore, AP devices (e.g., AP MLDs) that are affiliated with the SMD MLD (e.g., and currently serve non-AP MLDs) may be well-suited to provide a list of recommended AP MLDs that non-AP MLDs can roam to.

[0064] Various aspects of this disclosure provide techniques for recommending the transition of a non-AP MLD from one set of serving APs to a different set of APs. This disclosure provides mechanisms (e.g., container / signaling frameworks) for providing such recommendations. In some aspects, such recommendations may be based on an Extended Basic Service Set (BSS) Transformation Management (BTM) framework or a Multi-Link (ML) Reconfiguration framework, or a combination of both. In some aspects, such recommendations may be based on a request from the non-AP MLD or may be unsolicited.

[0065] The techniques proposed in this article for seamless roaming recommendations can be referenced. Figure 7 For an understanding, refer to the example call flowchart 700. In some respects, Figure 7 The collection of AP devices and STAs described in the text can be about Figure 1 Examples of AP102 (e.g., AP STA) and STA 104 depicted and described.

[0066] As illustrated, STA device (e.g., non-AP MLD) 720 may initially be served by a first set of serving AP devices 710-1.

[0067] As illustrated at 704, the first set of serving AP devices may send a frame indicating recommended AP devices attached to the SMD entity (e.g., a list of recommended target AP devices). In some aspects, this frame may be a BTM request or an ML reconfiguration request. As illustrated at 702, in some cases, the STA device may optionally request a recommendation for the set of target AP devices.

[0068] As illustrated at 706, the STA can select a target set of AP devices based on this recommendation. For example, in some aspects, the STA can perform an ML reconfiguration procedure to add / remove APs from the target AP list to match the recommended set. In some aspects, the STA can perform a deletion operation before the addition operation. In some aspects, the deleted APs can include any AP that is not part of the recommended set. In some aspects, the added APs can be a subset of the recommended set.

[0069] As illustrated at 708, a STA can switch / hand over / roam from a serving set of AP devices to a selected set of target AP devices. As illustrated at 712, a STA can communicate with the target set of AP devices after switching. Although not shown, such a switch may involve the above references. Figure 4 or Figure 5 One or more operations described (e.g., HO instructions and context transfers).

[0070] In some systems, such as non-AP STAs (e.g., STA 720), a request can be made for more information about other candidate APs. This can be done, for example, through a query or subscription.

[0071] For example, a non-AP STA can query before or after an AP STA has received a recommendation to switch to the target AP (actively). The query and corresponding response, including the requested information, can be any suitable type of query and response, such as a multi-link probe request / response or an Access Network Query Protocol (ANQP) query / response. In some systems, the query and / or response may use protected frames (e.g., using encryption).

[0072] In some systems, non-AP STAs can subscribe to (e.g., by expressing their interest) information related to a subset of candidate APs (the subscribed candidate set). In some cases, the serving AP (MLD) can provide updates related to the parameters of the subscribed candidate APs in an unsolicited manner. In some cases, the serving AP can restrict its recommendations to APs within the subscribed candidate set.

[0073] In some cases, a non-AP MLD / STA may only be serviceable by a single AP MLD (e.g., all affiliated APs belong to the same set of devices). In such cases, the ML reconfiguration process (e.g., defined by certain wireless communication standards) can be adapted to this recommendation for the target AP device (e.g., by adding exceptions and / or extensions).

[0074] In some respects, an AP attached to a serving AP can send a link reconfiguration notification frame containing a reconfiguration ML IE to a non-AP STA attached to a non-AP MLD. The MLD MAC address field may be present in the element and may carry the MLD MAC address of the target AP MLD.

[0075] In some aspects, the reconfiguration ML IE may not include any per-STA profiles, which could indicate that all associated APs of the target AP MLD are recommended. In other aspects, the reconfiguration ML IE may include per-STA profiles, each corresponding to a recommended associated AP of the target AP MLD. In either case, the recommended set can be all associated APs of the target AP MLD.

[0076] In some cases, a non-AP MLD can be served by more than one AP MLD (e.g., attached APs may belong to a non-coordinated set). In such cases, an AP attached to one of the serving AP MLDs can send a link reconfiguration notification frame containing one or more reconfiguration ML IEs to a non-AP STA attached to a non-AP MLD. An MLD MAC address field may be present in the element and may carry the MLD MAC address of the corresponding target AP MLD. Similar to the case where a non-AP MLD is served by a single AP MLD, the reconfiguration ML IE may or may not include any per-STA profile.

[0077] In scenarios where a non-AP MLD (e.g., capable of being served by only one AP MLD, e.g., all associated APs belong to the same set of juxtapositions) can send a BTM request frame to a non-AP STA attached to a non-AP MLD. The BTM request frame contains one or more adjacent reporting elements, each carrying a basic ML IE.

[0078] The basic ML IE may or may not include a per-STA profile (e.g., based on recommendations regarding a specific affiliated AP). In some aspects, the MLD MAC address field of the basic ML IE may carry the MAC address of the SMD MLD. In some aspects, the MLD MAC address field of the basic ML IE may carry the MAC address of the target AP MLD along with one or more other fields indicating that the target AP MLD belongs to the same SMD MLD.

[0079] For scenarios where a non-AP MLD can be served by more than one AP MLD (i.e., the affiliated AP can belong to a non-co-located set), the BTM request frame (e.g., defined by some wireless communication standards) can be adapted for this recommendation of the target AP device (e.g., by adding exceptions and / or extensions).

[0080] In some respects, an AP attached to one of the serving AP MLDs can send a BTM request frame to a non-AP STA attached to a non-AP MLD. The BTM request frame may contain one or more adjacent reporting elements.

[0081] In some aspects, each adjacent reporting element may include a single basic ML IE, where the MLD MAC address field carries the MAC address of the SMD MLD and one or more per-STA profiles, each per-STA profile corresponding to one or more recommended affiliated APs. For each recommended affiliated AP, the field may identify the set of juxtapositions to which the AP is affiliated (e.g., APMLD ID or AP MLD MAC address).

[0082] In some respects, each neighbor reporting element may include a basic ML IE for each AP MLD for which its associated AP is recommended. For each basic ML IE, the MLD MAC address field may carry the MAC address of the AP MLD and one or more per-STA profiles, each per-STA profile corresponding to one or more recommended associated APs of that AP MLD.

[0083] Certain aspects of this disclosure provide several recommended options for carrying multiple (target) AP MLDs for seamless roaming.

[0084] In some respects, new variations of the ML IE or per-MLD profile can be included in existing variations of the ML IE (e.g., reconfigured ML IE). This allows for the inclusion of information at various levels regarding the recommended AP MLD. For example, only the identifier can be included by including only the MLD control field in each per-MLD profile. Alternatively, common information at the MLD level can be provided by including the MLD information field. Similarly, additional information (e.g., information about affiliated APs) can be provided by including the MLD profile field.

[0085] In some respects, the AP MLD ID list may be included in the common information field or link information field of existing variants of the ML IE (e.g., reconfiguration or basic). In such respects, only the identifier of the recommended AP MLD is provided.

[0086] In some respects, each recommended AP MLD may include a separate basic ML IE or a reconfigured ML IE. In such respects, for example, a common information field of the basic ML IE or the reconfigured ML IE may allow the inclusion of an AP MLD ID subfield, which identifies the AP MLD whose information is provided. In such respects, information at various levels regarding the recommended AP MLD can be provided.

[0087] In some respects, recommendations for AP devices (e.g., AP MLDs) may be carried in link reconfiguration notification frames (e.g., which may be defined in certain wireless communication standards such as 802.11be) that recommend APs attached to the same AP MLD. In other respects, recommendations for AP devices may be carried in probe responses or (re)association responses as a preemptive list of candidate APs not belonging to an AP MLD.

[0088] According to certain aspects of this disclosure, one or more recommended AP devices may not be attached to an SMD entity. For example, one or more recommended AP devices may be attached to different SMD entities. In such cases, re-association may be required when performing a transition / handover / roaming. In other words, the techniques disclosed herein are applicable to scenarios involving non-seamless roaming, where re-association may be necessary.

[0089] Depending on certain aspects, the serving AP MLD may transmit the contents of a complete profile essentially equivalent to at least one of the indicated / recommended AP devices, rather than providing limited information about the target AP MLD. In some cases, inheritance may be used to transmit information about the target AP MLD set. For example, for a link reconfiguration notification frame (sent as the first frame), inheritance could be about the first per-STA / per-MLD profile.

[0090] Using inherent properties in this way can be beneficial when the serving AP MLD provides complete information about one or more target AP MLDs, as the size of the information could become excessive.

[0091] The concept of inherentity can be leveraged by the following trend: there exists a large amount of common replication information across all APs in an AP MLD, and some different (or incremental) information specific to certain APs within that AP MLD. (See above reference.) Figure 8 As described, common (replicated) information can be transmitted in the actual frame, while incremental information can be included. Every STA In the configuration file.

[0092] In the case of the link reconfiguration notification frame (first frame), inheritance can be applied regarding the first per-STA profile / per-MLD profile. In this way, the serving AP MLD can identify which is the per-STA profile / per-MLD profile, which helps to minimize the size of the total information. Subsequent per-STA profiles can then carry only incremental information.

[0093] Figure 8A flowchart illustrating an example process 800 that can be executed at a first wireless node according to certain aspects of this disclosure is shown. Operation of process 800 may be implemented by a wireless AP or wireless STA, or a component thereof, as described herein. For example, process 800 may be implemented by a wireless communication device (such as reference 1) operating as a wireless AP or wireless STA, or operating within such a wireless AP or wireless STA. Figure 10 The described wireless communication device 800 performs the operation. In some examples, the process 800 may be performed by a wireless AP or a wireless STA (such as reference 800). Figure 1 This is performed by either a wireless AP (102) or a wireless STA (104).

[0094] Process 800 begins at step 805, where an association with a single mobility domain (SMD) entity is established.

[0095] Then, process 800 proceeds to step 810, in which communication is made with a first set of one or more service access point (AP) devices attached to the SMD entity.

[0096] Then, process 800 proceeds to step 815, where at least a first frame indicating one or more AP devices attached to the SMD entity is obtained.

[0097] Then, process 800 proceeds to step 820, where, after obtaining at least the first frame, a second set of one or more target AP devices is selected.

[0098] Then, process 800 proceeds to step 825, where the transition from the first set to the second set occurs.

[0099] In some respects, the transformation is performed in a manner independent of the re-association with the SMD entity.

[0100] In some respects, process 800 also includes outputting a request for the first frame, which is obtained after the output request.

[0101] In some respects, the option includes at least one of the following: deleting one or more AP devices from the target AP device list; or adding one or more AP devices to the target AP device list.

[0102] In some respects, the added one or more AP devices comprise a subset of the one or more AP devices indicated by the frame.

[0103] In some respects, the first frame includes a link reconfiguration notification frame.

[0104] In some respects, the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

[0105] In some respects, the first frame includes a Basic Services Set (BSS) Transformation Management (BTM) request frame.

[0106] In some respects, the BTM request frame delivers at least one adjacent report information element (IE).

[0107] In some respects, the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with an SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); at least one target AP MLD belonging to an SMD entity; an identifier (ID) of at least one target AP MLD; or one or more station (STA) profiles corresponding to one or more AP devices indicated by the frame.

[0108] In some respects, the first frame delivers a STA profile for at least one of the indicated AP devices.

[0109] In some respects, the first frame includes: at least one of a first one or more fields or a first one or more elements that transmit information common to the plurality of indicated AP devices; and at least one of a second one or more fields or a second one or more elements that transmit information specific to one of the indicated AP devices.

[0110] In some respects, the first one or more fields and the first one or more elements are carried in the first STA configuration file; and the second one or more fields and the second one or more elements are carried in the second STA configuration file.

[0111] In some respects, the first STA profile appears in the first frame before the second STA profile.

[0112] In some respects, process 800 also includes outputting a request for information about one or more AP devices among the one or more AP devices indicated in the first frame.

[0113] In some respects, process 800 also includes obtaining information after an output request.

[0114] In some respects, process 800 also includes using this information when selecting a second set of one or more target AP devices.

[0115] In one respect, process 800 or any aspect thereof may be made possible by means of a device (such as...) Figure 10 The communication device 1000 performs the operation, and the device includes various components capable of operating, being configured, or being adapted to perform the process 800. The communication device 1000 is described in more detail below.

[0116] It should be noted that, Figure 8 This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are also possible.

[0117] Figure 9 A flowchart illustrating an example process 900 that can be executed at a second wireless node according to certain aspects of this disclosure is shown. Operation of process 900 may be implemented by a wireless AP or wireless STA or a component thereof as described herein. For example, process 900 may be implemented by a wireless communication device (such as reference _____) operating as a wireless AP or wireless STA or within such a wireless AP or wireless STA. Figure 10 The described wireless communication device 800 performs the operation. In some examples, the process 800 may be performed by a wireless AP or a wireless STA (such as reference 800). Figure 1 This is performed by either a wireless AP (102) or a wireless STA (104).

[0118] Process 900 begins at step 905, wherein at least a first frame is generated indicating one or more serving AP devices attached to a single mobile domain (SMD) entity, wherein a second radio node is also attached to the SMD entity.

[0119] Then, process 900 proceeds to step 910, in which at least the first frame is output to the first wireless node attached to the SMD entity.

[0120] Then, process 900 proceeds to step 915, where, after outputting the first frame, it participates in the process of transferring the first wireless node from a first set of one or more serving AP devices to a second set of one or more serving AP devices.

[0121] In some respects, process 900 also includes obtaining a request for the first frame, which is output after the request is obtained.

[0122] In some respects, the first frame includes a link reconfiguration notification frame.

[0123] In some respects, the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

[0124] In some respects, the first frame includes a Basic Services Set (BSS) Transformation Management (BTM) request frame.

[0125] In some respects, the BTM request frame delivers at least one adjacent report information element (IE).

[0126] In some respects, the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with an SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); at least one target AP MLD belonging to an SMD entity; an identifier (ID) of at least one target AP MLD; or one or more station (STA) profiles corresponding to one or more AP devices indicated by the frame.

[0127] In some respects, the first frame delivers a STA profile for at least one of the indicated AP devices.

[0128] In some respects, the first frame includes: at least one of a first one or more fields or a first one or more elements that transmit information common to the plurality of indicated AP devices; and at least one of a second one or more fields or a second one or more elements that transmit information specific to one of the indicated AP devices.

[0129] In some respects, the first one or more fields and the first one or more elements are carried in the first STA configuration file; and the second one or more fields and the second one or more elements are carried in the second STA configuration file.

[0130] In some respects, the first STA profile appears in the first frame before the second STA profile.

[0131] In some respects, the one or more serving AP devices indicated in the first frame include at least one single AP MLD attached to a set of co-located APs.

[0132] In some respects, the one or more serving AP devices indicated in the first frame include at least two AP MLDs attached to a set of non-coordinated APs.

[0133] In some respects, process 900 also includes a request for information regarding one or more AP devices among the one or more AP devices indicated in the first frame.

[0134] In some respects, process 900 also includes outputting information after a request is received.

[0135] In one respect, process 900 or any aspect thereof may be made possible by means of a device (such as...) Figure 10 The communication device 1000 performs the operation, and the device includes various components capable of operating, being configured, or being adapted to perform the process 900. The communication device 1000 is described in more detail below.

[0136] It should be noted that, Figure 9This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are also possible.

[0137] Figure 10 A block diagram of an example wireless communication device 1000 supporting the techniques disclosed herein is shown, such as enabling network entities to instruct wireless stations on recommended techniques for seamless roaming. In some examples, the wireless communication device 1000 is configured to perform reference... Figure 8 The process described is 800. In some examples, the wireless communication device 1000 is configured to perform the reference... Figure 9 The process described is 900. Wireless communication device 1000 may include one or more chips, SoCs, chipsets, packages, components, or devices that individually or collectively constitute or include a processing system. The processing system may interface with other components of wireless communication device 1000 and typically processes information (such as inputs or signals) received from and outputs information (such as outputs or signals) to such other components. In some aspects, an example chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, enabling device 1000 to transmit information output from the chip. In such an example, the second interface may refer to an interface between the chip's processing system and a receiving component, enabling device 1000 to receive information, which is then passed to the processing system. In some such examples, the first interface may also, for example, acquire information from the transmitting component, and the second interface may also, for example, output information to the receiving component.

[0138] The processing system of the wireless communication device 1000 includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as a central processing unit (CPU), graphics processing unit (GPU), or digital signal processor (DSP)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuitry, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories may be coupled to one or more processors and may store processor-executable code, individually or collectively, which, when executed by one or more processors, configures one or more processors to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without software configuration. The processing system may also include or be coupled to one or more modems (such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem). In some embodiments, one or more processors of the processing system include or implement one or more modems. The processing system may also include or be coupled to multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers.

[0139] In some examples, the wireless communication device 1000 may be configured to be used for or configured to be used in an AP or STA (such as reference). Figure 1This is used in the described AP 102 or STA 104. In some other examples, the wireless communication device 1000 may be an AP or STA that includes such a processing system as well as other components including multiple antennas. The wireless communication device 1000 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 1000 may be configured to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more wireless communication protocol standards in the IEEE 802.11 series of wireless communication protocol standards. In some other examples, the wireless communication device 1000 may be configured to transmit and receive signals and communications conforming to one or more 3GPP specifications, including specifications for 5G NR or 6G. In some examples, the wireless communication device 1000 also includes one or more application processors or may be coupled to such one or more application processors, which may be further coupled to one or more other memories. In some examples, the wireless communication device 1000 also includes at least one external network interface coupled to a processing system, which enables communication with the core network or backhaul network implementing the wireless communication device 1000 to obtain access to external networks, including the Internet.

[0140] Wireless communication device 1000 includes an establishment component 1002, a communication component 1004, an acquisition component 1006, a selection component 1008, a conversion component 1010, an output component 1012, a usage component 1014, a generation component 1016, and a participation component 1018. A portion of one or more of components 1002, 1004, 1006, 1008, 1010, 1012, 1014, 1016, and 1018 may be implemented at least partially in hardware or firmware. For example, the acquisition component 1006 may be implemented at least partially by a processor or a modem. In some examples, portions of one or more of components 1002, 1004, 1006, 1008, 1010, 1012, 1014, 1016, and 1018 may be implemented at least partially by a processor and software in the form of processor-executable code stored in memory.

[0141] In some implementations, the processor may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which may be passed to, for example, other systems or components of the wireless communication device 1000). For example, the processing system of the wireless communication device 1000 may refer to a system that includes various other components or sub-components of the wireless communication device 1000, such as a processor, transceiver, or communication manager, or other components or combinations of components of the wireless communication device 1000. The processing system of the wireless communication device 1000 may interface with other components of the wireless communication device 1000 and may process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of the wireless communication device 1000 may include a processing system, a first interface for outputting information, and a second interface for receiving information. In some implementations, the first interface may refer to the interface between the processing system of the chip or modem and a transmitter, enabling the wireless communication device 1000 to transmit information output from the chip or modem. In some specific implementations, the second interface may refer to the interface between the processing system of the chip or modem and the receiver, enabling the wireless communication device 1000 to receive information or signal input, and the information to be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0142] Example Terms Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication at a first wireless node, the method comprising: establishing an association with a single mobile domain (SMD) entity; communicating with a first set of one or more serving access point (AP) devices attached to the SMD entity; obtaining at least a first frame indicating the one or more AP devices attached to the SMD entity; after obtaining the at least first frame, selecting a second set of one or more target AP devices; and switching from the first set to the second set.

[0143] Clause 2: The method described in Clause 1, wherein the transformation is performed independently of the reassociation with the SMD entity.

[0144] Clause 3: The method according to any one of Clauses 1 to 2 further includes outputting a request for the first frame, wherein the first frame is obtained after the request is output.

[0145] Clause 4: The method according to any one of Clauses 1 to 3, wherein the selection includes at least one of the following: deleting one or more AP devices from the target AP device list; or adding one or more AP devices to the target AP device list.

[0146] Clause 5: The method described in Clause 4, wherein the added one or more AP devices comprise a subset of the one or more AP devices indicated by the frame.

[0147] Clause 6: The method according to any one of Clauses 1 to 5, wherein the first frame includes a link reconfiguration notification frame.

[0148] Clause 7: The method described in Clause 6, wherein the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

[0149] Clause 8: The method according to any one of Clauses 1 to 7, wherein the first frame includes a Basic Service Set (BSS) Transformation Management (BTM) request frame.

[0150] Clause 9: The method described in Clause 8, wherein the BTM request frame transmits at least one Adjacent Reporting Information Element (IE).

[0151] Clause 10: The method according to any one of Clauses 1 to 9, wherein the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with the SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); the at least one target AP MLD belonging to the SMD entity; an identifier (ID) of the at least one target AP MLD; or one or more station (STA) profiles corresponding to the one or more AP devices indicated by the frame.

[0152] Clause 11: The method according to any one of Clauses 1 to 10, wherein the first frame transmits a STA profile for at least one of the indicated AP devices.

[0153] Clause 12: The method according to Clause 11, wherein the first frame includes: at least one of a first one or more fields or a first one or more elements that transmit information common to a plurality of indicated AP devices; and at least one of a second one or more fields or a second one or more elements that transmit information specific to one of the indicated AP devices.

[0154] Clause 13: The method according to Clause 12, wherein: the first one or more fields and the first one or more elements are carried in a first STA configuration file; and the second one or more fields and the second one or more elements are carried in a second STA configuration file.

[0155] Clause 14: The method according to Clause 13, wherein: the first STA profile appears in the first frame before the second STA profile.

[0156] Clause 15: The method according to any one of Clauses 1 to 14, the method further comprising: outputting a request for information regarding one or more AP devices among the one or more AP devices indicated in the first frame; obtaining the information after outputting the request; and using the information when selecting a second set of one or more target AP devices.

[0157] Clause 16: A method for wireless communication at a second wireless node, the method comprising: generating at least a first frame indicating one or more serving AP devices attached to a single mobile domain (SMD) entity, wherein the second wireless node is also attached to the SMD entity; outputting the at least first frame to a first wireless node attached to the SMD entity; and, after outputting the first frame, participating in a process of transitioning the first wireless node from a first set of one or more serving AP devices to a second set of one or more serving AP devices.

[0158] Clause 17: The method according to Clause 16 further includes obtaining a request for the first frame, wherein the first frame is output after the request is obtained.

[0159] Clause 18: The method according to any one of Clauses 16 to 17, wherein the first frame includes a link reconfiguration notification frame.

[0160] Clause 19: The method described in Clause 18, wherein the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

[0161] Clause 20: The method according to any one of Clauses 16 to 19, wherein the first frame includes a Basic Service Set (BSS) Transformation Management (BTM) request frame.

[0162] Clause 21: The method according to Clause 20, wherein the BTM request frame transmits at least one Adjacent Reporting Information Element (IE).

[0163] Clause 22: The method according to any one of Clauses 16 to 21, wherein the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with the SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); the at least one target AP MLD belonging to the SMD entity; an identifier (ID) of the at least one target AP MLD; or one or more station (STA) profiles corresponding to the one or more AP devices indicated by the frame.

[0164] Clause 23: The method according to any one of Clauses 16 to 22, wherein the first frame delivers a STA profile for at least one of the indicated AP devices.

[0165] Clause 24: The method according to Clause 23, wherein the first frame includes: at least one of a first one or more fields or a first one or more elements that transmit information common to a plurality of indicated AP devices; and at least one of a second one or more fields or a second one or more elements that transmit information specific to one of the indicated AP devices.

[0166] Clause 25: The method according to Clause 24, wherein: the first one or more fields and the first one or more elements are carried in a first STA configuration file; and the second one or more fields and the second one or more elements are carried in a second STA configuration file.

[0167] Clause 26: The method according to Clause 25, wherein: the first STA profile appears in the first frame before the second STA profile.

[0168] Clause 27: The method according to any one of Clauses 16 to 26, wherein the one or more serving AP devices indicated in the first frame include at least one single AP MLD attached to a set of co-located APs.

[0169] Clause 28: The method according to any one of Clauses 16 to 27, wherein the one or more serving AP devices indicated in the first frame include at least two AP MLDs attached to a set of non-coordinated APs.

[0170] Clause 29: The method according to any one of Clauses 16 to 28, the method further comprising: obtaining a request for information regarding one or more AP devices among the one or more AP devices indicated in the first frame; and outputting the information after obtaining the request.

[0171] Clause 30: An apparatus comprising: at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 1 to 29.

[0172] Clause 31: An apparatus comprising components for performing the method according to any one of Clauses 1 to 29.

[0173] Clause 32: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of the apparatus, cause the apparatus to perform the method according to any one of Clauses 1 to 29.

[0174] Clause 33: A computer program product embodied on a computer-readable storage medium, said computer-readable storage medium including code for performing the method according to any one of Clauses 1 to 29.

[0175] Clause 34: A wireless station comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the device to perform a method according to any one of Clauses 1 to 15, wherein the at least one transceiver is configured to receive the first frame.

[0176] Clause 35: An access point (AP) comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 16 to 29, wherein the at least one transceiver is configured to transmit the first frame.

[0177] Additional considerations As used herein, the term "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, estimation, investigation, searching (such as by searching in a table, database, or other data structure), reasoning, probing, or measurement, among other possibilities. Furthermore, "determine" can include receiving (such as receiving information), accessing (such as accessing data stored in memory), or sending (such as sending information), among other possibilities. Additionally, "determine" can include parsing, selecting, obtaining, choosing, building, and other similar actions.

[0178] As used herein, the phrase “at least one of” or “one or more of” refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc. As used herein, “or” is intended to be interpreted as inclusive unless otherwise explicitly stated. For example, “a or b” could include only a, only b, or a combination of a and b. Furthermore, as used herein, the phrase referring to “one” element means one or more of such elements that act individually or collectively to perform the stated function. Additionally, “set” refers to one or more items, and “subset” refers to less than the entire set, but not empty.

[0179] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0180] Components for establishing, communicating, acquiring, selecting, transforming, outputting, using, generating, participating, deleting, and adding may include one or more processors, as referenced above. Figure 10 One or more of the processors described.

[0181] As used herein, unless otherwise expressly indicated, “based on” is intended to be interpreted in an inclusive sense. For example, unless otherwise explicitly indicated, “based on” may be used interchangeably with “at least partially based on,” “associated with,” “associated with,” or “according to.” Specifically, unless the phrase in the context means “based on only one” or an equivalent, whether it is “based on one” or “at least partially based on one”, it may be based solely on “one” or based on a combination of “one” and one or more other factors, conditions, or information.

[0182] The various exemplary components, logic units, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the examples disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of its functionality and exemplified in the various exemplary components, blocks, modules, circuits, and processes described above. Whether this functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0183] Various modifications to the examples described herein will be apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the examples shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0184] Furthermore, the various features described in the context of individual examples in this specification may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple examples. Thus, although features may be described above as functioning in a particular combination, and even initially claimed in this way, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may involve sub-combinations or variations of sub-combinations.

[0185] Similarly, although operations are depicted in a specific order in the diagrams, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the accompanying figures may schematically depict one or more example processes in the form of flowcharts or flow diagrams. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples described above should not be construed as requiring such separation in all examples, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. An apparatus for wireless communication, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the device to: Establish association with Single Mobility Domain (SMD) entities; Communicate with a first set of one or more service access point (AP) devices attached to the SMD entity; Obtain at least a first frame indicating one or more AP devices attached to the SMD entity; After obtaining the at least first frame, a second set of one or more target AP devices is selected; as well as Transform from the first set to the second set.

2. The apparatus of claim 1, wherein the transformation is performed independently of reassociation with the SMD entity.

3. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Output a request for the first frame, wherein the first frame is obtained after the request is output.

4. The apparatus of claim 1, wherein, for selection, the one or more processors are further configured to cause the apparatus to perform at least one of the following operations: Remove one or more AP devices from the target AP device list; or Add one or more AP devices to the target AP device list.

5. The apparatus of claim 4, wherein the added one or more AP devices comprise a subset of the one or more AP devices indicated by the frame.

6. The apparatus of claim 1, wherein the first frame includes a link reconfiguration notification frame.

7. The apparatus of claim 6, wherein the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

8. The apparatus of claim 1, wherein the first frame comprises a Basic Service Set (BSS) Transformation Management (BTM) request frame.

9. The apparatus of claim 8, wherein the BTM request frame transmits at least one neighbor report information element (IE).

10. The apparatus of claim 1, wherein the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with the SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); the at least one target AP MLD belonging to the SMD entity; an identifier (ID) of the at least one target AP MLD; or one or more station (STA) profiles corresponding to the one or more AP devices indicated by the frame.

11. The apparatus of claim 1, wherein the first frame transmits a STA profile for at least one of the indicated AP devices.

12. The apparatus of claim 11, wherein the first frame comprises: The first one or more fields or the first one or more elements that provide common information to the multiple indicated AP devices are transmitted. and at least one of a second or more fields or a second or more elements that transmit information specific to one of the indicated AP devices.

13. The apparatus of claim 12, wherein the first one or more fields and the first one or more elements are carried in a first STA configuration file; and the second one or more fields and the second one or more elements are carried in a second STA configuration file.

14. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Output a request for information about one or more of the one or more AP devices indicated in the first frame; The information is obtained after the request is output; as well as The information is used when selecting the second set of one or more target AP devices.

15. The apparatus of claim 1, further comprising at least one transceiver configured to receive the first frame, wherein the apparatus is configured as a wireless station.

16. An apparatus for wireless communication, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the device to: Generate at least a first frame indicating one or more serving AP devices attached to a single mobility domain (SMD) entity, wherein said devices are also attached to the SMD entity; The first frame is output to a wireless node attached to the SMD entity; as well as After outputting the first frame, participate in the process of transferring the wireless node from a first set of one or more serving AP devices to a second set of one or more serving AP devices.

17. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: A request is received for the first frame, wherein the first frame is output after the request is received.

18. The apparatus of claim 16, wherein the first frame includes a link reconfiguration notification frame.

19. The apparatus of claim 18, wherein the link reconfiguration notification frame delivers at least one multi-link (ML) information element (IE).

20. The apparatus of claim 16, wherein the first frame comprises a Basic Service Set (BSS) Transformation Management (BTM) request frame.

21. The apparatus of claim 20, wherein the BTM request frame transmits at least one adjacent report information element (IE).

22. The apparatus of claim 16, wherein the first frame includes one or more fields indicating at least one of the following: a media access control (MAC) address associated with the SMD entity; at least one MAC address associated with at least one target AP multilink device (MLD); the at least one target AP MLD belonging to the SMD entity; an identifier (ID) of the at least one target AP MLD; or one or more station (STA) profiles corresponding to the one or more AP devices indicated by the frame.

23. The apparatus of claim 16, wherein the first frame transmits a STA profile for at least one of the indicated AP devices.

24. The apparatus according to claim 23, wherein: The first frame includes: at least one of a first one or more fields or a first one or more elements that transmit information common to a plurality of indicated AP devices; and at least one of a second one or more fields or a second one or more elements that transmit information specific to one of the indicated AP devices; The first one or more fields and the first one or more elements are carried in the first STA configuration file; The second or more fields and the second or more elements are carried in the second STA configuration file; and The first STA profile appears in the first frame before the second STA profile.

25. The apparatus of claim 16, wherein the one or more serving AP devices indicated in the first frame include at least one single AP MLD attached to a set of co-located APs.

26. The apparatus of claim 16, wherein the one or more serving AP devices indicated in the first frame comprise at least two AP MLDs attached to a set of non-coordinated APs.

27. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: A request to obtain information regarding one or more AP devices among the one or more AP devices indicated in the first frame; and The information is output after the request is received.

28. The apparatus of claim 16, further comprising at least one transceiver configured to transmit the first frame, wherein the apparatus is configured as an access point (AP).

29. A method for performing wireless communication at a first wireless node, the method comprising: Establish association with Single Mobility Domain (SMD) entities; Communicate with a first set of one or more service access point (AP) devices attached to the SMD entity; Obtain at least a first frame indicating one or more AP devices attached to the SMD entity; After obtaining at least the first frame, a second set of one or more target AP devices is selected; as well as Transform from the first set to the second set.

Images