Systems, methods, and apparatus for association enhancements in UHR

Abstract

The present disclosure relates to systems, methods, and apparatus for association enhancements in UHR. For example, the present disclosure relates to a wireless communication system that may include a multi-link multi-device (MLMD). The MLMD may be associated with a single MLMD MAC address. A set of access point (AP) multi-link devices (MLDs) may be associated with the MLMD. Each of the AP MLDs may include one or more APs. A station (STA) may use the MLMD MAC address to establish links with multiple APs across different AP MLDs and roam between APs.

Description

Technical Field

[0001] The present patent application generally relates to a wireless communication system including a network entity for associating a plurality of access points (APs) multi-link devices (MLDs). Background Art

[0002] Wireless communication technologies use various standards and protocols to transmit data between access points and wireless communication devices. For example, wireless communication system standards and protocols may include, for example, the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry organizations as Wi-Fi). ® ).

[0003] In the 802.11 standard for WLAN, an access point (AP) is a device that creates a wireless local area network (WLAN) or Wi-Fi. ® A WLAN is a device that connects to a wired network. An AP can connect to a wired network (such as Ethernet) and provide wireless access to that network for other devices. A station is a device that can wirelessly connect to an AP to join a WLAN network. A station can be a laptop, smartphone, tablet, or any other device with a WLAN adapter.

[0004] AP and stations use Wi-Fi ® Various protocols have been established to improve security on wireless communication networks. For example, simultaneous authentication of peer entities is the core authentication protocol of WPA3-Personal, and all Wi-Fi ® Alliance-certified devices, including both access points (APs) and non-AP stations (STAs), must support the protocol. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or action, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 An example signal flow diagram for Fast Basic Service Set (BSS) Transition (FT) is shown in accordance with some embodiments.

[0007] Figure 2 An example multi-link multi-device (MLMD) that may be used to reduce roaming delays is shown according to some embodiments.

[0008] Figure 3 An example network diagram using two MLMDs is shown according to some embodiments.

[0009] Figure 4An example basic multi-link element (MLE) and an example MLMD element are shown according to some embodiments.

[0010] Figure 5 A table of example AP and link IDs that may be determined by a STA during discovery according to some embodiments is shown.

[0011] Figure 6 An example beacon frame body is shown according to some embodiments.

[0012] Fig. 7A Example authentication request frames and authentication response frames are shown in accordance with some embodiments.

[0013] Figure 7B An example authentication frame body is shown in accordance with some embodiments.

[0014] Figure 8 An example signal diagram of a STA MLD associated with one or more APs corresponding to one or more AP MLDs corresponding to MLMDs is shown in accordance with some embodiments.

[0015] Fig. 9 An example STA Control field format in a reconfiguration MLE is shown according to some embodiments.

[0016] Fig.10 An example signal diagram is shown of a STA MLD using an MLMD association request frame with one AP MLD to establish links across multiple AP MLDs in accordance with some embodiments.

[0017] Fig.11 An example signal flow diagram is shown for establishing links across multiple AP MLDs using inter-AP MLD communications in accordance with some embodiments.

[0018] Fig.12 An example STA state transition table is shown according to some embodiments.

[0019] Fig.13 An example network is shown in which two STAs are assigned the same AID in accordance with some embodiments.

[0020] Fig.14 An example signal flow diagram of a CCMP package according to some embodiments is shown.

[0021] Fig.15 An example system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is shown. DETAILED DESCRIPTION

