Communication methods and devices, computer programs, and electronic devices for non-AP MLDs.

Abstract

The present disclosure provides a communication method and device for non-AP MLD, a storage medium, and an electronic device, including the steps of: a distributed MLD controller collecting link information of each link between the non-AP MLD and a plurality of AP MLDs from the AP MLD; and a distributed MLD controller selecting a target AP MLD from the plurality of AP MLDs based on the link information of each link, and communicating with the non-AP MLD via the target AP MLD. By adopting the above technical aspects, the problem that the conventional technology relies on conventional roaming technology to adjust the transmission link when the AP MLD communicates with the non-AP MLD, which causes excessive delay in data communication, is solved.

Description

Technical Field

[0001] This disclosure claims priority based on a Chinese patent application filed with the China National Intellectual Property Administration on May 30, 2022, with an application number of 202210601048.2 and an invention title of "Communication Method and Apparatus, Storage Medium, and Electronic Device for non-AP MLD", the entire content of which is incorporated herein by reference.

[0002] This disclosure relates to the field of communications, and more particularly, to a communication method and apparatus, a storage medium, and an electronic device for non-AP MLD.

Background Art

[0003] In future home environments, most smart home devices will be in a networking scenario of an access point multi-link device (AP MLD for short). In the networking scenario of AP MLD, when the AP MLD communicates with a non-access point multi-link device (non-AP MLD for short), it is necessary to complete the adjustment of the transmission link in a roaming manner. On the other hand, when the non-AP MLD roams, it is necessary to perform operations such as disassociation, re-association, and 4-way handshake. Due to these operations, the delay of data communication exceeds 50 ms.However, as a 7th generation wireless network communication technology, Wi-Fi 7 technology needs to control the delay of data communication within 5 ms. Therefore, the conventional roaming technology fails to meet the technical requirements of Wi-Fi 7.

[0004] Thus, in AP MLD networking scenarios, if conventional roaming methods are used to adjust the transmission link during communication between AP ML and non-AP MLD, the data communication delay will no longer meet the technical requirements of Wi-Fi 7. On the other hand, conventional technology has no choice but to rely on conventional roaming technology to achieve the adjustment of the transmission link during communication between AP ML and non-AP MLD.

[0005] In conventional technology, when an AP MLD communicates with a non-AP MLD, it relies on conventional roaming technology to adjust the transmission link, which can cause excessive delays in data communication. Currently, no effective countermeasures have been proposed to address this problem.

[0006] Therefore, it is necessary to improve the related technologies in order to overcome the aforementioned shortcomings in those technologies. [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] Embodiments of this disclosure provide a communication method and apparatus for non-AP MLDs, a storage medium, and an electronic device to at least solve the problem in the prior art where AP MLDs rely on conventional roaming technology to adjust the transmission link when communicating with non-AP MLDs, which can cause excessive delays in data communication. [Means for solving the problem]

[0008] One embodiment of the present disclosure provides a method for communicating with a non-AP MLD, comprising the steps of: a distributed MLD controller collecting link information from an AP MLD for each link which is a link between a non-AP MLD and a plurality of AP MLDs; and the distributed MLD controller selecting a target AP MLD from the plurality of AP MLDs based on the link information for each link and communicating with the non-AP MLD via the target AP MLD.

[0009] In another embodiment of the present disclosure, a communication device for a non-AP MLD is further provided, comprising a management module configured to collect link information from an AP MLD for each link which is a link between a non-AP MLD and a plurality of AP MLDs, and the management module configured to select a target AP MLD from the plurality of AP MLDs based on the link information for each link, and to communicate with the non-AP MLD via the target AP MLD. [Effects of the Invention]

[0010] According to this disclosure, the distributed MLD controller collects link information from the AP MLDs for each link between the non-AP MLD and multiple AP MLDs, selects a target AP MLD from among the multiple AP MLDs based on this link information, and communicates with the non-AP MLD through this target AP MLD. By adopting the above technical embodiment, link information is collected for each link between the non-AP MLD and multiple AP MLDs, and based on the link information, the optimal AP MLD is selected in real time from among the multiple AP MLDs, the link between this AP MLD and the non-AP MLD is made the transmission link, and the transmission link adjustment is realized in a non-roaming manner, thereby avoiding the delay problem caused by relying on roaming to adjust the transmission link. Therefore, the problem that arises when the AP MLD communicates with the non-AP MLD, which relies on conventional roaming technology to adjust the transmission link and causes excessive delay in data communication, can be solved.

[0011] The drawings described herein constitute part of this disclosure to further illustrate it, and the exemplary embodiments and descriptions herein are illustrative of this disclosure and do not unduly limit it. [Brief explanation of the drawing]

