Communication equipment, method, device and computer readable medium

Abstract

The embodiment of the invention relates to communication equipment, a communication method, a communication device and a computer readable medium. In one aspect, a first access point (AP) device allocates a device identification to a station (STA) device during performing an association procedure with the STA device. In addition, the first AP device transmits the device identification allocated to the STA device to at least one of the second AP device or the control device. In this manner, the performance of a communication network may be improved, for example, an EasyMesh network with enhanced performance may be implemented.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of communications, and more particularly to communication devices, methods, apparatuses, and computer-readable media. Background Art

[0002] More and more home or small business networks adopt multi-access point (multi-AP) deployments to solve the coverage problem of communication networks (such as Wi-Fi) and improve the user experience. The Wi-Fi Alliance's Wi-Fi EasyMesh program defines the control protocol between access points, the mechanism for routing traffic within the network, and the data objects required to facilitate the joining, configuration, control, and automated management of access points in a Wi-Fi EasyMesh network.

[0003] A communication network (such as a Wi-Fi EasyMesh network) may include a controller and one or more agents. The EasyMesh controller is responsible for monitoring network conditions, managing the network, configuring the radios on the access points, and optimizing network operations. The EasyMesh agent may be responsible for collecting and reporting measurement results and capabilities in the Wi-Fi EasyMesh network. In addition, the EasyMesh agent may execute commands sent from the controller and may provide Wi-Fi services to client devices. However, there is still room for optimization and improvement in communication networks (such as EasyMesh networks). Summary of the Invention

[0004] Generally, example embodiments of the present disclosure relate to a technical solution for wireless communication, particularly a technical solution for enhancing the performance of a communication network (such as an EasyMesh network), for example, providing a mechanism for identifying non-AP stations with randomly changing Media Access Control (MAC) addresses (RCM) in a multi-access point (AP) network.

[0005] In a first aspect of the present disclosure, a first access point (AP) device is provided. The first AP device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first AP device to at least: assign a device identifier to a station (STA) device during an association process with the STA device; and send the device identifier to at least one of a second AP device or a control device.

[0006] In a second aspect of the present disclosure, a second AP device is provided. The second AP device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second AP device to at least: receive from a first AP device a device identifier assigned by the first AP device to a STA device; and perform communication with the STA device based on the device identifier.

[0007] In a third aspect of the present disclosure, a control device is provided. The control device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the control device to at least: receive from a first AP device a device identifier assigned by the first AP device to a STA device; and control operations related to the STA device based on the device identifier.

[0008] In a fourth aspect of the present disclosure, a STA device is provided. The STA device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the STA device to at least: obtain from a first AP device a device identifier assigned by the first AP device to the STA device during an association process with the first AP device; and perform communication with a second AP device based on the device identifier.

[0009] In a fifth aspect of the present disclosure, a communication method is provided. The communication method includes: at a first AP device, during an association process with a STA device, assigning a device identifier to the STA device; and sending the device identifier to at least one of a second AP device or a control device.

[0010] In a sixth aspect of the present disclosure, a communication method is provided. The communication method includes: at a second AP device, receiving from a first AP device a device identifier assigned by the first AP device to a STA device; and performing communication with the STA device based on the device identifier.

[0011] In a seventh aspect of the present disclosure, a communication method is provided. The communication method includes: at a control device, receiving from a first AP device a device identifier assigned by the first AP device to a station (STA) device; and controlling operations related to the STA device based on the device identifier.

[0012] In an eighth aspect of the present disclosure, a communication method is provided. The communication method includes: at a STA device, during an association process with a first AP device, obtaining from the first AP device a device identifier assigned by the first AP device to the STA device; and performing communication with a second AP device based on the device identifier.

[0013] In a ninth aspect of the present disclosure, a communication device is provided. The communication device includes: a component for allocating a device identifier to a STA device during an association process between a first AP device and the STA device; and a component for sending the device identifier to at least one of a second AP device or a control device.

[0014] In a tenth aspect of the present disclosure, a communication device is provided. The communication device includes: a component for receiving, at a second AP device, a device identifier allocated by a first AP device to a STA device from the first AP device; and a component for performing communication with the STA device based on the device identifier.

[0015] In an eleventh aspect of the present disclosure, a communication device is provided. The communication device includes: a component for receiving, at a control device, a device identifier allocated by a first AP device to a STA device from the first AP device; and a component for controlling operations related to the STA device based on the device identifier.

[0016] In a twelfth aspect of the present disclosure, a communication device is provided. The communication device includes: a component for obtaining, at a STA device, a device identifier allocated by a first AP device to the STA device from the first AP device during an association process between the STA device and the first AP device; and a component for performing communication with a second AP device based on the device identifier.

[0017] In a thirteenth aspect of the present disclosure, a non-transitory computer-readable medium is provided, including program instructions for causing a device to execute any one of the methods in at least the fifth aspect to the eighth aspect.

[0018] In a fourteenth aspect of the present disclosure, a non-transitory computer-readable medium is provided, including program instructions stored thereon, and the program instructions execute any one of the methods in at least the fifth aspect to the eighth aspect.

[0019] In a fifteenth aspect of the present disclosure, a computer program including instructions is provided, which when executed by a device, causes the device to at least: at a first AP device, allocate a device identifier to a STA device during an association process between the first AP device and the STA device; and send the device identifier to at least one of a second AP device or a control device.

[0020] In a sixteenth aspect of the present disclosure, a computer program including instructions is provided, which when executed by a device, causes the device to at least: at a second AP device, receive a device identifier allocated by a first AP device to a STA device from the first AP device; and perform communication with the STA device based on the device identifier.

[0021] In a seventeenth aspect of the present disclosure, there is provided a computer program including instructions which, when executed by a device, cause the device to at least: at a control device, receive, from a first AP device, a device identifier assigned by the first AP device to a station (STA) device; and control operations related to the STA device based on the device identifier.

[0022] In an eighteenth aspect of the present disclosure, there is provided a computer program including instructions which, when executed by a device, cause the device to at least: at the STA device, during an association process with a first AP device, obtain, from the first AP device, a device identifier assigned by the first AP device to the STA device; and perform communication with a second AP device based on the device identifier.

[0023] In a nineteenth aspect of the present disclosure, there is provided a first AP device. The first AP device includes an allocation circuit for assigning a device identifier to a STA device during an association process with the STA device; and a transmission circuit for transmitting the device identifier to at least one of a second AP device or a control device.

[0024] In a twentieth aspect of the present disclosure, there is provided a second AP device. The second AP device includes a receiving circuit for receiving, from a first AP device, a device identifier assigned by the first AP device to a STA device; and an execution circuit for performing communication with the STA device based on the device identifier.

[0025] In a twenty - first aspect of the present disclosure, there is provided a control device. The control device includes a receiving circuit for receiving, from a first AP device, a device identifier assigned by the first AP device to a STA device; and a control circuit for controlling operations related to the STA device based on the device identifier.

[0026] In a twenty - second aspect of the present disclosure, there is provided a STA device. The STA device includes an obtaining circuit for obtaining, from a first AP device, a device identifier assigned by the first AP device to the STA device during an association process with the first AP device; and an execution circuit for performing communication with a second AP device based on the device identifier.

[0027] It should be understood that the content described in the summary of the invention section is not intended to limit the key or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the embodiments of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A block diagram of an example communication system in which embodiments of the present disclosure may be implemented is shown.