[0022] Wireless communication systems (e.g., Wi-Fi® Roaming in a wireless network refers to the transition of a wireless client device or station, such as a smartphone or laptop, between different access points within a wireless network. When a device moves away from one access point and the signal fades, the device can automatically connect to another nearby access point without losing connection. This technology allows users to stay connected to the Internet and maintain a continuous network session while moving within or across coverage areas.

[0023] On Wi-Fi ® In a roaming scenario, a roaming device may send out a signal to search for an available access point and / or scan for signals from one or more available access points. Once a compatible access point is detected, the device negotiates a connection with the new access point and authenticates itself. The ongoing communication session is then transferred to the new access point, ensuring uninterrupted data transfer. Wi-Fi ® Roaming enables users to move freely between access points without having to manually reconnect.

[0024] However, transitions between access points introduce latency. The embodiments herein provide systems, devices, and methods for reducing latency in roaming scenarios. Reducing latency ensures a seamless user experience. Low latency ensures that transitions between access points are fast and smooth, providing users with uninterrupted connectivity. Latency also directly affects the latency of Wi-Fi. ® The quality of service provided by the network. High latency can cause packet loss, jitter, and other performance issues, resulting in poor voice or video quality, slower data delivery, and overall poor network performance. Minimize Wi-Fi ® Latency during roaming helps maintain high-quality service levels and ensures that data transfer is reliable and efficient. By reducing latency, the time it takes for a device to authenticate and connect to a new access point is reduced or even minimized. This can allow users to effortlessly switch between access points while maintaining a stable and continuous network connection, thereby enhancing mobility and productivity. Minimizing Wi-Fi ® Delays in roaming can optimize network utilization.

[0025] Various embodiments are described with respect to stations (STAs) and access points (APs). However, references to STAs and APs are provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, STAs and APs as described herein are used to represent any suitable electronic components.

[0026] Figure 1An example signal flow diagram 102 for fast basic service set (BSS) transition (FT) according to some embodiments is shown. FT (also known as 802.11r) is a Wi-Fi standard that allows a client device (e.g., FT initiator (FTO 106)) to roam from one AP (e.g., current AP 108) to another AP (e.g., target AP 110).

[0027] In signal flow diagram 102, FTO 106 establishes a successful session and data transfer with current AP 108. FTO 106 determines 104 that the FTO needs to transition to target AP 110. For example, if FTO 106 has moved, the signal from current AP 108 may be weaker than the signal from target AP 110.

[0028] When a STA (e.g., FTO 106) decides to roam to a new AP (e.g., target AP 110), the following steps are performed for FT. The 802.1X controlled port is blocked, and PM=1 is sent to the current AP 108. Authentication, reassociation, and a four-way handshake for PTK (pairwise transient key) generation are performed. For example, when the FTO 106 needs to roam to the target AP 110, the FTO sends an authentication request frame 112 to the target AP 110. The target AP 110 sends an authentication response frame 114 to the FTO 106. A successful reassociation occurs when the time between the authentication request and the reassociation request does not exceed the reassociation deadline. The FTO 106 sends a reassociation request frame 116 to the target AP 110, and the target AP 110 sends a reassociation response frame 118 to the FTO 106. The 802.1X controlled port is unblocked, and a session can be established between the target AP 110 and the FTO 106.

[0029] In addition, as part of FT, the FTO 106 can send a Gratuitous Address Resolution Protocol (GARP) to the target AP 110 to update the routing table. GARP messages can be used to update the routing table with new or modified network information. The GARP message can include the MAC (Media Access Control) address of the FTO 106 and the network address that the GARP message expects or has changed. When receiving the GARP message, the target AP 110 processes the information and updates its routing table accordingly. This enables the router to appropriately forward network traffic within the network or make routing decisions based on the updated information.

[0030] The roaming process may introduce data transmission and reception delays. For example, roaming delays may range from 50ms to 120ms. Roaming delay refers to the time difference between the last uplink packet to the current AP 108 and the first uplink packet to the target AP 110. A delay of less than 100ms for a video call or Wi-Fi call or 40ms for a group video call may be an acceptable value. As shown in the figure, an authentication frame may cause a delay of 2.5ms and a reassociation frame may cause a delay of 8.26ms. The delay of FT over the air (OTA) may be 13.4ms. In addition, GARP may cause considerable delays. The embodiments of this article can reduce delays.

[0031] Figure 2 An example multi-link multi-device (MLMD 202) that may be used to reduce roaming delays according to some embodiments is shown. MLMD 202 is a logical (virtual) entity that includes a set of AP multi-link devices (MLDs) (e.g., AP MLD 204, AP MLD 206, and AP MLD 208). The AP MLDs may communicate over multiple links (e.g., radio channels in multiple frequency bands) using two or more radios for transmission to one or more STAs.

[0032] Each AP MLD may have a data connection to the router 210. The router 210 maintains information about the data path to forward downlink data to the location of the STA, regardless of where the STA roams. Figure 1 As discussed, generally when a STA moves to a different AP MLD, a delay may occur due to the need for authentication and reassociation frames accordingly.

[0033] In some embodiments, there may be a separation between the data connection and the control connection of the AP MLD. Figure 2 As shown, a control path to MLMD 202 may be implemented between AP MLDs. This control path may allow a STA to move from one AP MLD to another AP MLD without requiring authentication and reassociation frames.

[0034] In some embodiments, a single MLMD media access control (MAC) address may be used to facilitate mobility between different AP MLDs. In addition to the MAC address, the MLMD may also have an IP address to serve as a virtual MAC Service Access Point (SAP), while the physical MAC SAP resides at each AP MLD associated with the MLMD. The MLMD MAC address may be associated with several MAC addresses corresponding to each AP MLD. Each AP MLD may have a unique AP MLD MAC address that may be mapped to or associated with a single MLMD address.

[0035] For 11bn STAs, after association, data encryption (e.g., CCMP, GCMP) may be performed using the MLMD MAC address and SN and PN spaces shared across the AP MLDs associated with the MLMD. This may allow the STA to maintain a single encryption key (e.g., PTK) across the AP MLDs corresponding to the MLMD 202. This may allow the STA to roam without re-association because the PTK is based on a common MLMD MAC address that is consistent across AP MLDs.

[0036] The architecture can also support legacy STAs. For 11be STAs, data encryption can use the AP MLD MAC address. These STAs can perform Figure 1 to roam between AP MLDs.

[0037] Figure 3 An example network diagram 302 using two MLMDs (i.e., MLMD 304 and MLMD 306) according to some embodiments is shown. As shown, there may be a set of AP MLDs connected to MLMD 304 and another set of AP MLDs connected to MLMD 306. Each MLMD may be communicatively coupled to a router (e.g., router 310 and router 314) and a switch (switch 308 and switch 312). The MLMDs may be coupled via an ISP / cloud connection.

[0038] When a STA roams between AP MLDs associated with MLMD 304, the STA can use the MLMD MAC address and the common SN and PN space shared between the current AP MLD and the target AP MLD to which the STA wants to roam. Using the MLMD MAC address can eliminate the need for authentication and reassociation frames, thereby reducing latency. If the STA is moving from MLMD 304 to MLMD 306, it can perform Figure 1In some embodiments, the AP MLD may be configured to perform data encryption between the STA and the AP using the MLMD MAC address, so that the AP MLD can support STAs roaming between AP MLDs using the same encryption key, and can use the same or shared sequence number (SN), packet number (PN) space, a block ACK session negotiated for one or more traffic identifiers (TIDs), or one or more of a BA bitmap for each negotiated TID.

[0039] Figure 4 An example basic multilink element (MLE) 402 and MLMD element 406 according to some embodiments are shown. The AP MLD may send the basic MLE 402 and MLMD element 406 to the STA in a beacon frame. In some embodiments, the MLMD element 406 may be sent to the STA in another management frame, such as a probe response frame. The basic MLE 402 and MLMD element 406 may include information about the MLD and MLMD. For example, the basic MLE 402 may include the MLD MAC address 404 of the AP MLD.

[0040] The MLMD element 406 may include information about the MLMD associated with the AP MLD. As shown, the MLMD element 406 may include an element ID field 408. The MLMD element 406 may be included in a beacon frame. The MLMD element 406 may include an element ID field 408, a length field 410, an element ID extension field 412, an MLMD control field 414, an MLMD common information field 416, and an MLMD link information field 418.

[0041] The element ID field 408 may identify the element as the MLMD element 406. The element ID extension field 412 may be used to extend the range of element ID values. The length field 410 specifies the length of the MLMD element 406. The MLMD control field 414 may include an MLMD link information field 420. The MLMD link information field 420 may indicate whether an MLMD link exists.

[0042] The MLMD common information field 416 may include an MLMD MAC address field 422 and a support MLMD with multiple AP MLDs field 424. The MLMD MAC address field 422 indicates the MLMD MAC address. The STA may discover the AP MLD as part of a single MLMD based on the MLMD MAC address. The support MLMD with multiple AP MLDs field 424 may indicate support for the ML establishment process. For example, the support MLMD with multiple AP MLDs field 424 may be used to indicate support for establishing a link across AP MLDs after associating with a single AP MLD within the MLMD and support for establishing a link across AP MLDs during association with a single AP MLD within the MLMD.

[0043] In some embodiments, each MLMD may use a single service set identifier (SSID). In some embodiments, multiple MLMDs with a single SSID may be allowed. This may help with legacy roaming when roaming between MLMDs. Neighbor Report (NR) / Reduced Neighbor Report (RNR) announcements may include MLMD level parameters and their constituent AP MLDs. Each BSSID of a multiple Basic Service Set Identifier (BSSID) set may be associated with an AP MLD and a MLMD, as indicated by the indication in the multiple BSSID elements.

[0044] When a STA is associated with an AP MLD, the STA can determine the MLMD MAC address using the MLMD element 406 from the beacon frame. The STA can use the MLMD MAC address to encrypt its data. When a STA moves between different AP MLDs under the same MLMD, the STA can use the same encryption.

[0045] Figure 5 An example table 502 of AP and link IDs that may be determined by a STA during discovery according to some embodiments is shown. As shown, an 11be STA may identify an AP and link ID based on MLE (e.g., Figure 4 In addition to the AP's BSSID 504 and AP MLD MAC address 506, the 11bn STA may determine the AP's BSSID 504 and AP MLD MAC address 506 based on the MLMD element (e.g., Figure 4 The MLMD element 406) is used to determine the MLMD MAC address 508.

[0046] Figure 6An example beacon frame body 602 is shown in accordance with some embodiments. As shown, the beacon frame body 602 may include an MLMD element 604. The MLMD element may be present if dot11MultiLinkMultiDeviceActivated is true and the frame exchange is with a peer STA affiliated with MLD. Otherwise, the MLMD element may not be present.

[0047] Fig. 7A An example authentication request frame 702 and authentication response frame 704 are shown in accordance with some embodiments. For initial MLMD association and authentication, the STA and AP MLD may use the authentication request frame 702 and authentication response frame 704 to indicate support for MLMD level association.

[0048] For example, the STA may perform discovery and find an AP with an acceptable signal strength (e.g., a signal strength that satisfies a predetermined threshold). If the STA is affiliated with another non-AP MLD, the STA may send an authentication request frame 702 to the AP affiliated with the AP MLD. The STA may use signaling to indicate support for MLMD level association. For example, the authentication request frame 702 may include an MLMD element 706 indicating that the STA supports MLMD level association. In some embodiments, there may be a "seamless roaming support" signaling field in the MAC capability information element included in the management frame of the STA (e.g., an association request frame).

[0049] The AP belonging to the AP MLD sends an authentication response frame 704 to the STA belonging to the non-AP MLD. The authentication response frame 704 may include an MLMD element 708. The AP may include a "seamless roaming support" signaling field in a MAC capability IE included in a management frame (e.g., a beacon frame). The AP may include a "seamless roaming support" signaling field in the MLMD element 708 within the frame body of the frame. MLMD MAC The address subfield includes the MLMD MAC address. Note that the AP MLD MAC address may be included in the basic MLE. The STA receiving the authentication response frame 704 may determine that the AP supports MLMD association based on the presence of the "Seamless Roaming Support" field in the MAC Capability IE or the presence of the MLMD element 708 in the authentication response frame 704. The MLMD element 708 may include at least one of the following fields, namely, MLMD control, MLMD Public Information and MLMD Link information field. It may not exist in the authentication frame. MLMD Link Information Field. In some embodiments, the same security context (eg, Counter Mode Cipher Block Chaining Message Authentication Code Protocol (CCMP) 128, Authentication and Key Management (AKM)) may be used within MLMD.

[0050] Figure 7B An example authentication frame body 710 is shown in accordance with some embodiments. As shown, the authentication frame body 710 may include an MLMD element 712. If dot11MultiLinkMultiDeviceActivated is true and the frame exchange is with a peer STA affiliated with an MLD, the MLMD element 712 is present. Otherwise, the MLMD element may not be present.

[0051] After the discovery state (state 1) and the authentication state (state 2), the STA may associate with one or more APs (state 3). In state 3, the STA may be authenticated and associated with an AP. Figure 8 An example signal diagram 802 of a STA MLD 804 associated 806 with one or more APs corresponding to one or more AP MLDs 808 corresponding to MLMD 810 is shown in accordance with some embodiments.

[0052] STA MLD 804 may include multiple STAs 812 that allow association with multiple APs. In the illustrated embodiment, STA MLD 804 includes four STAs (e.g., STA 1, STA 2, STA 3, and STA 4). STA 1, STA 2, and STA 3 may use different frequency ranges to connect to different APs. For example, STA 1 may use 2.4 GHz, STA 2 may use 5 GHz, and STA 3 may use 6 GHz. In the illustrated embodiment, STA 4 is a virtual station.

[0053] Each AP MLD 808 may include multiple APs (e.g., AP 806). For example, the first AP MLD 814 includes AP 11, AP 12, and AP 13. The second AP MLD 816 includes AP 21, AP 22, and AP 23. Each AP MLD in the AP MLD 808 may be associated with a single MLMD 810. The MLMD may unify the connections between the APs 806 using a single MLMD MAC address, regardless of whether the APs are on the same AP MLD. The MLMD 810 may also keep updating the STA status maintenance table.

[0054] STA MLD 804 may perform initiating link establishment. The initial MLMD association may be made with a single AP MLD (e.g., first AP MLD 814), and then STA MLD 804 may subsequently add links across multiple AP MLDs. A STA (e.g., STA 1) may send an association request frame to the AP, which carries in the MLMD element MLMDThe MLMD link information field indicates the link that is requested to be established. MLMD The link information field includes the link information of the current AP MLD.

[0055] A STA may also send a reconfiguration MLE to initiate a multi-link (ML) reconfiguration operation for establishing a link with an AP belonging to a different AP MLD. Additional overhead may be used for each link added to the ML establishment.

[0056] For example, in the illustrated embodiment, STA 1 sends a setup request 818 to AP 12. The setup request 818 may initiate link establishment between AP 12 and STA 1, AP 11 and STA 3, and AP 13 and STA 2. As shown, during the initiation of the link establishment, the STA MLD 804 initial MLMD association is performed with a single AP MLD (e.g., the first AP MLD 814). For the initial association, the STA MLD 804 may send an association request frame that carries an MLMD link information field in the MLMD element, which indicates a request to establish links with AP 11, AP 12, and AP 13.

[0057] STA MLD 804 may then establish links with other AP MLDs (e.g., second AP MLD 816) that are associated to the same MLMD 810 as first AP MLD 814. For example, STA 4 may send a reconfiguration MLE 820 to add a link to AP 22 associated with second AP MLD 816. Even though AP 22 is not affiliated with first AP MLD 814, reconfiguration MLE 820 may initiate an ML reconfiguration operation for establishing links with AP 22 and STA 4.

[0058] Fig. 9 An example STA control field format 902 in a reconfiguration MLE according to some embodiments is shown. The STA control field format 902 may be used by a STA to indicate that the STA wants to add a link to an AP on an AP MLD different from the current AP MLD to which the STA is linked, and the different AP MLD belongs to the same MLMD as the current AP MLD. For example, the STA may use the Operation Update Type subfield 906 to indicate that it is desired to add a link to another AP on a different AP MLD. As shown, the Operation Update subfield encoding 904 may include a value (e.g., 2) indicating that the reconfiguration MLE is to add a link.

[0059] Fig.10 and Fig.11Another associated signaling process for establishing a link across multiple AP MLDs is shown. Figure 8 and Fig. 9 In order to add a link to an AP belonging to multiple AP MLDs, the STA will send an association request frame to add a link to the first AP MLD, and then send a reconfiguration MLE to add a link to another AP MLD. Fig.10 and Fig.11 Defines a method that allows a STA to establish links across multiple AP MLDs using a single request frame.

[0060] For example, Fig.10 An example signal diagram 1002 is shown of a STA MLD 1004 using an MLMD association request frame with one AP MLD to establish links across multiple AP MLDs 1006. This approach may allow links to be established across multiple AP MLDs and used in standby mode to facilitate roaming across APs 1010 in different AP MLDs 1006.

[0061] As shown, the first STA 1012 sends an association request frame to the current AP (eg, AP 12). The association request frame may carry MLMD The link information field indicates the links of multiple AP MLDs requested to be established. MLMD The link information field may include link information of the current MLD (e.g., the first AP MLD 1008) or link information of links of other AP MLDs (e.g., the second AP MLD 1014) within the MLMD 1016. The link information may include a link ID and a STA MAC address of the AP belonging to the AP MLD. For example, in the illustrated embodiment, the first STA 1012 may request to establish a link between the AP 12 and the first STA 1012 and between the AP 22 and the fourth STA 1018 using an association request frame through a single request sent to the AP 12.

[0062] The first AP MLD 814 may send a STA Setup Request to the second AP MLD 1014 indicating the desired link of the STA MLD 1004. The STA Setup Request may include information about the link and credentials for the link. The second AP MLD 816 may send a STA Setup Response to indicate that the link has been accepted or rejected. An AP (e.g., AP12) affiliated with the first AP MLD 1008 may send a STA Setup Response carrying all "accepted" links to be established after exchanging messages (i.e., STA Setup Request / Response) between the first AP MLD 1008 and the second AP MLD 1014. MLMD Association Response frame with Link Information field.

[0063] Note that in 11be, restrictions may be imposed on link establishment. That is, each of any two links requested to be established must be in different non-overlapping operating channels of 11be. In some embodiments, this restriction can be relaxed by having a STA request multiple links to be established that are in the same operating channel, with one link being active at any point in time. A power saving mode may be used to disable other links (e.g., links that are not active for data transmission / reception). For example, MLMD Link in the Link Information field ID The subfield identifies each link PM The bit indication may indicate whether the link is disabled (e.g., in power save mode) or enabled. "Disable link" signaling may be used for links added to other AP MLDs (e.g., second AP MLD 1014). In other words, a STA MLD may selectively activate and disable links to roam between APs across different STA MLDs.

[0064] Fig.11 An example signal flow diagram 1102 is shown for establishing a link across multiple AP MLDs using inter-AP MLD communication according to some embodiments. The signal flow diagram 1102 shows Fig.10 Communication between the first STA 1012, AP 12, the first AP MLD 1008 and the second AP MLD 1014.

[0065] As shown, the first STA 1012 sends an MLMD association request 1104 to the AP 12. The MLMD association request 1104 may include in the MLMD element MLMD Link information field, the MLMD link information field indicates the links of multiple AP MLDs requested to be established. For example, MLMD The link information field may include the link information of the current MLD and / or the link information of the links of other AP MLDs in the MLMD. The link information may include the link identifier and the STA MAC address of the AP belonging to the AP MLD.

[0066] If the MLMD association request 1104 includes a request to establish a link with the AP 22 of the second AP MLD 1014, the AP MLD affiliated with the AP 12 (i.e., the first AP MLD 1008) can send a STA establishment request 1106 to the second AP MLD 1014. The first AP MLD 1008 and the second AP MLD 1014 can communicate over the air (OTA) or through a distributed system (DS) to establish a desired link for the requesting STA. The STA establishment request 1106 may include information and credentials about the link that the first STA 1012 desires to use with the AP 22. The second AP MLD 1014 can send a STA establishment response 1108 to the first AP MLD 1008. The STA establishment response 1108 may indicate that the link has been accepted or rejected. After the first AP MLD 1008 receives the STA establishment response 1108, the AP 12 can send an MLMD association response 1110 to the first STA 1012. The MLMD association response 1110 may include all accepted links to be established. MLMD Link Information Field.

[0067] Fig.12 An example STA state transition table 1202 according to some embodiments is shown. The STA state transition table 1202 may also be referred to herein as a STA state maintenance table. The MLMD may maintain the STA state transition table 1202 to keep a record of an association identifier (AID). The AID is a unique identifier assigned to a wireless client device when the wireless client device is associated with a wireless access point (AP). The AID may be used to identify a client device.

[0068] The AID is a temporary identifier that is valid for the duration of the association. When the client device disassociates from the AP, the AID is released. The MLMD may maintain a STA state transition table 1202 to determine the next available AID to be allocated when the STA associates with the AP. The MLMD may track the AID of the STA as it roams between APs.

[0069] The STA state transition table 1202 may include a list of metrics for each STA. For example, the STA state transition table 1202 may include a STA MAC address 1204 and a non-AP MLD MAC address to which the STA belongs (e.g., a STA MLD MAC address 1206). Therefore, the STA state transition table 1202 may include the MAC address of the STA and the MAC address of the STA MLD associated with the STA. The STA state transition table 1202 may include the AP MAC address currently associated with the STA. In addition, the STA state transition table 1202 may include information 1208 of a subset of links established with the MLMD. For example, the information 1208 may include details such as link ID, AP MAC address, and PM bit. The STA state transition table 1202 may include an assigned AID 1210, a pairwise temporary key (PTK) 1212 established per session, and a PN for each STA MAC address. In some embodiments, the STA state transition table 1202 may include an SN and an active BA session.

[0070] The MLMD may manage a group of AP MLDs mapped to a single MLMD MAC address. The MLMD may maintain a list of AP MLDs in the group that have direct interfaces (e.g., Ethernet, fiber). In some embodiments (e.g., first option 1214), the STA state transition table 1202 also maintains an AID pool for 11bn STAs. Each AP may update the AID pool as it releases an AID after disassociation. Each AP may not assign an AID from the pool to a legacy STA.

[0071] In some embodiments (eg, second option 1216), the STA state transition table 1202 may maintain an AID pool from the forward compatible AID space of 11bnSTAs. The AP MLD MAC address may be mapped to each of the component AP MAC addresses.

[0072] Fig.13An example network 1302 is shown in which two STAs (e.g., STA 1304 and 11be STA 1306) are assigned the same AID. Such AID conflicts may occur if each MLMD association assigns a single AID and AP MLD 1308 handles the assignment of AIDs without knowing the AIDs assigned by other AP MLDs. In the illustrated example, the first AP MLD 1312 assigns AID 10 to STA 1304, and the second AP MLD 1310 assigns the same AID 10 to a legacy STA (11be STA 1306). When STA 1304 roams to AP 22, there is a conflict. Therefore, some embodiments herein use MLMD-level AID assignment. MLMD 1316 can use STA state maintenance table 1314 to track the assigned AIDs on the associated AP MLD 1308. In some embodiments, a roaming STA can use an AID assigned by its current AP after roaming to its target AP.

[0073] The AID may be included in the Traffic Indication Map (TMI) of a Power Save (PS) STA. The AID may be included in the multi-user uplink / downlink resource allocation. The signaling may be in the User Information field in the TF. The signaling may be in the Extended High Throughput / Ultra High Rate (EHT / UHR) SIG of the downlink (DL) multi-user (MU) physical protocol data unit (PPDU).

[0074] In IEEE 802.11be, when ML is successfully established, an AID is allocated by the AP MLD to the non-AP MLD. All STAs belonging to the non-AP MLD have the same AID allocated to the non-AP MLD.

[0075] In IEEE 802.11bn, if a non-AP MLD exists with a single MLMD association, the following may be options for handling AID allocation to avoid conflicts. In some embodiments, AID allocation may be at the MLMD level. In some embodiments, AID allocation may be at the MLD level (as in 11be).

[0076] For implementations where AID allocation may be at the MLMD level, AIDs may be allocated from an available AID pool maintained in the STA state maintenance table 1314. In some implementations, the available AID pool does not overlap with the AIDs allocated to legacy STAs by each of the AP MLDs 1308 within the MLMD 1316. This may result in processing conflicts for AID allocations between roaming and associated STAs.

[0077] An implementation where AID allocation is at the MLD level may allow local management of AID allocation for each AP MLD. However, there may be multiple AIDs to be managed by non-AP MLDs.

[0078] Fig.14 An example signal flow diagram 1402 of CCMP encapsulation according to some embodiments is shown. For a Robust Security Network Association (RSNA) established by SME and 802.1X authentication (SC 12.6.10) or FT protocol (SC 13.5), a STA may invoke Simultaneous Authentication of Peers (SAE) authentication to establish a PMK. Temporary key establishment may mean a unique temporary key (TK) and therefore a PTK for the session established between the STA and its current AP, and a TK and PTK between the STA and its target AP.

[0079] In some embodiments, CCMP may use the MLMD MAC address instead of the AP MLD MAC address for encryption. CCMP (CTR with CBC-MAC protocol) encapsulation may construct AAD (Additional Authentication Data) using knowledge of the MPDU MAC header (i.e., Rx MLMD MAC address (A1), A2, AP's MLMD MAC address (A3), Sequence Control, and QoS Control). CCMP encapsulation may construct the CCM nonce using knowledge of A2 (Tx's MLD MAC address), priority (QoS control field), MLMD MAC address, and PN. CCM encryption (data, MIC) may be a function of inputs from constructed AAD, nonce, MPDU data, TK. The encrypted MPDU may be a function of CCM encryption and the constructed CCMP header (a function of Key ID, PN-6 octets). A single PN space for individually addressed MPDUs is maintained by the MLD and used for all affiliated STAs using the same TN.

[0080] Fig.15 An example system 1500 for performing signaling 1534 between a STA 1502 and an AP 1518 according to embodiments disclosed herein is shown. The system 1500 may be part of a wireless communication system as described herein. The STA 1502 may be, for example, a user equipment (UE) of a wireless communication system. The AP 1518 may be, for example, an access point of a wireless communication system.

[0081] STA 1502 may include one or more processors 1504. Processor 1504 may execute instructions to perform various operations of STA 1502 as described herein. Processor 1504 may include one or more baseband processors, which are implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0082] STA 1502 may include memory 1506. Memory 1506 may be a non-transitory computer-readable storage medium storing instructions 1508 (which may include, for example, instructions executed by processor 1504). Instructions 1508 may also be referred to as program code or a computer program. Memory 1506 may also store data used by processor 1504 and results calculated by the processor.

[0083] STA 1502 may include one or more transceivers 1510, which may include radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 1512 of STA 1502 to facilitate signaling (e.g., signaling 1534) to and / or from STA 1502 and other devices (e.g., AP 1518).

[0084] STA 1502 may include one or more antennas 1512 (e.g., one, two, four, or more antennas). For implementations with multiple antennas 1512, STA 1502 may take advantage of the spatial diversity of such multiple antennas 1512 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission by STA 1502 may be implemented based on precoding (or digital beamforming) applied at STA 1502, which multiplexes data streams between antennas 1512 based on known or assumed channel characteristics, so that each data stream is received with appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with the data stream). Certain embodiments may use a single-user MIMO (SU-MIMO) approach (where data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0085] In certain embodiments with multiple antennas, STA 1502 may implement analog beamforming techniques whereby the phases of signals transmitted by antennas 1512 are relatively adjusted such that the (joint) transmissions of antennas 1512 may be directed (this is sometimes referred to as beam steering).

