PRIMARY LINK CHANGE PROCEDURE FOR A MOBILE AP MLD

Methods and apparatuses for facilitating a primary link change procedure for mobile AP MLD are provided. A method for wireless communication performed by an access point (AP) multi-link device (MLD), the AP MLD comprising APs forming a mobile AP MLD, the method comprising: forming links with corresponding stations (STAs) associated with a non-AP MLD; instructing the APs to form a first link and a second link with the corresponding STAs; designating the first link as a primary link and the second link as a non-primary link; determining that the primary link is experiencing degradation; and in response to determining that the primary link is experiencing degradation, effecting a change in the primary link designation, or implementing a channel change procedure to change a channel within the primary link.

TECHNICAL FIELD

This disclosure relates generally to a primary link change procedure for a mobile AP MLD.

BACKGROUND

An AP MLD is typically able to simultaneously transmit and receive over all of its links. However, 802.11be standards define a special AP MLD, namely, NSTR Mobile AP MLD, which can have NSTR link pairs. An NSTR mobile AP MLD has a number of use cases (e.g., Wi-Fi hotspot support, peer to peer operation, etc.). As per the 802.11be standard, an NSTR mobile AP MLD shall designate one link of an NSTR link pair as the primary link. The other link of the NSTR link pair becomes the non-primary link.

IEEE 802.11be standards define primary link and non-primary link for NSTR Mobile AP MLD. The NSTR Mobile AP MLD designates one link of an NSTR link pair as the primary link and other link of the NSTR link pair as the non-primary link. Further, the non-primary link transmissions of a STA affiliated with the non-AP MLD (or the AP affiliated with the NSTR mobile AP MLD) are constrained so that they may happen only if the corresponding STA affiliated with the non-AP MLD (or the corresponding AP affiliated with the NSTR mobile AP MLD) is also initiating a transmission as a TXOP holder with the same start time. This can create some performance issues for the NSTR Mobile AP MLD especially when the primary link performance degrades or the primary link becomes inoperable due to a number of reasons, some of which are explained below, and the Mobile AP MLD may want to change the primary link designation:

Network congestion: It is possible that the network is highly contested in the primary link resulting in large delays in channel capture for the AP1 affiliated with the NSTR Mobile AP MLD or the STA1 affiliated with the non-AP MLD. Due to the transmission constraints on the non-primary link, AP2 and the STA2 will also face a performance degradation despite having a non-congested channel on the non-primary link.

RF environment degradation: It is possible that due to RF degradation, the primary link's condition can become inoperable. As a result, the performance of the non-primary link will also suffer.

Radar operation: As per the DFS operation described in Clause 11.8, an AP is required to move the BSS to a different channel if radar operation is detected on its current channel of operation. The standard mandates that before moving to a new channel, the AP has to perform a check to ensure that the new channel does not have radar operation on it. If radar operation is detected on the new channel, the AP may need to select another channel and continue the check until a channel without radar operation is detected. Depending on the region and the selected channel, such checks can take up to several minutes until a suitable channel is found. During such checks, the primary link may not be available and consequently, the performance on the non-primary link can also get disrupted. Further, the AP affiliated with the NSTR Mobile AP MLD and forming the primary link might have established a restricted TWT schedule with another non-AP MLD. Now if the primary link becomes unavailable, the latency sensitive traffic flow of the non-AP MLD will be interrupted as the non-primary link also becomes inoperable.

Consequently, the Mobile AP MLD may want to change the primary link designation. As a result, a solution to enable the Mobile AP MLD to change the primary link designation is needed.

SUMMARY

Embodiments of the present disclosure provide methods and apparatuses for a primary link change procedure for a mobile AP MLD.

In one embodiment, a multi-link device (MLD) comprises: access points (APs) forming a mobile AP MLD, each AP comprising a transceiver configured to form a link with a corresponding station (STA) associated with a non-AP MLD; and a processor operably coupled to the APs, the processor configured to: instruct the (APs) to form a first link and a second link with the corresponding STAs; designate the first link as a primary link and the second link as a non-primary link; determine that the primary link is experiencing degradation; and in response to determining that the primary link is experiencing degradation, effect a change in the primary link designation, or implement a channel change procedure to change a channel within the primary link.