[0012] [Figure 1]This is a hardware configuration block diagram of a computer terminal for an optional non-AP MLD communication method according to an embodiment of the present disclosure. [Figure 2] This is a schematic diagram illustrating the conventional data roaming process in related technologies. [Figure 3] This is an architectural diagram of a multilink device (MLD) in related technologies. [Figure 4] This is a flowchart illustrating a communication method for an optional non-AP MLD according to the embodiment of this disclosure. [Figure 5] This is an architectural diagram of an optional distributed multilink device (MLD) according to an embodiment of the present disclosure. [Figure 6] This is a flowchart illustrating the construction and maintenance of an optional distributed multilink device (MLD) according to the embodiments of this disclosure. [Figure 7] This is a flowchart of an optional Distributed MLD Service Management according to the embodiments of this disclosure. [Figure 8] This is a schematic diagram showing data communication via link1 using an optional non-AP MLD according to Embodiment 1 of this disclosure. [Figure 9] This is a schematic diagram showing data communication via link2 using an optional non-AP MLD according to Embodiment 1 of this disclosure. [Figure 10] This is a schematic diagram showing data communication via link2 using an optional non-AP MLD according to Embodiment 1 of this disclosure. [Figure 11] This is a schematic diagram showing data communication via link1 using an optional non-AP MLD according to Embodiment 2 of this disclosure. [Figure 12] This is a schematic diagram showing an optional multilink transmission via link1 and link3 by AP MLD1 according to Embodiment 2 of this disclosure. [Figure 13] This is a schematic diagram showing an optional multilink transmission via link1, link2, and link3 by AP MLD1 according to Embodiment 2 of this disclosure. [Figure 14]Schematic diagram showing optional multi-link communication between an AP MLD and a non-AP MLD according to Embodiment 3 of the present disclosure. [Figure 15] Schematic diagram showing optional reduction from link1, link2, and link3 to link1 and link3 of a transmission link according to Embodiment 3 of the present disclosure. [Figure 16] Schematic diagram showing optional switching from link1 and link3 to link2 of a transmission link according to Embodiment 3 of the present disclosure. [Figure 17] Schematic diagram showing optional mode switching between a distributed MLD and a conventional MLD according to Embodiment 4 of the present disclosure. [Figure 18] Block diagram (Part 1) of a communication device of an optional non-AP MLD according to an embodiment of the present disclosure. [Figure 19] Block diagram (Part 2) of a communication device of an optional non-AP MLD according to an embodiment of the present disclosure.

Mode for Carrying Out the Invention

[0013] Hereinafter, in order for those skilled in the art to better understand the aspects of the present disclosure, the technical aspects of the embodiments of the present disclosure will be clearly and completely described while referring to the drawings of the embodiments of the present disclosure. It is needless to say that the described embodiments are only some of the embodiments of the present disclosure, not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without the need for creative labor should also be included within the protection scope of the present disclosure.

[0014] In addition, terms such as "first", "second", etc. in the specification, claims, and the above-described drawings of the present disclosure are for distinguishing similar objects and not for describing a specific order or priority. It should be understood that the numbers used in this way can be interchanged as appropriate in order to enable the embodiments of the present disclosure described herein to be implemented in an order other than the order shown or described herein. Also, the terms "comprising", "having", and any variations thereof are intended to cover what is included without being exclusive. For example, a process, method, system, product, or device including a series of steps or units need not be limited to the clearly shown steps or units, and can include steps or units not clearly shown for these processes, methods, products, or devices, or other steps or units inherent to these.

[0015] Embodiments of the methods provided in the embodiments of this disclosure can be executed on a computer terminal or a similar arithmetic unit. Taking execution on a computer terminal as an example, Figure 1 is a hardware configuration block diagram of a computer terminal for an optional non-AP MLD communication method according to an embodiment of this disclosure. As shown in Figure 1, the computer terminal may include one or more (only one is shown in Figure 1) processors 103 (the processors 103 may include, but are not limited to, a microprocessor unit (simply MPU) or a programmable logic device (simply PLD)) and memory 104 for storing data. In one exemplary embodiment, the computer terminal may further include a transmission device 106 and an input / output device 108 for communication functions. Those skilled in the art will understand that the configuration shown in Figure 1 is schematic and not limiting to the configuration of the computer terminal. For example, the computer terminal may further include more or fewer components than those shown in Figure 1, or may have the same functions as those shown in Figure 1 or a different configuration than those shown in Figure 1.

[0016] Memory 104 can store computer programs such as software programs and modules of application software, such as a computer program corresponding to the communication method of non-AP MLD in embodiments of this disclosure, and the processor 103 executes various functional applications and data processing by executing the computer programs stored in memory 104, i.e., realizing the method described above. Memory 104 may include high-speed random-access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 104 may further include memory located remotely from the processor 103, and these remote memories may be connected to computer terminals via a network. Examples of the network include, but are not limited to, the Internet, intranet, local area network, mobile communication network, and combinations thereof.

[0017] The transmission device 106 transmits and receives data over a network. Specific examples of the network include a wireless network provided by the computer terminal's communication vendor. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that is connected to other network devices via a base station and can communicate with the Internet. In another example, the transmission device 106 may be a radio frequency (RF) module that communicates with the Internet wirelessly.

[0018] Next, we will describe the relevant technologies in this disclosure. Roaming: As shown in Figure 2, Figure 2 is a schematic diagram illustrating the flow of conventional data roaming in related technologies. In Figure 2, the conventional data roaming flow includes the process from when Station (STA) disassociates itself from the first radio access point (AP1) to when STA re-establishes its association with the second radio access point (AP2). During the evolution of Wi-Fi technology, technologies such as 802.11V's BSS transition management (BTM, where BSS is the base station subsystem), 802.11r's fast roaming, and 802.11ai's Fast Initial Link Set Up (FILS) have been introduced to improve the roaming experience. Although each has different application scenarios, in terms of roaming latency, 802.11r's fast roaming is currently the closest to Wi-Fi technology, and 802.11r's fast roaming can reduce roaming latency to around 50ms. This disclosure focuses on 802.11r fast roaming technology.

[0019] Multilink: Multi-link operation (MLO), the technology proposed in the current 802.11be, is a key technological direction for the future of Wi-Fi 7. Multilink transmission offers relatively superior performance in terms of improved throughput, reduced latency, and resistance to disturbances. A multi-link device (MLD) is a device equipped with MLO functionality. As shown in Figure 3, Figure 3 is an architectural diagram of a multi-link device (MLD) in related technologies. In Figure 3, the functions of the Media Access Control (MAC) layer are divided as follows: Specifically, the framing details related to the Mac Protocol Data Unit (MPDU) and the frame aggregation function of the Aggregation Medium Access Control Protocol Data Unit (A-MPDU) are distributed to the MLD lower MAC sub-layer, and the remaining MAC functions are distributed to the MLD upper MAC sub-layer. The traffic identifier and link mapping information (TID-to-link mapping module) in the special upper MAC sublayer is used to realize a specific transmission path for data and management frames, i.e., to realize the transmission of management and data frames through a certain link.