[0086] STA 1502 may include one or more interfaces 1514. Interface 1514 may be used to provide input to STA 1502 or provide output of the STA. For example, STA 1502 as a UE may include interface 1514, such as a microphone, speaker, touch screen, button, etc., to allow a user of the UE to input and / or output to the UE. Other interfaces of such UE may be composed of transmitters, receivers and other circuits that allow communication between the UE and other devices (e.g., in addition to the transceiver 1510 / antenna 1512 described above), and may be based on known protocols (e.g., Wi-Fi ® 、Bluetooth ® etc.) to perform the operation.

[0087] The STA 1502 may include an MLMD link module 1516. The MLMD link module 1516 may be implemented via hardware, software, or a combination thereof. For example, the MLMD link module 1516 may be implemented as a processor, circuit, and / or instructions 1508 stored in the memory 1506 and executed by the processor 1504. In some examples, the MLMD link module 1516 may be integrated within the processor 1504 and / or the transceiver 1510. For example, the MLMD link module 1516 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the processor 1504 or the transceiver 1510.

[0088] The MLMD link module 1516 may be used in various aspects of the present disclosure, for example, Figures 2 to 14 The MLMD link module 1516 is configured to establish links with one or more APs across one or more AP MLDs associated with the MLMD.

[0089] The AP 1518 may include one or more processors 1520. The processor 1520 may execute instructions to perform various operations of the AP 1518 as described herein. The processor 1520 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0090] AP 1518 may include memory 1522. Memory 1522 may be a non-transitory computer-readable storage medium that stores instructions 1524 (which may include, for example, instructions executed by processor 1520). Instructions 1524 may also be referred to as program code or a computer program. Memory 1522 may also store data used by processor 1520 and results calculated by the processor.