[0029] Figure 2Shows a schematic diagram of the interaction process between communication devices according to some embodiments of the present disclosure.

[0030] Figure 3 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure.

[0031] Figure 4 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure.

[0032] Figure 5 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure.

[0033] Figure 6 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure.

[0034] Figure 7 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure.

[0035] Figure 8 Shows a schematic diagram of the process executed by the first AP device according to some embodiments of the present disclosure.

[0036] Figure 9 Shows a schematic diagram of the process executed by the second AP device according to some embodiments of the present disclosure.

[0037] Figure 10 Shows a schematic diagram of the process executed by the control device according to some embodiments of the present disclosure.

[0038] Figure 11 Shows a schematic diagram of the process executed by the STA device according to some embodiments of the present disclosure.

[0039] Figure 12 Shows a simplified block diagram of an electronic device suitable for implementing embodiments of the present disclosure.

[0040] Figure 13 Shows a schematic diagram of a computer-readable medium suitable for implementing embodiments of the present disclosure.

[0041] In all the figures, the same or similar reference numerals denote the same or similar elements. Detailed Embodiments

[0042] The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments shown in the accompanying drawings. It should be understood that these specific embodiments are described to enable those skilled in the art to better understand and implement the embodiments of the present disclosure, rather than to limit the scope of the present disclosure in any way.

[0043] As used herein, the term "comprising" and its like shall be understood as an open inclusion, i.e., "including but not limited to". The term "based on" shall be understood as "at least partially based on". The term "an embodiment" or "the embodiment" shall be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included hereinafter.

[0044] As used herein, the term "determine" encompasses a variety of actions. For example, "determine" may include operations, calculations, processing, derivations, investigations, lookups (e.g., lookups in a table, database, or another data structure), ascertainments, etc. Additionally, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Further, "determine" may include parsing, selecting, choosing, establishing, etc. As used herein, "at least one of: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar phrasings, where the list of two or more elements is joined by "and" or "or", means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0045] The term "circuit" as used herein refers to one or more of the following: (a) only hardware circuit implementations (such as only analog and / or digital circuit implementations); and (b) combinations of hardware circuits and software, such as (if applicable): (i) combinations of analog and / or digital hardware circuits and software / firmware, and (ii) any part of a hardware processor and software (including a digital signal processor, software, and memory that work together to enable a device such as a radio frequency device or other computing device to perform various functions); and (c) hardware circuits and / or processors, such as a microprocessor or a part of a microprocessor, which require software (e.g., firmware) for operation, but may be without software when software is not required for operation.

[0046] The definition of circuit applies to all usage scenarios of this term in this application (including any claims). As another example, the term "circuit" as used herein also covers implementations of only a hardware circuit or a processor (or processors), or a part of a hardware circuit or a processor, or its accompanying software or firmware. For example, if applicable to a particular claim symbol, the term "circuit" also covers a baseband integrated circuit or a processor integrated circuit or a similar integrated circuit in other computing devices.

[0047] In a typical EasyMesh network architecture, during the internal communication between the controller and the agent, messages including configuration information, the capabilities of APs / STAs, metrics, and operation requests / responses are transmitted via Wi-Fi or Ethernet backhaul. Among these messages, the MAC address of the STA is a key field used to identify and track each individual client device associated with the network. According to the latest EasyMesh specification, there are several scenarios involving identifying a client device based on the STA MAC address.

[0048] Scenario 1 involves sensing and collecting network topology information and topology changes. In the IEEE 1905 topology response message with associated client type length value (TLV) and the 1905 topology notification message with client association event TLV, the MAC address of the STA is transmitted between the EasyMesh controller and the agent to identify each STA and its attached AP. Such messages and TLVs enable each EasyMesh node (controller and agent) to understand network topology changes.

[0049] Scenario 2 involves collecting the capabilities and metrics of client devices. In an EasyMesh network, the controller collects the capabilities of all client devices and periodically collects metric information to sense the state of the entire network, and then triggers some optimization operations to improve the performance of the entire network. The AP metric response message includes associated STA link metric TLV, associated STA traffic statistics TLV, associated STA extended link metric, and associated Wi-Fi 6 STA status report TLV. The EasyMesh agent sends responses regarding the metrics of each associated STA, such as uplink / downlink data rate, transmit / receive channel utilization, and queue size, to the controller through this response message. The non-associated STA link metric query / response message includes non-associated STA link metric query / response TLV. Through this query / response message, the EasyMesh agent can collect the received channel power indicator (RCPI) information of non-associated STAs on a specific channel and report this information to the controller to further improve network performance. The EasyMesh controller and the agent also exchange beacon metric information via the beacon metric query / response TLV, and the controller collects beacon reports from specific STAs. In summary, in all the above cases related to the collection of client device capabilities and metrics, the MAC address of the STA is used as the device identifier to determine which STA information should be collected.

[0050] Scenario 3 involves network optimization operations for a specific STA. The EasyMesh controller will take some network optimization measures based on the collected network device capabilities, metrics, and statistical data. Some optimization operations (e.g., roaming, association control) are targeted at specific client devices. To improve the performance of the entire network or a specific STA, the EasyMesh controller can send a client roaming request message carrying a roaming request TLV or a Profile-2 roaming request TLV to the agent to guide the STA to roam to the best BSSID. On the other hand, for STAs that do not support 802.11v BTM requests, the controller can send a client association control request message to guide the specific STA to associate with the desired BSSID / AP.

[0051] Scenario 4 involves transmitting network optimization policies. Under certain conditions, the EasyMesh controller can use policies to manage and control the behavior of network devices and take necessary optimization measures. For example, the controller can send policies for certain specific STAs to the agent, and the agent will trigger actions for behavior optimization.

[0052] In some usage scenarios, the EasyMesh controller can send a multi-AP policy configuration request message carrying a roaming policy TLV to the agent to set the conditions / thresholds for triggering roaming operations. For example, the controller can use a QoS management policy TLV to allow / forbid the Stream Classification Service (SCS) or Mirrored Stream Classification Service (MSCS) operations for a specific STA to enhance QoS management. In the above cases, the MAC address of the STA is used as the device identifier to identify each client device to apply the policy.

[0053] In the 802.11 standard, the fixed and unencrypted MAC address of the STA is widely used in the frame header, which enables an unauthorized party to identify and track the STA based on the MAC address. To prevent the STA from being tracked and improve the privacy of 802.11, MAC address randomization has become a commonly used technology recently.

[0054] However, the use of such Randomized Changed MAC (RCM) also leads to new problems, namely that it becomes more difficult to identify and track STAs when needed. In this regard, the IEEE802.11bh and 802.11bi groups focus on using RCM to identify STAs without compromising user privacy. 802.11bh focuses on identifying devices (i.e., non-AP STAs) through MAC randomization during the pre-association phase, while the devices (i.e., non-AP STAs) still do not change their MAC addresses after association (i.e., post-association). On the other hand, IEEE 802.11bi takes solving privacy issues as part of its work and tries to address the situation where non-AP STAs can also change their MAC addresses after association. It should be noted that non-AP STAs are abbreviated as STAs in the embodiments of the present disclosure. The device ID and / or IRM (Identifiable Random MAC) proposed by the 802.11bh group can solve the identification problem for independent APs or AP-MLDs with RCM (Randomized Changed MAC address).

[0055] There is currently no solution to the identification problem in a multi-AP network environment. Further descriptions of the identification problem in a multi-AP network will be listed below.