[0020] Figure 4 is a flowchart of an optional non-AP MLD communication method applied to a distributed MLD controller according to an embodiment of the present disclosure. As shown in Figure 4, this non-AP MLD communication method includes the following steps S402 to S404.

[0021] In step S402, the distributed MLD controller collects link information for each link from the AP MLD, where each link is a link between a non-AP MLD and multiple AP MLDs.

[0022] In step S404, the distributed MLD controller selects a target AP MLD from among the multiple AP MLDs based on the link information of each link, and communicates with the non-AP MLD via the target AP MLD.

[0023] Through the steps described above, the distributed MLD controller collects link information from the AP MLDs regarding the links between the non-AP MLD and multiple AP MLDs. Based on this link information, it selects a target AP MLD from among the multiple AP MLDs and communicates with the non-AP MLD through this target AP MLD. By adopting the above technical configuration, the controller collects link information regarding the links between the non-AP MLD and multiple AP MLDs, and based on this link information, selects the optimal AP MLD from among the multiple AP MLDs in real time. This AP MLD then uses the link between the non-AP MLD and the non-AP MLD as the transmission link, enabling transmission link adjustment in a non-roaming manner. This avoids the delay problems caused by relying on roaming to adjust the transmission link. Therefore, the conventional technology can solve the problem of excessive delay in data communication caused by relying on conventional roaming technology to adjust the transmission link when the AP MLD communicates with the non-AP MLD.

[0024] Furthermore, the distributed MLD controller described above is distributed across PON chips. First, to aid in understanding this disclosure, the architecture of the distributed MLD will be described. Figure 5 is an architecture diagram of an optional distributed multilink device MLD according to an embodiment of this disclosure. In Figure 5, the IEEE 802.1x protocol (access control function), A-MSDU frame aggregation, and MPDU frame encryption (key management) functions located in the MLD mac upper sublayer of the original AP MLD architecture are moved upward to the distributed MLD controller chip of the home distributed MLD controller device. The MLD retains the rest of its architecture. In particular, the distributed MLD controller chip and AP MLD are newly equipped with Distributed MLD Service Management functionality, which includes, but is not limited to, a Management module and a Multilink Device Traffic Scheduling MLD Traffic Schedule module, and is configured to guide communication between the distributed MLD controller and target AP MLDs and to enable scheduling management of data and management information for multiple AP MLDs.

[0025] In the original MLD architecture, one or more of the following features located in the MLD mac upper supporter—IEEE 802.1x (access control function), A-MSDU frame aggregation, and MPDU frame encryption (key management)—can be optionally moved upward to the distributed MLD controller chip of the home distributed MLD controller device. Moving IEEE 802.1x upward can enhance the management and control capabilities of the distributed MLD controller chip, MSDU frame aggregation can improve the transmission efficiency of the transmission channel, and MPDU frame encryption can replace transmission channel encryption and be used for exchanging key information between the distributed MLD controller and multiple AP MLDs.

[0026] The following embodiment consists of two parts: the first part is the construction and maintenance of a distributed MLD, and the second part is the Distributed MLD Service Management flow.

[0027] Part 1: Building and Maintaining a Distributed MLD In one exemplary embodiment, a distributed MLD controller receives a discovery request message sent from the AP MLD via unicast or broadcast before collecting link information for each link from the AP MLD, identifies the role of the AP MLD, and declares the role information of the distributed MLD controller by replying based on the discovery request message or by actively sending a discovery response.

[0028] Furthermore, the AP MLD declares its role as a multilink device by sending a discovery request message using a unicast or broadcast method. In this embodiment, the role of the distributed MLD controller is that of a multilink device group manager.

[0029] In one exemplary embodiment, the distributed MLD controller receives a join request message sent from the AP MLD before collecting link information for each link from the AP MLD, collects and maintains the multilink information contained in the join request message, and either replies to the join request message with a join response message permission message or refuses the AP MLD to join the Distributed MLD group.

[0030] In one exemplary embodiment, the distributed MLD controller receives notification messages sent from the AP MLD and updates and maintains the multilink information contained in the notification messages before collecting link information for each link from the AP MLD.

[0031] In one exemplary embodiment, before collecting link information for each link from the AP MLD, the distributed MLD controller sends a configuration request message containing the link information for each of the multiple AP MLDs to be maintained, either by unicast or broadcast, requesting the AP MLD to change its configuration according to the link information.

[0032] In one exemplary embodiment, a distributed MLD controller receives data and management messages transmitted from the AP MLD and / or transmits data and management messages to the AP MLD before collecting link information for each link from the AP MLD.

[0033] Next, to aid in understanding the embodiments described above, the complete flow of construction and maintenance of a distributed multilink device (MLD) will be further described. Figure 6 is a flowchart of construction and maintenance of an optional distributed multilink device (MLD) according to the embodiments of this disclosure. As shown in Figure 6, this flow of construction and maintenance of a distributed multilink device (MLD) includes the following phases.

[0034] Dynamic Host Configuration Protocol (DHCP) Phase: The AP MLD device initiates registration with the DHCP server via its Multilink Device Media Access Control (MLD) MAC, obtains an Internet Protocol (IP) address, and configures it for subsequent communication.