[0091] AP 1518 may include one or more transceivers 1526, which may include RF transmitter and / or receiver circuitry that uses antenna 1528 of AP 1518 to facilitate signaling (e.g., signaling 1534) to and / or from AP 1518 and other devices (e.g., STA 1502).

[0092] AP 1518 may include one or more antennas 1528 (eg, one, two, four, or more antennas). In embodiments with multiple antennas 1528, AP 1518 may perform MIMO, digital beamforming, analog beamforming, beamsteering, etc., as described.

[0093] The AP 1518 may include one or more interfaces 1530. The interface 1530 may be used to provide input to the AP 1518 or provide output of the AP. For example, the AP 1518 as a base station may include an interface 1530 composed of a transmitter, a receiver and other circuit systems (e.g., in addition to the transceiver 1526 / antenna 1528 described above), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., for the purpose of operating, managing and maintaining the base station or other equipment operably connected to the base station.

[0094] The AP 1518 may include an MLMD link module 1532. The MLMD link module 1532 may be implemented via hardware, software, or a combination thereof. For example, the MLMD link module 1532 may be implemented as a processor, circuit, and / or instructions 1524 stored in the memory 1522 and executed by the processor 1520. In some examples, the MLMD link module 1532 may be integrated within the processor 1520 and / or the transceiver 1526. For example, the MLMD link module 1532 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuit systems) within the processor 1520 or the transceiver 1526.

