Non-AP MLD communication method and device, computer program, and electronic device

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 to a Chinese patent application filed on May 30, 2022 with the China Patent Office, bearing application number 202210601048.2 and entitled "Non-AP MLD communication method and apparatus, storage medium and electronic device," the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to the field of communications, and more particularly to a non-AP MLD communication method and device, a storage medium, and an electronic device. [Background technology]

[0003] In the future home environment, most smart home devices will be in the networking scenario of Access Point Multi-Link Device (AP MLD). In the networking scenario of AP MLD, AP MLD needs to complete the transmission link adjustment in a roaming manner when communicating with non-Access Point Multi-Link Device (non-AP MLD). Meanwhile, non-AP MLD needs to perform operations such as disassociation, reassociation, and four-way handshake when roaming, which causes the data communication delay to be more than 50ms. However, Wi-Fi7 technology, the seventh generation wireless network communication technology, needs to control the data communication delay to within 5ms, so the traditional roaming technology will not meet the technical requirements of Wi-Fi7.

[0004] Thus, in the networking scenario of AP MLD, if the traditional roaming method is adopted to adjust the transmission link when communicating between AP ML and non-AP MLD, the data communication delay will not meet the technical requirements of Wi-Fi 7. Meanwhile, in the conventional technology, the only way to realize the adjustment of the transmission link when communicating between AP ML and non-AP MLD is to rely on the traditional roaming technology.

[0005] In the prior art, when an AP MLD communicates with a non-AP MLD, the transmission link is adjusted by relying on conventional roaming technology, which causes excessive delays in data communication. At present, no effective solution has been proposed to this problem.

[0006] Therefore, there is a need for improvements in the related art to overcome the above-mentioned deficiencies in the related art. Summary of the Invention [Problem to be solved by the invention]

[0007] The embodiments of the present disclosure provide a communication method and device for non-AP MLD, a storage medium, and an electronic device, in order to at least solve the problem that in the prior art, when an AP MLD communicates with a non-AP MLD, it relies on conventional roaming technology to adjust the transmission link, which causes excessive delay in data communication. [Means for solving the problem]

[0008] In one aspect of an embodiment of the present disclosure, a communication method for a non-AP MLD is provided, the method including: a step of a distributed MLD controller collecting link information of each link between a non-AP MLD and a plurality of AP MLDs from an AP MLD; and a step of the 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.

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

[0010] According to the present disclosure, the distributed MLD controller collects link information of each link between the non-AP MLD and multiple AP MLDs from the AP MLD, selects a target AP MLD from the multiple AP MLDs based on the link information, and communicates with the non-AP MLD through the target AP MLD. By adopting the above technical aspect, link information of each link between the non-AP MLD and multiple AP MLDs is collected, and an optimal AP MLD is selected from the multiple AP MLDs in real time based on the link information, and the link between the AP MLD and the non-AP MLD is used as a transmission link, and the adjustment of the transmission link 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 in the prior art, when the AP MLD communicates with the non-AP MLD, the transmission link is adjusted by relying on the conventional roaming technology, which causes excessive delay in data communication, can be solved.

[0011] The drawings described herein constitute a part of the present disclosure to facilitate a further understanding of the present disclosure, and the exemplary embodiments and the description thereof are intended to explain the present disclosure and are not intended to unduly limit the present disclosure. [Brief description of the drawings]