[0056] Problem 1 is that the network topology is incorrect. In an EasyMesh network, when associating an STA with any agent or disassociating an STA from any agent, the agent will send a client association event TLV carrying the client MAC address to notify the controller and other agents of the topology change. For example, an RCM-enabled STA can roam from AP1 to AP2. The network may think that the STA with RCM1 is disassociating from AP1 and a new STA with RCM2 is associating with AP2. But in fact, the STA with RCM1 or RCM2 is the same client device. Due to this unidentifiable problem on each associated client, the statistical data and status-related information on a certain STA may also be incorrect.

[0057] Problem 2 is that the client roaming decision is inappropriate. Client roaming is a key feature used to optimize network performance in an EasyMesh network. In some use cases, before the controller intends to send a client roaming request message, it needs to collect some metrics in advance for a specific STA on each agent, such as RCPI, operation class, and working channel. Based on this, the network can further decide which STAs to select for roaming and when to trigger the roaming operation.

[0058] According to the latest EasyMesh specification, the associated STA link metric TLV and the non - associated STA link metric TLV are sent from the controller to the agent to collect metrics of the STA, such as RCPI. The controller sends the associated STA link metric TLV and the non - associated STA link metric TLV carrying the same STA MAC to the attached AP and the non - attached AP respectively. Regarding the non - associated STA link metric query, the non - attached AP obtains the expected RCPI information of a certain STA by matching the MAC address carried in the received probe request with the MAC address included in the non - associated STA link metric TLV. Unfortunately, the STA may send a probe request with a new RCM, which causes the non - attached AP to fail to collect RCPI information and further leads to incorrect client roaming decisions.

[0059] Problem 3 is the outdated QoS management policies and requests. In the EasyMesh R4 specification, WFA QoS management support is introduced, allowing the controller to enable or disable SCS / MSCS operations on specific STAs through QoS management policies. For example, if such allow / deny policies are configured from the controller to the agent, the AP may not perform QoS processing negotiation for the specific traffic sent by a specific STA. However, if the STA randomly changes its MAC, the policy of allowing / denying SCS / MSCS operations will become invalid when the specific STA associates with the agent.

[0060] In addition to the QoS management policy that allows / denies SCS / MSCS negotiation, the controller can also configure the SCS / MSCS descriptor and include the QoS management descriptor TLV in the service priority request message. Such descriptor elements can be propagated to any agent, even to a specific STA that is not associated with it, so that the SCS / MSCS descriptors configured on any agent are aligned and consistent on all agents. However, if the STA changes its MAC during the next association with another agent, this configuration based on the STA MAC will not take effect, and the expected QoS processing for the specific traffic specified in the QoS management descriptor will not occur.

[0061] The current technical solutions have not solved the problems caused by the use of RCM by non-AP STAs in a multi-AP network. In view of this, some embodiments of the present disclosure propose a device identifier synchronization mechanism to enhance the identification and tracking of STAs in a communication network (e.g., an EasyMesh network) and to achieve optimization of the entire communication network (e.g., an EasyMesh network). It should be noted that although the above analysis and description are made with examples of EasyMesh networks, the embodiments of the present disclosure are not limited to EasyMesh networks. In fact, the embodiments of the present disclosure can be equivalently or similarly applied to any communication network or communication system with similar defects or problems.

[0062] Figure 1 FIG. shows a block diagram of an example communication system in which embodiments of the present disclosure can be implemented. As Figure 1 shown, the communication system 100 includes a plurality of communication devices, such as communication devices 110, 120, 130, 140. The plurality of communication devices can communicate directly or indirectly with each other. For example, communication device 110 can communicate with the other plurality of communication devices. In this document, communication device 110 can be referred to as the first AP device 110, communication device 120 can be referred to as the second AP device 110, communication device 130 can be referred to as the control device 110, and communication device 140 can be referred to as the STA device 110. It should be noted that an AP device can also be referred to as an agent in this document. It should be noted that the number of communication devices in the embodiments of the present disclosure is not limited to the above examples.

[0063] Figure 2 FIG. shows a schematic diagram of an interaction process between communication devices according to some embodiments of the present disclosure. For ease of understanding, in the process 200 as Figure 2 shown, reference can be made to the devices involved in Figure 1 (e.g., AP devices 110 and 120, control device 130, STA device 140) for description.

[0064] At the first AP device 110, during the process of associating with the STA device 140, a device identifier is assigned (202) to the STA device 140. Next, the first AP device 110 sends (204, 206) the device identifier to at least one of the second AP device 120 or the control device 130. In some embodiments, the device identifier is sent included in a 1905 topology notification message.

[0065] At the second AP device 120, the device identifier allocated by the first AP device 110 to the STA device 140 is received (204), for example, the device identifier is included in the 1905 topology notification message and is received. In some embodiments, the second AP device 120 may also store the device identifier. Next, the second AP device 120 performs (208) communication with the STA device 140 based on the device identifier.

[0066] At the control device 130, the device identifier allocated by the first AP device 110 to the STA device 140 is received (206), for example, the device identifier is included in the 1905 topology notification message and is received. In some embodiments, the control device 130 may also store the device identifier. The control device 130 controls (210) operations related to the STA device 140 based on the device identifier.

[0067] At the STA device 140, during the process of performing an association with the first AP device 110, the device identifier allocated by the first AP device 110 to the STA device 140 is obtained (202), and communication with the second AP device 120 is performed (212) based on the device identifier.

[0068] In some embodiments, the 1905 topology notification message may include a client association event type length value (TLV), the client association event TLV may include bit information, and the bit information may be used to indicate whether the device identifier is used.

[0069] In some embodiments, if the TLV indicates that the device identifier is used, the 1905 topology notification message may further include a client device identifier TLV. The client device identifier TLV may include the device identifier and the media access control (MAC) address of the STA device 140. Alternatively or additionally, in addition to the device identifier, the client device identifier TLV may further include the MAC address of the first AP device 110.

[0070] In some embodiments, the control device 130 may perform operations related to the STA device 140 through the following operations, and the second AP device 120 and the STA device 140 may perform communication through the following operations. First, the control device 130 sends a link metric query TLV for the STA device 140 to the second AP device 120, where the link metric query TLV includes a device identifier. Accordingly, at the second AP device 120, a link metric query TLV for the STA device 140 is received from the control device 130. Based on the received link metric query TLV, the second AP device 120 may monitor a probe request message sent from the STA device 140, and the probe request message may include a device identifier. In the case where the probe request message is monitored, the second AP device 120 may obtain the link metric information of the STA device 140 based on the probe request message. Next, the second AP device 120 may send a link metric response TLV to the control device 130, and the link metric response TLV may include a device identifier and link metric information. At the control device 130, the link metric response TLV is received from the second AP device 120.

[0071] In some embodiments, the control device 130 may perform operations related to the STA device 140 through the following operations. The control device 130 sends a Quality of Service (QoS) management policy TLV to at least one of the first AP device 110 or the second AP device 120, and the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation. Accordingly, at the first AP device 110, the QoS management policy TLV may be received from the control device 130. The first AP device 110 may also receive a QoS processing negotiation request from the STA device 140, and determine whether to allow the QoS processing negotiation request of the STA device 140 based on the QoS management policy TLV. Accordingly, at the second AP device 120, the QoS management policy TLV may also be received from the control device 130. The second AP device 120 may also perform communication with the STA device 140 through the following operations. For example, the second AP device 120 may receive a QoS processing negotiation request from the STA device 140, and determine whether to allow the QoS processing negotiation request of the STA device 140 based on the QoS management policy TLV.

