Association transfer

Abstract

The invention relates to association transfer. Disclosed herein is a method comprising determining that a first access point and a second access point are in a coordination protocol, and determining that there is an association between a device and the first access point. The method also includes sending a discovery request to a second access point. The discovery request includes a query as to whether the second access point will accept a transfer of association with the device. The method also includes receiving a discovery response from the second access point, the discovery response indicating that the second access point accepts a discovery request to transfer association with the device. The method also includes negotiating terms of association between the device and the second access point between the first access point and the second access point.

Description

Technical Field

[0001] The example embodiments may relate to systems, methods, and / or computer programs for wireless networks. Specifically, the example embodiments relate to coverage vulnerability mitigation and association transfer in wireless networks using multi-access point coordination. Background Technology

[0002] In computer networks, a wireless access point (AP) is a network hardware device that allows Wi-Fi (IEEE 802.11 network) compatible client devices to wirelessly connect to wired networks and other client devices. APs are typically connected to a router as standalone devices (directly or indirectly via a wired network), but an AP can also be an integral part of the router itself. Several nodes can also work collaboratively via direct wired or wireless connections in a wireless local area network (WLAN). In some WLAN implementations, APs may collaborate in a scheme called Multi-Access Point Coordination (MAPC). Two or more APs can coordinate certain operations. This coordination can include AP association transfer and coverage gap mitigation. Summary of the Invention

[0003] The independent claims define the scope of protection for various embodiments of the invention. Embodiments and features described in this specification that are not within the scope of the independent claims (if any) are to be interpreted as examples that aid in understanding the various embodiments of the invention.

[0004] According to a first aspect, an apparatus is described, comprising components for: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; sending a discovery request to the second access point, the discovery request including: an inquiry about whether the second access point will accept a transfer of association with the device; receiving a discovery response from the second access point, the discovery response indicating that: the second access point accepts the discovery request to transfer the association with the device; and negotiating terms between the first access point and the second access point regarding the association between the device and the second access point.

[0005] In some embodiments, the apparatus may further include: a component for authorizing the association between the device and the second access point, wherein the authorization includes: sending user association information for the device to the second access point.

[0006] In some embodiments, the device may be a first access point.

[0007] In some embodiments, the apparatus may further include: components for determining that the first access point and the second access point are in a coordination protocol, including components for determining that the first access point and the second access point are part of a Multi-Access Point Coordination (MAPC) group.

[0008] In some embodiments, the user association information of the device may include at least one of the following: the device's unique identifier, the device's Media Access Control (MAC) address, and the terms of association between the device and the second access point.

[0009] In some embodiments, a discovery request or discovery response may include at least one association capability for the association between the second access point and the device.

[0010] In some embodiments, at least one associated capability may include at least one of the following: the operating frequency band of the device, the maximum number of devices to be supported, the minimum received signal strength indicator (RSSI) of the device, the maximum bandwidth to be shared with the device, and the shared availability calendar of the device and the second access point.

[0011] In some embodiments, the apparatus may further include: components for negotiating terms of association between the device and the second access point, including components for sending user association records of the device to the second access point.

[0012] In some embodiments, a user association record may include at least one of the following: the device’s Media Access Control (MAC) address, the protocol version used by the device, the device’s operating frequency band, the device’s at least one channel width capability, the device’s support for at least one specific feature, and at least one requirement associated with the device.

[0013] In some embodiments, the device may further include a component for monitoring the association between the device and the second access point.

[0014] In some embodiments, the components for monitoring the association between the device and the second access point may include components for tracking at least one performance indicator of the association. The performance indicator may include at least one of the following: latency of the wireless connection between the device and the second access point, usage of the wireless connection between the device and the second access point, and minimum received signal strength indicator (RSSI) of the wireless connection between the device and the second access point.

[0015] In some embodiments, the apparatus may further include: a component for sending a deassociation request to a second access point to terminate the association between the device and the second access point. In some embodiments, the apparatus may further include: a component for receiving confirmation of the deassociation request from the second access point.

[0016] According to a second aspect, an apparatus is described, comprising components for: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; sending a discovery request to the first access point, wherein the discovery request includes: an inquiry regarding whether the first access point will accept a transfer of association with the device; receiving a discovery response from the first access point, the discovery response indicating that: the first access point accepts the discovery request to transfer the association with the device; and negotiating terms between the first access point and the second access point regarding the association between the device and the second access point.

[0017] In some embodiments, the apparatus may further include: a component for authorizing the association between the device and a second access point, wherein the authorization includes: receiving user association information for the device from a first access point.

[0018] In some embodiments, the device may be a second access point.

[0019] In some embodiments, the components for determining that the first access point and the second access point are in a coordination protocol may include components for determining that the first access point and the second access point are part of a Multi-Access Point Coordination (MAPC) group.

[0020] In some embodiments, the user association information of the device may include at least one of the following: the device’s unique identifier, the device’s Media Access Control (MAC) address, and the terms of association between the device and the second access point.

[0021] In some embodiments, at least one of the discovery request or discovery response may include at least one association capability for association between the second access point and the device.

[0022] In some embodiments, at least one associated capability includes at least one of the following: the operating frequency band of the device, the maximum number of devices to be supported, the minimum received signal strength indicator (RSSI) of the device, the maximum bandwidth to be shared with the device, and the shared availability calendar of the device and the second access point.

[0023] In some embodiments, the components for negotiating the terms of the association between the device and the second access point may include: components for receiving user association records of the device from the first access point.

[0024] In some embodiments, a user association record may include at least one of the following: the device’s Media Access Control (MAC) address, the protocol version used by the device, the device’s operating frequency band, the device’s at least one channel width capability, the device’s support for at least one specific feature, and at least one requirement associated with the device.

[0025] In some embodiments, the device may further include a component for monitoring the association between the device and the second access point.

[0026] In some embodiments, the components for monitoring the association between the device and the second access point may include components for tracking at least one performance indicator of the association. The performance indicator may include at least one of the following: latency of the wireless connection between the device and the second access point, usage of the wireless connection between the device and the second access point, and minimum received signal strength indicator (RSSI) of the wireless connection between the device and the second access point.

[0027] In some embodiments, the apparatus may further include: a component for sending a deassociation request to a first access point to terminate the association between the device and a second access point. In some embodiments, the apparatus may further include: a component for receiving confirmation of the deassociation request from the first access point.

[0028] According to a third aspect, an apparatus is described, comprising components for: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; identifying that the device is located in an overlay vulnerability of the first access point; sending a request to the first access point or the second access point to transfer the association between the device and the first access point to the second access point; and initiating the association between the device and the second access point.

[0029] In some embodiments, the device may be the equipment.

[0030] In some embodiments, the apparatus may further include at least one of the following: a component for monitoring the association between the device and the second access point; a component for sending a deassociation request to the first access point or the second access point to terminate the association between the device and the second access point; or a component for receiving confirmation of the deassociation request from the first access point or the second access point.

[0031] According to a fourth aspect, a method is described, the method comprising: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; sending a discovery request to the second access point, the discovery request including an inquiry as to whether the second access point will accept a transfer of association with the device; receiving a discovery response from the second access point, the discovery response indicating that the second access point accepts the discovery request to transfer the association with the device; negotiating terms between the first access point and the second access point for the association between the device and the second access point; and authorizing the association between the device and the second access point, the authorization including sending user association information of the device to the second access point.