[0012] [Figure 1]FIG. 2 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. [Diagram 2] FIG. 1 is a schematic diagram showing a conventional data roaming flow in the related art; [Diagram 3] FIG. 1 is an architecture diagram of a multi-link device MLD in the related art. [Figure 4] 1 is a flow diagram of an optional non-AP MLD communication method according to an embodiment of the present disclosure. [Diagram 5] FIG. 2 is an architecture diagram of an optional distributed multi-link device MLD according to an embodiment of the present disclosure. [Figure 6] 4 is a flow diagram of an optional distributed multi-link device MLD construction and maintenance according to an embodiment of the present disclosure. [Figure 7] 1 is a flow diagram of optional Distributed MLD Service Management according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a schematic diagram showing data communication via link1 by optional non-AP MLD according to the first embodiment of the present disclosure. [Figure 9] FIG. 2 is a schematic diagram showing data communication via link2 by optional non-AP MLD according to the first embodiment of the present disclosure. [Figure 10] FIG. 2 is a schematic diagram showing data communication via link2 by optional non-AP MLD according to the first embodiment of the present disclosure. [Figure 11] FIG. 11 is a schematic diagram showing data communication via link1 by optional non-AP MLD according to embodiment 2 of the present disclosure. [Figure 12] FIG. 11 is a schematic diagram showing optional multi-link transmission via link1 and link3 by AP MLD1 according to embodiment 2 of the present disclosure; [Figure 13] FIG. 11 is a schematic diagram showing optional multi-link transmission via link1, link2 and link3 by AP MLD1 according to embodiment 2 of the present disclosure; [Figure 14]FIG. 11 is a schematic diagram showing optional multi-link communication between AP MLD and non-AP MLD according to embodiment 3 of the present disclosure; [Figure 15] FIG. 11 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. [Figure 16] FIG. 11 is a schematic diagram illustrating an optional switching of transmission links from link1 and link3 to link2 according to embodiment 3 of the present disclosure. [Figure 17] FIG. 11 is a schematic diagram illustrating optional distributed MLD and conventional MLD mode switching according to the fourth embodiment of the present disclosure; [Figure 18] FIG. 1 is a configuration block diagram (part 1) of an optional non-AP MLD communication device according to an embodiment of the present disclosure. [Figure 19] FIG. 2 is a configuration block diagram (part 2) of an optional non-AP MLD communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] In the following, the technical aspects of the embodiments of the present disclosure will be clearly and completely described with reference to the drawings of the embodiments of the present disclosure, so that those skilled in the art can better understand the aspects of the present disclosure. It goes without saying that the described embodiments are only some embodiments of the present disclosure, and are not all of them. Other embodiments that those skilled in the art can obtain based on the embodiments of the present disclosure without requiring creative labor should all be included in the protection scope of the present disclosure.

[0014] In addition, the terms "first", "second", and the like in the specification and claims of the present disclosure and the drawings described above are intended to distinguish between similar objects, and are not intended to describe a specific order or priority. It should be understood that the numbers used in this manner can be interchanged where appropriate to allow the embodiments of the present disclosure described herein to be implemented in an order other than the order shown or described herein. In addition, the terms "including", "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 steps or units explicitly shown, but may include steps or units not explicitly shown for these processes, methods, products, or devices, or other steps or units inherent thereto.

[0015] The embodiment of the method provided in the embodiment of the present disclosure may be executed on a computer terminal or a similar computing device. As an example of execution on a computer terminal, FIG. 1 is a hardware configuration block diagram of a computer terminal of an optional non-AP MLD communication method according to an embodiment of the present disclosure. As shown in FIG. 1, the computer terminal may include one or more (only one is shown in FIG. 1) processors 103 (the processor 103 may include, but is not limited to, a microprocessor (Microprocessor Unit, simply referred to as MPU) or a programmable logic device (simply referred to as PLD)) and a 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. It is understood by those skilled in the art that the configuration shown in FIG. 1 is merely schematic and does not limit the configuration of the computer terminal. For example, the computer terminal may further include more or less components than those shown in FIG. 1, or may have the same functions as those shown in FIG. 1 or a different configuration from those shown in FIG. 1.

[0016] The 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 the embodiment of the present disclosure, and the processor 103 executes various functional applications and data processing by executing the computer programs stored in the memory 104, i.e., realizing the above-mentioned method. The memory 104 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memories located remotely with respect to the processor 103, and these remote memories can be connected to the computer terminal via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0017] The transmission device 106 transmits and receives data via a network. A specific example of the network may include a wireless network provided by a communication vendor of the computer terminal. 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 one example, the transmission device 106 may be a radio frequency (simply referred to as RF) module that communicates with the Internet wirelessly.

[0018] Next, the related art in this disclosure will be described. Roaming: As shown in FIG. 2, FIG. 2 is a schematic diagram showing the flow of conventional data roaming in related technology. In FIG. 2, the flow of conventional data roaming includes a process from when a station STA (Station) disassociates with a first wireless access point AP1 to when the STA re-establishes association with a second wireless access point AP2. During the technological evolution of WIFI, in order to improve the roaming experience, technologies such as 802.11V BSS transition management (BSS is a base station subsystem), 802.11r fast roaming, and 802.11ai fast initial link set up (FILS) have been introduced, and although their application scenarios are different, in terms of roaming delay, currently, 802.11r fast roaming is closest to Wi-Fi technology, and 802.11r fast roaming can keep the roaming delay to about 50 ms. This disclosure focuses on 802.11r fast roaming technology.