[0072] In some other embodiments, the control device 130 may perform operations related to the STA device 140 through the following operations. First, the control device 130 may receive a QoS management descriptor TLV for the STA device 140 from the first AP device 110, and the QoS management descriptor TLV includes a device identifier and QoS management information for the STA device 140. For example, the QoS management descriptor TLV is included in a QoS management communication message and is received from the first AP device 110. Next, the control device 130 may send the QoS management descriptor TLV to the second AP device 120.

[0073] Accordingly, at the second AP device 120, the QoS management descriptor TLV may be received from the control device 130. For example, at the second AP device 120, the QoS management descriptor TLV is included in a service priority request message and is received.

[0074] In some embodiments, the second AP device 120 and the STA device 140 may perform communication through the following operations. For example, during the association process with the STA device 140 based on the device identifier, the second AP device 120 assigns the same device identifier to the STA device 140. Accordingly, at the STA device 140, during the association process with the second AP device 120 based on the device identifier, the same device identifier assigned by the second AP device 120 to the STA device 140 is obtained from the second AP device 120.

[0075] In some embodiments, the control device 130 may perform operations related to the STA device 140 through the following operations, and the STA device 140 and the second AP device 120 may perform communication through the following operations. For example, the control device 130 may send an association control request TLV to the second AP device 120, and the association control request TLV includes a device identifier and association control information for the STA device 140. The STA device 140 sends an association request message or a probe request message to the second AP device 120, and the association request message or the probe request message includes a device identifier. Accordingly, at the second AP device 120, the association control request TLV is received from the control device 130, and the association request message or the probe request message is received from the STA device 140. Next, the second AP device 120 processes the association request message or the probe request message of the STA device 140 based on the association control information.

[0076] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification. The following will be combined with Figures 3 to 7will be described in detail. In some embodiments of the present disclosure, it is assumed that the APs and STAs in the EasyMesh network comply with the 802.11bh specification so that the network pays attention to the RCM and the device ID of the STA during association.

[0077] Figure 3 FIG. shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure. As Figure 3 shown, the agent associated with the STA propagates the device ID of the STA to the controller and other agents. During the (re)association process, the agent determines whether the AP grants a device ID to the STA. If granted, the agent will send a 1905 topology notification multicast message, which includes a client association event TLV, where the bits used for the device ID are set to 1. Therefore, the agent includes the new client device ID TLV in the 1905 topology notification message to propagate the device ID to each agent in the network.

[0078] Theoretically, when an STA associates with different EasyMesh agents, different agents can dispatch variable device IDs to the same STA. To avoid tracking device ID changes, the network can maintain the same device ID across the entire network. Once any agent in the EasyMesh network dispatches a device ID to an STA, that same device ID will remain unchanged until the STA leaves the network. Subsequently, when the STA associates with any other agent due to roaming, the same and propagated device ID will be granted to the same STA.

[0079] Specifically, as Figure 3 shown, the attached AP dispatches the device ID to the STA and synchronizes the device ID to the entire EasyMesh network, as described in the following steps. It should be noted that in the context of describing the embodiments of the present disclosure, the term "step" may represent an operation (or action), or a combination of multiple operations (or actions). The multiple operations (or actions) belonging to one "step" are not necessarily executed or occur simultaneously, but may also occur successively. In addition, the multiple operations (or actions) in one "step" are not necessarily executed or occur in the order described herein, but may be executed or occur in other different orders.

[0080] Step 1: The STA performs authentication (301), association (302), and 4-way handshake (303) to associate with Agent_1 in the EasyMesh network. During the 4-way handshake, the STA obtains the device ID from Agent_1.

[0081] Step 2: Agent_1 sends (304) a 1905 topology notification message to other agents and the controller, indicating whether the device ID is in use (a device ID bit set to 1 indicates in use, and a device ID bit set to 0 indicates not in use). In the case of using the device ID, a new client device ID TLV is added to the 1905 topology notification message, which includes the device ID, the RCM of the STA, and the AP MAC.

[0082] Step 3: When receiving the 1905 topology notification message, the controller saves (305) it as the identifier of the STA and uses it in subsequent request messages for that specific STA. Other agents also retain (306) it.

[0083] Step 4: When this STA associates with Agent_n due to roaming, Agent_n dispatches the same device ID to the same STA. Specifically, the STA performs (307) a roaming operation to Agent_n and associates (308) with Agent_n using the device ID. Agent_n checks (309) to assign the same or a new device ID. In the case of assigning the same device ID, the STA performs a 4-way handshake (310) to associate with Agent_n in the EasyMesh network.

[0084] In Table 1 below, a bit called the device ID bit is extended in the client association event TLV to identify whether the client device ID is in use. If in use, the new client device ID TLV defined in Table 2 is included in the 1905 topology notification message (which includes the STA device ID, as well as the STA MAC and the AP MAC).

[0085] Table 1 Client Association Event TLV

[0086]

[0087]

[0088] Table 2 Client Device ID TLV

[0089]

[0090] Figure 4 Shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure. As Figure 4As shown, non-associated STA link metrics are collected based on the device ID. Since the controller maintains information related to the device ID of the STA, before it triggers a client roaming request, it will send a non-associated STA link metric query including the device ID to collect specific non-associated STA RCPI. Therefore, the non-affiliated AP can obtain the RCPI information of the expected STA based on the device ID carried in the probe request sent by the STA.

[0091] Specifically, as Figure 4 shown, the non-affiliated AP collects non-associated STA link metrics for roaming decisions. Before the controller makes a roaming decision, if the STA uses RCM, the controller will collect the RCPI information of the specific STA from the affiliated AP and the non-affiliated AP, as shown in the following process.

[0092] Step 1: The controller uses associated STA link metric query / response communication (401) to obtain STA metrics (such as RCPI, estimated data rate) from the affiliated AP.

[0093] Step 2: The controller sends (402) a non-associated STA link metric query message to the non-affiliated APs (Agent_2 to Agent_n), which includes a new non-associated STA with an RCM link metric query TLV defined in Table 3.

[0094] Step 3: The non-affiliated APs (Agent_2 to Agent_n) monitor (403) the probe requests sent (404) by the STA with the device ID and obtain (405) the RCPI information based on this.

[0095] Step 4: The non-affiliated APs (Agent_2 to Agent_n) send (406) a non-associated STA link metric response message to the controller, which includes a new non-associated STA with an RCM link metric response TLV defined in Table 4. When receiving this response, the controller will verify the metrics based on the device ID of the STA rather than the MAC of the STA.

[0096] Step 5: The controller integrates the metrics collected from the affiliated AP and the non-affiliated APs and makes (407) a client roaming decision.

[0097] Table 3 Non-associated STA with RCM Link Metric Query TLV

[0098]

[0099]

[0100] Table 4 Non-associated STA with RCM Link Metric Response TLV

[0101]

[0102]