In another embodiment, a non-AP MLD comprises: STAs, each comprising a transceiver configured to form a primary link and a non-primary link with a corresponding AP of an MLD comprising APs forming a mobile AP MLD; and a processor operably coupled to the STAs, the processor, based on the primary link experiencing degradation, configured to receive via the transceiver an indication from the mobile AP MLD about a change in primary link designation.

In yet another embodiment, a method for wireless communication performed by an AP MLD, the AP MLD comprising APs forming a mobile AP MLD, the method comprising: forming links with corresponding STAs associated with a non-AP MLD; instructing the APs to form a first link and a second link with the corresponding STAs; designating the first link as a primary link and the second link as a non-primary link; determining that the primary link is experiencing degradation; and in response to determining that the primary link is experiencing degradation, effecting a change in the primary link designation, or implementing a channel change procedure to change a channel within the primary link.

Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.

DETAILED DESCRIPTION

The following documents and standards descriptions are hereby incorporated into the present disclosure as if fully set forth herein:

[1] IEEE P802.11be/D1.0—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 throughput (EHT).

[2] 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.

Aspects, features, and advantages of the disclosure are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the disclosure. The disclosure is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. The disclosure is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

FIG.1illustrates an example wireless network100according to various embodiments of the present disclosure. The embodiment of the wireless network100shown inFIG.1is for illustration only. Other embodiments of the wireless network100could be used without departing from the scope of this disclosure.

As shown inFIG.1, the wireless network100includes access points (APs)101and103. The APs101and103communicate with at least one network130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. The AP101provides wireless access to the network130for a plurality of stations (STAs)111-114within a coverage area120of the AP101. The APs101-103may communicate with each other and with the STAs111-114using WI-FI or other WLAN communication techniques. The STAs111-114may communicate with each other using peer-to-peer protocols, such as Tunneled Direct Link Setup (TDLS).

Dotted lines show the approximate extents of the coverage areas120and125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with APs, such as the coverage areas120and125, may have other shapes, including irregular shapes, depending upon the configuration of the APs and variations in the radio environment associated with natural and man-made obstructions.

As described in more detail below, one or more of the APs may include circuitry and/or programming for facilitating a primary link change procedure for mobile AP MLD. AlthoughFIG.1illustrates one example of a wireless network100, various changes may be made toFIG.1. For example, the wireless network100could include any number of APs and any number of STAs in any suitable arrangement. Also, the AP101could communicate directly with any number of STAs and provide those STAs with wireless broadband access to the network130. Similarly, each AP101-103could communicate directly with the network130and provide STAs with direct wireless broadband access to the network130. Further, the APs101and/or103could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

FIG.2Aillustrates an example AP101according to various embodiments of the present disclosure. The embodiment of the AP101illustrated inFIG.2Ais for illustration only, and the AP103ofFIG.1could have the same or similar configuration. However, APs come in a wide variety of configurations, andFIG.2Adoes not limit the scope of this disclosure to any particular implementation of an AP.

The AP101includes multiple antennas204a-204n, multiple RF transceivers209a-209n, transmit (TX) processing circuitry214, and receive (RX) processing circuitry219. The AP101also includes a controller/processor224, a memory229, and a backhaul or network interface234. The RF transceivers209a-209nreceive, from the antennas204a-204n, incoming RF signals, such as signals transmitted by STAs in the network100. The RF transceivers209a-209ndown-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to the RX processing circuitry219, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The RX processing circuitry219transmits the processed baseband signals to the controller/processor224for further processing.

The TX processing circuitry214receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor224. The TX processing circuitry214encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers209a-209nreceive the outgoing processed baseband or IF signals from the TX processing circuitry214and up-converts the baseband or IF signals to RF signals that are transmitted via the antennas204a-204n.