[0019] Multi-Link: The Multi-Link Operation technology (MLO) proposed in the current 802.11be is an important technical direction for the future Wi-Fi7, and the multi-link transmission has relatively good performance in terms of improving throughput, reducing delay, and resistance to disturbance. A Multi-Link Device (MLD) is a device with an MLO function. As shown in FIG. 3, FIG. 3 is an architecture diagram of a Multi-Link Device MLD in the related technology. In FIG. 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 assigned to the MLD lower MAC sub-layer, and the remaining MAC functions are assigned to the MLD upper MAC sublayer. A traffic identifier and link mapping information TID-to-link mapping module in a special upper MAC sublayer is used to realize a specific transmission path of data and management frames, that is, to realize the transmission of management and data frames through a certain link Link.

[0020] 4 is a flow diagram 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 FIG. 4, the non-AP MLD communication method includes the following steps S402 to S404.

[0021] In step S402, the distributed MLD controller collects link information of each link from an 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 link information of each of the links, and communicates with the non-AP MLD via the target AP MLD.

[0023] Through the above steps, the distributed MLD controller collects link information of the links between the non-AP MLD and multiple AP MLDs from the AP MLD, selects a target AP MLD from the multiple AP MLDs based on the link information, and communicates with the non-AP MLD through the target AP MLD. By adopting the above technical aspect, link information of the links between the non-AP MLD and multiple AP MLDs is collected, and further selects an optimal AP MLD from the multiple AP MLDs in real time based on the link information, and the link between the AP MLD and the non-AP MLD is used as a 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 in the prior art, when the AP MLD communicates with the non-AP MLD, the transmission link is adjusted by relying on the conventional roaming technology, which causes excessive delay in data communication, can be solved.

[0024] The distributed MLD controller is distributed among the PON chips. First, the architecture of distributed MLD will be described to help understand the present disclosure. FIG. 5 is an architecture diagram of an optional distributed multi-link device MLD according to an embodiment of the present disclosure. In FIG. 5, in the original AP MLD architecture, the IEEE802.1x protocol (access control function), A-MSDU frame aggregation, and MPDU frame encryption (key management) functions located in the MLD mac upper sublayer are moved upward to the distributed MLD controller chip of the home distributed MLD controller device. And the MLD keeps the remaining architecture as it is. In particular, the distributed MLD controller chip and AP MLD are newly added with a Distributed MLD Service Management function, which includes, but is not limited to, a Management module and a multi-link device traffic scheduling MLD Traffic Schedule module, and is configured to guide the communication between the distributed MLD controller and the target AP MLD, and realize the scheduling management of data and management information for multiple AP MLDs.

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

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

[0027] Part 1: Building and maintaining a distributed MLD In one exemplary embodiment, before collecting link information of each link from an AP MLD, the distributed MLD controller receives a discovery request message transmitted from the AP MLD in a unicast or broadcast manner, 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 actively sending a discovery response.

[0028] In addition, the AP MLD declares its role as a multilink device by sending a discovery request message in a unicast or broadcast manner. In this embodiment, the distributed MLD controller's role is a multilink device group manager.

[0029] In one exemplary embodiment, before collecting link information of each link from an AP MLD, a distributed MLD controller receives a join request message sent from the AP MLD, collects and maintains multi-link information included in the join request message, and returns a join response message permission message or denies the AP MLD from joining a Distributed MLD group in response to the join request message.

[0030] In one exemplary embodiment, before collecting link information of each link from the AP MLD, the distributed MLD controller receives a notification message sent from the AP MLD, and updates and maintains the multi-link information included in the notification message.

[0031] In one exemplary embodiment, before collecting link information of each link from the AP MLD, the distributed MLD controller sends a configuration request message including each link information of multiple AP MLDs to be maintained in a unicast or broadcast manner, and requests the AP MLD to change the setting of the AP MLD according to the each link information.

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

[0033] In the following, in order to facilitate understanding of the above-mentioned embodiment, the complete flow of the construction and maintenance of the distributed multilink device MLD will be further described. Figure 6 is a flow diagram of the construction and maintenance of the optional distributed multilink device MLD according to an embodiment of the present disclosure. As shown in Figure 6, the construction and maintenance flow of the 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 through its Multilink Device Media Access Control (MLD MAC) to obtain an Internet Protocol (IP) address and configure it for subsequent communication.