[0035] Discovery Phase: AP MLDs and distributed MLD controllers explore each other through a certain mechanism, preparing for the subsequent construction of a multilink device group (MLD group). This mechanism can be understood as follows:

[0036] Distributed MLD controller: It is compatible with receiving discovery request messages sent from AP MLD via unicast or broadcast, identifying the sender's role (multilink device), and declaring its own role information (multilink device group manager) by replying to the discovery request message or actively sending a discovery response.

[0037] AP MLD side: Declares its role (multilink device) by sending a discovery request message via unicast or broadcast, and is responsible for finding the multilink device group manager. It also receives a discovery response message and identifies the role of the sender.

[0038] Joining Phase: The AP MLD sends its link information and other data to the distributed MLD controller, which then decides whether or not to add this AP MLD to the distributed MLD group.

[0039] Notification Phase: If the link information of an AP MLD changes, the AP MLD notifies the distributed MLD controller of this change by sending a notification. For example, if an AP MLD originally supported three links but for some reason can now only support two, the AP MLD needs to send a notification to the distributed MLD controller informing it of the change in relevant information.

[0040] Configuration Phase: The distributed MLD controller integrates the link information of all AP MLDs added to the MLD group and configures this information in each AP MLD. Then, during subsequent capability announcement and execution, the AP MLDs must contain the link information of other AP MLDs. Therefore, from the perspective of non-AP MLDs, the distributed MLD group is a broad MLD.

[0041] For example, a distributed MLD group might include AP MLD1 (link1, link2, link3), AP MLD2 (link4, link5, link6), and AP MLD3 (link7, link8). A conventional AP MLD only contains its own multilink information in its beacon frame. For example, AP MLD1 contains only information for link1, link2, and link3. On the other hand, in a distributed MLD, AP MLD1 needs to contain information for link1 through link8. From the perspective of a non-AP MLD, a distributed MLD is an independent AP MLD device with eight links from link1 to link8.

[0042] Data Transmission / Management Transmission Phase: Once the data and management channels between the AP MLD and the distributed MLD controller are established, the distributed MLD controller on the data channel communicates with the AP MLD via scheduling using its Traffic Schdule module. The distributed MLD controller on the management channel periodically collects link information from each AP, and reporting changes in AP link information can be actively triggered.

[0043] Reconfiguration Phase: When the distributed MLD controller detects that the link information of a particular AP MLD has changed, it triggers the reconfiguration of the link information for each AP MLD.

[0044] Part 2: Flow of Distributed MLD Service Management In one exemplary embodiment, the distributed MLD controller is configured with the Distributed MLD Service Management function, and the AP MLD is configured with the Distributed MLD Service Management function.

[0045] The Distributed MLD Service Management function described above includes, but is not limited to, guiding communication between the distributed MLD controller and the target AP MLD. Furthermore, the core technology of this disclosure is the Distributed MLD Service Management function, which enables dynamic adjustment of the target AP MLD and related links through periodic collection of link information, ultimately allowing non-AP MLDs to complete transmission link adjustment in a non-roaming manner, and reducing transmission delay from the 50ms or more originally required for roaming to within 1ms selected by flow scheduling. The Distributed MLD Service Management function can be implemented by a Management module and an MLD Traffic Schedule module, etc. The Management module is responsible for building the Distributed MLD group and maintaining management information, as well as implementing functions such as related information, periodic link information, selection of target AP MLDs and link switching, and maintaining the management link. The MLD Traffic Schedule is responsible for managing and maintaining the data links on the distributed MLD controller and AP MLD side.

[0046] In one exemplary embodiment, the distributed MLD controller receives a multilink association request forwarded by the AP MLD and sent from the non-AP MLD, where the multilink association request is intended to indicate multiple links associated with the non-AP MLD. The distributed MLD controller also replies to the multilink association request with an allow or reject message, and if it replies with a reject message, it sends recommended multilink information to the non-AP MLD and instructs the non-AP MLD to restart the multilink association request according to the multilink information.

[0047] In one exemplary embodiment, the distributed MLD controller periodically sends link measurement requests to the plurality of AP MLDs and receives link information for each link sent by the plurality of AP MLDs in response to the link measurement requests.

[0048] Optionally, in this embodiment, link measurement requests may be periodically sent to the multiple AP MLDs via the Management of the distributed MLD controller, requesting the multiple AP MLDs to collect link information for each link. Here, the link information includes, but is not limited to, the operation type, channel number, physical negotiation rate, real-time rate, non-AP MLD signal strength, neighbor information, etc.

[0049] In one exemplary embodiment, the MLD Traffic Schedule module in the distributed MLD controller schedules data to guide the target AP MLD to communicate with the non-AP MLD.

[0050] In one exemplary embodiment, if it is detected that the link information has changed, the method further includes at least one of the following steps: the distributed MLD controller guides the target subSTA in the non-AP MLD to roam and enables link switching; and the distributed MLD controller selects a new target AP MLD and guides the new target AP MLD to communicate with the non-AP MLD.

[0051] In this embodiment, when the link quality of a non-AP MLD changes, the distributed MLD controller has two options: 1) Guide a sub-STA within the non-AP MLD to roam and enable link switching. That is, the distributed MLD controller guides the non-AP MLD to connect to the recommended link. 2) The distributed MLD controller selects a new target AP MLD, and the MLD Traffic Schedule module guides the new target AP MLD to communicate with the non-AP MLD.

[0052] Next, to aid in understanding the embodiments described above, the complete flow of building and maintaining a distributed multilink device (MLD) will be further described. Figure 7 is an optional flowchart of Distributed MLD Service Management according to the embodiments of this disclosure, and as shown in Figure 7, this Distributed MLD Service Management flow includes the following steps.