[0032] According to a fifth aspect, a method is described, the method comprising: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; sending a discovery request to the first access point, the discovery request including: an inquiry regarding whether the first access point will accept a transfer of association with the device; receiving a discovery response from the first access point, the discovery response indicating that: the first access point accepts the discovery request to transfer the association with the device; negotiating terms between the first access point and the second access point for the association between the device and the second access point; and authorizing the association between the device and the second access point, the authorization including: receiving user association information of the device from the first access point.

[0033] According to the sixth aspect, a method is described, the method comprising: determining that a first access point and a second access point are in a coordination protocol; determining that an association exists between a device and the first access point; identifying that the device is located in an overlay vulnerability of the first access point; sending a request to the first access point or the second access point to transfer the association between the device and the first access point to the second access point; and initiating the association between the device and the second access point.

[0034] According to a seventh aspect, a computer program product is provided, the computer program product including an instruction set that, when executed on a device, is configured to cause the device to perform any of the methods defined in the foregoing method.

[0035] According to the eighth aspect, a non-transitory computer-readable medium is provided, the medium including program instructions stored thereon for performing any of the methods defined above. Attached Figure Description

[0036] Exemplary embodiments will now be described by way of non-limiting example with reference to the accompanying drawings, in which:

[0037] Figure 1 The network architecture of a Wi-Fi communication system is illustrated as an example;

[0038] Figure 2 The coverage vulnerability is illustrated with an example;

[0039] Figure 3 The coverage vulnerability is illustrated with an example;

[0040] Figure 4 The relationship between the AP and the device is illustrated with an example;

[0041] Figure 5 The association transfer process is illustrated with an example;

[0042] Figure 6 The first method for association transfer is illustrated by example;

[0043] Figure 7 A second method for association transfer is illustrated by way of example;

[0044] Figure 8 A multi-access point coordination management frame is shown as an example;

[0045] Figure 9A The discovery message is shown as an example; Figure 9B The discovery response message is shown as an example;

[0046] Figure 10 The negotiation message is shown as an example;

[0047] Figure 11 The completion message is shown as an example;

[0048] Figure 12 Monitoring messages are shown as examples;

[0049] Figure 13A The termination message is shown as an example; Figure 13B The termination confirmation message is shown as an example;

[0050] Figure 14 A third method for association transfer is illustrated by way of example; and

[0051] Figure 15 A block diagram of the device is shown as an example. Detailed Implementation

[0052] Coverage holes are a major source of customer complaints for Wi-Fi providers and Internet Service Providers (ISPs). A coverage hole is an area in which an access point (AP) or base station (BS) is unable to provide acceptable service to its associated users due to poor signal propagation, such as attenuation caused by the medium and physical obstacles.

[0053] Commercial Wi-Fi access points (APs) can include proprietary coverage vulnerability detection and mitigation mechanisms, implemented at the Radio Resource Management (RRM) level. A major drawback of existing methods is that they perform coverage vulnerability mitigation through adaptive transmit power, thus attempting to address potential detection vulnerabilities by increasing transmit power levels to cover the maximum possible area and reach all devices wishing to connect to the AP. This approach can increase interference, as APs tend to use higher power, which can severely impact the performance of Overlapping Basic Service Sets (OBSS). Furthermore, even with maximum power, the AP can still reach limited coverage areas. Therefore, coverage vulnerability mitigation cannot be guaranteed, and improved technologies are needed.

[0054] Figure 1An example embodiment of a communication system 100 is depicted, comprising a Wi-Fi access point 120, a Wi-Fi client 110, and a controller 130 configured to control the association between the Wi-Fi client and the Wi-Fi access point. Figure 1 The example embodiment of the communication system 100 is an illustration of a possible Wi-Fi system provided for the background information disclosed herein. Figure 1 The communication system 100 is not intended to provide any limitation on this disclosure.

[0055] The communication system 100 includes Wi-Fi client sets 110-1 to 110-C (collectively referred to as Wi-Fi clients 110), Wi-Fi access point sets (APs) 120-1 to 120-A (collectively referred to as WiFi APs 120), a Wi-Fi access controller 130, and a communication network 140. Wi-Fi clients 110 can associate with Wi-Fi APs 120 based on Wi-Fi access control functions supported by the Wi-Fi access controller 130 to obtain network access to the communication network 140. Alternatively, each Wi-Fi AP 120 can operate autonomously and / or independently. For example, each Wi-Fi AP 120 can have its own Wi-Fi access controller (not shown). The communication network 140 accessed by Wi-Fi client 110 via Wi-Fi AP 120 may include any (multiple) communication networks that can be used by Wi-Fi client 110, such as public communication networks, private communication networks, and various combinations thereof (e.g., Internet-related networks, enterprise networks, data center networks, and various combinations thereof).

[0056] Wi-Fi client 110 includes any device that can be associated with Wi-Fi AP 120 to obtain network access to communication network 140. Wi-Fi client 110 may support one or more of various IEEE 802.11 standards, such as 802.11 (Wi-Fi 0, 2.4GHz), 802.11b (Wi-Fi 1, 2.4GHz), 802.11a (Wi-Fi 2, 5GHz), 802.11g (Wi-Fi 3, 5GHz), 802.11n (Wi-Fi 4, 2.4 / 5GHz), 802.11ac (Wi-Fi 5, 5GHz), 802.11ax (Wi-Fi 6, 2.4 / 5 / 6GHz), 802.11b (Wi-Fi 1, 2.4GHz), and 802.11be (Wi-Fi 7, 2.4 / 5 / 6GHz). Wi-Fi client 110 can support one or more Wi-Fi radio frequency bands (e.g., single-band, dual-band, tri-band, etc.), which can be used by Wi-Fi client 110 for communication with Wi-Fi AP 120 (e.g., one or more of 2.4GHz, 5GHz, 6GHz, etc.). Figure 1 In the examples, for clarity, each Wi-Fi client 110 is depicted as a dual-band device supporting the 2.4 GHz and 5 GHz bands; however, it should be understood that Wi-Fi client 110 may include single-band devices (e.g., supporting only one of 2.4 GHz, 5 GHz, 6 GHz, etc.), multi-band devices supporting other numbers or combinations of Wi-Fi radio bands, and various combinations thereof. Wi-Fi client 110 may also be referred to interchangeably as a "device" herein. For example, Wi-Fi client 110 / device may include computers, smartphones, televisions, home control devices, appliances, Internet of Things (IoT) devices, etc.

[0057] The latest IEEE 802.11be standard introduces an architecture that allows multiple frequency bands to operate concurrently by a single entity called a multi-link device (MLD). The MLD communicates with both the Wi-Fi AP 120 and the Wi-Fi client 110.

