WO2023231422A1 - non-AP MLD的通信方法、装置、存储介质及电子装置 - Google Patents

non-AP MLD的通信方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2023231422A1
WO2023231422A1 PCT/CN2023/072698 CN2023072698W WO2023231422A1 WO 2023231422 A1 WO2023231422 A1 WO 2023231422A1 CN 2023072698 W CN2023072698 W CN 2023072698W WO 2023231422 A1 WO2023231422 A1 WO 2023231422A1
Authority
WO
WIPO (PCT)
Prior art keywords
mld
link
distributed
controller
link information
Prior art date
Application number
PCT/CN2023/072698
Other languages
English (en)
French (fr)
Inventor
李炎
唐珂
李云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023231422A1 publication Critical patent/WO2023231422A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1061—Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present disclosure relates to the field of communications, and specifically, to a communication method, device, storage medium and electronic device of non-AP MLD.
  • Wi-Fi7 Wireless Fidelity
  • Wi-Fi7 seventh-generation wireless network communication technology
  • AP MLD and non-AP MLD rely on traditional roaming technology to adjust the transmission link when communicating, resulting in excessive data communication delay. No effective solution has yet been proposed.
  • Embodiments of the present disclosure provide a non-AP MLD communication method, device, storage medium and electronic device to at least solve the problem in the prior art that AP MLD relies on traditional roaming technology to adjust transmission when communicating with non-AP MLD. link, thus causing the problem of excessive data communication delay.
  • a communication method for non-AP MLD including: a distributed MLD controller collects link information of each link from an AP MLD, wherein each link is non-AP Links between MLD and multiple AP MLDs; the distributed MLD controller selects a target AP MLD from the multiple AP MLDs according to the link information of each link, and communicates with all AP MLDs through the target AP MLD The non-AP MLD communicates.
  • a communication device for non-AP MLD including: a management module configured to collect link information of each link from the AP MLD, wherein each link is Links between non-AP MLD and multiple AP MLDs; the management module is configured to select a target AP MLD from the multiple AP MLDs according to the link information of each link, and select the target AP MLD through the target AP The MLD communicates with the non-AP MLD.
  • the distributed MLD controller collects the link information of each link between the non-AP MLD and multiple AP MLDs from the AP MLD, and then selects the target AP MLD from the multiple AP MLDs based on these link information, And communicates with non-AP MLD through this target AP MLD.
  • the link information of each link between the non-AP MLD and multiple AP MLDs is collected, and then the optimal AP MLD is selected from multiple AP MLDs in real time based on the link information, and this AP
  • the link between MLD and non-AP MLD serves 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, it can solve the problem in the existing technology that AP MLD and non-AP MLD rely on traditional roaming technology to adjust the transmission link when communicating, thereby causing excessive data communication delay.
  • Figure 1 is a hardware structure block diagram of a computer terminal of an optional non-AP MLD communication method according to an embodiment of the present disclosure
  • Figure 2 is a schematic diagram of a traditional data roaming process in related technologies
  • Figure 3 is an architecture diagram of a multi-link device MLD in related technologies
  • Figure 4 is a flow chart of an optional non-AP MLD communication method according to an embodiment of the present disclosure
  • FIG. 5 is an architectural diagram of an optional distributed multi-link device MLD according to an embodiment of the present disclosure
  • Figure 6 is a flow chart for the establishment and maintenance of an optional distributed multi-link device MLD according to an embodiment of the present disclosure
  • FIG. 7 is a flow chart of an optional Distributed MLD Service Management according to an embodiment of the present disclosure.
  • Figure 8 is a schematic diagram of an optional non-AP MLD performing data communication through link1 according to Embodiment 1 of the present disclosure
  • Figure 9 is a schematic diagram of an optional non-AP MLD performing data communication through link2 according to Embodiment 1 of the present disclosure.
  • Figure 10 is a schematic diagram of an optional non-AP MLD performing data communication through link2 according to Embodiment 1 of the present disclosure
  • Figure 11 is a schematic diagram of an optional non-AP MLD performing data communication through link1 according to Embodiment 2 of the present disclosure
  • Figure 12 is a schematic diagram of multi-link transmission of an optional AP MLD1 through link1 and link3 according to Embodiment 2 of the present disclosure
  • Figure 13 is a schematic diagram of multi-link transmission of an optional AP MLD1 through link1, link2 and link3 according to Embodiment 2 of the present disclosure
  • Figure 14 is a schematic diagram of optional multi-link communication between AP MLD and non-AP MLD according to Embodiment 3 of the present disclosure
  • Figure 15 is a schematic diagram of an optional transmission link reduced from link1, link2 and link3 to link1 and link3 according to Embodiment 3 of the present disclosure
  • Figure 16 is an illustration of an optional transmission link switching from link1 and link3 to link2 according to Embodiment 3 of the present disclosure. intention;
  • Figure 17 is a schematic diagram of optional distributed MLD and traditional MLD mode switching according to Embodiment 4 of the present disclosure
  • Figure 18 is a structural block diagram (1) of an optional non-AP MLD communication device according to an embodiment of the present disclosure
  • Figure 19 is a structural block diagram (2) of an optional non-AP MLD communication device according to an embodiment of the present disclosure.
  • FIG. 1 is a hardware structure block diagram of a computer terminal of an optional non-AP MLD communication method according to an embodiment of the present disclosure.
  • the computer terminal may include one or more (only one is shown in Figure 1) processors 103 (the processor 103 may include but is not limited to a microprocessor (Microprocessor Unit, MPU for short) or programmable logic. Device (Programmable logic device, referred to as PLD)) and a memory 104 for storing data.
  • processors 103 may include but is not limited to a microprocessor (Microprocessor Unit, MPU for short) or programmable logic.
  • Device Programmable logic device, referred to as PLD)
  • memory 104 for storing data.
  • the above-mentioned computer terminal may also include a transmission device 106 for communication functions and an input and output device 108.
  • a transmission device 106 for communication functions
  • an input and output device 108 an input and output device 108.
  • the structure shown in Figure 1 is only illustrative, and it does not limit the structure of the above-mentioned computer terminal.
  • the computer terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration with equivalent functions or more functions than shown in FIG. 1 .
  • the memory 104 can be used to store computer programs, such as software programs and modules of application software, such as computer programs corresponding to the communication methods of non-AP MLD in embodiments of the present disclosure.
  • the processor 103 runs the computer programs stored in the memory 104 , thereby executing various functional applications and data processing, that is, implementing the above method.
  • 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.
  • the memory 104 may further include memory located remotely relative to the processor 103, and these remote memories may be connected to the computer terminal through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.
  • Transmission device 106 is used to receive or send data via a network.
  • Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the computer terminal.
  • transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through base stations to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet wirelessly.
  • NIC Network Interface Controller
  • FIG. 2 is a schematic diagram of a traditional data roaming process in related technologies.
  • the traditional data roaming process includes disconnecting the slave station STA (Station) from the first wireless access point AP1 The process for the STA to re-establish association with the second wireless access point AP2.
  • BSS switching management BTM BSS transition management, where BSS is the base station subsystem
  • 802.11V BSS transition management, where BSS is the base station subsystem
  • 802.11r fast roaming of 802.11r
  • fast link of 802.11ai were introduced.
  • FILS Fast Initial Link Set Up
  • 802.11 R's fast roaming can control roaming delay to about 50ms. This disclosure focuses on the fast roaming technology of 802.11r.
  • Multi-link The multi-link operation technology (Multi-Link Operation, referred to as MLO) proposed in the current 802.11be is an important technical direction of Wi-Fi7 in the future. Multi-link transmission will improve the throughput. It has outstanding performance in terms of delay reduction and anti-interference. Multi-Link Device (MLD for short) is a device with MLO function. As shown in Figure 3, Figure 3 is an architecture diagram of a multi-link device MLD in related technologies.
  • the Media Access Control (Media Access Control, referred to as MAC) layer functions are segmented as follows, involving Framing details of Mac Procotal Date Unit (MPDU) and aggregation
  • the frame aggregation function of Aggregation Message Procotal Date Unit (A-MPDU) is divided into multi-link device media access control
  • the remaining MAC functions are divided into the multi-link device media access control upper layer MLD upper MAC sublayer; the special service identifier and link mapping information in the upper MAC sublayer TID-to-link mapping module is used to realize the specific transmission path of data and management frames, that is, to realize the transmission of management and data frames through a specific link Link.
  • FIG. 4 is a flow chart of an optional non-AP MLD communication method according to an embodiment of the present disclosure, applied to a distributed MLD controller. As shown in Figure 4, the steps of the non-AP MLD communication method include :
  • Step S402 the distributed MLD controller collects link information of each link from the AP MLD, where each link is a link between a non-AP MLD and multiple AP MLDs;
  • Step S404 The distributed MLD controller selects a target AP MLD from the multiple AP MLDs according to the link information of each link, and communicates with the non-AP MLD through the target AP MLD.
  • the distributed MLD controller collects the link information of the links between the non-AP MLD and multiple AP MLDs from the AP MLD, and then selects the target AP MLD from the multiple AP MLDs based on the link information, and Through this target AP MLD communicates with the non-AP MLD.
  • the link information of the links between non-AP MLD and multiple AP MLDs is collected, and then the optimal AP MLD is selected from multiple AP MLDs in real time based on the link information, and this AP MLD is
  • the link with the non-AP MLD is used as a transmission link to adjust the transmission link in a non-roaming manner, thus avoiding the delay problem caused by relying on roaming to adjust the transmission link. Therefore, it can solve the problem in the existing technology that AP MLD relies on traditional roaming technology to adjust the transmission link when communicating with non-AP MLD, thereby causing excessive data communication delay.
  • Figure 5 is an architectural diagram of an optional distributed multi-link device MLD according to an embodiment of the present disclosure.
  • the original AP MLD architecture Move 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 to the distributed MLD controller chip of the home distributed MLD controller device Medium; MLD keeps the rest of the architecture unchanged.
  • IEEE 802.1x protocol access control function
  • A-MSDU frame aggregation A-MSDU frame aggregation
  • MPDU frame encryption key management
  • the Distributed MLD Service Management function is added to the distributed MLD controller chip and AP MLD, including but not limited to the management module and the multi-link device traffic scheduling MLD Traffic Schedule module, which is set to guide the distributed MLD controller and Communication of target AP MLD and implementation of scheduling management of data and management information for multiple AP MLD.
  • one or more of the IEEE 802.1x (access control function), A-MSDU frame aggregation, and MPDU frame encryption (key management) located in the MLD mac upper sublayer can be moved up to the home distributed MLD controller.
  • IEEE 802.1x upward movement can enhance the management and control capabilities of the distributed MLD controller chip
  • MSDU frame aggregation can improve the transmission channel transmission efficiency
  • MPDU frame encryption can replace the transmission channel encryption, and can Used for the interaction of distributed MLD controllers and multiple AP MLD key information.
  • the following embodiment includes two parts, the first part is the establishment and maintenance of distributed MLD, and the second part is the distributed MLD service management process.
  • Part 1 Distributed MLD establishment and maintenance
  • the distributed MLD controller before collecting link information of each link from the AP MLD, receives the unicast or broadcast discovery request message sent by the AP MLD and identifies the role of the AP MLD; Reply based on the discovery request message or actively send a discovery response to announce the role information of the distributed MLD controller.
  • the AP MLD declares its role as a multi-link device by sending a unicast or broadcast discovery request message.
  • the role of the distributed MLD controller is a multi-link device group manager.
  • the distributed MLD controller before collecting the link information of each link from the AP MLD, receives the join request message sent by the AP MLD, collects and maintains the multi-link information carried in the join request message. Route information; respond to the join request message with a join response message to accept the message, or refuse the AP MLD to join the Distributed MLD group.
  • the distributed MLD controller before collecting the link information of each link from the AP MLD, receives the notification message sent by the AP MLD, and updates and maintains the multi-link information carried in the notification message.
  • the distributed MLD controller before the distributed MLD controller collects link information of each link from the AP MLD, it sends a unicast or broadcast configuration request message, where the configuration request message carries multiple APs maintained. Each link information of the MLD is requested to modify the configuration of the AP MLD according to the link information.
  • the distributed MLD controller collects link information of each link from the AP MLD, Receive data and management messages sent by the AP MLD; and/or send data and management messages to the AP MLD.
  • Figure 6 is a flow chart for establishing and maintaining an optional distributed multi-link device MLD according to an embodiment of the present disclosure. As shown in Figure 6, the process for establishing and maintaining the distributed multi-link device MLD includes:
  • Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, referred to as DHCP) phase: The AP MLD device initiates registration with the DHCP server through its own multi-link device media access control MLD MAC to obtain the Internet Protocol (Internet Protocol, referred to as IP) address. Set up for follow-up communication.
  • IP Internet Protocol
  • AP MLD and distributed MLD controller discover each other through a certain mechanism to prepare for the subsequent establishment of multi-link device group MLD group.
  • the above-mentioned certain mechanism can be understood as the following process:
  • AP MLD side supports sending unicast or broadcast discovery request messages to announce its role (multi-link device) and looking for multi-link device group managers. It supports receiving discovery response messages and identifying the role of the sender.
  • AP MLD sends its own link information to the distributed MLD controller, and the distributed MLD controller determines whether to add the AP MLD to the distributed MLD group.
  • Notification stage When the link information of AP MLD changes, AP MLD sends notification notification to inform the distributed MLD controller of this change. For example, AP MLD originally supported 3 links, but for some reasons it can only currently support 2 links. At this time, AP MLD needs to send notification to inform the distributed MLD controller of changes in relevant information.
  • the distributed MLD controller integrates the link information of all AP MLDs added to the MLD group and configures this information to each AP MLD, and the AP MLD needs to carry other AP MLDs during subsequent capability announcements and operations.
  • Link information therefore, from the perspective of non-AP MLD, distributed MLD group is a generalized MLD.
  • AP MLD1 link1, link2, link3
  • AP MLD2 link4, link5, link6
  • AP MLD3 link7, link8
  • the traditional AP MLD only carries itself in the beacon frame Multi-link information, such as AP MLD1 only carries the information of link1, link2 and link3; but in distributed MLD, AP MLD1 needs to carry the information of link1 ⁇ link8; from the perspective of non-AP MLD, distributed MLD is a network with link1 ⁇ link8 is an independent AP MLD device for these 8 links.
  • Data Transmission/Management Transmission Management Transmission stage The data and management channel between AP MLD and distributed MLD controller is established.
  • the distributed MLD controller on the data channel performs data communication with AP MLD through its own Traffic Schdule module scheduling. ;
  • the distributed MLD controller on the management channel periodically collects link information of each AP, etc., and changes in AP link information can actively trigger reporting.
  • Reconfiguration phase When the distributed MLD controller learns that the link information of an AP MLD has changed ation, triggers the reconfiguration of the link information of each AP MLD.
  • Part 2 Distributed MLD Service Management process.
  • the Distributed MLD Service Management function is provided on the distributed MLD controller, and the Distributed MLD Service Management function is provided on the AP MLD.
  • Distributed MLD Service Management functions include but are not limited to: guiding the communication between the distributed MLD controller and the target AP MLD.
  • the core technical point of this disclosure is: Distributed MLD Service Management function.
  • This disclosure achieves dynamic adjustment of target AP MLD and associated links through periodic link information collection, and ultimately realizes non-AP MLD in a non-roaming manner. The adjustment of the transmission link is completed, and the transmission delay is reduced from the original roaming requirement of more than 50ms to the flow scheduling selection of less than 1ms.
  • the Distributed MLD Service Management function can be realized through the Management module and the MLD Traffic Schedule module.
  • the Management module is responsible for the establishment and management information maintenance of the Distributed MLD group, and is responsible for associated information, periodic link information, target AP MLD selection and link switching.
  • the implementation of functions and the maintenance of management links, MLD Traffic Schedule is responsible for the management and maintenance of the data links between the distributed MLD controller and the AP MLD side.
  • the distributed MLD controller receives a multi-link association request forwarded by the AP MLD and sent by the non-AP MLD, wherein the multi-link association request is used to indicate that the Multiple links associated with the non-AP MLD; the distributed MLD controller replies with an acceptance message or a rejection message to the multi-link association request, and when replying to the rejection message, sends a message to the non-AP MLD Send recommended multi-link information to instruct the non-AP MLD to re-initiate a multi-link association request based on the multi-link information.
  • the distributed MLD controller periodically sends link measurement requests to the plurality of AP MLDs; receives the respective data sent by the multiple AP MLDs based on the link measurement requests. Link information for the link.
  • link measurement requests can be periodically sent to the multiple AP MLDs through Management of the distributed MLD controller to request multiple AP MLDs to collect link information of each link, where, Link information includes but is not limited to: operation category, channel number, physical negotiation rate, real-time rate, non-AP MLD signal strength, neighbor information, etc.
  • data is scheduled through the MLD traffic schedule module in the distributed MLD controller to guide the target AP MLD to communicate with the non-AP MLD.
  • the method further includes at least one of the following: the distributed MLD controller guides the target sub-STA in the non-AP MLD to perform Roaming to achieve link switching; the distributed MLD controller selects a new target AP MLD to guide the new target AP MLD and non-AP MLD communications.
  • the distributed MLD controller when the non-AP MLD link quality changes, the distributed MLD controller has the following two options: 1 Guide a certain sub-STA in the non-AP MLD to roam to implement 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 uses MLD Traffic The Schedule module directs communication between new target AP MLD and non-AP MLD.
  • FIG. 7 is a flow chart of an optional Distributed MLD Service Management according to an embodiment of the present disclosure. As shown in Figure 7, the process of the Distributed MLD Service Management includes:
  • Step 1 Complete the link information update of distributed MLD through the configuration and reconfigration process.
  • Step 1 Complete the link information update of distributed MLD through the configuration and reconfigration process.
  • the Configuration phase and reconfigration phase of the distributed MLD establishment and maintenance process please refer to the Configuration phase and reconfigration phase of the distributed MLD establishment and maintenance process.
  • Step 2 The beacon frame sent independently by each AP MLD contains all link information in the distributed MLD.
  • Step 3 When the Non-AP MLD actively initiates multi-link association, since the non-AP MLD cannot sense that the multi-links are distributed in different AP MLDs, it may be unreasonable to request association links.
  • Step 4 The distributed MLD controller guides the non-AP MLD to connect to the recommended link.
  • the distributed MLD controller periodically collects the link information of each AP MLD, selects the recommended link based on the AP MLD, and guides the non-AP MLD Connect to recommended links.
  • Step 5 The distributed MLD controller selects the target AP MLD for the non-AP MLD: When the non-AP MLD multi-link is associated with different AP MLD, the distributed MLD controller selects the only target AP MLD and non-AP at the same time. MLD communication.
  • Step 6 When the non-AP MLD link quality changes, the distributed MLD controller has the following two options:
  • the distributed MLD controller selects a new target AP MLD and guides the communication between the new target AP MLD and non-AP MLD through the MLD Traffic Schedule module.
  • This disclosure constructs an architecture based on a distributed MLD solution.
  • the above embodiment introduces how the distributed MLD controller side executes the distributed MLD solution of the present disclosure.
  • the following embodiment will introduce how the other end-AP MLD executes this solution. of:
  • the following embodiment includes two parts, the first part is the establishment and maintenance of distributed MLD, and the second part is the distributed MLD service management process.
  • Part One Distributed MLD establishment and maintenance.
  • the AP MLD sends a unicast or broadcast discovery request message to announce its role as a multi-link device, and to find the multi-link device group manager, and receives the discovery response message and identifies the sending of the discovery response. terminal role information.
  • the AP MLD sends a join request message, which carries its own multi-link information; the AP MLD receives the join response message and identifies whether the request to join the Distributed MLD group is accepted.
  • a notification message is actively sent. This message is used to notify the distributed MLD controller of the updated multi-link information.
  • the AP MLD receives a unicast or broadcast configuration request and identifies the link information carried in the configuration request; the AP MLD responds to the configuration request message with a configuration reply message to accept or reject the request for configuration information; if accepted, Then it is necessary to update the received link information to the local link information, and carry the updated link information in subsequent beacon frames.
  • the AP MLD receives a unicast or broadcast reconfiguration request and identifies the link information carried by the reconfiguration request; the AP MLD responds to the reconfiguration request message with a reconfiguration reply message to accept or reject the request for configuration information; if accepted, Then it is necessary to update the received link information to the local link information, and carry the updated link information in subsequent beacon frames.
  • the AP MLD receives data and management messages sent by the distributed MLD controller, and sends data and management messages to the distributed MLD controller.
  • Part 2 Distributed MLD Service Management process.
  • the AP MLD forwards the multi-link association request sent by the non-AP MLD to the distributed MLD controller, and receives and forwards the association response message replied by the distributed MLD controller in response to the multi-link association request.
  • the non-AP MLD may carry the recommended link information and initiate a multi-link association request again.
  • the AP MLD receives a link measurement request sent by the distributed MLD controller and reports link quality information in real time.
  • This link quality information includes but is not limited to: operation category, channel number, and physical negotiation rate. , real-time rate, non-AP MLD signal strength, neighbor information, etc.
  • the AP MLD supports communication of local AP MLD and non-AP MLD directed by a distributed MLD controller.
  • the AP MLD supports directing the designated link of the non-AP MLD to complete link switching through roaming and other methods triggered by the distributed MLD controller.
  • this disclosure constructs an architecture based on a distributed MLD solution, integrating the IEEE 802.1x protocol (access control function) of the MLD mac upper sublayer, A-MSDU frame aggregation, and MPDU frame encryption (key management)
  • the function is moved up to the distributed MLD controller chip of the home distributed MLD controller device.
  • the Distributed MLD Service Management function is added to the distributed MLD controller chip and AP MLD. This function implements the scheduling and management of data and management information for multiple AP MLDs.
  • This function includes but is not limited to the Management module, MLD Traffic Schedule module.
  • MLD Traffic Schedule module This disclosure constructs a distributed MLD process and describes processes such as distributed MLD group establishment, MLD configuration, and data transmission.
  • This disclosure implements the Distributed MLD Service Management process and describes how the distributed MLD controller implements the target AP MLD selection and flow scheduling functions for the specified Non-AP MLD through this process, thereby avoiding roaming operations and reducing latency.
  • three sub-STAs of the non-AP MLD are associated with one sub-AP among the three AP MLDs.
  • Figure 8 is a schematic diagram of an optional non-AP MLD performing data communication through link1 according to Embodiment 1 of the present disclosure.
  • the distribution The conventional MLD controller determines that the target AP for the non-AP MLD is AP MLD1 through periodic collection of AP link information. Then the distributed MLD controller schedules the data flow to AP MLD1 through the MLD traffic schedule module to achieve non- AP MLD implements data communication through link1.
  • Figure 9 is a schematic diagram of an optional non-AP MLD performing data communication through link2 according to Embodiment 1 of the present disclosure.
  • the distributed MLD controller determines that the target AP for the non-AP MLD is AP MLD2 based on the collection of link information of each AP. Then the distributed MLD controller schedules the data flow to AP MLD2 through the MLD traffic schedule module to implement non-AP MLD. Data communication is achieved through link2.
  • Figure 10 is a schematic diagram of an optional non-AP MLD performing data communication through link2 according to Embodiment 1 of the present disclosure.
  • the distributed MLD controller determines that the target AP for the non-AP MLD is AP MLD3 based on the collection of each AP link information, then the distributed MLD controller schedules the data flow to AP MLD3 through the MLD traffic schedule module to achieve non-AP MLD implements data communication through link3.
  • the distributed MLD controller schedules the AP MLD with the best link quality in real time to communicate with the non-AP MLD, avoiding the need for roaming to improve link quality and thus introducing delay problem.
  • three sub-STAs of the non-AP MLD are associated with one sub-AP among the three AP MLDs.
  • Figure 12 is a schematic diagram of an optional non-AP MLD performing data communication through link1 according to Embodiment 2 of the present disclosure.
  • the distribution The conventional MLD controller determines that the target AP for the non-AP MLD is AP MLD1 through periodic collection of AP link information. Then the distributed MLD controller schedules the data flow to AP MLD1 through the MLD traffic schedule module to achieve non- AP MLD implements data communication through link1.
  • Figure 12 is a schematic diagram of multi-link transmission of an optional AP MLD1 through link1 and link3 according to Embodiment 2 of the present disclosure.
  • the distributed MLD controller periodically collects the link information of the AP and determines to switch the link3 link with poor link quality to AP MLD1 through roaming. Then AP MLD1 can realize multi-link transmission of link1 and link3. .
  • Figure 13 is a schematic diagram of multi-link transmission of an optional AP MLD1 through link1, link2 and link3 according to Embodiment 2 of the present disclosure.
  • the distributed MLD controller periodically collects AP link information and determines to switch the link2 link with relatively poor link quality to AP MLD1 through roaming. Then AP MLD1 can realize link1, link2 and Link3's multi-link transmission is converted into a traditional MLD scenario and has the advantages of high throughput and low latency that traditional Multi-link has.
  • the three sub-STAs of the non-AP MLD are respectively associated with the three sub-APs of the AP MLD1.
  • Figure 14 is a schematic diagram of multi-link communication between an optional AP MLD and a non-AP MLD according to Embodiment 3 of the present disclosure. It is currently a working scenario of a traditional MLD, distributed MLD control
  • the router schedules communication between AP MLD1 and non-AP MLD through the MLD Traffic Schedule module.
  • AP MLD1 implements multi-link communication with non-AP MLD through three links: link1, link2 and link3.
  • Figure 15 is a schematic diagram of an optional transmission link reduced from link1, link2 and link3 to link1 and link3 according to Embodiment 3 of the present disclosure.
  • the distributed MLD controller determines the relative positions of non-AP MLD and each AP MLD by periodically collecting AP link information, and determines the sub-STA2 of the non-AP MLD suitable for roaming; Then the distributed MLD controller triggers the roaming operation, and AP2 of AP MLD2 guides STA2 of non-AP MLD to roam to AP2 of AP MLD2; the current transmission links are link1 and link3 (from the perspective of non-AP MLD, the transmission link From link1, link2 and link3 to link1 and link3, there is no delay problem caused by roaming operation).
  • Figure 16 is a schematic diagram of an optional transmission link switching from link1 and link3 to link2 according to Embodiment 3 of the present disclosure.
  • the transmission link is switched from link1 and link3 to link2.
  • the non-AP MLD continues to move away from AP MLD1 and moves near AP MLD2.
  • the distributed MLD controller determines the relative positions of the non-AP MLD and each AP MLD through periodic collection of AP link information, and schedules it through the MLD Traffic Schedule module AP MLD2 communicates with non-AP MLD; the current transmission link is link2 (from the perspective of non-AP MLD, the transmission link is switched from link1 and link3 to link2.
  • the delay of several milliseconds caused by traffic scheduling is far less than the five seconds of roaming operation. Delay of more than ten milliseconds).
  • the original full-link roaming operation is replaced by pre-partial link roaming and subsequent traffic scheduling, which significantly reduces the roaming delay.
  • the cost is only the reduction in the limit throughput caused by pre-partial link roaming. Therefore, It is acceptable in most application scenarios.
  • Figure 17 is a schematic diagram of optional distributed MLD and traditional MLD mode switching according to Embodiment 4 of the present disclosure.
  • this embodiment supports the compatibility mode of distributed MLD and traditional MLD.
  • the distributed MLD controller can realize switching between distributed MLD and traditional MLD modes for specific non-AP MLD by periodically collecting link information of AP MLD.
  • the method according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or that contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD), including several instructions to cause a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of various embodiments of the present disclosure.
  • FIG 18 is a structural block diagram (1) of an optional non-AP MLD communication device according to an embodiment of the present disclosure.
  • the communication devices of non-AP MLD include:
  • the management module 1802 is configured to collect link information of each link from the AP MLD, where each link is a link between a non-AP MLD and multiple AP MLDs;
  • the management module 1802 is configured to select a target from the multiple AP MLDs according to the link information of each link. AP MLD, and communicates with the non-AP MLD through the target AP MLD.
  • the distributed MLD controller collects the link information of the links between the non-AP MLD and multiple AP MLDs from the AP MLD, and then selects the target AP MLD from the multiple AP MLDs based on the link information, and Through this target AP MLD communicates with the non-AP MLD.
  • the above device is used to collect link information of links between non-AP MLD and multiple AP MLDs, and then select the optimal AP MLD from multiple AP MLDs in real time based on the link information, and combine this AP MLD with
  • the link between non-AP MLDs is used as a transmission link to adjust the transmission link in a non-roaming manner, thereby avoiding the delay problem caused by relying on roaming to adjust the transmission link. Therefore, it can solve the problem in the existing technology that AP MLD and non-AP MLD rely on traditional roaming technology to adjust the transmission link when communicating, thereby causing excessive data communication delay.
  • the management module 1802 is further configured to receive a multi-link association request forwarded by the AP MLD and sent by the non-AP MLD, wherein the multi-link association request is used to indicate the Multiple links associated with the non-AP MLD; the distributed MLD controller replies with an acceptance message or a rejection message to the multi-link association request, and when replying to the rejection message, sends a message to the non-AP MLD Send recommended multi-link information to instruct the non-AP MLD to re-initiate a multi-link association request based on the multi-link information.
  • the management module 1802 is further configured to periodically send link measurement requests to the multiple AP MLDs; and receive the link measurement requests sent by the multiple AP MLDs based on the link measurement requests. Link information for each link.
  • Figure 19 is a structural block diagram (2) of an optional non-AP MLD communication device according to an embodiment of the present disclosure. As shown in Figure 19, the above device also includes: a scheduling module 1902 , set as scheduling data to guide the target AP MLD to communicate with the non-AP MLD.
  • a scheduling module 1902 set as scheduling data to guide the target AP MLD to communicate with the non-AP MLD.
  • the scheduling module 1902 is also configured to receive the unicast or broadcast discovery request message sent by the AP MLD, and identify the role of the AP MLD; reply based on the discovery request message or actively send a discovery response. Declare the role information of the distributed MLD controller.
  • the scheduling module 1902 is also configured to receive the join request message sent by the AP MLD, collect and maintain the multi-link information carried in the join request message, and reply with a join response message in response to the join request message. Accept the message, or deny the AP MLD from joining the Distributed MLD group.
  • the scheduling module 1902 is also configured to receive the notification message sent by the AP MLD, and update and maintain the multi-link information carried in the notification message.
  • the scheduling module 1902 is also configured to send a unicast or broadcast configuration request message, wherein the configuration request message carries the link information of multiple AP MLDs maintained, requesting the AP The MLD modifies the configuration of the AP MLD according to the information of each link.
  • the scheduling module 1902 is further configured to receive data and management messages sent by the AP MLD; and/or send data and management messages to the AP MLD.
  • the scheduling module 1902 is also configured to, when detecting a change in the link information, perform processing in at least one of the following ways: the distributed MLD controller guides the non-AP The target sub-STAs in the MLD roam to implement link switching; the distributed MLD controller selects a new target AP MLD to guide communication between the new target AP MLD and the non-AP MLD.
  • the Distributed MLD Service Management function is provided on the above-mentioned device, and the Distributed MLD Service Management function is provided on the AP MLD.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
  • the above-mentioned processor may be configured to perform the following steps through a computer program:
  • the distributed MLD controller collects link information of each link from the AP MLD, where each link is a link between a non-AP MLD and multiple AP MLDs;
  • the distributed MLD controller selects a target AP MLD from the multiple AP MLDs according to the link information of each link, and communicates with the non-AP MLD through the target AP MLD.
  • the above-mentioned processor may be configured to perform the following steps through a computer program:
  • the distributed MLD controller collects link information of each link from the AP MLD, where each link is a link between a non-AP MLD and multiple AP MLDs;
  • the distributed MLD controller selects a target AP MLD from the multiple AP MLDs according to the link information of each link, and communicates with the non-AP MLD through the target AP MLD.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules or steps of the present disclosure can be implemented using general-purpose computing devices, and they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices. They may be implemented in program code executable by a computing device, such that they may be stored in a storage device for execution by the computing device, and in some cases may be executed in a sequence different from that shown herein. Or the described steps can be implemented by making them into individual integrated circuit modules respectively, or by making multiple modules or steps among them into a single integrated circuit module. As such, the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了一种non-AP MLD的通信方法、装置、存储介质及电子装置，包括：分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，各个链路为non-AP MLD与多个AP MLD之间的链路；分布式MLD控制器根据各个链路的链路信息从多个AP MLD选择目标AP MLD，并通过目标AP MLD与non-AP MLD进行通信。采用上述技术方案，解决了现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。