[0095] The MLMD link module 1532 may be used in various aspects of the present disclosure, for example, Figures 2 to 14The MLMD link module 1532 is configured to establish links with one or more APs across one or more AP MLDs associated with the MLMD.

[0096] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, the processor described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown herein. For another example, the circuit system associated with the STA or AP described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown herein.

[0097] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0098] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.

[0099] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated herein.

[0100] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0101] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A wireless communication system, the system comprising: A multi-link multi-device MLMD, wherein the multi-link multi-device includes an MLMD MAC address; and a set of access point AP multi-link devices MLD associated with the MLMD, wherein each of the AP MLDs includes one or more APs, The AP MLD is configured to perform data encryption between a station STA and an AP using the MLMD MAC address, so that the AP MLD can support the STA to roam between the AP MLDs using the same encryption key, and can use the same or shared sequence number SN, packet number PN space, a block ACK session negotiated for one or more traffic identifiers TID, or one or more of a BA bitmap for each negotiated TID.

2. The system of claim 1, further comprising a plurality of routers coupled to the AP MLD, wherein the AP MLD has a data path with the routers and a control path with the MLMD.

3. The system of claim 1, wherein the AP MLD is further configured to send a MLMD element to the STA during a beacon frame, wherein the MLMD element includes the MLMD MAC address and may include a MLMD IP address.