The controller/processor224can include one or more processors or other processing devices that control the overall operation of the AP101. For example, the controller/processor224could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers209a-209n, the RX processing circuitry219, and the TX processing circuitry214in accordance with well-known principles. The controller/processor224could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor224could support beam forming or directional routing operations in which outgoing signals from multiple antennas204a-204nare weighted differently to effectively steer the outgoing signals in a desired direction. The controller/processor224could also support OFDMA operations in which outgoing signals are assigned to different subsets of subcarriers for different recipients (e.g., different STAs111-114). Any of a wide variety of other functions could be supported in the AP101by the controller/processor224including facilitating a primary link change procedure for mobile AP MLD. In some embodiments, the controller/processor224includes at least one microprocessor or microcontroller. The controller/processor224is also capable of executing programs and other processes resident in the memory229, such as an OS. The controller/processor224can move data into or out of the memory229as required by an executing process.

The controller/processor224is also coupled to the backhaul or network interface234. The backhaul or network interface234allows the AP101to communicate with other devices or systems over a backhaul connection or over a network. The interface234could support communications over any suitable wired or wireless connection(s). For example, the interface234could allow the AP101to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface234includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory229is coupled to the controller/processor224. Part of the memory229could include a RAM, and another part of the memory229could include a Flash memory or other ROM.

As described in more detail below, the AP101may include circuitry and/or programming for facilitating a primary link change procedure for mobile AP MLD. AlthoughFIG.2Aillustrates one example of AP101, various changes may be made toFIG.2A. For example, the AP101could include any number of each component shown inFIG.2A. As a particular example, an access point could include a number of interfaces234, and the controller/processor224could support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry214and a single instance of RX processing circuitry219, the AP101could include multiple instances of each (such as one per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, such as in legacy APs. Also, various components inFIG.2Acould be combined, further subdivided, or omitted and additional components could be added according to particular needs.

FIG.2Billustrates an example STA111according to various embodiments of this disclosure. The embodiment of the STA111illustrated inFIG.2Bis for illustration only, and the STAs111-115ofFIG.1could have the same or similar configuration. However, STAs come in a wide variety of configurations, andFIG.2Bdoes not limit the scope of this disclosure to any particular implementation of a STA.

The STA111includes antenna(s)205, a radio frequency (RF) transceiver210, TX processing circuitry215, a microphone220, and receive (RX) processing circuitry225. The STA111also includes a speaker230, a controller/processor240, an input/output (I/O) interface (IF)245, a touchscreen250, a display255, and a memory260. The memory260includes an operating system (OS)261and one or more applications262.

The RF transceiver210receives, from the antenna(s)205, an incoming RF signal transmitted by an AP of the network100. The RF transceiver210down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry225, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry225transmits the processed baseband signal to the speaker230(such as for voice data) or to the controller/processor240for further processing (such as for web browsing data).

The TX processing circuitry215receives analog or digital voice data from the microphone220or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the controller/processor240. The TX processing circuitry215encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver210receives the outgoing processed baseband or IF signal from the TX processing circuitry215and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s)205.

The controller/processor240can include one or more processors and execute the basic OS program261stored in the memory260in order to control the overall operation of the STA111. In one such operation, the controller/processor240controls the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver210, the RX processing circuitry225, and the TX processing circuitry215in accordance with well-known principles. The controller/processor240can also include processing circuitry configured to facilitate a primary link change procedure for mobile AP MLD. In some embodiments, the controller/processor240includes at least one microprocessor or microcontroller.

The controller/processor240is also capable of executing other processes and programs resident in the memory260, such as operations for facilitating a primary link change procedure for mobile AP MLD. The controller/processor240can move data into or out of the memory260as required by an executing process. In some embodiments, the controller/processor240is configured to execute a plurality of applications262, such as applications for detect interference from a neighboring BSS and inform the associated AP of the interference. The controller/processor240can operate the plurality of applications262based on the OS program261or in response to a signal received from an AP. The controller/processor240is also coupled to the I/O interface245, which provides STA111with the ability to connect to other devices such as laptop computers and handheld computers. The I/O interface245is the communication path between these accessories and the controller240.

The controller/processor240is also coupled to the touchscreen250and the display255. The operator of the STA111can use the touchscreen250to enter data into the STA111. The display255may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites. The memory260is coupled to the controller/processor240. Part of the memory260could include a random-access memory (RAM), and another part of the memory260could include a Flash memory or other read-only memory (ROM).