[0058] The Wi-Fi AP 120 is configured to support communication between Wi-Fi clients 110 and the communication network 140. The Wi-Fi AP 120 can support one or more of various IEEE standards, such as 802.11 (Wi-Fi 0, 2.4 GHz), 802.11b (Wi-Fi 1, 2.4 GHz), 802.11a (Wi-Fi 2, 5 GHz), 802.11g (Wi-Fi 3, 5 GHz), 802.11n (Wi-Fi 4, 2.4 / 5 GHz), 802.11ac (Wi-Fi 5, 5 GHz), 802.11ax (Wi-Fi 6, 2.4 / 5 / 6 GHz), 802.11b (Wi-Fi 1, 2.4 GHz), and 802.11be (Wi-Fi 7, 2.4 / 5 / 6 GHz). Wi-Fi AP 120 may support one or more Wi-Fi radio frequency bands, which can be used by Wi-Fi client 110 for communication with Wi-Fi AP 120 (e.g., one or more of 2.4GHz, 5GHz, 6GHz, etc.). Each Wi-Fi AP 120 supports a set of Wi-Fi radios 121 (illustratively, Wi-Fi AP 120-1 supports Wi-Fi radios 121-11 and 121-12, and Wi-Fi AP 120-A supports Wi-Fi radios 121-A1 and 121-A2), which are configured to support Wi-Fi-based communication with Wi-Fi client 110. Figure 1 In the examples, for clarity, each Wi-Fi AP 120 is depicted as a dual-band device supporting the 2.4 GHz and 5 GHz bands; however, it should be understood that the Wi-Fi AP 120 may include a single-band device (e.g., supporting only one of 2.4 GHz, 5 GHz, 6 GHz, etc.), a multi-band device supporting other numbers or combinations of Wi-Fi radio bands, and various combinations thereof. The Wi-Fi AP 120 is configured to support control over the association between the Wi-Fi client 110 and the Wi-Fi AP 120. The Wi-Fi AP is configured to support control over the association between the Wi-Fi client 110 and the Wi-Fi AP 120 by receiving an association request from the Wi-Fi client 110, in which the Wi-Fi client 110 requests association with a specific Wi-Fi radio band of the Wi-Fi AP 120, and the Wi-Fi AP 120 accepts or rejects the association request to allow or block the association between the Wi-Fi client 110 and the Wi-Fi AP 120. It should be understood that the Wi-FiAP 120 can also be referred to as a Wi-Fi router in this article.

[0059] Wi-Fi access controller 130 can be configured to support control over the association between Wi-Fi client 110 and Wi-Fi AP 120. Wi-Fi access controller 130 can be configured to support control over the association between Wi-Fi client 110 and Wi-Fi AP 120 based on Wi-Fi access control information 131, which is determined by Wi-Fi access controller 130 (shown as Wi-Fi access control information 131 maintained on Wi-Fi access controller 130) and provided by Wi-Fi access controller 130 to Wi-Fi AP 120 for use by Wi-Fi AP 120 in controlling the association between Wi-Fi client 110 and Wi-Fi AP 120. The Wi-Fi access control information 131 maintained on Wi-Fi AP 120 can be used by Wi-Fi AP 120 when processing association requests from Wi-Fi client 110, thereby enabling Wi-Fi AP 120 to control the association between Wi-Fi client 110 and Wi-Fi AP 120, as well as the Wi-Fi radio band of Wi-Fi AP 120. In some Wi-Fi communication systems, association control can be performed directly by the Wi-Fi client 110 attempting to associate with the Wi-Fi AP 120. In other Wi-Fi communication systems, association control can be implemented through a centralized system (e.g., using 802.1x), where a server manages user associations. In a centralized system, Wi-Fi AP 120 can simply forward association requests to the server. The disclosure herein can be applied to both methods of controlling associations.

[0060] Figure 2 An example embodiment of a communication system including Wi-Fi access point 1 (AP1) 201, Wi-Fi access point 2 (AP2) 202, and device 203 is depicted. AP1 201 and AP2 202 can correspond to, for example... Figure 1 The Wi-Fi AP 120 shown here can also be referred to as a Wi-Fi router. Device 203 can be as follows: Figure 1One of the Wi-Fi clients 110 shown. Device 203 can be a portable computing device including communication devices, including but not limited to the following types of devices: mobile station (mobile phone), smartphone, personal digital assistant, handheld device, device using a wireless modem (alarm or measuring device, etc.), laptop and / or touchscreen computer, tablet, game console, laptop, vehicle, fixed wireless access (FWA), and multimedia device. It should be understood that device 203 can also be a virtually exclusive uplink-only device, an example of which is a camera or camcorder used to load images or video clips onto the network. Device 203 can also be a device capable of operating in an Internet of Things (IoT) network, in which case objects can transfer data over the network without human-to-human or human-to-computer interaction.

[0061] Figure 2 The example embodiments shown can be located in any building (such as a house, commercial building, or apartment building), or alternatively, outdoors.

[0062] AP1 201 and device 203 are in a first communication session, and therefore device 203 is authenticated and associated with AP1 201. Authentication and / or association can be performed via known mechanisms and standardized messages, such as probe requests and responses, authentication requests and responses, and association requests and responses. Device 203 is currently unauthenticated or not associated with AP2 202.

[0063] AP1 201 and AP2 202 are both within a coordination protocol. This coordination protocol can be formally defined through the MAPC group. MAPC (Multi-Access Point Coordination Scheme) will be incorporated into Wi-Fi 8, and standardization work on Wi-Fi 8 has begun and is expected to be completed in the future. Therefore, AP1 201 and AP2 202 can share information about associated and certified devices (e.g., device 203). An association protocol (e.g., a MAPC group) indicates that AP1 201 and AP2 202 can communicate with each other using MAPC-specific signaling. Other access points (not shown) can form part of the MAPC group.

[0064] AP1 201 has a high coverage area 204 and a low coverage area 205, where the high coverage area has the strongest radio signal and the low coverage area has a weaker radio signal. Device 203 is located in a coverage gap area 206 of AP1 201. A coverage gap in AP1 201 is an area not covered by AP1 201, meaning that the signal strength of AP1 is insufficient to reach the area where device 203 is located. AP2 also has a high coverage area 207 with a stronger signal. Device 203 is located within the high coverage area 207 of AP2 202, and therefore, it would be ideal if the device could use AP2 202 instead of AP1 201 to provide improved service. Although AP2 202 is not currently certified or associated with device 203, the proposed apparatus and method provide a solution for allowing this via a coordination protocol.

[0065] Figure 3 Another example embodiment of the communication system is shown. Figure 3 middle, Figure 2 An example is shown as an apartment building for demonstration purposes. The coverage vulnerability area 206 of AP1 201 is located in apartment 1, where the signal strength of AP1 201 is insufficient to reach device 203. However, AP2 202 in apartment 2 can have sufficient signal strength to serve device 203 in the coverage vulnerability area.

[0066] By leveraging the advantages of MAPC in Wi-Fi 8, this paper presents a novel coverage vulnerability mitigation method that allows association transfer between AP1 201 and AP2 202. Through the MAPC framework, private APs enable the exchange and transfer of user associations between them. The proposed method is highly relevant to residential scenarios, such as... Figure 3 The example illustrates how multiple private APs can be leveraged to provide a better overall user experience, although the proposed scheme can also be used in many other scenarios. The proposed method also complements mesh deployments. Mesh Wi-Fi networks consist of multiple devices that supplement the functionality of an access point compared to a single access point device, providing seamless connectivity for users in a larger area. Mesh deployment offers a method for extending coverage and providing enhanced performance; however, the proposed method ensures a significantly increased chance of service by at least one AP in the coordination protocol should a device eventually fall into a coverage gap, thus preventing customer complaints.