4. The system of claim 3, wherein the MLMD element further comprises a field indicating whether the APMLD supports establishing links across the AP MLDs after associating with a single AP MLD within the MLMD or supports establishing links across the AP MLDs during associating with the single AP MLD within the MLMD.

5. The system of claim 1, wherein a single service set identifier (SSID) is used for the MLMD different from other MLMDs.

6. The system of claim 1, wherein the plurality of MLMDs use a single service set identifier (SSID).

7. The system of claim 1, wherein the AP is configured to: receiving an authentication request from the STA, wherein the authentication request includes an indication that the STA supports MLMD level association; and An authentication response including the MLMD MAC address is sent.

8. The system of claim 1, wherein the MLMD is configured to maintain a STA state transition table to track assigned association identifiers AIDs and determine the next available AID to be assigned.

9. The system of claim 1, wherein the STA corresponds to a STA MLD, and wherein the first AP receives an association request from the STA, and A second AP on a different AP MLD receives a reconfiguration multilink element MLE from a second STA corresponding to the STA MLD, wherein the reconfiguration MLE includes an update type field indicating that the reconfiguration MLE is to add a link between the second AP and the second STA.

10. The system of claim 1, wherein the STA corresponds to a STA MLD, and wherein the first AP receives an association request from the STA, the association request indicating a desired link to be established with the AP across a plurality of the AP MLDs, and wherein the AP MLDs communicate with each other over the air (OTA) or through a distributed system (DS) regarding establishing the desired link for the STA.