[0035] Discovery phase: AP MLD and distributed MLD controllers discover each other through a certain mechanism, and prepare for the subsequent construction of a multilink device group (MLD group). The above mechanism can be understood as the following flow.

[0036] Distributed MLD Controller: It supports receiving a discovery request message sent from the AP MLD in a unicast or broadcast manner, identifying the role of the sender (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 in the unicast or broadcast manner, and responds to searching for a multilink device group manager. It also responds to receiving a discovery response message and identifying the role of the sender.

[0038] Join phase: The AP MLD transmits its own link information and so on to the distributed MLD controller, and the distributed MLD controller decides whether or not to add this AP MLD to the distributed MLD group.

[0039] Notification phase: When the link information of AP MLD changes, AP MLD notifies the distributed MLD controller of the change by sending a notification. For example, if AP MLD originally supported three links but can now only support two links for some reason, AP MLD needs to send a notification to inform the distributed MLD controller of the change in related information.

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

[0041] For example, a distributed MLD group has AP MLD1 (link1, link2, link3), AP MLD2 (link4, link5, link6), and AP MLD3 (link7, link8). In a conventional AP MLD, only its own multilink information is included in a beacon frame. For example, AP MLD1 includes only information on link1, link2, and link3. On the other hand, in distributed MLD, AP MLD1 must include information on link1 to link8. From the perspective of a non-AP MLD, a distributed MLD is an independent AP MLD device with eight links, link1 to link8.

[0042] Data Transmission / Management Transmission Phase: The establishment of a data and management channel between the AP MLD and the distributed MLD controller is completed. The distributed MLD controller on the data channel schedules using its Traffic Schedule module and performs data communication with the AP MLD. In addition, the distributed MLD controller on the management channel periodically collects link information of each AP, and reports of changes in the AP's link information can be actively triggered.

[0043] Reconfiguration phase: When the distributed MLD controller learns that the link information of a certain AP MLD has changed, it triggers the reconfiguration of the link information of each AP MLD.

[0044] Part 2: Distributed MLD Service Management Flow In one exemplary embodiment, the distributed MLD controller is configured with a 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 includes, but is not limited to, guiding communication between the distributed MLD controller and the target AP MLD. Furthermore, the core technology of the present disclosure is the Distributed MLD Service Management function, and the present disclosure realizes dynamic adjustment of the target AP MLD and related links by periodically collecting link information, and finally realizes that the non-AP MLD completes the adjustment of the transmission link in a non-roaming manner, and reduces the transmission delay from 50 ms or more originally required for roaming to within 1 ms selected by flow scheduling. The Distributed MLD Service Management function can be realized by a Management module and an MLD Traffic Schedule module, etc., and the Management module is responsible for constructing a Distributed MLD group and maintaining management information, and is also responsible for realizing functions such as related information, periodic link information, selection of the target AP MLD, and link switching, and maintaining the management link. The MLD Traffic Schedule is responsible for managing and maintaining the data link on the distributed MLD controller and AP MLD side.

[0046] In one exemplary embodiment, the distributed MLD controller receives a multi-link association request sent from the non-AP MLD and forwarded by the AP MLD, where the multi-link association request is for indicating a plurality of links associated with the non-AP MLD. The distributed MLD controller also replies with an acceptance message or a rejection message for the multi-link association request, and when replying with the rejection message, sends recommended multi-link information to the non-AP MLD and instructs the non-AP MLD to re-initiate a multi-link association request according to the multi-link information.

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

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

[0049] In one exemplary embodiment, an 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, when it is detected that the link information has changed, the method further includes at least one of the steps of: the distributed MLD controller guiding a target sub-STA in a non-AP MLD to roam and realizing link switching; and the distributed MLD controller selecting a new target AP MLD and guiding the new target AP MLD to communicate with a non-AP MLD.

[0051] In this embodiment, when the link quality of the non-AP MLD changes, the distributed MLD controller has the following two options: 1) Guide a sub STA in the non-AP MLD to roam and realize 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 guides the new target AP MLD to communicate with the non-AP MLD through the MLD Traffic Schedule module.

[0052] In order to facilitate understanding of the above embodiment, the complete flow of the establishment and maintenance of distributed multi-link device MLD is further described below. Figure 7 is a flow chart of optional Distributed MLD Service Management according to an embodiment of the present disclosure, as shown in Figure 7, the flow of Distributed MLD Service Management includes the following steps:

[0053] Step 1: The update of link information of the distributed MLD is completed through the configuration and reconfiguration process, specifically, it can refer to the configuration phase and the reconfiguration phase in the construction and maintenance flow of the distributed MLD.

[0054] Step 2: The beacon frame transmitted independently by each AP MLD contains all the link information in the distributed MLD.

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

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

[0057] Step 5: The distributed MLD controller selects a target AP MLD for the non-AP MLD. If the non-AP MLD is associated with different AP MLDs by multi-links, at the same time, the distributed MLD controller selects only one target AP MLD to communicate with the non-AP MLD.

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

[0059] (1) Guide a sub-STA in a non-AP MLD to roam and realize link switching. That is, the distributed MLD controller guides the non-AP MLD to connect to a recommended link.

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

[0061] The present disclosure has established an architecture based on a distributed MLD scheme. The above embodiment describes how the distributed MLD controller side implements the distributed MLD scheme of the present disclosure, but the following embodiment describes how the other-AP MLD implements the solution.

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

[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 to declare its role as a multilink device, search for a multilink device group manager, and receives a discovery response message to identify 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 own multilink information, and receives the join response message to know whether the request to join the Distributed MLD group is allowed or not.

[0065] In one exemplary embodiment, when the AP MLD multilink information changes, it actively sends a notification message to inform the distributed MLD controller 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 included in the configuration request. The AP MLD also replies to the configuration request message with a configuration reply message to allow or deny the request for information configuration. If allowed, the received link information must be updated to 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 broadcast reconfiguration request and identifies link information included in the reconfiguration request. The AP MLD also replies to the reconfiguration request message with a reconfiguration reply message to allow or deny the request for information configuration. If allowed, the received link information must be updated to local link information, and the updated link information must be included in a subsequent beacon frame, etc.

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

[0069] Part 2: Distributed MLD Service Management Flow In one exemplary embodiment, the AP MLD forwards a multi-link association request sent from the non-AP MLD to the distributed MLD controller, receives an association response message sent by the distributed MLD controller in response to the multi-link association request, and forwards it to the non-AP MLD. If the response message contains recommended link information, the non-AP MLD may re-initiate a multi-link association request with the recommended link information.

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

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

[0072] In one exemplary embodiment, AP MLD corresponds to a distributed MLD controller triggered guide to link switching such as roaming of non-AP MLD designated links.

[0073] According to the above-mentioned embodiment, the conventional technology solves the problem that when an AP MLD communicates with a non-AP MLD, the transmission link is adjusted by relying on the conventional roaming technology, which causes excessive delay in data communication. To solve this problem, 1) the present disclosure establishes an architecture based on a distributed MLD scheme, and moves the IEEE802.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 the AP MLD, which realizes the scheduling management of data and management information for multiple AP MLDs. This function includes, but is not limited to, a Management module and an MLD Traffic Schedule module. 2) The present disclosure establishes a flow of distributed MLD, and describes the flow of distributed MLD group construction, MLD configuration, data transmission, etc. 3) This disclosure describes how the flow of Distributed MLD Service Management is implemented, and how a distributed MLD controller, through this flow, realizes target AP MLD selection and flow scheduling functions for a specified Non-AP MLD, thereby avoiding roaming operations and reducing delays.

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

[0075] As shown in Fig. 8, Fig. 8 is a schematic diagram illustrating data communication via link1 by optional non-AP MLD according to the first embodiment of the present disclosure. In Fig. 8, when non-AP MLD is close to AP MLD1, the distributed MLD controller determines that the target AP for this non-AP MLD is AP MLD1 by periodically collecting link information of APs. Then, the distributed MLD controller schedules data flow to AP MLD1 through the MLD Traffic Schedule module, so that non-AP MLD can realize data communication via link1.

[0076] As shown in Fig. 9, Fig. 9 is a schematic diagram illustrating data communication via link2 by optional non-AP MLD according to the first embodiment of the present disclosure. In Fig. 9, when non-AP MLD moves close to AP MLD2, the distributed MLD controller determines that the target AP for this non-AP MLD is AP MLD2 by collecting link information of each AP. Then, the distributed MLD controller schedules data flow to AP MLD2 through the MLD Traffic Schedule module, so that non-AP MLD can realize data communication via link2.