[0103] Figure 5 The figure shows a schematic diagram of the interaction process between communication devices according to certain embodiments of the present disclosure. Figure 5 The process can achieve client association control based on the device ID. For certain specific reasons, such as forced roaming, parental control, etc., the controller needs to block / unblock the association of some STAs with some APs in the EasyMesh network. Using the client association control request message, due to the use of RCM, the target AP cannot identify the association request or probe request from a specific STA, which results in the ineffectiveness and failure of such control. Therefore, as Figure 5 shown, this association control will change to be based on the device ID rather than the MAC address. For example, the target AP (Agent_n) receives (501) a client association control request with the device ID from the controller and receives (502) an association request with RCM_2 and the device ID from a specific STA. Next, the target AP (Agent_n) checks (503) the access control list based on the device ID and sends (504) a reject association request to the STA. If the STA sends (505) a probe request with RCM_2 and the device ID to the target AP, the target AP can check the access control list and not respond to it (506).

[0104] According to Figure 5 the process in, Table 5 defines a new client with an RCM association control request TLV and adds it to the client association control request message.

[0105] Table 5 Clients with RCM Association Control Request TLV

[0106]

[0107] Figure 6 and Figure 7 respectively show schematic diagrams of the interaction process between communication devices according to certain embodiments of the present disclosure. Specifically, Figure 6 the process shown realizes the configuration of the QoS management policy based on the device ID. Figure 7 the process shown realizes the configuration of the QoS management descriptor based on the device ID.

[0108] Typically, QoS management policies and configurations need to be propagated by the controller to other agents so that each agent maintains consistent QoS handling when the STA triggers an SCS / MSCS request for any of them. In the case of using RCM, the device ID is needed to identify the STA to which the policy or descriptor applies. When the controller propagates the QoS management descriptor to other non-affiliated agents, a new QoS management policy TLV carrying the device ID needs to be included in the multi-AP policy configuration request message.

[0109] In other words, when the controller configures the QoS management policy for a specific STA for an agent, the MAC of the STA and its device ID will be included in the new QoS management policy TLV carrying the device ID. When the specific STA triggers SCS / MSCS negotiation, any agent can effectively allow / deny SCS / MSCS negotiation according to the configured policy. This process can be referred to as shown in Figure 6 the schematic diagram of QoS management policy propagation as shown.

[0110] Step 1: The controller sends (611, 612) a multi-AP policy configuration request, which includes a QoS management policy TLV carrying the device ID. The definition of the device ID can be seen in Table 6 below.

[0111] Step 2: The STA associated with Agent_1 has RCM_1 and a device ID.

[0112] Step 3: The STA sends (602) an MSCS / SCS request to Agent_1.

[0113] Step 4: Agent_1 checks (603) the allow or deny MSCS / SCS policy for the specific STA.

[0114] Step 5: If the MSCS / SCS operation is allowed, Agent_1 sends (604) a response and receives the MSCS / SCS request from the STA.

[0115] Step 6: The STA can roam (605) from Agent_1 to Agent_n, and can associate (606) with Agent_n using RCM and the device ID. The STA associated with Agent_n has RCM_2 and a device ID.

[0116] Step 7: The STA sends (607) an MSCS / SCS request to Agent_n.

[0117] Step 8: Agent_n checks (608) whether to allow or disallow the MSCS / SCS policy for a specific STA. For example, in the case where RCM_1 and RCM_2 are different, Agent_n can check based on the device ID.

[0118] Step 9: If Agent_n does not allow the MSCS / SCS operation, Agent_n will reject (609) the MSCS / SCS request.

[0119] Table 6 QoS Management Policy TLV Carrying Device ID

[0120]

[0121] For the SCS / MSCS negotiation details, if the controller wishes to propagate the MSCS / SCS descriptor or the DSCP policy descriptor to other non - affiliated APs, a newly defined device - ID - based QoS management descriptor TLV (including the STA device ID) will be added to the service priority request message.

[0122] In other words, when the controller wants to control the details of QoS processing for a specific STA, it propagates the QoS management descriptor to any agent, and the MAC of the STA and its device ID will be included in the new device - ID - based QoS management descriptor TLV. Then, when the matching traffic sent by the specific STA is forwarded, any agent can perform aligned QoS processing according to the propagated SCS / MSCS descriptor. This process can be referred to as Figure 7 shown in the schematic diagram of QoS management descriptor propagation. Specifically, Agent_1 can perform (701) QoS processing for STA traffic based on the MSCS / SCS rules and send (702) a QoS management notification message including the QoS management descriptor TLV carrying the device ID to the controller. The controller can send (703) a service priority request message including the QoS management descriptor TLV carrying the device ID to Agent_n. The STA can roam (704) from Agent_1 to Agent_n. Next, the STA sends (705) an MSCS / SCS request to Agent_n. Agent_n can send (706) an MSCS / SCS response to this STA based on the descriptor. Communication (707) for data traffic can be achieved between the STA and Agent_n. Agent_n can perform (708) QoS processing for STA traffic based on the MSCS / SCS descriptor.

[0123] Table 7 Device - ID - based QoS Management Descriptor TLV

[0124]

[0125]

[0126] Using the technical solution of the embodiments of the present disclosure, each individual STA with an RCM can be identified and tracked by the EasyMesh network after its association. The following use case interruption problems caused by the RCM can be solved. First, the network topology and STA-related measurement results can be correctly collected. Additionally, the link metrics of non-associated STAs can be correctly collected, and appropriate client roaming decisions can be made for network optimization. Furthermore, the QoS management policies and descriptor configurations regarding MSCS / SCS and DSCP policies can be correctly propagated in the EasyMesh network, ensuring correct and consistent QoS handling for specific STAs. Moreover, the use of device IDs on APs and STAs is implemented in a multi-AP network environment, solving the potential problems brought by STAs using the RCM.

[0127] Figure 8 A flowchart executed by the first AP device 110 according to some embodiments of the present disclosure is shown. As Figure 8 shown, in process 800, at block 810, during the process of performing an association with the STA device 140, a device identifier is assigned to the STA device 140. At block 820, the device identifier is sent to at least one of the second AP device 120 or the control device 130.

[0128] In some embodiments, the device identifier is sent included in a 1905 topology notification message.

[0129] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

[0130] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0131] In some embodiments, the first AP device 110 is further caused to: receive a quality of service (QoS) management policy TLV from the control device 130, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

[0132] In some embodiments, the first AP device 110 is further caused to: receive a QoS processing negotiation request from the STA device 140; and determine whether to allow the QoS processing negotiation request of the STA device 140 based on the QoS management policy TLV.

[0133] In some embodiments, the first AP device 110 is further caused to: send a QoS management descriptor TLV to the control device 130, where the QoS management descriptor TLV includes a device identifier and QoS operation information for a data stream of the STA device 140.

[0134] In some embodiments, the QoS management descriptor TLV is included in a QoS management notification message and is sent.

[0135] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0136] Figure 9 A flowchart executed by the second AP device 120 according to some embodiments of the present disclosure is shown. As Figure 9 shown, in process 900, at block 910, receive a device identifier assigned by the first AP device 110 to the STA device 140 from the first AP device 110. At block 920, perform communication with the STA device 140 based on the device identifier.

[0137] In some embodiments, the second AP device 120 is further caused to: store the device identifier.

[0138] In some embodiments, the device identifier is received included in a 1905 topology notification message.

[0139] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

[0140] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0141] In some embodiments, the second AP device 120 is caused to perform communication with the STA device 140 by: during the association process with the STA device 140 based on the device identifier, assign the same device identifier to the STA device 140.