AlthoughFIG.2Billustrates one example of STA111, various changes may be made toFIG.2B. For example, various components inFIG.2Bcould be combined, further subdivided, or omitted and additional components could be added according to particular needs. In particular examples, the STA111may include any number of antenna(s)205for MIMO communication with an AP101. In another example, the STA111may not include voice communication or the controller/processor240could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, whileFIG.2Billustrates the STA111configured as a mobile telephone or smartphone, STAs could be configured to operate as other types of mobile or stationary devices.

FIG.3illustrates an example of NSTR mobile AP MLD operation300according to various embodiments of this disclosure. The embodiment of the example of NSTR mobile AP MLD operation300inFIG.3is for illustration only. Other embodiments of the example of NSTR mobile AP MLD operation300could be used without departing from the scope of this disclosure.

As depicted inFIG.3, two APs namely AP1 and AP2 are affiliated with a NSTR Mobile AP MLD. Further, STA1 and STA2 are two non-AP STAs affiliated with a non-AP MLD. STA1 and STA2 are associated with AP1 and AP2 respectively resulting in two links. The link between AP1 and STA1 is designated as the primary link and the link between AP2 and STA2 is designated as the non-primary link. Further, according to the standard, beacons and probe response frames can be transmitted only on the primary link formed between AP1 and STA1. As the NSTR mobile AP MLD has NSTR link pairs, the STA1 and STA2 affiliated with the non-AP MLD that is associated with the NSTR mobile AP MLD and the AP1 and AP2 affiliated with the NSTR mobile AP MLD have to follow the start time sync and end time alignment constraints defined for NSTR operation. In addition to these constraints, when intending to transmit in the non-primary link, there are some additional constraints:1. STA2 affiliated with the non-AP MLD may initiate a PPDU transmission to its associated AP (i.e., AP2) affiliated with the NSTR mobile AP MLD in the non-primary link only if STA1 affiliated with the same MLD in the primary link is also initiating the PPDU as a TXOP holder with the same start time.2. Further, AP2 affiliated with the NSTR mobile AP MLD may initiate a PPDU transmission to its associated non-AP STA (i.e., STA2) in the non-primary link only if the AP affiliated with the same NSTR mobile AP MLD in the primary link (i.e., AP1) is also initiating the PPDU as a TXOP holder with the same start time.

In the embodiments described herein, two entities can be considered—an initiator and a responder. The initiator (e.g., the Mobile AP MLD) intends to change the designation of the primary link and starts the process with the responder (e.g., the non-AP MLD associated with the Mobile AP MLD).

FIG.4illustrates an example method400for a primary link designation change procedure according to various embodiments of this disclosure. The embodiment of the example method400for a primary link designation change procedure inFIG.4is for illustration only. Other embodiments of the example method400for a primary link designation change procedure could be used without departing from the scope of this disclosure.

FIG.5illustrates an example method500for a primary link designation change procedure according to various embodiments of this disclosure. The embodiment of the example method500for a primary link designation change procedure inFIG.5is for illustration only. Other embodiments of the example method500for a primary link designation change procedure could be used without departing from the scope of this disclosure.

According to one embodiment, when the initiator (e.g., the Mobile AP MLD) decides to change the designation of the primary link, the initiator can transmit the primary link designation change information on the current primary link as shown inFIG.4. Upon receiving the primary link designation change information from the initiator, the responder can update its primary link information according to the information indicated by the initiator after making necessary verification related to the initiator (e.g., if the initiator is the Mobile AP MLD and the responder is the non-AP MLD, then the responder can check if the initiator is a Mobile AP MLD or alternatively if the initiator is a non-AP MLD and the responder is the Mobile AP MLD, then the responder can check if the initiator is a non-AP MLD associated with it). An example is shown inFIG.5when the responder is the non-AP MLD associated with a Mobile AP MLD and the initiator is the Mobile AP MLD.

FIG.6illustrates an example MLD capabilities subfield600according to various embodiments of this disclosure. The embodiment of the example MLD capabilities subfield600inFIG.6is for illustration only. Other embodiments of the example MLD capabilities subfield600could be used without departing from the scope of this disclosure.

An example format of the MLD Capabilities subfield combining embodiments described herein is as shown inFIG.6.