[0067] like Figure 4As shown in the illustration, further demonstration illustrates the relationship between the first access point 401, the second access point 402, and the device 403. The first access point 401 and the second access point 402 can be access point multilink devices (AP-MLDs). The device 403 is a non-access point multilink device (non-AP-MLD). The first access point 401 (AP-MLD1) is authenticated and associated with the device 403 (e.g., ...). Figure 4 (As shown by the solid line in the diagram). Authentication and / or association can be performed via known mechanisms and standardized messages, such as probe requests and responses, authentication requests and responses, and association requests and responses. Second access point 402 (AP-MLD2) is currently not authenticated or associated with device 403, although potential temporary association is possible (e.g., ...). Figure 4 (As shown by the dashed line in the image).

[0068] AP-MLD1 401 and AP-MLD2 402 are both within a coordination protocol. This coordination protocol can be a MAPC group. MAPC (Multi-Access Point Coordination Scheme) will be incorporated into Wi-Fi 8, and standardization work on Wi-Fi 8 has begun and is expected to be completed in the future. Therefore, AP-MLD1 401 and AP-MLD2 402 can share information about associated and certified devices (e.g., device 403). An association protocol (e.g., a MAPC group) indicates that AP-MLD1 401 and AP-MLD2 402 can communicate with each other using MAPC-specific signaling. Therefore, AP-MLD1 401 and AP-MLD2 402 can communicate via coordination signaling, whether over the air or using a wired connection (e.g., ...). Figure 4 (As shown by the dashed arrow in the diagram). Additional AP-MLDs (not shown) can also form part of the MAPC group.

[0069] Coverage vulnerabilities can negatively impact a user's Wi-Fi experience because they can cause radio link failures when a user moves to an area with poor coverage. Therefore, in Wi-Fi and wireless networks, it is crucial to mitigate the impact of coverage vulnerabilities by allowing device association transfers between access points (APs).

[0070] The disclosure herein aims to transfer associations to allow device 403 to seamlessly connect to other AP-MLDs that are different from the AP-MLDs to which they explicitly perform authentication and association. Two approaches are discussed herein. The first approach involves an association transfer initiated by a 'host AP', where the 'host AP' (e.g., AP-MLD1 401) shares its association with the device with other AP-MLDs (e.g., AP-MLD2 402) within the same coordination group. The second approach involves an association transfer initiated by a 'visited AP', where the 'visited AP' (e.g., AP-MLD2 402) logs in and serves new users of other APs (e.g., AP-MLD1 401) within the same coordination group.

[0071] Association sharing requests can be triggered for various reasons. For example, combining... Figure 2 and Figure 3 One relevant example discussed is addressing coverage vulnerabilities, although other reasons are also possible. After reporting higher signal quality perceived from the 'visited AP', the 'host AP' can decide to share its association with the 'visited AP'.

[0072] Figure 5 An overview of the proposed association transfer process between AP-MLD1 401 and AP-MLD2 402 and device 403 is illustrated with examples. The proposed coverage vulnerability mitigation process consists of several steps, including Prerequisite 1, Prerequisite 2, Step 1 – User Association Transfer Discovery, Step 2 – User Association Transfer Negotiation, Step 3 – User Association Transfer Completion, Step 4 – User Association Transfer Monitoring, and Step 5 – User Association Transfer Termination. Each step in these steps will be discussed sequentially below, combining "host AP-initiated" and "visited AP-initiated" association transfers.

[0073] Association transfer initiated by the host AP.

[0074] Figure 6 A flowchart of method 600 according to an exemplary embodiment is shown by way of example. Each element of the flowchart may include one or more operations. These operations may be performed in hardware, software, firmware, or a combination thereof. For example, these operations may be performed individually or collectively by a component, wherein the component may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the operations to be performed.

[0075] Method 600 can be performed by a host AP (e.g., AP-MLD1 401). This can be referred to herein as a 'host AP-initiated' association transfer. The motivation for method 600 is an association transfer performed at a 'host AP' that has been previously authenticated and associated with device 403 and is in a coordination protocol with the visited AP (e.g., AP-MLD2 402).

[0076] Figure 6 Method 600 includes a first operation 601 of determining that a first access point AP-MLD1 401 and a second access point AP-MLD2 402 are in a coordination protocol. The first operation 601 may include determining that AP-MLD1 401 and AP-MLD2 402 are part of a MAPC group. In other words, the coordination protocol may be a MAPC coordination protocol. This means that AP-MLD1 401 and AP-MLD2 402 can communicate with each other using MAPC-specific signaling. Determining that AP-MLD1 401 and AP-MLD2 402 are in a coordination protocol is a first prerequisite for method 500 (e.g., as...). Figure 5 (as shown in "Prerequisite 1").

[0077] Figure 6 Method 600 includes a second operation 602 of determining an association between device 403 and AP-MLD1 401. Determining an association between device 403 and AP-MLD1 401 may include determining that device 403 and AP-MLD1 401 are in a current wireless communication session, and / or that it is otherwise associated with device 403 and / or has been authenticated by AP-MLD1 401. Therefore, AP-MLD1 401 trusts device 403. Determining that device 403 is associated with AP-MLD1 401 and has been authenticated by AP-MLD1 401 is a second prerequisite for method 600 (e.g., as...). Figure 5 (as shown in "Prerequisite 2").

[0078] Figure 6 Method 600 further includes a third operation 603: sending a discovery request to AP-MLD2 402. The discovery request includes an inquiry regarding whether AP-MLD2 402 will accept a transfer of association with device 403. The discovery request proposes a transfer of association with device 403 to AP-MLD2 402. The purpose of the discovery request is to initiate a user association transfer by discovering a coordinating AP-MLD that may be a peer willing to serve a user of device 403. The third operation 603 is performed by, for example... Figure 5 The “1a Push-based Discovery Push” shown in the diagram illustrates this. During the third operation 603, AP-MLD1 401 sends a push message with a user association transfer request to AP-MLD2 402.

[0079] Figure 6 The method 600 further includes a fourth operation 604 of receiving a discovery response from AP-MLD2 402, the discovery response indicating that AP-MLD2 402 accepts the discovery request to transfer association with the device 403. In other words, AP-MLD2 402 responds with a decision (accept or reject). The fourth operation 604 is as follows: Figure 5 The “1b Push-based Discovery Push Response” shown is illustrated. The discovery response may optionally include the reason for a potential rejection of the requested user association transfer and other relevant information. In the event of rejection, the method will cease, and AP-MLD1 401 will continue searching for a suitable AP-MLD where the association can be transferred.

[0080] Discovery requests and / or discovery responses may include at least one association capability between AP-MLD2 402 and device 403. The purpose of association capabilities is to allow AP-MLD1 401 to express to the potential transfer association AP-MLD2 402 the capabilities required to transfer the association of device 403 from AP-MLD1 401 to AP-MLD 402. Furthermore, AP-MLD2 402 may respond to AP-MLD1 401 by indicating whether it meets these desired association capabilities. At least one association capability may include at least one of the following: the operating frequency band of device 403, the maximum number of devices 403 to be supported, the minimum Received Signal Strength Indicator (RSSI) of device 403, the maximum bandwidth to be shared with the device, and the shared availability calendar of device 403 and AP-MLD2 402.