[0053] Step 1: The Configuration and reconfiguration process completes the updating of the link information for the distributed MLD. Specifically, this refers to the Configuration and reconfiguration phases in the flow of building and maintaining the distributed MLD.

[0054] Step 2: Each AP MLD independently transmits a beacon frame containing all link information within the distributed MLD.

[0055] Step 3: If a Non-AP MLD actively initiates a multilink association, it may not be reasonable for the Non-AP MLD to request a link association because it cannot recognize that the multilinks are distributed across different AP MLDs.

[0056] Step 4: The distributed MLD controller guides non-AP MLDs to connect to recommended links. The distributed MLD controller periodically collects link information for each AP MLD, selects recommended links based on the AP MLDs, and guides non-AP MLDs to connect to the recommended links.

[0057] Step 5: The distributed MLD controller selects a target AP MLD for the non-AP MLD. If a non-AP MLD is associated with multiple AP MLDs via multilink, the distributed MLD controller will select only one target AP MLD to communicate with the non-AP MLD at the same time.

[0058] Step 6: When the link quality of non-AP MLD changes, the distributed MLD controller has two options:

[0059] (1) A sub-STA within the non-AP MLD is guided to roam, enabling link switching. In other words, the distributed MLD controller guides the non-AP MLD to connect to the recommended link.

[0060] (2) The distributed MLD controller selects a new target AP MLD, and the MLD Traffic Schedule module guides the new target AP MLD to communicate with the non-AP MLD.

[0061] This disclosure constructs an architecture based on a distributed MLD scheme. While the above embodiments describe how the distributed MLD controller side implements the distributed MLD scheme of this disclosure, the following embodiments describe how the other side—AP MLD—implements the solution.

[0062] The following embodiment consists of two parts: the first part is the construction and maintenance of a distributed MLD, and the second part is the Distributed MLD Service Management flow.

[0063] Part 1: Building and Maintaining a Distributed MLD In one exemplary embodiment, the AP MLD sends a discovery request message in a unicast or broadcast manner, declares its role as a multilink device, searches for the multilink device group manager, and also receives a discovery response message and identifies the role information of the sender of the discovery response.

[0064] In one exemplary embodiment, the AP MLD sends a join request message containing its multilink information. The AP MLD also receives a join response message and recognizes whether the request to join the Distributed MLD group has been approved.

[0065] In one exemplary embodiment, when the multilink information of the AP MLD changes, a notification message is actively sent to the distributed MLD controller to inform it of the updated multilink information.

[0066] In one exemplary embodiment, the AP MLD receives a unicast or broadcast configuration request and identifies the link information contained in the configuration request. The AP MLD then replies to the configuration request message with a configuration response message, indicating whether to allow or deny the request for information configuration. If allowed, the received link information must be updated with local link information, and the updated link information must be included in subsequent beacon frames, etc.

[0067] In one exemplary embodiment, the AP MLD receives a unicast or broadcasted reconfiguration request and identifies the link information contained in the reconfiguration request. The AP MLD also replies to the reconfiguration request message with a reconfiguration response message, indicating whether to allow or deny the request for information configuration. If allowed, the received link information must be updated with local link information, and the updated link information must be included in subsequent beacon frames, etc.

[0068] In one exemplary embodiment, AP MLD receives data and management messages sent from a distributed MLD controller and sends data and management messages back to the distributed MLD controller.

[0069] Part 2: Flow of Distributed MLD Service Management In one exemplary embodiment, the AP MLD forwards the multilink association request sent from the non-AP MLD to the distributed MLD controller, receives the association response message that the distributed MLD controller sends back to the multilink association request, and forwards it to the non-AP MLD. If this response message contains recommended link information, the non-AP MLD may restart the multilink association request with the recommended link information.

[0070] In one exemplary embodiment, the AP MLD receives link measurement requests from a distributed MLD controller and reports link quality information in real time. This link quality information includes, but is not limited to, the operation type, channel number, physical negotiation rate, real-time rate, non-AP MLD signal strength, and neighbor information.

[0071] In one exemplary embodiment, the AP MLD handles communication between a local AP MLD and a non-AP MLD, guided by a distributed MLD controller.

[0072] In one exemplary embodiment, the AP MLD responds to guidance from a distributed MLD controller to a non-AP MLD, such as roaming on a designated link, which is triggered by the MLD controller.

[0073] According to the embodiments described above, the conventional technology solves the problem that when an AP MLD communicates with a non-AP MLD, it relies on conventional roaming technology to adjust the transmission link, which causes excessive delays in data communication. To solve this problem, 1) this disclosure constructs an architecture based on a distributed MLD scheme and moves the IEEE 802.1x protocol (access control function), A-MSDU frame aggregation, and MPDU frame encryption (key management) functions of the MLD mac upper sublayer upward to the distributed MLD controller chip of the home distributed MLD controller device. In particular, a Distributed MLD Service Management function is added to the distributed MLD controller chip and AP MLD, and this function enables scheduling management of data and management information for multiple AP MLDs. This function includes, but is not limited to, the Management module and the MLD Traffic Schedule module. 2) This disclosure constructs a distributed MLD flow and describes the flow of building a distributed MLD group, MLD configuration, data transmission, etc. 3) This disclosure describes how the Distributed MLD Service Management flow is implemented, and how the distributed MLD controller, through this flow, enables the selection of a target AP MLD for a designated Non-AP MLD and flow scheduling functions, thereby avoiding roaming operations and reducing latency.

[0074] (Embodiment 1) In this embodiment, the three sub-STAs of the non-AP MLD are associated with one of the three sub-APs of the AP MLD.