According to one embodiment, the primary link designation change information can be included in the MLD capabilities subfield of the Basic Multi-Link element. According to this embodiment, the upon receiving the primary link designation change information in the MLD capabilities subfield of the Basic Multi-Link element, the responder can update the primary link information according to the information indicated in the MLD capabilities subfield.

According to one embodiment, the initiator can convey its intention to change the primary link designation by using one or more of the bits in the MLD capabilities subfield of the Basic Multi-Link element. According to one embodiment, the MLD capabilities subfield of the Basic Multi-Link element can contain a Mobile AP MLD Primary Link Designation Change Indication bit. The initiator that intends to change the designation of the primary link of the Mobile AP MLD, can set the Mobile AP MLD Primary Link Designation Change Indication bit to 1 to indicate the change. When set to 0, the same primary link can be retained.

According to one embodiment, when there are only two links for a Mobile AP MLD (one primary link and one non-primary link) and the initiator sets the Mobile AP MLD Primary Link Designation Change Indication bit to 1, the non-primary link becomes the new primary link and the primary link becomes the new non-primary link.

According to one embodiment, the initiator can indicate the link that it intends to use as the new primary link when making the primary link designation change. Further, according to this embodiment, the initiator can indicate the link ID of the new primary link in the MLD capabilities subfield of the Basic Multi-Link element. As an example, the link ID of the new primary link can be indicated by using the B8˜B11 bits.

According to one embodiment, the initiator can indicate the time it intends to change the primary link designation. According to one embodiment, the time it intends to change the primary link designation can be indicated in the MLD capabilities subfield of the Basic Multi-Link element. According to one embodiment, the primary link designation change time can be indicated in terms of a counter whose value would count down in each MLD capabilities subfield that is transmitted by the initiator. As an example, the counter value can be indicated by using the reserved bits (B14˜B15) in the MLD capabilities subfield of the Basic Multi-Link element.

According to another embodiment, the time the initiator intends to change the primary link designation can be indicated in the MLD capabilities subfield as a multiple of a fixed pre-negotiated or pre-known value (e.g., TBTT, TU). As an example, the time the initiator intends to change the primary link designation can be indicated by using one or more of the reserved bits (e.g., B14˜B15) in the MLD capabilities subfield of the Basic Multi-Link element.

FIG.7illustrates an example method700for link swapping according to various embodiments of this disclosure. The embodiment of the example method700for link swapping inFIG.7is for illustration only. Other embodiments of the example method700for link swapping could be used without departing from the scope of this disclosure.

When the responder is the non-AP MLD, then according to one embodiment, the non-AP MLD can switch the primary link operation without any explicit notification to the initiator. In another embodiment, as illustrated inFIG.7, upon reception of a Basic Multi-Link element with the Primary Link Change subfield set to 1, the associated non-AP MLD may also send another Basic Multi-Link element with the Primary Link Change subfield set to 1 as an acknowledge to the change of primary link designation.

When the initiator is the non-AP MLD, the NSTR Mobile AP MLD may or may not accept the primary link designation change. In such a scenario, the NSTR Mobile AP MLD can explicitly indicate to the non-AP MLD that its request for primary link designation change has been denied by transmitting a basic multi-link element with the primary link change subfield set to 0.

FIG.8illustrates an example NSTR mobile AP MLD primary link change element frame format800according to various embodiments of this disclosure. The embodiment of the example NSTR mobile AP MLD primary link change element frame format800inFIG.8is for illustration only. Other embodiments of the example NSTR mobile AP MLD primary link change element frame format800could be used without departing from the scope of this disclosure.

According to another embodiment, the NSTR Mobile AP MLD can use a Mobile AP MLD Primary Link Change element to indicate to its associated non-AP MLD about the intention of the NSTR Mobile AP MLD to change the designation of the primary link and the non-primary link via link swapping. The NSTR Mobile AP MLD Primary Link Change element can contain one or more of the following fields:

TABLE IDetails of the fields of the NSTR MobileAP MLD Primary Link Change elementField NameDetailsElement IDThe element ID for the NSTR Mobile AP MLDPrimary Link Change elementLengthThe Length of the NSTR Mobile AP MLDPrimary Link Change elementElement ID extensionThe element ID extension for the NSTRMobile AP MLD Primary Link Change elementNew Primary Link IDThe Link ID for the link to be designatedas the primary linkPrimary Link ChangeTime in TBTT from the current TBTT toCountthe time of link swappingPrimary Link ChangePeriodicity of the change if the NSTRPeriodMobile AP MLD intends to periodicallyswitch the designation of the primarylink and the non-primary link