[0142] In some embodiments, the second AP device 120 is caused to communicate with the STA device 140 by: receiving, from the control device 130, a link metric query TLV for the STA device 140, where the link metric query TLV includes a device identifier; based on receiving the link metric query TLV, monitoring probe request messages sent by the STA device 140, where the probe request messages include a device identifier; in the case where a probe request message is monitored, obtaining link metric information of the STA device 140 based on the probe request message; and sending a link metric response TLV to the control device 130, where the link metric response TLV includes a device identifier and link metric information.

[0143] In some embodiments, the second AP device 120 is further caused to: receive, from the control device 130, a Quality of Service (QoS) management policy TLV, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

[0144] In some embodiments, the second AP device 120 is caused to communicate with the STA device 140 by: receiving a QoS processing negotiation request from the STA device 140; and based on the QoS management policy TLV, determining whether to allow the QoS processing negotiation request of the STA device 140.

[0145] In some embodiments, the second AP device 120 is further caused to: receive, from the control device 130, a QoS management descriptor TLV, where the QoS management descriptor TLV includes a device identifier and QoS management information for the STA device 140.

[0146] In some embodiments, the QoS management descriptor TLV is received included in a service priority request message.

[0147] In some embodiments, the second AP device 120 is caused to communicate with the STA device 140 by: receiving, from the control device 130, an association control request TLV, where the association control request TLV includes a device identifier and association control information for the STA device 140; receiving an association request message or a probe request message from the STA device 140, where the association request message or the probe request message includes a device identifier; and processing the association request message or the probe request message of the STA device 140 based on the association control information.

[0148] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0149] Figure 10 A flowchart executed by the control device 130 according to some embodiments of the present disclosure is shown. AsFigure 10 As shown, in process 1000, at block 1010, a device identifier allocated by the first AP device 110 to the STA device 140 is received from the first AP device 110. At block 1020, operations related to the STA device 140 are controlled based on the device identifier.

[0150] In some embodiments, the control device 130 is further caused to: store the device identifier.

[0151] In some embodiments, the device identifier is received included in a 1905 topology notification message.

[0152] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

[0153] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0154] In some embodiments, the control device 130 is caused to perform operations related to the STA device 140 by: sending a link metric query TLV for the STA device 140 to the second AP device 120, where the link metric query TLV includes the device identifier; and receiving a link metric response TLV from the second AP device 120, where the link metric response TLV includes the device identifier and the link metric information of the STA device 140.

[0155] In some embodiments, the control device 130 is caused to perform operations related to the STA device 140 by: sending a quality of service (QoS) management policy TLV including a list of device identifiers that do not allow QoS processing negotiation to at least one of the first AP device 110 or the second AP device 120.

[0156] In some embodiments, the control device 130 is caused to perform operations related to the STA device 140 by: receiving a QoS management descriptor TLV for the STA device 140 from the first AP device 110, where the QoS management descriptor TLV includes the device identifier and the QoS management information for the STA device 140; and sending the QoS management descriptor TLV to the second AP device 120.

[0157] In some embodiments, the QoS management descriptor TLV is included in a QoS management communication message and received from the first AP device 110; or the QoS management descriptor TLV is included in a service priority request message and sent to the second AP device 120.

[0158] In some embodiments, the control device 130 is caused to perform operations related to the STA device 140 by: sending an association control request TLV to the second AP device 120, where the association control request TLV includes a device identifier and association control information for the STA device 140.

[0159] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0160] Figure 11 A flowchart executed by the STA device 140 according to some embodiments of the present disclosure is shown. As Figure 11 shown, in process 1100, at block 1110, during the process of associating with the first AP device 110, a device identifier assigned by the first AP device 110 to the STA device 140 is obtained from the first AP device 110. At block 1120, communication with the second AP device 120 is performed based on the device identifier.

[0161] In some embodiments, the STA device 140 is caused to perform communication with the second AP device 120 by: during the process of associating with the second AP device 120 based on the device identifier, obtaining the same device identifier assigned by the second AP device 120 to the STA device 140 from the second AP device 120.

[0162] In some embodiments, the STA device 140 is caused to perform communication with the second AP device 120 by: sending a probe request message to the second AP device 120, where the probe request message includes a device identifier.

[0163] In some embodiments, the STA device 140 is caused to perform communication with the second AP device 120 by: sending an association request message or a probe request message to the second AP device 120, where the association request message or the probe request message includes a device identifier.

[0164] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 belong to an EasyMesh network.

[0165] In some example embodiments, a device capable of performing method 800 (e.g., implemented at the first AP device 110) may include components for performing the various steps of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0166] In some embodiments, the device may include: a component for allocating a device identifier to the STA device 140 during an association process with the STA device 140; and a component for sending the device identifier to at least one of the second AP device 120 or the control device 130.

[0167] In some embodiments, the device identifier is included in a 1905 topology notification message and is sent.

[0168] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

[0169] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0170] In some embodiments, the device may further include: a component for receiving a quality of service (QoS) management policy TLV from the control device 130, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

[0171] In some embodiments, the device may further include: a component for receiving a QoS processing negotiation request from the STA device 140; and a component for determining whether to allow the QoS processing negotiation request of the STA device 140 based on the QoS management policy TLV.

[0172] In some embodiments, the device further includes: a component for sending a QoS management descriptor TLV to the control device 130, where the QoS management descriptor TLV includes the device identifier and QoS operation information for a data stream of the STA device 140.

[0173] In some embodiments, the QoS management descriptor TLV is included in a QoS management notification message and is sent.

[0174] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0175] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 800. In some embodiments, the components include at least one processor and at least one memory storing computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the execution of the apparatus.

[0176] In some example embodiments, an apparatus capable of performing method 900 (e.g., implemented at the second AP device 120) may include components for performing the respective steps of method 900. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0177] In some embodiments, the apparatus may include: components for receiving, from a first AP device 110, a device identifier assigned by the first AP device 110 to an STA device 140; and components for performing communication with the STA device 140 based on the device identifier.

[0178] In some embodiments, the apparatus may further include: components for storing the device identifier.

[0179] In some embodiments, the device identifier is received included in a 1905 topology notification message.

[0180] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

[0181] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0182] In some embodiments, the components for performing communication with the STA device 140 include: components for allocating the same device identifier to the STA device 140 during an association process with the STA device 140 based on the device identifier.

[0183] In some embodiments, the components for performing communication with the STA device 140 include: components for receiving a link metric query TLV for the STA device 140 from the control device 130, where the link metric query TLV includes a device identifier; components for monitoring probe request messages sent by the STA device 140 based on the received link metric query TLV, where the probe request messages include a device identifier; components for obtaining link metric information of the STA device 140 based on the probe request messages in case the probe request messages are monitored; and components for sending a link metric response TLV to the control device 130, where the link metric response TLV includes a device identifier and link metric information.

[0184] In some embodiments, the apparatus further includes: components for receiving a Quality of Service (QoS) management policy TLV from the control device 130, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

[0185] In some embodiments, the components for performing communication with the STA device 140 include: components for receiving a QoS processing negotiation request from the STA device 140; and components for determining whether to allow the QoS processing negotiation request of the STA device 140 based on the QoS management policy TLV.

[0186] In some embodiments, the apparatus further includes: components for receiving a QoS management descriptor TLV from the control device 130, where the QoS management descriptor TLV includes a device identifier and QoS management information for the STA device 140.

[0187] In some embodiments, the QoS management descriptor TLV is received included in a service priority request message.

[0188] In some embodiments, the components for performing communication with the STA device 140 include: components for receiving an association control request TLV from the control device 130, where the association control request TLV includes a device identifier and association control information for the STA device 140; components for receiving an association request message or a probe request message from the STA device 140, where the association request message or the probe request message includes a device identifier; and components for processing the association request message or the probe request message of the STA device 140 based on the association control information.