[0077] As shown in Fig. 10, Fig. 10 is a schematic diagram illustrating data communication via link2 by optional non-AP MLD according to the first embodiment of the present disclosure. In Fig. 10, when non-AP MLD continues to move close to AP MLD3, the distributed MLD controller determines that the target AP for this non-AP MLD is AP MLD3 by collecting link information of each AP. Then, the distributed MLD controller schedules data flow to AP MLD3 through the MLD Traffic Schedule module, so that non-AP MLD can realize data communication via link3.

[0078] According to this embodiment, while the non-AP MLD is moving, 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 problem that would otherwise be caused by the need for roaming to improve link quality.

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

[0080] As shown in FIG. 12, FIG. 12 is a schematic diagram illustrating data communication via link1 by optional non-AP MLD according to the second embodiment of the present disclosure. In FIG. 12, when non-AP MLD is close to AP MLD1, the distributed MLD controller determines that the target AP for this non-AP MLD is AP MLD1 by periodically collecting link information of APs. Then, the distributed MLD controller schedules data flow to AP MLD1 through the MLD traffic schedule module, so that non-AP MLD can realize data communication via link1.

[0081] As shown in Fig. 12, Fig. 12 is a schematic diagram illustrating optional multi-link transmission via link1 and link3 by AP MLD1 according to embodiment 2 of the present disclosure. In Fig. 12, when non-AP MLD is stable near AP MLD1, the distributed MLD controller periodically collects link information of APs, and determines to switch the link of link3 with poor link quality to AP MLD1 in a roaming manner, so that multi-link transmission via link1 and link3 by AP MLD1 can be realized.

[0082] As shown in FIG. 13, FIG. 13 is a schematic diagram showing the optional multi-link transmission via link1, link2 and link3 by AP MLD1 according to the second embodiment of the present disclosure. In FIG. 13, when non-AP MLD keeps stable near AP MLD1, the distributed MLD controller periodically collects the link information of APs, and decides to switch the link of link2, which has a relatively poor link quality, to AP MLD1 in a roaming manner, thereby realizing the multi-link transmission via link1, link2 and link3 by AP MLD1. If converted into a conventional MLD scenario, it has the advantages of conventional Multi-link, such as high throughput and low delay.

[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 showing an optional multi-link communication between AP MLD and non-AP MLD according to the third embodiment of the present disclosure. Currently, in the operation scenario of traditional MLD, the distributed MLD controller schedules AP MLD1 to communicate with non-AP MLD through the MLD Traffic Schedule module, where AP MLD1 realizes multi-link communication with non-AP MLD through three links: link1, link2 and link3.

[0085] As shown in FIG. 15, FIG. 15 is a schematic diagram showing the optional reduction of transmission links from link1, link2, and link3 to link1 and link3 according to the third embodiment of the present disclosure. In FIG. 15, when non-AP MLD moves between AP MLD1 and AP MLD2, the distributed MLD controller determines the relative position of non-AP MLD and each AP MLD by periodically collecting link information of AP, and determines the sub STA2 of non-AP MLD suitable for roaming. Then, the distributed MLD controller triggers a roaming operation, and the AP2 of AP MLD2 guides the STA2 of non-AP MLD to roam to the AP2 of AP MLD2. The current transmission links are link1 and link3 (from the perspective of non-AP MLD, the transmission links are reduced from link1, link2, and link3 to link1 and link3, but the delay problem caused by the roaming operation does not occur).

[0086] As shown in FIG. 16, FIG. 16 is a schematic diagram showing an optional switching of transmission links from link1 and link3 to link2 according to the third embodiment of the present disclosure. In FIG. 16, the transmission links are switched from link1 and link3 to link2, and when the non-AP MLD continues to move away from AP MLD1 and close to AP MLD2, the distributed MLD controller periodically collects the link information of APs to determine the relative positions of the non-AP MLD and each AP MLD, and schedules the AP MLD2 to communicate with the non-AP MLD by the MLD Traffic Schedule module. The current transmission link is link2 (from the perspective of the non-AP MLD, the transmission links are switched from link1 and link3 to link2, but the delay of several milliseconds caused by traffic scheduling is much smaller than the delay of 50 milliseconds or more caused by roaming operation).

[0087] In this embodiment, by replacing the original full-link roaming operation with partial link roaming in advance and subsequent traffic scheduling, the roaming delay is significantly reduced at the expense of only the marginal throughput degradation due to partial link roaming in advance, which is acceptable in most application scenarios.

[0088] (Embodiment 4) As shown in Fig. 17, Fig. 17 is a schematic diagram illustrating an optional distributed MLD and traditional MLD mode switching according to embodiment 4 of the present disclosure. In Fig. 17, in this embodiment, the compatible mode of distributed MLD and traditional MLD is supported, and the distributed MLD controller can periodically collect link information of AP MLD to realize the mode switching between distributed MLD and traditional MLD for a specific non-AP MLD.

[0089] From the above description of the embodiments, those skilled in the art can understand that the method according to the above-mentioned embodiment can be realized by adding a general-purpose hardware flip form required for software, and can also be realized by hardware, but in many cases, it is preferable to implement it in the former way. Based on this, the essence of the technical aspects of the present disclosure or a part that contributes to the prior art can be realized in the form of a software product, and the computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) containing a plurality of instructions that cause a terminal device (which may be a mobile phone, a computer, a server, a network device, etc.) to execute the method according to each embodiment of the present disclosure.