11. An operation method for a station STA multi-link device MLD, the method comprising: receiving a beacon frame from two or more of the access point AP multi-link devices MLD, wherein the beacon frame includes a multi-link multi-device MLMD element, the MLMD element having a MLMD MAC address; determining which of the AP MLDs are associated with the same MLMD based on the MLMD MAC address; sending an authentication request, wherein the authentication request includes an indication that the STA supports MLMD level association; receiving an authentication response including the MLMD MAC address; as well as A link is established between one or more STAs belonging to the STA MLD and one or more APs across the AP MLD associated with the same MLMD.

12. The operating method according to claim 11, further comprising performing data encryption using the MLMD MAC address, and roaming between the AP MLDs using the same encryption key.

13. The operating method according to claim 11, wherein establishing a link comprises: Sending an association request to the first AP on the first AP MLD; as well as A reconfiguration multilink element (MLE) is sent to the second AP on the second AP MLD, wherein the reconfiguration MLE includes an update type field, and the update type field indicates that the reconfiguration MLE is used to add the link.

14. The operating method according to claim 11, wherein establishing a link comprises: An association request is sent to a first AP on a first AP MLD, the association request indicating a desired link to be established with the AP across a plurality of AP MLDs in the AP MLDs, and wherein the AP MLDs communicate with each other over the air (OTA) or through a distributed system (DS) regarding establishment of the desired link for the STA.