[0081] Figure 6 Method 600 further includes a fifth operation 605: negotiating the terms of association between device 403 and AP-MLD2 402 between AP-MLD1 401 and AP-MLD2 402. The fifth operation 605 is performed by, for example... Figure 5The section “2. User Association Transfer Negotiation” illustrates this. AP-MLD1 401 and AP-MLD2 402 negotiate terms and conditions under which AP-MLD2 402 can serve the associated device 403 to be transferred. The transfer negotiation includes: potential capabilities and compatibility requirements to be shared with each notification. Furthermore, the negotiation may include mechanisms for enforcing trust in the user association transfer (e.g., two-way interrogation to verify the legitimacy of the user association transfer). Negotiating the association terms between device 403 and AP-MLD2 402 may include sending the device's User Association Record (UAR) to AP-MLD2 402. The UAR may include at least one of the following: the Media Access Control (MAC) address of device 403, the protocol version used by device 403, the operating frequency band of device 403, at least one channel width capability of device 403, support for at least one specific feature by device 403, and at least one requirement for association with device 403. The UAR is used by AP-MLD2 402 to determine whether it can serve device 403. Other relevant information can be shared to further support user association transfers. Some examples are calendar information, which can indicate the periods during which AP-MLD2402 will be shut down so that AP-MLD1 401 can take over or reward data to incentivize association sharing.

[0082] Figure 6 Method 600 may also optionally include a sixth operation (not shown) of association between the authorized device 403 and AP-MLD2 402. The sixth operation 606 is performed by, for example... Figure 5 The “3. User Association Transfer Complete” instruction is shown. Authorization includes sending the device's user association information to AP-MLD2402. AP-MLD1 401 and AP-MLD2 402 exchange user association information and perform the user association transfer. For this, AP-MLD1 401 transfers the user's identifier, and service conditions must be provided to AP-MLD2402. AP-MLD2 402 creates a new association ID (AID) for each newly logged-in device 403 to distinguish different devices from which the association can be transferred. A successful user association transfer to AP-MLD2 402 can be confirmed using the status code of each shared association record (e.g., 1 if successful, 0 if unsuccessful).

[0083] The user association information of device 403 may include at least one of the following: the unique identifier of device 403, the media access control MAC address of device 403, and the terms of association between device 403 and AP-MLD2 402.

[0084] Figure 6Method 600 may optionally include additional operations to monitor the association between monitoring device 403 and AP-MLD2 402. Monitoring such as Figure 5 As shown in “4. User Association Transfer Monitoring”, the purpose of monitoring is to determine information to enable further decisions regarding the status of the transferred user association. Monitoring the association between device 403 and AP-MLD2 402 may include tracking at least one performance indicator (i.e., a key performance indicator) of the association. The performance indicator may include at least one of the following: latency of the wireless connection between device 403 and AP-MLD2 402, usage of the wireless connection between device 403 and AP-MLD2 402, and minimum received signal strength indicator (RSSI) of the wireless connection between device 403 and AP-MLD2 402. Therefore, AP-MLD1 401 may be able to determine, based on the performance indicator, whether to change the terms of the association transfer to AP-MLD2 402 or terminate the association transfer. Continuous monitoring of the connection between device 403 and AP-MLD2 402 allows for continuous evaluation of whether the association transfer is worthwhile and in the best interests of the device. Therefore, it may be decided to terminate the association transfer or move it to a different AP-MLD in the coordination protocol, which better meets the needs of device 403.

[0085] Figure 6 Method 600 may optionally include an additional operation, namely, sending a deassociation request to AP-MLD2 402 to terminate the association between device 403 and AP-MLD2 402, and receiving confirmation of the deassociation request from AP-MLD2 402. The deassociation request and confirmation are provided by, for example... Figure 5 The section “5a. Termination and Confirmation Initiated by Shared AP-MLD” illustrates this. Disassociation signaling can also be informational, as it may not require message passing of the disassociation request and confirmation type. This could occur, for example, if device 403 moves away from the coverage area or otherwise disconnects. In this case, AP-MLD2 402 can notify AP-MLD1 401 that device 403 has been disassociated. This is an association transfer initiated by the access AP.

[0086] Figure 7 A flowchart of method 700 according to an exemplary embodiment is shown by way of example. Each element of the flowchart may include one or more operations. These operations may be performed in hardware, software, firmware, or a combination thereof. For example, these operations may be performed individually or collectively by a component, wherein the component may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the operations to be performed.

[0087] Method 700 can be performed by the visited AP (e.g., AP-MLD2 402). This can be referred to herein as a 'visited AP-initiated' association transfer. The motivation for method 700 is an association transfer performed at the 'visited AP' (e.g., AP-MLD2 402) that is in a coordination protocol with the host AP (e.g., AP-MLD1 401). Device 403 is not yet associated with the 'visited AP' AP-MLD2 402; however, the method based on AP-MLD2 402 is used to request a transfer of association from AP-MLD1 401 to AP-MLD2 402.

[0088] Figure 7 Method 700 includes: a first operation 701 of determining that AP-MLD1 401 and AP-MLD2 402 are in a coordination protocol. Figure 7 The method 700 includes a second operation 702 of determining an association between device 403 and AP-MLD1 401. Figure 7 The first operation 701 and the second operation 702 are equivalent to Figure 6 The first operation 601 and the second operation, and also by Figure 5 The "Prerequisite 1" and "Prerequisite 2" shown are used to demonstrate this.

[0089] Figure 7 Method 700 includes a third operation 703 of sending a discovery request to AP-MLD1 401. The discovery request inquires whether AP-MLD1 401 will accept a transfer associated with device 403. The third operation 703 is performed by, for example... Figure 5 The “1b. Polling-based discovery polling request” shown in the figure is illustrated. Figure 7 Method 700 includes a fourth operation 704 of receiving a discovery response from AP-MLD1 401, the discovery response indicating whether AP-MLD1 401 accepts the discovery request to transfer the association with device 403. In other words, AP-MLD2 402 sends a polling message to AP-MLD1 401 with an association transfer request. AP-MLD1 401 then responds to the request affirmatively or negatively, also indicating a reason code (if applicable). The motivation for this polling-based method is that certain events for initiating a user association transfer can be triggered from the 'visited AP' AP-MLD2 402. The fourth operation 704 is as follows: Figure 5 The “1b Polling-based Discovery Polling Response” shown in the diagram illustrates this. A discovery request or response may also have at least one association capability, as previously discussed in conjunction with association transfers initiated by a 'host AP'.

[0090] Figure 7Method 700 includes a fifth operation 705: negotiating the terms of association between device 403 and AP-MLD2 402 (if the association is authorized) between AP-MLD1 401 and AP-MLD2 402. Negotiating the terms of association between device 403 and AP-MLD2 402 may include receiving the device's user association record from AP-MLD1 401. Figure 7 Method 700 may optionally include a sixth operation 706 (not shown) for components used to authorize the association between device 403 and AP-MLD2 402. Authorization includes receiving user association information of device 403 from AP-MLD1 401. Figure 7 Operations 705 and 706 are equivalent to Figure 6 The fifth operation 605 and the sixth operation 606, and also by, as Figure 5 The steps “2. User association transfer negotiation” and “3. Complete using association transfer” are shown in the diagram.