An example embodiment of the NSTR Mobile AP MLD Primary Link Change element is as shown inFIG.8.

Further, according to this embodiment, for changing the primary link designation, the NSTR mobile AP MLD may also indicate the time in terms of TB TT when the primary link designation will be changed. Moreover, it can also indicate periodicity of the change if the NSTR Mobile AP MLD intends to periodically switch the designation of the primary link and non-primary link.

In order to realize this, the NSTR Mobile AP MLD can send a Mobile AP MLD Primary Link Change element to its associated non-AP MLD in order to indicate the NSTR Mobile AP MLD's intention to change the designation of the primary link and non-primary link.

FIG.9illustrates an example method900for NSTR mobile AP MLD primary link change element operation according to various embodiments of this disclosure. The embodiment of the example method900for NSTR mobile AP MLD primary link change element operation inFIG.9is for illustration only. Other embodiments of the example method900for NSTR mobile AP MLD primary link change element operation could be used without departing from the scope of this disclosure.

FIG.10illustrates an example method1000for NSTR mobile AP MLD primary link change element operation according to various embodiments of this disclosure. The embodiment of the example method1000for NSTR mobile AP MLD primary link change element operation inFIG.10is for illustration only. Other embodiments of the example method1000for NSTR mobile AP MLD primary link change element operation could be used without departing from the scope of this disclosure.

According to another embodiment, one or more of the above subfields can be absent from the Mobile AP MLD Primary Link Change element. According to another embodiment, one or more subfields in addition to the subfields described above can also be present in the Mobile AP MLD Primary Link Change element.

According to another embodiment, the NSTR Mobile AP MLD can send a NSTR Mobile AP MLD Primary Link Change Notification frame to its associated non-AP MLD in order to indicate the NSTR Mobile AP MLD's intention to change the designation of the primary link and non-primary link. The contents of the NSTR Mobile AP MLD Primary Link Change Notification frame would be similar to the subfields described in the previous embodiments—New Primary Link-Link ID, Primary Link Change Count, and Primary Link Change Period.

According to another embodiment, a non-AP MLD can request its associated NSTR Mobile AP MLD to change its Primary link designation. In order to indicate this request, the non-AP MLD can send a Mobile AP MLD Primary Link Change element or NSTR Mobile AP MLD Primary Link Change Notification frame to its associated NSTR Mobile AP MLD.

According to another embodiment, upon reception of a request of NSTR Mobile AP MLD Primary link change from an associated non-AP MLD, the NSTR Mobile AP MLD, as a response to the request, can send another Mobile AP MLD Primary Link Change element or NSTR Mobile AP MLD Primary Link Change Notification frame with the same content as that of request received from the non-AP MLD if the NSTR Mobile AP MLD accepts the request. The procedure for this is as depicted inFIG.8. In another embodiment, the NSTR Mobile AP MLD either doesn't send any response frame or sends a response frame with content different that received in the request frame from the non-AP MLD.

According to another embodiment, the NSTR indication bitmap subfield of the per-STA profile sub-element in the basic multi-link element can be used for primary link designation indication. Further according to this embodiment, the bit corresponding to the primary link can be set to 1 in this bitmap to indicate the primary link designation.

In one embodiment, this NSTR indication bitmap can be advertised on the non-primary link. Thus, by using the indication, STA(s) of non-AP MLDs operating on the non-primary link can identify the primary link.

In another embodiment, this same bit that is used for primary link designation can be used for primary link designation change. According to this embodiment, when a primary link designation change occurs, the AP can set the bit corresponding to the new primary link in the bitmap to 1. Therefore, STA(s) of non-AP MLDs that receive such a bitmap from the AP can identify the new primary link based which bit is set to 1.

In another embodiment, channel switching can be performed when a need to change the primary link occurs. According to this embodiment, the channel corresponding to the primary link can be changed by performing a channel switching procedure.