Description

non-AP MLD的通信方法、装置、存储介质及电子装置
本公开要求于2022年05月30日提交中国专利局、申请号为202210601048.2、发明名称“non-AP MLD的通信方法、装置、存储介质及电子装置”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开涉及通信领域，具体而言，涉及一种non-AP MLD的通信方法、装置、存储介质及电子装置。
背景技术
未来的家居环境中，智能家居设备大多处于接入点多链路设备(Access Point Multi-Link Device，简称为AP MLD)组网场景下。在AP MLD组网场景下，AP MLD与非接入点多链路设备(non-Access Point Multi-Link Device，简称为non-AP MLD)进行通信时，需要通过漫游的方式来完成传输链路的调整。而non-AP MLD进行漫游时需要进行去关联、重关联、四次握手等操作，这些操作会造成数据通信的时延超过50ms以上，但是第七代无线网络通信技术Wi-Fi7技术要求数据通信的时延控制在5ms内，因此传统的漫游技术已经不符合Wi-Fi7的技术要求。
可见，在AP MLD组网场景下，采用传统漫游的方式来调整AP ML和non-AP MLD通信时的传输链路，会导致数据通信的时延不符合Wi-Fi7的技术要求。但是现有技术却只能依赖于传统的漫游技术来实现对AP ML和non-AP MLD通信时的传输链路的调整。
针对现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题，目前尚未提出有效的解决方案。
因此，有必要对相关技术予以改良以克服相关技术中的所述缺陷。
发明内容
本公开实施例提供了一种non-AP MLD的通信方法、装置、存储介质及电子装置，以至少解决现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。
根据本公开实施例的一方面，提供一种non-AP MLD的通信方法，包括：分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；所述分布式MLD控制器根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
根据本公开实施例的又一方面，还提供了一种non-AP MLD的通信装置，包括：管理模块，设置为从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；所述管理模块，设置为根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
通过本公开，分布式MLD控制器从AP MLD收集non-AP MLD与多个AP MLD之间的各个链路的链路信息，再根据这些链路信息从多个AP MLD中选择目标AP MLD，并通过这一目标AP MLD与non-AP MLD进行通信。采用上述技术方案，收集non-AP MLD与多个AP MLD之间的各个链路的链路信息，进而根据链路信息实时从多个AP MLD中选择最优的AP MLD，并将这一AP MLD与non-AP MLD之间的链路作为传输链路，进而实现通过非漫游的方式传输链路的调整，从而规避了依赖漫游来调整传输链路导致的时延问题。因而可以解决现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示例性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例的一种可选的non-AP MLD的通信方法的计算机终端的硬件结构框图；
图2是相关技术中传统的数据漫游流程的示意图；
图3是相关技术中多链路设备MLD的架构图；
图4是根据本公开实施例的一种可选的non-AP MLD的通信方法的流程图；
图5是根据本公开实施例的一种可选的分布式多链路设备MLD的架构图；
图6是根据本公开实施例的一种可选的分布式多链路设备MLD建立和维护的流程图；
图7是根据本公开实施例的一种可选的Distributed MLD Service Management的流程图；
图8是根据本公开实施例1的一种可选的non-AP MLD通过link1进行数据通信的示意图；
图9是根据本公开实施例1的一种可选的non-AP MLD通过link2进行数据通信的示意图；
图10是根据本公开实施例1的一种可选的non-AP MLD通过link2进行数据通信的示意图；
图11是根据本公开实施例2的一种可选的non-AP MLD通过link1进行数据通信的示意图；
图12是根据本公开实施例2的一种可选的AP MLD1通过link1和link3的多链路传输的示意图；
图13是根据本公开实施例2的一种可选的AP MLD1通过link1、link2和link3的多链路传输的示意图；
图14是根据本公开实施例3的一种可选的AP MLD和non-AP MLD之间的多链路通信的示意图；
图15是根据本公开实施例3的一种可选的传输链路由link1、link2和link3降低为link1和link3的示意图；
图16是根据本公开实施例3的一种可选的传输链路由link1和link3切换到link2的示 意图；
图17是根据本公开实施例4的一种可选的分布式MLD和传统MLD模式切换的示意图；
图18是根据本公开实施例的一种可选的non-AP MLD的通信装置的结构框图(一)；
图19是根据本公开实施例的一种可选的non-AP MLD的通信装置的结构框图(二)。
具体实施方式
为了使本技术领域的人员更好地理解本公开方案，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本公开保护的范围。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开实施例中所提供的方法实施例可以在计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图1是本公开实施例的一种可选的non-AP MLD的通信方法的计算机终端的硬件结构框图。如图1所示，计算机终端可以包括一个或多个(图1中仅示出一个)处理器103(处理器103可以包括但不限于微处理器(Microprocessor Unit，简称是MPU)或可编程逻辑器件(Programmable logic device，简称是PLD))和用于存储数据的存储器104，在一个示例性实施例中，上述计算机终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述计算机终端的结构造成限定。例如，计算机终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示等同功能或比图1所示功能更多的不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的non-AP MLD的通信方法对应的计算机程序，处理器103通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器103远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输设备106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输设备106包括一个网络适配器 (Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输设备106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
接下来对本公开中的相关技术进行说明：
漫游：如图2所示，图2是相关技术中传统的数据漫游流程的示意图，在图2中，传统的数据漫游流程包括从站点STA(Station)与第一无线接入点AP1断开关联到STA重新和第二无线接入点AP2建立关联的过程。在WIFI的技术演进过程中，为了改善漫游体验推出了如802.11V的BSS切换管理BTM(BSS transmition management，其中，BSS为基站子系统)，802.11r的快速漫游fast roaming，以及802.11ai的快速链路建立(Fast Initial Link Set Up，简称为FILS)等技术，各自的应用场景有所区别，而在漫游时延方向上，目前与Wi-Fi技术中最贴近的是802.11r的fast roaming，802.11r的fast roaming可以将漫游时延控制在50ms左右。本公开关注的就是802.11r的fast roaming技术。
多链路：在目前的802.11be中提出的多链路操作技术(Multi-Link Operation，简称为MLO)是未来Wi-Fi7的一个重要技术方向，多链路的传输在吞吐量的提升，时延降低，抗干扰等方面都有较为亮眼的表现。多链路设备(Multi-Link Device，简称为MLD)是具备MLO功能的设备。如图3所示，图3是相关技术中多链路设备MLD的架构图，在图3中，将媒体访问控制(Media Access Contorl，简称为MAC)层功能做了如下的切分，涉及到mac协议数据单元(Mac Procotal Date Unit，简称为MPDU)的成帧细节和聚合mac协议数据单元(Aggregation Message Procotal Date Unit，简称为A-MPDU)的帧聚合功能划分到多链路设备介质访问控制底层MLD lower MAC sub-layer中，其余MAC功能划分到多链路设备介质访问控制高层MLD upper MAC sublayer中；特别的upper MAC sublayer中的业务标识与链路映射信息TID-to-link mapping模块用于实现数据和管理帧的具体的传输路径，即通过具体某条链路Link实现管理和数据帧的传输。
图4是根据本公开实施例的一种可选的non-AP MLD的通信方法的流程图，应用于分布式MLD控制器，如图4所示，该non-AP MLD的通信方法的步骤包括：
步骤S402，分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
步骤S404，所述分布式MLD控制器根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
通过上述步骤，分布式MLD控制器从AP MLD收集non-AP MLD与多个AP MLD之间的链路的链路信息，再根据这些链路信息从多个AP MLD中选择目标AP MLD，并通过这一目标AP MLD与non-AP MLD进行通信。采用上述技术方案，收集non-AP MLD与多个AP MLD之间的链路的链路信息，进而根据链路信息实时从多个AP MLD中选择最优的AP MLD，并将这一AP MLD与non-AP MLD之间的链路作为传输链路，进而实现通过非漫游的方式传输链路的调整，从而规避了依赖漫游来调整传输链路导致的时延问题。因而可以解决现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。
需要说明的是，上述分布式MLD控制器分布在PON芯片中。
为了帮助理解本公开，首先对分布式MLD架构进行说明，图5是根据本公开实施例的一种可选的分布式多链路设备MLD的架构图，在图5中，在原AP MLD架构中将位于MLD mac upper sublayer的IEEE 802.1x协议(访问控制功能)、A-MSDU帧聚合，MPDU帧加密(密钥管理)功能上移到入户分布式MLD控制器设备的分布式MLD控制器芯片中；MLD保持其余架构不变。特别的，分布式MLD控制器芯片和AP MLD上新增Distributed MLD Service Management功能，其中包括但不限于管理Management模块、多链路设备流量调度MLD Traffic Schedule模块，设置为引导分布式MLD控制器和目标AP MLD的通信以及实现针对多个AP MLD的数据和管理信息的调度管理。
原MLD架构中位于MLD mac upper sublayer的IEEE 802.1x(访问控制功能)、A-MSDU帧聚合，MPDU帧加密(密钥管理)可选其中一个或多个上移到入户分布式MLD控制器设备的分布式MLD控制器芯片中，其中：IEEE 802.1x上移可以增强分布式MLD控制器芯片的管控能力，MSDU帧聚合可以提升传输通道传输效率，MPDU帧加密可以代替传输通道加密，并且可以用于分布式MLD控制器和多个AP MLD密钥信息的交互。
下述实施例包括两个部分，第一部分是分布式MLD建立和维护，第二部分是分布式MLD服务管理Distributed MLD Service Management流程。
第一部分：分布式MLD建立和维护
在一个示例性实施例中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，接收所述AP MLD发送的单播或广播discovery request消息，并识别所述AP MLD的角色；基于discovery request消息回复或主动发送discovery response来宣告所述分布式MLD控制器的角色信息。
需要说明的是，AP MLD通过发送单播或广播discovery request消息来宣告自身角色为多链路设备，在本实施例中，分布式MLD控制器的角色为多链路设备组管理者。
在一个示例性实施例中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，接收所述AP MLD发送的join request消息，收集并维护所述join request消息中携带的多链路信息；针对join request消息回复join response消息接受消息，或拒绝所述AP MLD加入Distributed MLD group。
在一个示例性实施例中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，接收AP MLD发送的notification消息，更新和维护所述notification消息中携带的多链路信息。
在一个示例性实施例中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，发送单播或广播的configuration request消息，其中，所述configuration request消息中携带维护的多个AP MLD的各个链路信息，请求所述AP MLD按照所述各个链路信息修改所述AP MLD的配置。
在一个示例性实施例中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，接 收所述AP MLD发送的数据和管理消息；和/或向所述AP MLD发送数据和管理消息。
为了帮助理解上述实施例，接下来分布式多链路设备MLD建立和维护的完整流程进行进一步说明。图6是根据本公开实施例的一种可选的分布式多链路设备MLD建立和维护的流程图，如图6所示，该分布式多链路设备MLD建立和维护的流程包括：
动态主机配置协议(Dynamic Host Configuration Protoeol，简称为DHCP)阶段：AP MLD设备通过自身的多链路设备媒体访问控制MLD MAC向DHCP服务器发起注册，获取网络协议(Internet Protoeol，简称为IP)地址，设置为后续通信。
发现Discovery阶段：AP MLD和分布式MLD控制器通过某一机制发现对方，为后续的多链路设备组MLD group建立做准备，其中，上述某一机制可以理解为以下流程：
分布式MLD控制器：
支持接收AP MLD发送的单播或广播discovery request消息，并识别发送端的角色(多链路设备)；支持针对discovery request消息回复或主动发送discovery response来宣告自身角色信息(多链路设备组管理者)。
AP MLD端：支持发送单播或广播discovery request消息宣告自身角色(多链路设备)并寻找多链路设备组管理者，支持接收discovery response消息并识别发送端的角色。
加入Join阶段：AP MLD将自身的链路信息等发送给分布式MLD控制器，分布式MLD控制器确定是否将该AP MLD加入到分布式MLD group中。
通知Notification阶段：当AP MLD的链路信息发生变化时，AP MLD发送通知notification来告知分布式MLD控制器这一变化，比如，AP MLD原本支持3条链路，因为某些原因目前只能支持2条链路，此时AP MLD需要发送notification告知分布式MLD控制器相关信息的变化。
配置Configuration阶段：分布式MLD控制器整合加入到MLD group中所有AP MLD的各链路信息，并将这些信息配置给各个AP MLD，并且AP MLD在后续能力公告和运行过程中需要携带其他AP MLD的链路信息；因此，从non-AP MLD看来，分布式MLD group是个广义的MLD。
举个例子：分布式MLD group中有AP MLD1(link1，link2，link3)，AP MLD2(link4，link5，link6)，AP MLD3(link7，link8)；传统的AP MLD在信标帧中只携带自身多链路信息，如AP MLD1只携带link1、link2和link3的信息；但在分布式MLD中，AP MLD1需要携带link1～link8的信息；从non-AP MLD来看，分布式MLD是一个拥有link1～link8这8条链路的一个独立AP MLD设备。
数据传输Data Transmission/管理传输Management Transmission阶段：AP MLD和分布式MLD控制器间的数据和管理通道建立完成，数据通道上的分布式MLD控制器通过自身的Traffic Schdule模块调度和AP MLD进行数据通信；管理通道上分布式MLD控制器周期性收集各AP的链路信息等，AP的链路信息变动可以主动触发上报。
重新配置Reconfiguration阶段：当分布式MLD控制器获知某AP MLD的链路信息发生变 化时，触发重新配置各AP MLD的链路信息。
第二部分：Distributed MLD Service Management流程。
在一个示例性实施例中，所述分布式MLD控制器上设置有Distributed MLD Service Management功能，以及所述AP MLD上设置有所述Distributed MLD Service Management功能。
需要说明的是，上述Distributed MLD Service Management功能包括但不限于：引导分布式MLD控制器和目标AP MLD的通信。进一步的，本公开的核心技术点为：Distributed MLD Service Management功能，本公开通过周期性的链路信息收集实现目标AP MLD和关联链路的动态调整，最终实现non-AP MLD通过非漫游的方式完成传输链路的调整，传输时延由原本漫游要求的50ms以上降低到流调度选择的1ms以内。而Distributed MLD Service Management功能可以通过Management模块和MLD Traffic Schedule模块等来实现，其中Management模块负责Distributed MLD group建立和管理信息维护，负责关联信息、周期性链路信息、目标AP MLD选择和链路切换等功能的实现和管理链路的维护，MLD Traffic Schedule负责分布式MLD控制器和AP MLD端的数据链路的管理和维护。
在一个示例性实施例中，所述分布式MLD控制器接收所述AP MLD转发的由所述non-AP MLD发送的多链路关联请求，其中，所述多链路关联请求用于指示所述non-AP MLD所关联的多个链路；所述分布式MLD控制器针对所述多链路关联请求回复接受消息或者拒绝消息，在回复所述拒绝消息时，向所述non-AP MLD发送推荐的多链路信息，以指示所述non-AP MLD根据所述多链路信息重新发起多链路关联请求。
在一个示例性实施例中，所述分布式MLD控制器周期性的向所述多个AP MLD发送链路测量请求；接收所述多个AP MLD基于所述链路测量请求发送的所述各个链路的链路信息。
可选的，在本实施例中，可以通过分布式MLD控制器的Management周期性向所述多个AP MLD发送链路测量请求，以请求多个AP MLD收集各个链路的链路信息，其中，链路信息包括但不限于：操作类别，信道号，物理协商速率，实时速率，non-AP MLD的信号强度，邻居信息等。
在一个示例性实施例中，通过所述分布式MLD控制器中的MLD traffic schedule模块调度数据，以引导所述目标AP MLD与所述non-AP MLD进行通信。
在一个示例性实施例中，在检测到所述链路信息发生变化的情况下，所述方法还至少包括以下之一：所述分布式MLD控制器引导non-AP MLD中的目标子STA进行漫游，以实现链路切换；所述分布式MLD控制器选择新的目标AP MLD，以引导新的目标AP MLD和non-AP MLD通信。
需要说明的是，在本实施例中，当non-AP MLD链路质量变化时，分布式MLD控制器有如下两种选择：①引导non-AP MLD中某子STA漫游，实现链路切换，即分布式MLD控制器引导non-AP MLD连接推荐链路；②分布式MLD控制器选择新的目标AP MLD，通过MLD Traffic  Schedule模块引导新的目标AP MLD和non-AP MLD通信。
为了帮助理解上述实施例，接下来分布式多链路设备MLD建立和维护的完整流程进行进一步说明。图7是根据本公开实施例的一种可选的Distributed MLD Service Management的流程图，如图7所示，该Distributed MLD Service Management的流程包括：
步骤1：通过configuration和reconfigration流程完成分布式MLD的链路信息更新，具体可参见详见分布式MLD建立和维护流程的Configuration阶段和reconfigration阶段。
步骤2：各AP MLD独立发送的信标帧中包含了分布式MLD中所有链路信息。
步骤3：Non-AP MLD主动发起多链路关联时，由于non-AP MLD无法感知到多链路分布在不同AP MLD中，故请求关联链路可能并不合理。
步骤4：分布式MLD控制器引导non-AP MLD连接到推荐链路，分布式MLD控制器周期性收集各AP MLD的链路信息，并根据AP MLD选择推荐链路，并引导non-AP MLD连接到推荐链路。
步骤5：分布式MLD控制器为non-AP MLD选择目标AP MLD：当non-AP MLD多链路关联在不同AP MLD时，同一时刻分布式MLD控制器选择唯一的目标AP MLD和non-AP MLD通信。
步骤6：当non-AP MLD链路质量发生变化时，分布式MLD控制器有如下两种选择：
(1)引导non-AP MLD中某子STA漫游，实现链路切换，即分布式MLD控制器引导non-AP MLD连接推荐链路。
(2)分布式MLD控制器选择新的目标AP MLD，通过MLD Traffic Schedule模块引导新的目标AP MLD和non-AP MLD通信。
本公开构建了基于分布式MLD方案的架构，上述实施例中介绍了分布式MLD控制器端如何执行本公开的分布式MLD方案，下述实施例将介绍另一端-AP MLD是如何执行本方案的：
下述的实施例包括两个部分，第一部分是分布式MLD建立和维护，第二部分是分布式MLD服务管理Distributed MLD Service Management流程。
第一部分：分布式MLD建立和维护。
在一个示例性实施例中，AP MLD发送单播或广播discovery request消息，以宣告自身角色-多链路设备，并寻找多链路设备组管理者，并接收discovery response消息并识别discovery response的发送端的角色信息。
在一个示例性实施例中，AP MLD发送join request消息，这一join request消息中携带了自身的多链路信息；AP MLD接收join response消息并识别加入Distributed MLD group的请求是否被接受。
在一个示例性实施例中，当AP MLD的多链路信息发生变化时，主动发送notification消息，这一消息用于将更新的多链路信息通知给分布式MLD控制器。
在一个示例性实施例中，AP MLD接收单播或广播的configuration request，识别configuration request中携带的链路信息；AP MLD针对configuration request消息回复configuration repsonse消息接受或拒绝配置信息的请求；如接受，则需要将接收到的链路信息更新到本地链路信息，并在后续的信标帧等携带更新的链路信息。
在一个示例性实施例中，AP MLD接收单播或广播的reconfiguration request，并识别reconfiguration request携带的链路信息；AP MLD针对reconfiguration request消息回复reconfiguration repsonse消息接受或拒绝配置信息的请求；如接受，则需要将接收到的链路信息更新到本地链路信息，并在后续的信标帧等携带更新的链路信息。
在一个示例性实施例中，AP MLD接收分布式MLD控制器发送的数据和管理消息，并给分布式MLD控制器发送数据和管理消息。
第二部分：Distributed MLD Service Management流程。
在一个示例性实施例中，AP MLD向分布式MLD控制器转发由non-AP MLD发送的多链路关联请求，并接收针对多链路关联请求分布式MLD控制器回复的关联应答消息并转发给non-AP MLD；当该应答消息中携带推荐链路信息时，non-AP MLD可能会携带推荐链路信息再次发起多链路关联请求。
在一个示例性实施例中，AP MLD接收分布式MLD控制器发送链路测量请求，并实时上报链路质量信息，这一链路质量信息包括但不限于：操作类别，信道号，物理协商速率，实时速率，non-AP MLD的信号强度，邻居信息等。
在一个示例性实施例中，AP MLD支持分布式MLD控制器引导的本端AP MLD和non-AP MLD的通信。
在一个示例性实施例中，AP MLD支持分布式MLD控制器触发的引导non-AP MLD的指定链路通过漫游等方式完成链路切换。
通过上述实施例，解决了现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。为了解决这一技术问题，①本公开构建了基于分布式MLD方案的架构，将MLD mac upper sublayer的IEEE 802.1x协议(访问控制功能)、A-MSDU帧聚合，MPDU帧加密(密钥管理)功能上移到入户分布式MLD控制器设备的分布式MLD控制器芯片中。特别的，分布式MLD控制器芯片和AP MLD上新增Distributed MLD Service Management功能，该功能实现了针对多AP MLD的数据和管理信息的调度管理，这一功能其包括但不限于Management模块、MLD Traffic Schedule模块。②本公开构建了分布式MLD流程，描述了分布式MLD组建立，MLD配置，数据传输等流程。③本公开执行了Distributed MLD Service Management流程，描述了分布式MLD控制器通过该流程实现针对指定Non-AP MLD的目标AP MLD选择和流调度功能，进而规避漫游操作，降低时延。
实施例1
在本实施例中，non-AP MLD三个子STA与3个AP MLD中的一个子AP关联。
如图8所示，图8是根据本公开实施例1的一种可选的non-AP MLD通过link1进行数据通信的示意图，在图8中，当non-AP MLD在AP MLD1附近时，分布式MLD控制器通过周期性对AP的链路信息收集确定针对该non-AP MLD的目标AP为AP MLD1，则分布式MLD控制器通过MLD traffic schedule模块将数据流调度给AP MLD1，实现non-AP MLD通过link1实现数据通信。
如图9所示，图9是根据本公开实施例1的一种可选的non-AP MLD通过link2进行数据通信的示意图，在图9中，当non-AP MLD移动到AP MLD2附近时，分布式MLD控制器根据各AP链路信息收集确定针对该non-AP MLD的目标AP为AP MLD2，则分布式MLD控制器通过MLD traffic schedule模块将数据流调度到AP MLD2，实现non-AP MLD通过link2实现数据通信。
如图10所示，图10是根据本公开实施例1的一种可选的non-AP MLD通过link2进行数据通信的示意图，在图10中，当non-AP MLD继续移动到AP MLD3附近时，分布式MLD控制器根据各AP链路信息收集确定针对该non-AP MLD的目标AP为AP MLD3，则分布式MLD控制器通过MLD traffic schedule模块将数据流调度到AP MLD3，实现non-AP MLD通过link3实现数据通信。
通过本实施例，在non-AP MLD的移动过程中，分布式MLD控制器实时调度链路质量最好的AP MLD与non-AP MLD进行通信，规避了原本需要漫游才能改善链路质量从而引入的时延问题。
实施例2
在本实施例中，non-AP MLD三个子STA与3个AP MLD中的一个子AP关联。
如图12所示，图12是根据本公开实施例2的一种可选的non-AP MLD通过link1进行数据通信的示意图，在图12中，当non-AP MLD在AP MLD1附近时，分布式MLD控制器通过周期性对AP的链路信息收集确定针对该non-AP MLD的目标AP为AP MLD1，则分布式MLD控制器通过MLD traffic schedule模块将数据流调度给AP MLD1，实现non-AP MLD通过link1实现数据通信。
如图12所示，图12是根据本公开实施例2的一种可选的AP MLD1通过link1和link3的多链路传输的示意图，在图12中，当non-AP MLD稳定在AP MLD1附近时，分布式MLD控制器通过周期性对AP的链路信息收集确定通过漫游方式将链路质量较差的link3链路切换到AP MLD1上，进而AP MLD1可以实现link1和link3的多链路传输。
如图13所示，图13是根据本公开实施例2的一种可选的AP MLD1通过link1、link2和link3的多链路传输的示意图，在图13中，当non-AP MLD持续稳定在AP MLD1附近时，分布式MLD控制器通过周期性对AP的链路信息收集确定通过漫游方式将链路质量相对较差的link2链路切换到AP MLD1上，进而AP MLD1可以实现link1、link2和link3的多链路传输，转换成传统MLD场景，具备传统Multi-link具备的高吞吐量，低时延等优点。
实施例3
在本实施例中，non-AP MLD三个子STA分别与AP MLD1的三个子AP关联。
如图14所示，图14是根据本公开实施例3的一种可选的AP MLD和non-AP MLD之间的多链路通信的示意图，当前为传统MLD的工作场景，分布式MLD控制器通过MLD Traffic Schedule模块调度AP MLD1和non-AP MLD通信，其中AP MLD1实现了通过link1、link2和link3三条链路和non-AP MLD进行多链路通信。
如图15所示，图15是根据本公开实施例3的一种可选的传输链路由link1、link2和link3降低为link1和link3的示意图，在图15中，当non-AP MLD移动到AP MLD1和AP MLD2之间，分布式MLD控制器通过周期性对AP的链路信息收集确定non-AP MLD和各AP MLD的相对位置，并确定适合进行漫游的non-AP MLD的子STA2；然后分布式MLD控制器触发漫游操作，由AP MLD2的AP2引导non-AP MLD的STA2漫游到AP MLD2的AP2上；当前传输链路为link1和link3(从non-AP MLD角度看，传输链路由link1、link2和link3降低为link1和link3，未出现漫游操作引起的时延问题)。
如图16所示，图16是根据本公开实施例3的一种可选的传输链路由link1和link3切换到link2的示意图，在图16中，传输链路由link1和link3切换到link2当non-AP MLD继续远离AP MLD1，移动到AP MLD2附近，分布式MLD控制器通过周期性对AP的链路信息收集确定non-AP MLD和各AP MLD的相对位置，并通过MLD Traffic Schedule模块调度AP MLD2和non-AP MLD通信；当前传输链路为link2(从non-AP MLD角度看，传输链路由link1和link3切换到link2，流量调度导致的几毫秒时延，远小于漫游操作的五十毫秒以上的时延)。
本实施例中，通过预先的部分链路漫游和后续的流量调度来代替原本的全链路漫游操作，明显地降低了漫游时延，代价只是预先部分链路漫游导致的极限吞吐量降低，因而在绝大多数应用场景中是可接受的。
实施例4
如图17所示，图17是根据本公开实施例4的一种可选的分布式MLD和传统MLD模式切换的示意图，在图17中，本实施例支持分布式MLD和传统MLD的兼容模式，同时分布式MLD控制器通过周期性对AP MLD的链路信息收集可以针对具体的non-AP MLD实现分布式MLD和传统MLD模式的切换。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例的方法。
图18是根据本公开实施例的一种可选的non-AP MLD的通信装置的结构框图(一)。如图18所示，non-AP MLD的通信装置包括：
管理模块1802，设置为从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
所述管理模块1802，设置为根据所述各个链路的链路信息从所述多个AP MLD选择目标 AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
通过上述装置，分布式MLD控制器从AP MLD收集non-AP MLD与多个AP MLD之间的链路的链路信息，再根据这些链路信息从多个AP MLD中选择目标AP MLD，并通过这一目标AP MLD与non-AP MLD进行通信。采用上述装置，收集non-AP MLD与多个AP MLD之间的链路的链路信息，进而根据链路信息实时从多个AP MLD中选择最优的AP MLD，并将这一AP MLD与non-AP MLD之间的链路作为传输链路，进而实现通过非漫游的方式传输链路的调整，从而规避了依赖漫游来调整传输链路导致的时延问题。因而可以解决现有技术中，AP MLD与non-AP MLD通信时依赖于传统的漫游技术来调整传输链路，进而造成数据通信的时延过大的问题。
在一个示例性实施例中，管理模块1802，还设置为接收所述AP MLD转发的由所述non-AP MLD发送的多链路关联请求，其中，所述多链路关联请求用于指示所述non-AP MLD所关联的多个链路；所述分布式MLD控制器针对所述多链路关联请求回复接受消息或者拒绝消息，在回复所述拒绝消息时，向所述non-AP MLD发送推荐的多链路息，以指示所述non-AP MLD根据所述多链路信息重新发起多链路关联请求。
在一个示例性实施例中，管理模块1802，还设置为，周期性的向所述多个AP MLD发送链路测量请求；接收所述多个AP MLD基于所述链路测量请求发送的所述各个链路的链路信息。
在一个示例性实施例中，图19是根据本公开实施例的一种可选的non-AP MLD的通信装置的结构框图(二)，如图19所示，上述装置还包括：调度模块1902，设置为调度数据，以引导所述目标AP MLD与所述non-AP MLD进行通信。
在一个示例性实施例中，调度模块1902，还设置为接收所述AP MLD发送的单播或广播discovery request消息，并识别所述AP MLD的角色；基于discovery request消息回复或主动发送discovery response来宣告所述分布式MLD控制器的角色信息。
在一个示例性实施例中，调度模块1902，还设置为接收所述AP MLD发送的join request消息，收集并维护所述join request消息中携带的多链路信息；针对join request消息回复join response消息接受消息，或拒绝所述AP MLD加入Distributed MLD group。
在一个示例性实施例中，调度模块1902，还设置为接收AP MLD发送的notification消息，更新和维护所述notification消息中携带的多链路信息。
在一个示例性实施例中，调度模块1902，还设置为发送单播或广播的configuration request消息，其中，所述configuration request消息中携带维护的多个AP MLD的各个链路信息，请求所述AP MLD按照所述各个链路信息修改所述AP MLD的配置。
在一个示例性实施例中，调度模块1902，还设置为接收所述AP MLD发送的数据和管理消息；和/或向所述AP MLD发送数据和管理消息。
在一个示例性实施例中，调度模块1902，还设置为，在检测到所述链路信息发生变化的情况下，通过以下至少一种方式进行处理：所述分布式MLD控制器引导non-AP MLD中的目标子STA进行漫游，以实现链路切换；所述分布式MLD控制器选择新的目标AP MLD，以引导新的目标AP MLD和non-AP MLD通信。
在一个示例性实施例中，上述装置上设置有Distributed MLD Service Management功能，以及所述AP MLD上设置有所述Distributed MLD Service Management功能。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
S2，所述分布式MLD控制器根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
可选地，在另一实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
S2，所述分布式MLD控制器根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (14)

  1. 一种non-AP MLD的通信方法，包括：
    分布式MLD控制器从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
    所述分布式MLD控制器根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述分布式MLD控制器接收所述AP MLD转发的由所述non-AP MLD发送的多链路关联请求，其中，所述多链路关联请求用于指示所述non-AP MLD所关联的多个链路；
    所述分布式MLD控制器针对所述多链路关联请求回复接受消息或者拒绝消息，在回复所述拒绝消息时，向所述non-AP MLD发送推荐的多链路息，以指示所述non-AP MLD根据所述多链路信息重新发起多链路关联请求。
  3. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息，包括：
    所述分布式MLD控制器周期性的向所述多个AP MLD发送链路测量请求；
    接收所述多个AP MLD基于所述链路测量请求发送的所述各个链路的链路信息。
  4. 根据权利要求1所述的方法，其中，通过所述目标AP MLD与所述non-AP MLD进行通信，包括：
    通过所述分布式MLD控制器中的MLD traffic schedule模块调度数据，以引导所述目标AP MLD与所述non-AP MLD进行通信。
  5. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，所述方法还包括：
    接收所述AP MLD发送的单播或广播discovery request消息，并识别所述AP MLD的角色；
    基于所述discovery request消息回复或主动发送discovery response来宣告所述分布式MLD控制器的角色信息。
  6. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，所述方法还包括：
    接收所述AP MLD发送的join request消息，收集并维护所述join request消息中携带的多链路信息；
    针对所述join request消息回复join response消息接受消息，或拒绝所述AP MLD加入Distributed MLD group。
  7. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，所述方法还包括：
    接收所述AP MLD发送的notification消息，更新和维护所述notification消息中携带的多链路信息。
  8. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，所述方法还包括：
    发送单播或广播的configuration request消息，其中，所述configuration request消息中携带维护的多个AP MLD的各个链路信息，请求所述AP MLD按照所述各个链路信息修改所述AP MLD的配置。
  9. 根据权利要求1所述的方法，其中，分布式MLD控制器从AP MLD收集各个链路的链路信息之前，所述方法还包括：
    接收所述AP MLD发送的数据和管理消息；和/或向所述AP MLD发送数据和管理消息。
  10. 根据权利要求1所述的方法，其中，在检测到所述链路信息发生变化的情况下，所述方法还至少包括以下之一：
    所述分布式MLD控制器引导所述non-AP MLD中的目标子STA进行漫游，以实现链路切换；
    所述分布式MLD控制器选择新的目标AP MLD，以引导所述新的目标AP MLD和所述non-AP MLD通信。
  11. 根据权利要求1至10中任一项所述的方法，其中，所述分布式MLD控制器上设置有Distributed MLD Service Management功能，以及所述AP MLD上设置有所述Distributed MLD Service Management功能。
  12. 一种non-AP MLD的通信装置，应用于分布式MLD控制器，包括：
    管理模块，设置为从AP MLD收集各个链路的链路信息，其中，所述各个链路为non-AP MLD与多个AP MLD之间的链路；
    所述管理模块，设置为根据所述各个链路的链路信息从所述多个AP MLD选择目标AP MLD，并通过所述目标AP MLD与所述non-AP MLD进行通信。
  13. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至11任一项中所述的方法。
  14. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至11任一项中所述的方法。
PCT/CN2023/072698 2022-05-30 2023-01-17 non-AP MLD的通信方法、装置、存储介质及电子装置 WO2023231422A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210601048.2 2022-05-30
CN202210601048.2A CN117202317A (zh) 2022-05-30 2022-05-30 non-AP MLD的通信方法、装置、存储介质及电子装置

Publications (1)

Publication Number Publication Date
WO2023231422A1 true WO2023231422A1 (zh) 2023-12-07

Family

ID=88985574

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072698 WO2023231422A1 (zh) 2022-05-30 2023-01-17 non-AP MLD的通信方法、装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN117202317A (zh)
WO (1) WO2023231422A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111741500A (zh) * 2020-08-03 2020-10-02 成都极米科技股份有限公司 多链路场景下的漫游方法、多链路设备及存储介质
CN113543243A (zh) * 2020-04-18 2021-10-22 华为技术有限公司 链路处理方法、多链路设备及计算机可读存储介质
WO2021238823A1 (zh) * 2020-05-27 2021-12-02 华为技术有限公司 多链路试关联方法及相关装置
WO2022042426A1 (zh) * 2020-08-31 2022-03-03 中兴通讯股份有限公司 多链路设备、通信方法及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113543243A (zh) * 2020-04-18 2021-10-22 华为技术有限公司 链路处理方法、多链路设备及计算机可读存储介质
WO2021238823A1 (zh) * 2020-05-27 2021-12-02 华为技术有限公司 多链路试关联方法及相关装置
CN113747502A (zh) * 2020-05-27 2021-12-03 华为技术有限公司 多链路试关联方法及相关装置
CN111741500A (zh) * 2020-08-03 2020-10-02 成都极米科技股份有限公司 多链路场景下的漫游方法、多链路设备及存储介质
WO2022042426A1 (zh) * 2020-08-31 2022-03-03 中兴通讯股份有限公司 多链路设备、通信方法及存储介质

Also Published As

Publication number Publication date
CN117202317A (zh) 2023-12-08

Similar Documents

Publication Publication Date Title
EP4145947A1 (en) Multi-link tentative association method and related apparatus
TWI433566B (zh) 無線區域網路中實施交遞之無線通信方法及組件
US7623863B2 (en) System and method for adjusting connection parameters in a wireless network
CN106954236B (zh) 一种控制无线终端无缝漫游的方法和无线接入点
CN100499543C (zh) 用于对ieee802.11网络优化的快速切换方法
US7697482B2 (en) Load redistribution method and system for reducing interference in a wireless network
CN108235395A (zh) 一种实现无线终端在wlan中跨信道漫游切换的方法
JP4737400B2 (ja) ネットワーク内の移動局との通信を制御する方法
CN105210424A (zh) 无线通信系统中执行数据发送的方法和装置
WO2022012426A1 (zh) Uu路径到直接通信路径的切换及候选中继UE指示方法、装置、存储介质、终端、基站
JP5947391B2 (ja) Ｗｉｆｉ−ｄｅｃｔワイヤレス通信ネットワークにおいて端末に関連するワイヤレス・アクセス・ポイントを変更する方法
US8359030B2 (en) Method and apparatus of searching for base station using paging procedure in mobile communication network
WO2018228347A1 (zh) 无线客户端sta漫游
CN101621449A (zh) mesh网络中终端接入和代理更新的方法、装置
US20230247703A1 (en) Multi-link reconfiguration method and apparatus
CN111698742B (zh) 数据通信方法、终端设备、电子设备及计算机存储介质
EP3386240B1 (en) Switchover method in master-slave network, master device, slave device, and system
CN106454909A (zh) AP组信息处理方法及eNB
US11936589B2 (en) Systems and methods for customizing wireless communication beacons and transmitting wireless communication beacons
CN104113918B (zh) 一种切换过程中承载信息的交互方法及装置
WO2023231422A1 (zh) non-AP MLD的通信方法、装置、存储介质及电子装置
WO2023045768A1 (zh) 通信方法及相关装置
CN111277959B (zh) 一种报文转发方法及装置
US20240259777A1 (en) Feature allocation between a roaming ap mld and affiliated ap mlds
WO2023207876A1 (zh) 通信方法以及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23814621

Country of ref document: EP

Kind code of ref document: A1