[0091] Figure 7 Method 700 may optionally include additional operations for monitoring the association between monitoring device 403 and AP-MLD2 402. Monitoring such as Figure 5 As shown in “4. User Association Transfer Monitoring”, the association between monitoring device 403 and AP-MLD2 402 may include at least one performance indicator (i.e., a key performance indicator) for tracking the association.

[0092] Figure 7 Method 700 may optionally include an additional operation, namely, sending a deassociation request to AP-MLD1 401 to terminate the association between device 403 and AP-MLD2 402, and receiving confirmation of the deassociation request from AP-MLD1 401. The deassociation request and confirmation are handled by, for example... Figure 5 The “5b. Termination and Confirmation Initiated by Shared AP-MLD” shown in the figure is illustrated.

[0093] The proposed method allows for benefits in both residential and industrial networks.

[0094] In residential networks, coverage vulnerabilities can be addressed through the transfer of associations between APs and MLDs, thereby improving the user experience in Wi-Fi. Consumers can decide whether to enable this proposed method and can determine the coordination group that will enable coordination (e.g., by manually importing the AP's ID from the home AP's configuration). Furthermore, in industrial networks, while some association transfer methods already exist, current association transfers occur in a semi-static manner. Using the proposed process implemented in a standard will allow for faster and more dynamic responses. A key advantage of the proposed method in both residential and industrial environments is that coordination occurs at the protocol level, utilizing standardized processes rather than proprietary ones, thus improving interoperability and potential benefits.

[0095] The proposed method requires the existence of a MAPC framework, which allows coordinated AP-MLDs to exchange specific signaling for various coordination use cases. For example... Figure 8 As shown, the general MAPC framework can be defined by MAPC management frame 800. MAPC management frame 800 is used by any type of established coordination mechanism to enable the necessary signaling. Figure 8 The proposed MAPC management frame 800 can be used to standardize user-associated transfer messages, thereby specifically enabling... Figure 6 and Figure 7 The method defined in [the document]. Figures 9 to 13 illustrate the methods for performing [the task]. Figure 6 and Figure 7 The content of the message in the steps.

[0096] like Figure 8 As shown, these messages can be defined in frame body 801 to enable specific types of coordination corresponding to user-associated transfers. The coordination type of the user-associated transfer is indicated in the coordination protocol field 802 of frame body 801. Different defined messages are identified by different values ​​in the message type field 803 of frame body 801. Furthermore, depending on the message type, the same message may include different information elements 804 (e.g., sending information about different devices).

[0097] Example found that request 900 was in Figure 9AThe following fields are shown: Coordination Protocol 901, Message Type 902, and AP-MLD Capability 903. For example, in a discovery request, Coordination Protocol 901 can be set to a “User Association Transfer” message, and Message Type 902 can indicate whether the discovery message is a discovery request initiated by the 'host AP' or the 'visited AP'. The AP-MLD Capability 903 field can include at least one association capability of the 'visited AP' to support users from the 'host AP'. The AP-MLD Capability 903 field can include the following information: the operating frequency band of the device, the maximum number of devices to be supported, the minimum Received Signal Strength Indicator (RSSI) of the device, the maximum bandwidth to be shared with the device (e.g., 10%), and the shared availability calendar of device 403 and AP-MLD2 402 (e.g., from 23h to 5h).

[0098] Example found 905 response in Figure 9B The discovery response 905 is shown and includes the following fields: Coordination Protocol 906, Message Type 907, Response Code 908, and AP-MLD Capability 909. For example, in the discovery response 905, Coordination Protocol 906 can be set to a "User Association Transfer" message, and Message Type 907 can indicate whether the discovery message is a discovery request initiated by the "host AP" or the "visited AP". The Response Code 908 field indicates whether AP-MLD is willing (e.g., set to 1) or unwilling (e.g., set to 0) to perform a user association transfer. The AP-MLD Capability 909 field may also include at least one association capability in response to at least one related capability requested in the discovery request.

[0099] Example negotiation message 1000 in Figure 10The message is shown and includes the following fields: Coordination Protocol 1001, Message Type 1002, at least one User Association Record (UAR) 1003, and Additional Information 1005. The negotiation message is used to exchange information and negotiate the terms of a potential user association transfer between coordinated APs-MLDs. For example, in negotiation message 1000, Coordination Protocol 1001 can be set to a “User Association Transfer” message, and Message Type 1002 can indicate that the message is a negotiation message, and optionally can indicate a subtype of the message, which may include, for example, messages for requesting information, renegotiating terms, or challenging other AP-MLDs (e.g., for enforcing trust). Additional Information field 1005 may include other relevant information to be shared to further support the user association transfer. Some examples of information shared in Additional Information field 1005 are calendar information indicating the periods during which the host AP will be shut down so that the visited AP can take over or reward data to incentivize association sharing. UAR field 1003 contains information about the specific device association to be transferred. If multiple devices have associations to be transferred, several UARs may be included in the same message. The UAR field 1003 may include information about the user address (or device address) 1006, user capabilities 1007, and user-specific additional information 1008. The user address 1006 includes the user's address and, in particular, may include the MAC address of the device to be transferred. The user capability field 1007 may indicate the capabilities of the device to be transferred. The user capability field 1007 includes information such as the protocol version used by the device (e.g., 802.11n / ac / ax), the device's operating frequency band (e.g., 2.4 GHz, 5 GHz), the device's at least one channel width capability (e.g., 20 MHz, 40 MHz), the device's support for at least one specific feature, and at least one requirement associated with the device. Depending on the use case and subtype of the negotiation message, the user-specific additional information field 1008 may include various information. Examples of information to be included in the user-specific additional information field 1008 are user service requirements, measurements from the host AP's perspective (e.g., RSSI perceived from the considered user), and analyses and statistics (e.g., user-specific service patterns).

[0100] Example completion message 1100 Figure 11 The following fields are shown: Coordination Protocol 1101, Message Type 1102, and at least one User-Associated Transfer Completion Element 1103. The completion message is used by the 'Host AP' to confirm the user's association with a transfer on an agreed 'Host AP' within the same MAPC group. The completion message 1100 can be equivalent to the following: Figure 6 and Figure 7The method for authorizing the association between the device and AP-MLD2 402 is discussed in steps 606 and 706. For example, in completion message 1100, coordination protocol 1101 can be set to a "User Association Transfer" message, and message type 1102 can indicate that the message is a completion message. The User Association Transfer completion message includes user association information. User association information may include the following items: a unique identifier for the device, the address of the device (i.e., user address 1106), and the terms of association between the device and the AP-MLD (i.e., user association terms UAT). The unique identifier may include a User Association Transfer ID (ATID) 1105. This ATID is used to manage association records between AP-MLDs. This identifier is different from the Association ID (AID) used by each AP-MLD to process user associations.