[0075] As shown in Figure 8, Figure 8 is a schematic diagram illustrating data communication via link 1 by an optional non-AP MLD according to Embodiment 1 of this disclosure. In Figure 8, when a non-AP MLD is near AP MLD1, the distributed MLD controller periodically collects AP link information to determine that AP MLD1 is the target AP for this non-AP MLD. The distributed MLD controller then uses the MLD Traffic Schedule module to schedule a data flow to AP MLD1, enabling the non-AP MLD to communicate data via link 1.

[0076] As shown in Figure 9, Figure 9 is a schematic diagram illustrating data communication via link 2 by an optional non-AP MLD according to Embodiment 1 of this disclosure. In Figure 9, when a non-AP MLD moves near AP MLD2, the distributed MLD controller collects link information for each AP and determines that AP MLD2 is the target AP for this non-AP MLD. The distributed MLD controller then uses the MLD Traffic Schedule module to schedule a data flow to AP MLD2, enabling the non-AP MLD to communicate data via link 2.

[0077] As shown in Figure 10, Figure 10 is a schematic diagram illustrating data communication via link 2 by an optional non-AP MLD according to Embodiment 1 of this disclosure. In Figure 10, as the non-AP MLD continues to move near AP MLD3, the distributed MLD controller collects link information for each AP and determines that AP MLD3 is the target AP for this non-AP MLD. The distributed MLD controller then uses the MLD Traffic Schedule module to schedule a data flow to AP MLD3, enabling the non-AP MLD to communicate data via link 3.

[0078] According to this embodiment, during the movement of a non-AP MLD, the distributed MLD controller schedules the AP MLD with the best link quality in real time to communicate with the non-AP MLD, thereby avoiding the delay problems that would otherwise be caused by roaming, which is necessary to improve link quality.

[0079] (Embodiment 2) In this embodiment, the three sub-STAs of the non-AP MLD are associated with one of the three sub-APs of the AP MLD.

[0080] As shown in Figure 12, Figure 12 is a schematic diagram illustrating data communication via link 1 by an optional non-AP MLD according to Embodiment 2 of this disclosure. In Figure 12, when a non-AP MLD is near AP MLD1, the distributed MLD controller periodically collects AP link information to determine that AP MLD1 is the target AP for this non-AP MLD. The distributed MLD controller then uses the MLD traffic schedule module to schedule a data flow to AP MLD1, enabling the non-AP MLD to communicate data via link 1.

[0081] As shown in Figure 12, Figure 12 is a schematic diagram showing an optional multilink transmission via link 1 and link 3 by AP MLD1 according to Embodiment 2 of this disclosure. In Figure 12, when the non-AP MLD stabilizes near AP MLD1, the distributed MLD controller periodically collects AP link information and decides to switch the link of link 3, which has poor link quality, to AP MLD1 in a roaming manner, thereby enabling multilink transmission via link 1 and link 3 by AP MLD1.

[0082] As shown in Figure 13, Figure 13 is a schematic diagram showing an optional multilink transmission via link1, link2, and link3 by AP MLD1 according to Embodiment 2 of this disclosure. In Figure 13, if the non-AP MLD remains stable near AP MLD1, the distributed MLD controller periodically collects AP link information and decides to switch the link 2, which has relatively poor link quality, to AP MLD1 in a roaming manner, thereby enabling multilink transmission via link1, link2, and link3 by AP MLD1. When converted to a conventional MLD scenario, it has the advantages of conventional multi-link, such as high throughput and low latency.

[0083] (Embodiment 3) In this embodiment, the three sub-STAs of the non-AP MLD are associated with the three sub-APs of the AP MLD1, respectively.

[0084] As shown in Figure 14, Figure 14 is a schematic diagram illustrating an optional multilink communication between an AP MLD and a non-AP MLD according to Embodiment 3 of this disclosure. Currently, this is a conventional MLD operation scenario, in which the distributed MLD controller schedules AP MLD1 to communicate with the non-AP MLD using the MLD Traffic Schedule module, and AP MLD1 achieves multilink communication with the non-AP MLD via three links: link1, link2, and link3.

[0085] As shown in Figure 15, Figure 15 is a schematic diagram illustrating an optional reduction of transmission links from link1, link2, and link3 to link1 and link3 according to Embodiment 3 of the present disclosure. In Figure 15, when a non-AP MLD moves between AP MLD1 and AP MLD2, the distributed MLD controller determines the relative position of the non-AP MLD to each AP MLD by periodically collecting AP link information and determines a sub-STA2 of the non-AP MLD suitable for roaming. The distributed MLD controller then triggers a roaming operation, and AP2 of AP MLD2 guides the STA2 of the non-AP MLD to roam to AP2 of AP MLD2. The current transmission links are link1 and link3 (from the perspective of the non-AP MLD, the transmission links are reduced from link1, link2, and link3 to link1 and link3, but no delay issues occur due to the roaming operation).

[0086] As shown in Figure 16, Figure 16 is a schematic diagram illustrating an optional switching of transmission links from link 1 and link 3 to link 2 according to Embodiment 3 of the present disclosure. In Figure 16, the transmission links are switched from link 1 and link 3 to link 2, and as the non-AP MLD continues to move away from AP MLD1 and closer to AP MLD2, the distributed MLD controller determines the relative position of the non-AP MLD to each AP MLD by periodically collecting AP link information, and the MLD Traffic Schedule module schedules AP MLD2 to communicate with the non-AP MLD. The current transmission link is link 2 (from the perspective of the non-AP MLD, the transmission links are switched from link 1 and link 3 to link 2, but the delay of a few milliseconds due to traffic scheduling is much smaller than the delay of 50 milliseconds or more due to roaming operations).