[0090] FIG. 18 is a configuration block diagram (part 1) of a communication device of optional non-AP MLD according to an embodiment of the present disclosure. As shown in FIG. 18, the communication device of non-AP MLD has The present invention further includes a management module 1802 configured to collect link information of each link, which is a link between a non-AP MLD and a plurality of AP MLDs, from an AP MLD, the management module 1802 being configured to select a target AP MLD from among the plurality of AP MLDs based on the link information of each link, and communicate with the non-AP MLD via the target AP MLD.

[0091] According to the above device, the distributed MLD controller collects link information of the links between the non-AP MLD and multiple AP MLDs from the AP MLD, selects a target AP MLD from multiple AP MLDs based on the link information, and communicates with the non-AP MLD through the target AP MLD. The above device is used to collect link information of the links between the non-AP MLD and multiple AP MLDs, and further selects an optimal AP MLD from multiple AP MLDs in real time based on the link information, and uses the link between the AP MLD and the non-AP MLD as a transmission link, thereby realizing the adjustment of the transmission link in a non-roaming manner, thereby avoiding the delay problem caused by relying on roaming to adjust the transmission link. Therefore, the problem that in the prior art, when the AP MLD communicates with the non-AP MLD, it relies on the conventional roaming technology to adjust the transmission link, which causes excessive delay in data communication, can be solved.

[0092] In one exemplary embodiment, the management module 1802 is further configured to receive a multi-link association request sent from the non-AP MLD forwarded by the AP MLD, where the multi-link association request is to indicate a plurality of links associated with the non-AP MLD, and the distributed MLD controller replies with an acceptance message or a rejection message for the multi-link association request, and if the distributed MLD controller replies with the rejection message, sends recommended multi-link information to the non-AP MLD and instructs the non-AP MLD to re-initiate a multi-link association request according to the multi-link information.

[0093] In one exemplary embodiment, the management module 1802 is further configured to periodically send link measurement requests to the multiple AP MLDs, and receive link information for each of the links sent by the multiple 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 of an optional non-AP MLD according to an embodiment of the present disclosure. As shown in Figure 19, the device further includes 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 a discovery request message 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 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 multilink information included in the join request message, and reply to the join request message with a join response message permission message or deny the AP MLD from joining a Distributed MLD group.

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

[0098] In an exemplary embodiment, the scheduling module 1902 is further configured to send a configuration request message, including each link information of a plurality of AP MLDs to be maintained, in a unicast or broadcast manner, to request the AP MLD to modify a setting of the AP MLD according to the each 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 transmit data and management messages to the AP MLD.

[0100] In one exemplary embodiment, the scheduling module 1902 is further configured to perform at least one of the following operations when it is detected that the link information has changed: guiding the distributed MLD controller to a target sub-STA in a non-AP MLD to roam and realize link switching; and guiding the distributed MLD controller to select a new target AP MLD and to communicate with a non-AP MLD.

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

[0102] As specific examples of this embodiment, reference may be made to the examples described in the above-mentioned embodiments and exemplary embodiments, and detailed description of this embodiment will be omitted.

[0103] An embodiment of the present disclosure further provides an electronic device comprising a memory and a processor, the memory having a computer program stored therein, the processor being configured to execute the computer program to implement the steps of any of the method embodiments described above.

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

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

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

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

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

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

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

[0111] As specific examples of this embodiment, reference may be made to the examples described in the above-mentioned embodiments and exemplary embodiments, and detailed description of this embodiment will be omitted.