[0189] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0190] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 900. In some embodiments, the components include at least one processor and at least one memory storing computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to perform.

[0191] In some example embodiments, an apparatus capable of performing method 1000 (e.g., implemented at control device 130) may include components for performing the respective steps of method 1000. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0192] In some embodiments, the apparatus may include: components for receiving, from a first AP device 110, a device identifier assigned by the first AP device 110 to an STA device 140; and components for controlling operations related to the STA device 140 based on the device identifier.

[0193] In some embodiments, the apparatus may include: components for storing the device identifier.

[0194] In some embodiments, the device identifier is received included in a 1905 topology notification message.

[0195] In some embodiments, the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is in use.

[0196] In some embodiments, the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device 140; or the MAC address of the first AP device 110.

[0197] In some embodiments, the components for performing operations related to the STA device 140 include: components for sending, to a second AP device 120, a link metric query TLV for the STA device 140, where the link metric query TLV includes the device identifier; and components for receiving, from the second AP device 120, a link metric response TLV, where the link metric response TLV includes the device identifier and link metric information of the STA device 140.

[0198] In some embodiments, the components for performing operations related to the STA device 140 include: components for sending a Quality of Service (QoS) management policy TLV to at least one of the first AP device 110 or the second AP device 120, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

[0199] In some embodiments, the components for performing operations related to the STA device 140 include: components for receiving a QoS management descriptor TLV for the STA device 140 from the first AP device 110, where the QoS management descriptor TLV includes a device identifier and QoS management information for the STA device 140; and components for sending the QoS management descriptor TLV to the second AP device 120.

[0200] In some embodiments, the QoS management descriptor TLV is received from the first AP device 110 included in a QoS management communication message; or the QoS management descriptor TLV is sent to the second AP device 120 included in a service priority request message.

[0201] In some embodiments, the components for performing operations related to the STA device 140 include: components for sending an association control request TLV to the second AP device 120, where the association control request TLV includes a device identifier and association control information for the STA device 140.

[0202] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 comply with the Wi-Fi Alliance EasyMesh specification.

[0203] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1000. In some embodiments, the components include at least one processor and at least one memory storing computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the execution of the apparatus.

[0204] In some example embodiments, an apparatus capable of performing method 1100 (e.g., implemented at the STA device 140) may include components for performing the respective steps of method 1100. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0205] In some embodiments, the apparatus may include: components for obtaining, during an association process with a first AP device 110, a device identifier assigned by the first AP device 110 to a STA device 140 from the first AP device 110; and components for performing communication with a second AP device 120 based on the device identifier.

[0206] In some embodiments, the components for performing communication with a second AP device 120 include: components for obtaining, during an association process with the second AP device 120 based on the device identifier, the same device identifier assigned by the second AP device 120 to the STA device 140 from the second AP device 120.

[0207] In some embodiments, the components for performing communication with a second AP device 120 include: components for sending a probe request message to the second AP device 120, where the probe request message includes the device identifier.

[0208] In some embodiments, the components for performing communication with a second AP device 120 include: components for sending an association request message or a probe request message to the second AP device 120, where the association request message or the probe request message includes the device identifier.

[0209] In some embodiments, the first AP device 110, the second AP device 120, and the control device 130 belong to an EasyMesh network.

[0210] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 1100. In some embodiments, the components include at least one processor and at least one memory storing computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to execute.

[0211] Figure 12 is a simplified block diagram of an electronic device 1200 suitable for implementing embodiments of the present disclosure. The device 1200 may be provided to implement a communication device, such as Figure 1 the communication devices 110, 120, 130, 140 shown. As shown, the device 1200 includes one or more processors 1210, one or more memories 1220 are coupled to the processors 1210, and one or more communication modules 1240 are coupled to the processors 1210.

[0212] The communication module 1240 is used for two-way communication. For example, the communication module 1240 may include a transmitter, a receiver, or a transceiver for embodiments of the present disclosure. The communication interface may represent any interface necessary for communicating with other network elements.

[0213] The processor 1210 can be of any type suitable for the local technical network and can include, but is not limited to, a general-purpose computer, a special-purpose computer, a microcontroller, a digital signal controller (DSP), and one or more in a controller-based multi-core controller architecture. The device 1200 can have multiple processors, such as an application-specific integrated circuit chip, which is subordinate to a clock synchronized with the main processor in time.

[0214] The memory 1220 can include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1224, erasable programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1222 and other volatile memories that do not persist during a power-off duration.

[0215] The computer program 1230 includes computer-executable instructions executed by the associated processor 1210. The program 1230 can be stored in the ROM 1220. The processor 1210 can perform any suitable actions and processes by loading the program 1230 into the RAM 1222.

[0216] Embodiments of the present disclosure can be implemented by means of the program 1230, such that the device 1200 can execute any process of the embodiments of the present disclosure as discussed with reference to Figures 2 to 7 The embodiments of the present disclosure can also be implemented by hardware or by a combination of software and hardware.

[0217] In some embodiments, the program 1230 can be tangibly embodied in a computer-readable medium, which can be included in the device 1200 (such as in the memory 1220) or other storage devices accessible by the device 1200. The program 1230 can be loaded from the computer-readable medium into the RAM 1222 for execution. The computer-readable medium can include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0218] Figure 13 An example of a computer-readable medium 1300 in the form of a CD or DVD is shown. The program 1230 is stored on the computer-readable medium.

[0219] In general, the various embodiments of the present disclosure may be implemented in hardware or specific circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, a microprocessor, or other computing devices. Although the various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented as, by way of non-limiting example, hardware, software, firmware, specific circuits or logic, general-purpose hardware or a controller or other computing devices, or some combination thereof.

[0220] Embodiments of the present disclosure also provide at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the methods 800, 900, 1000, and 1100 as referenced above Figures 8 to 11 Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules may be combined or divided as needed. The machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in local and remote storage media.

[0221] The computer program code for implementing the methods of the embodiments of the present disclosure may be written in one or more programming languages. This computer program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the program code is executed by the computer or other programmable data processing device, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code may be executed entirely on the computer, partially on the computer, as a stand-alone software package, partially on the computer and partially on a remote computer, or entirely on a remote computer or server.

[0222] In the context of the embodiments of the present disclosure, the computer program code or related data may be carried by any suitable carrier such that the device, apparatus, or processor can perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and the like. Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, etc.

[0223] A computer-readable medium can be any tangible medium that contains or stores a program for or relating to an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of a computer-readable storage medium include an electrical connection with one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical storage device, a magnetic storage device, or any suitable combination thereof. As used herein, the term "non-transitory" or "non-transient" is a limitation on the medium itself (i.e., tangible, rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0224] Moreover, although the operations of the methods of the embodiments of the present disclosure are described in a specific order in the drawings, this is not required or implied to perform these operations in that specific order, or that all of the illustrated operations must be performed to achieve the desired result. On the contrary, the steps depicted in the flowchart can be changed in the order of execution. Additionally or alternatively, certain steps can be omitted, multiple steps can be combined into one step for execution, and / or one step can be decomposed into multiple steps for execution. It should also be noted that the features and functions of two or more devices according to the embodiments of the present disclosure can be embodied in one device. Conversely, the features and functions of one device described above can be further divided and embodied by multiple devices.