[0087] In this embodiment, the original full link roaming operation is replaced by pre-emptive partial link roaming and subsequent traffic scheduling, significantly reducing roaming delay at the expense of only the reduction in maximum throughput caused by pre-emptive partial link roaming, making it acceptable in most application scenarios.

[0088] (Embodiment 4) As shown in Figure 17, Figure 17 is a schematic diagram illustrating an optional mode switching between distributed MLD and conventional MLD according to Embodiment 4 of the present disclosure. In Figure 17, the present embodiment supports a compatible mode between distributed MLD and conventional MLD, and the distributed MLD controller can achieve mode switching between distributed MLD and conventional MLD for specific non-AP MLDs by periodically collecting AP MLD link information.

[0089] From the above description of the embodiments, it will be understood that the method according to the embodiments described above can be implemented in a manner that adds a general-purpose hardware flap form necessary for the software, and can also be implemented by hardware, but in many cases it is preferable to implement it by the former method. Based on this, the essence of the technical aspects of the present disclosure or parts that contribute to the prior art can be implemented in the form of a software product, and such computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) that contains a plurality of instructions that cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the method according to each embodiment of the present disclosure.

[0090] Figure 18 is a block diagram (1) of the configuration of an optional non-AP MLD communication device according to the embodiment of this disclosure. As shown in Figure 18, the non-AP MLD communication device is A management module 1802 is configured to collect link information from an AP MLD for each link that is a link between a non-AP MLD and a plurality of AP MLDs, and the management module 1802 is configured to select a target AP MLD from the plurality of AP MLDs based on the link information of each link, and to communicate with the non-AP MLD via the target AP MLD.

[0091] According to the above device, the distributed MLD controller collects link information from the AP MLDs regarding the links between a non-AP MLD and multiple AP MLDs. Based on this link information, it selects a target AP MLD from among the multiple AP MLDs and communicates with the non-AP MLD through this target AP MLD. By employing the above device, link information is collected regarding the links between a non-AP MLD and multiple AP MLDs, and based on this link information, the optimal AP MLD is selected in real time from among the multiple AP MLDs. The link between this AP MLD and the non-AP MLD is then used as the transmission link, and the transmission link is adjusted using a non-roaming method. This avoids the delay problems caused by relying on roaming to adjust the transmission link. Therefore, the problem of excessive delay in data communication caused by relying on conventional roaming technology to adjust the transmission link when an AP MLD communicates with a non-AP MLD can be solved.

[0092] In one exemplary embodiment, the management module 1802 is further configured to receive a multilink association request forwarded by the AP MLD from the non-AP MLD, where the multilink association request is for indicating multiple links associated with the non-AP MLD, and the distributed MLD controller replies to the multilink association request with an allow or a reject message, and if it replies with a reject message, it sends recommended multilink information to the non-AP MLD and instructs the non-AP MLD to restart the multilink association request according to the multilink information.

[0093] In one exemplary embodiment, the management module 1802 is further configured to periodically send link measurement requests to the plurality of AP MLDs and to receive link information for each of the links sent by the plurality of AP MLDs in response to the link measurement requests.

[0094] In one exemplary embodiment, Figure 19 is a block diagram (part 2) of a communication device for an optional non-AP MLD according to an embodiment of the present disclosure. As shown in Figure 19, the device further comprises a scheduling module 1902 configured to schedule data to guide the target AP MLD to communicate with the non-AP MLD.

[0095] In one exemplary embodiment, the scheduling module 1902 is further configured to receive discovery request messages sent from the AP MLD in a unicast or broadcast manner, identify the role of the AP MLD, and declare the role information of the distributed MLD controller by replying based on the discovery request message or by actively sending a discovery response.

[0096] In one exemplary embodiment, the scheduling module 1902 is further configured to receive a join request message sent from the AP MLD, collect and maintain the multilink information contained in the join request message, and either reply a join response message permission message to the join request message or refuse the AP MLD to join the Distributed MLD group.

[0097] In one exemplary embodiment, the scheduling module 1902 is further configured to receive notification messages sent from the AP MLD and to update and maintain the multilink information contained in the notification messages.

[0098] In one exemplary embodiment, the scheduling module 1902 is further configured to send a configuration request message, either unicast or broadcast, containing link information for each of the multiple AP MLDs being maintained, requesting the AP MLDs to change their configuration according to the link information.

[0099] In one exemplary embodiment, the scheduling module 1902 is further configured to receive data and management messages transmitted from the AP MLD and / or to transmit data and management messages to the AP MLD.

[0100] In one exemplary embodiment, the scheduling module 1902 is further configured to, when it detects that the link information has changed, perform at least one of the following actions: the distributed MLD controller guides the target subSTA in the non-AP MLD to roam and enables link switching; and the distributed MLD controller selects a new target AP MLD and guides the new target AP MLD to communicate with the non-AP MLD.

[0101] In one exemplary embodiment, the above-mentioned device is configured with the Distributed MLD Service Management function, and the AP MLD is configured with the Distributed MLD Service Management function.

[0102] Specific examples in this embodiment can be found in the embodiments described above and in the exemplary embodiments, and detailed explanations are omitted in this embodiment.

[0103] Embodiments of the present disclosure further provide an electronic device comprising memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to perform steps of any of the embodiments of the method described above by executing the computer program.

[0104] Optionally, in this embodiment, the processor may be configured to perform the following steps by a computer program.

[0105] In S1, the distributed MLD controller collects link information from the AP MLDs for each link, which is the link between the non-AP MLD and multiple AP MLDs.