[0101] Example monitoring message 1200 Figure 12 The message is shown and includes the following fields: coordination protocol 1201, message type 1202, and at least one user association transfer monitoring element 1203. Monitoring message 1200 is used by the 'host AP' or 'visited AP' to exchange information about the performance of active user association transfers. For example, in a completion message 1200, coordination protocol 1201 can be set to a 'user association transfer' message, and message type 1202 can indicate that the message is a monitoring message, and optionally can indicate a subtype of the message, which may include, for example, a monitoring information request or a monitoring information response. User association transfer monitoring element 1203 can be sent for each device to be monitored. The same message may include several monitoring elements, including an ATID identifier 1205 for managing association records between APs and MLDs. User-associated transfer monitoring element 1203 may also include a user-associated transfer performance field 1206, which includes relevant monitoring information, including various key performance indicators such as the delay of the wireless connection between the device and the AP-MLD, the usage of the wireless connection between the device and the AP-MLD, and the minimum received signal strength indicator RSSI of the wireless connection between the device and the AP-MLD.

[0102] Example of unlinking message 1300 Figure 13AThe deassociation message 1300 is shown and includes the following fields: coordination protocol 1301, message type 1302, and at least one user association transfer termination element 1303. The deassociation message 1300 is used by the 'host AP' or 'visited AP' to notify of the termination of the association transfer. For example, in the deassociation message 1300, coordination protocol 1301 can be set to a 'user association transfer' message, and message type 1302 can indicate that the message is for termination. For each user association transfer to be terminated, a user association transfer termination element 1303 can be sent. Several termination elements can be included in the same UAT termination message. The user association transfer termination element 1303 can include a user ATID 1305 used to identify the device to be deassociated. The user ATID 1305 is used to manage association records between APs and MLDs. The user association transfer termination element 1303 can also include a reason code 1306 provided to indicate the reason for deassociation. Example reason codes are described in Table 1.

[0103] Example confirmation message 1350 Figure 13B The acknowledgment message 1350 is shown and includes the following fields: coordination protocol 1351, message type 1352, and status code 1353. The acknowledgment message 1350 can be used to acknowledge either the completion message 1100 or the deassociation message 1300. For example, in the acknowledgment message 1300, coordination protocol 1351 can be set to a "user association transfer" message, and message type 1352 can indicate that the message is an acknowledgment. The acknowledgment message 1350 includes a detailed status code 1353 for each receiving user's association sharing record. Status code 1353 indicates the result of the acknowledgment message provided. Example status codes are described in Table 2.

[0104] User-associated transfer codes are used to provide details about the decisions made by a given AP-MLD when receiving a specific request from another coordinating AP-MLD. WLAN status codes (16-bit fields) are utilized and extended to support the proposed user-associated transfer mechanism.

[0105] Tables 1 and 2 describe the complete list of codes.

[0106]

[0107]

[0108] Table 1: WLAN reason codes, expanded to support user association transfer.

[0109]

[0110]

[0111] Table 2: WLAN status codes, expanded to support user association transfer.

[0112] Device perspective of associated transfer

[0113] For completeness, the following will combine... Figure 14 Provides a 403 perspective on the device for mitigating the coverage vulnerability.

[0114] Figure 14 A flowchart of method 1400 according to an exemplary embodiment is shown by way of example. Each element of the flowchart may include one or more operations. These operations may be performed in hardware, software, firmware, or a combination thereof. For example, these operations may be performed individually or collectively by a component, wherein the component may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the aforementioned operations to be performed.

[0115] Method 1400 can be performed by device 403.

[0116] Method 1400 may include a first operation 1401 of determining that AP-MLD1 401 and AP-MLD2 402 are in a coordination protocol. This can be achieved by device 403 actively sending a probe request with fields related to the MAPC packet, or passively by eavesdropping on beacons from AP-MLD1 401 or AP-MLD2 402 indicating information about the MAPC packet.

[0117] Method 1400 may include a second operation 1402 determining an association between device 403 and AP-MLD1 401.

[0118] Method 1400 may include a third operation 1403 identifying the device as being located in a coverage vulnerability in AP-MLD1 401. Device 403 can naturally become aware of this information due to a failed wireless communication session or degraded service quality. The discovery of the coverage vulnerability will trigger device 403 to search for an alternative AP-MLD for association.

[0119] Method 1400 may include a fourth operation 1404 of sending a request to MLD1 401 and / or AP-MLD2 402 to transfer the association of device 403 with MLD1 401 to AP-MLD2 402.

[0120] Method 1400 may include a fifth operation 1405: initiating the association between device 403 and AP-MLD2 402. Therefore, the association between device 403 and AP-MLD2 402 is authorized.

[0121] Optionally, method 1400 may further include: monitoring the quality of the service provided by AP-MLD2 402. Device 403 may send information about the monitoring activity to AP-MLD1 401. Device 403 may also send consistency signals to AP-MLD2 402, which may forward them to AP-MLD1 401, which will then make decisions such as disconnecting device 403 from AP-MLD2 402. In this case, device 403 may revert to its previous association with AP-MLD1 401.

[0122] Optionally, method 1400 may further include: device 403 selecting to unassociate with AP-MLD2 402, and device 403 may also indicate: a reason code related to a specific circumstance of the coverage vulnerability mitigation (e.g., not required to be satisfied in the coverage vulnerability). Device 403 can return to its home by reassociating with AP-MLD1 401, and may provide a summary of past sessions with AP-MLD2 402. For example, device 403 may provide a report on past sessions. AP-MLD1 401 may use this information to make decisions in the future (e.g., based on the quality of service of transferring associations, not transferring more associations to a given AP).

[0123] Example device

[0124] Figure 15 A block diagram of an apparatus capable of performing the methods(s) disclosed herein is shown by way of example. Device 1500 is shown, which may include, for example, a mobile communication device, such as... Figure 2 AP1 201 and / or AP2 202 and / or device 203. Device 1500 includes processor 1510, which may include, for example, a single-core or multi-core processor, wherein a single-core processor includes one processing core and a multi-core processor includes more than one processing core. Processor 1510 may typically include a control device. Processor 1510 may include more than one processor. Processor 1510 may be a control device. Processor 1510 may include at least one application-specific integrated circuit (ASIC). Processor 1510 may include at least one field-programmable gate array (FPGA). Processor 1510 may be a component for performing method steps in device 1500. Processor 1510 may be configured at least partially by computer instructions to perform actions.

[0125] A processor may include, or be configured as, one or more circuit systems configured to perform various stages of the methods according to the example embodiments described herein. As used herein, the term “circuit system” may refer to one or more or all of the following: (a) a purely hardware circuit implementation, such as an implementation solely in analog and / or digital circuit systems; and (b) a combination of hardware circuitry and software, such as, where applicable: (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware; and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories having software that work together to enable a device (such as a mobile phone or network node) to perform various functions; and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0126] This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term circuit system also covers only the implementation of hardware circuitry or a processor (or multiple processors) or portions thereof, and their accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0127] Device 1500 may include memory 1520. Memory 1520 may include random access memory and / or permanent memory. Memory 1520 may include at least one RAM chip. Memory 1520 may include, for example, solid-state, magnetic, optical, and / or holographic memory. Memory 1520 may be at least partially accessible by processor 1510. Memory 1520 may be at least partially included in processor 1510. Memory 1520 may be a component for storing information. Memory 1520 may include instructions, such as computer instructions, that processor 1510 is configured to execute. When instructions configured to cause processor 1510 to perform certain actions are stored in memory 1520, and device 1500 as a whole is configured to run using instructions from memory 1520 under the guidance of processor 1510, processor 1510 and / or at least one of its processing cores may be considered to be configured to perform some of the aforementioned actions. Memory 1520 may be at least partially located outside device 1500, but may be accessible by device 1500.