[0225] Although the embodiments of the present disclosure have been described with reference to several specific embodiments, it should be understood that the present disclosure is not limited to the specific embodiments disclosed. The present disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A first access point (AP) device, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the first AP device to at least: allocate a device identifier to a station (STA) device during an association process with the STA device; and send the device identifier to at least one of a second AP device or a control device.

2. The first AP device according to claim 1, wherein the device identifier is sent included in a 1905 topology notification message.

3. The first AP device according to claim 2, wherein the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

4. The first AP device according to claim 2 or 3, wherein the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: the media access control (MAC) address of the STA device; or the MAC address of the first AP device.

5. The first AP device according to any one of claims 1-4, wherein the first AP device is further caused to: receive a quality of service (QoS) management policy TLV from the control device, wherein the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

6. The first AP device according to claim 5, wherein the first AP device is further caused to: receive a QoS processing negotiation request from the STA device; and determine whether to allow the QoS processing negotiation request of the STA device based on the QoS management policy TLV.

7. The first AP device according to any one of claims 1-6, wherein the first AP device is further caused to: send a QoS management descriptor TLV to the control device, wherein the QoS management descriptor TLV includes the device identifier and QoS operation information for a data stream of the STA device.

8. The first AP device according to claim 7, wherein the QoS management descriptor TLV is sent included in a QoS management notification message.

9. The first AP device according to any one of claims 1-8, wherein the first AP device, the second AP device, and the control device comply with the Wi-Fi Alliance EasyMesh specification.

10. A second access point (AP) device, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the second AP device to at least: receive from a first AP device the device identifier allocated by the first AP device to a station (STA) device; and perform communication with the STA device based on the device identifier.

11. The second AP device according to claim 10, wherein the second AP device is further caused to: Store the device identifier.

12. The second AP device according to claim 10 or 11, wherein the device identifier is received included in a 1905 topology notification message.

13. The second AP device according to claim 12, wherein the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

14. The second AP device according to claim 12 or 13, wherein the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: The media access control (MAC) address of the STA device; or The MAC address of the first AP device.

15. The second AP device according to any one of claims 10-14, wherein the second AP device is caused to communicate with the STA device by: During the association process with the STA device based on the device identifier, allocate the same device identifier to the STA device.

16. The second AP device according to any one of claims 10-15, wherein the second AP device is caused to communicate with the STA device by: Receive a link metric query TLV for the STA device from a control device, wherein the link metric query TLV includes the device identifier; Based on receiving the link metric query TLV, monitor probe request messages sent by the STA device, wherein the probe request messages include the device identifier; In the case of monitoring the probe request message, obtain link metric information of the STA device based on the probe request message; And Send a link metric response TLV to the control device, wherein the link metric response TLV includes the device identifier and the link metric information.

17. The second AP device according to any one of claims 10-16, wherein the second AP device is further caused to: Receive a quality of service (QoS) management policy TLV from a control device, wherein the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

18. The second AP device according to claim 17, wherein the second AP device is caused to communicate with the STA device by: Receive a QoS processing negotiation request from the STA device; and Based on the QoS management policy TLV, determine whether to allow the QoS processing negotiation request of the STA device.

19. The second AP device according to any one of claims 10-18, wherein the second AP device is further caused to: Receive a QoS management descriptor TLV from a control device, where the QoS management descriptor TLV includes the device identifier and QoS management information for the STA device.

20. The second AP device according to claim 19, wherein the QoS management descriptor TLV is received included in a service priority request message.

21. The second AP device according to any one of claims 10-20, wherein the second AP device is caused to communicate with the STA device by: Receiving an association control request TLV from a control device, where the association control request TLV includes the device identifier and association control information for the STA device; Receiving an association request message or a probe request message from the STA device, where the association request message or the probe request message includes the device identifier; And Processing the association request message or the probe request message of the STA device based on the association control information.

22. The second AP device according to any one of claims 10-21, wherein the first AP device, the second AP device, and the control device comply with the Wi-Fi Alliance EasyMesh specification.

23. A control device, Comprising: At least one processor; And At least one memory storing instructions that, when executed by the at least one processor, cause the control device to at least: Receive the device identifier assigned by the first access point (AP) device to a station (STA) device; and Control operations related to the STA device based on the device identifier.

24. The control device according to claim 23, wherein the control device is further caused to: Store the device identifier.

25. The control device according to claim 23 or 24, wherein the device identifier is received included in a 1905 topology notification message.

26. The control device according to claim 25, wherein the 1905 topology notification message includes a client association event type length value (TLV), the client association event TLV includes bit information, and the bit information is used to indicate whether the device identifier is used.

27. The control device according to claim 25 or 26, wherein the 1905 topology notification message further includes a client device identifier TLV, and the client device identifier TLV includes the device identifier and at least one of the following: The media access control (MAC) address of the STA device; or The MAC address of the first AP device.

28. The control device according to any one of claims 23-27, wherein the control device is caused to perform operations related to the STA device by: Sending a link metric query TLV for the STA device to a second AP device, where the link metric query TLV includes the device identifier; and Receive a link metric response TLV from the second AP device, where the link metric response TLV includes the device identifier and link metric information of the STA device.

29. The control device according to any one of claims 23-28, wherein the control device is caused to perform operations related to the STA device by: Send a quality of service (QoS) management policy TLV to at least one of the first AP device or the second AP device, where the QoS management policy TLV includes a list of device identifiers that do not allow QoS processing negotiation.

30. The control device according to any one of claims 23-29, wherein the control device is caused to perform operations related to the STA device by: Receive a QoS management descriptor TLV for the STA device from the first AP device, where the QoS management descriptor TLV includes the device identifier and QoS management information for the STA device; and Send the QoS management descriptor TLV to the second AP device.

31. The control device according to claim 30, wherein at least one of the following: The QoS management descriptor TLV is received from the first AP device included in a QoS management communication message; or The QoS management descriptor TLV is sent to the second AP device included in a service priority request message.

32. The control device according to any one of claims 23-31, wherein the control device is caused to perform operations related to the STA device by: Send an association control request TLV to the second AP device, where the association control request TLV includes the device identifier and association control information for the STA device.

33. The control device according to any one of claims 23-32, wherein the first AP device, the second AP device, and the control device comply with the Wi-Fi Alliance EasyMesh specification.

34. A method, comprising: At a first access point (AP) device, during an association process with a station (STA) device, assign a device identifier to the STA device; and Send the device identifier to at least one of a second AP device or a control device.

35. A method, comprising: At a second access point (AP) device, receive the device identifier assigned by the first AP device to a station (STA) device from the first AP device; and Based on the device identifier, perform communication with the STA device.

36. A method, comprising: At a control device, receive the device identifier assigned by the first AP device to a station (STA) device from the first AP device; and Based on the device identifier, control operations related to the STA device.

37. A device, comprising: Components for assigning a device identifier to the STA device during an association process with the STA device at a first access point (AP) device; and A component that sends the device identifier to at least one of a second AP device or a control device.

38. A device, comprising: A component for receiving, at a second access point (AP) device, a device identifier assigned by a first AP device to a station (STA) device from the first AP device; and A component for performing communication with the STA device based on the device identifier.

39. A device, comprising: A component for receiving, at a control device, a device identifier assigned by a first access point (AP) device to a station (STA) device from the first AP device; and A component for controlling operations related to the STA device based on the device identifier.

40. A computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform the method according to any one of claims 34-36.

Images