[0106] In S2, the distributed MLD controller selects a target AP MLD from among the multiple AP MLDs based on the link information of each link, and communicates with the non-AP MLD via the target AP MLD.

[0107] Optionally, in another embodiment, the processor may be configured to perform the following steps by a computer program.

[0108] In S1, the distributed MLD controller collects link information from the AP MLDs for each link, which is the link between the non-AP MLD and multiple AP MLDs.

[0109] In S2, the distributed MLD controller selects a target AP MLD from among the multiple AP MLDs based on the link information of each link, and communicates with the non-AP MLD via the target AP MLD.

[0110] In one exemplary embodiment, the electronic device may further comprise a transmission device and an input / output device. The transmission device is connected to the processor, and the input / output device is connected to the processor.

[0111] Specific examples in this embodiment can be found in the embodiments described above and in the exemplary embodiments, and detailed explanations are omitted in this embodiment.

[0112] Each module or step of the present disclosure described above can be implemented by a general-purpose computer, and if it can be integrated into a single computer, it can be distributed across a network of multiple computers, and furthermore, it can be implemented by program code executable by a computer, and so on

[0113] The foregoing are merely preferred embodiments of the Disclosure and are not intended to limit the Disclosure. Those skilled in the art can make various modifications and alterations to the Disclosure. Any modifications, substitutions of equivalents, or improvements within the principles of the Disclosure should be included within the scope of the Disclosure.

Claims

1. A communication method for non-AP MLD, The distributed MLD controller collects link information from the AP MLDs for each link, which is a link between a non-AP MLD and multiple AP MLDs. The distributed MLD controller selects a target AP MLD from among the plurality of AP MLDs based on the link information of each link, and communicates with the non-AP MLD via the target AP MLD. The distributed MLD controller receives a multilink association request transmitted from the non-AP MLD forwarded by the AP MLD, wherein the multilink association request is for indicating multiple links associated with the non-AP MLD. The distributed MLD controller replies to the multilink association request either an allow message or a reject message, and if it replies a reject message, it sends recommended multilink information to the non-AP MLD and instructs the non-AP MLD to restart the multilink association request according to the multilink information. A method that includes this.

2. The step in which the distributed MLD controller collects link information for each link from the AP MLD is: The distributed MLD controller periodically sends link measurement requests to the multiple AP MLDs, The method according to claim 1, comprising the step of receiving link information for each of the links transmitted by the plurality of AP MLDs in response to the link measurement request.

3. The step of communicating with the non-AP MLD via the target AP MLD is: The method according to claim 1, further comprising the step of scheduling data using an MLD Traffic Schedule module in the distributed MLD controller to guide the target AP MLD to communicate with the non-AP MLD.

4. Before the distributed MLD controller collects link information for each link from the AP MLD, the method proceeds as follows: The steps include receiving a discovery request message transmitted from the AP MLD via unicast or broadcast, and identifying the role of the AP MLD, The method according to claim 1, further comprising the step of declaring the role information of the distributed MLD controller by responding based on the discovery request message or by actively sending a discovery response.

5. Before the distributed MLD controller collects link information for each link from the AP MLD, the method proceeds as follows: The steps include receiving a join request message sent from the AP MLD, and collecting and maintaining the multilink information contained in the join request message, The method according to claim 1, further comprising the steps of responding to the join request message with a join response message permission message, or refusing to allow the AP MLD to join the Distributed MLD group.

6. Before the distributed MLD controller collects link information for each link from the AP MLD, the method proceeds as follows: The method according to claim 1, further comprising the steps of receiving a notification message transmitted from the AP MLD and updating and maintaining the multilink information contained in the notification message.

7. Before the distributed MLD controller collects link information for each link from the AP MLD, the method proceeds as follows: The method according to claim 1, further comprising the step of sending a configuration request message containing link information for each of several AP MLDs to be maintained, by unicast or broadcast, and requesting the AP MLDs to change their settings according to the link information.

8. Before the distributed MLD controller collects link information for each link from the AP MLD, the method proceeds as follows: The method according to claim 1, further comprising the steps of receiving data and management messages transmitted from the AP MLD, and / or transmitting data and management messages to the AP MLD.

9. If the link information is detected to have changed, the method shall The distributed MLD controller guides the target sub-STA within the non-AP MLD to roam and enables link switching. The method according to claim 1, further comprising at least one of the steps of: the distributed MLD controller selecting a new target AP MLD; and guiding the new target AP MLD to communicate with the non-AP MLD.

10. The method according to claim 1, wherein the distributed MLD controller is configured with the Distributed MLD Service Management function, and the AP MLD is configured with the Distributed MLD Service Management function.

11. A communication device for non-AP MLD applicable to a distributed MLD controller, A management module configured to collect link information from AP MLDs for each link between a non-AP MLD and a plurality of AP MLDs, the management module being configured to select a target AP MLD from the plurality of AP MLDs based on the link information for each link, and to communicate with the non-AP MLD via the target AP MLD, The management module is configured such that the distributed MLD controller receives a multilink association request sent from the non-AP MLD forwarded by the AP MLD, and the multilink association request is intended to indicate multiple links associated with the non-AP MLD. The management module is configured such that the distributed MLD controller responds to the multilink association request with either an allow message or a reject message, and if a reject message is returned, it sends recommended multilink information to the non-AP MLD and instructs the non-AP MLD to restart the multilink association request according to the multilink information. A communication device for non-AP MLD.

12. A computer program configured to cause a computer to perform the method described in any one of claims 1 to 10.

13. Equipped with memory and a processor, The aforementioned memory stores computer programs. An electronic device wherein the processor is configured to realize the method according to any one of claims 1 to 10 by executing the computer program.

Images