[0128] Device 1500 may include a transmitter 1530. Device 1500 may include a receiver 1540. Transmitter 1530 and receiver 1540 may be configured to transmit and receive information according to at least one cellular or non-cellular standard, respectively. Transmitter 1530 may include more than one transmitter. Receiver 1540 may include more than one receiver. Transmitter 1530 and / or receiver 1540 may be configured to operate according to standards such as GSM, WCDMA, 5G, LTE, IS-95, WLAN (e.g., Wi-Fi), Ethernet, and / or WiMAX.

[0129] Device 1500 may include a user interface (UI) 1560. UI 1560 may include at least one of the following: a display, a keyboard, a touch screen, a vibrator arranged to signal to a user by causing device 1500 to vibrate, a speaker, and a microphone.

[0130] Device 1500 may include or be arranged to accept a subscriber identity module 1570. Subscriber identity module 1570 may include, for example, a subscriber identity module SIM card that can be installed in device 1500. Subscriber identity module 1570 may include subscription information identifying the user of device 1500. Subscriber identity module 1570 may include password information that can be used to verify the identity of the user of device 1500 and / or facilitate the encryption of communication information.

[0131] Processor 1510 may be equipped with a transmitter arranged to output information from processor 1510 to other devices included in device 1500 via electrical wires within device 1500. Such a transmitter may include a serial bus transmitter arranged to output information to memory 1520 for storage, for example, via at least one electrical wire. Alternatively, the transmitter may include a parallel bus transmitter. Similarly, processor 1510 may include a receiver arranged to receive information from other devices included in device 1500 within processor 1510 via electrical wires within device 1500. Such a receiver may include a serial bus receiver arranged to receive information from receiver 1540, for example, via at least one electrical wire for processing within processor 1510. Alternatively, the receiver may include a parallel bus receiver.

[0132] Processor 1510, memory 1520, transmitter 1530, receiver 1540, NFC transceiver 1550, UI 1560, and / or user identity module 1570 can be interconnected in various ways via electrical wires within device 1500. For example, each of the above devices can be individually connected to a main bus within device 1500 to allow the devices to exchange information. However, those skilled in the art will understand that this is only one example, and various methods can be selected for interconnecting at least two of the above devices according to embodiments.

[0133] Unless otherwise stated or explicitly stated from the context, different claims by two entities indicate that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this specification may be based on different hardware, or some or all entities may be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this specification may be based on different software, or some or all entities may be based on the same software. Each entity described in this specification may be implemented in the cloud.

[0134] The term "component" as used in the specification and claims may refer to one or more individual elements configured to perform one or more corresponding functions, or it may refer to several elements for performing such one or more functions. Furthermore, the functions recited in the claims may be performed by the same individual components or combinations of the same components. For example, performing one or more such functions in a device may be caused by a processor executing instructions stored in the memory of the device.

[0135] As a non-limiting example, implementations of any of the blocks, devices, systems, techniques, or methods described above include hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or combinations thereof. Some embodiments may be implemented in the cloud. It should be understood that the foregoing is currently considered merely as an example. However, it should be noted that the description of these embodiments is given by way of example only, and various modifications may be made without departing from the scope defined by the appended claims.

Claims

1. A device for communication, comprising: Components used to determine whether the first access point and the second access point are in the coordination protocol; Components used to determine the association between the device and the first access point; A component for sending a discovery request to the second access point, wherein the discovery request includes an inquiry about whether the second access point will accept the associated transfer with the device; Components for receiving a discovery response from the second access point, the discovery response indicating that the second access point accepts the discovery request to transfer the association with the device; as well as A component for negotiating the terms of the association between the device and the second access point between the first access point and the second access point.

2. The apparatus according to claim 1, further comprising: A component for authorizing the association between the device and the second access point, wherein the authorization includes sending user association information for the device to the second access point.

3. The apparatus according to any one of the preceding claims, wherein the component for determining that the first access point and the second access point are in the coordination protocol comprises: A component used to determine that the first access point and the second access point are part of a Multi-Access Point Coordination (MAPC) group.

4. The apparatus according to any one of the preceding claims, wherein the user association information of the apparatus includes at least one of the following: The unique identifier of the device; The media access control MAC address of the device; The terms of the association between the device and the second access point.

5. The apparatus according to any one of the preceding claims, wherein the discovery request or the discovery response comprises: At least one association capability for the association between the second access point and the device.

6. The apparatus according to any one of the preceding claims, wherein the component for negotiating the terms of association between the device and the second access point comprises: A component for sending the device's user association records to the second access point.

7. The apparatus according to any one of the preceding claims further comprises: Components for sending a deassociation request to the second access point to terminate the association between the device and the second access point; as well as A component for receiving confirmation of the deassociation request from the second access point.

8. A device for communication, comprising: Components used to determine whether the first access point and the second access point are in the coordination protocol; Components used to determine the association between the device and the first access point; A component for sending a discovery request to the first access point, wherein the discovery request includes: an inquiry about whether the first access point will accept the associated transfer with the device; A component for receiving a discovery response from the first access point, the discovery response indicating that the first access point accepts the discovery request to transfer the association with the device; as well as A component for negotiating the terms of the association between the device and the second access point between the first access point and the second access point.

9. The apparatus according to claim 8, further comprising: A component for authorizing the association between the device and the second access point, wherein the authorization includes receiving user association information for the device from the first access point.

10. The apparatus according to any one of claims 8 to 9, wherein at least one of the discovery request or the discovery response comprises: At least one association capability for the association between the second access point and the device.

11. The apparatus according to any one of claims 8 to 10, wherein the component for negotiating the terms of association between the device and the second access point comprises: A component for receiving user association records of the device from the first access point.

12. The apparatus according to any one of claims 8 to 11, further comprising: A component for sending a deassociation request to the first access point to terminate the association between the device and the second access point; as well as A component for receiving confirmation of the deassociation request from the first access point.

13. An apparatus for communication, comprising: Components used to determine whether the first access point and the second access point are in the coordination protocol; Components used to determine the association between the device and the first access point; Components used to identify the device located in the coverage vulnerability of the first access point; A component for sending a request to the first access point or the second access point to transfer the association of the device with the first access point to the second access point; as well as Components used to initiate the association between the device and the second access point.

14. The apparatus of claim 13, further comprising at least one of the following: Components used to monitor the association between the device and the second access point; A component for sending a deassociation request to the first access point or the second access point to terminate the association between the device and the second access point; or A component for receiving confirmation of the deassociation request from the first access point or the second access point.

15. The apparatus according to any one of the preceding claims, wherein the apparatus is one of the following: a first access point according to any one of claims 1 to 7, a second access point according to any one of claims 8 to 12, or a device according to any one of claims 13 to 14.

Images