15. The operating method of claim 11, selectively activating and deactivating the link to roam between APs across different STAMLDs.

16. A station STA multi-link device MLD device, the STA MLD device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: receiving a beacon frame from two or more of the access point AP multi-link devices MLD, wherein the beacon frame includes a multi-link multi-device MLMD element, the MLMD element having a MLMD MAC address; determining which of the AP MLDs are associated with the same MLMD based on the MLMD MAC address; sending an authentication request, wherein the authentication request includes an indication that the STA supports MLMD level association; receiving an authentication response including the MLMD MAC address; as well as A link is established between one or more STAs belonging to the STA MLD and one or more APs across the AP MLD associated with the same MLMD.

17. The STA MLD device of claim 16, wherein the instructions further configure the device to perform data encryption using the MLMD MAC address and to roam between the AP MLDs using the same encryption key.

18. The STA MLD device of claim 16, wherein establishing a link comprises: Sending an association request to the first AP on the first AP MLD; as well as A reconfiguration multilink element (MLE) is sent to the second AP on the second AP MLD, wherein the reconfiguration MLE includes an update type field, and the update type field indicates that the reconfiguration MLE is used to add the link.

19. The STA MLD device of claim 16, wherein establishing a link comprises: An association request is sent on a first AP MLD to a first AP, the association request indicating a desired link to be established with the AP across a plurality of APMLDs in the AP MLDs, and wherein the AP MLDs communicate between each other regarding the desired link.

20. The STA MLD apparatus of claim 16, wherein the link is selectively activated and disabled to roam between APs across different STA MLDs.

21. An apparatus comprising means for performing the method according to any one of claims 11 to 15.

22. A computer-readable medium comprising instructions, which, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 11 to 15.

23. An apparatus comprising logic components, modules or circuits for performing the method according to any one of claims 11 to 15.

Images