[0112] It will be obvious to those skilled in the art that each module or step of the present disclosure described above can be realized by a general-purpose computing device, and if it can be integrated into a single computing device, it can also be distributed over a network consisting of multiple computing devices, and furthermore, it can be realized by program codes executable by computing devices, which can be stored in a storage device and executed by a computing device, and in some cases, the steps illustrated or described can be executed in a different order from that shown here, or each can be manufactured as an integrated circuit module, or multiple modules or steps can be manufactured as a single integrated circuit module. Thus, the present disclosure is not limited to any specific combination of hardware and software.

[0113] The above is merely a preferred embodiment of the present disclosure, and is not intended to limit the present disclosure. Those skilled in the art can make various modifications and variations to the present disclosure. Any modifications, equivalent replacements, improvements, etc. within the principle of the present disclosure should be included within the protection scope of the present disclosure.

Claims

1. A non-AP MLD communication method, comprising: A distributed MLD controller collects link information of each link between a non-AP MLD and a plurality of AP MLDs from the AP MLD; the distributed MLD controller selects a target AP MLD from among the plurality of AP MLDs based on link information of each of the links, and communicates with the non-AP MLD via the target AP MLD; The method includes:

2. the distributed MLD controller receiving a multi-link association request sent from the non-AP MLD forwarded by the AP MLD, the multi-link association request being for indicating a plurality of links associated with the non-AP MLD; 2. The method of claim 1, further comprising: the distributed MLD controller returning an acceptance message or a rejection message to the multi-link association request, and if the distributed MLD controller returns the rejection message, sending recommended multi-link information to the non-AP MLD and instructing the non-AP MLD to re-initiate a multi-link association request according to the multi-link information.

3. The step of the distributed MLD controller collecting link information of each link from the AP MLD includes: the distributed MLD controller periodically sending link measurement requests to the multiple AP MLDs; receiving link information for each of the links transmitted by the plurality of AP MLDs in response to the link measurement request.

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

5. Before the distributed MLD controller collects link information of each link from the AP MLD, the method further comprises: receiving a discovery request message transmitted in a unicast or broadcast manner from the AP MLD and identifying a role of the AP MLD; The method of claim 1 , further comprising: replying based on the discovery request message or declaring role information of the distributed MLD controller by actively sending a discovery response.

6. Before the distributed MLD controller collects link information of each link from the AP MLD, the method further comprises: receiving a join request message sent from the AP MLD, and collecting and maintaining multilink information included in the join request message; The method of claim 1 , further comprising: returning a join response message permission message to the join request message, or refusing to allow the AP MLD to participate in a Distributed MLD group.

7. Before the distributed MLD controller collects link information of each link from the AP MLD, the method further comprises: The method of claim 1 , further comprising the steps of receiving a notification message sent from the AP MLD, and updating and maintaining multilink information contained in the notification message.

8. Before the distributed MLD controller collects link information of each link from the AP MLD, the method further comprises:

2. The method of claim 1, further comprising: sending a configuration request message, including link information of a plurality of AP MLDs to be maintained, in a unicast or broadcast manner, to request the AP MLD to change the setting of the AP MLD according to the link information of each AP MLD.

9. Before the distributed MLD controller collects link information of each link from the AP MLD, the method further comprises: The method of 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.

10. If it is detected that the link information has changed, the method further comprises: The distributed MLD controller guides the target sub-STA in the non-AP MLD to roam and realizes link switching; the distributed MLD controller selecting a new target AP MLD and guiding the new target AP MLD to communicate with the non-AP MLD.

11. The method according to any one of claims 1 to 10, wherein a Distributed MLD Service Management function is configured in the distributed MLD controller, and the Distributed MLD Service Management function is configured in the AP MLD.

12. A non-AP MLD communication device applied to a distributed MLD controller, A communication device for a non-AP MLD comprising: a management module configured to collect link information of each link, which is a link between a non-AP MLD and a plurality of AP MLDs, from an AP MLD, the management module being configured to select a target AP MLD from among 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.

13. A computer-readable storage medium having a computer program stored thereon, A computer readable storage medium, the computer program being configured, when executed, to implement the method according to any one of claims 1 to 11.

14. A memory and a processor, The memory stores a computer program, An electronic device, wherein the processor is configured to execute the computer program to implement the method according to any one of claims 1 to 11.

Images